They may get off. But I highly doubt Kristy Noem and Stephen Miller will. Or even Greg Bovino. The people responsible for the policies that led to those murders will be held accountable.

Not sure if you’re doing a bit, but i’ll bite: Can you recall any historical examples of US public officials being held accountable for their obviously-criminal policy decisions? Eg, remind me who from the Bush administration went to prison due to the fact that they (as Obama put it) “tortured some folks”? And who from the Obama administration went to prison for any of their war crimes (eg)? What makes you think it will be different for people like Noem and Miller? 🤔

i think i get Candand (what some Barnes & Noble spam once rendered C++ as?) but, what is borsuk language?

💯

hopefully a FOSS organization will hire the person who made this

Reputable news source “GLOBAL FACTZ”

😂

Fwiw, before reposting this meme, I actually checked to make sure that the underlying “weird news” story here was not solely reported by random clickbait fake news sites but was also covered by an actual news organization.

So in summary. You’re right. Sealed sender is not a great solution. But

Thanks :)

But, I still maintain it is entirely useless - its only actual use is to give users the false impression that the server is unable to learn the social graph. It is 100% snake oil.

it is a mitigation for the period where those messages are being accepted.

It sounds like you’re assuming that, prior to sealed sender, they were actually storing the server-visible sender information rather than immediately discarding it after using it to authenticate the sender? They’ve always said that they weren’t doing that, but, if they were, they could have simply stopped storing that information rather than inventing their “sealed sender” cryptographic construction.

To recap: Sealed sender ostensibly exists specifically to allow the server to verify the sender’s permission to send without needing to know the sender identity. It isn’t about what is being stored (as they could simply not store the sender information), it is about what is being sent. As far as I can tell it only makes any sense if one imagines that a malicious server somehow would not simply infer the senders’ identities from their (obviously already identified) receiver connections from the same IPs.

Sure. If a state serves a subpoena to gather logs for metadata analysis, sealed sender will prevent associating senders to receivers, making this task very difficult.

Pre sealed-sender they already claimed not to keep metadata logs, so, complying with such a subpoena^[1] should already have required them to change the behavior of their server software.

If a state wanted to order them to add metadata logging in a non-sealed-sender world, wouldn’t they also probably ask them to log IPs for all client-server interactions (which would enable breaking sealed-sender through a trivial correlation)?

Note that defeating sealed sender doesn’t require any kind of high-resolution timing or costly analysis; with an adversary-controlled server (eg, one where a state adversary has compelled the operator to alter the server’s behavior via a National Security Letter or something) it is easy to simply record the IP which sent each “sealed” message and also record which account(s) are checked from which IPs at all times.

sealed sender isn’t theater, in my view. It is a best effort attempt to mitigate one potential threat

But, what is the potential threat which is mitigated by sealed sender? Can you describe a specific attack scenario (eg, what are the attacker’s goals, and what capabilities do you assume the attacker has) which would be possible if Signal didn’t have sealed sender but which is no longer possible because sealed sender exists?

In case it wasn’t clear, I’m certainly not advocating for using WhatsApp or any other proprietary, centralized, or Facebook-operated communication systems 😂

But I do think Facebook probably really actually isn’t exploiting the content of the vast majority of whatsapp traffic (even if they do turn out to be able to exploit it for any specific users at any time, which i wouldn’t be surprised by).

“Anonymity” is a vague term which you introduced to this discussion; I’m talking about metadata privacy which is a much clearer concept.

TLS cannot prevent an observer from seeing the source and destination IPs, but it does include some actually-useful metadata mitigations such as Encrypted Client Hello, which encrypts (among other things) the Server Name Indicator. ECH a very mild mitigation, since the source and destination IPs are intrinsically out of scope for protection by TLS, but unlike Sealed Sender it is not an entirely theatrical use of cryptography: it does actually prevent an on-path observer from learning the server hostname (at least, if used alongside some DNS privacy system).

The on path part is also an important detail here: the entire world’s encrypted TLS traffic is not observable from a single choke point the way that the entire world’s Signal traffic is.

Many people have reverse-engineered and analyzed whatsapp; it’s clear that they are actually doing e2ee. It is not certain that they don’t have ways to bypass it for targeted users, and there is currently a lawsuit alleging that they do, but afaik no evidence has been presented yet.

This MFer thought there were so smart and then said “Donroe Doctorine” like a good little boy. You know, the infantile word games the media plays in order to propagandize its subservient population of Epstein defenders! Congratulations on your brogramming! You get an extra special treat after today’s slop!

I suspect that you’re missing the actual importance and historical context of the Donroe Doctrine, also known as the Trump Corollary to the Monroe Doctrine, and you’re incorrectly assuming that it is just another goofy nonsense portmanteau Trump made up?

I recommend reading about the Monroe Doctrine, the Olney corollary, the Roosevelt Corollary, and the Kennedy Doctrine, and reconsidering if you don’t expect Donroe Doctrine to appear alongside them in history books.

I also recommend this text: https://progressive.international/wire/2026-01-27-a-doutrina-donroe-e-o-imperialismo-descarado-da-interveno-na-venezuela-1/en/ (there are translations to English and many other languages at that URL)

anyone who objects to mass surveillance obviously hates puppies

Signal protocol is awesome for privacy, not anonymity

The “privacy, not anonymity” dichotomy is some weird meme that I’ve seen spreading in privacy discourse in the last few years. Why would you not care about metadata privacy if you care about privacy?

Signal is not awesome for metadata privacy, and metadata is the most valuable data for governments and corporations alike. Why do you think Facebook enabled e2ee after they bought WhatsApp? They bought it for the metadata, not the message content.

Signal pretends to mitigate the problem it created by using phone numbers and centralizing everyone’s metadata on AWS, but if you think about it for just a moment (see linked comment) the cryptography they use for that doesn’t actually negate its users’ total reliance on the server being honest and following their stated policies.

Signal is a treasure-trove of metadata of activists and other privacy-seeking people, and the fact that they invented and advertise their “sealed-sender” nonsense to pretend to blind themselves to it is an indicator that this data is actually being exploited: Signal doth protest too much, so to speak.

100% of options funded by western governments

One of their four, SimpleX, is not funded by western governments (…but it instead has some venture capital 🤡)

a wifi access point that gets online via a cellular network is called a mobile hotspot, regardless of if it’s running on a phone or a dedicated router device

huh? mobile hotspot is double-bad

https://en.wikipedia.org/wiki/Operation_Metro_Surge is (according to DHS) “the largest immigration enforcement operation ever carried out”

I don’t think anyone called those “web apps” though. I sure didn’t.

As I recall, the phrase didn’t enter common usage until the advent of AJAX, which allowed for dynamically loading data without loading or re-loading a whole page. Early webmail sites simply loaded a new page every time you clicked a link. They didn’t even need JavaScript.

The term “web app” hadn’t been coined yet but, even without AJAX I think in retrospect it’s reasonable to call things like the early versions of Hotmail and RocketMail applications - they were functional replacements for a native application, on the web, even though they did require a new page load for every click (or at least every click that required network interaction).

At some point, though, I’m pretty sure that some clicks didn’t require server connections, and those didn’t require another page load (at least if js was enabled): this is what “DHTML” originally meant: using JavaScript to modify the DOM client-side, in the era before sans-page-reload network connections were technically possible.

The term DHTML definitely predates AJAX and the existence of XMLHTTP (later XMLHttpRequest), so it’s also odd that this article writes a lot about the former while not mentioning the latter. (The article actually incorrectly defines DHTML as making possible “websites that could refresh interactive data without the need for a page reload” - that was AJAX, not DHTML.)

A cascade of satellite collisions is called Kessler syndrome and the risk of it happening is rapidly increasing due to megaconstellations like Starlink:

Here we propose a new metric, the CRASH Clock, that measures such stress in terms of the timescale for a possible catastrophic collision to occur if there are no satellite manoeuvres or there is a severe loss in situational awareness. Our calculations show the CRASH Clock is currently 5.5 days, which suggests there is limited time to recover from a wide-spread disruptive event, such as a solar storm. This is in stark contrast to the pre-megaconstellation era: in 2018, the CRASH Clock was 164 days.

Kessler syndrome could be a solution to the Fermi paradox.

Weird this article doesn’t mention Hotmail and RocketMail, which both had email client web apps in 1996.