Many people share this same sentiment that RSS feeds should use a push vs pull mechanism, as if it's somehow going to solve all scalability problems. Both approaches run into scaling issues, they're just different.
Sure, pulling may fix the issue of a server working overtime to fulfill floods of excessive, unnecessary requests. But when pushing, you'll now have to have a strategy to scale and manage having so many client connections.
Yeah, relying too much on modified headers from requests to send the appropriate response isn't ideal, because request headers can be incorrect and largely unreliable.
Responding with a Cache-Control header with a max-age seems like a much more superior option for these cases.
Not surprised to see Reeder in there. It’s a great app for Apple users. But that app can bring a website to its knees with how aggressive it is.
I can see in my logs that it constantly makes over ~20 requests to different RSS feeds on my domain, all in the exact same millisecond. Happens multiple times a day. And it appears to rotate IPs. Scary… Tried reaching out to the developer about it twice, but they never responded.
> Not surprised to see Reeder in there. It’s a great app for Apple users.
I agree. Until you find a bug or have a feature request.
> Tried reaching out to the developer about it twice, but they never responded.
And this is exactly why. The developer is the most unresponsive I’ve ever seen. I don’t know why they bother with a “Support / Feedback / Contact” form on the website. And it’s not just you or me, I’ve seen the same commentary from other people.
So if you want to use the app, you better like it as it is. Especially since the developer is working on something else which overlaps in functionality, so I doubt Reeder will get much love going forward. It’s a shame, because it’s the best feed reader I’ve tried, and its small annoyances could be easily solved.
It also queries from external servers? I was under the impression it’s all from the IP of the users themselves. I have Reeder on iOS, and all the feed storage set to iCloud, and afaik whenever I open the app and it’s syncing, I imagine it’s going via whatever network I’m currently connected to.
I don’t see any mention of anything else but Safari on the page.
> According to their PDF, Private Relay also covers apps
Only if the app’s traffic is unencrypted, which is a an important caveat. In practice, I doubt that affects many.
Still, thank you for the correction. I was under the impression there was another small case in addition to Safari but wasn’t finding it so thought I misremembered.
And it is relevant in this case since it is plausible someone added a non-HTTPS feed URL as a feed and never updated it.
Usually these awesome lists are created with enthusiasm, then they get a sponsor or paid link at the top, and sit abandoned and never updated.
You can see the linked list has a link to their android app Plenary at the top, and see the last commit was three years ago. Showing the same pattern.
All the "awesome-xxx" repositories seem to follow this approach, whether by accident or design. I'm sure reviewing and rejecting the expected spammy submissions will take its toll, but it always feels a little more deliberate than that when you see the recurring pattern.
> in a strange way, this almost makes the behavior of hopping onto every new framework rational.
Or maybe not doing that and just using native browser APIs? Many of these frameworks are overkill and having so many "new" ones just makes the situation worse.
Many of them predate those native browser APIs. Pollyfills, the topic at hand, were literally created to add modern APIs to all browsers equally (most notably old Safaris, Internet Explorers, etc.).
Also note, Cloudflare blocks IPs of legitimate automated "good bots" by default, like RSS feed fetchers (1), but allows traffic to some of the most aggressive bots on the web, like Google bot and all sorts of AI bots (2).
OpenRSS is a service that creates RSS feeds using web scraping. Unfortunately, it can't create enclosure links for audio content that's sitting behind Spotify's paywall, so this isn't a podcast feed.
JRE simply isn't a podcast anymore. It's just a Spotify channel.
I'm curious of whether, in the US, Tesla can be sued if their cars hit other drivers who arent using a Tesla. Legally speaking, it seems that the hit driver has legal grounds to sue either Tesla or the driver.
Unfortunately, RSS has become less relevant when compared to other popular platforms made by "Big Tech". But I've been using RSS for over a decade now as a window to everything on the internet and I haven't missed a beat. Subscribed to Ebay listings, Instagram, shopping sites, podcasts, blogs, etc--virtually any internet content I'm interested in on any website, all without any flawed algorithms or ads. Site's like rss.app and openrss.org make RSS pretty easy to use now compared to a decade ago. I'm pretty enthusiastic about the future of RSS.
Sure, pulling may fix the issue of a server working overtime to fulfill floods of excessive, unnecessary requests. But when pushing, you'll now have to have a strategy to scale and manage having so many client connections.