this sounds interesting. can you give me one or two use cases? #interested
If you have a nostr event that you want to sign or publish, here is an app for it. Most clients don't allow you to get a signed event without publishing it, or publish an already signed event. That's why I made this. nostr:nprofile1qqsgdp0taan9xwxadyc79nxl8svanu895yr8eyv0ytnss8p9tru047qpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsq3samnwvaz7tmwdaehgu3wwdc8ymmkdahhxapwdekqgd20r7 nostr:nprofile1qqs8y6s7ycwvv36xwn5zsh3e2xemkyumaxnh85dv7jwus6xmscdpcygprpmhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0ekucf3
Discussion
nostrudel can do this stuff too
not sure about pre-signing separate to publishing tho, i think it does sign/publish in one step, click on the "more" item on the sidebar to see it... i forget ... event publisher and event console, one is for write, the other for read... it also lints the syntax on your json, generally speaking the publisher you have to remove the id and sig fields and you usually want to also remove the created_at so it is updated to the moment you click send (or YOLO as it sometimes is labeled as i've seen)
Yes thanks, I've was thinking to have it updated the created at upon sending
The first use case was a request from nostr:nprofile1qqs8y6s7ycwvv36xwn5zsh3e2xemkyumaxnh85dv7jwus6xmscdpcygprpmhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0ekucf3 for a site he could use to have someone sign an event that he had constructed and send the signed event back to him for publishing. The second use case was a request from nostr:nprofile1qqsgdp0taan9xwxadyc79nxl8svanu895yr8eyv0ytnss8p9tru047qpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsq3samnwvaz7tmwdaehgu3wwdc8ymmkdahhxapwdekqgd20r7 to be able to easily publish a signed event when his usual client wasn't publishing successfully.
thanks!