Goofed Home

RE: https://mastodon.social/@bagder/116359048796181736

Could be potentially nice for fediverse server testing, as more implementations make the jump to final RFC 9421 HTTP signatures.

On the flip side, ever more complex curl invocations (here: Accept header plus signature fields plus key file, presumably) suggest use of more specialized CLI tools, such as provided by @fedify, or at least scripts/aliases.

Speaking of RFC 9421, which notable fediverse implementations can't handle it yet? Anyone keeping track?

#ActivityPub #FediDev #RFC9421

@fedify@hollo.social @julian@fietkau.social

excelent

@gabboman @fedify @julian I'm adding it to activitypub-bot this week. I'll send a link when it's up.

@julian@activitypub.space As I understand the migration path, it's like

1. Able to receive RFC 9421 in addition to draft-cavage
2. Able to send RFC 9421 in addition to draft-cavage
3. Send RFC 9421 by default, but be able to fall back to draft-cavage if needed

So by “can't handle” I meant step 1. 🙂 Although the unspoken step 4 is to remove draft-cavage support once everyone else has taken step 1, I'm ultimately also wondering when we'll get there.

@julian@fietkau.social @julian@activitypub.space Honestly, I think it's going to be a while.

I think the term for step 3 is "double knocking", and it's called out in the HTTP Signature report for the Social CG:

https://swicg.github.io/activitypub-http-signature/

@geniodiabolico I haven't looked at Starling in detail yet, but as I understand it it's intended as a standalone server. Connecting it to your existing blog, regardless of what it runs on, would most likely take some nontrivial programming work. 🫤

@rick have you started to figure out how to get quote posts working?

@liaizon @rick Probably very unlikely as long as the vocabulary isn't in Fedify: https://github.com/fedify-dev/fedify/issues/452 But now that the interaction policy vocab is in, it might not take too much longer.

@julian @rick oh yay I forgot that was the next step in fedify we were waiting for

@webbeef You're a new web browser? Neat! 👍

I don't think we have a “just do this one thing” solution for browser builders in ActivityPub right now. FedCM is a thing that people seem to be working on, but I gather it's a future target.

Maybe you'd like to incorporate the functionality of https://streetpass.social natively, I think that'd be a low barrier start.

Or talk to @benpate about what native browser support for Activity Intents might look like. I hear he doesn't have enough to do yet. 😇

@andypiper Looking forward to it! 😀

My ongoing #ActivityPub projects in order of priority, for anyone waiting for something:

– Interaction policy / reply controls FEP: highest priority, stalled for the past few weeks due to other responsibilities
– @encyclia: probably migrating from Deno+Fresh to Node+Hono for @fedify 2.0, boring infra work
– Updating @fedidevs starter packs for compatibility with @loops and @Mastodon packs: on warm hold, will get to it, but vainly hoping someone will write a Python lib for it before I have to 🙃

@julian @smallcircles

Fascinating idea! And stuff like this is going to spark many more..

Would you Follow the book in order to see when it’s back on the shelf?

@benpate @julian@activitypub.space @smallcircles In case you haven't come across it yet, https://millsfield.sfomuseum.org/blog/2024/03/12/activitypub/ will be a fun read!

@fabio yay it looks like it works now!

another tiny bug I will note: the way you are adding my mention in your reply is causing mastodon to make a link preview for it. while I don't know what you need to do technically to disable it, I know its able to be done since they only show up like this for certain server softwares

@julian @fabio oh interesting! this seems like something there should be a FEP for huh

@fabio this is getting annoying, every time you save your site you are sending a new version of all your likes so this thread gets bumped to the top of my feed