81–90 of 259 posts
In some ways my twitter feed is almost like RSS, and the people I follow tend to be interesting people who post interesting content or links to other content they've found.
I just wish Mozilla introduce subscribing to RSS as a first class feature in Firefox. If they can introduce and integrate Pocket, I think an open technology like RSS deserves a fair chance. But they'd need to invest a little bit to make it easy to subscribe—similar to following on Twitter/Instagram or Liking pages on Facebook—to receive site updates. Having to find and enter byzantine URLs is not the way to go althou…
I'm considering integrating RSS with Polar: https://getpolarized.io/ Ton on my plate now trying to focus on shipping mobile and a few other features too. I like the idea of Polar having data sources that are high quality and that the user can just easily subscribe to specific PDFs, research, or high quality content feeds. We're also going to add social content discovery which is sort of like a Twitter feed but just p…
It really helps to limit it to a finite amount of content for you to consume as well as making it so you don't have the almost non-existent barrier of instantly being able to react to the news.
I love RSS, and have for years. My first blog post ever was about RSS: http://www.mooreds.com/wordpress/archives/4 . I recently wrote that new developers should use RSS: https://letterstoanewdeveloper.com/2019/03/25/use-an-rss-rea... But reading through the post and the comments here, I'm sensing an omission. What Twitter (and social media in general) provides that RSS doesn't is interaction . I don't login to twitte…
Has anyone tried to build conversation into RSS? An RSS item that is related or responsive to another RSS item? (Or is that what Mastodon is trying to do?)
Let RSS be good at one-way consumption and ActivityPub be good at bi-directional communication.
Earlier quoted context omitted.
What part of my comment made it seem like I need to be educated about what RSS is? I think it would have felt nicer for you to inquire rather than just tell me what RSS is. I’m saying that it’s easily possible to imagine a world where the uses of RSS vary from what they’re used for today — different from the parent commentor.
Your comment didn't educate HN readers sufficiently; I thought it could use a technical backgrounder which could help others imagine the use cases and trade-offs. (I don't understand the Twitter architecture enough to add that for comparison, but perhaps many readers are more familiar with Twitter than RSS due to its popularity.)
Earlier quoted context omitted.
Has anyone tried to build conversation into RSS? An RSS item that is related or responsive to another RSS item? (Or is that what Mastodon is trying to do?)
Mastodon has per-user RSS feeds you can subscribe to but they are non-interactive. For interactive communications ActivityPub is the standard at play and the one to promote. Let RSS be good at one-way consumption and ActivityPub be good at bi-directional communication.
RSS is like articles without comment sections, completely pointless nowadays. If you can't read corrections, conflicting opinions for something, you might just as well go watch TV. The whole point of Twitter is that it's commentary, not a feed of published articles.
RSS is a different network of users, so it really can't be compared to Twitter. But those mega tweet 10 posts in a row threads would be far better served by a classic blog and RSS feed... Rather than 280 word chunks that have to be tracked and edited separately.
Then comes the blogs out there which pretty much use Twitter as a glorified RSS feed. They just post announcements whenever they post a blog post. This is necessary because of the network effect, but I would argue that RSS is a superior technology for this use case.
I think part of the issue with RSS is the real pain of dealing with XML. I'm mildly cheering for something like https://jsonfeed.org - which would be a big step towards making a decentralized system more of a reality.
Doing this in JSON does not suddenly mean you don't need a convention (aka standard) for fields and types. It's data exchange. The reader needs to know what your data means. You still have pubdates, links, titles, descriptions and you still need to label them in a semi-strict way somehow.
All in all, JSON will save you a few bytes but it would just be another standard on the pile, just with no libraries around to write the RSSJSON format.
JSON doesn't fix XML.