Closed SpencerIsGiddy closed 1 year ago
I would say a) as soon as they get their issue count down to at least 130 from 230 or b)they add back the host file list which was breaking everything for nextdns users, c)both or d)until energized gets a better reputation but that is hard to measure other then active issues on GitHub
Not all lists have a bunch of false positives, blu, blu go and spark seem to fine for the most part. It’s just the latter bunch are where it gets annoying to deal with. In any situation I feel like getting rid of energized unified is useful because it’s not much different from ultimate, it’s just ultimate+porn protection like I said yesterday. That’s just my recommendation. You’re the boss
Sure. How do we know when to un-dead these? What would be a good criteria?
You’re the boss
I may have the keys to this repo, but I don't mind relying on folks who actually get the pulse of these things more than I.
Sure. How do we know when to un-dead these? What would be a good criteria?
You’re the boss
I may have the keys to this repo, but I don't mind relying on folks who actually get the pulse of these things more than I.
What are your thoughts on when the GitHub reaches less than 175 active issues because 230 is obsurd and it would be unwise to adds these lists back if no one is getting help. Even 200 is a fine number with me
Ah, okay. Sounds good.
(Apologies, I missed literally the same comment you made earlier).
The title says "mark some energized list as dead" or have you marked all dead?
Also, what is the criteria to add Energized back? I'd prefer I add them back as soon as possible, tbh, because if anyone's using just Energized would see all ads/tracker/spyware content pass-through with the next update.