Open christabor opened 6 years ago
Example:
[themes]
bootstrap='mycustombootstrap-theme'
[hide-dom]
#foo.bar
.rad.cool > li a
This obviously requires logic to parse and manipulate these settings, so that makes it less useful when compared to things like Stylish and Greasemonkey/Tampermonkey
Use themes, configs, other relevant sittings in a sort of "global internet ini" file that is stored in a public git repository.
Then if you have say, a plugin installed, it will use this repo (not necessary to authenticate, as it's read-only and public) to load settings for a site.
E.g.
if the site uses bootstrap, set a default theme of your choice (e.g. https://bootswatch.com/)
if the site has ads, hide them based on given prefixes or selectors
This starts to converge with a lot of what greasemonkey type plugins do, but this would be easier to manage for certain things, and allows for "sharing" different settings via git repo.