social.coop is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Fediverse instance for people interested in cooperative and collective projects. If you are interested in joining our community, please apply at https://join.social.coop/registration-form.html.

Administered by:

Server stats:

479
active users

Dmitri | 🇺🇦

Last day of 2024. Excellent sessions. More linkdump / bookmarks:

* Unconference in the UK coming up -> oggcamp.org (Andy Piper is one of the organisers and it is open source and free culture)

oggcamp.orgOGGCAMP 24 - OggCamp 24

This awesome chart fed.brid.gy/docs#compare compares the components of various Fediverse protocols (ActivityPub, ATProto, IndieWeb, etc)

fed.brid.gyBridgy Fed

Great discussion on DIDs and the Fediverse. Talked about DID<->AP Actor Profile<->ATP round-trip linking, migration from dead servers, migration across different protocols and domains, other stuff. And hey, resulted in this: github.com/snarfed/bridgy-fed/

Inspired by a FediForum DID afterparty with @dmitrizagidulin @bnewbold @bumblefudge et al! We should: Put a Bluesky account's DID into its bridged ActivityPub actor object Put an ActivityPub actor ...
GitHubPut Bluesky DIDs and AP actor ids into `alsoKnownAs` in actor objects and DID docs · Issue #1331 · snarfed/bridgy-fedBy snarfed

@dmitri @evan I probably won't understand any of it. But I can't wait to read it!

@dmitri seriously, I think we need a TF for this. Does `alsoKnownAs` work?

@evan Great question! The thought so far is - it could be as "simple" as careful `alsoKnownAs` usage. Let's see what the initial prototypes/implementations say, maybe we won't need a TF after all.