Commit ada87679 authored by Laura Kalbag's avatar Laura Kalbag

Tidy up some of the markdown formatting in the readme

parent 5be4e66a
......@@ -207,19 +207,19 @@ Currently, you need to have commit rights to the Content repository to use the B
## Find who owns and runs the tracker
1. Start by editing the tracker: `better/edit drafts/trackers/somedoma.in`.
* 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.
* 2. First, enter the domain 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.
* 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:
* 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 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.
......@@ -231,17 +231,18 @@ Other useful tools:
## Add the tracker/site name to the tracker markdown file
* The name should be formatted as:
The name should be formatted as:
```markdown
**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.
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.
*When you edit a tracker markdown file for the first time, the domain.tld will already be in the title.*
## Add the site description
* Add a concise one-line description of what the tracker, or the tracker owner, does.
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.*
......@@ -264,9 +265,11 @@ Other useful tools:
1. The first tracker found and investigated is the canonical tracker.
2. Any further trackers with the same name/owner should link to the canonical tracker in place of the description. *Example from [addthisedge.com tracker](https://better.fyi/trackers/addthisedge.com/):*
```markdown
> See [addthis.com](/trackers/addthis.com/).
```
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.
......
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