Replying to Avatar monlovesmango

not yet. for mute I was hoping to use the encrypted lists nip (kind 30000) that I had proposed: https://github.com/nostr-protocol/nips/pull/114

also wanted to get an unencrypted version out there.

#[0] do you guys have any documentation on these new kinds?

It's very simple. Private block:

{

kind: 16462,

content: nip04.encrypt(myPriv, myPub, JSON.stringify(privateBlockedUsersArray))

}

Public block:

{

kind: 16463,

content: JSON.stringify(publicBlockedUsersArray)

}

I picked the kind by random from the replaceable events range.

Any improvements are welcome. One thing that comes to mind is recording the reason or expiry date for block. If such additional attributes are needed, object might be better than array.

Reply to this note

Please Login to reply.

Discussion

`JSON.stringify(obj, null, 2)` to increase happiness 😊

sats sent using 1-click experience on astral.ninja with Alby wallet connected to my Bitcoin Jungle wallet. what kind of future am I living in?

That's how hyperbitcoinization will look like. This is just a glimpse of it.. 🍀 ⚡ 💜 🤙

would you consider using the nip I linked above? have you had a chance to review it? its written to be extensible for events, hashtags, users. and to allow users to create lists other than just mute that they can name themselves.

also I don't think its appropriate for nip04 encryption scheme here..? isn't this only for when shared secret is needed?

also how do you query for public blocks if the user list is in the content and not the tags..?

just a thought looking at this, why not keep everything in the same event and have the public be in tags and private in encrypted content? would that simplify or complicate?

this is a really neat idea. might suggest this in the encrypted lists pr, so it could public and private lists