This post knows where you're viewing it from (Lemmy doesn't proxy external images) [ARCHIVED]
Note: This post now archived and as such no longer works
Syndicated from the fediverse. Read and engage on the original instance.
View original on lemmy.mlView original on lemmy.ml
15 replies
This is possible because Lemmy doesn't proxy external images but instead loads them directly. While not all that bad, this could be used for Spy pixels by nefarious posters and commenters.
Note, that the only thing that I willingly log is the "hit count" visible in the image, and I have no intention to misuse the data.
I guess it knows that it's unknown
I guess mobile clients screw with their fingerprinting method. Also doesn't work on Slide.
Wait what, slideforreddit works for lemmy now?
looks like sync in the screenshot, i think thats what they meant
It sees my phone fine (Chrome on Android)
It's the same for me
I guess Donald Rumsfeld was right.
This is true for most link aggregators that attempt to render external content. Proxying images and videos would dramatically increase costs.
If you care that much about anonymity, use a VPN/Tor and a browser with advanced fingerprinting resistance — tor browser, mullvad browser, or firefox with resist fingerprinting = true.
That makes sense. But I guess there’s these questions: at what resolution? For how long? Maybe the status quo is such because it’s simpler code. The project is still relatively young. I wonder where/how we can discuss these things?
It still adds up fast especially if you run an instance that stores to s3 with a cdn. My mastodon server racked up 1k in cdn usage one month before I switched to local storage no cdn.
My favorite Linux distro: Windows.
This reminds me of those old forum signatures which looked like a signpost, and showed your IP address, browser, OS etc. They were pretty popular back then (when no one cared about their privacy), to the point that some folks even made parody versions of those signatures (like changing the IP to "127.0.0.1" or writing a funny message).
But I'm not on chrome mobile...
*brave