For those on laptops (or the more laptop-ish tablets, if that makes sense) who want to Google for ways to remove the cookie, it seems the specific term of art is “element hiding”. Here are instructions specific to Google Chrome, Windows 11 which for better or worse require extension installations (courtesy of Gemini, but here is the non-AI cite):
For element hiding: Install CustomBlocker or uBlock’s Element Picker (Ctrl + Shift + C in uBlock) to permanently hide any specific visual element on a webpage.
…
Here is a good general article addressing several different types of browsers on a variety laptops, tablets, and phones. Unfortunately, it looks like Amazon devices like Fire and Kindle are not covered.
If you’re using the Silk browser to access the Dope, you must have a newer Fire tablet than mine with newer software. The Silk browser on mine gives me the dreaded message from Discourse “Unfortunately, your browser is unsupported …” .
Last I checked – this was some years ago – it wasn’t that hard to sideload the Google Play store to an Amazon Fire tablet. It’s certainly unsupported by Amazon but AFAIK they’ve never tried to block it. I’ve gotten some very useful apps from the Play store including Firefox for Android and the uBlock Origin extension, which is the only browser on there that supports the stupid new Discourse requirements and allows me to haunt the Dope from bed in the middle of the night!
Note that I can no longer download or update Firefox but I think that’s because my version of the Amazon-hacked Android OS is too old – it hasn’t been updated in several years and probably never will be.
I agree with you 100%. But are the “site admins” or other accountable parties yet identified? @engineer_comp_geek posted in this thread at post #12, but has not posted again since. I don’t know if engineer_comp_geek is a SDMB site admin, or a liaison with Discourse’s admin team, or something else.
(Please note: The paragraph above is not a complaint, and especially not one against engineer_comp_geek. I truly don’t know to whom we’d address issues like this present cookie issue. While I think I know engineer_comp_geek can tap our admins, such as they are, on the shoulder and get a response … I don’t know anything about engineer_comp_geek’s specific role vis a vis the SDMB.)
So, anyway … us users are adrift in the water for the near term. We’re on our own to deal with the cookie problem at the individual user level. Working the problem from the powers-that-be side is a good ultimate goal, but doesn’t yet look feasible.
None of the Moderators are Admins. This needs to be bumped up probably to @Ed_Zotti to get to the Techs. I’m still recovering from a bug and have only been partially here. Hopefully one of the moderators already bumped this up, not sure.
It’s worth repeating that the free versions of both Adblock Plus and uBlock Origin will hide the obnoxious cookie in their ordinary default modes. No special configuration is necessary. I haven’t seen the infamous cookie since mid-July.
It’s not really “user-friendly” if the cookie refuses to go away after the user saves their preferences. Allowing a user to go back and change their cookie settings is something that should be accomplished through the “Preferences” setting in their profile. I suspect that using the third-party Osano service for cookie management may make that difficult.
While we’re waiting for a back-end fix, there’s yet another page-level fix on a laptop running Windows – that is, if you’d like to get rid of the cookie temporarily while your engaged in one thread (like if you need to click Reply but the cookie is in the way). Courtesy of Google Gemini (non-AI link):
Right-click directly on the floating cookie image.
Select Inspect (or Inspect Element depending on your browser) from the menu.
Press the Delete key (or Backspace) on your keyboard [NOTE: We need to press Delete twice to get rid of the cookie. Try it, you’ll see - b].
The cookie icon will instantly vanish from your view. It will remain hidden until you click a link, open a new tab, or refresh the page.
These days … for a lot of tech folks, “laptops” is a general enough term to include desktops [I’m curious if Doper techies agree, though we all skew older]. Most laptops are used on desk tops most of the time, anyway. A “park on the driveway” semantic situation coming to life as we type.
I just tried it, and it took several presses: The mold-spots disappeared one at a time, and then the outline narrowed and then disappeared, then there was a blank image-placeholder, and then that disappeared.
The first time I tried it, it was the cookie at the lower-left corner of one of Osano’s own webpages! That took two DELETEs … or maybe I left the placeholder, but it was invisible there? Dunno.
You’re right about using Inspect/delete trick here on the SDMB, though. Three DELETEs.
Strong disagree. We have enough ambiguity in language without trying to introduce more. “Laptop” and “notebook” were terms introduced to distinguish small, portable, battery-operated computers from the kind that sat permanently on or under desks with dozens of connectors poking out of them and that couldn’t be moved without a team of technicians in attendance.
Even though a laptop can be plugged into a docking station and have the advantages of a large monitor and a real keyboard and mouse, it’s still uniquely different from a desktop computer.