Ben Pate 🤘🏻Dec 29

It's live.

I've just released my final software update for 2025, which includes 100% fidelity account migrations between #Bandwagon servers.

This long-overdue enhancement means that everyone can take their identity to any other #Emissary server on the #Fediverse. EVERYTHING moves with you.. music uploads, album sales, everything. And, your followers are forwarded to your new address.

There's plenty more, including a 2025 recap, and some plans for 2026 here: https://bandwagon.fm/2025-december

December 2025

Bandwagon.fm
Show threadwordsmith‽ ⁂
@benpate this is great news, it shouldn't come as a surprise that a Fedi contributor such as yourself made this feature such a high priority but considering how big your to-do list must be, it still surprises me. Bravo!
Dec 29 at 9:34pmWeb
Show threadBen Pate 🤘🏻Dec 29

@wordsmith

Thank you! Data Portability always had to get out the door this year, and the E2EE project was the final push to get it done now. I neeeeded this off the kanban board so I can focus exclusively on encryption through February. #JustBetweenUs

Show thread Shlee messed around &Dec 30

@benpate @wordsmith E2EE is a huge thing and I've seen about 4 different people announce similar plans recently

What's your plans for E2EE? Anything public? are you planning on using the key management stuff announced recently?

Show threadBen Pate 🤘🏻Dec 30

The spec is published here: https://swicg.github.io/activitypub-e2ee/mls

There’s a lot to do, but I feel pretty confident in the people working on this.

@shlee @wordsmith

Messaging Layer Security in ActivityPub

Show thread Shlee messed around &Dec 30

@benpate @wordsmith MLS over AP? Those are some lovely words to hear.

*salutes*

Show thread Shlee messed around &Dec 30

@benpate @wordsmith wait..

"For an Image in Portable Network Graphics (PNG) format, the content property value will be the base64-encoded image data." / attachment. These values should not be Link objects; instead, they should be content objects of the above types. They should be *included fully* using base64-encoded values in the content property, with the mediaType property set.

{
"@context": "https://www.w3.org/ns/activitystreams",
  "id": "uri:uuid:38B03587-CEA8-439B-AFCE-6CC3C69E51FD",
"type": "Image",
"name": "One-pixel PNG",
"mediaType": "image/png",
"content": "iVBORw0KGgoAAAANSUhEUgAAAAEAAAABAQMAAAAl21bKAAAAA1BMVEUAAACnej3aAAAAAXRSTlMAQObYZgAAAApJREFUCNdjYAAAAAIAAeIhvDMAAAAASUVORK5CYII="
}

 I hope I'm misunderstanding... attachments are just included and we're going to have 100MB json blobs sharing videos?!

"Base64 encoding increases the size of data by approximately 33%" if I remember correctly.

ActivityStreams 2.0 Terms

This document lists the terms used for the ActivityStreams 2.0 protocol and its stable extensions, and provides a namespace so each term has an HTTP IRI.

Show threadBen Pate 🤘🏻Dec 30

Our first iterations will be text only. But yeah.. if you want to share images E2EE, then you can’t post a link to the elsewhere. They’d need to be included in the encrypted messages. It’s how Sognal works today.

@shlee @wordsmith