I do as well, however that represents only a small part of f-droids userbase. A lot of people aren’t financiallt in the position to get a new device that support GrapheneOS/lineageos/eOS etc or need some apps that will only work on google verified devices
The less people use the app repositories the less support they get by app developers, they need any support they can get if they want to offer a decent number of apps
When you release an app using the Nostr protocol, clients like Zapstore grab the app directly from GitHub, GitLab or whatever platform the developer uses, bypassing the need for repositories.
I do as well, however that represents only a small part of f-droids userbase. A lot of people aren’t financiallt in the position to get a new device that support GrapheneOS/lineageos/eOS etc or need some apps that will only work on google verified devices
@RmDebArc_5
Lineage runs on a zillionolder older inexpensive phones.
If they can’t figure somethjng out, then that’s on them. I honestly don’t care about zombie sheeple like them. They deserve what they get.
The less people use the app repositories the less support they get by app developers, they need any support they can get if they want to offer a decent number of apps
@RmDebArc_5
When you release an app using the Nostr protocol, clients like Zapstore grab the app directly from GitHub, GitLab or whatever platform the developer uses, bypassing the need for repositories.
Zapstore still has some kind of app repository, even if that isn’t the official name. And someone still has to publish the app
@RmDebArc_5
Zapstore is only a client that grabs Nostr events from Nostr relays and displays the “app release” events.
Any Nostr client could display those events.
You grab Zapstore from their website or GitHub, just like you do F-Droid.
But someone has to make sure that the apps are being added to Nostr, no? Or does it just display all apks published on Github/Lab/etc?