Tracking issue: https://github.com/zapstore/backlog/issues/6 

 Love Spring but it seems development has stopped? nostr:nprofile1qqsrx4k7vxeev3unrn5ty9qt9w4cxlsgzrqw752mh6fduqjgqs9chhgppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg3waehxw309ahx7um5wgh8w6twv5hsxct838 

 Tout a fait 

 Good question! Each APK needs to be added manually and so it's vetted. With updates to the  UI we'll start making these things more clear. And next year integrating DVMs to help with these checks.

The idea is to bring many more FOSS apps that are not as releases on Github.

In reality this doesn't change much from the current practice of ingesting Github releases. Some of those could theoretically be compromised. 

 *I didn't mean the APK, but the recipe on how to fetch version and artifact, so once it's set up we automate that 

 Yes! Adding a button to load more releases, as a first step. In the next release. 

 We had an issue due to the size of the Fountain APK but it's fixed now.

nostr:nprofile1qqsx2wyjt6lmvc05rrvv05r5hm3w3t7h0pcpmkyswrpd4ymd2u09tscpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3kamnwvaz7tmwdaehgu339e682mnwv4k8xct5wvhxxmmdqywhwumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wscn3xgh nostr:nprofile1qqswfa547pdmqkerzf2uen3agudc67wxffjmenqpge3dylc006fppyspzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgqghwaehxw309aex2mrp0yhxvmm4de6xz6tw9enx6qgkwaehxw309aex2mrp0yh8qunfd4skctnwv46qj40rct you can use the zapstore-cli tool (0.1.0)!

If you had it installed, to update just do: zapstore install zapstore  

 nostr:nprofile1qqsrq7p2sv3m0jvtzuk952hhyp4ms2puv4d7dhwwzyfnvydq8403zacpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtchhmqvn icon and images for ya🤙 

 By the way, nostr:nprofile1qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgspr3mhxue69uhksmmyd33x7epwvdhhyctrd3jjuar0dak8xtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9umdntf8, I tested with the following snippet and it did work for me:

Just run it like: zapstore publish coracle (that will pull from github)

coracle:
  android:
    repository: https://github.com/coracle-social/coracle
    artifacts:
      - app-release-signed.apk
 

 Awesome! 

 Thanks! Mastodon seems ok to me, can you try refreshing?  

 Thanks for trying out zap.store! If you trust our account you can go ahead and install. The NIP-05 is not necessary, but better when you want to have extra assurance 

 You can also paste your npub and it will work! Again, if you trust the author/signer (greenart7c3) then just install 

 Would be so cool. The current categories are "list of apps" events (kind 30267), we could allow devs to push these to the relay as well. Needs more thought, though 

 I think it's the same issue of the other day. It's fixed! Working on other bugs as we speak, to be able to release all the fixes asap! 

 nostr:nprofile1qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgspr3mhxue69uhksmmyd33x7epwvdhhyctrd3jjuar0dak8xtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9umdntf8 would you mind updating (zapstore install zapstore, or pull from latest) and let me know if it works now? 🤞 

 Also working on the Android app where bugs have been fixed. I don't think it's a LineageOS specific issue. A little more patience and we'll have 0.1.4 released (or you can try building from source!) 

 Everything will be released in due course, but what are you referring to specifically? Cli first (likely today or tomorrow) and then the Android app 

 Thanks. I'm fixing that rn 

 An issue where the button reads "Sorry release is incompatible with your device" has just been fixed.

If you keep experiencing it, go to Settings (⚙️) and tap on Delete cache.

It was a data issue where the latest release events were invalid (numbers instead of strings in nostr tags). These releases (around 30) were removed from the relay.

Since we are transitioning to zapstore-cli to power our indexer, which always generates valid events, the problem is fixed but it will take a few days to deploy. So no updates for a few days.

Developer signed releases are not affected.

nostr:nevent1qqs8y978pu5vxemd058sayw3a5fy87tnnr7vp9m0ymlkezh2c3f9jgqprpmhxue69uhkummnw3ezuendwsh8w6t69e3xj730qgsv0ccqav0zjlznx8840tsnqj6gukk7adtvfyke73gyjjeea98tuwqrqsqqqqqpy34tvd 

 Interesting, I will check. Thanks 

 nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcppemhxue69uhkummn9ekx7mp0qyghwumn8ghj7mn0wd68ytnhd9hx2tcewvzaw if you'd like to display images and a longer description you can pull extra metadata from the Play Store (use --overwrite-app)  

 That's the whole point of app stores 

 Owned by whom? 

 Which hashes? Can you explain what your goal is? 

 zap.store does this for you, but you are right that for verifying zap.store itself you need to either trust the domain or verify the hash.

This is why we publish hashes in our nostr profile.

If you already have AppVerifier, that's one way. Or you could do it in the computer. Would be nice to have tutorials for both 

 I'm not against it but you need to trust the website host then.

Ideally we want multiple websites pulling these events. https://zap.store eventually will show this info, and then something like an app in nostrudel "more" could work too 

 One of zap.store goals is to finish what PGP never could.

I share your concern and to bridge the PGP-nostr gap we have NIP-39 cryptographic identities that soon will be integrated into zapstore-cli.

https://github.com/nostr-protocol/nips/pull/1335

Other tools could be built to leverage these events and feed them into Openkeychain for example.

That said, you mention "updates" and a phone which I suppose is Android. Keep in mind that the OS handles this verification for you, so no worries except on first install.

nostr:nevent1qqs0jls3pxsvs792443sdlg8f673f237hx4gfe3f5gl9fq3uv2a0zngpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsyg8dk3czwy5h43dxrunh70x3fhj5celttnxjpmcdnhefhcvxskasqspsgqqqqqqsmtjg7h 

 Awesome. I need to delete the previous app event for Amethyst version to show! When I get back to the computer 

 If you have ideas a great place to leave them, too, is:

https://github.com/zapstore/backlog/issues 

 Hey, which app? What is the actual error message? 

 Ok, thanks! 

We will start supporting other architectures (than arm64-v8a) in a few more releases. Before the end of the year 

 Great job guys... LF...GO! 

 Thanks! It will go with a big fat closed source label 😄 

 nostr:nprofile1qqszw70nm86zcl0wzlcwd0xulzdgl82e95v78vdm6fl0rnlarfle35gpzfmhxue69uhhqatjwpkx2urpvuhx2ucpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqg4waehxw309ajkgetw9ehx7um5wghxcctwvsv0rdp9 nostr:nprofile1qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgspr3mhxue69uhksmmyd33x7epwvdhhyctrd3jjuar0dak8xtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0ss9zgs this should fix it for you! 

 💪 

 😭

Will investigate promptly, sir 

 Fixed and pushed! If you want to build from source it's there, otherwise I'll cut a new release tomorrow 

 Why not download both from zap.store instead?

The Amber release for example is signed by the developer himself. We hope to do the same for 0xchat soon 

 PWAs are planned, it's one way we'll support iOS.

Also experimented with packaged PWAs, that don't require visiting a website 

 Actually zap.store fetches most apps from Github. But with additional security guards (checking hashes signed by the dev), web of trust display and better discovery. And soon zaps. Obviously Github directly has way more apps, but we're getting there. 

 Thank you! 

 Very interesting, and exactly what we seek to fix.

Beyond curated relays and web of trust, there definitely are plans to incorporate external services reports for malware, reproducible attestations and much more - likely through a DVM open market.

Some planned: https://github.com/zapstore/zapstore/milestone/3


nostr:nevent1qqs9up4jeehzxhxkdd269ygsyk7j3xu2fpcg2n64vvkhdkzqmzp9hacpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgs072l6htl2n4wrkq87dg59zwfrjqfxsreuhap6c4fj4pek490cquqrqsqqqqqp6tymtn 

 Awesome nostr:nprofile1qqs2hr9cpe0y9fwytl8s5mpf0e6ckyf6sld22q5tzzezhzkl2w2a2qspzamhxue69uhky6t5vdhkjmn9wgh8xmmrd9skctcpp4mhxue69uhkummn9ekx7mqpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmq32ahfv ! We did have some similar by nostr:nprofile1qqs2js6wu9j76qdjs6lvlsnhrmchqhf4xlg9rvu89zyf3nqq6hygt0spz9mhxue69uhkummnw3ezuamfdejj7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qgmwaehxw309a6xsetxdaex2um59ehx7um5wgcjucm0d5hscwu9av but need to find where they are 

 Need t-shirt of this 

 Correction, Ser: it's also available as CLI (even though we have like 5 packages there😆)

The app currently mostly runs on MacOS but we need to rework the installer for different OSes. It's not a huge amount of work to get on MacOS and Linux.

That paired with the new zapstore-cli tool (for devs and as crawler) which supports basically any platform (OS/architecture) to be available as nostr events. 

 👋 

 Heads up: There is something broken when accessing the citrine screen, and I can only have a look later today. Spoke too soon😄 

 Probably us 😄 

 Yes🙏 It's early days so nsec only. Promise we don't rug, but otherwise you can build from souce. I also need to add your npub to our relay whitelist. If it sounds good lmk! 

 Right. Can you retry with --overwrite-release ? 

 Ouch, sorry about that. I will be fixing that over the weekend and let you know! 

 All that should be fixed now!

zapstore install zapstore to update to 0.0.6 and try again 

 It's available now!

nostr:nprofile1qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgspr3mhxue69uhksmmyd33x7epwvdhhyctrd3jjuar0dak8xtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0ss9zgs if at any point you'd like to self-publish just let us know.


nostr:nevent1qqspmfevqmg9uh23e52xfypdcwfpglvdcryxcqaflfxafddfnduganspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygqh2wxu9f38d8gfgsl33smuhc6cl26mh7vpzu6592nutlchrmthcspsgqqqqqqs2jdtc4 

 Feel free to open an issue on our github! 

 Great question! Zapping releases is coming soon.

Currently focused on bringing more developers to self publish, and ironing out the last bugs around those tools. Then, entering the zap milestone. 

I'll make zap.store live up to its name⚡😄

nostr:nevent1qqs2rkuta5pyf9tckz0k5jqfhkvlw5askwstwfyfktka8czxr47834gpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygqmcu9qzj9n7vtd5vl78jyly037wxkyl7vcqflvwy4eqhxjfa4yzypsgqqqqqqs4phx0n 

 Hmm interesting. What happens when you tap on Update?
It might be an issue on their side, as most APK versions resolve via versionCode and not versionName (the one you are seeing) 

 No worries, thanks!