Announcing zsp, our new tool exclusive for publishing apps to Nostr and Blossom, written from scratch in Go. ๐Ÿš€ It addresses many of the zapstore-cli limitations and brings way more features, speed and security to the table. โš  Attention developers โš  please try it out and report bugs... this tool will eventually replace zapstore-cli, and it's ready for publishing under the new NIP format we're migrating to. First look here: Downloads: SHA-256 checksums: 404f15b256bceae2ecaf652155a6cebd4759cabd3c63ef95f14d6746a212c70a zsp-darwin-arm64 720597c6cee94b05188cb8f82e0b3ef8e64dbb2d98490d569096bcb852e28869 zsp-linux-amd64 c05907b9262e654f0149f5fa67825829380111a5e25ac14c27f347ff140f8e2b zsp-linux-arm64

Replies (17)

White Noise's avatar
White Noise 5 days ago
Making it easier to build on Nostr is how we win. nevent1qqs97h9ednrvfx04gp8y0x2nfkw28xuan3r3lewul3v2geqt5s2y79szypuvuma2wgny8pegfej8hf5n3x2hxhkgcl2utfjhxlj4zv8sycc86qcyqqqqqqgehu35dView quoted note โ†’
Arjen's avatar
Arjen 4 days ago
Really cool! I would want to use this, but for desktop apps/cli-tools. Would you suggest creating something entirely separate or do you think it would fit as and addition to this cli? Desktop has way more architectures and different metadata on the binary files
Feeling slightly silly - I'm having trouble installing zsp. Says it needs go installed, so I tried "sudo apt install golang-go". But it said zap requires a newer go version, so I removed the apt version and installed the snap version. Then it seems to be struggling with an incorrect file path. I can find the file, at a slightly different path, but it doesn't seem to do anything if I try to execute it, and "zsp publish --wizard" just says the command zsp is not found, so I don't think it's successfully installed. Downloading the release file didn't get me any further. I guess I'm still a newbie... I can keep trying things, but thought I'd let you know.
Haha! That helped. I got it installed! It struggled to download the APK file - it worked on the seventh try! But I saw there was something I needed to fix, so I deleted the file from the zsp cache and tried again. Using the zsp publish command, it shows the download progress, but times out before it finishes downloading. I'll go find faster internet and see if that helps. Almost there!
I think I'm hitting some kind of context window limit, not a timeout. I get this error: Error: failed to download APK: failed to write file: context deadline exceeded (Client.Timeout or context cancellation while reading body) The APK is about 82 MB. And, a question - will people with @Zapstore and Zapstore Alpha both "automatically" update to Alpha? I want to set people up with Alpha, but don't want to confuse them when things merge.
With lots of trial and error, I got it eventually! Once I figured out how to get the config file to fetch the APK from my computer instead of downloading it, but still get the metadata from Codeberg, it worked. Just had to set up my signatures and all that to properly sign the file. If more specific feedback is helpful, I'd be happy to share. It did work in the end!
โ†‘