Why is a good question, I am still in observation mode. When you join an active discord community there is always a bunch of people interacting about a topic, if you interact with the topic as well, you usually get feedback and are welcome to join. I probably don’t follow the right people here yet or get a grip of topics that are floating around, but I am curious to learn more
I guess I am still figuring out what to expect, I developed an app on nostr and basically trying frantically to get some feedback from anybody and even after contacting quite a number of people I only got one reaction. I totally get it that nobody needs to give a shit and I usually don’t like being contacted myself, but I don‘t even know if I was able to reach anybody or my message just vanished in the abyss.
I have to admit that the ecosystem here is very hard to grasp, it feels like a free for all with a few users and general low interaction.
I made a rsvp app the last two days: https://rsvplease.netlify.app
#asknostr #development nostr:note15dum20tvs4rgeycjp224et7fnfkv9ugf2rp43fwjwfcvzrtpnjlqyv47x9
Together with mtsarah i made a rsvp event app - any #feedback and testers are appreciated. #reactjs #development
Nostr app dev journey: I think I have a good grip on nostr-tools and nostr-react know, stuff I am currently struggling with:
- caching of user information. When I load many events and I want the user meta data attached to the events I have to do an extra request to fetch the user data it seems. I am thinking of doing a batch request with multiple ids on multiple relays, but I still have to react to updates. I would like tonisches more on the client.
- meta data: when I publish an event like a channel message (kind 42), how should I structure additional data. As a Tag seems most logical to me, but I guess naming things is hard
- user onboarding: how to make sure that the user doesn’t care about nostr, UX is little tough
#reactjs #development #caching #nostr-tools
Nostr app dev journey: I think I have a good grip on nostr-tools and nostr-react know, stuff I am currently struggling with:
- caching of user information. When I load many events and I want the user meta data attached to the events I have to do an extra request to fetch the user data it seems. I am thinking of doing a batch request with multiple ids on multiple relays, but I still have to react to updates. I would like tonisches more on the client.
- meta data: when I publish an event like a channel message (kind 42), how should I structure additional data. As a Tag seems most logical to me, but I guess naming things is hard
- user onboarding: how to make sure that the user doesn’t care about nostr, UX is little tough
Winning the #blockchain #hackathon challenge for loyalty of Raiffeisen bank international with our nostr client!
We did win this hackathon!
Hey #[0] - I am at a hackathon in Vienna, Austria and we will build a nostr client for the loyalty challenge here - what should I do?
Hello Nostr, curious to meet you!