𝔗𝚎𝚑 𝔅𝚊𝚖𝚜𝚔𝚒@lemmy.world to Microblog Memes@lemmy.worldEnglish · 1 year agoGott'emi.imgur.comimagemessage-square24linkfedilinkarrow-up11.21K
arrow-up11.21KimageGott'emi.imgur.com𝔗𝚎𝚑 𝔅𝚊𝚖𝚜𝚔𝚒@lemmy.world to Microblog Memes@lemmy.worldEnglish · 1 year agomessage-square24linkfedilink
minus-square🇰 🌀 🇱 🇦 🇳 🇦 🇰 🇮 🏆@yiffit.netlinkfedilinkEnglisharrow-up18·1 year agoThis is really what we need from things like Google Lens and things that can scan images for text; filtering out stuff based on text visible in an image.
minus-squareAce! _SL/S@ani.sociallinkfedilinkEnglisharrow-up12·1 year agoFuck Google, just use tesseract
minus-squaresurewhynotlem@lemmy.worldlinkfedilinkEnglisharrow-up4·1 year agoLemmy should do this automatically on the server to help with our filters. How do we submit a feature request?
minus-squarepearsaltchocolatebar@discuss.onlinelinkfedilinkEnglisharrow-up4·1 year agoThat would be a pretty expensive feature request.
minus-squareSharpieThunderflare@lemmy.calinkfedilinkEnglisharrow-up6·1 year agoOCR and especially AI image processing takes a lot of computing power, much much more than filtering plain text.
minus-squareqaz@lemmy.worldlinkfedilinkEnglisharrow-up1·edit-21 year agoLast time I checked tesseract had pretty good performance, but I may be mistaken.
minus-squareSeptimaeus@infosec.publinkfedilinkEnglisharrow-up2·1 year agoYou’re right. I’ve preferred it in mobile applications where specialized hardware is not guaranteed and battery use matters. Results are consistent.
This is really what we need from things like Google Lens and things that can scan images for text; filtering out stuff based on text visible in an image.
Fuck Google, just use tesseract
yeh!
Lemmy should do this automatically on the server to help with our filters.
How do we submit a feature request?
That would be a pretty expensive feature request.
Why?
OCR and especially AI image processing takes a lot of computing power, much much more than filtering plain text.
Last time I checked tesseract had pretty good performance, but I may be mistaken.
You’re right. I’ve preferred it in mobile applications where specialized hardware is not guaranteed and battery use matters. Results are consistent.