RFC 35140: HTTP Do-Not-Stab (2023) • Hacker News Board

Re: RFC 35140: HTTP Do-Not-Stab (2023)

#211

Post by Tarq0n » Tue, Nov 26, 2024, 4:40 PM UTC

cjs_ac wrote: post #138

klabb3 wrote: post #124

Earlier quoted context omitted.

> IMO we need to start normalizing being militant about this stuff again, to aggressively and adversarially defend the freedom to use your computer the way you choose to use it Yes. As a millennial the times of civil disobedience was better. Not only did we get a better internet for consumers, but better companies were rewarded and won. Rose tinted glasses? Possibly, but there’s another reason for disobedience: the o…

> Concretely, is there something like Adblock that can be done for cookies? I use a combination of two browser extensions: Cookie AutoDelete [0] and I don't care about cookies [1]. The second hides any GDPR 'compliance' popup; the first deletes any cookies set by a website when you close the last tab with it open. Both extensions have whitelist functionality. [0] https://github.com/Cookie-AutoDelete/Cookie-AutoDelete…

GDPR compliance isn't about cookies, it's about processing personal data. You can be tracked without cookies, so ignore these at your own peril.

Re: RFC 35140: HTTP Do-Not-Stab (2023)

#212

Post by brookst » Tue, Nov 26, 2024, 11:42 PM UTC

wahnfrieden wrote: post #81

blooalien wrote: post #67

Earlier quoted context omitted.

You'd think there'd be some "competitive advantage" to be had, but when their entire industry is built upon tracking and profiling everyone they possibly can, they'll do anything they can, fighting tooth-and-nail to the very end against any legislation that somehow interferes with their tracking, even if it means resorting to childish and petty temper tantrums that further enshittify the web. What little "competition…

Other replier believes that competition is a system that works toward consumer needs and betterments. Advertising is extractive

Actually I thought I was clear in my framing that, if site owners are unhappy with cookie banners, it is unlikely that a conspiracy of ad networks would force them to accept the nuisance.

The claim is that no sites value their user experience enough to pick an ad solution with a better experience. I doubt that claim.

Re: RFC 35140: HTTP Do-Not-Stab (2023)

#213

Post by zombot » Wed, Nov 27, 2024, 6:08 AM UTC

The date in the title is wrong, it should be 2111. Most appropriately, because something as forward-thinking as this proposal cannot be expected to even come up within this century, let alone be accepted.

Re: RFC 35140: HTTP Do-Not-Stab (2023)

#214

Post by vrighter » Wed, Nov 27, 2024, 1:09 PM UTC

Well, given that we need to tell them what they are not allowed to do, vs what they they are allowed, we need some "Do-Not-X" standard convention for headers.

For example, I have my browser send all of these with each request:

Do-Not-Eat: 1

Do-Not-Insert-Into-Anus: 1

Do-Not-Do-Evil: 1

Do-Not-Chew-Loudly: 1

Do-Not-Forget-To-Bring-A-Towel: 1

Do-Not-Pee-Into-The-Wind: 1

Do-Not-Give-Me-Up: 1

Do-Not-Let-Me-Down: 1

Do-Not-Turn-Around: 1

Do-Not-Desert-Me: 1

Do-Not-Stab: 1

The last one I added just now because this article opened my eyes to this glaring omission.

Re: RFC 35140: HTTP Do-Not-Stab (2023)

#215

Post by tremon » Wed, Nov 27, 2024, 6:09 PM UTC

Tarq0n wrote: post #211

cjs_ac wrote: post #138

Earlier quoted context omitted.

> Concretely, is there something like Adblock that can be done for cookies? I use a combination of two browser extensions: Cookie AutoDelete [0] and I don't care about cookies [1]. The second hides any GDPR 'compliance' popup; the first deletes any cookies set by a website when you close the last tab with it open. Both extensions have whitelist functionality. [0] https://github.com/Cookie-AutoDelete/Cookie-AutoDelete…

GDPR compliance isn't about cookies, it's about processing personal data. You can be tracked without cookies, so ignore these at your own peril.

GDPR compliance also requires explicit opt-in, so ignoring those popups has the same effect as refusing to be tracked. YMMV of course, but I don't see why ignoring cookie banners should lead to worse results than laboriously denying to be auctioned off.

Re: RFC 35140: HTTP Do-Not-Stab (2023)

#216

Post by orbat » Thu, Nov 28, 2024, 4:44 PM UTC

SirHumphrey wrote: post #93

orbat wrote: post #23

Earlier quoted context omitted.

So the EU is bad because you can't learn to screw on a bottle cap that's different than before?

I am not joining the whole “EU is bad argument”, however the new caps are very annoying, especially the limited benefits they provide.

Honestly I find it baffling that a competent adult could find the caps annoying or hard to use

Re: RFC 35140: HTTP Do-Not-Stab (2023)

#217

Post by narrator » Thu, Nov 28, 2024, 5:15 PM UTC

This will probably become less funny when everyone has a home robot that can cook for them. A robot that can handle a knife with sufficient dexterity can be a trained assassin if the owner doesn't pay the extortion demand of the malware that has infected their robot.

Re: RFC 35140: HTTP Do-Not-Stab (2023)

#218

Post by CRConrad » Fri, Nov 29, 2024, 2:37 PM UTC

account42 wrote: post #187

CRConrad wrote: post #91

Earlier quoted context omitted.

No, he needs to learn how to screw on a bottle cap. We keep soda bottles horizontal in our fridge, and they don't leak.

Dismissing people's real concerns is how you get them to vote for parties you don't like. Fact is that the new caps do make it easier to end up without a good seal.

That's only a "real concern" if... I don't know, if you're somehow exceptionally clumsy? But then, you'd be much more likely to drop the old-style cap while trying to screw it on, so the new one would probably be an improvement. So no, it is not a "fact" that the new caps make it easier to end up with a bad seal. I rather think you'd have to go out of your way to specifically do that.

Re: RFC 35140: HTTP Do-Not-Stab (2023)

#219

Post by anticensor » Mon, Dec 02, 2024, 4:44 PM UTC

lucumo wrote: post #155

cjs_ac wrote: post #138

Earlier quoted context omitted.

> Concretely, is there something like Adblock that can be done for cookies? I use a combination of two browser extensions: Cookie AutoDelete [0] and I don't care about cookies [1]. The second hides any GDPR 'compliance' popup; the first deletes any cookies set by a website when you close the last tab with it open. Both extensions have whitelist functionality. [0] https://github.com/Cookie-AutoDelete/Cookie-AutoDelete…

> I don't care about cookies[1]. The second hides any GDPR 'compliance' popup > [1] https://www.i-dont-care-about-cookies.eu/ I like to use Consent-o-Matic[1] for this. IDCAC accepts tracking when ignoring the request doesn't work. CoM rejects all tracking on those popups. I like the slight Fuck Off that that sends. [1] https://consentomatic.au.dk/

Firefox has built-in consent banner decline feature, see how to enable it: https://www.ghacks.net/2022/12/24/configure-firefox-to-rejec...