Nostr Web Client

someone DMs me nip17. I respond nip17. I NEVER SEE A REPLY.

Is it broken? see this is why im struggling.. every fucking day im faced with trying really hard not to go debug nostr. but i open it and theres tons of broken shit every where i step.

i already debugged nip17 for a solid week just a few months ago, got it all working. now its broken again, i wont know why unless i debug.

meanwhile, this possibly valuable interaction is left in the dust.

depressing.

theres only so much depressing backward progress i can tolerate before i write off entire swaths of apps and code as DOA.

Reply to this note

Please Login to reply.

Discussion

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

i will be building a proper app and tools for actual working IRC style messaging... it will need a bot for caching messages, as it won't be relying on the relays to actually store the events so it can work ok with other relays than my relay, which is not perfect, working on an issue with parameterized replaceable events not being stored currently

also, yeah, i found out there is a go package that provides a key value store for the wasm browser environment so i will have an app that runs on all platforms and can be used as a web app (need to also figure out how to get it to talk to the extension signer as well, shouldn't be hard once i'm that deep into working with wasm/js environment

کیهان 1y ago

dms on nostr never worked for me.

minestr.app 1y ago

NIP04 DMs seem to work. I think NIP 17 is like herding cats.