android
#Android picks of the day:
➡️ @WeAreFairphone - Community account for ethical manufacturer of Android phones
➡️ @Androidauth - Tech news site about Android-based devices
➡️ @androidfaithful - Podcast about Android news
➡️ @androidweekly - Android development newsletter
➡️ @droidapp - Dutch-language Android news site
➡️ @paug - Paris Android user group (in French)
➡️ @e_mydata (OS) & @murena (phones) - Makers of de-Googled Android OS, also sell phones with de-Googled OS preinstalled
🧵 1/6
Oh lol.. I just managed to export a working #Android build for the first time yay!
It does uses an older API (29) for now but it should work!
#introduction après quelque temps sur mastodon :
- intéressé (assez pour y passer trop de temps) par les outils informatiques du monde #libre en commençant par #linux (#MXlinux user here) mais aussi #android et #foss
- réfléchit aux outils libres... qui libèrent ! notamment autour de la #décentralisation et du #smallweb #smolweb
- kiffe la musique du #Mali
- de manière très originale aime la #nature, les #arbres, et développe ses compétences en #permaculture
- un peu de #photographie de rue
#XMPP enthusiasts out there: what would you say the ultimate Achilles heel of the XMPP ecosystem is, at present? Fragmentation of clients? What?
My sense is that it's this: when one goes to store an XMPP address in one's addressbook, there doesn't seem to be standard way to store an XMPP address. #Android doesn't have that as an allowable field, and #Thunderbird and #Nextcloud have an "Instant Messaging" field, where the type can be set to "XMPP". But are these two compatible with each other when trying to sync between them? Edit: Yes, but there's a catch: *the XMPP address must be prefixed with "xmpp:"*
So "user@foo.bar" is not an OK XMPP address, but "xmpp:user@foo.bar" is.
Then to make matters worse, now there's a wish to change the labeling of "XMPP Address" to "Chat ID": https://gultsch.social/@daniel/114012904576436518
It might be a long time before the address synchy-ness ever works again between Android <-> #Davx5 <-> Nextcloud <->Thunderbird
Note: Android allows a "Jabber" type for an IM address, where you *don't* prefix the address with "xmpp:".
(#DeltaChat gets to gloat hard here, as they have plain-old email addresses)
#prosody #conversations #gajim #dino #snikket #monocles #monal
Even though #Signal *itself* has sound security - taken in isolation - it's always moored in an ecosystem (that of smartphones which run #iOS or #Android) which, by default, have #AI set up to shoulder-surf Signal, sending reports back to the mothership. In #iOS, that AI is called "#Apple Intelligence", and in #Android, it's called #Google Assistant. Repeat, these are on by default. *Only a small percentage of your family, friends, colleagues, and fellow country-persons will pain-stakingly disable these.*
Sure, Signal itself is secure by default, but "a chain is only as strong as its weakest link". And the weakest link is the ecosystem which Signal is moored in - that of smartphones policed and patrolled by AI, which report back to their respective motherships *in a strong majority of cases*.
Alternatives like #Deltachat (for normies willing to open their wallets/purses to rent an auto-crypt-compatible email address) and #XMPP (easily free to use, however realistic and mature only for non-iOS/#MacOS-users at present) have comparable E2E encryption. Deltachat and XMPP *don't* require smart-phone "moorings" - thereby making it much more realistic to dodge the almost-pervasively AI-patrolled ecosystems.