this post was submitted on 15 Sep 2024
1401 points (97.3% liked)
Microblog Memes
5731 readers
1368 users here now
A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.
Created as an evolution of White People Twitter and other tweet-capture subreddits.
Rules:
- Please put at least one word relevant to the post in the post title.
- Be nice.
- No advertising, brand promotion or guerilla marketing.
- Posters are encouraged to link to the toot or tweet etc in the description of posts.
Related communities:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
To add to this.
Here’s a website to help you check your own trackability:
https://coveryourtracks.eff.org
It can also help give you advice on how to improve your privacy.
Things that help: (tldr use adblockers but otherwise it’s really about blending into the crowd)
Hard to track: uses Firefox with uBlock origin. Maybe using a popular VPN. Uses an iPhone or a popular model of Android like the Pixel (although Google owning Android/Pixel might mean they get your data anyway…)
Actually very easy to track: uses a niche Chromium-based browser you got from GitHub with niche GitHub project as blockers and a little/known VPN. Uses a niche brand of smartphone with a niche non-Android based OS on it.
That was interesting.
Is there an add-on that changes the header information from an HTTP request to show bogus but common identifying information?
That is crowdsource the most common configurations and set that as the default in the add-on, so now you look like just another face in the crowd.
It’s more than just the header information. The graphics and audio checksum can give away details of what your device is, even if those details don’t match what header information you are sending. That mismatch is itself information they can use.
Brave is the only browser I can actually get a decent score with, too bad it has crypto brainrot