Known limitations (browser extension) » History » Version 4
jahoti, 09/12/2021 11:00 PM
Rename "Hachette" to "Haketilo"
| 1 | 1 | koszko | # Known limitations |
|---|---|---|---|
| 2 | |||
| 3 | 4 | jahoti | We list surprising, non-obvious issues and possible privacy shortcomings in version 0.1 of Haketilo. |
| 4 | 1 | koszko | |
| 5 | 4 | jahoti | * Haketilo currently uses short-lived cookies tp smuggle settings to its content scripts. Although partially worked around using outgoing response filtering and unlikely to happen in practice, cookies might leak and a website owner could use them to learn that a user's browser has Haketilo running in it. We are investigating possible solutions. |
| 6 | 1 | koszko | * Currently, user scripts can only be injected to HTML pages. |
| 7 | * Currently, user scripts under Mozilla-based browsers may fail to run on pages loaded from `file://` schema. |
||
| 8 | 4 | jahoti | * On some (Mozilla-based) browsers Haketilo might disrupt XML preview. |
| 9 | * Haketilo doesn't have additional features one could expect from a content blocker: |
||
| 10 | 1 | koszko | * There is currently no option to disable Service Workers while allowing normal scripts to execute. |
| 11 | 2 | jahoti | * There is currently no option to disable loading of external/third-party fonts, tracking pixels, or other strategies that are used by Google and similar companies for snooping on internet users. |
| 12 | 4 | jahoti | * There is currently no facility to anonymize queries Haketilo makes to its script repositories. This means a bad admin of a [Hydrilla](https://hachettebugs.koszko.org/projects/hydrilla/wiki) instance could see the sites for which a Haketilo user tried to find custom scripts. |
| 13 | * Haketilo is still missing: |
||
| 14 | 1 | koszko | * UI Translations |
| 15 | * Accessiblity features |
||
| 16 | * Mobile support |
||
| 17 | 4 | jahoti | * Pages that were open during Haketilo's installation/enabling might break in weird ways (under Mozilla browsers) and Haketilo will not function there properly (all browsers). Reloading each browser tab is the simplest solution to this issue. |
| 18 | 3 | koszko | * There are almost certainly other bugs. |