clarify content filtering improvement plans
This commit is contained in:
parent
0b503c46d0
commit
6dae129935
@ -941,10 +941,10 @@
|
||||
particularly with our goal of having most Vanadium users using nearly the same
|
||||
configuration.</p>
|
||||
|
||||
<p>We plan to move to a better content engine with support for content hiding
|
||||
and more advanced filter rules in the future. Expanding the standard filters
|
||||
will depend on having support for the extensions used by uBlock Origin, AdGuard
|
||||
and other filters.</p>
|
||||
<p>We plan to move to a better content engine with support for more advanced
|
||||
filter rules and cosmetic filtering in the future. Expanding the standard
|
||||
filters will depend on having support for the extensions used by uBlock Origin,
|
||||
AdGuard and other filters.</p>
|
||||
|
||||
<p>Most browser data is currently excluded from OS backups, which will likely be
|
||||
changed once GrapheneOS has a better backup service included. Export/import for
|
||||
|
Loading…
x
Reference in New Issue
Block a user