TehBamski@lemmy.world to Microblog Memes@lemmy.worldEnglish · 7 个月前Gott'emi.imgur.comimagemessage-square24fedilinkarrow-up11.21Karrow-down121
arrow-up11.19Karrow-down1imageGott'emi.imgur.comTehBamski@lemmy.world to Microblog Memes@lemmy.worldEnglish · 7 个月前message-square24fedilink
minus-squaresurewhynotlem@lemmy.worldlinkfedilinkEnglisharrow-up4arrow-down1·7 个月前Lemmy should do this automatically on the server to help with our filters. How do we submit a feature request?
minus-squarepearsaltchocolatebar@discuss.onlinelinkfedilinkEnglisharrow-up4·7 个月前That would be a pretty expensive feature request.
minus-squareSharpieThunderflare@lemmy.calinkfedilinkEnglisharrow-up6·7 个月前OCR and especially AI image processing takes a lot of computing power, much much more than filtering plain text.
minus-squareqaz@lemmy.worldlinkfedilinkEnglisharrow-up1·edit-27 个月前Last time I checked tesseract had pretty good performance, but I may be mistaken.
minus-squareSeptimaeus@infosec.publinkfedilinkEnglisharrow-up2·6 个月前You’re right. I’ve preferred it in mobile applications where specialized hardware is not guaranteed and battery use matters. Results are consistent.
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.