I’ve been trying various RSS readers over the last couple of months. Initial Vienna (which felt dated), then Cappuccino (buggy), and now Evergreen… thus far has been lovely.
As noted here, Evergreen is going to be the new NetNewsWire 5.0:
You probably know that I’ve been working on a free and open source reader named Evergreen. Evergreen 1.0 will be renamed NetNewsWire 5.0 — in other words, I’ve been working on NetNewsWire 5.0 all this time without knowing it!
This move back to RSS or feeds in general was a side-effect of getting away from Twitter. Wanting to get away from Twitter was… it’s not important. The end result is that i send less time being interrupted driven, but also miss more things that might be interesting.
My move to Mastodon is a rather lonely affair – without millions of users it lacks the essential “reach” that motivates people’s engagement with Twitter. In order to keep up with friends on Twitter, but without the Twitter “drama”, i’m using TwitRSS.me to scrape RSS feeds.
The RSS returned is a little funky, but Evergreen is doing a reasonable job of rendering. There seem to be alternatives (RSSHub, FetchRSS, etc), although none of them seems to be focused on keeping Twitter at arms length.
Anyway, it’s nice the NetNewsWire is coming back, and if we’re lucky some renewed interest in RSS in general.
There is very little going on (for me) on Mastodon, but it’s still interesting to see how it develops.
My latest thing is leaving a a desktop client called Whalebird open. Another Electron app… which obviously isn’t ideal, but becoming a trend – it’s quick to throw together a standalone app wrapped around the existing browser interfaces. Unfortunately it’s essentially running a full browser for every app. That probably isn’t as bad as it sounds (modern o/s have on demand page loading, etc) but it makes every Electron app an easy target for accusations of bloat.. one of those mind-numbing discussion killers, which is increasingly at odds with the amount of memory available (and generally sitting unused).
Meanwhile there is more discussion, beyond “It’s federated! It’s good!”, focusing on the practical reasons for avoiding Twitter:
The Why: Twitter Is in the Outrage Business; Mastodon Isn’t a Business
Though i don’t think it will happen, it would be interesting to see if Mastodon could survive, in it’s current rather open / tolerant form, an influx of Twitter’s current user base. Perhaps it doesn’t need to, and multiple communities can form on unconnected instances. Do we really need to suffer brands? Will instance owners actively manage their communities, and resist the “freeze peach” pressure to which Twitter has so easily yielded?
When all is said and done, i don’t think Mastodon is ever going to escape it’s niche and challenge Twitter. It might be that it’s too similar for most people’s level on engagement, and a more radical / gimmicky alternative is needed. Until that happens i’m stuck between worlds, with a curated set of Twitter friends followed via RSS!