#obtainium — Public Fediverse posts

Code Scan To Clipboard 1.5.0 is out — the simple barcode and QR scanner that copies straight to the clipboard. Faster cold starts (Baseline Profiles), library updates, and you can install/update it via #Obtainium from Codeberg. Find all download options on codescantoclipboard.tkuenneth.dev

Code Scan To Clipboard 1.5.0 is out — the simple barcode and QR scanner that copies straight to the clipboard. Faster cold starts (Baseline Profiles), library updates, and you can install/update it via #Obtainium from Codeberg. Find all download options on codescantoclipboard.tkuenneth.dev

Min Time 2.0.3 is out — your minimalistic talk timer for structuring presentations. Faster cold starts (Baseline Profiles), library updates, and you can install/update it via #Obtainium from Codeberg. Find all download options on https://mintime.tkuenneth.dev/

Min Time 2.0.3 is out — your minimalistic talk timer for structuring presentations. Faster cold starts (Baseline Profiles), library updates, and you can install/update it via #Obtainium from Codeberg. Find all download options on https://mintime.tkuenneth.dev/

Sensitive permissions aren't a Console checkbox. They're the line between using #Android and renting it.

Play can ban a feature the OS already guards with runtime consent. Call Log was the warning. Contacts is the 2026 sequel. Developer verification goes further: an identity checkpoint even for installs outside Play.

FOSS only stays free if we can still ship it. @fdroidorg. #Obtainium. @IzzyOnDroidOrg. Direct.

New on DEV: https://dev.to/tkuenneth/dealing-with-sensitive-permissions-on-android-3icg

#Android #FOSS #DigitalSovereignty

Sensitive permissions aren't a Console checkbox. They're the line between using #Android and renting it.

Play can ban a feature the OS already guards with runtime consent. Call Log was the warning. Contacts is the 2026 sequel. Developer verification goes further: an identity checkpoint even for installs outside Play.

FOSS only stays free if we can still ship it. @fdroidorg. #Obtainium. @IzzyOnDroidOrg. Direct.

New on DEV: https://dev.to/tkuenneth/dealing-with-sensitive-permissions-on-android-3icg

#Android #FOSS #DigitalSovereignty

TKWeek, my versatile date and calendaring tool, is now also available via #Obtainium.

Check it out at https://tkweek.tkuenneth.dev/ and get the app through Obtainium or @fdroidorg

And, no, it is no longer available on Google Play

TKWeek, my versatile date and calendaring tool, is now also available via #Obtainium.

Check it out at https://tkweek.tkuenneth.dev/ and get the app through Obtainium or @fdroidorg

And, no, it is no longer available on Google Play

Be nice is now on Google Play, @IzzyOnDroidOrg, and #Obtainium.

Play for the store. IzzyOnDroid for the FOSS repo. Obtainium if you want the Codeberg APK the moment it ships.

https://benice.tkuenneth.dev/

Thanks @lehtimaeki

#Android #FOSS

Be nice is now on Google Play, @IzzyOnDroidOrg, and #Obtainium.

Play for the store. IzzyOnDroid for the FOSS repo. Obtainium if you want the Codeberg APK the moment it ships.

https://benice.tkuenneth.dev/

Thanks @lehtimaeki

#Android #FOSS

Be nice is now on Google Play, @IzzyOnDroidOrg, and #Obtainium.

Play for the store. IzzyOnDroid for the FOSS repo. Obtainium if you want the Codeberg APK the moment it ships.

https://benice.tkuenneth.dev/

Thanks @lehtimaeki

#Android #FOSS

Be nice is now on Google Play, @IzzyOnDroidOrg, and #Obtainium.

Play for the store. IzzyOnDroid for the FOSS repo. Obtainium if you want the Codeberg APK the moment it ships.

https://benice.tkuenneth.dev/

Thanks @lehtimaeki

#Android #FOSS

Be nice is now on Google Play, @IzzyOnDroidOrg, and #Obtainium.

Play for the store. IzzyOnDroid for the FOSS repo. Obtainium if you want the Codeberg APK the moment it ships.

https://benice.tkuenneth.dev/

Thanks @lehtimaeki

#Android #FOSS

#Obtainium currently doesn't work with @codefloe as it looks like they've hardcoded Codeberg for Forgejo instead of having a generic Forgejo repo solution.

A bug opened:
https://github.com/ImranR98/Obtainium/issues/3212

Not sure how to help solve this. But not being able ot use Obtainium is a huge bloker for hosting OSS Android projects at Codefloe :-(

#Obtainium currently doesn't work with @codefloe as it looks like they've hardcoded Codeberg for Forgejo instead of having a generic Forgejo repo solution.

A bug opened:
https://github.com/ImranR98/Obtainium/issues/3212

Not sure how to help solve this. But not being able ot use Obtainium is a huge bloker for hosting OSS Android projects at Codefloe :-(

#Obtainium currently doesn't work with @codefloe as it looks like they've hardcoded Codeberg for Forgejo instead of having a generic Forgejo repo solution.

A bug opened:
https://github.com/ImranR98/Obtainium/issues/3212

Not sure how to help solve this. But not being able ot use Obtainium is a huge bloker for hosting OSS Android projects at Codefloe :-(

#Obtainium currently doesn't work with @codefloe as it looks like they've hardcoded Codeberg for Forgejo instead of having a generic Forgejo repo solution.

A bug opened:
https://github.com/ImranR98/Obtainium/issues/3212

Not sure how to help solve this. But not being able ot use Obtainium is a huge bloker for hosting OSS Android projects at Codefloe :-(

#Obtainium currently doesn't work with @codefloe as it looks like they've hardcoded Codeberg for Forgejo instead of having a generic Forgejo repo solution.

A bug opened:
https://github.com/ImranR98/Obtainium/issues/3212

Not sure how to help solve this. But not being able ot use Obtainium is a huge bloker for hosting OSS Android projects at Codefloe :-(

There is now a manually created “Incident with GitHub.com”: roughly 20% error rates across the web experience and API traffic, and around 50% error rates for archive downloads and raw repository content. Pull requests, issues, webhooks, and Actions are affected too.

Meanwhile, the component tiles are still green except for Copilot.

The incident text: “GitHub is on fire.”

The dashboard: “🟢 All systems operational.”

A status page as a Kafkaesque escape room.

That matches the failures retrieving commits and Obtainium suddenly being unable to find releases.

#GitHub #GitHubDown #Obtainium #githubstatus #OpenSource #DevOps

Update: The actual trigger

After digging a little deeper, it turns out that the #FDroid version of #Joplin was not the official Android release maintained by Joplin’s maintainer, @laurent22.

The F-Droid build was maintained by muelli, who apparently released Joplin 3.7.2 prematurely. That is what triggered my little sync-update circus in the first place.

That release has since been withdrawn. F-Droid is now back to Joplin 3.6.21 as its latest version, which also matches the version available through the official Joplin website’s alternative Android downloads.

Lesson learned.

Since my shared sync target has already been migrated to the 3.7 format, I’m keeping desktop, tablet, and phone on compatible versions for now. Downgrading again would just mean unnecessarily poking around in sync data and backups.

So, going forward:

• No more Joplin from #FDroid
• Instead, I’ll use #Obtainium to track the official alternative-release channel from @laurent22
• Once #CachyOS and Android officially ship Joplin 3.7+, I’ll switch back to the regular package sources

URL for Obtainium ...

https://github.com/laurent22/joplin-android/releases

Well. That is what happens when an unofficial build deploys a new sync format before the official release channels catch up.

#ArchLinux #CachyOS #Android #ReleaseChannelHell #SyncTroubles

Update: The actual trigger

After digging a little deeper, it turns out that the #FDroid version of #Joplin was not the official Android release maintained by Joplin’s maintainer, @laurent22.

The F-Droid build was maintained by muelli, who apparently released Joplin 3.7.2 prematurely. That is what triggered my little sync-update circus in the first place.

That release has since been withdrawn. F-Droid is now back to Joplin 3.6.21 as its latest version, which also matches the version available through the official Joplin website’s alternative Android downloads.

Lesson learned.

Since my shared sync target has already been migrated to the 3.7 format, I’m keeping desktop, tablet, and phone on compatible versions for now. Downgrading again would just mean unnecessarily poking around in sync data and backups.

So, going forward:

• No more Joplin from #FDroid
• Instead, I’ll use #Obtainium to track the official alternative-release channel from @laurent22
• Once #CachyOS and Android officially ship Joplin 3.7+, I’ll switch back to the regular package sources

URL for Obtainium ...

https://github.com/laurent22/joplin-android/releases

Well. That is what happens when an unofficial build deploys a new sync format before the official release channels catch up.

#ArchLinux #CachyOS #Android #ReleaseChannelHell #SyncTroubles

Update: The actual trigger

After digging a little deeper, it turns out that the #FDroid version of #Joplin was not the official Android release maintained by Joplin’s maintainer, @laurent22.

The F-Droid build was maintained by muelli, who apparently released Joplin 3.7.2 prematurely. That is what triggered my little sync-update circus in the first place.

That release has since been withdrawn. F-Droid is now back to Joplin 3.6.21 as its latest version, which also matches the version available through the official Joplin website’s alternative Android downloads.

Lesson learned.

Since my shared sync target has already been migrated to the 3.7 format, I’m keeping desktop, tablet, and phone on compatible versions for now. Downgrading again would just mean unnecessarily poking around in sync data and backups.

So, going forward:

• No more Joplin from #FDroid
• Instead, I’ll use #Obtainium to track the official alternative-release channel from @laurent22
• Once #CachyOS and Android officially ship Joplin 3.7+, I’ll switch back to the regular package sources

URL for Obtainium ...

https://github.com/laurent22/joplin-android/releases

Well. That is what happens when an unofficial build deploys a new sync format before the official release channels catch up.

#ArchLinux #CachyOS #Android #ReleaseChannelHell #SyncTroubles

Update: The actual trigger

After digging a little deeper, it turns out that the #FDroid version of #Joplin was not the official Android release maintained by Joplin’s maintainer, @laurent22.

The F-Droid build was maintained by muelli, who apparently released Joplin 3.7.2 prematurely. That is what triggered my little sync-update circus in the first place.

That release has since been withdrawn. F-Droid is now back to Joplin 3.6.21 as its latest version, which also matches the version available through the official Joplin website’s alternative Android downloads.

Lesson learned.

Since my shared sync target has already been migrated to the 3.7 format, I’m keeping desktop, tablet, and phone on compatible versions for now. Downgrading again would just mean unnecessarily poking around in sync data and backups.

So, going forward:

• No more Joplin from #FDroid
• Instead, I’ll use #Obtainium to track the official alternative-release channel from @laurent22
• Once #CachyOS and Android officially ship Joplin 3.7+, I’ll switch back to the regular package sources

URL for Obtainium ...

https://github.com/laurent22/joplin-android/releases

Well. That is what happens when an unofficial build deploys a new sync format before the official release channels catch up.

#ArchLinux #CachyOS #Android #ReleaseChannelHell #SyncTroubles

Update: Der eigentliche Auslöser

Nach etwas tieferer Recherche hat sich herausgestellt: Die Joplin-Version bei #FDroid war nicht die offizielle Android-Veröffentlichung von #Joplin-Maintainer @laurent22.

Der F-Droid-Build stammt von muelli und hatte offenbar versehentlich Joplin 3.7.2 freigegeben. Genau dieses Update hat meinen kleinen Sync-Zirkus überhaupt erst ausgelöst.

Die Version wurde inzwischen wieder zurückgezogen. Aktuell ist bei F-Droid wieder Joplin 3.6.21 die neueste verfügbare Version – und das entspricht auch der Version, die auf der offiziellen Joplin-Seite unter den alternativen Android-Downloads angeboten wird.

Wieder was gelernt.

Da mein gemeinsames Sync-Ziel inzwischen bereits auf dem 3.7er-Format liegt, lasse ich Desktop, Tablet und Smartphone vorerst auf den entsprechenden Versionen. Ein Downgrade würde jetzt nur wieder unnötig an Sync-Daten und Backups herumoperieren.

Die Konsequenz für mich:

• Keine Joplin-App mehr aus #FDroid
• Stattdessen die alternativen offiziellen Releases von @laurent22 über #Obtainium
• Sobald #CachyOS und Android offiziell bei Joplin 3.7+ angekommen sind, wechsle ich wieder zu den regulären Paketquellen

Tja. Das kommt davon, wenn ein inoffizieller Build schneller ein neues Sync-Format ausrollt als die offiziellen Release-Kanäle hinterherkommen.

#ArchLinux #CachyOS #Android #ReleaseChannelHell #SyncTroubles

Update: Der eigentliche Auslöser

Nach etwas tieferer Recherche hat sich herausgestellt: Die Joplin-Version bei #FDroid war nicht die offizielle Android-Veröffentlichung von #Joplin-Maintainer @laurent22.

Der F-Droid-Build stammt von muelli und hatte offenbar versehentlich Joplin 3.7.2 freigegeben. Genau dieses Update hat meinen kleinen Sync-Zirkus überhaupt erst ausgelöst.

Die Version wurde inzwischen wieder zurückgezogen. Aktuell ist bei F-Droid wieder Joplin 3.6.21 die neueste verfügbare Version – und das entspricht auch der Version, die auf der offiziellen Joplin-Seite unter den alternativen Android-Downloads angeboten wird.

Wieder was gelernt.

Da mein gemeinsames Sync-Ziel inzwischen bereits auf dem 3.7er-Format liegt, lasse ich Desktop, Tablet und Smartphone vorerst auf den entsprechenden Versionen. Ein Downgrade würde jetzt nur wieder unnötig an Sync-Daten und Backups herumoperieren.

Die Konsequenz für mich:

• Keine Joplin-App mehr aus #FDroid
• Stattdessen die alternativen offiziellen Releases von @laurent22 über #Obtainium
• Sobald #CachyOS und Android offiziell bei Joplin 3.7+ angekommen sind, wechsle ich wieder zu den regulären Paketquellen

URL fur zB Obtainium:

https://github.com/laurent22/joplin-android/releases

Tja. Das kommt davon, wenn ein inoffizieller Build schneller ein neues Sync-Format ausrollt als die offiziellen Release-Kanäle hinterherkommen.

#ArchLinux #CachyOS #Android #ReleaseChannelHell #SyncTroubles

Update: Der eigentliche Auslöser

Nach etwas tieferer Recherche hat sich herausgestellt: Die Joplin-Version bei #FDroid war nicht die offizielle Android-Veröffentlichung von #Joplin-Maintainer @laurent22.

Der F-Droid-Build stammt von muelli und hatte offenbar versehentlich Joplin 3.7.2 freigegeben. Genau dieses Update hat meinen kleinen Sync-Zirkus überhaupt erst ausgelöst.

Die Version wurde inzwischen wieder zurückgezogen. Aktuell ist bei F-Droid wieder Joplin 3.6.21 die neueste verfügbare Version – und das entspricht auch der Version, die auf der offiziellen Joplin-Seite unter den alternativen Android-Downloads angeboten wird.

Wieder was gelernt.

Da mein gemeinsames Sync-Ziel inzwischen bereits auf dem 3.7er-Format liegt, lasse ich Desktop, Tablet und Smartphone vorerst auf den entsprechenden Versionen. Ein Downgrade würde jetzt nur wieder unnötig an Sync-Daten und Backups herumoperieren.

Die Konsequenz für mich:

• Keine Joplin-App mehr aus #FDroid
• Stattdessen die alternativen offiziellen Releases von @laurent22 über #Obtainium
• Sobald #CachyOS und Android offiziell bei Joplin 3.7+ angekommen sind, wechsle ich wieder zu den regulären Paketquellen

URL fur zB Obtainium:

https://github.com/laurent22/joplin-android/releases

Tja. Das kommt davon, wenn ein inoffizieller Build schneller ein neues Sync-Format ausrollt als die offiziellen Release-Kanäle hinterherkommen.

#ArchLinux #CachyOS #Android #ReleaseChannelHell #SyncTroubles

Update: Der eigentliche Auslöser

Nach etwas tieferer Recherche hat sich herausgestellt: Die Joplin-Version bei #FDroid war nicht die offizielle Android-Veröffentlichung von #Joplin-Maintainer @laurent22.

Der F-Droid-Build stammt von muelli und hatte offenbar versehentlich Joplin 3.7.2 freigegeben. Genau dieses Update hat meinen kleinen Sync-Zirkus überhaupt erst ausgelöst.

Die Version wurde inzwischen wieder zurückgezogen. Aktuell ist bei F-Droid wieder Joplin 3.6.21 die neueste verfügbare Version – und das entspricht auch der Version, die auf der offiziellen Joplin-Seite unter den alternativen Android-Downloads angeboten wird.

Wieder was gelernt.

Da mein gemeinsames Sync-Ziel inzwischen bereits auf dem 3.7er-Format liegt, lasse ich Desktop, Tablet und Smartphone vorerst auf den entsprechenden Versionen. Ein Downgrade würde jetzt nur wieder unnötig an Sync-Daten und Backups herumoperieren.

Die Konsequenz für mich:

• Keine Joplin-App mehr aus #FDroid
• Stattdessen die alternativen offiziellen Releases von @laurent22 über #Obtainium
• Sobald #CachyOS und Android offiziell bei Joplin 3.7+ angekommen sind, wechsle ich wieder zu den regulären Paketquellen

Tja. Das kommt davon, wenn ein inoffizieller Build schneller ein neues Sync-Format ausrollt als die offiziellen Release-Kanäle hinterherkommen.

#ArchLinux #CachyOS #Android #ReleaseChannelHell #SyncTroubles

Update: Der eigentliche Auslöser

Nach etwas tieferer Recherche hat sich herausgestellt: Die Joplin-Version bei #FDroid war nicht die offizielle Android-Veröffentlichung von #Joplin-Maintainer @laurent22.

Der F-Droid-Build stammt von muelli und hatte offenbar versehentlich Joplin 3.7.2 freigegeben. Genau dieses Update hat meinen kleinen Sync-Zirkus überhaupt erst ausgelöst.

Die Version wurde inzwischen wieder zurückgezogen. Aktuell ist bei F-Droid wieder Joplin 3.6.21 die neueste verfügbare Version – und das entspricht auch der Version, die auf der offiziellen Joplin-Seite unter den alternativen Android-Downloads angeboten wird.

Wieder was gelernt.

Da mein gemeinsames Sync-Ziel inzwischen bereits auf dem 3.7er-Format liegt, lasse ich Desktop, Tablet und Smartphone vorerst auf den entsprechenden Versionen. Ein Downgrade würde jetzt nur wieder unnötig an Sync-Daten und Backups herumoperieren.

Die Konsequenz für mich:

• Keine Joplin-App mehr aus #FDroid
• Stattdessen die alternativen offiziellen Releases von @laurent22 über #Obtainium
• Sobald #CachyOS und Android offiziell bei Joplin 3.7+ angekommen sind, wechsle ich wieder zu den regulären Paketquellen

URL fur zB Obtainium:

https://github.com/laurent22/joplin-android/releases

Tja. Das kommt davon, wenn ein inoffizieller Build schneller ein neues Sync-Format ausrollt als die offiziellen Release-Kanäle hinterherkommen.

#ArchLinux #CachyOS #Android #ReleaseChannelHell #SyncTroubles

Hi @CoMaps.
I’m unable to install CoMaps from Codeberg using Obtainium on GrapheneOS.

Obtainium correctly detects `CoMaps-26080703-main-release.apk`, but the download repeatedly fails because the connection is interrupted. The repository URL and APK filter appear to be correct.

Is this a known issue with the Codeberg release download, or is a different Obtainium configuration required?

#CoMaps #Obtainium #GrapheneOS #Codeberg #OpenSource #Privacy

Hi @CoMaps.
I’m unable to install CoMaps from Codeberg using Obtainium on GrapheneOS.

Obtainium correctly detects `CoMaps-26080703-main-release.apk`, but the download repeatedly fails because the connection is interrupted. The repository URL and APK filter appear to be correct.

Is this a known issue with the Codeberg release download, or is a different Obtainium configuration required?

#CoMaps #Obtainium #GrapheneOS #Codeberg #OpenSource #Privacy

Hi @CoMaps.
I’m unable to install CoMaps from Codeberg using Obtainium on GrapheneOS.

Obtainium correctly detects `CoMaps-26080703-main-release.apk`, but the download repeatedly fails because the connection is interrupted. The repository URL and APK filter appear to be correct.

Is this a known issue with the Codeberg release download, or is a different Obtainium configuration required?

#CoMaps #Obtainium #GrapheneOS #Codeberg #OpenSource #Privacy

I have moved all my repositories away from #Codeberg.

This includes #Phandroid.
The cool part: For Fdroid-users (and similar stores) this is fully transparent. You don't need to do anything.

Only #Obtainium users that used the Codeberg repository directly need to adjust their settings manually.
The old Codeberg page tells you what to do.

The new home of Phandroid is https://code.umrath.dev/thoralf/Phandroid .
I'm quite pleased how the process turned out and that most users won't notice the change.

I have moved all my repositories away from #Codeberg.

This includes #Phandroid.
The cool part: For Fdroid-users (and similar stores) this is fully transparent. You don't need to do anything.

Only #Obtainium users that used the Codeberg repository directly need to adjust their settings manually.
The old Codeberg page tells you what to do.

The new home of Phandroid is https://code.umrath.dev/thoralf/Phandroid .
I'm quite pleased how the process turned out and that most users won't notice the change.

I have moved all my repositories away from #Codeberg.

This includes #Phandroid.
The cool part: For Fdroid-users (and similar stores) this is fully transparent. You don't need to do anything.

Only #Obtainium users that used the Codeberg repository directly need to adjust their settings manually.
The old Codeberg page tells you what to do.

The new home of Phandroid is https://code.umrath.dev/thoralf/Phandroid .
I'm quite pleased how the process turned out and that most users won't notice the change.

I have moved all my repositories away from #Codeberg.

This includes #Phandroid.
The cool part: For Fdroid-users (and similar stores) this is fully transparent. You don't need to do anything.

Only #Obtainium users that used the Codeberg repository directly need to adjust their settings manually.
The old Codeberg page tells you what to do.

The new home of Phandroid is https://code.umrath.dev/thoralf/Phandroid .
I'm quite pleased how the process turned out and that most users won't notice the change.

I have moved all my repositories away from #Codeberg.

This includes #Phandroid.
The cool part: For Fdroid-users (and similar stores) this is fully transparent. You don't need to do anything.

Only #Obtainium users that used the Codeberg repository directly need to adjust their settings manually.
The old Codeberg page tells you what to do.

The new home of Phandroid is https://code.umrath.dev/thoralf/Phandroid .
I'm quite pleased how the process turned out and that most users won't notice the change.

This week in #FDroid (TWIF) is live:

* last alpha 2.0 testing
* #EuroCommons #France #FLOSS migration #CaisseDesDepots
* #Scrib on-device transcription
* #Immich huge update
* #Fauxx for Desktop
* #XMPP #Quicksy abused, shut-down 😢 switch to #Conversations_IM
* track substance use w/ #JournalMultilingual
* #HeliBoard big news
* #Obtainium w/ #MaterialDesign Expressive
* #SidePhone store? F-Droid w/ a trenchcoat
+ 46 new apps
& 384 updates
- 1 archived

Upgrade client: https://f-droid.org/2026/07/16/twif.html

This week in #FDroid (TWIF) is live:

* last alpha 2.0 testing
* #EuroCommons #France #FLOSS migration #CaisseDesDepots
* #Scrib on-device transcription
* #Immich huge update
* #Fauxx for Desktop
* #XMPP #Quicksy abused, shut-down 😢 switch to #Conversations_IM
* track substance use w/ #JournalMultilingual
* #HeliBoard big news
* #Obtainium w/ #MaterialDesign Expressive
* #SidePhone store? F-Droid w/ a trenchcoat
+ 46 new apps
& 384 updates
- 1 archived

Upgrade client: https://f-droid.org/2026/07/16/twif.html

This week in #FDroid (TWIF) is live:

* last alpha 2.0 testing
* #EuroCommons #France #FLOSS migration #CaisseDesDepots
* #Scrib on-device transcription
* #Immich huge update
* #Fauxx for Desktop
* #XMPP #Quicksy abused, shut-down 😢 switch to #Conversations_IM
* track substance use w/ #JournalMultilingual
* #HeliBoard big news
* #Obtainium w/ #MaterialDesign Expressive
* #SidePhone store? F-Droid w/ a trenchcoat
+ 46 new apps
& 384 updates
- 1 archived

Upgrade client: https://f-droid.org/2026/07/16/twif.html

This week in #FDroid (TWIF) is live:

* last alpha 2.0 testing
* #EuroCommons #France #FLOSS migration #CaisseDesDepots
* #Scrib on-device transcription
* #Immich huge update
* #Fauxx for Desktop
* #XMPP #Quicksy abused, shut-down 😢 switch to #Conversations_IM
* track substance use w/ #JournalMultilingual
* #HeliBoard big news
* #Obtainium w/ #MaterialDesign Expressive
* #SidePhone store? F-Droid w/ a trenchcoat
+ 46 new apps
& 384 updates
- 1 archived

Upgrade client: https://f-droid.org/2026/07/16/twif.html

This week in #FDroid (TWIF) is live:

* last alpha 2.0 testing
* #EuroCommons #France #FLOSS migration #CaisseDesDepots
* #Scrib on-device transcription
* #Immich huge update
* #Fauxx for Desktop
* #XMPP #Quicksy abused, shut-down 😢 switch to #Conversations_IM
* track substance use w/ #JournalMultilingual
* #HeliBoard big news
* #Obtainium w/ #MaterialDesign Expressive
* #SidePhone store? F-Droid w/ a trenchcoat
+ 46 new apps
& 384 updates
- 1 archived

Upgrade client: https://f-droid.org/2026/07/16/twif.html

Uppdateringar. Telefonen. Om man föredrar Obtainium (tycker själv den är himla bra), själva appen, för att lägga till appar där. Så får man inte glömma att lägga till Obtainium själv i Obtainium. Nuvarande när jag skriver detta är version 1.6.4. Har varit tre uppdateringar på ganska kort tid, senaste två igår och idag. Just denna bland annat uppdaterade översättningar, brasiliansk portugisiska och tyska. Men också själva funktionaliteten kring uppdateringar.

#obtainium

These weeks in #FDroid (TWIF) is live:

* client, posts, website, categories work
* @gardiner_bryant makes interviews
* #AppVerifier the #FLOSS way
* first #HRT app, #Featherline
* #Fennec #Firefox crashes? Read here
* #ObtainX forks #Obtainium #MaterialDesign3
* #Saracroche @cbouvat interview
* #AppManager update
* @ferlagod muses on being forced to...
* #wallabag ecosystem health
+ 72 new apps
& 408 updates
- 58 archived

Will you fight? https://f-droid.org/2026/07/09/twif.html

These weeks in #FDroid (TWIF) is live:

* client, posts, website, categories work
* @gardiner_bryant makes interviews
* #AppVerifier the #FLOSS way
* first #HRT app, #Featherline
* #Fennec #Firefox crashes? Read here
* #ObtainX forks #Obtainium #MaterialDesign3
* #Saracroche @cbouvat interview
* #AppManager update
* @ferlagod muses on being forced to...
* #wallabag ecosystem health
+ 72 new apps
& 408 updates
- 58 archived

Will you fight? https://f-droid.org/2026/07/09/twif.html

These weeks in #FDroid (TWIF) is live:

* client, posts, website, categories work
* @gardiner_bryant makes interviews
* #AppVerifier the #FLOSS way
* first #HRT app, #Featherline
* #Fennec #Firefox crashes? Read here
* #ObtainX forks #Obtainium #MaterialDesign3
* #Saracroche @cbouvat interview
* #AppManager update
* @ferlagod muses on being forced to...
* #wallabag ecosystem health
+ 72 new apps
& 408 updates
- 58 archived

Will you fight? https://f-droid.org/2026/07/09/twif.html

These weeks in #FDroid (TWIF) is live:

* client, posts, website, categories work
* @gardiner_bryant makes interviews
* #AppVerifier the #FLOSS way
* first #HRT app, #Featherline
* #Fennec #Firefox crashes? Read here
* #ObtainX forks #Obtainium #MaterialDesign3
* #Saracroche @cbouvat interview
* #AppManager update
* @ferlagod muses on being forced to...
* #wallabag ecosystem health
+ 72 new apps
& 408 updates
- 58 archived

Will you fight? https://f-droid.org/2026/07/09/twif.html

These weeks in #FDroid (TWIF) is live:

* client, posts, website, categories work
* @gardiner_bryant makes interviews
* #AppVerifier the #FLOSS way
* first #HRT app, #Featherline
* #Fennec #Firefox crashes? Read here
* #ObtainX forks #Obtainium #MaterialDesign3
* #Saracroche @cbouvat interview
* #AppManager update
* @ferlagod muses on being forced to...
* #wallabag ecosystem health
+ 72 new apps
& 408 updates
- 58 archived

Will you fight? https://f-droid.org/2026/07/09/twif.html

@pixelfed when are we expecting the app update ?? #Obtainium

@pixelfed when are we expecting the app update ?? #Obtainium

@pixelfed when are we expecting the app update ?? #Obtainium

@pixelfed when are we expecting the app update ?? #Obtainium

Rocinante v1.0.4: Búsqueda de usuarios, libros federados y soporte para Obtainium
https://blog.forjalibre.eu/blog/rocinante-v104-busqueda-de-usuarios-libros-federados-y-soporte-para-obtainium/
#Android #SoftwareLibre #BookWyrm #Rocinante #Obtainium #ActivityPub

Rocinante v1.0.4: Búsqueda de usuarios, libros federados y soporte para Obtainium
https://blog.forjalibre.eu/blog/rocinante-v104-busqueda-de-usuarios-libros-federados-y-soporte-para-obtainium/
#Android #SoftwareLibre #BookWyrm #Rocinante #Obtainium #ActivityPub

Rocinante v1.0.4: Búsqueda de usuarios, libros federados y soporte para Obtainium
https://blog.forjalibre.eu/blog/rocinante-v104-busqueda-de-usuarios-libros-federados-y-soporte-para-obtainium/
#Android #SoftwareLibre #BookWyrm #Rocinante #Obtainium #ActivityPub

Rocinante v1.0.4: Búsqueda de usuarios, libros federados y soporte para Obtainium
https://blog.forjalibre.eu/blog/rocinante-v104-busqueda-de-usuarios-libros-federados-y-soporte-para-obtainium/
#Android #SoftwareLibre #BookWyrm #Rocinante #Obtainium #ActivityPub

Rocinante v1.0.4: Búsqueda de usuarios, libros federados y soporte para Obtainium
https://blog.forjalibre.eu/blog/rocinante-v104-busqueda-de-usuarios-libros-federados-y-soporte-para-obtainium/
#Android #SoftwareLibre #BookWyrm #Rocinante #Obtainium #ActivityPub

I did the math, and I've been using GrapheneOS for a little over two years. I know there are many who have used it longer.

It's been a really positive experience. There are a lot of great open source apps out there. I don't need Google Play Services.

I use Obtainium to update my 45 phone apps. Most of these app projects are posted on GitHub, Codeberg, or F-Droid.

I think this ecosystem will continue to grow. We don't need Google Play Store.

#DeGoogle #GrapheneOS #PlayStore #Obtainium

I did the math, and I've been using GrapheneOS for a little over two years. I know there are many who have used it longer.

It's been a really positive experience. There are a lot of great open source apps out there. I don't need Google Play Services.

I use Obtainium to update my 45 phone apps. Most of these app projects are posted on GitHub, Codeberg, or F-Droid.

I think this ecosystem will continue to grow. We don't need Google Play Store.

#DeGoogle #GrapheneOS #PlayStore #Obtainium

I did the math, and I've been using GrapheneOS for a little over two years. I know there are many who have used it longer.

It's been a really positive experience. There are a lot of great open source apps out there. I don't need Google Play Services.

I use Obtainium to update my 45 phone apps. Most of these app projects are posted on GitHub, Codeberg, or F-Droid.

I think this ecosystem will continue to grow. We don't need Google Play Store.

#DeGoogle #GrapheneOS #PlayStore #Obtainium

I did the math, and I've been using GrapheneOS for a little over two years. I know there are many who have used it longer.

It's been a really positive experience. There are a lot of great open source apps out there. I don't need Google Play Services.

I use Obtainium to update my 45 phone apps. Most of these app projects are posted on GitHub, Codeberg, or F-Droid.

I think this ecosystem will continue to grow. We don't need Google Play Store.

#DeGoogle #GrapheneOS #PlayStore #Obtainium