-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Todo list #7
Comments
Maybe the correct name should be "I don't care about Cookies or Avast" hahaha Bring back the additional options to "report a cookie warning" and also an option to "disable extension on _____ website here_____.com" |
Hahahaha love that name Oh and thanks for the notify about the report & disable will fix that indeed :) winskil Thanks a lot for the tutorial and I placed it on the wiki with credits of course |
You're welcome! I have a Chrome tutorial ready as well, but it still has the |
Maybe a question here (and a statement), coming from someone who cares about cookies - cares to have the least of them tracking cookies used. Is this extension just plainly going the "Accept All Cookies" route or it attempts to "Reject All Cookies" (or do its best to achieve minimum cookies stored)? I always found the "I don't care" part confusing - does the extension just do whatever is necessary to remove the banner/pop-up? If it does its best to minimize the amount of cookies used, I'd be welcoming altogether new name, such as "Cookie? No, thank you!", "Cookie rejecter", "Reject All Cookies" or whatever pun you can think of in that direction... |
One thing that is probably more important and easily fixed is the details on the extension in Firefox such as the author which still displays "Daniel Kladnik @ kiboke studio" as well as the version numbering would be great if it were somewhat different I guess. |
@maricn Copied this from the original site |
Thank you for sharing that quote. I remember it well, and was repeatedly sorry for the (afaik) lack of public issue tracker and open source nature of the project to address it. Unless the website is in breach of ePrivacy, GDPR and/or other local regulations (which btw you may assume exactly all of them are, just a matter of extent; however let's assume they're not) - they shouldn't store any cookies that are strictly not necessary. That means just killing a pop-up should be enough to stop the website from storing any tracking cookies. What I hope can be improved in a fork of the original project (perhaps over time, not immediately) is to avoid accepting all cookies. Instead of doing "what's easier", go the hard way for improving user privacy. That's just my dream, I felt this could be a good moment to share it, but I don't promise involvement in developing the extension, so please feel free to ignore my POV. :) |
As for the name, I think we shouldn't stick to the original one, because I don't care about cookies can evoke that we don't care if we allow all cookies and let be snooped on. |
In my experience the extension mostly accepted all cookies. I think (if wanted) we can improve on that while (or after) cleaning up the original code. |
IDGAF About Cookies |
Agreed. It seems it's the path taken by Consent-O-Matic, but after a few hours of surf, many cookie popups are still visible. |
A mix of Consent-O-Matic and I don't care about cookies would be perfect. The extension could:
Since some users wouldn't like the option to accept cookies, a setting could be added to disable these "fallbacks", giving the user the chance to leave the site without accepting any cookies. |
jsyk according to the latest rulings (at least per GDPR and ePrivacy) websites shouldn't make it any harder for the user to reject than to accept non essential cookies.. also by default they should be unchecked.. ofc that doesn't mean there will be no websites in violation and/or transition to that behavior.. |
A LOT of sites only display the accept all button and options, where everything is checked by default. |
About the rewrite and cleanup, I think it might be useful to rename |
That's indeed a good idea :) |
After looking at the part that loads the |
Did already some things u suggested in #223 , will create a guide as well this week 😄 |
Looks good 👍, much cleaner |
* Added support for education.lego.com fixes #224 * Added support for bonobology.com fixes #241 * Added support for bodypak.pl fixes #242 * Added support for moebelix.at/sk/cz/de fixes #245 * Added support for beurer.se fixes #249 * Added support for arsys.es fixes #250 * Added support for swb-busundbahn.de fixes #251 * Added support for uni-mozarteum.at fixes #247
In Edit: done |
It would be really nice if you could set the addon (in some kind of settings tab because I think some people maybe don't want it) to display one pop up with it asking to keep the banner and let you answer it or remove the entire banner (with the information displayed about if it will accept or reject the cookies). so like a popup that has 2 buttons first one: Remove cookies banner and accept (or reject in the cases that would be possible) cookies. 2nd button will be: leave banner open and choose yourself. |
Request: Reason: |
Another way to optimize rules, maybe it's possible to automatically append !important to css rules, as it's always the case anyway |
Also, code starting from 250 and line 284 in |
Another idea, add issue tags for the used browser, so people that want to make rules for a specific browser can easily see what issue they have to click (could also automatically tag for mobile) Edit: automatic NSFW tagging could also be possible by looking up the domain name on a list |
Yandex's or NextDNS's database could be used. Or, alternatively, any anti-NSFW uBlock filter. |
Another idea, linking duplicate issues together: |
I think |
|
What I miss is that the pop-up report don't remembers the entry text - if something closes it, I lose the text. Apparently in Firefox, maybe opening in the sidebar will work: https://addons.mozilla.org/en-US/firefox/addon/open_in_sidebar/ |
Is there any progress on the Pale moon version for this. I find Basilisk and Pale moon are making some nice progress of late and it would be nice to have this extension for those browsers. Has there been any progress on the Rewrite. I know both of these tasks are huge and would like to know if you are okay with everything. Sadly I do not have any skills to add to this project so I hope you are getting some sort of support with this. |
Added support for prenatal.nl
Todo
(Was thinking of I Don't Care About Cookies (debloated) or something like that but not sure what ff & chrome allowed)
(This is just the initial todo list after this I need to create the maintain todo list)
If someone has suggestions or things like that this is the place 👍
The text was updated successfully, but these errors were encountered: