Conversation

Notices

1. Embed this notice
   Alex Gleason (alex@gleasonator.com)'s status on Saturday, 18-Mar-2023 08:45:58 JST Alex Gleason

   Alright boys, I’ve officially submitted NIP-69: https://github.com/nostr-protocol/nips/pull/377

   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Saturday, 18-Mar-2023 09:28:24 JST Alex Gleason

     in reply to

     • Tassoman

     @tassoman That’s exactly what the NIP does.

   • Embed this notice
     Tassoman (tassoman@orwell.fun)'s status on Saturday, 18-Mar-2023 09:28:25 JST Tassoman

     in reply to
     Compromised pubkeys should be revoked I'm not sure for the eternal destroyer bot. Maybe the relays can "automagically" destroy objects by themself when it's signed using a key flagged revoked...
   • Embed this notice
     Tassoman (tassoman@orwell.fun)'s status on Saturday, 18-Mar-2023 09:38:28 JST Tassoman

     in reply to
     Does the deletion is delegated to the relay? I mean the relay should distribute deletion event instead of publication or other events on the content.
     I'm not really into the protocol, maybe the relay can't do any active initiative but must be triggered by user ?
     Alex Gleason likes this.
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Saturday, 18-Mar-2023 09:40:23 JST Alex Gleason

     in reply to

     • Tassoman

     @tassoman Ohh, relays never talk to other relays. Except strfry, which has an experimental “sync” function: https://github.com/hoytech/strfry#syncing

     However, clients can take a stranger’s event and put it onto any relay without permission. This is how reposts work.

     So spreading deletions isn’t too hard in theory.