Em Adespoton

Yes; the problem IPFS has is the same problem IPv6 has.

The hash-in-a-URL solution can function cleanly in the background on top of what people already use.

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.

Remind me to ping Jason about that.

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.

Next up: Dems working on secret report found Epstein and Trump were friends!

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.

At least it’s realistic.

What exactly do we consider the Diaspora to be? First generation?

Because there are people living in my area whose ancestors came from China 200 years ago.

Totally incoherent; the first half was meant to be a reply to a completely different comment. Fixing.

Most people who hit the kill line have someone to go live with.

The tent cities aren’t a symptom of two totally different issues: mental health and drug addiction.

And THESE are due to a more endemic cultural issue of: who takes care of people when their friends and family won’t, coupled with the people rejecting the help that’s offered because from their perspective, the tent cities are better than the alternatives?

I’m left with the same questions at the end of that as at the start.

Also, how does OAuth integrate with Passkeys? Because they seem like compatible concepts.

So they’re fined the amount I pay them annually? What about fines for all the other Canadians they’ve defrauded?

To add to the article, Persona is also one of the companies at the centre of the recent furore around Discord age verification.

The ones at my local water park do!

It uses a completely different paradigm of process chaining and management than POSIX and the underlying Unix architecture.

That’s not to say it’s bad, just a different design. It’s actually very similar to what Apple did with OS X.

On the plus side, it’s much easier to understand from a security model perspective, but it breaks some of the underlying assumptions about how scheduling and running processes works on Linux.

So: more elegant in itself, but an ugly wart on the overall systems architecture design.

Along with the other advice, it’s worth noting that “USB” ports can have different specs; make sure you’re plugged into one that supports USB 3.1 or higher.

Also, USB is CPU-bound; if the CPU is busy doing other things, peripheral communication slows down.

Technically, Trump is a “White House Staffer.” He’s the executive in charge.

Generational shift is Apple being a direct competitor with YouTube?