Starting to wonder how significant this news really is?
5,535 karma · joined March 12, 2012
Starting to wonder how significant this news really is?
Words that climb the Zipf curve get squeezed for maximum compression, even at the cost of technical correctness. Entropy > pedantry. Resisting it only Streisands the shorthand.
It's very easy to present a story that is 100% factually accurate, but that implies causal links or other claims that are not. Our brains love hasty generalizations, and media outlets rely on that to present near-100% truthful facts to their viewers, such that they jump to completely opposite generalizations. We're further primed for this with thought-terminating cliches like "trust the data" and "look at the facts". Media profits enormously from the subsequent outrage.
The more folks talk about "fact checking" without acknowledging the danger of cherry-picking and Texas sharpshooters and confounding variables, like in this article, the less I trust "fact checking" as a useful mechanism for forming opinions from their reported facts. Fact-checking is definitely a requirement, but still insufficient.
This is also exacerbated by narratives like those presented by TAL that introduce enormous complexity to the task, due to the emotional context.
The irony and tragedy is broader and encompasses both the cult leaders and the cult detractors who are both unwilling separate the ideas from the people.
People love to talk about what they think is important, but NOT when they think they're being setup or playing into someone else's hand.
(I think the answer is because of the "requirement" that middleware be run out-of-process as Vercel edge functions.)
Relevant parallel to this is the x-forwarded-for header and (mis)trusting it for authz.
This seems like a consequence of Vercel pushing that weird "middleware runs on edge functions" thing on NextJS, and b/c they are sandboxed they have no access to in-memory request state so the only way they can communicate w/ the rest of the framework is via in-band mechanisms like headers.
Is that a fair characterization?
(the fix was to add a random string as another header then checking to make sure it's still there afterwards, effectively an auth token: https://github.com/vercel/next.js/pull/77201/files )
If you thought browser fingerprinting for ad tracking was creepy, just wait until they're using your actual fingerprint.
We're kind of stuck between a rock and a hard place here. Which do you prefer, entrenched incumbents or affordable/open hosting?
It's a very hard space in the long tail, like tables that span pages or tables with complex internal structures. I went into it thinking "eh how hard can tables be?". Very hard. Thankfully it's a pretty active research area.
The argument here is that the loss of privacy and the incentives that will increase centralization might not be worth the gain in security for some folks, but good luck opting out. It basically requires telling bigco about your domains. How convenient for crawlers…
(Note that it's not just GDPR, there's also the EU AI Act which has a whole extra set of requirements for compliance.)
Ironically, dismissing an argument with an ad hominem--like calling it a "trained response"--is also a mechanism that makes ideologies resilient.