Yep. It's due to the embedded tweets. Any site that allows for tweet embeds has those. Unfortunately they're mostly an unavoidable fact-of-life because even just clicking on a twitter link will activate those same trackers. Only solution would be to never click on a twitter link or read a twitter-embedded post.
I just recently learned that you can add some code to the html that tells the browser not to tell linked sites where you came from when you click links.
Though you're better off just putting a plugin in your own browser that refuses to send referrers.
Yep. It's due to the embedded tweets. Any site that allows for tweet embeds has those. Unfortunately they're mostly an unavoidable fact-of-life because even just clicking on a twitter link will activate those same trackers. Only solution would be to never click on a twitter link or read a twitter-embedded post.
I just recently learned that you can add some code to the html that tells the browser not to tell linked sites where you came from when you click links.
Though you're better off just putting a plugin in your own browser that refuses to send referrers.
It’s much better to set a Referrer-Policy header, as the browser will honor this.
But yeah, if it’s done through JavaScript and info is added to the URL, then there isn’t much you can do apart from using something like Neat URL.
Oh yeah, I remember years ago I read an article saying javascript can just straight up grab your browsing history somehow.
could just do a proxy... basically it'd save the screenshot or raw code of the tweet and render the image or raw HTML here.