Birb and Fossil: An RSS Revival?
timkellogg.me
timkellogg.me
The value of RSS to me is getting everything in chronological order, so I (not some algo) can throw 99% of it away, unread.
(and if I do want to go back and look at something I'd skipped without reading, it's easily findable, searchable by keyword or at least still there in the "read" list, next to all the things that were temporally close)
If it's ordered by algorithm I have no way of knowing what or how much I've missed.
On top of that is further organisation: non-HN feeds are batched together in a single display, but HN often produces more than a screenful (~70) of unreads, so then I have hotkeys that filter out alphabetic subsets: A-G, H-R, or S-Z. That normally suffices to avoid any scrolling, but when I haven't been following RSS for several days, I also have filters that further limit to a single day, either 1, 2, 3, or 4 days ago.
Although the underlying data is kept chronologically indexed by newsboat, and I can always refer to it that way (frex the concrete splits AG/HR/SZ were determined by querying newsboat's SQLite instance) it by no means prevents layering a myriad (well 20, not counting newsboat's ad-hoc command line filter interface) of other ways to organise on top.
PS thank you for reminding me to finally look up how to turn off threading (View»Organise by Conversation) in the mac default mail proggy!
Everything else is either an attempt to do less work or an attempt to shape user experiences for your own goals.
Threading requires two data elements per message, generated at the time of message creation: a unique-enough message ID, and the parent message ID. The client needs to have a method of storing 1 bit of state per message, either locally or on a home server. If messages have a timestamp, then a high-water mark is a useful heuristic. If the messages have required subjects, tags or topic groups, you can significantly improve both performance and user experience.
Usenet shall be resurrected, time and time again.
Generally it means "select the material and the ordering in the manner that maximizes revenue for the platform's owners". I'd call that a sensible (if morally questionable) strategy for the owners.
For example, I've started ordering my calendar by algorithm. Whatever's at the top I'll go to, even if it was a week ago. Occasionally there'll still be some other people similarly sticking around in the concert hall or meeting room. Oh boy, do they have some stories!
I've also started paying bills by algorithm. If it's important enough, I'll pay it twice. Because algorithms at identifying the products I really need to pay for. If the algorithm doesn't prioritise it, I let it slide. I feel on the vanguard.
That's the only logical way. Give it a try.
To the author's point, it's just that a lot of mass-market consumption of web content for the past decade or so has been on walled-garden platforms that never offered syndication in the first place.
But even there, I think the article is overstating things -- it implies that Reddit, HN, Medium, and Substack have only recently begun offering RSS feeds, but these have never not offered RSS feeds (and HN has always had a native top-level article feed, even if the 3rd-party solution is more extensive). Even YouTube has always offered RSS feeds (albeit without enclosures, so they can't be used as podcast feeds -- but Odysee, a web frontend to LBRY which is gaining traction against YouTube does offer feeds with enclosures).
I guess this application is a good solution for people who want to follow syndicated content via Mastodon, but it should be pointed out that the traditional model of using standalone RSS readers never went away -- when Google Reader was shut down, the void was quickly filled with a variety of solutions like TinyTinyRSS, MiniFlux, Feedly, Inoreader, etc.
I personally use TinyTinyRSS, with Liferea as a desktop client, as my primary interface to all of the blogs, podcasts, subreddits, and YouTube channels I read, along with aggregators like HN and Lobsters. I've been using this solution for over 10 years now; nothing has ever stopped working and none of the sites ever pulled back from publishing feeds.
[1]https://www.theguardian.com/technology/2023/jul/16/lbry-clos...
If you go to Explore → News on Mastodon, there's like a list of 10 trending articles within your network. It also includes "discussed by X people in the past Y days", but annoyingly there's no way to reach those discussions and read what people thought about the article.
So I feel like Mastodon's moving in the right path to serve that purpose, it's just unfinished.
stop commenting when your comment tells others to stop doing what they like because you don't like it.
i'm not interested in changing your mind.
What is a dissenting opinion other than an expression of dissatisfaction toward a thing, be that an action of another or not? You say dissent is okay, byt in the same breath say byt only if you do it the way I think it should be done.
Hypocrisy is a helluva drug, I guess.
Anyway, have a great day. Didn't mean to piss in anyone's cereal quite this early.
Anyway, I have unpopular, but sincerely held opinions - anyone is free to disagree, of course. The point I'm trying to get to is that while I hardly ever downvote, if I did, I would hope that I would also comment on what the issue was.
As a courtesy, it should be downvote + comment, if poss.
I don't see how using an optional, open-source, non-chronological feed means that someone should just "go use Twitter". For one, the incentives are completely different between Twitter which generates revenue based on engaging users (and juicing subsequent algorithms), and someone who builds a separate feed interface for Mastodon.
>I don't get this mentality of "I like X, but I don't want to use X, so imma go turn Y into X" some devs seem to have.
Developers like to solve problems and build things. I've re-created other projects and products lots of times. Why is it a problem what someone chooses to do with their own time for their own reasons?
>Playing into people's FOMO is what got the Internet into the rat's nest
Disagree. Incentives tied to advertising-based business models is the root cause here, not FOMO.
Disclaimer: I made my own alternative timeline for Mastodon as well, so I'm pretty biased. :)
We can perhaps agree to disagree on that, but I'm considering your other points.
FOMO is the psychological response that the ad-based algorithm is playing off of, neither one is the problem in and of itself.
You really don't understand why someone would prefer Mastodon because of its decentralized and open source nature, but would like to take some of the things they like about Twitter and include it in their Mastodon experience?
> Playing into people's FOMO
This implies that the only form of "algorithmic feed" is one where clickbait and inflammatory content is maximized.
An algorithmic feed can also mean something like a "for you" feed that tries to find you posts you'd find interesting based solely on your current follows, but from other accounts you're not following.
It can also mean a "what you missed" feed like the one Twitter used to have, that shows you the top posts from your follows since the last time you logged in. If someone doesn't open mastodon for a week because they were on vacation, it's not feasible for them to scroll through an entire weeks worth of posts to "catch up".
Understand that people have a wide variety of experiences they'd like to get out of social media, and that this whole mentality of "my idea of a social network is the most enlightened and correct one, and everyone else is stupid" just feeds into the stereotype of the socially inept engineer.
I am not saying algos are bad, so I should clarify that. What I should have directed my ire at is the people that implement them since, historically speaking, they can not be trusted to do so without bias or other motives. Chronological feeds cannot be abused in this way, to my knowledge, and represent a state of purity in my mind.
Appreciate you taking the time to make salient points, though.
IMO this is the fundamental reason for chronological feeds. Aligning the algorithm is an unsolved problem, I'd rather just not use it at all.
Use case: I want to log into Mastodon once or twice a week. I want to follow lots of interesting people and topics, but I don't have time to read it all. So, I want to have an algorithm that allows me to see all things from a subset of accounts I consider friends and, after that, see the most shared and starred from the larger group I follow, then the most shared and starred from the topics I follow.
But if I happen to be browsing more frequently, I can see the chronological feed again in that order: close friends, acquaintances, topics. This isn't what Twitter does: their algorithm does not serve me.
I'll you the same thing I told the other responder; Hypocrisy's a helluva drug, eh?
Anyway, moving on.
/joke
What I'm mainly curious about here is what drew this author to these two technologies in the first place? What's the hook for them?
---
Subjective aside: before I read the line on algorithms & the HN comments bemoaning the same, I was already very turned off by the awful AI header image. Until tools like Dall-E, &c. get to the point where they can reliably generate images that aren't blatantly & obviously AI-generated (they seem a surprisingly long way off still), I think this effect is worth keeping in mind: for me the aesthetic is a massive turnoff for any product page.
My comment does seem a little dogmatic whereas there's always a broad variety of approaches & preferences with anything. I was somewhat exaggerating, but my goal was to represent the typical user as best as I can glean.
As someone who advocated heavily for Mastodon (& continues to), I spend more time on bsky now, but I've found people's reasons for being there over Mastodon to be either my reason: network effect, or for the vast majority of folk: UX. ActivityPub client/server UX remains abysmal in comparison to centralised services (not complaining as I know it's a harder problem for decentralised tech, just stating the fact).
Algorithmic feeds haven't come up in the context of bsky prefs mainly because - in my experience - algorithmic feeds in any app/website are broadly hated by all but the most tech-savvy of people.
"Newest first" is annoying because unless I manage to read everything that's new then I have gaps. If I've only got a couple of minutes now then I want to be able to see a few things without losing track of what I have and haven't read.
"Oldest first" is annoying because -- as much as I might want to -- I can't keep up.
"Newest unread" is annoying because if someone's posted a series then I want to read them in order.
"Prioritised unread" might be OK -- if someone only posts once a month then I probably want to prioritise reading their post over reading absolutely everything by someone who posts multiple times a day.
I'm currently reading my RSS with Newsblur, and it's not perfect but it does give me flexibility through the "intelligence trainer" to highlight the stuff I want to prioritise.
Aside, RSS and Mastodon definitely are algorithmic. "Chronological ordering" is an algorithm, and it's not always the most appropriate.
https://www2.fossil-scm.org/home/doc/trunk/www/index.wiki
Since fossil SCM has been around awhile, the author might consider a name change to avoid confusion?
Ten seconds of reading and you'd have avoided any confusion.