Add possibility to define custom blocked services

[alexruf]

The feature to just quickly block & unblock popular sites and services in the general tab with a simple click is awesome. As a father of children who sometimes overdo it with online gaming, it would be great if you could define your own custom services there to extend and customize the list of services. I think of it like this: You simply enter the name of your service and it creates a small separate block list associated with this service name. With a toggle button somewhere in the UI you now can simply enable enable and disable the blocking of these DNS entries.

In theory you could go even further and also add the ability to schedule times when those services are automatically blocked. I think this could be a really useful feature.

[szolin]

Is it really necessary to have a custom list of blocked services?

1. We have a compiled static list for the most popular services - it's much better to add more services there, because it will automatically help other people. Plus our community will keep this list up to date.
2. If there are several domains you want to block for specific clients - you can use $ctag filters for that. I agree it's not that simple as click on enable/disable button, but it will do exactly the same.

[ameshkov]

Let me postpone this task a little bit, we have too much on v0.103 already.

Regarding defining custom services, let's discuss.

Here are our options:

1. Keep the list as is and do nothing
2. Allow people to define their custom sets (kinda overlaps with filter lists)
3. Allow people to pull request more "services" to AdGuard Home. We may need to change the UI a little bit because the list of services will grow huge

[temporallyaccount]

2. Allow people to define their custom sets (kinda overlaps with filter lists)

Then let people to add their own[2] and this feature can be improve more than current.

[dark0mode]

options: 2

[R9980]

2

[esvra]

2

[temporallyaccount]

Let me postpone this task a little bit, we have too much on v0.103 already.

@ameshkov last time this postponed to v0.104 but secretly has moved to v0.106 No much to-do list on v0.104 so can you add this back to it?

[ameshkov]

We're going to conduct some massive refactoring in v0.104 or v0.105 so I am keeping these releases without new features.

[temporallyaccount]

We're going to conduct some massive refactoring in v0.104 or v0.105 so I am keeping these releases without new features.

Okey :) If there any chance later then consider to assign to **v0.104*** or 5

[ameshkov]

Zero chances

[ameshkov]

As I said, I am keeping 0.104/0.105 without new features. We need this refactoring to integrate a more important feature -- content blocking proxy. Unfortunately, everything else will have to wait.

[temporallyaccount]

Zero chances

(๑◕︵◕๑)

[tomcoleman]

alexruf that would be amazing what you posted!!!

[vipinjn24]

Anything on this ticket going on?

[alexsannikov]

Bump this ticket. This feature request still looks very attractive, and is still awaiting. The main idea of this suggestion is the very quick allow/disallow some customers pre-defined service. It may be not very well known, or maybe even very narrowly user-specific, and never to be included into the new release. Of course, adding and removing the domain (one or many) into custom rules does the same, but one toggle is much more useful and simple. Thanks

[overwatch3560]

@alexruf is your issue resolved by now?

[quaintdev]

Currently, time schedule-based blocking can only be applied to services listed in the Blocked Services. This limitation prevents users from applying time-based restrictions on any services not included in this list. Expanding this feature would allow for greater flexibility and control, accommodating the vast array of regional and global services that users may want to restrict based on specific schedules. This enhancement is highly needed to provide comprehensive time-based blocking capabilities.