logo

blog

My little blog can’t be this cute!

badwolf.shtml (6650B)


      1 <!DOCTYPE html>
      2 <html lang="en">
      3 	<head>
      4 <!--#include file="/templates/head.shtml" -->
      5 		<title>BadWolf — lanodan’s cyber-home</title>
      6 	</head>
      7 	<body>
      8 <!--#include file="/templates/en/nav.shtml" -->
      9 	<main>
     10 		<h1>BadWolf</h1>
     11 		<blockquote>
     12 		<details>
     13 		<summary><em>Rose</em>: I am the Bad Wolf, I create myself. I take the words… I scatter them in time and space. A message to lead myself here.<br/></summary>
     14 		<em>Doctor</em>: Rose, you've got to stop this! You've go to stop this now! You got the entire vortex running through your head. You're gonna burn!<br/>
     15 		<em>Rose</em>: I want you safe. My Doctor. Protected from the false god<br/>
     16 		<em>Dalek Emperor</em>: You cannot hurt me! I am immortal!<br/>
     17 		<em>Rose</em>: You are tiny. I can see the whole of time and space. Every single atom of your existance and I divide them. Everything must come to dust. All things. Everything dies. The Time War ends.<br/>
     18 		<em>Dalek Emperor</em>: I will not die! I cannot die!<br/>
     19 		</details>
     20 		</blockquote><cite>Doctor Who (2005), Season 1, Episode 13</cite>
     21 		<a href="/images/badwolf_2019-05-11.png"><img class="thumb_inline right" src="/images/badwolf_2019-05-11.png" alt="Screenshot of badwolf on this page"/></a>
     22 		<p>BadWolf is a privacy-oriented WebKitGTK browser that doesn’t do compromises for first-usage intuitiveness. Privacy is the first goal, and it should be nicely usable/accessible (the security=usability<sup>-1</sup> 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.</p>
     23 		<p>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.</p>
     24 		<p>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.</p>
     25 
     26 		<h2>Releases</h2>
     27 		<p>Badwolf is using <a href="https://semver.org/spec/v2.0.0.html">Semantic Versioning</a> with considering the User-Interface as an API. Once 1.0.0 release is out, a release branch (ie. 1.0.x) is supported for 6 months for any bug fixes and 2 years for security fixes.</p>
     28 		<p>You can get the releases tarballs and changelogs at <a href="https://hacktivis.me/releases/">https://hacktivis.me/releases/</a> and <a href="https://gitlab.com/lanodan/badWolf/-/tags">https://gitlab.com/lanodan/badWolf/-/tags</a>, the latter also provides an <a href="https://gitlab.com/lanodan/badWolf/-/tags?format=atom">Atom feed</a>. Only source release are supported outside of ones supported by software distribution, static-linking and Flatpaks should work but their distribution of them will have to be done by some other party.</p>
     29 		<h3>Packages / Recipes</h3>
     30 		<ul>
     31 			<!-- Alphabetically sorted -->
     32 			<li>Alpine: Added in edge testing in 2019-12-30 as <code><a href="https://pkgs.alpinelinux.org/packages?name=badwolf">badwolf</a></code></li>
     33 			<li>ArchLinux: Present in the AUR as <code><a href="https://aur.archlinux.org/packages/badwolf/">badwolf</a></code></li>
     34 			<li>Gentoo: Present in the <a href="https://wiki.gentoo.org/wiki/Project:GURU">GURU overlay</a> as <code><a href="http://gpo.zugaina.org/www-client/badwolf">www-client/badwolf</a></code></li>
     35 		</ul>
     36 		<p>And maybe other platforms not added to this list yet but can probably be found via <a href="https://repology.org/project/badwolf/versions">https://repology.org/project/badwolf/versions</a></a>
     37 
     38 		<h2>Tested and supported platforms</h2>
     39 		<ul>
     40 			<li>OS: */Linux, NetBSD, OpenBSD, FreeBSD</li>
     41 			<li>CPU Architectures: x86_64/amd64, armv7hf</li>
     42 			<li>Display: Wayland, X11</li>
     43 			<li>WebKitGTK: 2.26.x+, compiling it yourself is recommended</li>
     44 		</ul>
     45 		<p>Badwolf should also work well on other similar systems, feel free to report tests on them and volunteer for testing releases before they are published.<br/>If you have a libre system where WebKitGTK runs but isn't Linux or *BSD, I'll be interested in knowing about them. Proprietary systems are unsupported.</p>
     46 
     47 		<h2>Tickets (bug, feature request, …)</h2>
     48 		<p>You can <a href="/about">reach me</a> directly or write a ticket on the <a href="https://gitlab.com/lanodan/badwolf">Gitlab repository</a>.</p>
     49 		<p>For security issues, sending an email to <a href="mailto:contact+badwolf-security@hacktivis.me">contact+badwolf-security@hacktivis.me</a> is the preferred way.</p>
     50 
     51 		<h2>Contributing</h2>
     52 		<p>Please try to <a href="/about">reach me</a> before modifying code, I wish to avoid rejecting patches because their design didn't fit while the idea could be more than welcome.</p>
     53 		<h3>Translation</h3>
     54 		<p>Badwolf is using gettext po files for translations, help in getting it translated in more languages is welcome (but please do not submit machine translation, I can do this myself).</p>
     55 		<h3>Code</h3>
     56 		<p>The git repositories are using <a href="https://nvie.com/posts/a-successful-git-branching-model/">GitFlow</a> with commits that are clean with descriptive messages. I'll probably ask you to rewrite your commits or rewrite them if they aren't.</p>
     57 		<ul>
     58 			<li>You can use <a href="/git/badwolf">/git/badwolf.git</a> and send me an email (<code>git send-email</code> is accepted, <a href="https://git-send-email.io/">here is a tutorial</a>) at <code>contact+badwolf@hacktivis.me</code></li>
     59 			<li>You can use <a href="https://gitlab.com/lanodan/badwolf">the gitlab repository</a> (note: will get cleanly migrated to something else at some point)</li>
     60 			<li>You can also use other means, like an actual pull request(sending a link to a repo and a branch)</li>
     61 		</ul>
     62 
     63 		<h2>See also</h2>
     64 		<h3>Similar browsers</h3>
     65 		<p>Theses are the browsers where I drew inspiration or some hints from their code from:</p>
     66 		<ul>
     67 			<li><a href="https://uninformativ.de/git/lariza">lariza</a>: Minimalist WebKitGTK browser, reuses tabbed, vi modal edition</li>
     68 			<li><a href="https://wiki.gnome.org/Apps/Web">Epiphany</a> (aka Gnome Web): GNOME-weight WebKitGTK browser, haven’t used it but looked at the code for hints</li>
     69 		</ul>
     70 		<h3>Related Articles</h3>
     71 		<ul>
     72 			<li><a href="https://hacktivis.me/articles/Mozilla%20is%20Broken">Mozilla is Broken</a></li>
     73 			<li><a href="https://hacktivis.me/articles/www-client%20are%20broken">www-client are broken</a> (which can serve as a loose roadmap)</li>
     74 		</ul>
     75 	</main>
     76 <!--#include file="/templates/en/footer.html" -->
     77 	</body>
     78 </html>