home.social

#webfeeds — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #webfeeds, aggregated by home.social.

  1. Finally got around to add and feeds to my blog.

    I also added a page to make more accessible even for people without backgrounds. Let me know what you think!

    samuelplumppu.se/subscribe

  2. “RSS feels like riding a bike: fast enough to get somewhere, but slow enough that the ride is enjoyable. Which is unlike the stationary bike of social media, where some red-pilled millionaire engineer is cranking a dial to make you pedal faster.” — James Folta

    _____
    #Business #Publishing #Content #Blogs #Websites #SocialMedia #WebFeeds #RSS #Quotes

  3. I accidentally marked everything as read in my reader and I feel both horrified and relieved

  4. Was looking at adding a “Mark All as Read” button or something to Feed Reader—I know, I got the best names—and then I realized I could also go the WP-CLI route.

    And then learned I once created a (completely unrelated) wp reader cleanup command, which permanently deletes read-or-trashed entries not currently in any actual RSS feed.

    https://bddz.be/V6D

  5. Finally followed up on https://jan.boddez.net/notes/129131667e and had /.well-known/recommendations.opml redirect to /wp-json/feed-reader/v1/users/3/opml.

    And, I just learned that WordPress itself already exposes all of its “bookmarks” at /wp-links-opml.php. D’oh!

    Of course, Feed Reader’s OPML endpoint is tied to a specific user (and can be disabled), where WordPress’ built-in OPML endpoint exposes all links for a certain site, and is always public.

    It’s still kind of ironic that I sync, over a HTTP request, WordPress’ links to my feed reader’s OPML, when they happen to live in the exact same database. I should probably look into filtering get_terms and get_bookmarks instead—even though doing so, too, would come with (some) additional overhead—and leave the links database empty.

    https://bddz.be/OBy

  6. Feeds

    I’ve had a /feeds page for a while, but it was only linked to from my About page. I now added a link in the footer as well. While at it, I also added a link to my “article-only feed” to my site’s head, for easier discovery by (certain) feed readers. I have IndieBlocks set […]

    (https://bddz.be/N8p)

  7. Blogrollin’

    I made my blogroll look a tiny bit nicer. I’m planning to still add actual RSS or Atom links, and remove any duplicate entries. (They’re there because I occasionally follow multiple versions of the same feed, for troubleshooting purposes1, or multiple feeds from a single site.) Ages ago, I created a WordPress plugin called Sync […]

    (https://bddz.be/2RG)

  8. I love microformats, but only a handful of people really use h-feed readers. Maybe add some (explicit) reply context to your RSS feeds, too?

    (https://bddz.be/JN1)

  9. Bookmarked inessential: On Mastodon Support in NetNewsWire.

    It still seems like RSS and Mastodon could fit in the same app, though! If I were designing it, I’d start with the social media experience: the single timeline of posts. Very simple sidebar. No article view.

    That’s how Microsub readers have been doing it, mostly, including, back in the day, mine.

    My current feed reader, too, will display short enough “notes” in full, right there in the category or feed “timeline.” There’s no “third” pane articles open up in; clicking an article title simply loads a new web page. (Just like on my blog, in fact!)

    The one thing I do miss (a bit), is the way I currently have things laid out makes it more difficult to also display bookmark, reply or repost URLs/context. (That’s also the [only] reason h-feed isn’t yet supported.)

    https://jan.boddez.net/notes/c53fd47086

  10. Bookmarked Scripting News: Monday, December 11, 2023.

    Do you have a feed-only blog?

    No. Got feed-only posts, though. (I sometimes call them “unlisted,” after Mastodon’s “unlisted” statuses.)

    https://jan.boddez.net/notes/dac1123c47