When I click on it, I get a whole bunch of cookie policy options, and when I agree and click “Save”, the stubborn partially eaten cookie image is still there. What purpose does it now serve except to be an annoying distraction (it partially obscures the “Reply” button)?
Is that just on the SDMB or is it Google Chrome? I selected it, chose all the “hell, NO” options, and then used my page editor to delete it it was so damn annoying covering the Reply button!
I saw it on my phone at lunch just a few minutes ago, and when I returned and refreshed my work computer there it was. If anyone figures out how to make it go away, please share that.
(My SDMB window is scrunched down smaller at work, and the cookie icon covers a bunch of text.)
The cookie consent stuff is required by the GDPR (EU data protection laws) that specify that cookie consent options be available at all times. Discourse has been supporting it since at least 2023, the date of the documentation linked below. Usually an admin would configure it to comply with the applicable laws in the local region, so I don’t know why U.S. users are suddenly seeing it.
I didn’t read the documentation in detail, but it seems like a configuration by site, not for Discourse as a whole. I don’t see anything on the general Discourse board about this change, so I wonder if someone updated something specifically for us (either intentionally or inadvertently? @engineer_comp_geek?).
I’m honestly not sure what I did, but it’s gone now. Maybe I didn’t do anything and it coincidentally went away? I looked up how to “block an element” on a page using Adblock-plus and Google AI said to right-click on the element and choose “block element.” Not an option - at least not in Win10 - but there were some other options I investigated and when I got done, the cookie had vanished. I don’t miss it.
Seems to be the case. I’ve disabled the “Block Element” filter in Adblock and the obnoxious half-eaten cookie is now gone for good!
In any case it seems to have been poorly implemented. Once you indicate your cookie preferences (which the EU mandate requires) and those preferences are saved, there should be no further nags.