I’m not convinced by Session’s decision to remove forward secrecy. I don’t care if it’s malice or incompetence, they shouldn’t be in business of encrypted messaging either way.

And their lack of transparency on their share of underlying network and the associated costs for new entrants doesn’t make them smell like a cryptoscam any less.

My personal advice is avoid. You’ll be far better off with simplex, or xmpp+omemo for something not paired with phone number.

EU is not doing it yet, however there is strong push from interested parties within and outside of the EC:

https://balkaninsight.com/2023/09/25/who-benefits-inside-the-eus-fight-over-scanning-for-child-sex-content

Including illegal use of targeted advertising / misinformation campaign:

https://eupolicy.social/@ilumium/111226868912928077

Look at https://simplex.im/ then. It’s work in progress but the design is good.

But I’m glad to have a better Signal client too.

Only when requested via special form I believe.

I should prepare a guide on how to take your data with you when quitting Reddit.

For instance when you want to be able to prove that it’s your account without disclosing your legal name publicly on Reddit you may use keyoxide.org for cryptographic proof. I think I’ll talk to keyoxide folks about a method of obfuscating those proofs so they are harder for Reddit to systematically delete.

I understand not everyone will be willing to go to court for this, but at this point I want enough of us to be able to to get them fined enough for every platform to notice.

Lobbying will happen whether acknowledged or not.

XMPP actually has that right now, as you can restrict publish-subscribe nodes to contacts. Which is different from private groupchats in that you have unified timeline interface rather than separate chats in the few clients that support it right now.

Personally I strongly dislike this context-less mode of communication and very much prefer topical chatrooms and fora, but to each their own. I just wanted to note this exists and encourage people to try Movim and/or Libveria (both are web based) if that is something people are interested in.

This does sound like something that would work much better with Lemmy.

Partly it is my personal preference for structured threaded discussion as found on on classic blog comment systems and public fora ever since the Usenet.

But also: you get WebMentions so you know where links were posted, you get the entire discussion not just a fragment, and much more useful moderation both thanks to the vote system and thanks to being able to filter specific communities should you want to, in addition to the rather loose instance-based or very specific user-based filtering.

As far as I know the XMPP-AP gateway is pretty much here already, so XMPP should move to the right and be connected with much of the networking platforms. Perhaps highlighting the specific client software (Libervia & Movim) that currently support pub/sub blogging on XMPP, as opposed to just direct and group chat the protocol started with.

I’m also missing RSS/Atom protocols being highlighted in the diagram. While they aren’t bidirectional (or maybe because of it) they still create an immensely useful way to subscribe to content on the social web.

I’m probably missing something, but wouldn’t it be far easier to redirect people to install page of extension for their respective browser? Such extension could then transform the button as needed to point to whichever social web instance.

That’s wishful thinking when some of the platforms just flat out refuse to support necessary features for maintaining p2p connections.

Complaining to application developers won’t change a thing about that.

Complain to Apple instead, preferably in the form of not buying their products unless they actually open their devices to third-party software without artificial limitations in the way.

Like it or not Apple may just say no. They already refuse to give Bluetooth access to background applications in a way that would be useful to p2p messenger. And AppStore inclusion is at their whim, which given their current track record in HK/China I’d be very skeptical about. So unless you are talking about users willing to jailbreak and modify core components of their devices support from application developers doesn’t necessarily accomplish what you want.

That said, Briar developers said they are willing to give technical support to any independent party developing iOS client, they are just not planning to do it themselves. Which I find very understandable because:

• They have no iOS app developers on staff
• Their codebase is not portable to iOS, requiring basically full rewrite anyway
• This whole affair is a risky investment of time and energy for something that competes with core Apple product (AirDrop)

If SimpleX decides to implement any form of Bluetooth messaging that’s compatible with iOS it will be by necessity very restricted and there’s very little the developers can do about that.

While potentially great idea for local area communication, I’d very much prefer more work on basic UX and usability for now.

As for non-local communication, I’m not sure how well that fits with SimpleX model. Briar is able to use mesh of relays that can be only intermittently connected to each other. On the other hand SimpleX is designed to give as little information to relay nodes on the internet about the origin or recipient of the messages. From what I’d read of it so far I’d assume that giving relays enough information to route messages to you would be counter to it’s privacy guarantees.

Feels like https://m.xkcd.com/743/ all over again. :-]