The whole idea of BlueSky supporting nomadic identities but the rest of the ActivityPub (plus other stuff) Fediverse being unable to do so is such an oversold idea.
A new service using ActivityPub behind the scenes (and not the AT Protocol) can absolutely support nomadic identities, even if the service doesn't treat a whole website as the actor.
It will still use did:plc, same as AT Protocol (BlueSky), but once done so, an application that understands how to work with did:plc can dereference an actor based on the DID.
That said, an existing service will simply not be compatible with this idea, without changing how it operates.
Tonight I implemented something "just because" on my version of @Edent ActivityPub educational server. Some platforms will pick up a profile background image and display it along with your banner and avatar.
In your webfinger record, add this little bit at the root of the file and wallah. Akkoma is picking it up, at least! It's fun to play around.
#Fedify is an #ActivityPub server framework in #TypeScript & #JavaScript. It aims to eliminate the complexity and redundant boilerplate code when building a federated server app, so that you can focus on your business logic and user experience.
The key features it provides currently are:
• Type-safe objects for Activity Vocabulary (including some vendor-specific extensions)
• #WebFinger client and server
• HTTP Signatures
• Middleware for handling webhooks
• #NodeInfo protocol
If you're curious, take a look at the Fedify website! There's comprehensive docs, a demo, a tutorial, example code, and more:
Part 6 of "A Guide to Implementing ActivityPub in a Static Site (or Any Website)" is now out.
Sorry about the delay, this is the part that not many people will like, I assume. I try to explain how to implement the inbox, which by nature is dynamic non-static.
I have been making progress with the #webfinger and even the actor profile. But I still can't get it to show on Mastodon. Not sure where is it wrong. I've been comparing it with many tutorials, code bases and profiles. Only my old WordPress profile still shows. @marisabel Not sure if it is just time. The profile does work in rss-is-dead.lol and the webfinger also on webfinger.net . I still need to research more. I don't want to bother with inboxes until it shows. #activitypub
Improved the webfinger handler for the #GoActivityPub reference implementation to support finding https:// resources alongside acct: double @ ones used by the larger fediverse.
Hmmm.... wondering if it's possible to craft a custom #webfinger endpoint that enables serving different users from different #ActivityPub software on the same hostname.
Part 3 of "A Guide to Implementing ActivityPub in a Static Site (or Any Website)" is just out the oven!
In this blog post, I explain how to make your blog discoverable in the Fediverse as an account, and also address some of the annoying pitfalls I encountered.
A case of spec ambiguity, maybe? I can't find a mention in WebFinger or ActivityPub specs of usernames being case insensitive. Are @osma and @osma referring to the same actor? Is that up to implementation? How does a remote server determine which is correct?
Edit: I wrote above (at)Osma@mas.to and (at)osma@mas.to, but some part of the stack converted both to a lowercase mention during posting. I don't know which part, and what specs describes that.