Skip to content
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

Sorry for the inactivity and for not maintaining it as well as promised. #10278

Open
OhMyGuus opened this issue Dec 13, 2023 · 46 comments
Open
Labels

Comments

@OhMyGuus
Copy link
Owner

OhMyGuus commented Dec 13, 2023

Sorry all for the inactivity, and not maintaining it as well as promised.

I have been working on my studies for the past few months, which are now in the final stage, meaning you have to follow an internship, and about 60+ hours a week have gone into this.
Sadly, this meant that I didn't have the energy to work on this project. Now, there is a spark of hope; my studies will most likely conclude successfully on January 16th. After that, I will have six weeks of holiday to bring this project and my other projects back on track, and following that period, I will have time alongside work to continue on this and my other projects.

If there are big sites not working, just @OhMyGuus and then I will get a notification on my phone and then I can still work on it.
I will also test and merge all the PR's that are currently open and do a release today/tomorrow.

If there are any questions or things put it here or you can always contact me on discord: thaguus

Just a note: reporting websites is down for a couple of hours going to remove the dupes + add a dupe check.

@azgaresncf
Copy link
Contributor

azgaresncf commented Dec 13, 2023

Sorry all for the inactivity, and not maintaining it as well as promised.

I have been working on my studies for the past few months, which are now in the final stage, meaning you have to follow an internship, and about 60+ hours a week have gone into this. Sadly, this meant that I didn't have the energy to work on this project. Now, there is a spark of hope; my studies will most likely conclude successfully on January 16th. After that, I will have six weeks of holiday to bring this project and my other projects back on track, and following that period, I will have time alongside work to continue on this and my other projects.

If there are big sites not working, just @OhMyGuus and then I will get a notification on my phone and then I can still work on it. I will also test and merge all the PR's that are currently open and do a release today/tomorrow.

If there are any questions or things put it here or you can always contact me on discord: thaguus

Just a note: reporting websites is down for a couple of hours going to remove the dupes + add a dupe check.

Thank you very much for your answer!
Don't worry at all! We we're just worried about why you haven't made any commits since so long.

Just do the dupe check, and then we will do the work for you ;)

Continue to work on your final stage, it is important

We can also talk about it on Discord if you want to: azgaresncf.

And finally, @OhMyGuus, your plugin is very cool! ;)
I'm sure that we can maintain it!

@obfuscated-loop
Copy link
Collaborator

Thank you for the update; I figured you were probably busy with education or something similar. Good stuff on keeping the project alive and kicking! I will continue to make PRs in the future. Take care 👍

@appeasementPolitik
Copy link
Contributor

Welcome back!

@ThomasFrans
Copy link

Thank you for this extension. It makes the web just a little bit more bearable these days. It's incredible that people manage to keep these projects alive for such a long time. I can't imagine how much work and dedication it requires.

@useronegit
Copy link

useronegit commented Apr 26, 2024

Any new news on that? Is still updated?

@dreirund
Copy link

If there are big sites not working, just @OhMyGuus and then I will get a notification on my phone and then I can still work on it.

Has been done already e.g. here.

Regards and thanks for the project!!

@ghost
Copy link

ghost commented Jun 2, 2024

People never like to hear the truth. Those who read it. Deal with it.

@azgaresncf
Copy link
Contributor

People never like to hear the truth. Those who read it. Deal with it.

Why did you have deleted the message?

@ghost
Copy link

ghost commented Jun 3, 2024

People never like to hear the truth. Those who read it. Deal with it.

Why did you have deleted the message?

Well, getting thumbs down from people who want to wait for eternity instead of taking action, if you want to know the whole story with "advanced content" PM me.

Cheers

I am not here to be taken as a fool, which i am not. thats why i deleted plus let the people who reacted onto it be however they are. ignorant, sort of selfish, religious behaviour, and so on and so forth. :-)

@BlackDragonBE
Copy link

BlackDragonBE commented Jun 4, 2024

@ONE11111111ONE So what's your proposed action? Fork this project? Because it doesn't seem you've created a fork.

EDIT: Also, the creator seems to be active, as is evident from the issues he's fixing.

@ghost
Copy link

ghost commented Jun 4, 2024

Some fanatic with a good heart, good intention and time should do it, since i am 0% programmer. If he has the spirit others will want to be part of it. I will not fork this project.

According your edit. Well, then at least i am curious whats gonna happen...

@dreirund
Copy link

dreirund commented Jun 4, 2024 via email

@ghost
Copy link

ghost commented Jun 4, 2024

Yet, we all know things right. Like seeing that nothing is private here on m$ github like as you posted. I see and know things, which cannot be taken away. If people would know how much power 1 single person has, you guys would just do something about the situation. :-)

@M1Aston
Copy link

M1Aston commented Jun 5, 2024

So, development of this extension is very slow. Reported websites from months ago are not added anymore. What would be a good alternative? ublock with cookie lists or a browser extension like Consent-O-Matic?

@ghost
Copy link

ghost commented Jun 5, 2024

OK, i am out of this.

@BlackDragonBE
Copy link

@OhMyGuus
I think the best course of action is to allow more people to solve pull requests and existing issues. I appreciate your work, but I think it's too much for a single person to keep up with.
A good way to get more contributions is writing a guide in the wiki on the workflow to add more sites. I looked at the code, but it's not clear to me at first glance how it works.

By making this a group effort, it will be more realistic to get through the ever-growing list of issues.

Finally, I think people here that are complaining without any technical skills are being way too entitled. If you never wrote a line of code in your life or had to juggle a project like this and your personal life, your contribution to the discussion isn't worth much. You can blabber on about power and knowledge all day, but in the end you are just making noise if you don't tie that to concrete actions.

@Paradoxum
Copy link

@OhMyGuus I think the best course of action is to allow more people to solve pull requests and existing issues. I appreciate your work, but I think it's too much for a single person to keep up with. A good way to get more contributions is writing a guide in the wiki on the workflow to add more sites. I looked at the code, but it's not clear to me at first glance how it works.

By making this a group effort, it will be more realistic to get through the ever-growing list of issues.

Finally, I think people here that are complaining without any technical skills are being way too entitled. If you never wrote a line of code in your life or had to juggle a project like this and your personal life, your contribution to the discussion isn't worth much. You can blabber on about power and knowledge all day, but in the end you are just making noise if you don't tie that to concrete actions.

Came here looking for info on why i'm seeing cookies everywhere again, it's crazy to me that there are no alternatives or that nobody else has forked it by now since literally everyone that uses a browser in the eu is going to suffer cookie popups everywhere, you'd think more people would be doing something right? I dunno just seems odd to me. Glad we at least have something though.

@ChuckMichael
Copy link

(...) What would be a good alternative? (...)

Cookie Dialog Monster

@ghost
Copy link

ghost commented Jun 14, 2024

Since its all controlled by the AI MS uses... I cannot talk openly.

I cannot program but i can give solutions, like making an e.V. and then organization out it and then get money from sponsors e.V. members and specific ppl... if one needs money as an vehicle to build up the Nr. 1 wordwide cookie (blocker or minimal acceptor). Dragon and so forth. Well i have solutions then... i just need the right people around. Like gorhill from ublock origin. He drives for it all time and is sorrounded by good ppl he can relay on.

Man i had ppl during the last days where they went nuts, because isdcac killed the website and it all goes back to the person who gives the recommendation. In the end it goes all back to guus. End of the Story. He gets the credits or debts. And me as well. F... this discord thing. Lets meet on efnet e.g. channel isdcac. I open it tomorrow evening as first step. If anyone is interested into it...feel free to join. I got idieas over the days. Cheers

@BlackDragonBE
Copy link

@ONE11111111ONE If you don't have programming or organization skills, you're contributing nothing.

image

You said this one week ago. Make up your mind.
You keep complaining about AI, but I had chats with LLMs that were way more coherent than whatever word soup you're spitting out here.

@ghost
Copy link

ghost commented Jun 14, 2024

I am not talking about programming, there i am out of it, yet i offer solutions for european, at best german programmers. Cheers

Your nickname also btw shows your subconcsious belongings, and i deal with it and dont give a f.

Fly back to the deep hole where you re coming from. Make the earth free from this stupid beings.

@obfuscated-loop
Copy link
Collaborator

Stop arguing bruddas,

there is too much hatred and whining about life, and I say that, not to sound demeaning, but because we have all done the same in the past. I may fork this project, I tried speaking to Gus etc but he has stuff going on in his life I'm pretty sure and is prolly busy. I may ask to be a maintainer of the repo and to continue development.

@ONE11111111ONE You are funny bro but please stop now, I do get your frustration really but dont take it out on us, we're trying our best and all contributing to fight this proprietary software, in our own ways.

If there are any other possible maintainers, help would be appreciated but not expected. Open source has always been a voluntary team effort, it is not expected.

@dreirund
Copy link

dreirund commented Jul 7, 2024

I now switch to "Cookie Dialog Monster", since it is maintained, and finally got an up to date permanent firefox addon (read here or/and here).

@M1Aston
Copy link

M1Aston commented Jul 7, 2024

I now switch to "Cookie Dialog Monster", since it is maintained, and finally got an up to date permanent firefox addon (read here or/and here).

Great news. I'm gonna install it right now. :-)

@dreirund
Copy link

dreirund commented Oct 11, 2024

I now switch to "Cookie Dialog Monster", since it is maintained, and finally got an up to date permanent firefox addon (read here or/and here).

Great news. I'm gonna install it right now. :-)

Does anyone know what happend to @wanhose and the addon?

https://github.com/wanhose just gives a HTTP error 404 now.

Now I am trying out "Consent-O-Matic".

@cremor
Copy link

cremor commented Oct 11, 2024

@dreirund I don't know why, but it is now on GitLab: https://gitlab.com/wanhose/cookie-dialog-monster
I found it via the website https://www.cookie-dialog-monster.com/

@dreirund
Copy link

@dreirund I don't know why, but it is now on GitLab: https://gitlab.com/wanhose/cookie-dialog-monster

According to the maintainer this is the reason:

On the morning of October 11, 2024, GitHub unexpectedly hid our repository without any 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, unfortunately, we did not receive any response yet. Given the critical impact on our services and the lack of communication from GitHub, we made the decision to migrate the entire repository to a more reliable platform.

We are pleased to announce that the repository has now been successfully migrated, along with all releases and open issues (excluding discussions), to GitLab. This migration required a significant initial refactor of our systems and code to ensure continuity across all of our services, but it was necessary to protect the integrity and accessibility of the project moving forward.

We will no longer support platforms that disregard the contributions of our users and the work invested over the last five years. Once our GitHub account is reinstated, we will set up a redirect to guide users to this new home on GitLab.

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.

Regards!

@dreirund
Copy link

dreirund commented Oct 13, 2024

but it is now on GitLab: https://gitlab.com/wanhose/cookie-dialog-monster

And now moved to a self-hosted service:

As updated in our README.md:

This repository has been moved to a self-hosted alternative due to several technical issues with GitLab.

Starting on the morning of October 12, 2024, we experienced persistent disruptions with GitLab's service, including critical functionality being blocked which is unacceptable.

To ensure reliable and uninterrupted service, we've migrated this project to a new repository.

Please update your bookmarks. Thank you for your understanding and continued support!

This is yet another attempt to bring down this project, but honestly, I'm too stubborn to let that happen. I've taken some drastic steps to keep things going, like setting up my own self-hosted platform to deploy all my projects from now on. I'm done relying on providers who might be next in line to mess with us.

Thank you for your patience through all of this. I know the downtime and disruptions have been frustrating (and they're out of my control) but I've done everything I can to get this sorted quickly. You have no idea how hard I've worked the past few days to keep everything up and running, even with all the insane issues these Git providers keep throwing at me.

Thanks again for sticking with me through this chaos!

I wonder a bit if @wanhose is doing some "evil" stuff in the background which makes them blocked, or if it is really the git service providers that are shitty to trust on. (I easily believe the latter, but questions about the former comes into my mind. Has anyone reviewed the code behind "Cookie Dialog Monster", that it is not "phoning home"?)

Regards!

@cremor
Copy link

cremor commented Oct 13, 2024

The GitLab problems are explained in the new readme on https://git.wanhose.dev/wanhose/cookie-dialog-monster

About possibly doing "evil" stuff: Around October 4th there was a weird issue with the extension where all YouTube page loads were redirected to a specific video and the channel of that video was automatically subscribed. That was resolved with addon version 7.3.1, but someone might have reported it for being malicious because of that.

I do not know if the extension actually does something malicious or if this was just a very weird bug.

@d4k0
Copy link

d4k0 commented Oct 14, 2024

About possibly doing "evil" stuff: Around October 4th there was a weird issue with the extension where all YouTube page loads were redirected to a specific video and the channel of that video was automatically subscribed. That was resolved with addon version 7.3.1, but someone might have reported it for being malicious because of that.

This is far too specific to be just a bug ...

@dreirund
Copy link

dreirund commented Oct 14, 2024 via email

@dreirund
Copy link

About possibly doing "evil" stuff: Around October 4th there was a weird issue with the extension where all YouTube page loads were redirected to a specific video and the channel of that video was automatically subscribed. That was resolved with addon version 7.3.1, but someone might have reported it for being malicious because of that.

This is far too specific to be just a bug ...

I suggest to discuss "Cookie Dialog Monster"-related stuff over here at it's current repository so that the author can be included.

@cremor
Copy link

cremor commented Oct 18, 2024

I suggest to discuss "Cookie Dialog Monster"-related stuff over here at it's current repository so that the author can be included.

I agree, and for anyone reading this I'd like to point them to the official answer to all this "possible evil stuff" from the addon author: https://git.wanhose.dev/wanhose/cookie-dialog-monster/issues/138#issuecomment-415

@ColourGrey
Copy link

@dreirund, @cremor: So far, the "Cookie dialog monster" developer(s) got into conflict with Firefox (their extension is no longer published on the FF addons site), with Github and with Gitlab. I would stay away from this project, I find it extremely suspicious.

@dreirund
Copy link

dreirund commented Oct 22, 2024 via email

@d4k0
Copy link

d4k0 commented Oct 22, 2024

On Tue, 22 Oct 2024 10:16:44 -0700, ColourGrey @.***> wrote: got into conflict with Firefox (their extension is no longer published on the FF addons site),
It is, I just found it via their search function: https://addons.mozilla.org/en-US/firefox/addon/cookie-dialog-monster/?utm_source=addons.mozilla.org&utm_medium=referral&utm_content=search

This is a very very old version from 2022 that hardly works properly today. I also don't understand why he in particular has any issues with Mozilla as there are a few other addons with similar functionality there. He doesn't even seem to be trying to get the extension onto the official addon page anymore. Instead, he wants you to download the XPI file from his self-hosted repository.

@dreirund
Copy link

dreirund commented Oct 22, 2024 via email

@d4k0
Copy link

d4k0 commented Oct 22, 2024

So why doesn't he just create a new account at Mozilla? Why is he so careless with his two-factor authentications, especially as a developer (I'm a software developer myself)? Anyone who does anything with IT knows how important these are and that you have to store them securely.

@dreirund
Copy link

Why is he so careless with his two-factor authentications, especially as a developer

Without judging the content of your statement, "carelessness" is something different as doing something evil (which is conscious).

So far, the "Cookie dialog monster" developer(s) got into conflict with [&ldots] Gitlab.

About Gitlab, they stated that the issue just was that, when they mass-imported the GitHub issues to GitLab to have them available there, GitLab's spam detection mechanism did think the issues where spam and did hide them. So, if this is correct, it is not getting into conflict with GitLab but just beeing upset by unwanted automatisms of GitLab. And this gave the impulse for the authors to not rely anymore on third party services.

@azgaresncf
Copy link
Contributor

azgaresncf commented Nov 6, 2024

On Tue, 04 Jun 2024 09:58:39 -0700, existence @.***> wrote: i am 0% programmer
Me neither.

It's pretty hard to completely maintain it, especially when you have 8000+ issues to check :/

For example, I can put from 10 seconds to 5 or even 10 minutes for the most sophisticated-techniques to make ONE rule. Sometimes, you have to read through some deliberately obfuscated code, and it can be pretty tough for some people.

Multiply this by 8000 (including duplicated issues and so on...), and that's why it's not easy to maintain.

@ColourGrey
Copy link

ColourGrey commented Nov 6, 2024

It's pretty hard to completely maintain it, especially when you have 8000+ issues to check :/

@azgaresncf: Have you ever asked about how this extension got to 8000+ issues? This happened because the maintainer has stopped working on it for about 10 months already.

The best strategy would be for the maintainer to freeze this project, thus sending a strong message to the community of its users to fork it or move elsewhere. Until this happens the users will still cling to the faintest hope of resurrection, and not be motivated to use something else.

I totally understand that one's life might get more involved, and that one may no longer have time for small side projects like this one. But then, why not announce this publicly and pass stewardship to someone else, or merge the project with another one? This would be the only ethical approach.

@dreirund
Copy link

dreirund commented Nov 6, 2024

to fork it or move elsewhere.

There are a few forks, e.g. this one which got updates.

@OhMyGuus, yes, maybe:

I totally understand that one's life might get more involved, and that one may no longer have time for small side projects like this one. But then, why not announce this publicly [...] The best strategy would be for the maintainer to freeze this project

archive this?

Regards!

@azgaresncf
Copy link
Contributor

azgaresncf commented Nov 7, 2024

to fork it or move elsewhere.

There are a few forks, e.g. this one which got updates.

@OhMyGuus, yes, maybe:

I totally understand that one's life might get more involved, and that one may no longer have time for small side projects like this one. But then, why not announce this publicly [...] The best strategy would be for the maintainer to freeze this project

archive this?

Regards!

I'm also trying to do my best as soon as I can to fix some websites
(I'm editing rules locally for the moment)

@wanhose
Copy link

wanhose commented Nov 11, 2024

I now switch to "Cookie Dialog Monster", since it is maintained, and finally got an up to date permanent firefox addon (read here or/and here).

Great news. I'm gonna install it right now. :-)

Does anyone know what happend to @wanhose and the addon?

https://github.com/wanhose just gives a HTTP error 404 now.

Now I am trying out "Consent-O-Matic".

@dreirund I don't know why, but it is now on GitLab: https://gitlab.com/wanhose/cookie-dialog-monster I found it via the website https://www.cookie-dialog-monster.com/

@dreirund I don't know why, but it is now on GitLab: https://gitlab.com/wanhose/cookie-dialog-monster

According to the maintainer this is the reason:

On the morning of October 11, 2024, GitHub unexpectedly hid our repository without any 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, unfortunately, we did not receive any response yet. Given the critical impact on our services and the lack of communication from GitHub, we made the decision to migrate the entire repository to a more reliable platform.
We are pleased to announce that the repository has now been successfully migrated, along with all releases and open issues (excluding discussions), to GitLab. This migration required a significant initial refactor of our systems and code to ensure continuity across all of our services, but it was necessary to protect the integrity and accessibility of the project moving forward.
We will no longer support platforms that disregard the contributions of our users and the work invested over the last five years. Once our GitHub account is reinstated, we will set up a redirect to guide users to this new home on GitLab.
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.

Regards!

but it is now on GitLab: https://gitlab.com/wanhose/cookie-dialog-monster

And now moved to a self-hosted service:

As updated in our README.md:

This repository has been moved to a self-hosted alternative due to several technical issues with GitLab.
Starting on the morning of October 12, 2024, we experienced persistent disruptions with GitLab's service, including critical functionality being blocked which is unacceptable.
To ensure reliable and uninterrupted service, we've migrated this project to a new repository.
Please update your bookmarks. Thank you for your understanding and continued support!

This is yet another attempt to bring down this project, but honestly, I'm too stubborn to let that happen. I've taken some drastic steps to keep things going, like setting up my own self-hosted platform to deploy all my projects from now on. I'm done relying on providers who might be next in line to mess with us.
Thank you for your patience through all of this. I know the downtime and disruptions have been frustrating (and they're out of my control) but I've done everything I can to get this sorted quickly. You have no idea how hard I've worked the past few days to keep everything up and running, even with all the insane issues these Git providers keep throwing at me.
Thanks again for sticking with me through this chaos!

I wonder a bit if @wanhose is doing some "evil" stuff in the background which makes them blocked, or if it is really the git service providers that are shitty to trust on. (I easily believe the latter, but questions about the former comes into my mind. Has anyone reviewed the code behind "Cookie Dialog Monster", that it is not "phoning home"?)

Regards!

The GitLab problems are explained in the new readme on https://git.wanhose.dev/wanhose/cookie-dialog-monster

About possibly doing "evil" stuff: Around October 4th there was a weird issue with the extension where all YouTube page loads were redirected to a specific video and the channel of that video was automatically subscribed. That was resolved with addon version 7.3.1, but someone might have reported it for being malicious because of that.

I do not know if the extension actually does something malicious or if this was just a very weird bug.

About possibly doing "evil" stuff: Around October 4th there was a weird issue with the extension where all YouTube page loads were redirected to a specific video and the channel of that video was automatically subscribed. That was resolved with addon version 7.3.1, but someone might have reported it for being malicious because of that.

This is far too specific to be just a bug ...

On Mon, 14 Oct 2024 13:09:21 -0700, d4k0 @.***> wrote: > About possibly doing "evil" stuff: Around October 4th there was a > weird issue with the extension where all YouTube page loads were > redirected to a specific video and the channel of that video was > automatically subscribed. That was resolved with addon version > 7.3.1, but someone might have reported it for being malicious > because of that. This is far too specific to be just a bug ...
Maybe it was a request to some "generic" (sub)site, and a YouTube algorithm filled the generic request which what it seemed to be the "most interesting video" at that time?

I suggest to discuss "Cookie Dialog Monster"-related stuff over here at it's current repository so that the author can be included.

I agree, and for anyone reading this I'd like to point them to the official answer to all this "possible evil stuff" from the addon author: https://git.wanhose.dev/wanhose/cookie-dialog-monster/issues/138#issuecomment-415

@dreirund, @cremor: So far, the "Cookie dialog monster" developer(s) got into conflict with Firefox (their extension is no longer published on the FF addons site), with Github and with Gitlab. I would stay away from this project, I find it extremely suspicious.

On Tue, 22 Oct 2024 10:16:44 -0700, ColourGrey @.***> wrote: got into conflict with Firefox (their extension is no longer published on the FF addons site),
It is, I just found it via their search function: https://addons.mozilla.org/en-US/firefox/addon/cookie-dialog-monster/?utm_source=addons.mozilla.org&utm_medium=referral&utm_content=search

On Tue, 22 Oct 2024 10:16:44 -0700, ColourGrey @.***> wrote: got into conflict with Firefox (their extension is no longer published on the FF addons site),
It is, I just found it via their search function: https://addons.mozilla.org/en-US/firefox/addon/cookie-dialog-monster/?utm_source=addons.mozilla.org&utm_medium=referral&utm_content=search

This is a very very old version from 2022 that hardly works properly today. I also don't understand why he in particular has any issues with Mozilla as there are a few other addons with similar functionality there. He doesn't even seem to be trying to get the extension onto the official addon page anymore. Instead, he wants you to download the XPI file from his self-hosted repository.

On Tue, 22 Oct 2024 10:49:22 -0700, d4k0 @.***> wrote:

On Tue, 22 Oct 2024 10:16:44 -0700, ColourGrey @.***> wrote: > got into conflict with Firefox (their extension is no longer > published on the FF addons site), It is, I just found it via their > search function: > https://addons.mozilla.org/en-US/firefox/addon/cookie-dialog-monster/?utm_source=addons.mozilla.org&utm_medium=referral&utm_content=search > This is a very very old version from 2022 that hardly works properly today. I also don't understand why he in particular has any issues with Mozilla as there are a few other addons with similar functionality there.
According to the author: Lost two factor authentication second factor and was not able to restore access or the procedure was too complicated. (I totally can understand this part, having been through a similar thing at the Arch Linux "SSO" needed to report issues to their packages, which enforces oath two factor authentication.)
He doesn't even seem to be trying to get the extension onto the official addon page anymore. Instead, he wants you to download the XPI file from his self-hosted repository.
For Chromium it is in the official chrome store, though.

So why doesn't he just create a new account at Mozilla? Why is he so careless with his two-factor authentications, especially as a developer (I'm a software developer myself)? Anyone who does anything with IT knows how important these are and that you have to store them securely.

Why is he so careless with his two-factor authentications, especially as a developer

Without judging the content of your statement, "carelessness" is something different as doing something evil (which is conscious).

So far, the "Cookie dialog monster" developer(s) got into conflict with [&ldots] Gitlab.

About Gitlab, they stated that the issue just was that, when they mass-imported the GitHub issues to GitLab to have them available there, GitLab's spam detection mechanism did think the issues where spam and did hide them. So, if this is correct, it is not getting into conflict with GitLab but just beeing upset by unwanted automatisms of GitLab. And this gave the impulse for the authors to not rely anymore on third party services.

Do you have any idea how frustrating it is to read the things some of you have said here without being able to respond? It's like you're missing the whole picture. For a while, I felt like I only had two options:

  1. I could have created multiple accounts, risking that GitHub might flag them, making the situation even messier.

  2. I could wait things out and hope the truth would come to light on its own. And that's what I chose to do.

We have a saying in Spain: "Things in the palace move slowly." But after a long month, GitHub finally admitted its mistake.

So, let me clear this up. Cookie Dialog Monster is a simple browser extension to hide those constant cookie pop-ups without messing with user preferences. If a site is broken, users can report it, and I'll open an issue in my repository with basic info like the domain and the page URL, which is valuable to me and requires no GitHub account for the user.

But here's what happened: GitHub's automated bots scanned my repository, flagged all those URLs as spam, and, just like that, my account (including my repos, contributions, and six years of work) was suspended. It was all gone in seconds, flagged over a misunderstanding.

Then we come to GitLab. I was paying nearly €100 a year in hosting and domain costs, and after spending hours migrating everything to GitLab, their bot flagged my issues for having a similar structure to my GitHub issues list—again, spam. Seriously? After more than five years of work, that's the thanks I get? Well, I'm done. I've moved everything to a self-hosted alternative, which saves me money, stress, and—most importantly—gets me out of messes like this.

How about Firefox? Look, I lost access to my Firefox account two years ago due to strict 2FA rules, which meant I couldn't recover my keys (not password, I still remember my password). I know some of you are saying, "Well, you should have been more careful." Yes, I get that. But I'm not "perfect" like some people (see @d4k0 who never lost nothing). I'm just someone trying to keep their work accessible, even if that means relying on an outdated version. And you know what? It's still out there, still working, still getting positive reviews, and that means something to me—even if it doesn't to you.

I don't think it's too much to ask for people to actually understand what they're talking about before trashing an open-source project. Unlike closed-source software from big companies, with open source, you can inspect every line of code. If you don't understand the code, there are tools (like ChatGPT) to explain it to you. But throwing baseless accusations only hurts the people trying to create something helpful.

So, yeah, I'm back, and I'm done with the nonsense. We won't be talking again here, this thread has a completely different purpose.

@dreirund
Copy link

dreirund commented Nov 11, 2024 via email

@ColourGrey
Copy link

@wanhose, how come the thousands of sites reported by users for this extension have never triggered GitHub's spam detector? Or the reports for EasyList cookie list? I am not necessarily suspecting you of any evil, but you should probably adopt the same techniques as those projects in order not to trigger the GitHub robots.

Concerning Firefox: all right, your explanation is reasonable, I buy it. But why not contact the Firefox team, explaining to them what happened? Or why not simply create another account (and then ask the Firefox team to merge the two)?

Frankly, when you write stuff like "This is yet another attempt to bring down this project", this sounds like a conspiracy theory (the big bad Mossad & CIA pulling strings in order to silence the little rebel Firefox extension), so I hope that you will agree that your too passionate tone can make some have some doubts. Especially in 2024, when plenty of conspiracy theories have come to replace common sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

17 participants