Seems like they’re advocating using a Fairphone running e/OS, Ecosia as the search engine, LibreWolf as the browser, LibreOffice as the office package, and W for social media?
Yes, but they’re mostly rich and powerful people, right? So they would have left the country when Apartheid ended in 1994, 32 years ago, or decided to dig in and hold on to what their ancestors rightfully stole?
I just don’t see why anyone who meets the criteria would want to come to the US as a refugee in 2026….
"What would usually take, for an analysis piece, maybe half a day to a day, was really being crunched down to a few hours, and (it) was scarily accurate," says Kolga, who tested out Cipher in its early stages and still uses the AI agent to expedite his work.
Seems to me that all this would do in my case is identify that I’m likely the same person in the various forums I post on.
I’ve used LLMs to go hunting for me online, and it took a LOT of prompting to link the same anonymous me across more than a few of the most popular online forums, even when I fed it excerpts from less popular places.
Since I use a different voice in my private communications and don’t post to public forums under my real name, there’s very little to be matched.
Matching up multiple Reddit and Instagram accounts? Sure, LLMs can do that with ease.
The idea is to verify the archival copy’s URL, not to verify the original content. So yes, a server could push different content to the archiver than to people, or vary by region, or an AitM could modify the content as it goes out to the archiver. But adding the sha256 in the URL query parameter means that if someone publishes a link to an archive copy online, anyone else using the link can know they’re looking at the same content the other person was referencing.
If the archive content changes, that URL will be invalid; if someone uses a fake hash, the URL will be invalid (which is why MD5 wouldn’t be appropriate).
The beauty of this technique is that query parameters are generally ignored if unsupported by the web server, so any archival service could start using this technique today, and all it would require is a browser extension to validate the parameter.
Link it to something like Web of Trust, and you’ve solved the separate issue you described.
In fact, this is a feature WoT could add to their extension today, and it would “Just Work”. For that matter, Archive.org could add it to their extension today, too.
Only works for archived pages though, because for any regular page, a large portion of the page will be dynamically generated; hashing the HTML will only say the framework hasn’t changed.
They buried the lede — the decision to blocklist them was because the archived pages were modified in a petty fit of retribution, meaning the archive can no longer be considered an archive (its contents can’t be trusted to stay the same).
The DDoS was just the spotlight that got them thinking about it.
Of course it’s a broad generalization; my point was that the tent cities aren’t predominantly made up of people who hit the kill line, that the situation isn’t that simple.
Fixing the kill line won’t affect tent cities that much; there are further societal issues that are also at play.
In China, substance abuse is handled differently as is mental health issues… so you don’t end up with those people in tent cities either.
This doesn’t mean those people don’t exist in a state of suffering; it just means they’re not publicly visible.
Sounds better than the current solution; I have a feeling it would only take a generation for the same integrity lacking folks to figure out how to game the system though.
He only modified archived pages in response to a dox attempt?
And the thing is, the discovery of the modified pages revealed that it wasn’t even the first time he’d modified pages. And he used a real person’s identity to try and shift blame.
Irrespective of the doxxing allegations, if he’s done all this multiple times already, it means the page archives can’t be trusted AND there’s no guarantee that anything archived with the service will be available tomorrow.
Seems like we need to switch to URLs that contain the SHA256 of the page they’re linking to, so we can tell if anything has changed since the link was created.
My mother’s maiden name was also Spartacus!