|How many trackers does a single Chrome extension need?|
|https://pixel.getpaidfordata.com/ (manifest.json, background.html)|
|Probably wouldn't even have noticed if that last one wasn't sending my browsing history over the internet /in plain text/.|
It gets worse than that.
Some servers I manage were getting crawlers hitting urls with user-agent 'niki-bot'. The URLs were not publically accessible URLs - they were URLs of internal or administrative backend pages of various apps (such as Jenkins configuration URLs, which require staff authentication).
The nature of the URLs allowed us to pinpoint that they were all URLs visited by a specific user in the organisation. That user had installed this chrome extension 'awesomeschreesnot'.
In other words: not only is the extension tracking you, but they, or the advertisers they are selling the data to, return to conduct reconnaissance of all websites you visit, for who knows what purpose.
See another report of this by someone else: https://groups.google.com/forum/#!msg/google-appengine/jEihs3D7Gig/eM9xuJLfnRgJ
Is this still the case with the "relaunched" Awesome Screenshot (https://www.awesomescreenshot.com)?