Re: Intermediate auth service

Jacky:

Oh yeah my plan for the indieauth profile service was to also provide h-card and (optional) micropub endpoints. :) I wrote more about that on one of my Subl-related blog posts (which I’m short on spoons to find at the moment).

So I’ve been thinking about this more and more. Having an intermediate service that lets people log in from a silo is excellent for the case you’ve ((@fluffy@queer.party)[https://queer.party/@fluffy]) mentioned. I think I got too far with this and was wondering if they’d use this to do replies, likes and the whole range of responses one could do from their own site.

Having the intermediate service be log-in-able via a silo would certainly be an option but what I was suggesting was actually having an intermediate service where you can also log in with a username/password or whatever. Like, it could be a “silo.” Like, have it as a bootstrap for people getting into IndieWeb without needing to self-host anything.

What I meant by “provide MicroPub endpoints” was me being overly terse and just saying that on the profile you set up on the profile service you could also link your profile to arbitrarily many other services (hosted by others), including MicroPub, as well as authority sources for RelMeAuth or whatever. Basically, a little catch-all tool to fix the bit that I feel is currently missing from the IndieWeb experience for someone who doesn’t have/want to self-host anything.

Incidentally, this is the blog entry I mentioned in that thread where I kind of rambled about this stuff. Also since then I’ve come to realize that there’s no real reason to integrate Pushl directly into Publ since now it does a lot more stuff and more generically than what is suitable for putting into the Publ side of things. (That said, you absolutely can use the same pipenv/venv for both Pushl and Publ, which is how I have things set up on the dayjob website. But that’s getting off in the weeds of minutiae.)

Also, it seems that both of our respective Markdown implementations have gotten confused by the parentheses around the queer.party link. Neat.

Sending ActivityPub backfills

For folks following this site via ActivityPub, I need to run a WebMention backfill which is going to look quite spammy (one post per five seconds when it gets going). Feel free to mute or unfollow; I promise this will end eventually and then things should be sensible for a while.

The process should take around three hours. I’ll post from my main Mastodon account when it’s theoretically safe to follow again.

Not that I expect anyone to really follow this site via ActivityPub anyway! So far this experiment has proven to me what I’d already suspected – ActivityPub isn’t really a great replacement to RSS/Atom.

More ActivityPub testing

Okay so it looks like re-pinging of existing content to fed.brid.gy doesn’t cause it to reappear again, although it’s still a bit of a UX disaster how backfilled toots show up (namely as a gigantic flood to every follower’s timeline). I think that’s more of a Mastodon UX problem than ActivityPub or fed.brid.gy though, and it’s probably a necessary evil based on what happens when a Mastodon sidekiq queue gets backlogged or whatever. Not to mention even in a things-are-current context, the nature of how Pushl works means it’ll probably still cause stuff to get missed.

Read more…

Haha, oops

Looks like fed.brid.gy will happily re-ping itself for already-ingested content, and it also shows up on your timeline as a flood of current items with whatever random dates are in place.

That seems… suboptimal.

Re: tag-reply posts

Haha, sorry for the in-line links! I was thinking of tag-reply posts from the receiving side, as a way of letting others suggest tags for your posts. Readers of your comics post tag-replies on their site, your site would receive them as webmentions and you could add them to the comic post or not.

It’s all IndieWeb building blocks, but it’s a lot of plumbing on your side (accepting webmention data into your tags, moderating) and theirs (making a post on their own site with markup, sending webmentions).

Don’t apologize for the inline links, I could have just not added them. ;)

And okay, I understand what you’re getting at now! Yeah that seems like a possible way to do things although it’s a lot of setup for a lot of people and I like to use the principle of least effort for things like this.

Also this has inspired me to make a subcategory for the blog for conversational threads. I wonder if the webmentions will end up getting re-sent to the previous entry on this new category. I also wonder if I should set up a rule on my Atom feed to let people filter out posts like these.

Tag-reply posts?

In response to my tagging announcement, Marty McGuire writes:

This could be a use case for tag-reply posts!

Brid.gy supports this for tagging people in Flickr posts, as well as adding labels to GitHub issues.

(wow I really have got to write some sort of reply-to post importer… hand-converting that to Markdown was way more work than it should have been!)

I’m not quite sure I understand the use case that’s being called for, here. Publ tags are “tags” in the Tumblr sense, where they’re used to filter and organize posts, like being able to limit things to rants or whatever; I get the feeling that this is confusion over multiple uses of the word “tag,” like how on Twitter/Facebook/Flickr/etc. “tagging” means signaling to someone that they should read a post (akin to “Tag! You’re it!”). Think Technorati tags from way back when, or Atom categories, which are most akin to hashtags on Twitter and Facebook.

I think a tag-as-in-notification thing would be implemented in Publ the same way I implement in-reply-to and so on – I have a corresponding header in the entry file and my template generates an invisible <a class="u-in-reply-to" href="..."> in the post body. The relevant bit in my entry template is:

{% for type in ('like-of', 'in-reply-to', 'repost-of', 'bookmark-of', 'mention-of', 'rsvp') %}
    {% for link in entry.get_all(type) %}
        <a href="{{link}}" class="u-{{type}}"></a>
    {% endfor %}
{% endfor %}

So in that sense Publ already supports that at the template level; I can simply add tag-of to the list of microformat types. Or am I completely misunderstanding what is being suggested?