4 ms·

Thank you. Please get rid of the cookie popup. If a lawyer tells you you need it, find a better lawyer.

ryandrake 4y ago
I agree with this one. On mobile it's a full-screen capture, too. Totally overboard. Why would a reference guide even need cookies? If the author is worried about lawyers, I'd just ditch the cookie use altogether.
waltbosz 4y ago
How long before browsers have a built in setting to automatically tell these cookie prompts "essential cookies only please"?
- pessimizer 4y ago
  Never. If there's anything that browser developers hate, it's for their users to have fine control over what the sites they visit either save (or run) on their computers. proof: they've had plenty of time, and even browsers that claim to be public services can't even keep the APIs stable for cookie/storage control.
  - Eisenstein 4y ago
    opposing proof: Brave does.
    - pessimizer 4y ago
      Godspeed to Brave.
    - GeorgeWBasic 4y ago
      I sure would love it if they came up with a way to block those "intent to leave" popups too.
1vuio0pswjnm7 4y ago
Is it a popup. For example, as a text-only browser user, i.e., no Javascript engine, I generally never see cookie consent popups. (I also control whether cookies are sent via a localhost-bound forward proxy.) However I am starting to notice cookie consents placed in the HTML of the page. This is one example. The cookie consent is wrapped in <div> tags. To get rid of the cookie consent in this case, curl https://img.ly/blog/ultimate-guide-to-ffmpeg/|sed 's/<div class=\"cke-overlay\">/&/' > 1.htm firefox ./1.htm Another way is to use the AMP URL: links https://img.ly/blog/ultimate-guide-to-ffmpeg/amp/ AMP actually looks great in a text-only browser such as links. It may also be possible to remove a <div>-based cookie consent using a browser Add-On like uBlock Origin. If it were up to me, cookie consents would be done via HTTP headers. The user could simply set their client to send an HTTP header indicating no consent. Something like Cookie-consent: False I use a localhost-bound forward proxy to selectively send cookies where they are actually needed. Thus it is not browser-specific. It works with any client, e.g., netcat.
- orliesaurus 4y ago
  what browser (that is text-only) do you use? genuinely curious to try it myself on my site!
  - 1vuio0pswjnm7 4y ago
    links
emsixteen 4y ago
If they're running anything tracking related then they need to gather consent. It's not complicated.

I agree with this one. On mobile it's a full-screen capture, too. Totally overboard. Why would a reference guide even need cookies? If the author is worried about lawyers, I'd just ditch the cookie use altogether.

waltbosz 4y ago

How long before browsers have a built in setting to automatically tell these cookie prompts "essential cookies only please"?

pessimizer 4y ago
Never. If there's anything that browser developers hate, it's for their users to have fine control over what the sites they visit either save (or run) on their computers. proof: they've had plenty of time, and even browsers that claim to be public services can't even keep the APIs stable for cookie/storage control.
- Eisenstein 4y ago
  opposing proof: Brave does.
  - pessimizer 4y ago
    Godspeed to Brave.
  - GeorgeWBasic 4y ago
    I sure would love it if they came up with a way to block those "intent to leave" popups too.

1vuio0pswjnm7 4y ago

Is it a popup. For example, as a text-only browser user, i.e., no Javascript engine, I generally never see cookie consent popups. (I also control whether cookies are sent via a localhost-bound forward proxy.) However I am starting to notice cookie consents placed in the HTML of the page. This is one example. The cookie consent is wrapped in <div> tags. To get rid of the cookie consent in this case, curl https://img.ly/blog/ultimate-guide-to-ffmpeg/|sed 's/<div class=\"cke-overlay\">/&/' > 1.htm firefox ./1.htm Another way is to use the AMP URL: links https://img.ly/blog/ultimate-guide-to-ffmpeg/amp/ AMP actually looks great in a text-only browser such as links. It may also be possible to remove a <div>-based cookie consent using a browser Add-On like uBlock Origin. If it were up to me, cookie consents would be done via HTTP headers. The user could simply set their client to send an HTTP header indicating no consent. Something like Cookie-consent: False I use a localhost-bound forward proxy to selectively send cookies where they are actually needed. Thus it is not browser-specific. It works with any client, e.g., netcat.

orliesaurus 4y ago
what browser (that is text-only) do you use? genuinely curious to try it myself on my site!
- 1vuio0pswjnm7 4y ago
  links

emsixteen 4y ago

If they're running anything tracking related then they need to gather consent. It's not complicated.