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.

As I receive questions on this topic from time to time, I posted a page explaining the syntax for the custom search URL.


I have written a blog post about the negative privacy implications of saving the instance state that was introduced in Privacy Browser 3.5.


The Dark Theme page has been updated with information about how things now work in the 3.5 release.


Thiago Nazareno Conceição Silva de Jesus <mochileiro2006-trilhas@yahoo.com.br> has kindly agreed to do a Portuguese translation of Privacy Browser. Anything that is ready will be included in the 3.5 release, with the full translation to follow.

Main WebView is by far the most complicated because it has the most things going in. I am doing the other first so I can learn all the tricks before tackling the hardest one. When it is done, 3.5 will be ready for release.

Show thread

The following three activities remain:

• Bookmarks
• Bookmarks Database View
• Main WebView

Show thread

Privacy Browser can now gracefully restart (change day/night theme) for the following activities:

• About
• Domains
• Guide
• Import/Export
• Logcat
• Requests
• View Source

The last thing to do before the 3.5 release is to train Privacy Browser to save and restore the state when it is killed in the background. This is very important for the new day/night theme because every time the theme changes (like entering battery saver mode) the app is restarted. Handling this correctly is a tricky process, and I have no idea how long it will take to figure it out. But, I just made the logcat restore the scroll position on restart. 😀


Show more

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