One of the things I love about RSS and its clients is that I can walk away from my computer for a month, and then catch up (or not! I can mark feeds, folders, or the whole thing as read!) on what I've missed, whether it's from someone posting something once an hour, or something once a year, as the author suggests.<p>But with Spring 83, I leave a board, and may come back to a totally different board, knowing nothing of the context of how it got to where it is now. It's the equivalent of AIM status messages!<p>That's probably a feature in some people's minds, which is fine, but it's definitely not a feature for me.
I found the narrative explanation of this protocol really beautifully written.<p><a href="https://www.robinsloan.com/lab/specifying-spring-83/" rel="nofollow">https://www.robinsloan.com/lab/specifying-spring-83/</a>
Thread a couple of years ago <a href="https://news.ycombinator.com/item?id=32233412">https://news.ycombinator.com/item?id=32233412</a>
> Spring ’83 doesn’t formalize interactions and relationships. The protocol doesn’t provide any mechanism for replies, likes, favorites, or, indeed, feedback of any kind. Publishers are encouraged to use the full flexibility of HTML to develop their own approaches, inviting readers to respond via email, join a live chat, send a postcard … whatever!<p>I think this is one of the biggest missing features of this sort of decentralized approach to following/aggregating content. There is so much in the commenting/interaction handling of the current centralized approach that keep people coming back.
This kind of reminds me of Instagram stories, somewhat ephemeral, the current state of being of people I follow, and things I'm interested in. I guess I like the federated timeline because it's a federated timeline of things I care about.
Question: why would I use this, when it seems like it has less functions than <a href="https://en.wikipedia.org/wiki/Gemini_(protocol)" rel="nofollow">https://en.wikipedia.org/wiki/Gemini_(protocol)</a> ?
I love Robin Sloan, but why not just build this on Nostr?<p>It can do everything required here and more, and you get immediate community support, and therefore increased adoption, a broad existing list of compatible clients (depending on event kind) and immediate ability to give back real value to those who provided you with content you found valuable.<p>His objection to Mastodon is that it is a "timeline" but he doesn't even mention Nostr. There are Libraries, App Stores, Podcasting Apps, Job Boards, Live Streaming services and more built on Nostr. It can be whatever you want it to be.
It's a beautiful goal, but like so many things on the Internet, it wants a social change and hopes to achieve it via a technological solution that rejects most of the things people want from their Internet. And neither nostalgia nor technology will fix social issues.<p>If I were to put it in a quip, I'd say "Doesn't support cat pictures, dead".<p>If you truly want to fix what's broken about the Internet (and there's so much!) you will need to engage with <i>why</i> it's broken, why those forces shaped it the way they did, and how you will address those forces in your new proposals. You will need to think about why people would <i>want</i> to change their behavior.<p>I mean, don't get me wrong - it's still a very cool experiment & art project, from the builder perspective. But like most art projects, it will only reach a small audience.