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.
#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:
I write a lot of notes in #Obsidian (@obsidian) where I mention fediverse handles in the @username@domain.tld format.
I always want to link it to their profile so I manually change it to @username@domain.tld (or whatever the form of url the software they are using is) I feel like there should be a simple way to solve this with an Obsidian plugin that resolves #WebFinger names or maybe some RegEx userscript macro would be easier? Anyone have a solution to my silly problem?
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.
@julian I think the best way is to subscribe to the the mailing list and reply to state your interest to participate and in what way.
I am not sure about how-to-subscribe for this particular list, and I'm not subscribed myself. I created the socialhub topic to draw attention to fedi dev community there.
See that there's a 'reply' icon on the thread, which pops up an email form. Dunno if that works. #IETF Search finds zilch searching for #WebFinger weirdly enough.
In case you missed it (I also didn't see it in the install doc), the new version of Mastodon (v4.2.0) includes automatic update checking every 30 minutes in the background
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.
Improved the webfinger handler for the #GoActivityPub reference implementation to support finding https:// resources alongside acct: double @ ones used by the larger fediverse.
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.
Just set up webfinger so "AT mastodon AT underlap.org" is an alias for my mastodon account on fosstodon.org. (I can't post the actual account because mastodon replaces it with the account it refers to!)
Tried to send a message to the IETF's #WebFinger mailing list with some feedback from @feditest. Tried three different sender e-mail addresses. None of them went through. Not sure what else to try.
Currently getting my head round webfinger, webmention, indielogin, and the like: a mix of standards, experiments, and some decent results.
When does it make sense to use webfinger link relations vs link tags with rel(ationship) attributes in the <head> section of a web page? Are these equivalent features that just happen to have grown up in parallel or is there some rationale delineating the two?
Any clarifying articles greatly appreciated, as are boosts.
Wrote a summary of web linking (AKA link relations; think rel="xxx" in a <a/> or <link/> HTML element).
The piece of the puzzle that's still unclear to me is whether WebFinger has been superseded, or maybe just generally ignored. There doesn't seem to be much adoption (except by Mastodon) or follow-on activity AFAICT.