In addition, Huawei now blocks sideloading Android apps to promote its ecosystem growth.
Well looks like I’m never going to get a device from this manufacturer then.
In addition, Huawei now blocks sideloading Android apps to promote its ecosystem growth.
Well looks like I’m never going to get a device from this manufacturer then.
This. Regulators are a joke
You may want to rework your privacy policy. It contadicts itself:
We do not track your online browsing activity on other online services over time and we do not permit third-party services to track your activity on our site beyond our basic Google Analytics tracking
- Analytics: We do not use any third-party Service Providers to monitor and analyze the use of our Service.
Be careful with those, they can interfere/kill your or your neighbors DSL connection. Terrible to diagnose these.
Antennapod supports syncing with podder.net and gpoddersync
They video was quiet promising. However looking at the app website shows that what was a false promise. The app does track every single launch and sends that to their servers (see privacy policy) not legal without consent in the EU. Calling this “tracker free” is more than misleading here. I’d call it a lie actually.
Have you tried https://github.com/jeena/fxsync-docker? It is a docker compose for selfhosting the new Firefox sync server rewritten in Rust.
Credits: https://lemmy.world/post/5839867
That’s so sad. Uses to buy all my music through them.
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:
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.
Thank you, I’ll look into it.
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.
Keepass on phone, desktop and tablet. Sync serverless via Syncthing.
On Android nothing comes close to gReader Pro with The Old Reader as sync Backend. Sadly the app is discontinued, however the apk can be used just fine.
Not in all situations. And in a way a user will not be aware of. The service or website can define what type of passkey is allowed (based in attestation). You may not be able to acutally use your “movable” keys because someone else decided so. You will not notice this until you actually face such a service. And when that happens, you can be sure that the average user will not understand what ia going on. Not all passkeys are equal, but that fact is hidden from the user.