![](https://lemmy.ml/pictrs/image/10f7b966-8580-4aa6-aef0-db020875ed9a.png)
![](https://lemmy.world/pictrs/image/0130a5eb-ebd6-402a-961b-6dc94d9541ca.jpeg)
Yup, I’m parsing the user agent with the user_agents
Python library.
If you wanted to target a specific user, you could always send a DM with the image
It does
Looks like your home instance hexbear.net is filtering external images.
Cool, didn’t know some Lemmy instances did this
Thought about adding the user’s location, but was worried PythonAnywhere could somehow cache the image between multiple people. A great demo though!
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.
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.
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.
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.