wanhose/cookie-dialog-monster
wanhose/cookie-dialog-monster
2
5
Fork 0
Code Issues 302 Pull Requests Releases 18 Wiki Activity

feat: enough github

Browse Source
This commit is contained in:
wanhose 2024-11-19 01:39:57 +01:00
parent 12a5d68e3c
commit d16f86cd32
2 changed files with 8 additions and 60 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
README.md
View File

@ -1,25 +1,7 @@
> AN IMPORTANT UPDATE
> <br><br>
> 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.
> <br><br>
> 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.
> <br><br>
> 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.
> <br><br>
> 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](https://git.wanhose.dev/wanhose/cookie-dialog-monster/src/branch/main/database.json) 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](https://choosealicense.com/licenses/mit/)
## Repositories
- [API](/wanhose/cookie-dialog-monster/src/branch/main/packages/api)
@ -34,3 +16,11 @@ Pull requests are welcome. For major changes, please open an issue first to disc
- [Pull requests](https://git.wanhose.dev/wanhose/cookie-dialog-monster/pulls)
- [Releases](https://git.wanhose.dev/wanhose/cookie-dialog-monster/releases)
- [Wiki](https://git.wanhose.dev/wanhose/cookie-dialog-monster/wiki/Help-or-issues%3F)
## Contributing
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.
## License
[MIT](https://choosealicense.com/licenses/mit/)

42
packages/web/src/index.html
View File

@ -40,48 +40,6 @@
</head>
<body>
<header>
<div class="bg-gray-300 text-secondary" role="banner">
<div class="max-w-5xl mx-auto p-4 text-justify" id="banner-content-preview">
<p class="font-semibold">AN IMPORTANT UPDATE</p>
<p class="mt-2">
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...&nbsp;
<span class="font-bold" id="banner-button" role="button" tabindex="0"> Read more </span>
</p>
</div>
<div class="hidden max-w-5xl mx-auto p-4 text-justify" id="banner-content-full">
<p class="font-semibold">AN IMPORTANT UPDATE</p>
<p class="mt-2">
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.
</p>
<p class="mt-2">
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.
</p>
<p class="mt-2">
We will no longer support platforms that overlook the contributions of our users and the
significant work invested over the last years. Once our GitHub account is reinstated, we
will set up a redirect to guide users to our new, self-hosted repository.
</p>
<p class="mt-2">
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.
</p>
</div>
</div>
<nav class="bg-secondary text-white">
<div class="flex items-center max-w-5xl mx-auto p-4">
<svg