DNSCrypt / dnscrypt-proxy

dnscrypt-proxy 2 - A flexible DNS proxy, with support for encrypted DNS protocols.
https://dnscrypt.info
ISC License
11.28k stars 1k forks source link

Enhancement : a whitelist to counter one's blacklist #198

Closed ghost closed 6 years ago

ghost commented 6 years ago

I know this has been discussed here already and as I understood it it's feasible: adding a setting to enable a domain whitelist conceived as an exception list in regard to one's blacklist (blacklist.txt).

When a user includes one or more filters in the blocklist some filters may include an entry which is either inappropriate objectively or undesirable by the user for personal considerations.

The idea is not new,

For instance I have a list I just don't add anymore given the fact it has one entry which is obviously a mistake. I won't check the blacklist to remove exceptions each time the list has been updated. If I could add that entry to a whitelist then I could take advantage of the whole list...

I must point out that of course the argument concerns more particularly users handling several blocking lists (merged into DNSCrypt-proxy's blacklist). I have nine lists, merged with removed redundancies. Having a whitelist then would be a welcomed feature.

ghost commented 6 years ago

Topic already exists on #117, OK, thanks Frank.

jedisct1 commented 6 years ago

Let's keep yours open instead, as the description is more concise.

ghost commented 6 years ago

I never know when to close or not doors I've opened myself in this place (I mean GitHub). :=)

sergeevabc commented 6 years ago

Issues are commonly closed if they are resolved as fixed, rejected, or invalid. I see whitelist feature was requested here and there and even there, but see no reason to believe it is resolved. So why is it closed with a weird timeout tag then? It’s a kind of disregard for users. Have you lost passion, @jedisct1?

jedisct1 commented 6 years ago

There hasn't been any progress after 30 days. I haven't had the time to do this, nobody offered to help either, so keeping this open is useless and won't make it magically happen in a near future.

ghost commented 6 years ago

Looks like the idea which I deployed after others had, meets little enthusiasm.

There hasn't been any progress after 30 days

is factual. I'm surprised but as always with little success the best concepts often vanish :=)

sergeevabc commented 6 years ago

Should we consider the project abandoned? Or bug reports are the only things to be processed from now? Is there a roadmap to see what is going to happen in the future?

jedisct1 commented 6 years ago

You wrote a lot of comments, but never ever contributed anything to the project. Instead of random comments on old tickets, you could have documented the problem discussed in each ticket and its solution. That would have improved the project. But you didn't.

Does it mean that the project is abandoned?

No, just that people do whatever they feel like doing. If they have spare time (which is not really a thing. It's more about trade-offs with other things), if they feel like doing something in particular, if they think that they can learn by doing it, if this can be useful to themselves, they will do it.

If not, they might do it whenever they feel like doing it. Later. For any definition of later. Or never. There are no obligations.

Now, by writing "should we consider the project abandoned" because I didn't abandon my actual job to work for free on something you suggested within 3 weeks, you can be sure that my motivation to spend time on this immediately went down to zero.

sergeevabc commented 6 years ago

@jedisct1, aren’t you confusing mere users with developers? User is not skilled to contribute in terms of changing code. User applies tool to tasks in a way you may not even think of, within the environment you do not have, then reports back to developer about ambiguous, broken and missing pieces. It explains why I asked a lot of questions lately, i.e. to make things clear, because you made things obscure in the first place. Public issue tracker implies developer’s intention to gather feedback — why else keep it open. Then it means doing, even with vague roadmap and loose schedules, not silently canceling issues or passive-aggressively confronting users. Otherwise, have guts to inform you’re (busy, burned out, done…), mute the tracker and mark the project as unmaintained to strangle public expectations for improvements.

jedisct1 commented 6 years ago

Here is a better picture.

perro-y-gato-durmiendo-petsonic

sergeevabc commented 6 years ago

Hooray, it’s implemented in 65e6b8569ee65e168095d9cfb562681491df22f0! Thank you, Frank.