(Very slowly) resumed work on https://feedreader.site.
(Very slowly) resumed work on https://feedreader.site.
(Very slowly) resumed work on https://feedreader.site.
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. (Heck, I make sure to fetch records—all SELECT
s should be scoped by user_id
—before attempting to update them for this very reason.) But, you never know …
Bookmarked https://nolanlawson.com/2022/11/22/thoughts-on-mastodon/.
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.