Soatok

TL;DR from oss-security:

At a glance, what I found is the following:

1. Session only uses 128 bits of entropy for Ed25519 keys. This means their ECDLP is at most 64 bits, which is pretty reasonably in the realm of possibility for nation state attackers to exploit.
2. Session has an Ed25519 verification algorithm that verifies a signature for a message against a public key provided by the message. This is amateur hour.
3. Session uses an X25519 public key as the symmetric key for AES-GCM as part of their encryption for onion routing.

Additional gripes about their source code were also included in the blog post.

That's a reasonable thing to dislike about it.

I dislike that I can't reply to another message with a sticker.

I also dislike that, despite having admin access, I can't delete abusive messages left in groups for anyone but myself. That makes it unsuitable for building communities.

How much can you control the conversation if the entity you are discussing only wants their name published?

It's not about what they want published. It's about what they don't want published.

Sure there will be a few GDPR letters and maybe an inquiry by some regulatory body. Satisfyingly annoying to them, but compared to the cost of an advertising campaign; would this not be just a drop in the bucket.

Advertising campaigns generally don't include OSINT on the people behind it and evidence of their crimes. How does what I published help them increase their revenue or reduce their costs? Everything is ruled by incentives.

That sort of comment might be true if I had responded with a shallow, emotional response. Something like "how dare these outrageous motherfuckers claim to 'roast' my hand-crafted artisanal open source beauty with their AI slop!!".

I didn't do that. I sifted through the public information, assembled a profile of the people behind it, discarded the irrelevant details, and used it to describe their conduct as illegal in the country their business is incorporated in, with enough receipts for anyone else who finds their AI grift to leverage to give them immense amounts of legal and compliance pain. And then I released this all on my furry blog with the keywords that other open source developers would likely to try in a search engine if confronted with their same outrageous behavior.

Rather than let my outrage make me a useful idiot, I've surveyed the landscape and made sure that I'm controlling the conversation. I'm also keeping the evidence preserved, and not giving them any SEO backlink juice. This all dovetails into how bad their AI is at what it even claimed to be doing.

If any of this plays into their hands, then they're playing chess on a dimension that the void cannot comprehend, let alone my mortal ass. But I'm willing to wager that the amount of legal anguish my blog post will create for their grift will significantly outweigh any benefit they get from the possible name recognition my blog creates.

Yeah, business children is an apt description.

I honestly don’t see the reason to hope for bluesky to win…

It was explained in detail in the other post, which was linked to in the section that said what you're referencing.

Yeah, I've got a proposal that's being worked on: https://github.com/soatok/mastodon-e2ee-specification