Danilo

@fribbledom@mastodon.social that's what a SOCKS proxy is made for... I think.

@FlohEinstein@chaos.social @pcdog@chaos.social @deuxcvsix@social.tchncs.de ich bin wohl synästhet, ich höre deine emoji 😂

@nblr@chaos.social @threemaapp@mastodon.social @eliasp@mastodon.social the good thing is that as a user you don't even need to trust the new owner. Thanks to open source and reproducible builds (https://threema.com/de/why-threema/open-source) you can verify the claims made in the cryptography whitepaper (https://threema.com/assets/documents/cryptography_whitepaper.pdf)

@nblr@chaos.social @threemaapp@mastodon.social @eliasp@mastodon.social the reason why private users choose Threema over WhatsApp and why companies choose Threema over Teams or Slack is the strong focus on privacy and security. What motivation would a new owner have to hurt that reputation? It's what makes Threema Threema. Secure communication is a growth market, and digital sovereignty a buzzword. No reason to change the trajectory of Threema.

@nblr@chaos.social @threemaapp@mastodon.social @eliasp@mastodon.social thanks (and I do mean that sincerely as well, we already follow each other for a few years now). Threema is positioned in a way where business goals and privacy/security goals align very well. I'm sure we're on a good path 🙂

@Suiseiseki@freesoftwareextremist.com @mjg59@nondeterministic.computer bold claim. GrapheneOS Auditor app uses attestation to verify that an installation was not tampered with. I would definitely put that into the "helpful" basket. https://github.com/GrapheneOS/Auditor

@odr_k4tana@infosec.exchange @nblr@chaos.social @threemaapp@mastodon.social @eliasp@mastodon.social what are you referring to, the verification process itself? Then - yes, but I'm affiliated with Threema 🙂

@stereo@freiburg.social @threemaapp@mastodon.social threema clients are open source, and that's where E2EE happens, so you *can* verify. threema is always E2EE (in contrast to Matrix, for example).

@mitsuhiko@hachyderm.io @badlogic@mastodon.gamedev.place This one resonates with me: "All these models see a local failure and try to locally defend against it. As maintainers we have to keep pulling the conversation back to the global invariant, which is harder than it should be, and it’s laborious." Did you already experiment with documenting the invariants in AGENTS.md, or creating skills to get the models to understand these invariants? If yes, how were the results?

@matthewcroughan@social.defenestrate.it here's another FP5 port: https://github.com/gian-reto/nixos-fairphone-fp5 Did you get audio/video working?