BadWolf

Screenshot of badwolf on this page

BadWolf is a privacy-oriented WebKitGTK browser that doesn’t do compromises for first-usage usability. Privacy is the first goal, and it should be usable (the security=usability-1 is false in my opinion). It should also stay fairly minimalist, stuff done in our dependencies that would need modification should be done upstream instead of us doing work we aren’t supposed to do in the first place.

It has also been my daily driver for quite a while now (specially since I added tabs) so you can expect it to be quite usable but still have few missing areas.

For now it is de-facto is a personnal project but I welcome contributions and could add maintainers and move to a more community-oriented way of doing the development.

Features that are not wanted to be present by default will either be done as an option or as a separate branch, this is to avoid having a pile of browsers doing the same thing. Also extensions will try to be independant of the browser.

Releases

The releases are stable but I would consider the current stage of development to be in beta as not everything is present yet. Badwolf is using Semantic Versioning.

You can get the releases tarballs and changelogs at https://hacktivis.me/releases/ and https://gitlab.com/lanodan/badWolf/-/tags (which also provides an Atom feed), there is only source releases for now but if I can be sure that I can have portable binairies without having to bundle the dependencies I’ll do them too.

Packages / Recipes

And maybe other platforms not added to this list yet but can be found via https://repology.org/project/badwolf/versions

Supported platforms

In a sort-of descending priority list, X11 and Wayland are supported.

Note: proprietary systems like Microsoft Windows and Apple OS are unsupported. If you have systems where WebKitGTK runs but isn’t a *BSD or a linux distro, I’ll be interested in knowing about them.

Bug reports / Contributions

The git repositories are using GitFlow with commits that are clean with descriptive messages. Expect your patchs to be rewrote or rejected if not, with proper explaination at it should always be.

See also

Similar browsers

Theses are the browsers where I drew inspiration or some hints from their code from:

Related Articles