Applications "profile" export, import, sharing with others (allowed, blocked ips and domains) outside of rdns Generic backup/restore

[onetimecontributor]

Hi. I would like to bring up a discussion around potential feature.
Environment: I have rdns with wireguard, on-device blocklists and upstream dns resolver (with blocklists).

I would like to be able to export/import user applications config - like mode (allowed/denied/isolated), ip/domain rules. This needs to be done outside of rdns generic backup/restore, so I can sync my different devices without affecting other rdns configurations and restore app config after app re-installation (now rdns doesn't preserve settings).
Greater possibility - allow community to share predefined profiles so others can import them and don't bother figuring out.

Reasoning:
Though blocklists (on-device and upstream) address a lot of privacy concerns for well-known trackers, there is still a set of application-specific addresses that those doesn't block though they are app-specific trackers and are not required for (controversial) basic app functioning.
So there is still a noticeable area of privacy leaks that, at the moment, can be addressed only manually by blocking particular domains in per-app settings.

Let's take Waze navigation app as an example. For my basic usage, it seems I only need 3 domains for it to work: ctilesgcs-row.waze.com, rt-xlb-row.waze.com and rt.waze.com
However, there are 16 other domains (also including clearly non-waze domains) that are reached by waze.
Though all of them do smth useful, there is also a great possibility that data will leake for profiling etc.
So I have isolated Waze with 3 domains whitelisted.

Another example is phone manufacturer system apps. I have system apps in isolation mode, keeping only OTA update servers whitelisted.

I understand the will be risks or downsides, like:

• this may be useful only to those who pay extra attention to side leaks (dunno what's the % of rdns userbase)
• will require periodical manual tuning (dunno if it will be worse than current manual efforts)
• as apps evolve, profiles will become obsolete
• certain domain may be required to rather preserve app privacy settings, and blocking it will damage this config (by allowing tracking)
• what is "basic" functionality for one person may not be enough for another (like with waze guest mode vs sign-in that requires extra domains)
• different app versions may use different domains that will make profiles not shareable, etx

What do you think?

[ignoramous]

Thanks. Not sure when we get to working on this, but: #1987