I suppose this Sealed Sender issue is problematic for some people, but it's not enough for me to seriously consider jumping ship.
I suppose this Sealed Sender issue is problematic for some people, but it's not enough for me to seriously consider jumping ship.
And what good did that achieve, practically? In effect, your friends and family:
- still use a centralised service with Signal (subject to enshittification/changing the deal overnight/acting as a single point of control and failure) - still use WhatsApp because they really have no choice: that's where everyone else is (and so, there is no avoiding Meta's data collection on them and indirectly, on you) - gained nothing compared to WhatsApp+E2EE (being centralised, both Signal and Meta can infer your social graph, the nature and volume of exchanges you have with your contacts, and hence the nature of your relationships, Signal only "pinky swears" it's not looking at it, and that's a very lame "guarantee").
The privacy fatalism in your comment here and in other comments is plainly incorrect.
With SSL, we no longer have to care, and that's much better that way. Signal has all the same means of (meta)data harvesting and analyzing as Meta. It can't be made different: this is built into their very centralised service. All I'm saying is that we should aim for better, and have guarantees baked into the protocol to avoid absolute metadata centralisation. Federation is a good start.
> Whatever issues Signal Foundation has had, they certainly pale in comparison to Meta's.
At this point I would trust a vibe-coded messenger app over anything produced by Meta. Security and privacy are completely opposed to Meta's business model and track record, regardless of how WhatsApp was once designed, and especially regardless of what their PR army claims. The idea that the same couldn't hypothetically happen to Signal is pure fantasy that's not worth entertaining in this discussion.