Does anyone have a solution for this "#e" and "#p" filter nonsense?? It's driving me insane.

SimpleX is based around queues. Instead of pushing everything to a relay and have it stay there forever, you push messages into a queue that eventually gets consumed by the person you’re sending the messages to. They exist on the relay temporarily and they are encrypted. Cool part is that there are no long-term “addresses” or “pubkeys” to send the message to, so spam is much harder.

I think nostr could learn a lot from this protocol, I believe we can use something like this to strengthen use cases on the nostr side. I am building a SimpleX rust library to learn the protocol further, and will be looking into how we can leverage it in our apps.

svelte? websockets are painful.

vanilla js? seems more doable, but it lacks the component stuff.

time to see how react goes.

websockets please cooperate

Y?

Challenge for next week: find 1 person who knows nothing about nostr and watch them sign up and use your client.

Don’t tell them how to do anything, just watch (in person) and listen. Take note of everything they say and do. Check to see where they get stuck.

This feedback will be more valuable than anything else you do this week. Focus on that.

i have reached the point where now i need to figure out how i'm going to manage data related to notes and all

it in fact did do the job.

found the issue, events are initially sent in reverse chronological order, but when new events are pushed on the stored list, it gets put at the bottom. i imagine switching which end events are pushed to after receiving eose would do the job.