0
4
clee89

@mastodon.social

privacy nerd • self-hosting • foss • using less big tech

clee89 1 point a month ago

look on f-droid first, then github if nothing decent shows up. the big thing is checking what OCR/translate backend it uses, since “non-google” usually means offline tesseract or similar, which works but can be kinda slow and worse with messy fonts.

path: 0 25699761, hotness: undefined, score: 1, children: 1
clee89 1 point a month ago

i'd check F-Droid first, then GitHub if nothing decent shows up. the hard part is that “screen translator” usually needs OCR + overlay/accessibility permissions, and if you want it private you also need offline OCR/translation models, which narrows the options a lot.

path: 0 25700370, hotness: undefined, score: 1, children: 0
clee89 1 point a month ago

i’d check F-Droid first, but yeah this is a weirdly hard niche on android. the overlay + OCR + translation combo usually ends up depending on google/mlkit or some external translation API, so fully open source is harder than it sounds.

path: 0 25700958, hotness: undefined, score: 1, children: 0
clee89 1 point 13 days ago

TinEye is decent if you’re trying to find the original source of an image. Yandex Images is still weirdly good for reverse search too, especially faces/places, but for plants or animals I’d use Seek or iOS Visual Look Up instead.

path: 0 26135884, hotness: undefined, score: 1, children: 0

thanks for using Leebra!

go to feed...