is now Small Technology Foundation. 14.8 KB
Newer Older
Aral Balkan's avatar
Aral Balkan committed
# Better
Aral Balkan's avatar
Aral Balkan committed

Aral Balkan's avatar
Aral Balkan committed
Better protects you from unethical web sites. It makes your web experience safer, lighter, and faster.
Aral Balkan's avatar
Aral Balkan committed

Aral Balkan's avatar
Aral Balkan committed
Better enforces the [Ethical Design Manifesto]( It helps the Web respect human rights, effort, and experience.
Aral Balkan's avatar
Aral Balkan committed

Better is curated by, a tiny two-person-and-one-husky social enterprise striving for social justice in the digital age. Better is free, open, and transparent.
Aral Balkan's avatar
Aral Balkan committed

Aral Balkan's avatar
Aral Balkan committed
## Content
Aral Balkan's avatar
Aral Balkan committed

Aral Balkan's avatar
Aral Balkan committed
This repository contains the Better content: Better’s database of information on trackers and other malware as well as the web sites that host them.
Aral Balkan's avatar
Aral Balkan committed

Aral Balkan's avatar
Aral Balkan committed
This content is in Blockdown format. Blockdown is an extension of Markdown with special vocabulary to describe web malware. Blockdown can also contain WebKit content blocking rules. The Blockdown pages in Better’s content repository both describe web malware and contain the rules to block them.
Aral Balkan's avatar
Aral Balkan committed

Aral Balkan's avatar
Aral Balkan committed
This content is processed by [Better Builder]( to generate the [Better web site]( as well as the data for the [Better iOS App](, including a WebKit `blockerList.json` file.
Aral Balkan's avatar
Aral Balkan committed

Aral Balkan's avatar
Aral Balkan committed
A seminal advantage of Better is that its database is human-readable, open, and extensible via pull requests. (The database is curated by using the Ethical Design Manifesto as the criteria for blocking rules.)
Aral Balkan's avatar
Aral Balkan committed

Contributing to the content is as easy as creating an account on []( and editing a content page in your browser.

Aral Balkan's avatar
Aral Balkan committed
## I’m not a developer, I just want to experience a Better web.

[Get Better from the App Store.](

Aral Balkan's avatar
Aral Balkan committed
25 26
## How can I support Better?

Laura Kalbag's avatar
Laura Kalbag committed
Buying [Better on the App Store]( is one way to support us. If you want to help with the ongoing costs of developing and maintaining Better, you can [donate to]( or, even better, [become a patron]( by setting up a recurring donation.
Aral Balkan's avatar
Aral Balkan committed
28 29 30

## I’m a developer, let me in!

31 32
The easiest way to get started is to follow the instructions in the readme for the [Better iOS app]( repository.

33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61
## Testing locally.

[Better Builder]( will automatically pick up your changes as you save and rebuild your local data.

To persist your changes locally, commit them in Git and push to origin:

git commit -am "My awesome content update"
git push origin master

Note that these changes will be destroyed if you run the Better Builder installer (or the Better iOS installer, which runs the Better Builder installer as part of its own installation process). To not lose any work, save your changes regularly by pushing to production, as explained below.

## Saving your changes by pushing to production

You can push to production with:


Or, manually run what the save script does, which is:

git push live master

## Deployment

Aral Balkan's avatar
Aral Balkan committed
62 63 64
Before you can deploy, you must [set up a GPG key and configure Git to use it]( This is used to sign your tags.

Then, if you have commit rights to the content repository, just run the deployment script:
65 66 67 68 69 70 71


This will create a tag (you will have to enter a tag mesage when prompted, describing the release) and push it to production. Please make sure that you have already committed your changes and pushed them to production either via `git push live master` or by running the `./save` script, which does the same thing.

# Guide to Blockdown

74 75
Better content is authored in Blockdown.

Blockdown is Markdown with an extended high-level vocabulary for describing web malware for the Better knowledge base.

## Sites
79 80 81

Site pages have the following sections:

### Ethical design violations
83 84 85 86 87

## Ethical design violations

This is a list of ethical design violations that gets converted to a collection of badges on the rendered site pages. The Trackers part of the list, detailed below, is updated automatically by [Better Inspector](
89 90 91

#### Trackers

92 93 94
The first badge is always the trackers badge. In Blockdown it is represented by a list item introduced by the word `Trackers`:

  * (Trackers)
96 97 98 99 100
    * Automatically
    * Generated
    * List
    * of
    * Trackers
101 102 103 104

This gets automatically translated by [Better Builder]( to a badge similar to the one below:

Laura Kalbag's avatar
Laura Kalbag committed
![Screenshot of the trackers badge](images/readme/better/trackers-badge-example.png)
106 107 108

Tapping on the badge displays a popover with links to the actual trackers.

Laura Kalbag's avatar
Laura Kalbag committed
![Screenshot of the trackers popover](images/readme/better/trackers-popover-example.png)

The other badges are manually added if they apply to the site in question:
112 113 114 115

#### Aggressive

* (Aggressive)
117 118

119 120
Attempts to block content blockers.

Laura Kalbag's avatar
Laura Kalbag committed
![Screenshot of the Aggressive Badge](images/readme/better/aggressive-badge-example.png)
122 123 124 125 126

#### Doorslam

* (Doorslam)
128 129

130 131
Interrupts and blocks using modal dialogs.

Laura Kalbag's avatar
Laura Kalbag committed
![Screenshot of the Doorslam Badge](images/readme/better/doorslam-badge-example.png)
133 134 135 136 137

#### Clickbait

* (Clickbait)
139 140

141 142
Uses exploitative, addictive content syndication network(s).

Laura Kalbag's avatar
Laura Kalbag committed
![Screenshot of the Clickbait Badge](images/readme/better/clickbait-badge-example.png)
144 145 146 147 148

#### Fingerprint

* (Fingerprint)
150 151

152 153
Uses hidden Canvas fingerprinting.

Laura Kalbag's avatar
Laura Kalbag committed
![Screenshot of the Fingerprint Badge](images/readme/better/fingerprint-badge-example.png)
155 156

#### Web Bug
158 159

* (Web bug)
161 162

163 164
Uses invisible tracking pixels.

Laura Kalbag's avatar
Laura Kalbag committed
![Screenshot of the Web Bugs Badge](images/readme/better/web-bugs-badge-example.png)
166 167

We might create new badges as and when we find new types of web malware and unethical practices to document and warn people about.
168 169 170 171 172 173 174

## After Better section

## After Better

The After Better section provides statistics about the before (without the Better content blocker active) and after (with the Better content blocker active) performance of a site.

It is automatically generated by [Better Inspector](

Laura Kalbag's avatar
Laura Kalbag committed
![Screenshot of the After Better Section](images/readme/better/after-better.png)
180 181 182 183 184 185 186 187 188 189 190 191 192

## Block Rules section

This is the section where we enter the actual WebKit content blocking rules. Each rule is written in a strict subset of MSON (Markdown JSON) and has a brief explanation detailing what the rule does and why.

The blocking rules in this section serve the following purposes, in line with the [Ethical Design Manifesto](

  * Remove any first-party trackers (respect human rights)
  * Improve the usability of the site by removing first-party impediments like doorslams (respect human effort)
  * Improve the experience of the site (respect human effort) – we should especially aim to create a better experience after trackers have been removed (like removing empty spaces left over, etc.)

Please note that this is not the place to put blocking rules for trackers. Each tracker encountered should be entered into the [Trackers](#trackers) section and you have its own page in the `/trackers` section of the content.

193 194 195
### Blockdown syntax

Here is an example of a site-specific blocking rule in Blockdown format:
196 197 198 199 200 201 202 203 204 205

- trigger:
  - url-filter:
- action:
  - type: block

206 207
The Blockdown parser in Better supports all of the [WebKit content blocking rules]( Instead of JSON, however, we enter blocking rules in MSON. All Blockdown rules are combined by Better Builder into a single `blockerList.json` file.

208 209
Blockdown differs from plain WebKit content blocker rules in several ways to make authoring easier and to aid in readability:

210 211 212
1. The default load type is ‘third-party’.
2. The default action type is ‘block’.
2. The default is for rules to be case sensitive.

So, if we take the following fully-specified rule:
215 216 217 218

- trigger:
  - url-filter: somedomain.ext
220 221 222
  - load-type: third-party
  - url-filter-is-case-sensitive: true
- action
223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241
  - type: block

We can simplify it naïvely by removing the properties that have defaults:

- trigger:
  - url-filter: somedomain.ext
- action

Which leaves us with a valid rule but a sad-looking empty action section. In Blockdown neither the trigger nor action sections are required, so we can remove those also. This leaves us with:

  - url-filter: somedomain.ext
242 243 244

245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270
But surely, we can do better than that. So we handle this special case in Blockdown by not requiring the url-filter key either:


Ah, better! ;)

All of the above Blockdown rules are equivalent and will compile into the following fully-formed and highly specific WebKit content blocking rule in JSON:

  "trigger": {
   "load-type": [
    "url-filter-is-case-sensitive": true,
    "url-filter": "^[^:]+://+([^:/]+\\.)?somedomain\\.ext[:/]?"
  "action": {
    "type": "block"

## Automatic URL filter compilation
273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297

Blockdown automatically compiles simple `url-filter` properties to regular expressions with higher specificity as recommended in the [domain targeting recommendations by WebKit engineer Benjamin Poulain](

This means that you can author your entries in plain text, like this:


  - url-filter: some-domain.ext


And Blockdown will compile them into the following form in the blockerList.json:


  "url-filter": "^[^:]+://+([^:/]+\\.)?some-domain\\.ext[:/]?"


## Further reading on WebKit content blocking

  * [Introduction to WebKit Content Blockers](
  * [Targeting Domains with Content Blockers](
  * [Official Safari content-blocking rules documentation from Apple](

298 299 300 301
# Investigation process

Currently, you need to have commit rights to the Content repository to use the Better commandline commands. However, you can use Git directly to fork the repository and submit merge requests and you can [add and edit pages through the online GitLab interface]( without commit rights.

302 303
## Find who owns and runs the tracker

304 305 306 307 308 309 310
1. **Start by editing the tracker**

	better/edit drafts/trackers/

	This will create an issue in GitLab (or update an existing issue, if one already exists) and create or checkout a branch for you. It will also open your working copy of the tracker page in your system editor and in the browser.

2. **Enter the tracker URL into your browser in a private window to see if it loads.**

	Make sure you don’t have an VPNs or extensions blocking or making your browser behave differently from the norm. If you have any tracker blockers already enabled, it may make it harder to investigate!

3. **If it doesn’t load, or if you get a blank page, perform a whois.**

	We are currently using for these so we can link to is as a source when stating ownership information. However, you will sometimes get more information from a direct whois look-up on your machine. In Terminal: `whois`

4. **Some trackers use a domain proxy or a cloaking service** (e.g., Domains by Proxy) to further hide their origins. In this case:
321 322
    * Open up the source of a site that the tracker originated on in the Web Developer console (Timeline view) of Safari (or in the web inspector of your browser of choice)
    * Try to recreate the original call. This might give you more clues about its origin. 
323 324 325 326 327 328 329 330

To find which sites a tracker is on, perform a search on the ~/ folder. For example, you can open up the folder in your text editor and do a global search for the tracker name.

You can also use [Better Inspector]( to search for strings within requests. e.g., to find all URLs that contain **, run:

	./inquiry --local
331 332 333

Other useful tools:

* [Mozilla Lightbeam](

336 337
## Add the tracker/site name to the tracker markdown file

338 339
The name should be formatted as:

340 341 342 343
**TrackerName** by Corporation (domain.tld)

If the tracker name is the same as the corporation name *(e.g. Adlucent by Adlucent)* then just keep the tracker name, and don’t incude the corporation name.
345 346
*When you edit a tracker markdown file for the first time, the domain.tld will already be in the title.*

347 348
## Add the site description

Add a concise one-line description of what the tracker, or the tracker owner, does.
350 351 352

*Usually the tracker sites have vague marketing spiel to describe themselves. Often a clearer description can be found in their privacy policy. If you can’t find a concise description in their own words, try to find their entry on [Wikipedia](, Bloomberg or Crunchbase.*

353 354
Other useful tools:

* [Wikipedia](
356 357 358 359 360 361 362 363 364 365 366 367

## Include references in Notes

* Whether it’s the domain whois, or where you found the site description, include a link back to every source in the Notes section.
* Include a link to the tracker/corporation Privacy Policy (if it exists!)
* If you end up looking through the source file to find more information, you can include relevant code snippets in markdown.

*You can use sub-lists in Notes by using indented lists in markdown.*
*[See the Demandbase tracker for an varied use of Notes](*

# Handling duplicate trackers

Loads of trackers have multiple domains for the same tracker, or group of trackers. In this case, we don’t want duplicate entries that don’t stay in sync.

1. The first tracker found and investigated is the canonical tracker.

372 373 374 375 376
2. Any further trackers with the same name/owner should link to the canonical tracker in place of the description. *Example from [ tracker](*

	> See [](/trackers/

378 379 380 381 382
3. The Ethical Design Violations are still necessary, as the type of violation might vary between the domains.

4. The Block Rule is still necessary, as it blocks this specific domain.

5. The only Notes necessary is the source for the domain origin. Any other notes can be added to the canonical tracker.

384 385 386
Read more in the [Better Content styleguide](

[Discussions on the Investigations processes can be found on the forum](