That's it. It just loads the Kind 3 events, lets you pick which one to restore and broadcasts a new Kind 3 from the contacts from that event (not the relays, it doesn't change that even though those are also stored on the kind 3 event). It's really simple.

Reply to this note

Please Login to reply.

Discussion

I'm getting it. Just haven't dealt with event signing snippets and manually played around with JSON payloads over websocket. Cool, thanks. Kind 3 ✅ .

Is there any trail suggesting which client may have been the culprit, any such client incoming metadata even.... to see where the hell the 0 came from? Or no way rather

I was on Amethyst update just scrolling, not even following only commenting on my existing follows (no immediate follow activity preceding the 0... weird)

Only if the client sets a "client" tag when events are posted. If it doesn't (most don't) then there's no way to know which client is responsible I'm afraid.

Ok. Ty 🙇‍♂️