nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcsrhspy regarding heliboard's apk which is available, I noticed there's a regular apk and a debug one. it seems zap.store is shipping the debug one instead, perhaps we could swap that. thanks :)
Yeah this will get better when devs start signing their apps, and for the rest we'll try to make a better job picking APKs!
Pretty sure someone suggested they integrated nostr and most comments were against it. This was last year in their github issues.
Want to join our telegram group and discuss it there? https://t.me/+Azeu1bePFNtkYWMx
Did you check out the sample events? App profile events are kind 32267 used in zap.store and will become a NIP! And for trust attestations, are you following the NIP-77 discussion?
Yes you must have the Play Store signed package. An option would be to back up and uninstall Simplex. Then reinstall it with zap.store or obtainium.
Error messaging will get better in the coming releases
This is correct, the current version parsing code is terrible.
Was, I should say, as it's already properly fixed. Available in the next release in a few more days, if all goes well.
Primal and a few other updates affected.
Workarounds: use Obtainium (available on zap.store) or uninstall/ reinstall the app you want to update - make sure you have backups!
Btw you can actually install and update Obtainium from zap.store (and viceversa)
But otherwise show the events to be copied and signed elsewhere
I guess it's up to each developer, first version will read nsec from env
nostr:npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8 are you interested in collaborating on a NIP? There is a huge overlap between App Stores and software repository releases. There may be benefits of aligning the two. I created gitworlshop.dev and ngit which are NIP-34 clients.
Tell me more, what kind of NIP?
In my view there's a strong connection between both but not much overlap.
zap.store is using NIP-51 kind 30063 for releases coming from a repo. I might need to update it slightly but it's simply a replaceable event listing release files. And others:
We target higher Android versions but will see if it's possible to lower the constraints!
I can't get nostr:npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8 to insall, anybody knows whats the min android version required?
What error are you getting? Which Android version?
Ouch. Sorry about that. It's a bug with version comparison, already fixed but will be out in the next release.
This is awesome! I'll be in touch
Would you be willing to sign every Amethyst release with your nsec?
In the next few weeks I'll be launching an (alpha) dev signer CLI ! Sign with nsec or browser extension
I can't wait for nostr:npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8 to no longer be bottlenecked by a single npub publishing notices of updates.
I want my new #amethyst damnit!
I promise, me too!
Update job just launched, latest versions should be available now
Nostr and Blossom fix this
zap.store will fight the bully
iOS: expect us
The use case I had in mind is to be able to import apps from their repositories, similar to what Obtanium allows you to do, by pasting a the link of the repo. As such, I could definitely replace Obtanium and switch to Zap.store, but I would still maintain Obtanium by the moment since I have some apps that I want to keep up-to-date, and they aren't available on Zap.store.
Another detail that could be interesting is the ability to attach metadata to files in the repository, similar to how Alby's PkgZap (https://pkgzap.albylabs.com/) allows you to do with all the necessary information to verify an app directly from the repo. This would provide a convenient way to access and evaluate apps without having to visit multiple sources.
I'm thinking we could have a way to manually add APKs. The tricky part is updates, how do we know a new release is out (unless hitting i.e. github's API)?
As for metadata probably not worth it because we're only doing this for the short term. The goal is metadata will live on nostr when devs sign their apps and releases.