I make a habit of following a few twitter accounts in my RSS reader. One thing I really hate about most organizational accounts is the way they post THE SAME THINGS repeatedly several times a day.
Then again that's probably because I'm reading it in an RSS reader instead of having it scroll by in a giant timeline.
Though I really would prefer a Mastodon interface that was more RSS flavored than 'timeline' flavored. (A feed for everyone you follow, with things being marked read or not.)
(Though now I have to take a good look at Plume and decide whether continuing OtherSky is worthwhile or whether I should just join their project. They're at least using a language I'm interested in coding in and not node.js or Python or something.)
@Azure Isn't that just a blog though? ;)
@vertigo Well, it's a microblog! And really I think the optimum would be a combination. Some subset of people one follows 'blog style' where one reads all the content they post, and then everyone else one follows being mingled together in a timeline just so you can get the /Zeitgeist/
Glitchsoc lists do something like that, but they don't track 'readness'. (And aren't integrated into ones RSS reader. Though I should look and see if they have a feed.)
@Azure My response was a bit cheeky, I'll admit.
It would be nice, I think to have a timeline user interface for one or more RSS feeds. I mean, the "home" timeline would just be an RSS feed for the microblog service as a whole. Notifications would be an RSS feed for your mentions, etc.
I think the hard part, though, is that RSS is a polled service; e.g., not terribly real-time in nature. Perhaps that can be simulated with long-polling, but that seems wasteful of server resources.
@vertigo This is something I've been thinking about for a while, off and on. Do you remember Way Back When in the 1990s when various institutions would set up Squid proxies and even arrange them into trees?
Something like this, that fans capacity out into the middle rather than requiring every site that ends up popular to be owned by some big cloud provider had appealed to me. HTTPS Everywhere kind of messes that up, though.
I've wondered about having an /authenticated/ but not /encrypted/
@vertigo delivery to try and support that kind of distributed caching, maybe even allowing peer-to-peer refresh of sites like this if I happened to know other folks subscribed to similar things I did, so long as there was a means for them to prove freshness and not-tampering.
@Azure This is a real use-case for named-data networking, a la what Van Jacobson was working on for a while (is he still involved? I've heard nothing about since about half a decade ago).
Alas, ..., this will never happen in our lifetimes, I predict. TCP/IP and its security model is too heavily baked into the psyche of network and systems engineers these days.
@vertigo Maybe? I guess it depends on what you mean by the security model. The crunchy firewall shell around a sweet, chewy center of delicious, delectable data with a distinct lack of non-perimeter access controls (or rather deficient ones) and a piquant admixture of Shadow IT is doing an excellent job of proving itself to be deficient and more interesting, less IP-based-authentication oriented models are taking off in the biggest companies, maybe they'll percolate down.
@Azure I was referring to HTTPS-everywhere in this case, but yeah, the candybar model of security is apt too. ;)
@Azure accounts “reposting for the evening (or morning) crowd” are obnoxious!
Something to work on after I finish my current ActivityPub project :)