[1]:https://github.com/system76/launch/blob/master/pcb/launch-pc...
809 karma · joined April 22, 2016
[1]:https://github.com/system76/launch/blob/master/pcb/launch-pc...
[1] https://www.cnil.fr/sites/default/files/atoms/files/draft_re...
Of course it takes into account the finality of the cookie (or any tracker for that matter).
* The proprietary cable. Seriously, in 2020..
* It does not support album cover in JPEG 2000. Seems like a detail, but if you like your library well organised, it can be a time sink !
EDIT: Thought about it, and if you only record the button click and does not identify the user, it works, and I am wrong! In general ePrivacy is very restrictive, only about access to terminal and not about personnal data ( and btw PII is not a GDPR thing, we say personnal data), but here it's ok! So yeah, no to me!
I must admit that does not quite fit with a lot of the thing I've read about Brave over the years.
But honestly this is a very minor point, if that's what is keeping you up at night, you are amongst the most compliant ones !
The goal is specifically to make the GDPR less daunting and more accessible! I guess it missed the mark.
But yeah, the GDPR has to formalize a lot of common sense practices, if you don't consider your user as "data trove" you want to abuse, you will be mostly ok!
This is covered here[1]
Basically:
* The right to object is not applicable if your processing is based on contract, legal obligation or protection of vital interest
* The right to erasure is not applicable in case of a legal obligation or public interest
[1]https://github.com/LINCnil/GDPR-Developer-Guide/blob/master/...
If you are a software architect, you need to ask yourself: can I delete a single user data across all my infra easily? If not, you might be in trouble a couple a year later when you are hit with thousands of deletion request and technically can't honor them.
Another side of tech debt I guess!
Getting a little off the computer was nice, plus this summer local bike touring will propably be the only option. Can't wait!
For exemple, as I said in another post, is explicitely allowed:
* Cookies for login/session
* Cookies for shopping carts
* Cookies for interface personnalisation (language, etc.)
* Cookies for load balancing
* Cookies to retain user choice regarding cookies
And quite a few other. So really you can run your website without consent notice if you care enough. One grey area is analytics, it varies amongst european DPAs. That I know of:
* In France it is allowed if you respect a few rules (no cross-processing, no localisation, etc..)
* In the UK, it is not per say allowed, but the ICO said they would not prosecute on those grounds.
I can't talk for other countries, but for France, the local DPA explicitely said so[0]!
Loose translation: "The analytics tool do not fit within the consent exemption when their provider reuse data for their own profit. That includes most big analytics service available (see for exemple Google Analytics confidentiality policy)"
[0]https://github.com/LINCnil/Guide-RGPD-du-developpeur/blob/ma...
This directive explicitely targets reading/writing into the user terminal without autorisation, hence the application to cookies.
Edit: removed a post, that was not explicative enough.
But the articulation is: ePrivacy says you need to consent to write non-essential trackers. GDPR defines how you can obtain the consent. So both laws take part in this ruling.
Explicitely allowed:
* Cookies for login/session
* Cookies for shopping carts
* Cookies for interface personnalisation (language, etc.)
* Cookies for load balancing
* Cookies to retain user choice regarding cookies
And quite a few other.
In general German eshop are the best (shopping from France).
So If they have data on you, that is older than a month, and did not contacted you to inform you of it, you can file a complaint!
[1]https://github.com/LINCnil/Guide-RGPD-du-developpeur/blob/ma... (In French sorry)
This is not an easy legal basis to rely on, and most of the time DPA are quite wary of processing relying on it!
Cookie banner are not directly related to the GDPR, but to the Eprivacy directive, which, not being a Regulation, is subject to variation in national law transcription. So the answer may vary depending on your country!
Still in an effort to have a uniform position on the question, DPAs( Data protection agency) are working at the EDPB (the European Data Protection Board, a sort of council of DPAs) to have a common position.
One of the currently shared position is that a cookie wall impedes the "free" part of the consent, since you have to support a negative consequence.
In a communication regarding the (future?) Eprivacy regulation, the EDPB clearly stated that:
"In order for consent to be freely given as required by the GDPR, access to services and functionalities must not be made conditional on theconsentof a userto the processing of personal data or the processing of information related to or processed by the terminal equipment of end-users, meaning that cookie walls should be explicitly prohibited." [1]
If I remember correctly the Austria DPA is not of favor of a cookie wall ban though..
From memory, not a legal advice!
EDIT: try to make the explanation clearer!
[1]: https://edpb.europa.eu/sites/edpb/files/files/file1/edpb_sta...
The best I could find for now is the EUMETSAT feed[1], but it is updated every hour and not as good as GOES-16 at night.
[1]: https://eumetview.eumetsat.int/static-images/MSG/RGB/NATURAL...
And regarding the option to set your preferences at the browser level, of course this is the best possible solution, but if you are following the ePrivacy reglement discussion, the article 10 (permitting browser to obtain consent for website with a standardized interface) is pretty close to getting killed.. Money talks.
It is true that the main limitation still is the construction code, which preserves the global proportion of the city.