Cookie accept form thing

[Pshepp]

Is your feature request related to a problem? Please describe. Pretty much some laws got passed and now sites need to ask about cookies. Just a better safe than sorry type of thing. Unsure if we really are even using cookies but I am assuming we will eventually need auth cookies

Quick blurb about the whole dealio: https://www.vox.com/recode/2019/12/10/18656519/what-are-cookies-website-tracking-gdpr-privacy

Describe the solution you'd like Basically what docker docs has (https://docs.docker.com/) is the footer banner which when selected pops up some quick prompts about a cookie

Describe alternatives you've considered None really, all sites do this now including stack exchange etc. I hate it cause it feels intrusive so lets keep that in mind during the design stage.

Additional context Maybe make the bar that would hold the "dark/light" theme a bit larger until the user selects an option for cookies and a simple close button to just remove them. Hopefully this makes sense

[danwentworthart]

@Dan

• this is not supreme priority, but would help a lot. It should be possible to capture someone's IP address in the javascript and send it back. We should for sure ensure that we get permission and that we don't if not. It would be nice to capture the IP address of anyone who makes any sort of request aside from "show me this page". For example, any time someone clicks "Done" or "Build selected". @Dave
• this could also go for glyfinder. And, then keep a little database of date, time, IP Address, app/page/whatever, action (e.g., 'done' or 'download'). If the action is download, also keep info about what. In the "accept cookies/tracking" notice that we need anyway, say we need this info for reports to grant agencies and "click here for more info". And, pester someone to write the 'more info".

[cexum]

Design meeting needed.

[Pshepp]

I think we spoke about this a bit, but luckily it is already done for the most part if we look at any site that has the form. Hell, we can just take inspo from stack overflows implementation of this but lets keep tracking cookies to a minimum because i think everyone cant stand it when there are a gazillion trackers for a single site and having to disable em all

[danwentworthart]

I believe that if we only track cookies that indicate things like "project id" guids, that we need not ask permission. My interpretation is that so long as we keep personal identifiable info out of the cookies, which we do, we can skip it. I also see this as a feature to the user, because asking permission unnecessarily is a hassle too.