(
echo url=https://musl.cc
echo header=Accept:
echo header=User-Agent:
echo resolve=musl.cc:443:216.82.192.10
)|curl -K/dev/stdin
Everyone victory lapping this as a grand failure should pay attention to the above snippet.
Software developers commenting on HN and elsewhere routinely focus on majorities, e.g., "80/20" memes, references to Zipf's Law, etc., and conclude without hesitation that if a small minority, say 5%, of software users do not follow a pattern that a large majority, say 95%, follow, the minority can be safely disregarded
Is it really suprising that people reading the MIT report might focus on the 95% instead of the 5%
IMO, the report is mostly about the 5% but as it happens people care about majorities like 95%
Deleted Comment
Deleted Comment
Out of the glibc tarpit
Instead those apps require that the Signal Messenger, LLC and Meta Platforms, Inc. companies do the encryption, according to their rules, following their protocols^1
The user cannot easily switch from one company to another, the Signal client cannot be used to send/receive messages via WhatsApp servers or vice versa, the protocols are proprietary. Approaches like "CipherGist" are more generic and work with any server that allows upload, temporary storage and download of data
If want to avoid any server storing blobs then can use the server only to provide port numbers for establishing peer-to-peer connections
1. Perhaps Signal and WhatsApp users send empty messages with encrypted blobs as attachments
But being commercial in nature the companies are secretive about how their servers operate
For example, its is easy to submit a blob to Github Gist servers, using any software the user chooses, including something as simple as a combination of small, open source UNIX utilities
This is not the case for Signal or WhatsApp servers