Oh, how did I not notice that before? Now should be fixed.

It's just a simple Flask server. I parse the user-agent using the user_agents Python library, apply some conditionals upon the result, render the image using Pillow and send it to the user.

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

That's weird. The extension should definitely work with the image, as that's what I used when building this quick demo. Does the content of a site like this update?

Thought about adding the user's location, but was worried PythonAnywhere could somehow cache the image between multiple people.

Yeah, I just use whatever the user_agents Python library gives me as user_agent.os.family.

You could also send the image through a DM if you want to find a particular user

The user-agent detection definitely isn’t great. If it doesn't recognize a client, it just says unknown. But that wasn't the main point of the post anyway, this was just meant as a quick proof of concept for anyone curious.

The user-agent detection definitely isn't great, this was just meant as a quick proof of concept for anyone curios.

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.

I've also started working on my own Lemmy app (in NativeScript). Maybe we should all create a community to share insights.