trekz

Not a fan. But why does the article have a reddit quote that is inaccurate? The article says Reddit said the following but nowhere does Reddit say it:

> If you use RSS for feeds outside of a community you moderate, there is no replacement. We know RSS has been a beloved part of the open web for a long time, and we’re grateful to everyone who used it to stay connected to Reddit.

> I don't see how any government or business (especially the former) can justify using X at this point

Open RSS wrote about exactly this a couple weeks ago [1]. Bluesky being publicly readable with RSS is an improvement. But government offices should be publishing on their own RSS feeds, and the platforms should be secondary, not the other way around. The amount of policy that gets announced on social media without even a mention on their own website is bizarre. Why isn't posting their content off platform legally required at this point?

[1] https://openrss.org/blog/government-updates-belong-in-an-ope...

I think he just means that you should add an autodiscovery link tag pointing to your RSS feed URL. Then it will automatically be picked up by RSS readers. See https://www.rssboard.org/rss-autodiscovery.

As unnecessarily snarky as this person is being with you, don't let a HackerNews comment stop you from being an great person.

Right. Consoles shouldn't be doing it either, but here we are...

I think openrss.org has YouTube playlist feeds

It does have an RSS feed at https://explainers.blog/feed.xml

Looks like there's an RSS feed at https://explainers.blog/feed.xml

It looks like it does have a feed: https://explainers.blog/feed.xml

> If you have a large enough codebase, you'll likely find a few cases where things work in TypeScript but its equivalent somehow fails type check in JSDoc.

You keep repeating this throughout the thread. Can you give an example?

Sorry but this is a pointless survey. Not sure how one could determine whether RSS is alive when it already is.

The other problem is that the responses will be skewed depending on where you choose to advertise this survey and who's more passionate about taking it. Posting it here would likely trigger responses from those more inclined to say "rss is not dead", since that's what the overwhelming sentiment is here.

I can only conclude that you likely already know the survey is pointless, but it's being used to advertise for your RSS reader (you plug that in on multiple places on the site). You'd probably be better off just advertising your RSS reader instead.

> I really am mad at Rachel

Don't know what you're so angry with Rachel about. I provide feeds for readers and many of them are way too greedy and frequently do hammer websites, often unneccessarily. Mix in all the rampant AI bots and you got a recipe for an extremely expensive server bill.

Getting angry at someone who's trying to keep their server costs down to provide you something for free is kind of weird.

It can be done but it's not practical because most RSS readers don't even send an Accept header at all, let alone one with an XML mime type.

You can try openrss.org. I believe the Spotify and Apple Music feeds will work for you.

https://openrss.org/feeds/spotify

Open RSS does https://openrss.org/www.bloomberg.com

Has feeds for deep-linked sections too https://openrss.org/www.bloomberg.com/technology

RSS feed: https://hnrss.org/submitted?id=whoishiring

Direct link to the comment on the thread:

https://github.com/mozilla/standards-positions/issues/340#is...

Nice. How are you syncing and deduping the data? The page says it uses an API but doesn't go into detail of which. Is there storage and caching implemented?

Well that sucks. Fortunately, there are apps that still allow you to generate RSS feeds like rss.app. OpenRSS.org may also be of interest, an organization built to fight against companies that get rid of their RSS feeds.

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.

Yeah, there are also third-party services that provide RSS feeds for additional Mastodon data like tags as well. e.g. https://openrss.org/mastodon.social/tags/assange

There's https://github.com/AboutRSS/ALL-about-RSS as well. And https://github.com/voidfiles/awesome-rss. Would be great to see the maintainers of these work together and combine them into one source.

> 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.

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).

(1) https://openrss.org/issue/144

(2) https://radar.cloudflare.com/traffic/verified-bots - GoogleBot, GPTBot, and AmazonBot are some of the first ones listed.

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.

You can try openrss by navigating to the user profile and adding openrss.org in front

https://openrss.org/www.youtube.com/@MandaloreGaming/videos

Probably needs something like how openrss.org does it. Shows a UX friendly view for RSS but gets picked up by RSS readers as well.