I'm staying away from macOS Tahoe for now. NetNewsWire has already announced that they will no longer support the earlier 6.x release that I use. I assume that means no bug fixes or back-porting of new features. Sad.
NetNewsWire Turns 23
81–90 of 108 posts
Re: NetNewsWire Turns 23
#82Earlier quoted context omitted.
> gotta pick your battles carefully Ok, and how is wasting time making the design worse to follow the OS instead of spending that time implementing missing features a carefully picked battle? I thought the philosophy was prioritizing quality > You can still use the version you're using Which would be missing bug fixes and those slow features the may be added next year
The app has always followed the masOS design language, because the app is built using the native macOS tools. It makes sense for it to match the OS it's on, apps built with stand UI components migrated to 'Liquid glass' much easier. The app is open source ( https://github.com/Ranchero-Software/NetNewsWire ), feel free to back-port any features or bug-fixes you would like to spend your time on.
Your suggestion is just as senseless: among the many things wrong with such a "write the app yourself" approach, you forgot about iOS, even though it's mentioned in the original comment, where you can't freely backport anything due to distribution being locked down
Re: NetNewsWire Turns 23
#83Earlier quoted context omitted.
Oh, thanks for the hint! I might be able to remove some code from my feed detection code (on pipes) then. But on a first glance, it seems like alternate links for channels are back, but playlists are missing. Still, that might be a step forward.
I think openrss.org has YouTube playlist feeds
Using openrss.org as an intermediary might work as well, but not ideal to rely on a third party for that.
Re: NetNewsWire Turns 23
#84More and more we need RSS feeds and this is the best app for consuming them for me. Happy Birthday.
Re: NetNewsWire Turns 23
#85Hands down the best RSS reader I've used. It's fast, tiny, built extremely well, and has no flab. It sits in a certain class of application along with Alfred and a handful of others in being a standout example of craftsmanship that's reminiscent of the golden era of OS X. More apps should strive for this standard.
- The feed item (read the XML)
- The site fulltext
- The original site (in case of login required)
For me that app is https://www.lireapp.com/
Re: NetNewsWire Turns 23
#86The biggest problem with newsreaders, IME, has been managing large numbers of feeds. Most user time is spent handling redundant stories - e.g., if you have feeds from many major news sources, for each major event you get one or more stories on each feed, saying mostly the same things. I haven't seen a newsreader solve that problem. Has anyone tried an LLM? The best solution I know is grouping redundant stories togeth…
If you do the embeddings calculation centrally, it becomes shared cost. Every new article gets analyzed only once for all users.
The rest then becomes providing a new view on your RSS feeds that leverages that. You could do a lot of the expensive stuff (vector comparisons) locally actually because most users only have hundreds/thousands of articles that they care about. So, simply download the embeddings for articles and do the comparisons/grouping locally.
This wouldn't be super hard to do. There are lots of OSS models that you can run locally as well. But they are kind of slow. So the trick is to amortize that over many users and share the burden.
The key challenge here is the finances. The centralized embeddings juggling gets costly quickly and you need a revenue model to finance that. That's why most of this stuff is happening by paywalls and staying kind of niche. All the "free" stuff is essentially ad sponsored.
But with some MCP layered on top and a few other bits and bobs, you could fairly easily implement an intelligent LLM based news agent that summarizes personalized news based on exactly your own preferences and news subscriptions. I haven't really seen anything like this done right. But we technically have all the OSS tech and models to do all of this now. It's just the compute cost that kills the use case.
If that could be decentralized bittorrent style, it wouldn't actually be that much of a burden. Given enough users, distributing say thousands of article updates per minute among tens/hundreds of thousands of readers means each of them expending maybe a couple of seconds of compute once in a while to calculate embeddings for articles that they are pulling that don't have embeddings yet. If you make that eventually consistent, it's not that big of a deal if you don't get embeddings for all the new stuff right away. And any finished embeddings could be uploaded and shared. Anything popular would quickly get embeddings. And you could make the point that publishers themselves could be providing embeddings as well for their own articles. Why not? If you only publish a handful of articles, the cost is next to nothing.
If I had more spare time, I might have a go at this. Sadly, I don't.
Re: NetNewsWire Turns 23
#87The biggest problem with newsreaders, IME, has been managing large numbers of feeds. Most user time is spent handling redundant stories - e.g., if you have feeds from many major news sources, for each major event you get one or more stories on each feed, saying mostly the same things. I haven't seen a newsreader solve that problem. Has anyone tried an LLM? The best solution I know is grouping redundant stories togeth…
You should try Scour ( https://scour.ing )! You specify your interests as free form text, it ranks articles by how closely they match, and you can consume your Scour feed as an RSS feed to read it in NNW. Disclaimer: I’m the developer
Re: NetNewsWire Turns 23
#88NNW is 100% on that list. It was my first feedreader, but at some point I shifted away from it (I think there was a time when it wouldn't sync with other services?), and now for years I've been using Feedbin's web client on my Mac instead of anything native because it's surprisingly solid. (On iOS, I use Reeder.)
But NetNewsWire is still awesome. I'm glad it's there, and I'm grateful that Brent and Sheila Simmons are out there making excellent software.
Re: NetNewsWire Turns 23
#89Earlier quoted context omitted.
The app has always followed the masOS design language, because the app is built using the native macOS tools. It makes sense for it to match the OS it's on, apps built with stand UI components migrated to 'Liquid glass' much easier. The app is open source ( https://github.com/Ranchero-Software/NetNewsWire ), feel free to back-port any features or bug-fixes you would like to spend your time on.
It doesn't make sense because the previous version also matches the OS it's on, liquid glass degradation isn't mandatory and "much easier" is still harder than doing the better nothing. Your suggestion is just as senseless: among the many things wrong with such a "write the app yourself" approach, you forgot about iOS, even though it's mentioned in the original comment, where you can't freely backport anything due to…
> you forgot about iOS, even though it's mentioned in the original comment, where you can't freely backport anything due to distribution being locked down
Yes you can. You can create an app today that is compatible with iOS 15.
Re: NetNewsWire Turns 23
#90Hands down the best RSS reader I've used. It's fast, tiny, built extremely well, and has no flab. It sits in a certain class of application along with Alfred and a handful of others in being a standout example of craftsmanship that's reminiscent of the golden era of OS X. More apps should strive for this standard.
With so many apps introducing either paywalls (requiring either login or circumvention measures) or terrible RSS feeds (with content missing, images missing etc.) I have found it necessary to use a feed reader that you can configure per-feed to open either: - The feed item (read the XML) - The site fulltext - The original site (in case of login required) For me that app is https://www.lireapp.com/