If you connect to <code>https://www.mozilla.org</code> and you are running a tool on your browser to spot third party trackers ([https://www.technologyreview.com/s/601488/largest-study-of-online-tracking-proves-google-really-is-watching-us-all/ https://www.technologyreview.com/s/601488/largest-study-of-online-tracking-proves-google-really-is-watching-us-all/], G. is the monopolist of those) you might see, on 11 October 2018, a connection to YouTube (this belong to Google infrastructure)
== Our collection and "attribution logic" ==
The issue is in attributing When we do a technical analysis we see only domain namenames, for example such as <code>google-analytics.com</code> to a , but the information we want is the companyname (Google) and the product name (Analytics). This example is the simplest, other Googleproduct have domain names without having <code>google</code> in their name, and the product is attributed by looking at the URL. The list used is currently this, and should be maintained/verify if is updated: [https://github.com/vecna/invi.sible.link/blob/master/lib/company.js#L570 company.js], and the attributing of Google product is made based on URL schema and domain name, this should be updated and verify too: [https://github.com/vecna/invi.sible.link/blob/master/lib/google.js#L16 google.js]
== Methodology ==
This list stay in a dedicate format, because should be machine readable, the methodology consists in:
1. # Pick a product , 2. Look for replacement * # Ask yourself: ''Is it a service?'': look at the privacy policy * , ''Is it a software?'': look at the technical specification.3. # Write a small summary, find the most accessible product link.4. # Open the page about the product replacements and add a new product.
====== Product list (and their replacement) ======
