I can't delete a repost? Made a mistake and reposted something about compiling rust to wasm as alternative to JavaScript. I would never advise such a thing, learn JavaScript and stick to that. WASM was dead on arrival, unfortunately.
Login to reply
Replies (9)
javascript in the browser is hard to beat, but in some cases a wasm runtime can be great.
I would never use a full featured wasm web framework though
Depending on the client, you might be able to delete a repost, but in Nostr, deletion merely means publishing a new deletion request event. This means that relays may choose not to accept the deletion request. Even if a relay does accept the deletion request, if someone has already seen your repost, it's highly likely that the repost won't disappear from their local device.
JS is great for web interactivity. Browsers are highly optimised for this purpose.
WASM is good if your web app needs to do a lot of background compute on a non-blocking thread. It's not dead on arrival.
People just need to use the right tool for the job.
you can request for relays to delete an event, depending on what client you are using. try a different client
The first Nostr client I built, Blockcore Notes, utilized Web Workers, which allows you to do non-blocking background workers simply with JS. It's pretty sweet to work with. WASM has some use case of course, but the dream did not pan out. I was excited for WASI to replace Node.js and execution on edge compute, but never panned out.
I'll have to implement it on nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcqyrgm6venxueae3q37rhgjwechpfzlsx7yfll73vanyzyemv7v4vpky728r9 soon so I can try it out 🤙
Yes web workers are great for that but languages like Rust & C++ are so much faster. If you have something that is slow to compute in JS, WASM will be faster.
now you can :)
we tested zaps on this note… your profile only specifies a nip05 nostr address, but not a lightning address, so we tried to zap your nip05 address.... we made six attempts to⚡zap this note, at kosta@korenkov.net, over a period of about 1 hour. in each case, we found that your lightning address service or server did not respond correctly. if you wanted to fix this... you could try getting a free rizful lightning address -- https://rizful.com ... if u get it set up, pls reply here so we can do this ⚡zap test again.