Todo list

[OhMyGuus]

Todo

• [x] Update manifest version from V2 to V3 & test
• [x] Write installation guides (chrome & Firefox are written)
• [x] Decide on the name & logo changes to make it clear that it's a non-Avast version in the ff store. (Was thinking of I Don't Care About Cookies (debloated) or something like that but not sure what ff & chrome allowed)
• [x] Publish on Mozilla & chrome webstore if allowed
• [x] Issue template for report a website
• [ ] Support for Pale Moon
• [ ] Rewrite & cleanup this mess

(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 👍

[winskil]

Installing the extension on Firefox: Download the .xpi from releases Type about:addons into the URL bar Click the gear wheel icon and click Install Add-on From File... Locate the corresponding .xpi file Install the extension by clicking Add

Firefox may try to install it straight away when you download it, in which case just click Continue to Installation

[Mystqr4]

Maybe the correct name should be "I don't care about Cookies or Avast" hahaha Just kidding but some sort on name and logo change would be great.

Bring back the additional options to "report a cookie warning" and also an option to "disable extension on _____ website here_____.com"

[OhMyGuus]

Maybe the correct name should be "I don't care about Cookies or Avast" hahaha Just kidding but some sort on name and logo change would be great.

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

[winskil]

You're welcome! I have a Chrome tutorial ready as well, but it still has the Manifest version 2 is deprecated, and support will be removed in 2023. warning so I will add it here when it's fixed (currently looking through the V3 migration docs)

[winskil]

Adding this anyway. Added a disclaimer about the errors to the bottom.

Installing the extension on Chrome

Download the .zip from releases

Type chrome://extensions into the URL bar Enable developer mode Drag the .zip to the extensions page

You may notice that the extension has errors. Why?

Chrome stops supporting Manifest V2 in 2023 (which the extension currently uses). This will be fixed in the future release so for now you can ignore it.

[maricn]

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...

[Mystqr4]

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.

[winskil]

@maricn Copied this from the original site In most cases, it just blocks or hides cookie related pop-ups. When it's needed for the website to work properly, it will automatically accept the cookie policy for you (sometimes it will accept all and sometimes only necessary cookie categories, depending on what's easier to do). It doesn't delete cookies.

[maricn]

@maricn Copied this from the original site In most cases, it just blocks or hides cookie related pop-ups. When it's needed for the website to work properly, it will automatically accept the cookie policy for you (sometimes it will accept all and sometimes only necessary cookie categories, depending on what's easier to do). It doesn't delete cookies.

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. :)

[ikanakova]

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.

[DamianGuth]

@maricn Copied this from the original site In most cases, it just blocks or hides cookie related pop-ups. When it's needed for the website to work properly, it will automatically accept the cookie policy for you (sometimes it will accept all and sometimes only necessary cookie categories, depending on what's easier to do). It doesn't delete cookies.

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.

[osdiab]

IDGAF About Cookies

[mll0]

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. :)

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. So maybe the present fork of IDCAC, associated with some cookie mangement addon I have yet to find, would be the right choice.

[holdit]

A mix of Consent-O-Matic and I don't care about cookies would be perfect. The extension could:

1. Try to uncheck all permissions and then submit the form (like Consent-O-Matic does).
2. When the above isn't possible (eg: if the extension doesn't support the popup), deny/reject all cookies.
3. If it's not possible to reject all, then accept them so the popup goes away.

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.

[maricn]

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..

[ghost]

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.

[appeasementPolitik]

About the rewrite and cleanup, I think it might be useful to rename common6.js, common3.js, common5.js to something like 6_cookies.js, 3_localstorage.js, 5_mouseclick.js to make it easier to locate the proper file to edit.

[OhMyGuus]

About the rewrite and cleanup, I think it might be useful to rename common6.js, common3.js, common5.js to something like 6_cookies.js, 3_localstorage.js, 5_mouseclick.js to make it easier to locate the proper file to edit.

That's indeed a good idea :)

[appeasementPolitik]

After looking at the part that loads the common(n).js files, (line 476 of context-menu.js) it looks like renaming the files to a better name is not possible, as the executeScript function needs a full file name to load. There could be something like an index with the numbers that belong to the file names in order to fix it, but this looks too complex. Maybe something like a contributors guide which explains what each file does is a better idea.

[OhMyGuus]

After looking at the part that loads the common(n).js files, (line 476 of context-menu.js) it looks like renaming the files to a better name is not possible, as the executeScript function needs a full file name to load. There could be something like an index with the numbers that belong to the file names in order to fix it, but this looks too complex. Maybe something like a contributors guide which explains what each file does is a better idea.

Did already some things u suggested in #223 , will create a guide as well this week 😄 Planning to do some more changes later as well like fixing the duplicated blockrules (manifestv2 & manifestv3 )

[appeasementPolitik]

Looks good 👍, much cleaner

[appeasementPolitik]

In rules.js, in the blockUrls part, there are a lot of q: false and e: false. Maybe there's a way to set false as the default value for q and e so that they can be removed?

Edit: done

[Deedikjupijn]

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.

[nicolaasjan]

Request: Provide a link to a Manifest v2 .crx file on Releases while Google still permits them.

Reason: Manifest v3 version is still somewhat slow and buggy.

[appeasementPolitik]

Another way to optimize rules, maybe it's possible to automatically append !important to css rules, as it's always the case anyway

[appeasementPolitik]

Also, code starting from 250 and line 284 in background.js is duplicate code, it might be possible to make a function for it

[appeasementPolitik]

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

[ghost]

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.

[appeasementPolitik]

Another idea, linking duplicate issues together:

https://github.com/OhMyGuus/I-Still-Dont-Care-About-Cookies/issues/1027#issuecomment-1341651294

[appeasementPolitik]

I think common.css could also be extended to allow rules like body.modal-open{overflow:unset !important}, which is a rule that would solve a lot of issues instantly, and also completely removes the need for commons rule 14. It should not break any websites, but if it does maybe a website blacklist could be implemented for these rules as well, as the likelyhood of this rule breaking a website seems a lot lower compared to the amount of websites it could fix.