# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 3
# self = https://watcher.sour.is/conv/yfln7na
@BLMG Hi mate, how are you? Did you know that the &utm_source=silverchair&utm_medium=email&utm_campaign=article_alert-jama&utm_content=olf&utm_term=050323 part of your link is tracking you and the people who click the link as a whole for advertisement or otherwise campaigns? Collecting Campaign Data - Google < for some information. I'm just asking if you knew, and perhaps what your policy is with sharing these GET requests with your links? Personally I always delete them when I can.

You know that every link originating from inside facebook app to outside it is appended with a ?fbclid=HASH and once the client clicks it they are actually (unless you workaround this, it's a pain) not given a choice as to their data being collected off of a simple hyperlink?
@BLMG
Furthermore interesting is that suppose facebook and google are married, cuz they are, and you pop off facebook to a new tab with a facebook click id in the query string (the part after the ?, dunno if you know this, we just met) and the resulting page includes google analytics, what do you think the odds are that 15 more clicks to google SEO hits and you've actually strung together a chain of tracking your whereabouts on the internet?

As you may or may not know, a website when a hit reaches it, the webserver has a parameter field called the referrer (link) and based on the website's own I think it's cross origin request something (CORS) it can actually know the full URI (potentially) of the page you were at before you got there. This is a webserver thing, just a thing that's there.

So if pages are sending with these query strings, and places are recieving for these GET request parameters (if you don't navigate far from google and on the upper web) then google / fb are tracking u
I am chunk, I host XMPP and do linux stuff, even if you knew that nice to meet ya :) But isn't it funny how that works eh.