![](https://media.kbin.social/media/7b/d0/7bd041d4dca0ad870d437567de6f895c25a9e9a0eb1fe7641d279e9b893b0496.png)
![](https://lemmy.world/pictrs/image/0943eca5-c4c2-4d65-acc2-7e220598f99e.png)
Lemmy stores who upvoted what but does not make it easily available to everyone like kbin does - you can set up a Lemmy instance to grab upvoted and read them from the DB if you are so inclined, or you could just look at kbin to see the same info
Some dude that enjoys working on open source projects, reverse engineering, 3d printing, experimenting with 3d graphics and lots of other tech hobbies.
Currently working on the kbin API: https://codeberg.org/Kbin/kbin-core/pulls/357
Games I play:
Shows I like:
Book series I enjoy:
Lemmy stores who upvoted what but does not make it easily available to everyone like kbin does - you can set up a Lemmy instance to grab upvoted and read them from the DB if you are so inclined, or you could just look at kbin to see the same info
Looking in ImageRepository.php
it doesn’t appear that images have their extra data stripped. Also testing it on my dev instance showed that GPS data remained in the image. Should be an easy fix since all image uploads are processed through that repository.
Edit: In fact there’s already an issue open for it - https://codeberg.org/Kbin/kbin-core/issues/374
Actually they’re still active - if you view from lemmy.world they last posted 3 hours ago, but if you view from your instance their last post was 9 days ago
Apparently it was like this when the Digg migration happened - give it a few weeks and it’ll die down as people get it out of their system
And then make it a pull request on the front end’s repo!
A single health check call a minute by a single app is nothing compared to real world usage