[jackdawed]

That's the core challenge in designing a system like this. Echo chambers and comfort cages emerge from recommendation algorithms, and before that, from lazy curation.

If you have control over the recommendation system, you could deliberately feed it contrarian and diverse sources. Or you could choose to be very constrained. Back in RSS days, if you were lazy about it, your taste/knowledge was dependent on other people's curation and biases.

Progress happens through trends anyway. Like in 2010s, there was just a lot of Rails content. Same with flat design. It wasn't really group think, it just seemed to happen out of collective focus and necessity. Everyone else was talking/doing this so if you wanted to be a participant, you have to speak the language.

My original principle when I was using Google Reader was I didn't really know enough to have strong opinions on tech or design, so I'll follow people who seem to have strong opinions. Over time I started to understand what was good design, even if it wasn't something I liked. The rate of taste development was also faster for visual design because you could just quickly scan through an image, vs with code/writing you'd have to read it.

I did something interesting with my Last.fm data once. I've been tracking my music since 2009. Instead of getting recommendations based on my preferences, I could generate a list of artists that had no or little overlap with my current library. It was pure exploration vs exploitation music recommendation. The problem was once your tastes get diverse enough, it's hard to avoid overlaps.