← Back to context

Comment by quantadev

1 day ago

When BlueSky was being designed I was involved in the developer discussions and continually urged them to make simple RSS be the least common denominator of their entire spec, and build on top of RSS rather than trying to replace RSS. They listened to a lot of what I said, including my "Repository" concept where every user basically has a big repository of IPFS content addressable elements, and incorporated that into their design, which I was glad to see, but BlueSky failed miserably on the "KISS" principle, because they made every detail super complicated. It could've been RSS-compatible, and that would've changed the world, and revived RSS, which is badly needed, but sadly they were unable to see the wisdom in that.

EDIT: And most of them (BlueSky devs) indeed were far left-leaning progressives who were much more concerned with censorship than freedom of information (this being around 2020 to 2022 Silicon Valley mindset), so they continually wanted to impose lock-downs and controls on the flow of information, rather than fostering principles of openness and freedom like what RSS is all about.

Mastodon supports RSS.

  • Yeah, I've written an ActivityPub implementation of my own. Very familiar with Mastodon too of course. RSS is such low hanging fruit and so obvious a thing to use as the basis for social media posts.