Did someone say cookie consent dialogs? 😋 https://www.cookie-dialog-monster.com
Go to file
2024-10-15 11:52:09 +02:00
.gitea feat: migrate to git.wanhose.dev 2024-10-13 11:11:31 +02:00
.husky refactor(packages): migrate to yarn workspaces 2022-05-05 17:19:35 +02:00
.vscode fix(packages): some bugs from last migration 2022-05-05 20:11:43 +02:00
.yarn chore: upgrade deps 2024-05-04 14:21:50 +02:00
packages fix(browser-extension): report cancel button clickable area 2024-10-15 11:52:09 +02:00
.commitlintrc fix(rules): issue #672 2024-08-04 12:29:16 +02:00
.gitignore feat(browser-extension): add declarativeNetRequest to block cmp.inmobi.com 2024-05-27 09:50:05 +02:00
.lintstagedrc chore: upgrade deps 2024-02-16 09:23:26 +01:00
.minify.json chore(web): move globally and update minify config 2022-05-24 23:55:26 +02:00
.prettierignore feat(browser-extension): add declarativeNetRequest to block cmp.inmobi.com 2024-05-27 09:50:05 +02:00
.prettierrc chore: set print width to 100 2022-05-06 12:20:41 +02:00
.yarnrc.yml chore: upgrade deps 2024-05-04 14:21:50 +02:00
database.json fix(database): issue #1034 2024-10-07 13:21:35 +02:00
LICENSE refactor: move licenses up 2024-10-15 11:51:07 +02:00
package.json refactor: move licenses up 2024-10-15 11:51:07 +02:00
README.md refactor: move licenses up 2024-10-15 11:51:07 +02:00
yarn.lock feat: migrate to git.wanhose.dev 2024-10-13 11:11:31 +02:00

AN IMPORTANT UPDATE

On the morning of October 11, 2024, GitHub unexpectedly hid our repository without any prior notification. This sudden action immediately disrupted all of our API services, as they relied on files from the repository that were no longer accessible. Our team reached out to GitHub support to understand the situation, but we have not yet received any response. Given the critical impact on our services and the lack of communication from GitHub, we decided to migrate the entire repository to an alternative platform to ensure continuity and reliability.

We initially migrated the repository, releases, and open issues (excluding discussions) to GitLab. However, during the migration of issues, GitLab's own spam detection mechanism mistakenly identified its bot activity as spam, leading to our issues being hidden. Despite reaching out to GitLab support, we have not yet received a resolution for this incident. Faced with these ongoing platform limitations and communication delays, we have opted to move forward with self-hosting our own Git system using Gitea to ensure full control over our repository and services.

We will no longer support platforms that overlook the contributions of our users and the significant work invested over the last five years. Once our GitHub account is reinstated, we will set up a redirect to guide users to our new, self-hosted repository.

Thank you to our community for your patience. Your contributions remain vital to this project, and we are committed to ensuring its stability and growth in a more secure environment.

Cookie Dialog Monster

Cookie Dialog Monster is a browser extension that hides cookie consent dialogs without changing user preferences. By default, we do NOT accept cookies (except in a few cases where the pages do not function without accepting them). You can report broken sites with a single click, which will create an issue in this repository to be fixed promptly.

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

License

MIT

Repositories

Resources