European Cookie Bullshit

Fastidious

I see no issues with the "European Cookie Bullshit" (I am from Europe, but as American as Lincoln now). It is intended to protect the user (any other hidden and ulterior purpose notwithstanding). It takes a second to make the notice disappear. More often than not, I simply ignore it and continue using the site as I was.

prog

@a_5mith I don't use it on forum, but some other sites.

All larger forums and blogs use Adsense or ads in general. If you have some heavy used website, which generates user experience from content, then you have to invest much time to this website. This is the time which you could invest in your job or family, so for me it is OK to monetize.

prog

@Fastidious said:

I see no issues with the "European Cookie Bullshit" (I am from Europe, but as American as Lincoln now). It is intended to protect the user (any other hidden and ulterior purpose notwithstanding). It takes a second to make the notice disappear. More often than not, I simply ignore it and continue using the site as I was.

By why should we (website owners) use this shit? 99,99% will click on OK and not leave the website. That is not a real choice, it is a button which every new user or every user with incognito browser-modus has to click on.

Fastidious

@prog said:

By why should we (website owners) use this shit?

Simple answer? It is the law, deal with it.

prog

@Fastidious said:

@prog said:

By why should we (website owners) use this shit?

Simple answer? It is the law, deal with it.

Clear, but it is against user experience and it makes no sense to me.

drew

As this is an EU only issue and NodeBB is in the US, should this be a plugin request?

yariplus

@drew said:

As this is an EU only issue and NodeBB is in the US, should this be a plugin request?

*Canada

drew

@yariplus oops sorry!

a_5mith

Why does this need to be a plugin? Throw this code into a header widget and "furget abawt it".

<script type="text/javascript">
    window.cookieconsent_options = {"message":"This website uses cookies to ensure you get the best experience on our website","dismiss":"Got it!","learnMore":"More info","link":"http://example.com/cookie-policy","theme":"dark-top"};
</script>

<script type="text/javascript" src="//s3.amazonaws.com/cc.silktide.com/cookieconsent.latest.min.js"></script>

Hints: Replace dark-top with any of the following:

dark-floating
dark-bottom
light-top
light-bottom
light-floating

Floating will float it in from the bottom right corner. Bottom sets it at the bottom just above urgh "the fold"
Problem solved.

drew

@a_5mith
Amazing. So just this and the custom pages plugin and it's all good.

exodo

@a_5mith said:

Why does this need to be a plugin? Throw this code into a header widget and "furget abawt it".
<script type="text/javascript">
    window.cookieconsent_options = {"message":"This website uses cookies to ensure you get the best experience on our website","dismiss":"Got it!","learnMore":"More info","link":"http://example.com/cookie-policy","theme":"dark-top"};
</script>

<script type="text/javascript" src="//s3.amazonaws.com/cc.silktide.com/cookieconsent.latest.min.js"></script>
Hints: Replace dark-top with any of the following:

dark-floating

dark-bottom

light-top

light-bottom

light-floating

Floating will float it in from the bottom right corner. Bottom sets it at the bottom just above urgh "the fold"
Problem solved.

but you get his everytime?

drew

@exo.do Nope, the js library takes care of only showing it once until someone says "got it"

Henry Wright

I'm firmly in the "this is a stupid law" camp but as @Fastidious said earlier, it is what it is and we just have to deal with that.

@a_5mith Thanks for the snippet!

rfc2822

Personally, I think it's funny that all sites I know (including all large sites) show a "This site uses cookie. Accept or leave immediately" banner, but

they don't explain what the cookies do and why. "This site requires cookies to work" is surely not a clear and comprehensive explanation, and
most sites show this warning after cookies have been set (because it's technically much easier).

So these sites annoy their users and miss the goals of the directive (i.e. they're – in my humble opinion – not fulfilling the legal requirements), and so top even the "lawmakers who couldn't use a mouse".

julian

Are we just not allowed to store any cookie in any form containing any data without consent?

Because if so, NodeBB won't fly, because even just landing on any page, you will get a single cookie with express.sid value.

I've wanted to remove this for a long time (about a year now? When did @miksago last post...), because a forum with lots of anons will clutter the db with useless sess:* entries, which stay active for 14 days.

Easier said than done actually... need to rewrite how we save cookie data (that is... don't save any cookie data until a login session is started)...

HolyPhoenix

It's not just any cookie.

However, some cookies are exempt from this requirement. Consent is not required if the cookie is:
used for the sole purpose of carrying out the transmission of a communication, and
strictly necessary in order for the provider of an information society service explicitly required by the user to provide that service.
Cookies clearly exempt from consent according to the EU advisory body on data protection- WP29pdf include:
user‑input cookies (session-id) such as first‑party cookies to keep track of the user's input when filling online forms, shopping carts, etc., for the duration of a session or persistent cookies limited to a few hours in some cases
authentication cookies, to identify the user once he has logged in, for the duration of a session
user‑centric security cookies, used to detect authentication abuses, for a limited persistent duration
multimedia content player cookies, used to store technical data to play back video or audio content, for the duration of a session
load‑balancing cookies, for the duration of session
user‑interface customisation cookies such as language or font preferences, for the duration of a session (or slightly longer)
third‑party social plug‑in content‑sharing cookies, for logged‑in members of a social network.

a_5mith

@julian said:

Are we just not allowed to store any cookie in any form containing any data without consent?

Because if so, NodeBB won't fly, because even just landing on any page, you will get a single cookie with express.sid value.

I've wanted to remove this for a long time (about a year now? When did @miksago last post...), because a forum with lots of anons will clutter the db with useless sess:* entries, which stay active for 14 days.

Easier said than done actually... need to rewrite how we save cookie data (that is... don't save any cookie data until a login session is started)...

They allow some cookies because they can't think of an alternative method. Says it all about the EU cookie law. "You can't have cookies, except some."

drew

@julian said:

because a forum with lots of anons will clutter the db with useless sess:* entries, which stay active for 14 days.

Is that 14 days fixed by redis, or can it be configurable?

julian

Can be configured in the ACP, but 14 days is the default.

psychobunny