Heads up zapstriches!

Not releasing much lately. Hard work happening under the surface:

- Working on UI/UX and data loading with nostr:nprofile1qqs2js6wu9j76qdjs6lvlsnhrmchqhf4xlg9rvu89zyf3nqq6hygt0spz9mhxue69uhkummnw3ezuamfdejj7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uygje4n

- Working on all-new relays with nostr:nprofile1qqsqgc0uhmxycvm5gwvn944c7yfxnnxm0nyh8tt62zhrvtd3xkj8fhgprdmhxue69uhkwmr9v9ek7mnpw3hhytnyv4mz7un9d3shjqgkwaehxw309aex2mrp0yhx6mmnw3ezuur4vghsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshs5p7jew

That is laying the groundwork for a LOT of cool social features, and access to massive amount of apps.

And my most important interop priority: ability to manage relays, Blossom servers and DVMs.

Reply to this note

Please Login to reply.

Discussion

You guys literally made me replace Google Play forever! Thanks

no plans to use zapoli relay on ddsrs? 😵‍💫

Zapoli is the one built in golang?

What is ddsrs?

yes, correct.

ddsr is the repo that contains zapoli and some other domain specific relays.

if you used it, we will continue its development actively. it's basically designed for zapstore and potentially other similar projects.

I see. Well, I appreciate you building this!

It seems you were motivated to develop the relay based on my note of months ago? I wished you had told me earlier that you were doing it, as my thinking about the tech stack evolved ever since.

I'm building a few (not just one) quite custom relays and I:

- would like to supervise and contribute to the codebase (I do not understand golang well)

- don't want to feel obliged to disturb you with constant requests, because there are many potential changes and I am mindful of your time

With that said, and as mentioned in my original note here, there will be relay selection in the UI so I'm hoping Zapoli will be used in the many app relays that we hope to see in the wild.

we appreciate your work