7heo
The essence of that article can be summarised in:
- The Streisand effect is helping the news outlets that meta censored.
- We can all move away from meta, and they will essentially go away.
Honestly, if the makefile is well written, I will take that any day. Good makefiles are 😙👌.
They are extremely rare, tho...
I guess the solution would be a declarative language that compiles to makefiles. So that people don't have to know the nitty gritty of writing good makefiles, and can just maintain a file of their dependencies and settings...
¹ Repudiation in SimpleX Chat will include client-server protocol from v5.7 or v5.8. Currently it is implemented but not enabled yet, as its support requires releasing the relay protocol that breaks backward compatibility.
² Post-quantum cryptography is available in beta version, as opt-in only for direct conversations. See below how it will be rolled-out further.
Some columns are marked with a yellow checkmark:
- when messages are padded, but not to a fixed size.
- when repudiation does not include client-server connection. In case of Cwtch it appears that the presence of cryptographic signatures compromises repudiation (deniability), but it needs to be clarified.
- when 2-factor key exchange is optional (via security code verification).
- when post-quantum cryptography is only added to the initial key agreement and does not protect break-in recovery.
It should be, but the server is overloaded.
It's being DDOSed. Too many users. Too many submits. The rendering code is light enough on the server that it still works (most of the work is client side, the sever just serves a bunch of json files), but the submitting code definitely crashes.
Cool, but it's now impossible to submit anything, as the server is being DDOS'd. Not out of malice, mind you, there are just too many geeks out there, and this is a Sunday...
Still, one can read the titles of the already posted rooms with:
env URL=https://incredible.xkcd.com \
curl -SsL $URL/machine/current \
| jq .grid[][] | grep -v '^null$' | tr -d '"' \
| while read uuid; do printf '%s: ' "$uuid"; \
curl -SsL $URL/folio/$uuid \
| jq .blueprint.title; done
(Useful to find out if your room made it to the public set)
Usually that's about when I strace
the process before running it through gdb...
Yes, I get that point, but I also think that it's tempting for the privacy-minded novice to think "the less information I provide, the better!", while in actuality, it is better to provide "more" information: the most common UA, even if it means lying about your featureset. In this case, truly, more is less.
Oh gee, I wasn't aware there was more to it than the UA. Thanks for opening my eyes.
Edit: I checked your link, most of the parameters on the test require client side execution. That (client side tracking) is absolutely unrelated to what (server side tracking) I was talking about, and is something you can control (by not allowing JavaScript, for example). Please do not confuse the two. There is literally nothing you can do against server side tracking.
Yeah, make your user agent absolutely unique. Too much entropy will surely confuse the shit out server side HTTP Header tracking. 😬
But hopefully I can delay and minimise it a bit, open a better channel of communication with a few friends and relatives and perhaps raise some awareness in the process.
Absolutely.