⭐️ Meet Feedle a New RSS Feed Search Engine

Comments

Bookmarked: Meet Feedle a New RSS Feed Search Engine

This search engine seems pretty cool. So far the catalog appears to only have human-submitted feeds, though. I’ve already submitted a couple of mine, and hopefully more folks get on board with it.

(via IndieWeb News)

💬 Re: I wish there were a better story around replying to blogs

Comments

In reply to: Re: I wish there were a better story around replying to blogs

I agree that this is a massive pain point and it’s something I’ve talked about a lot on this blog.

At present, I use a combination of 1 (via isso) and 4 (via webmention.io + webmention.js). The integration on 4 is also helped by using Bridgy and Bridgy Fed to receive webmentions from Mastodon and many of the silos, which strikes an okay balance for me, although it’s far from perfect.

One of the biggest problems with webmention, IMO, is that it doesn’t provide a good story for protected/private responses to protected/private entries. Ticket Auth might eventually provide that, but adoption of that protocol has been slow-going, to say the least, and there’s still open questions about how to actually manage the credentials in an unsupervised flow (especially when using a third-party webmention endpoint). An older WIP called AutoAuth had a much better story for that use case but the protocol was incredibly complicated and implementations never progressed beyond the proof-of-concept stage.

For me, isso as my primary comment system remains the least-bad option of a lot of bad options.

💬 Re: Internal blogging tools

Comments

In reply to: Re: Internal blogging tools

Ben Werdmuller posed a question:

If your company gives its employees a space to blog or journal internally, what platform do you use? What do you think of it?

eg: Confluence has blogs; at Medium they have a whole internal version of the site called Hatch; etc.

Back in the day, Amazon had an internal Movable Type site for internal blogging purposes, although it went mostly unused. When I returned for a couple years in 2012 it was still there although even more completely unused. I posted a couple more entries on it that nobody saw as far as I know.

Nowhere else I’ve worked has had formalized internal blogging (although a couple places had public blogging platforms that were mostly used by marketing folks), although a lot of people certainly would treat Slack as their personal blog.

💬 Re: Private Comments, or Why I’m Down On Webmentions

Comments

In reply to: Haven Blog: Private Comments, or Why I’m Down On Webmentions

This article raises some good points, but there’s another reason I’m not all-in on Webmention: comments on private posts.

Post privacy is incredibly important to me, and supporting webmention on a privacy-post context requires that the comment (and notification thereof) be visible to the receiver’s endpoint, without it being visible to the world at large. This is okay with “unguessable” private URLs, but if you are doing a login-requred thing you start running into issues where you have to either let endpoints through to see the data (which means that any bad actor could also do the same), or you need the endpoints to support the authentication protocols (via e.g. AutoAuth or TicketAuth), and given how difficult those have been to get any meaningful adoption, I’m not terribly optimistic about that changing any time soon, especially with how many people farm their webmentions out to webmention.io which isn’t really in the business of managing things like authentication tokens.

But also, if you live in a world of webmentions for replies, that also greatly increases the chances that someone’s reply will be accidentally posted in public. I already see enough issues where friends will reply to my unauthenticated “stub” entries on Mastodon, rather than posting native comments onto my blog.

The more I get annoyed with Internet comment mechanisms, the more I think that email really is the way.

💬 Re: Mastodon is the new Google Reader

Comments

In reply to: 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)

Comments

In reply to: 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?