☆ Yσɠƚԋσʂ ☆ to Open Source@lemmy.mlEnglish • 8 months agoMicrosoft open-sourced a Python tool for converting files and office documents to Markdowngithub.comexternal-linkmessage-square23fedilinkarrow-up1132arrow-down16
arrow-up1126arrow-down1external-linkMicrosoft open-sourced a Python tool for converting files and office documents to Markdowngithub.com☆ Yσɠƚԋσʂ ☆ to Open Source@lemmy.mlEnglish • 8 months agomessage-square23fedilink
minus-square@utopiah@lemmy.mllinkfedilink1•8 months agoThanks for the clarification. I checked the code you linked and noticed recognize_google and seems it’s relying on https://github.com/Uberi/speech_recognition which then seems to rely on https://github.com/Uberi/speech_recognition/blob/master/speech_recognition/recognizers/google.py so basically are they using an API, sending all the audio data to Google servers?
minus-square@django@discuss.tchncs.delinkfedilinkEnglish1•8 months agoYes, this is how I read it as well. The library would support to use a local model, but they decided to just send the audio data to Google.
minus-square@utopiah@lemmy.mllinkfedilink3•8 months agoMight open up a GDPR related issue there. I don’t think people using such a library assume they need connectivity nor that their data would be send to a 3rd party.
Thanks for the clarification. I checked the code you linked and noticed
recognize_googleand seems it’s relying on https://github.com/Uberi/speech_recognition which then seems to rely on https://github.com/Uberi/speech_recognition/blob/master/speech_recognition/recognizers/google.py so basically are they using an API, sending all the audio data to Google servers?Yes, this is how I read it as well. The library would support to use a local model, but they decided to just send the audio data to Google.
Might open up a GDPR related issue there. I don’t think people using such a library assume they need connectivity nor that their data would be send to a 3rd party.