Can we move away from the habit of just copy-pasting clickbait video titles with no information as to what they’re actually about? Lemmy gives you a description field, you have the power to summarise videos which should really be blog posts!
I’m using it to type this comment and I REALLY like it! But I will say it tries to do punctuation for me, and that drives me nuts.
(Video is about an open source voice to text, input method for Android, by the way.)
What’s the name of it? Then I don’t have to watch a video
Futo Voice Input, and there are links in the post ☺️ Weirdly, it doesn’t seem to be on Fdroid (yet?), but you can install it as an APK from their website.
I’m going with yet. They do mention an F-Droid build on GitLab.
There are four build flavors:
dev- for development, includes Play Store billing and all payment methods, auto-update, etcplayStore- Play Store build, does not include auto-update and only includes Play Store billingstandalone- does not include Play Store billing library, includes auto-updatefDroid- does not include Play Store billing nor auto-update
Gotcha. I missed that on their GitLab page, Thank you for pointing it out to me!
deleted by creator
The reported tracker is ACRA, a crash report library (https://github.com/ACRA/acra).
I digged a bit into the source code and the apk. From looking at the code alone one can’t tell if the crash report is actually enabled, the build configuration depends on some unpublished file. But looking into the apk allows to reconstruct it. These are my findings:
- the usage is implemented here: https://gitlab.futo.org/alex/voiceinput/-/blob/master/app/src/main/java/org/futo/voiceinput/CrashLoggingApplication.kt
- the crash handler is compiled in and also enabled (BuildConfig.ENABLE_ACRA=true)
- the crash handler is configured to dialog mode. According to the ACRA documentation (https://www.acra.ch/docs/Interactions#dialog) that means that user interaction is required for sending (a popup dialog with a cancel button).
- the upload domain is crash.sapples.net
- the dialog can’t be disabled via settings
- the usage of ACRA is missing in the licenses and about dialogs (https://gitlab.futo.org/alex/voiceinput/-/blob/master/app/src/main/assets/license-list.html)
- the privacy policy is correctly stated (https://voiceinput.futo.org/VoiceInput/PrivacyPolicy)
4.1. If the app crashes, you may be asked if you wish to submit a crash report. If you accept, your device information and crash details will be sent to us for the purposes of investigating the crash and improving the software.
Can you give more details of the scan result? Exodus only lists the Play store version. I installed the F-Droid version but Exodus app reports it as “same version” and just shows the clean Google Play Store results. This is obviously wrong, the SHA1 listed for the Play Store version on the Exodus website is different compared to the F-Droid .apk I have installed. Sadly the Exodus website does not support scanning F-Droid apps from third-party repos so I have no idea how to scan it.
That being said, according to the privacy policy (https://voiceinput.futo.org/VoiceInput/PrivacyPolicy), the F-Droid .apk version should have some kind of crash report build-in. So I could imagine that this might get flagged.
deleted by creator
Thank you, I’ll look into it.
deleted by creator
Unfortunetly they go with their own custom licence and AFAIK it’s not open source as it does not allow commercial use.
I didn’t install/scan it myself, but the exodus site shows no trackers on Google play version. https://reports.exodus-privacy.eu.org/en/reports/org.futo.voiceinput/latest/
deleted by creator
I figure if I lurk here someone will come along and breakdown whether this is legit to install or not
Louis Rossmann is a respectable person in the open source/right to repair arena
Right on, that helps to know, thank you
Howsabout you try it and let us all know if your phone gets hot?
I tried it on my device… Works great!
But it’s just a Voice to Text utility at the moment, so only where there’s a mic icon for said VTT applications. But they’re working on integration with open source keyboards and also suggested the possibility that they’d make one of their own keyboards.
deleted by creator
Damn. I appreciate that you did that leg work for the rest of us
From reading other posts it sounds like it is only for crash reporting and that the user has to click to provide the report in the event of a crash. It also appears to be documented in their policy docs so it’s not exactly like it’s anything underhanded.
If the user doesn’t trust that their data will be safe, couldn’t the domain attached to the tracker found by Classyshark be blocked using something like NextDNS or RethinkDNS to prevent any data from connecting to said domain?
deleted by creator
