z201205 I wish that I could set up a bookmark so that I didn’t have to interrupt my browsing experience with these pointless cookie prompts.
That’s one reason for why I’m requesting the ability to declare these by querystring or similar method that’s easy for the user to present to the site on first access. If the user were to openly declare their cookie preferences on first access this’d stand compliant with the cookie laws (It both proves the user is aware of cookies, and has expressed their preferences for them) and no modals would need to be presented. 👍️
Indeed, I’m quite surprised browser user groups havn’t already proposed standards for expressing those preferences in-browser for that purpose! 🤯
skier Totally agree about the intrusive modal cookie nonsense, but trust me, having already answered doesn’t stop them asking again next time.
If the user has already expressed their cookie preferences in the past - Whether on a prior visit, or by using in-browser declaration - I’d sooner see persistent Cookie badgering outlawed as being intrusive and defiant of the users’ right to not have their privacy or activity disturbed. I’d also view periodic review (Once per year or longer) acceptable, though. 👍️
Glad to see I’m not the only person who finds Any enforcement to have JS enabled offensive! I’ve long been of the mind that forcing the user to have JS turned on (Which is entirely the users prerogative, not that of the website operator) might well contravene the Computer Misuse Act - It forces the user to execute code on their computer that they have every right to choose not to execute on their system! 👩⚖️ 📜 ⚠️
It needs to be noted that JS and other technologies can - Potentially - Download anything to the users device and also store it on that device, often without the users knowledge. In theory one could use this to cause the storage of photos of TGVs on everybody’s devices…And if one can exploit this to cause the local storage of photos showing high-speed trains, they can use it to cause the storage of photos (and other media) showing literally anything! ⚠️ 🤯 🚫
One of the main reasons for my use of non-persistent OS’s is to prevent persistence of anything which is sneakily downloaded to the browser in that fashion with the intention of exploiting the user at a later date. If a malicious website were to cause the download of a strongly protected work of copyright^ to my PC with the intention of leveraging that against my legal reputation in the future (i.e: You pay us, or we tell the copyright holder that you have an illegal copy of work on your PC) the fact that work ended up on a RAMdisk - The contents of which became irretrievably lost when the PC was turned off - Means no evidence of this could be recovered from the user end, and no claim for theft of work or other copyright infringement would stand up in court. 👍️
(^ - I use strongly protected work of copyright here as an example, but there are other types of content that could be fed to a users browser which would lay them open to charges for far worse offences than just copyright infringement… ⚠️ 🚫 🤯 )
inspiron42 You can thank the EU for all those pointless cookie prompts. A complete waste of time and encourages automatic clicks on pop ups, increasing the risk of activating viruses, Trojans etc.
I don’t think this is just an EU ruling, although I’m aware it’s one of the many things the EU mandates - It’s the way this sort of thing works that appears to be (V..e..r..y s..l..o..w..l..y 😉 ) bringing me around to accepting Brexit💩 for what it is. 👍️
That said; Leaving the EU doesn’t necessarily mean we’ll see an end to the cookie modals. Aside from the fact EU law will still apply on day one after we’ve left the CU due to the working of the Great Repeal Bill (Which I have to concede I think is a good way of going about it) there’s every likelihood HM Government might choose not to change the law in that regard, or could potentially change it to something worse! 🤯
muddycalhoun I operate various privacy controls and virtually every webpage throws up its cookies policy to accept. Generally I would continue using those that don’t obstruct the whole view of the webpage but unless it is vital I just dump any that fully block the view of the contents.
That’s one of the best things about knowing how to use the Developer Tools! Annoying full-page cookie modal? Just delete it from the DOM! 😃
The only thing is that websites are increasingly becoming aware of this and are using more convoluted techniques to try to work around it. Where having JS off used to simply mean a page with no active content (And often no ads) it now tends to result in an apparently empty page until you find some deeply buried element whose CSS parameters are somehow forced to apply to the entire page. 💻️ 🔀 🤯
I’d so love to see laws bought in which oblige the display of basic content to all browsers by default and without any JS or cookie support, but the likelihood of that happening whilst we have a Conservative government in place is probably quite remote… 🇬🇧 💰️ 😉
+++ 🚄 ThunderDragon 🤘 +++
