Password is vaultearly644988
Pardon the dust. There's an app tie-in that I'm almost done with too, a widget-first app that shows your RSS feed collections on your phone's home screen. It would really be great if we could start to bring about an RSS renaissance!
I have sneaked in.
Suggestions:
White or almost white text would be better.
Make “Add” button visible on homepage.
Make a possibility to batch suggest feeds - a lot of people have opml xml exports from Google Reader so they can give it to you. Processing info would be nice so I as a supplier would immediately know how useful I was.
Move explanatory part of RSS to some other part than homepage.
(Not judging, just testing my radar)
I wish people would blog more like in the old days.
I care more about the stories (people call it 'content' nowadays) than about the tech, as long as the tech is open.
Can't blame them; it draws a bit more attention than normal.
I'm building Cove (https://covereader.app), a native Mac app that works as a permanent local archive. Excerpt-only feeds get the full article fetched and extracted on-device in an offline WebView, stored LZFSE-compressed. It can also read articles aloud with streaming TTS that runs entirely locally, so nothing that you read leaves the machine. No account, no servers.
Caveats: Mac-only, no sync yet, will be one-time purchase at 1.0 (beta is free now).
My favorite part of FeedLand is that you can see who subscribes to a blog and where else they subscribe. This makes RSS feel social, without the algorithmic tricks of traditional social media. Here's the listing for my blog, for example: https://feedland.com/?feedurl=https%3A%2F%2Falexsci.com%2Fbl...
We're going to have a new version pretty soon, hooking it up with RSS.chat.
https://pico.sh/feeds is an ssh app that is an rss-to-email service.
And so I wish people would stop calling feeds RSS, because it continues to compound the problem. Let RSS die! More than once I’ve seen people implement RSS feeds, at great pain and often with errors, simply because they hadn’t heard of Atom.
(I still need to decide which spec I hate more, RSS or OpenGraph. Hmm… RSS had more excuses for being bad, OpenGraph was just a spectacularly bad thing thrown over the wall by a company that should have known better. I drafted something examining how comprehensively bad it was some years ago, I should put it onto my new site and continue it at some point.)
We call them RSS feeds, RSS reader apps even if it might be implemented as an Atom feed.
While RSS is tricky to parse in practice, many of the challenges are due to invalid feeds, which Atom is not invulnerable to. Its very likely that there is a well-tested feed parser for your favorite programming language, so most developers using feed programmatically don't need to handle those challenges themselves.
For concerns like title encoding or summary vs full text description, you can handle those using namespaces. If you don't like any of the existing namespaces that do that you can create your own.
I don't really use RSS myself anymore, though; not since I stopped using Google Reader a few months before they pulled the plug. Wouldn't even know where to start nowadays.
Even though it's a simple standard that's been around for decades, there are still many sites which serve their feeds with a subtly wrong format. When something doesn't work, users come knocking on your door saying "it works in X reader but not in yours", so now you have to handle that and contribute to the ever growing list of out of spec edge cases that feed readers need to account for.