Notes tagged “indieweb”

Bookmarked https://wordpress.org/plugins/shortnotes/.

I’ve previously complained about not being able to easily add a class to inline links in Gutenberg. This here code takes a bit of a different approach, and uses span and data elements instead. (Still, I’d love to be able to just use a elements, in a robust manner.)

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.

Updated my “‘IndieWeb’ Custom Post Types” plugin a bit. Integrated a couple things I’d implemented as several must-use plugins at first; it all became a bit much. (Good thing nobody else actually uses it; their feeds would break.)

Heureusement, les formats sont très simples à mettre en place : seulement quelques attributs class à ajouter par-ci par-là.

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.

Some feed readers provide a “live” OPML endpoint. Miniflux does, and Inoreader, I think, allows for it too. In fact, way back when Frank wondered about syncing his reader’s OPML endpoint to his WordPress site’s blogroll, I created a plugin that does exactly that. Which then made me add an OPML endpoint to my Aperture—a Microsub server—install. I mean, doesn’t have to be a separate service. (Aperture, by the way, will also let you store a feed’s format and name.)

Spent an hour or two writing a (basic) WordPress plugin that consumes “audio scrobbles,” like those sent to Last.fm. So rather than (share my data with a third-party service and then) use their API to display a widget or whatever on my blog, my CMS itself is now the “audio scrobbling” endpoint.

If you’ve wondered about an “IndieWeb” site but don’t know where to start: Make what you need.

Wasn’t immediately clear to me that https://github.com/aaronpk/Static-Maps-API-PHP runs just fine on my shared hosting setup as well. (Yay!)

Added a job to my feed aggregator/Microsub server that quickly validates mf2 media, i.e., the URLs that end up in entries’ photo and video arrays, by means of a HEAD request. If the server returns a 404 (or similar), the URL is probably faulty (e.g., the result of a misplaced u-photo tag), and the item removed from the list. No more (well, definitely less) “broken images” below posts!

What if I used Indigenous to send “read” posts to my site and then have my server automatically push these articles—i.e., for URLs—to a specific “feed” in my reader? Same way I treat YouTube vids, kind of. I’d no longer need a separate read-it-later app!

It doesn’t make sense to display someone’s entire blog post underneath yours just because they casually mentioned it.

I often explicitly add things like, “In reply to …,” to notes like this, to offer some context to passers-by and RSS subscribers alike. And then forget to keep these sentences out of my e-content, so that social readers, which already pick up the microformats in them, don’t go and display the same information twice. Details matter.

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.