I'm scraping a curated set of projects from Github, just to bootstrap the project and make it usable.

That creates a few events (of kinds 1063, 30063 and 32267) that go to a specialized relay, now hardcoded at wss://relay.zap.store .

So what you pull in the app comes from the relay - not from Github directly.

I pull from Github because APKs there are signed with devs' certificates, unlike F-Droid

nostr:note1yruw725u4egljsntmq0e606nwlzge9e3cy85nf9l3ralp8sqeu9sxf4req

Reply to this note

Please Login to reply.

Discussion

Nice! Congrats, this is great.

Thank you!

Is that relay publicly writeable? Could I manually construct those event kinds with rust-nostr and submit new apps that way?

Right now your event will be rejected. But that is a scaffold I want to eventually throw away. I want you to sign your app and write to a bunch of relays.

I wrote this to share with devs to try to understand how to get there:

https://zap.store/developers

And for reference these are sample events: https://github.com/zapstore/zapstore/wiki/Sample-app-events

Very nice. Have you thought about expanding this to more than android, i.e. desktop packages?

Yes, absolutely, it's coming. The app already works on Mac and Linux.

The first feature of this app ever was in Madeira, where I demoed with nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr and nostr:npub1lunaq893u4hmtpvqxpk8hfmtkqmm7ggutdtnc4hyuux2skr4ttcqr827lj the download/verification/install of a zipped PWA file, so that is coming too

(That's when the application/pwa+zip mime type was born)

I don't know what a zipped pwa file is and at this point I'm too afraid to ask 😂

I was thinking more about native apps but it's probably very challenging since OSs so heterogeneous and there's too many competing standards for package formats.

Could some existing tooling like Nix be leveraged for this?