This whole cookie dickover concept is malicious compliance. The goal was: no tracking but ask consent if you must ("who would do this, that would be super annoying"). Except every website decided they'd rather annoy everyone.
Right the intention was to stop unchecked surveillance capitalism, now they use the normalcy of annoyance to wear you down such that you auto accept terms that you probably wouldn’t agree to if you read them. That’s what they want now.
This and other bad behavior will only go away when government says, “no this is predatory and you can’t do it” instead of saying “everything is OK if the user consents to it”.
Well… Europe do require the accept and deny options to both be equally visible and accessible, see for example this week-old court ruling:
> Administrative Court (BVwG), thereby upholding a decision made by the Austrian Data Protection Authority in 2024. Specifically, the ORF must ensure that the buttons to ‘accept’ or ‘reject’ tracking cookies are designed equally so that visitors are not tricked into agreeing.
GDPR doesn't mandate cookie banners, it says that you simply cannot store irrelevant PII for the sake of it. That's the point of it: to protect the privacy of the public against "data brokers" and other scum. You're welcome.
People seem to have forgotten, but cookie banners were a pest before GDPR. And newsletters and login popovers, those are GDPR?
I remember it being somewhat common for people to make forum posts consisting entirely of a joke image. However, they weren’t called memes at the time as the word had yet to be popularized.
But it's always been correct to interrupt a discussion on a PHP forum about PHP security by breaking into Rasmus's account and posting an ironic meme under his name.
I think it's the fivethirtyeight of of historical significance, and Disney is one of the largest and wealthiest companies on the planet. So it's just kinda like "whoa, this is stratospheric negligence" or "whoa, what is the reason for this... assuming they are not idiots?"
Also, they don’t any plans for the IP, and Nate would’ve paid above-market rate just to take over and preserve the content for posterity. He estimates that they deleted 200,000 hours of human labor.
This is just some Disney suits being extraordinarily petty.
Yes, just to add to this: in the article by Nate [0] he says that he tried to buy the IP but Disney refused because they were unhappy with some of his prior comments.
"I did approach Disney a year or two ago, through my agent, about acquiring the remaining IP. ...
We were told to basically get lost: ABC was annoyed with my critical public comments about their management of FiveThirtyEight. It apparently wasn’t a long conversation, so I don’t have a lot more color to report than that."
Here are some numbers roughly in the right ballpark: during the Disney era, which lasted about 10 years, FiveThirtyEight published about 20 stories a week. Let’s say that each story took about 20 hours to produce between research, writing, graphics and editing.3 Do the math, and that works out to about 200,000 person-hours of work that ABC News just deleted.
In a sense, nothing - and any other website should be archived, too.
In another sense, it's a journalistic source with information and commentary on past elections. Even aside from the political context that muddies the waters around or outright denies results, matters of public discourse on the web should not be ephemeral or subject to the decisions of the publication - they should be archived.
Nobody has it on, and unless BOTH sides are using it, your iMessage conversations are all readable by Apple, because they are backed up twice - one for each end.
This option is also disabled in the UK - an intentionally preserved backdoor for government access.
They haven't fumbled anything. One person has used AI to vibe code a rewrite of a Zig program in another language. Zig didn't gain popularity due to Bun, last I checked Bun doesn't even mention it is written in Zig on the homepage. Zig is appreciate for major improvements over C, while being simple and concise.
In addition, a core Zig developer has explained why the PR was rejected, because it would introduce non-deterministic bugs into the compiler, just to achieve a speedup Zig is already gaining thanks to recent work on the self-hosted backend and incremental compilation, which are far more general as well.
It's been repeated many times that the rejection of the Bun PR was unrelated to their AI-policy. It's also not clear they've "fumbled the ball" given how many projects are complaining about slop PRs.
I think it would help if Zig put out a statement on their actual AI policy, regardless of whether they’d be repeating something that should already be known.
As often happens, the online discourse has, for some reason, decided that this was an anti-AI stance, while - as far as I understand - the problem was simply that the PR had problems, which lead to Bun forking Zig.
reply