> At what point does privacy mean blending in with the crowd and not sticking out?
It's basically rule number one. Tor is all about making all users look like the same user. The so called anonymity set. They all look the same, so you can't tell them apart from each other.
I read here that most of the Tor exit nodes are operated by governments and governments are using parallel construction to keep that information out of legal documents.
Well, yes. They control ISPs and exit nodes, therefore they can correlate entries into and exits out of the Tor network, narrowing down candidate lists until only one user remains. Essentially a nation scale version of the Harvard bomb threat correlation:
As noted in the article, it wasn't the failure of Tor that led to arrest, it was poor OPSEC. Failure to cover, failure to conceal and failure to compartment.
Unlinking one's identity from one's activity is only getting harder as surveillance gets more and more pervasive. Effective OPSEC essentially turns one's life into a living hell and it's only getting hotter with time.
The issue is POSIX standardizing legacy stuff like shells, thereby tempting people to write "portable" software, leading these technologies to ossify and stick with us for half a century and counting. Someone comes along and builds something better but gets threatened for not following "the UNIX way".
This is a very good point. I wonder how hard it would be to get POSIX to standardise a scripting language that isn't awful.
Probably never going to happen. There is a dearth of good scripting languages, and I would imagine any POSIX committee is like 98% greybeard naysayers who think 70s Unix was the pinnacle of computing.
POSIX does not specify the init/rc script system, so it's not a factor here at all. A POSIX-compliant system could use Python scripts. macOS (which is UNIX 03 certified) uses launchd. A POSIX system has to ship the shell, not use it.
And FreeBSD isn't actually POSIX-certified anyway!
The real consideration here is simply that there are tons of existing rc scripts for BSDs, and switching them all would be a large task.
I'm also from Minas Gerais. Mariana and Brumadinho were truly devastating... The sludge is still visible in the rivers to this day. What gets me is how unnecessary it was. Could have been prevented.
Yes, it was heartbreaking. The gut-wrenching book "Arrastados"[0] by Daniela Arbex does a good job of retelling some of the stories from the Brumadinho disaster.
[0] For those that do not speak Portuguese: I think the book title can be translated as "The Dragged Ones".
If your assumed goal is regime change from autocratic to democratic, they lost. If it was for stability in the middle east, the lost. If it was for oil and pressure on OPEC, I'd say they lost, but I would hear and understand an opposite argument (and change my mind).
They did not lose. They failed to achieve certain long term strategic objectives. Their military still mopped the floor with all of their enemies, inflicting millions of casualties before finally retreating for whatever reason, and they're only getting better at it by constantly maximizing the casualties per dead US soldier ratio.
It's not going to go well for Venezuela if the US attacks it, no matter the result of the war.
> sequences are a band-aid over the lack of real iterator protocol
Wouldn't it be better to solve that problem? Proper generalized iteration with generators is just semicoroutines which can be implemented by swapping around stack pointers with zero copying. Should be competitive performance wise.
As linked, the extensible sequence protocol (https://shinmera.com/docs/trivial-extensible-sequences/) already exists and is quite workable. The problem is that it's not supported enough, both by implementations (CCL missing, for example) and the entire ecosystem.
In the end, it's simpler to stay with boring, ANSI compliant solutions well optimized by compilers.
There are effectively two Common Lisp worlds: the commercial world where Allegro and Lispworks dominate, and the non-commercial world where SBCL is more or less the only game in town.
Last release was August 14 2024. For a 30+ year old project, that's quite recent methinks.
It clearly doesn't move as fast as SBCL, but I wouldn't call it abandoned either.
ototh, afaiu, SBCL gave up on ARM32. Can't blame them for that, but until 2023 I was still using an early Banana Pi with such. CCL worked there much better (also it's GC seems more robust).
I've been toying with trying to add extensible sequences to ccl as a way to get more familiar with it, but ccl development seems dead so I'm not sure it's worth the effort.
> I guarantee you that Mozilla will be fine without all the non-sense people
> just put engineers in charge
I would like that but is that even possible? Look at Wikipedia. Look at schools. Once an organization develops a bad case of fat "administrator" class, can it be cured or is it terminal?
It's basically rule number one. Tor is all about making all users look like the same user. The so called anonymity set. They all look the same, so you can't tell them apart from each other.
It's also part of the rules of proper OPSEC.
https://en.wikipedia.org/wiki/The_Moscow_rules
> Do not look back; you are never completely alone.
> Go with the flow, blend in.
> Vary your pattern and stay within your cover.
reply