Sure, but we both know that security of a communication solution is more than the applied cryptography. My understanding was your article was originally in regards to product comparison tables. I only took issue in regards to the jurisdiction issue in that context.

I'm glad we agree with each other, but also take note that it's more than development but also the supply of software and updates. Middlemen can be compelled by these laws too. All this goes back to my original point: jurisdiction can matter due to supply chain risks, even for infrastructure.

If you read the material I sent to you, you would understand how this legislation can impact Australian users of numerous software.

It wasn't theoretical for the Oxen Privacy Tech Foundation

I should correct myself: I meant to say the "TOLA" not "TIA", which is different. TOLA is effectively just an amendment to the Telecommunications Act.

@session-app.bsky.social use to have a significant presence but had to leave the jurisdiction due to supply chain risks. Not the best article but www.theguardian.com/australia-ne...

I agree with a lot of what you're saying but I think the "But What If The Host Country" part underestimates the power of some legal tools in some jurisdictions. If you don't mind, I think I'll do a write up on the power of the Technical Capability Notice in Australia and just how much power it has.

E2EE is not going to help you if a jurisdiction can compel your hosting provider to serve up backdoored clients via it's respective update mechanism (Example: TAN's/TCN's under Australia's TIA Act)

Jurisdictional information is useful for evaluating supply chain risks.