Commit df6a0abe authored by Laura Kalbag's avatar Laura Kalbag

Start putting headings under investigation process and add info about adding tracker descriptions

parent fa8f9e00
......@@ -205,19 +205,27 @@ The Blockdown parser in Better supports all of the [WebKit content blocking rule
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](https://source.ind.ie/better/content) without commit rights.
## Find who owns and runs the tracker
1. Start by editing the tracker: `better/edit drafts/trackers/somedoma.in`. 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. First, enter the domain into your browser in a private window to see if it loads.
3. If it doesn’t load, or if you get a blank page, perform a whois. We are currently using http://whois.domaintools.com 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 somedoma.in`
4. Some trackers use a domain proxy or a cloaking service (e.g., Domains by Proxy) to further hide their origins. In this case, open up the source of some sites that the tracker originated on in the Web Developer console (Timeline view) of Safari (or in the web inspector of your browser of choice) and try to recreate the original call. That might give you more clues about its origin. (To find which sites a tracker is on, perform a search on the *~/better.fyi/drafts/sites folder*. For example, you can open up the folder in Sublime Text and do a global search for the tracker name.)
4. Some trackers use a domain proxy or a cloaking service (e.g., Domains by Proxy) to further hide their origins. In this case, open up the source of some sites that the tracker originated on in the Web Developer console (Timeline view) of Safari (or in the web inspector of your browser of choice) and try to recreate the original call. That might give you more clues about its origin. (To find which sites a tracker is on, perform a search on the *~/better.fyi/drafts/trackers folder*. For example, you can open up the folder in Sublime Text and do a global search for the tracker name.)
Other useful tools:
* [Wikipedia](wikipedia.org)
* [Mozilla Lightbeam](https://www.mozilla.org/en-US/lightbeam/)
## Add the site description
1. Add a concise one-line description of what the tracker, or the tracker owner, does.
*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](https://wikipedia.org), Bloomberg or Crunchbase.*
# Content authoring guidelines
* Be brief: do not quote the whole privacy policy; pick out interesting bits.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment