121–130 of 134 posts
Not to piss on his/her parade, though: this is a great thing. I am going to tinker with it tonight.
It seems that RSS feed generators are a bit like static site generators: it's often thought to be easier to make your own than to learn to use someone else's. Anyway, here's another self-hosted open source RSS feed generator for arbitrary websites: https://github.com/hueyy/HungryHippo
Thank you, will try it out. Two things I am using: Twitter to RSS: https://github.com/RSS-Bridge/rss-bridge Arbitrary RSS feeds: https://feedity.com
Thanks for using and mentioning Feedity! We've since rebranded to New Sloth: https://newsloth.com , which is now a simple integrated feed builder, reader and clusterer/deduplicator, specially aimed for knowledge workers with hundreds and thousands of feeds to monitor daily. Besides visual selector-based feed generation, our API can auto-magically detect relevant selectors (in most cases) as well.
Earlier quoted context omitted.
> I say just advertise it as “feeds”, not “RSS feeds”. I think that's even worse. For most ordinary people that has a bunch of unintended meanings. "My Facebook has a feed, do you mean subscribing to your site on Facebook? Why do I see a bunch of code when I click the link?"
I think it's the oposite. People continuing calling it RSS is limiting there understanding of this domain. Most people are all about RSS this, reviving that and talk about the specific format, instead of the purpose for which RSS is actually used. This also leads to rather poor solutions and discussions which are just reinventing the old stuff again and again, instead of letting the domain evolve to match modern dema…
Maybe I'm misunderstanding the question. This project is easy to use in all feed readers precisely because it just generates a feed URL that you can subscribe to like any other feed.
On the other hand, maybe you're asking why the feed readers don't have this feature built in. Some of them do! The one I've used for years, Inoreader, has it, although it might be a premium feature.
On the other other hand, sometimes it seems from your comment like your issue is with the very idea of RSS. That a website can publish a feed in a well-defined / open format and that feed can then be consumed by any conforming reader. That's as I see it the beauty of the whole system. I don't need to use the site itself, if it sucks. I can subscribe to anything I like using whatever software I like, rather than relying on a centralized service. What's the alternative, something like Twitter where I subscribe to a bunch of accounts and they push whatever they like into my feed?
It seems that RSS feed generators are a bit like static site generators: it's often thought to be easier to make your own than to learn to use someone else's. Anyway, here's another self-hosted open source RSS feed generator for arbitrary websites: https://github.com/hueyy/HungryHippo
Because the design of RSS/Atom put all of the complexity on the client (polling, state management, etc.) it's literally the same as static site generation. And by "the same", I don't mean "an equivalent but separate problem". I actually think having two separate generators—one outputting HTML, the other RSS—seems a bit wasteful. They're both parsing (presumably) the same content hierarchy and outputting it as SGML/XM…
My friend is working on a quite simple feed generator from any website, social media: https://rss.app . Maybe helpful.
Some feedback for the project, please reveal pricing/limits before signup.
For anyone curious: Free - 2 RSS feeds 24 hour refresh rate $9.99 - 40 RSS feeds 30 min refresh rate $19.99 - 100 RSS feeds 15 min refresh rate
My company uses RSS.app & I find it extremely nice to work with. You don't even have to provide selectors/click on elements for the vast majority of websites, they do that all for you.
We could roll our own solution using any of the above offerings (or something built in house), but it's cheap enough for our usecase that we don't see a point.
So GitHub Actions is essentially a free server to run any background cron jobs I want?
Actions should not be used for: - any other activity unrelated to the production, testing, deployment, or publication of the software project associated with the repository where GitHub Actions are used.
[1] https://docs.github.com/en/github/site-policy/github-terms-f...
Earlier quoted context omitted.
Because the design of RSS/Atom put all of the complexity on the client (polling, state management, etc.) it's literally the same as static site generation. And by "the same", I don't mean "an equivalent but separate problem". I actually think having two separate generators—one outputting HTML, the other RSS—seems a bit wasteful. They're both parsing (presumably) the same content hierarchy and outputting it as SGML/XM…
I disagree. I find the it wasteful, that every source will implement their way of rendering data. If we ignore the ad-problem for a moment, I would love if RSS would be the output of every website and the client then renders HTML to achieve the best UX possible. No broken layouts, no distractions, no dark pattern, just content.