Application modules

Boo Berry

Moderator + Beta Tester
Moderator
I've got a neat idea to share, which will help supporting new browsers and applications when they're supported in Adguard v6! My idea is the following; instead of releasing program updates to support new browsers/applications, issue module updates (kinda like an updated filter list) to add new browsers/applications without the need to release program updates. It'd have to be some sort of database file that contains the browser/application name, executable name along with a compressed icon that Adguard can use to display. Perhaps something like that could be done for adding new filter lists within Adguard without the need of program updates?

Thoughts?
 

Accel

Beta Tester
I've got a neat idea to share, which will help supporting new browsers and applications when they're supported in Adguard v6! My idea is the following; instead of releasing program updates to support new browsers/applications, issue module updates (kinda like an updated filter list) to add new browsers/applications without the need to release program updates. It'd have to be some sort of database file that contains the browser/application name, executable name along with a compressed icon that Adguard can use to display. Perhaps something like that could be done for adding new filter lists within Adguard without the need of program updates?

Thoughts?
or maybe use a port scanning which application can be added?

browser and messenger largely consist of 80, 8080 or 443 ports.
 

avatar

Administrator
Staff member
Administrator
Good idea!

---------- Post added at 10:59 PM ---------- Previous post was at 10:56 PM ----------

browser and messenger largely consist of 80, 8080 or 443 ports.
But they do not listen to these ports, they connect to.
And these connections are not persistent so port scan can show zero apps even if browser is running.
 

Boo Berry

Moderator + Beta Tester
Moderator
Okay, something to add to this. By default applications (non-browsers) in the database should have the injection of the Assistant/userscripts disabled to prevent possible issues (e.g. the AIM issue in the other thread with the Assistant injection) and for the fact the Assistant (probably) won't work at all with non-browsers.
 

avatar

Administrator
Staff member
Administrator
Okay, something to add to this. By default applications (non-browsers) in the database should have the injection of the Assistant/userscripts disabled to prevent possible issues (e.g. the AIM issue in the other thread with the Assistant injection) and for the fact the Assistant (probably) won't work at all with non-browsers.
We plan to use different filters for applications. Standard filters are too dangerous.
 
Top