Yeah that was the bit I thought was cool. I couldn't find the original note except by using the event ID.
The event existed but it wasn't in your list of published notes.
Did you publish it to a private relay?
Login to reply
Replies (2)
Ty! And, no... I didn't. 😎 ;)
Reposting this here for context/clues...
That was exactly where my brain was at at 3 am. Lol I don't want to give away the very simple—yet effective solution I found before you're ready for it, but I also don't want you over here thinking I hacked the mainframe to make it happen and lose interest in the logic puzzle. I didn't vibe code anything. When you're ready. I'm happy to disclose.
View quoted note →
A note is just a signed JSON. I can know everything about it before it's published; in fact, I can know it even before it's signed. So, creating chains doesn't seem that hard... To prevent it from showing a create at in the future or in the past would probably solve the problem with confusing your readers. For announcing things, a replace event would probably work... Not sure if any of this is true; I didn't dive in, I'm just guessing.