News for hackers. Stuff that matters.
Re:Winds 2.0: It’s Time to Revive RSS by skrause on Tuesday May 22, 2018 @06:06PM (#17129795)
> I love using RSS to follow the programming and tech news I care about. Unfortunately, the number of sites supporting RSS has been in rapid decline over the last few years. The reader ecosystem is slowly degrading as well.

After that introduction I was hoping Winds would be some kind of proxy that creates an RSS for sites that don't have one. But well, it's just another RSS reader. Those have actually never gone way, I'm using Inoreader every day.

Re:Winds 2.0: It’s Time to Revive RSS by nreece on Tuesday May 22, 2018 @08:57PM (#17130739)
* Shameless plug *: Our little startup, Feedity - https://feedity.com, helps create custom RSS feeds for any webpage, via an online feed builder and REST API.

Custom feeds can even be created for dynamic content, utilizing Chrome for full-rendering, and many other tweaks & techniques under the hood for seamless & scalable indexing.

Re:Winds 2.0: It’s Time to Revive RSS by Bromskloss on Tuesday May 22, 2018 @09:23PM (#17130857)
For those wondering: The least expensive plan is 9 USD per month for 20 feeds, 10 simultaneous articles per feed, and updates every 6 hours.
Re:Winds 2.0: It’s Time to Revive RSS by tschellenbach on Tuesday May 22, 2018 @09:08PM (#17130798)
That's awesome, I'll start making a little list of tools that help you do more with RSS
Re:Winds 2.0: It’s Time to Revive RSS by saamm on Friday May 25, 2018 @03:51PM (#17157275)
You may also be interested in Kill the Newsletter:

https://www.kill-the-newsletter.com/

(I think a fellow HN user made it? Can't remember)

Re:Winds 2.0: It’s Time to Revive RSS by O_H_E on Tuesday May 22, 2018 @09:19PM (#17130846)
Really Nice
Re:Winds 2.0: It’s Time to Revive RSS by jessriedel on Tuesday May 22, 2018 @06:32PM (#17129964)
For reasons I don't understand, it remains incredibly difficult to scrape a well-organized blog and turn it into something I can consume like RSS or a kindle book.

Note that many/most WordPress RSS feeds aren't that useful because they only show a snippet rather than the entire post. This dreary state of affairs is due in part to the fact that "checking" an RSS just means downloading the entire file containing all posts the author would like to make public, regardless of how many are new to the reader. This insanely unnecessary bandwidth usage penalizes sites that have long (>10) feeds with complete posts. (The single RSS file on my blog takes up the majority of my bandwidth costs.)

RSS needs to be replaced, not revived.

Re:Winds 2.0: It’s Time to Revive RSS by gkya on Tuesday May 22, 2018 @07:09PM (#17130230)
For your RSS issue, you can safely truncate your RSS feed to the latest N articles, where N is a random reasonable number you choose (10 is good, because it's so decimal). RSS reader software will know how to deal with it.

WRT scraping, it is getting harder because funny websites w/ no static content where everything is generated via Angular or Perpendicular or sth. are really hard to deal with. Recently my uni switched from an army of Wordpress websites to an homegrown AJAX-MVC-Reactive abomination where the links are reimplemented via some funny black magic where the actual link items (which are not anchors btw) don't have encoded in them the link targets, but only an onclick event that knows somehow where to go. And because they just killed all the RSS feeds, I wrote up sth. to revive them for me via phantomjs, but could not figure how to find the link targets, I cannot link the RSS items to anywhere but the main announcements page, and I can't add any description from the link target.

RSS should be kept, those who don't know the job they are doing should be replaced.

Re:Winds 2.0: It’s Time to Revive RSS by jessriedel on Tuesday May 22, 2018 @08:14PM (#17130547)
> For your RSS issue, you can safely truncate your RSS feed to the latest N articles, where N is a random reasonable number you choose (10 is good, because it's so decimal). RSS reader software will know how to deal with it.

But people who don't use the right aggregators will not be able to read past 10 posts. And if everyone was using aggregators, I wouldn't have such a high bandwidth bill.

> WRT scraping, it is getting harder because funny websites w/ no static content.

But sites that can have an RSS feed necessarily need to deliver their content in a static form. What surprises me is that we don't have a tool for even those cases.

Re:Winds 2.0: It’s Time to Revive RSS by gkya on Tuesday May 22, 2018 @08:59PM (#17130755)
> But people who don't use the right aggregators will not be able to read past 10 posts.

I do not think such aggregators exist, and you can just ignore people using software that do not comply to widespread conventions.

> And if everyone was using aggregators, I wouldn't have such a high bandwidth bill.

I don't understand this sentence. All RSS client software is called aggregator.

> But sites that can have an RSS feed necessarily need to deliver their content in a static form.

Not really. Many websites which are essentially blogs are transforming themselves into single-page web apps. My uni's websites included. Some do it for the $$$, some for reasons that I can not know (jumping the bandwagons with minds toggled off).

You can just set your blog software to truncate your feeds to a reasonable number w/o any worries. And I suggest you look at your logs, because some silly bots might be consuming your bandwith along with your normal traffic; there are some that like RSS feeds.

Re:Winds 2.0: It’s Time to Revive RSS by jessriedel on Wednesday May 23, 2018 @01:41AM (#17131682)
> I don't understand this sentence. All RSS client software is called aggregator

I'm trying to distinguish between (1) people using software the directly downloads the RSS feed from my website to their device and (2) people who use services that download the RSS feed to a server which can then serve a cached copy of the posts to many users. If everyone used (2), then I would only have my RSS file downloaded as many times as there are separate services, which is not very many. So apparently many people are doing (1), and if my feed is short then they are limited in the blog history they can read to how long they've personally been subscribed (or less, if they need to clear their device and can't re-download my old posts).

> Not really. Many websites which are essentially blogs are transforming themselves into single-page web apps

That's why I specified "But sites that can have an RSS feed...". If you have an RSS feed with useful posts in the feed, then you must be delivering static pages. (If you're just delivering snippets with links to a dynamic page, then there is no way for any service to cache the page either.) So my question is: why isn't there software to scrape webpages of blogs that offer an RSS feed with complete posts? This would enable me to comveneiently read post history going back more than 10 posts.

> And I suggest you look at your logs, because some silly bots might be consuming your bandwith along with your normal traffic; there are some that like RSS feeds.

All the bots put together make up 27% of my bandwidth. It's a lot, but it's not the root cause.

Re:Winds 2.0: It’s Time to Revive RSS by gkya on Wednesday May 23, 2018 @05:09AM (#17132491)
> So apparently many people are doing (1), and if my feed is short then they are limited in the blog history they can read to how long they've personally been subscribed (or less, if they need to clear their device and can't re-download my old posts).

RSS is a means for people to follow new posts from you, in order to read new posts they are supposed to come to your blog and use your archives.

Re:Winds 2.0: It’s Time to Revive RSS by jessriedel on Wednesday May 23, 2018 @04:04PM (#17137699)
The whole point of this subthread is about reading archives offline, and how RSS can't manage this. From my first comment:

> it remains incredibly difficult to scrape a well-organized blog and turn it into something I can consume like RSS or a kindle book.

> Note that many/most WordPress RSS feeds aren't that useful because...

Re:Winds 2.0: It’s Time to Revive RSS by gkya on Wednesday May 23, 2018 @06:00PM (#17138757)
> The whole point of this subthread is about reading archives offline, and how RSS can't manage this. From my first comment:

I don't think so, but maybe I missed. It is not the purpose of RSS anyways, though. RSS is for me to know when you post something new.

Re:Winds 2.0: It’s Time to Revive RSS by mtremsal on Tuesday May 22, 2018 @10:07PM (#17131012)
FWIW, I had a similar issue recently: if you cannot find the link targets, you can still simulate a click on the element using phantomjs.
Re:Winds 2.0: It’s Time to Revive RSS by gkya on Wednesday May 23, 2018 @05:13AM (#17132505)
Yeah, but for my case it means waiting 10 seconds per link, and another 10 seconds when returning to the initial page, which has some 20 entries, and there are more than ten such pages that I need to scrape, so I passed on that...
Re:Winds 2.0: It’s Time to Revive RSS by ChristianBundy on Tuesday May 22, 2018 @08:23PM (#17130582)
> ... where N is an arbitrary number you choose (12 is good, because https://dozenal.org).

FTFY ;)

Re:Winds 2.0: It’s Time to Revive RSS by progval on Wednesday May 23, 2018 @01:59AM (#17131730)
> because http://dozenal.org

FTFY

Re:Winds 2.0: It’s Time to Revive RSS by gkya on Tuesday May 22, 2018 @09:00PM (#17130761)
Take a nice little joke please, downvoters, will ya?
Re:Winds 2.0: It’s Time to Revive RSS by bArray on Tuesday May 22, 2018 @07:08PM (#17130224)
>This dreary state of affairs is due in part to the fact that "checking" an RSS just means downloading the entire file containing all posts the author would like to make public, regardless of how many are new to the reader. This insanely unnecessary bandwidth usage penalizes sites that have long (>10) feeds with complete posts. (The single RSS file on my blog takes up the majority of my bandwidth costs.)

Still, exceptionally low cost compared to running pretty much any website's massive CSS and JS files. A single image in most cases will take more than the entire RSS feed before compression.

That said, I would like to see a new standard (a new one would be needed [1]) that only gets the difference from what you last read - I think that would really take RSS feeds to new places of usefulness. There's no reason why you couldn't send the server an ID (not timestamp to avoid issues with timezones, clock stretching, forward/backward time setting, etc) of the last request and have it send back everything since (within reason).

[1] https://www.w3schools.com/XML/xml_rss.asp

Re:Winds 2.0: It’s Time to Revive RSS by elFarto on Wednesday May 23, 2018 @02:38AM (#17131837)
You should already be able to implement this using the If-Modified-Since HTTP header. The server only needs to send you back articles in the RSS feed that have been added after that date. The If-Modified-Since value is meant to come from the previous responses Last-Modified (not a timestamp you make up), so that side-steps timezone issues.
Re:Winds 2.0: It’s Time to Revive RSS by bArray on Wednesday May 23, 2018 @04:23AM (#17132270)
I think that still requires a change to both the server and the reader - although at least not a new standard.
Re:Winds 2.0: It’s Time to Revive RSS by jessriedel on Tuesday May 22, 2018 @08:21PM (#17130576)
> Still, exceptionally low cost compared to running pretty much any website's massive CSS and JS files.

My blog has both RSS and browser readers, but the bandwidth is dominated by the RSS feed. Since the RSS file has no images (just HTML pointing to the images), I think it's more likely that for my Wordpress blog the CSS/JS overhead is just not that much (as opposed to the alternative hypothesis that I have many many times more RSS readers who never end up downloading the images).

Re:Winds 2.0: It’s Time to Revive RSS by bArray on Wednesday May 23, 2018 @04:35AM (#17132317)
>the bandwidth is dominated by the RSS feed

Exceptionally low cost per hit, as opposed to overall bandwidth. Overall bandwidth will probably fair off worse as you say due to the polling nature of RSS. I think in general RSS readers could do a better job of fetching heads and checking whether or not there is a change worth fetching, that would save a tonne of bandwidth.

Also in general, I would be tempted to make an RSS feed more minimalist in terms of content and markup. It should just be a short `<description>` and a link to the main article (which would still allow you to potentially monetize your content or gauge interest more accurately).

>I think it's more likely that for my Wordpress blog the CSS/JS overhead is just not that much

Also, bandwidth is just one resource - potentially each call to a page is a database read, whereas your RSS feed should be static (not sure about the WordPress implementation, but I would hope for static caching with something that doesn't change for long periods of time). I've seen WordPress database lockups with modest amounts of traffic (again, most of the time this could have been easily statically cached - but doesn't appear to be by default).

Re:Winds 2.0: It’s Time to Revive RSS by jessriedel on Wednesday May 23, 2018 @04:07PM (#17137722)
>> the bandwidth is dominated by the RSS feed

> Exceptionally low cost per hit, as opposed to overall bandwidth.

I don't understand. I'm telling you that my RSS file literally dominates my bandwidth usage in GB.

> I think in general RSS readers could do a better job of fetching heads and checking whether or not there is a change worth fetching, that would save a tonne of bandwidth.

Yah! Agreed.

> It should just be a short `<description>` and a link to the main article (which would still allow you to potentially monetize your content or gauge interest more accurately).

No, I want people to be able to read it offline. I'm not trying to monetize anything.

> Also, bandwidth is just one resource - potentially each call to a page is a database read

I have a simple website. The bandwidth is the dominant cost.

Re:Winds 2.0: It’s Time to Revive RSS by bArray on Thursday May 24, 2018 @12:56AM (#17141201)
>> I think in general RSS readers could do a better job of fetching heads and checking whether or not there is a change worth fetching, that would save a tonne of bandwidth.

> Yah! Agreed.

You could also reduce the number of `<item>`s you keep in rotation to a more manageable number.

>> It should just be a short `<description>` and a link to the main article (which would still allow you to potentially monetize your content or gauge interest more accurately).

> No, I want people to be able to read it offline. I'm not trying to monetize anything.

It should still be much more lightweight than it's HTML counterpart. Should be almost nothing to it, next to no markup, no styling, no scripts and a highly compressible piece of data.

I don't understand how you're racking up massive bandwidth. Can you put some numbers to it:

* Bandwidth usage for RSS

* Bandwidth usage for webpage

* Hits to RSS

* Hits to webpage

* Links for both

Re:Winds 2.0: It’s Time to Revive RSS by prepend on Tuesday May 22, 2018 @08:37PM (#17130641)
Or you have way more users via rss than through their browser. This could be a good thing as it results in less bandwidth than if they all hit you directly through browser.
Re:Winds 2.0: It’s Time to Revive RSS by jessriedel on Wednesday May 23, 2018 @01:43AM (#17131685)
My parenthetical comment raised this hypothesis and rejected it with a reason. So you should address that reason if you want to disagree.
Re:Winds 2.0: It’s Time to Revive RSS by abecedarius on Tuesday May 22, 2018 @07:27PM (#17130318)
That’d impose a cost on the server, remembering an ID map. Instead make the client send back a value given by the server last time.
Re:Winds 2.0: It’s Time to Revive RSS by jerf on Tuesday May 22, 2018 @10:07PM (#17131009)
That's something both RSS consumers and produces should already support, but don't always, called an E-Tag, a standard part of the HTTP standard. However, the E-Tag is all-or-nothing; either it matches, and the entire request is essentially aborted, or it doesn't match, and the entire file is served up.

Passing "the ID of the last piece of content I saw" would allow the server to return just the updated stuff, or abort early like an E-Tag. However, counterintuitively, as is often the way in computer science, I'm not sure it would be that big a win to be able to return partial content. The vast bulk of the win on most blogs will just be the ability to abort at all, provided just fine by E-Tags.

I would say that if your site is getting hammered by HTTP requests for your RSS, do double-check that you've got E-Tags set up and working correctly. It is in the best interests of the big scrapers to support that properly, as they are paying for that bandwidth too. RSS aggregators don't have to get too large before this becomes a top-priority feature request. Unless the feed is literally changing on roughly the same frequency as it is scanned, it shouldn't be the dominant factor in your bandwidth bill.

Re:Winds 2.0: It’s Time to Revive RSS by cpeterso on Wednesday May 23, 2018 @02:45AM (#17131860)
Couldn't the feed server use the Last-Modified HTTP header to note the most recent feed item sent to the client?
Re:Winds 2.0: It’s Time to Revive RSS by jerf on Wednesday May 23, 2018 @10:29AM (#17134445)
It's at least a 95% solution; I don't know about 100%, in the face of the ability to delete items and modify timestamps after they've been posted.
Re:Winds 2.0: It’s Time to Revive RSS by Izkata on Tuesday May 22, 2018 @09:57PM (#17130978)
I think that's what they meant by "an ID [...] of the last request"
Re:Winds 2.0: It’s Time to Revive RSS by prepend on Tuesday May 22, 2018 @08:36PM (#17130633)
“This insanely unnecessary bandwidth usage penalizes sites that have long (>10) feeds with complete posts.”

Since rss is text only the sizes are very small and compress well. Considering the average web page is 3M[0], pulling down 10-100k of every post ever doesn’t matter. And http takes care of not pulling the same file over and over.

It’s certainly a downside, but completely useable as is, and better than any viable alternative.

As far as standards go, I prefer simple, static file, over something requiring dynamic response.

There’s also nothing stopping the site from limiting the RSS feed to only 5 posts with a link for full.

[0] https://speedcurve.com/blog/web-performance-page-bloat/

Re:Winds 2.0: It’s Time to Revive RSS by jessriedel on Wednesday May 23, 2018 @04:10PM (#17137752)
> Since rss is text only the sizes are very small and compress well. Considering the average web page is 3M[0], pulling down 10-100k of every post ever doesn’t matter.

My web pages are 100k and my RSS feed is 500k.

> It’s certainly a downside, but completely useable as is, and better than any viable alternative.

It doesn't fulfill the need I originally mentioned: making blog archives readable offline.

> As far as standards go, I prefer simple, static file, over something requiring dynamic response.

I agree static is better, but a dynamic response isn't necessary. You could just have a static file that listed all the blog posts, with a link to another static file for each post. This avoids having the user download 10 blog posts each time they want to poll if something new has happened.

Re:Winds 2.0: It’s Time to Revive RSS by viraptor on Tuesday May 22, 2018 @11:09PM (#17131235)
Even better: instead of serving the generated for, point your RSS subdomain to your favourite CDN and only update your files when the site changes. That's likely to save you some money.
Re:Winds 2.0: It’s Time to Revive RSS by iamdeedubs on Tuesday May 22, 2018 @08:45PM (#17130672)
They only show a snippet because they can't sell your eyeballs via the RSS feed. They need just need to drsw you to click onto their full site to blast you with ads.
Re:Winds 2.0: It’s Time to Revive RSS by Tehdasi on Tuesday May 22, 2018 @06:46PM (#17130065)
Sortof, if you are reading via a web based reader, the service itself only reads the feed once, and the users view the cached version.
Re:Winds 2.0: It’s Time to Revive RSS by jessriedel on Tuesday May 22, 2018 @06:53PM (#17130118)
You mean the fact that aggregators like The Old Reader just download the RSS file from the website periodically, and then serve up cached copies to their many user? True, although this is another way of saying that some of the value added by aggregators only exists by virtue of the terrible design of RSS.
Re:Winds 2.0: It’s Time to Revive RSS by JetSpiegel on Tuesday May 22, 2018 @07:43PM (#17130412)
It might be construed as a feature, since a blog can consist of simply static files, no need for running any code relating to RSS.
Re:Winds 2.0: It’s Time to Revive RSS by jessriedel on Tuesday May 22, 2018 @08:17PM (#17130555)
It doesn't need code. Just a static text file with a list of publication dates and URLs, each of which points to static HTML file for each publicly available posts. Then each user could check the list and download only what's new, without needing an aggregator. Users would never need to download the same content twice.
Re:Winds 2.0: It’s Time to Revive RSS by jerf on Tuesday May 22, 2018 @10:09PM (#17131019)
You can pretty much do that with RSS, if you want. Slightly decorated with some XML stuff but that'll pretty much gzip right away. Statically, if you use the right web servers and magic invocations the web server may specify.

You'll find your feed readers aren't particularly impressed, though.

Re:Winds 2.0: It’s Time to Revive RSS by jessriedel on Wednesday May 23, 2018 @01:46AM (#17131695)
This won't work because my users don't have software to automatically download the new posts, curate them, and save them for offline reading (in contrast to having the posts directly in the RSS file, for which all that does happen). That would require...a new standard, i.e., a replacement for RSS.
Re:Winds 2.0: It’s Time to Revive RSS by jerf on Wednesday May 23, 2018 @10:26AM (#17134426)
No, it would require a new type of consumer. RSS can carry a list of URLs just fine, as a degenerate case of RSS. RSS does not itself mandate that the content of the RSS must be displayed in "some sort of feed reader".

The good news is that means you don't have to wait. You can write that now. It will work on existing RSS feeds, just not quite as optimally for your proposed use case as you might personally like, but it will still work. It will work even better on yours, which will also work in conventional RSS readers.

Now, you might have problems getting "the real page content" from your URLs, but that's a separate problem. (History strongly suggests the large-scale content producers would actively fight you if you try, because you'll probably be trying to strip their ad revenue either deliberately or accidentally as part of what you'd be doing. Which is, after all, the reason why RSS is already not terribly favored by that crowd and why they want you in closed gardens of their own devising... unfortunately getting around this problem is a great deal more difficult than hypothesizing that some sort of new standard could somehow deal with it....)

Re:Winds 2.0: It’s Time to Revive RSS by jessriedel on Wednesday May 23, 2018 @04:23PM (#17137882)
I'm using "RSS" to refer to the standard practice people actually do. It's not very important that some organization somewhere defined an official RSS standard which in principle is flexible but which in practice is never used other than in a very specific way. (Without an agreement on how to use it more generally, no one can build an offline blog archive reader, and the fact that RSS could in principle be the base is irrelevant.)

If you want to play semantics, I'm fine with rephrasing my complaint as: "We need to build on the flexible super official RSS standard -- which is little more than an XML file -- and actually agree on a way of delivering blog archives for offline reading. RSS in practice does not currently achieve this very simple goal." This is just different words to describe the same thing.

> You can write that now. It will work on existing RSS feeds, just not quite as optimally for your proposed use case as you might personally like, but it will still work.

Huh? Other website owners who would like me to be able to read their archives can modify their RSS file, but we have no agreement on how to do that in a standard way. Likewise, I could modify my RSS file, but since there isn't a standard my readers won't have software to take advantage of it.

> (History strongly suggests the large-scale content producers would actively fight you if you try,...unfortunately getting around this problem is a great deal more difficult than hypothesizing that some sort of new standard could somehow deal with it....)

The blogs I want to read offline do not have ads and do not care about this. I just want a solution that works for this simple problem, not a way to take content from people who don't want to give it to me without attaching ads.

Re:Winds 2.0: It’s Time to Revive RSS by 23443463455 on Tuesday May 22, 2018 @06:44PM (#17130048)
Is the problem really that RSS needs replacement, or can it simply be improved. I think there is quite a bit of room for extension to address some of the concerns that are expressed here too, including accurate meta tagging for educational resource discovery purposes.
Re:Winds 2.0: It’s Time to Revive RSS by klez on Wednesday May 23, 2018 @03:01AM (#17131910)
I'm under the impression that pulling extensions on RSS will land us in the XMPP situation, where you have servers and clients speaking different languages.

On the other hand, if you want to say that your client supports this supposed RSS-ng standard they need to support those new features because they're part of the protocol.

This is to say, I don't like protocol extensions, but that's just me :)

Re:Winds 2.0: It’s Time to Revive RSS by zbentley on Tuesday May 22, 2018 @08:16PM (#17130554)
That's because rendering JS/CSS/whatever has become the norm. It has become the norm for two reasons: tooling for building "static" sites with this technology has gotten very popular and well-done, and sites with a vested (advertising/lockin) interest in showing their content "their way" have jumped on board.
Re:Winds 2.0: It’s Time to Revive RSS by eli on Tuesday May 22, 2018 @06:37PM (#17130002)
Re:Winds 2.0: It’s Time to Revive RSS by onli on Tuesday May 22, 2018 @06:45PM (#17130058)
If I may add mine: https://www.pipes.digital/. It allows creating feeds for sites if the site is structured enough, and the feed can then manipulated with other blocks, similar to how Yahoo Pipes worked.
Re:Winds 2.0: It’s Time to Revive RSS by rolandog on Tuesday May 22, 2018 @07:09PM (#17130233)
I miss Yahoo Pipes so much! Thanks for creating this service, I'll try it out soon and leave some feedback here!
Re:Winds 2.0: It’s Time to Revive RSS by onli on Wednesday May 23, 2018 @03:00AM (#17131906)
Feedback is always welcome (and subscribers even more ;) ), you can also send me a mail (in profile) or follow the way described in the docs to reach me (https://www.pipes.digital/docs#support).
Re:Winds 2.0: It’s Time to Revive RSS by m-localhost on Wednesday May 23, 2018 @02:34AM (#17131822)
One of the few Yahoo products that were great. I think Yahoo was pretty good in providing developer tools and apis.
Re:Winds 2.0: It’s Time to Revive RSS by superwayne on Wednesday May 23, 2018 @05:54AM (#17132727)
If you don't mind writing a bit of Python glue code, you can also use https://github.com/nblock/feeds (I'm one of the authors). It uses Scrapy under the hood and is supposed to run as a cronjob. It will create full text Atom feeds of whatever data you will feed to it. Spiders (plugins) are usually quite small, especially when there is no login (paywall) involved: https://github.com/nblock/feeds/tree/master/feeds/spiders
Re:Winds 2.0: It’s Time to Revive RSS by _b8r0 on Tuesday May 22, 2018 @07:02PM (#17130182)
Some other people had mentioned some services available but I'd like to add self-hosted options https://github.com/RSS-Bridge/rss-bridge and https://github.com/taroved/pol into the mix.

I use rss-bridge in combination with rss2email to follow instagram feeds after leaving instagram.

Re:Winds 2.0: It’s Time to Revive RSS by m-localhost on Wednesday May 23, 2018 @02:35AM (#17131825)
Here is another feed creator service, for websites that don't offer a newsfeed: http://createfeed.wprssaggregator.com/
Re:Winds 2.0: It’s Time to Revive RSS by stevewillows on Tuesday May 22, 2018 @07:18PM (#17130276)
I use http://feed43.com for this. Its nice because you can create your own standard for the output.
Re:Winds 2.0: It’s Time to Revive RSS by theDoug on Tuesday May 22, 2018 @06:37PM (#17130003)
I was hoping for the same. Still see no answer on how this does anything to support their claim that "It’s time to turn the tide"
Re:Winds 2.0: It’s Time to Revive RSS by simplify on Tuesday May 22, 2018 @06:47PM (#17130069)
Marketing is a powerful force. It's true that RSS has existed for many years, but also consider how many people have grown up without learning about it.
Re:Winds 2.0: It’s Time to Revive RSS by tunesmith on Tuesday May 22, 2018 @06:22PM (#17129909)
A site should still be able to choose to not produce RSS if they don't want. Encouraging RSS is different than forcing RSS feeds on sites that don't want them.
Re:Winds 2.0: It’s Time to Revive RSS by catach on Tuesday May 22, 2018 @06:31PM (#17129959)
Site creators have the freedom to produce what they want, and users likewise have the freedom to consume how they want.
Re:Winds 2.0: It’s Time to Revive RSS by franzpeterstein on Tuesday May 22, 2018 @07:46PM (#17130432)
I think so too. I use RSS as a very minimalist blog and have had good experiences with it so far. It's hard to monetize the format, but it really draws a lot of people to my side.
Re:Winds 2.0: It’s Time to Revive RSS by s73v3r_ on Tuesday May 22, 2018 @07:02PM (#17130181)
Do they? I'm fairly certain they don't. Otherwise everyone would just be torrenting and stripping commercials.
Re:Winds 2.0: It’s Time to Revive RSS by evrydayhustling on Tuesday May 22, 2018 @07:48PM (#17130445)
Torrenting is illegal because you (generally) weren't authorized to make a copy. Stripping commercials isn't because you're removing something, or changing the way you read it. There might be some legal case if you have to make another copy of media in order to alter your consumption, but thank God I'm aware of no case attempting to control your personal use of media.

(DMCA doesn't count, it's about circumventing things that prevent you from copying, not change your consumption.)

Re:Winds 2.0: It’s Time to Revive RSS by Izkata on Tuesday May 22, 2018 @10:26PM (#17131076)
Just to this point, an example: My parents' VCR had a built-in feature that would automatically fast-forward through commercials when playing back something that it recorded.
Re:Winds 2.0: It’s Time to Revive RSS by catach on Tuesday May 22, 2018 @07:08PM (#17130222)
Sure, as a broad absolutist statement there's plenty of practical, legal, metaphysical holes you could poke in it.

Not aware of any anti-user-made RSS laws, though.