Re: Mastodon is the new Google Reader

💬 Re: Mastodon is the new Google Reader

Why use ActivityPub when RSS still exists, and when IndieWeb adds social functionality to traditional, non-ActivityPub blogging?

Even at its best, ActivityPub is a very difficult standard to implement, with a lot of really hairy edge conditions and an at-best-mediocre experience for things that don’t fit neatly into its model, and Mastodon’s particular implementation of ActivityPub isn’t, y'know, great. (And I’ve written a bunch more about my thoughts on this as well.)

Basically I’d love to see more people support IndieWeb, using RSS/Atom and ideally also h-feed as the syndication formats, and to that end, I’d say that micro.blog is a better choice of “new Google Reader.”

Re: Announcing IndieWeb Utils v0.4.0 (with reflections on the library)

💬 Re: Announcing IndieWeb Utils v0.4.0 (with reflections on the library)

Indieweb Utils looks pretty neat and there’s a few projects I’ve had on the backburner which would benefit from this.

I’d also be pretty tempted to look into moving Pushl over to it, just to cut down on my own code maintenance requirements, except it looks like it doesn’t have any support for asyncio, which is less-than-optimal for an I/O-bound tool which sends a bunch of bulk updates. Is there any interest in adding asyncio support?

Re: Plurality and the IndieWeb

💬 Re: Plurality and the IndieWeb

@jamesg:

I am intrigued by the IndieWeb’s approach to plurality and building technologies that don’t serve the creation of monocultures or single ways of thinking about things. IndieWeb technologies help build plug-and-play social bridges. The technologies are your pipes. You get to decide how they connect and what you make with those pipes. This idea excites me to a great degree.

Could you explain what you mean by “plurality?” In the circles I run in it almost certainly means something different than what you mean by it, and the definition I’m familiar with is likely to be the more common one on the Internet in 2020 2022.

From context it seems like you’re talking about building a (distributed) voting/polling system, which is definitely an interesting topic to think about, and the first-cut approach would probably be to do something using fragmentions or otherwise having a u-vote-for (or similar) link either to an anchor on the page or to the resource being voted on (e.g. the image itself).

Re: Building a Feed Reader to Follow Blogs and Websites: Part 1

💬 Re: Building a Feed Reader to Follow Blogs and Websites: Part 1

Out of curiosity, have you put any thought into adding TicketAuth/bearer token support so that folks can get private subscription content as well? There’s a bunch of security aspects to consider with that but it’s a thing I’d love to see come into a reader.

There’s also a few UX things implied by microsub which I’m not a fan of, personally, and when I get around to finally building Subl (which I’ve only been talking about for as long as I’ve been talking about Publ) I was planning on building it as a standalone thing which could maybe optionally support microsub readers later, but the UX I want to build isn’t cleanly supported by the data model implied by microsub.

(Basically I want to build Feed on Feeds except in Python and with TicketAuth support.)

Re: Micropublish channel support

💬 Re: Micropublish channel support

Oh, cool, I didn’t know channel support was a thing. That just might be what gets me to finally work on Micropub support for Publ, since I couldn’t really wrap my head around how I was going to support posting to arbitrary sections of my site with the current UX on any of the Micropub clients I knew about.

Time to finally brush up on the protocol to see what other excuses I have for not supporting it. 😉