@RecursiveElegance Sites covered by #Cloudflare captcha can also block non-web clients like #RSS readers, as I discovered with Medium (I was trying to bypass its interface nagging & nonsense, so I figured I'd check its support for #webfeeds).
RSS readers do not typically implement interactive web display, so even if they had a #Javascript interpreter, it is impossible to answer the captcha query. This breaks the endpoint entirely.
#cloudflare #webfeeds #javascript #rss
https://fstop.cloud is able to fetch full articles even for summary-only feeds. It looks for either the `main` element or the first `article` on the page, but you can also hand it a (feed-specific) XPath selector indicating what you want to keep.
Either way, maybe I should give https://github.com/fivefilters/readability.php a try.
↬ Stefan Zweifel
@dekkzz76 @sqrtminusone @mdotblind Well, #RSS refers to a specific #webfeed format, but #Atom is also another one.
Both have the general benefits of #webfeeds over other ways of following up on online content. There could be other formats developed for it in the future, although they currently seem to do the job just fine.
@dekkzz76 @sqrtminusone @mdotblind Agreed. I wouldn't say that's a problem with #webfeeds, rather that's a feature.
No unnecessary spam, no tracking, and all the prioritization, filtering & sorting is dealt-with in the user-agent.
@mdotblind There are some issues with #RSS specifically... https://nullprogram.com/blog/2013/09/23/
But in any case yes, #webfeeds are great.
There are some nice integrations for #Youtube using #Elfeed https://github.com/karthink/elfeed-tube
#rss #webfeeds #youtube #elfeed #emacs #feedreader
Submitted https://github.com/janboddez/feed-reader for inclusion in the WP.org plugin directory. See what that brings. Thing I’m most “worried” about is that somehow the “image proxy” is frowned upon, or the way I set up the various “admin routes.” Or a glaring security issue. I mean, I’m fairly sure I sanitize all imported HTML and ensure that anything that’s ever touched does in fact belong to the logged-in user. But, you never know …
#wordpress #webfeeds #rss #plugins
Something else: I just saw someone include an entire HTML document, `head`, `script`s, the whole shebang, into their RSS items’ `description`s.
SSG, of course.
Look, I know most SSGs let you loop through a list of all posts, either midway the whole generation process, or after.
**Do not** just dump **all** of these into a feed and be done with it.
And **subscribe to your own feed(s)**, so as to quickly discover and fix these mistakes.
> I like my RSS feed. The signal-to-noise ratio is high, the timeline is slow, and there are no notifications. That’s about the right speed of social media for me.
My feed reader seems to strip `alt` attributes off `u-photo`s. My RSS feed has the `alt` text set to either the post title, or a truncated copy of the post content. That’s no good.
Feed reader now shows avatars—well, favicons—for non-microformats feeds as well.
So, after you’ve carefully thought about the different feeds and feed formats you’re going to offer potential subscribers, please help aggregators find them by adding a `link rel=alternate` tag to your site’s `head`.
Also, if you’re a developer who spends a lot of time curating their carefully crafted personal site, please, please advertise your feed by having, e.g., a `link rel="alternate" type="application/rss+xml"` tag in your `head`.
Got reminded of my own /feeds page today. This site only offers 3 “true” RSS feeds: one for regular blog posts (articles), one for shorter status updates (notes), and one for both. That said: most of this site’s sections double as a h-feed; you _can_ even follow search results! Moreover, both articles and notes are marked up using microformats, for social readers to do their thing.