FEP-ef61: Portable Objects - Fediverse Enhancement Proposals

Portable ActivityPub objects with server-independent IDs.

I know there's https://github.com/fedify-dev/fedify/issues/288, which is coming along, and https://github.com/mastodon/mastodon/issues/12423 on the Mastodon side, which seems to have stalled.

#fediverse #mastodon

FEP-ef61: Portable Objects · Issue #288 · fedify-dev/fedify

Add support for FEP-ef61 for creating server indepent fediverse applications This FEP are depend on 8b32 which already available in Fedify Implementation plan The following implementation plan was ...

GitHub
This is one area where ATProto bros do have a big advantage. I'd just love to shut them up about it.

Honestly, between this, https://www.fediscovery.org, and Mastodon getting proper reply controls with https://github.com/mastodon/mastodon/issues/14762, these Big Tech-brained ATProto bros will soon run out of VC money *and* any advantage their platform has right now.

https://stefanbohacek.online/@stefan/116697583448447818

So here for it.

@stefan I hope to see open source and fedi alike step into municipal service provisioning via iteratively responsive and controllable peer to peer local and regional networks. Kind of like refactoring for a neo-FIDOnet with a corresponding neo-Usenet to restore the connective tissues all this consumer capture capitalism drove out.

Show me that infrastructure. Maybe support SDF in standing it up. They still have the old pattern libraries. Both wet and dry ware. 🖖

@stefan I am for Loops, but it's a bit different than that FEP.

It's limited to Loops servers, and supports user migration even if their origin server becomes unavailable or shuts down suddenly.

It's more like ATProto, with a central auth service.