#FreeBSD server with #musicpd and #sndio backend in the basement, controlled by #MALP App installed from #fdroid ...

#FreeBSD thin client (rescued from eBay) in the living room, connected to a high end #DAC, humble amplifier, speakers from a local manufacturer.

A music collection that includes #mp3 converted on a 386 computer running #linux decades ago.

An endless source of #happiness .

Edit: Forgot to mention the coffee out of a #Bezzera BZ10

#FreeBSD server with #musicpd and #sndio backend in the basement, controlled by #MALP App installed from #fdroid ...

#FreeBSD thin client (rescued from eBay) in the living room, connected to a high end #DAC, humble amplifier, speakers from a local manufacturer.

A music collection that includes #mp3 converted on a 386 computer running #linux decades ago.

An endless source of #happiness .

Edit: Forgot to mention the coffee out of a #Bezzera BZ10

I bought an #Android 4.3 tablet (#Alcatel onetouch, 18 £). Sure it is outdated but is sufficient. I found several great apps via #fdroid and transferred them via Bluetooth (saved as txt) from my current phone to the old tablet (tablet certificate expired, need to update this). Is there any resource to find more apps in the meantime? I looked at #izzyondroid a bit.

@IzzyOnDroid do you have be chance a filter for the minimum Android version I missed in the web interface?

#android43#FediHelp

@fdroidorg i removed the broken 142.0 instance from my phone keeping all data.
Then I accessed #fdroid via the app selected version 141.0.2 and selected "install". Guess what happened: the broken version 142.0 was installed😠
OK, uninstalled it again, downloaded the 141.0.2 and installed that via #adb .
Now the latest useable version is running. OK - I know the risks😮

***** Google's plans to restrict sideloading on Android are an authoritarian wet dream come true *****

Let me be really clear about how horrifically dangerous #Google's plans are to restrict #Android sideloading to "verified developers" (that is, entities for which Google has full verified identity and associated information that they could hand over to authorities on demand).

This means that even though you own your Android device, you cannot install apps obtained from ANY source (except perhaps apps you build yourself that will only be permitted to run on your own device) unless Google knows pretty much everything about who created that app.

The ways that this could be abused are so numerous I won't even start listing them here, other than to note that it is absolutely horrific overreach by Google and at least appears to be Google bending over for abusive government demands, and could put already vulnerable individuals and groups at even more risk.

Absolutely disgusting.

L

@lauren how is this impacting the #fdroid project? @fdroidorg ?
Problemulv
Problemulv boosted

Svar til digitaliseringsministeriet (1/2)

Hej,

Jeg forstår

"For at opnå høj sikkerhed om den kommende app for aldersverifikation er det et krav, at appens integritet sikres, så der fx ikke kan laves falske apps."

sådan at I påtænker at bruge google play integrity api, og den tilsvarende funktion hos apple.

Dette er jo et problem for alle der ikke ønsker at lade sine data misbruge af google, eller overgive sig til den uønskede kommercielle overvågning fra nogen af de amerikanske big-tech-selskaber.

Det rigtige at gøre er selvfølgelig at I frigiver appen som open source og publicere den (også) via F-Droid, så den bliver tilgængelig for kritiske brugere også. Med F-Droid kan i bruge 'reproducible builds' og deres verification funktion til at sikre at jeres app er intakt, se https://f-droid.org/docs/Reproducible_Builds/

Dette er et svar på denne tekst: https://alundnc.dynv6.net/index.php/s/Gy6qt5x8prRjSsE

#privacy #fdroid #dkpol #eupol #aldersverifikaiton #ageverification

Svar til digitaliseringsministeriet (1/2)

Hej,

Jeg forstår

"For at opnå høj sikkerhed om den kommende app for aldersverifikation er det et krav, at appens integritet sikres, så der fx ikke kan laves falske apps."

sådan at I påtænker at bruge google play integrity api, og den tilsvarende funktion hos apple.

Dette er jo et problem for alle der ikke ønsker at lade sine data misbruge af google, eller overgive sig til den uønskede kommercielle overvågning fra nogen af de amerikanske big-tech-selskaber.

Det rigtige at gøre er selvfølgelig at I frigiver appen som open source og publicere den (også) via F-Droid, så den bliver tilgængelig for kritiske brugere også. Med F-Droid kan i bruge 'reproducible builds' og deres verification funktion til at sikre at jeres app er intakt, se https://f-droid.org/docs/Reproducible_Builds/

Dette er et svar på denne tekst: https://alundnc.dynv6.net/index.php/s/Gy6qt5x8prRjSsE

#privacy #fdroid #dkpol #eupol #aldersverifikaiton #ageverification

I am so appreciative of #FDroid, but holy fuck, it needs to improve fundamentally. Whether it's the recent server issues, which prevent new apps from being released because they didn't wanna upgrade their servers or just the whole release process. It all needs an overhaul.

Don't get me wrong, I'm entitled AF. I hold my hands up and admit that. But I'm an #Android enthusiast. I really enjoy my devices and look forward to each software update. F-Droid is supposed to offer peace of mind, enabling users to get open source software without the security concerns that would arise from random GitHub APKs. They often say to developers, submit your software and 3 days later it'll be in the repo. To me, that's not good enough. But as I said, I'm entitled. Honestly though, waiting 3 days for what could be a security critical release just isn't good enough. But I watched something get submitted 6 days ago and it's still not in the repository. The developer reached out and asked if anything was wrong and the response was "Nothing is wrong. Not sure when it will be available though." Huh? So even when you exceed your three days, doubling it, you can't even provide an explanation? F-Droid is a massive project being run like it's an after school project. It needs to be better because a lot of people rely on it. If other repositories can update daily, so should F-Droid be able to too.

Neil Brown
Neil Brown boosted

FYI: KOReader just got a version update to 2025.08 nicknamed "Parasol" and the inline/OTA update for my Kobo Libra 2 ereader went fine. It should reach F-Droid at some point soon for Android-based devices (Boox, older Tolino, etc.). Wallabag seems fine with the update though I didn't check all of the installed plugins.
https://github.com/koreader/koreader/releases

#KOReader #ereader #kobo #tolino #boox #fdroid #books #wallabag

FYI: KOReader just got a version update to 2025.08 nicknamed "Parasol" and the inline/OTA update for my Kobo Libra 2 ereader went fine. It should reach F-Droid at some point soon for Android-based devices (Boox, older Tolino, etc.). Wallabag seems fine with the update though I didn't check all of the installed plugins.
https://github.com/koreader/koreader/releases

#KOReader #ereader #kobo #tolino #boox #fdroid #books #wallabag

Откуда столько обновлений прилетело? Впервые такое вижу. При том недели полторы-две назад обновляла всё 🤷. С #fdroid что-то случилось?