As long as the service provider runs an instance in their infrastructure and allows everybody to read.
That said, RSS seems way simpler.
As long as the service provider runs an instance in their infrastructure and allows everybody to read.
That said, RSS seems way simpler.
A mastodon account provides an rss feed by default so both solutions coexist without duplicating the work.
RSS and IRC need new apps and new means to self host. To do that, there probably has to be new DNS.
We need to stop focusing on the specific protocol when it's not relevant and focus more on the patterns. Wanting RSS, specifically, made sense back when everyone had an RSS reader, the same way it makes sense to have an HTML website today because everyone has a web browser. But since very few people have RSS readers now, there's infinite flexibility in the format you use to provide your feed. The most useful is probably a phone app that vibrates your phone with a notification when your train is delayed. RSS can be provided as an option.
I don't disagree and I'm not a mastodon user but, as far as I know, if you local gov hosted an instance and your state gov did too, you could, essentially, join both and see them together?
RSS aggregation seems like the solution to me but I think we've got to admit defeat on that one because it's been around forever and people don't use it.
Pretty much every podcast in the world and all of their listeners are using RSS. WordPress powers something like 30% of the Web, and most of the operators behind those sites are publishing RSS whether they know it or not.
I thought I was more clear than I was being about rss in the context of the conversation about text based news.
How many people consuming text via rss the same way people consume audio via podcasts?
We're talking about text here. We all know how this sentence ends, "You should start a ..." and it isn't rss feed. Everyone used to have a blog and nobody really cared. Now everyone has a podcast and (more) people do. People don't know what an rss feed is.
> We all know how this sentence ends, "You should start a ..." and it isn't rss feed.
I don't know what this means. I'm guessing the correct answer is supposed to be "podcast"? Even so, weird false dichotomy.
That looking at tweets and listening to podcasts is more popular than reading long-form blog posts via RSS has a lot more to do with people's revealed preference for looking at tweets and listening to podcasts versus reading long-form blogs than it has to do with RSS.
(The actual context was delivery of notices by public services through non-Twitter feeds, anyway. Not blogging.)
> People don't know what an rss feed is.
I don't know why you think this is relevant here. It seems that when you're referring to using "RSS", what you mean is for people to care about RSS—in the way that Gemini, Secure Scuttlebutt, etc. have always been about caring about (and almost exclusively using them to talk about) Gemini, Secure Scuttlebutt, etc. than they ever were actually expected to be used organically and non-self-referentially.
The fact is that people (already/still) use RSS today. It hasn't been defeated. And Twitter could turn into an RSS-based feed reader tomorrow that works basically the same as it works today, and then suddenly everyone would be using RSS but no one would drop out because of it. Because people don't know (read: care) what an RSS feed is.
You can follow them both from your own mastodon account on a third server.
It's a technically bad solution though, because mastodon is push. The government server has to maintain a list of everyone who's subscribed and make an HTTP request to all of those random domains, and have some timeout and removal policy because sites die all the time. Pull-based, like RSS, is way cleaner.
Yes, you can subscribe from whatever instance you want.
(I'm not a mastodon user either. But I've read the docs.)