Google wants everyone to use scoped storage, but they can’t be bothered to use it themselves.

The Privacy Browser ROM Integration repository is being discontinued. If anyone is currently using it, please let me know and I would be happy to continue maintaining it.

Unfortunately, it looks like updating to targetSdkVersion 30 (which forces Android’s new scoped storage) breaks the saving of web archives (MHT files).

I am working on transitioning Privacy Browser to using the Storage Access Framework, which will allow me to remove the READ_EXTERNAL_STORAGE and WRITE_EXTERNAL_STORAGE permissions. I am quite surprised that this works all the way back to Android KitKat (API 19). I had assume that I would have to drop KitKat support when this feature was enabled.

I switched the protocol used to clone Privacy Browser’s repository from Git to HTTPS to prevent MITM attacks.

I wrote a blog post about removing and disabling comments on some parts of my webpage with the purpose of directing them to the correct locations.

I wrote a blog post describing the requirements for a search engine to be included in Privacy Browser.

I wrote a blog post about the Referer header and how Privacy Browser interacts with it.

I wrote a blog post about an annoying bug that manifests in WebView’s handling of nested scrolling.

I wrote a blog post about the change in certificate signing by Let’s Encrypt and how it affects Privacy Browser.

Up to this point, Privacy Browser had used separate light and dark HTML and icon files for the Guide and About. These have now been combined into one set of global icon files and one set of HTML files per language.

My primary goal was to remove the need for double file editing, which became surprisingly time consuming as the number of languages increased. However, there is an added benefit that doing so shrunk the APK file size by 0.8 MiB.

Show older

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.