Blake Leonard

Okay so I more or less know that WhatsApp, Matrix, and XMPP are all planning to integrate with MIMI. I wonder if @delta is also trying to brainstorm ways to integrate their chatmail distribution with MIMI, once the specs are finalized?

We're facing down a war of the chat apps, and unfortunately it looks like the closed-ecosystem RCS and developer-hostile PII-gathering centralized Signal and WhatsApp are winning. The open ecosystems can't win if we're all infighting.

I'm still curious what MIMI is coming up with. Last I checked it was pretty dominated by Matrix.

Looks like I'm rooting my phone today.

I'm definitely still going to lose a lot of data, though, because adb backup is nearly useless now (deprecated, plus apparently most apps forbid backups as indirectly enforced by Google Play), and without root there is no other full backup system.

Most of my apps use cloud/network services, so what those will take is signing in again. I just need to figure out what isn't, and back those up...

The one big thing I'm desperately missing on @Codeberg/@forgejo is search. Not just searching for repositories but for files and code inside a repository. Apart from that it's pretty much perfect!

(it does kinda suck that they're so strict about licensing. Totally understand forbidding proprietary/anti-user software, but I feel like they should be open to a wider selection of licenses, like NVPL, post-open, or some of the Perimeter licenses. And hell maybe they are and just don't say it, or it's something they typically overlook.....)

RE: tenforward.social/users/nivex/statuses/114088669351162294

It appears the prevailing mechanism for DMs over #ActivityPub is just direct Notes. Misskey/Firefish mark it as a DM with a non-standard field. Pixelfed either doesn't have any DM distinguisher, or it uses a different non-standard field. Pleroma uses a non-standard type ChatMessage and appears to apply certain special logistics to it (i.e. only one person, and it must be a single Actor, may be specified, and only in the to field).

Maybe the mechanism for Babilejo will aim for maximum compatibility with "type": ["Note", "ChatMessage", "https://joinbabilejo.org/ns/type#ChatMessage"], the Misskey special field, and treating the Babilejo ChatMessage type (and the Pleroma ChatMessage type) as a descendant of Note. That way, I don't have to have any special compatibility mode (as long as all the popular projects are spec-compliant, accepting multiple types...)