commit: bdd986dcca23ada2fdb8dd5920b273abfb78b284
parent f9beb6a539de4bb87b934bd3e9a31eba4ccb23c6
Author: Haelwenn (lanodan) Monnier <contact@hacktivis.me>
Date: Mon, 19 Apr 2021 23:03:30 +0200
projects/badwolf: Release 1.1.0
Diffstat:
2 files changed, 12 insertions(+), 5 deletions(-)
diff --git a/projects/badwolf.shtml b/projects/badwolf.shtml
@@ -13,7 +13,7 @@
</head>
<body itemscope="" itemtype="https://schema.org/SoftwareApplication">
<!--#include file="/templates/en/nav.shtml" -->
-<!--#set var="baseName" value='badwolf-1.0.3' -->
+<!--#set var="baseName" value='badwolf-1.1.0' -->
<main itemprop="applicationCategory" content="BrowserApplication">
<!--#include file="/projects/badwolf/nav.shtml" -->
<h1 itemprop="name">BadWolf</h1>
@@ -50,8 +50,8 @@
</ul>
<p>BadWolf is using <a href="https://semver.org/spec/v2.0.0.html">Semantic Versioning</a> with considering that the User-Interface is part of the interface stabilisation. Release branches (ie. <code>1.0.x</code>) are supported for 6 months for any bug fixes and 2 years for security fixes.</p>
<p>
- Tarball signature check: <a href="https://flak.tedunangst.com/post/signify">signify</a>/<a href="https://github.com/jedisct1/minisign">minisign</a> is the recommended tool to use, you can find my key at <a href="https://hacktivis.me/releases/signify/2020-05.pub">/releases/signify/2020-05.pub</a>, you can find more info about how I manage the keyset in: <a href="/articles/Bootstrapping%20signify%20for%20my%20assets">Bootstrapping signify for my assets</a>.<br />
- The command to verify the tarball looks like this: <code><kbd>signify -V -p signify/2020-05.pub -x <!--#echo var="baseName" -->.tar.gz.sign -m <!--#echo var="baseName" -->.tar.gz</kbd></code>
+ Tarball signature check: <a href="https://flak.tedunangst.com/post/signify">signify</a>/<a href="https://github.com/jedisct1/minisign">minisign</a> is the recommended tool to use, you can find my key at <a href="https://hacktivis.me/releases/signify/2021-04.pub">/releases/signify/2021-04.pub</a>, you can find more info about how I manage the keyset in: <a href="/articles/Bootstrapping%20signify%20for%20my%20assets">Bootstrapping signify for my assets</a>.<br />
+ The command to verify the tarball looks like this: <code><kbd>signify -V -p signify/2021-04.pub -x <!--#echo var="baseName" -->.tar.gz.sign -m <!--#echo var="baseName" -->.tar.gz</kbd></code>
</p>
<h2>Tested and supported platforms</h2>
@@ -64,7 +64,7 @@
<dd>Wayland, X11</dd>
</dl>
<p>Similar systems should work, feel free to reports tests/bugs and volunteer on testing before releases are published.<br />
- Libre Systems where WebKitGTK is up-to-date (2.28.0+) are the target, proprietary systems are unsupported.</p>
+ Libre Systems where WebKitGTK is up-to-date (2.32.0+) are the target, proprietary systems (Windows, MacOS, Oracle Solaris, …) are unsupported.</p>
<h2 id="contacts">Contacts / Discussions</h2>
<dl>
diff --git a/projects/badwolf/fqa.shtml b/projects/badwolf/fqa.shtml
@@ -45,7 +45,14 @@
</p>
<h2 id="adblocker"><a href="#adblocker">§</a> AdBlocker?</h2>
- <p>As written in the manpage, there is <a href="https://github.com/jun7/wyebadblock">wyebadblock</a>. And no, mere JavaScript blocking is nowhere near enough to avoid tracking, there is a lot of exploits based on pure CSS.</p>
+ <p>
+ As mere JavaScript blocking isn't enough, BadWolf includes support for WebKit's content-filters, this allows to block unwanted content (ads, nagware, ...) directly into the engine.<br />
+ The file is at <code>${XDG_CONFIG_HOME:-$HOME/.config}/badwolf/content-filters.json</code><br />
+ For some introductory information about the format see: <a href="https://webkit.org/blog/3476/content-blockers-first-look/">Introduction to WebKit Content Blockers</a>, <a href="https://webkit.org/blog/4062/targeting-domains-with-content-blockers/">Targeting Domains with Content Blockers</a>, <a href="https://developer.apple.com/documentation/safariservices/creating_a_content_blocker">Creating a Content Blocker</a>.
+ </p>
+
+ <p>For a converter using AblockPlus-style filters, try: <a href="https://gitlab.com/eyeo/adblockplus/abp2blocklist">https://gitlab.com/eyeo/adblockplus/abp2blocklist</a></p>
+ <p>For a ready-to-use file (that you should update periodically), try: <a href="https://easylist-downloads.adblockplus.org/easylist_min_content_blocker.json">https://easylist-downloads.adblockplus.org/easylist_min_content_blocker.json</a></p>
<h2 id="privacylvl"><a href="#privacylvl">§</a> How good is it's privacy?</h2>
<p>It's an in-between <a href="https://torproject.org/">Tor Browser</a> and your regular browser and much better than most other WebKitGTK browsers out there since day 1. Tor Browser stands for anonymity by having everyone get the same fingerprint over the Tor network. Badwolf is for when you don't use the tor network (for any reason) and thus need a more normal fingerprint depending on your region (ie. languages and timezones) while still having reasonable privacy.</p>
