Not sure how to comment on the article itself so I’ll put my brief thoughts and suggestion (use case) here.

1. I love the idea and it would be very useful and valuable to Nostr.

2. Use case. Re: delegation (ie team members posting content)

It would be great if there is a way during the revocation process to identify which post of the delegatee should be kept vs removed.

Since I haven’t yet seen a delete or edit and rebroadcast function for Nostr, this may not be possible to delete malicious notes.

But I can imagine a scenario where a team member (nsub) has posted 1000 notes then They go rogue and start posting junk…I’d want to keep the 1000 proofs of work (notes) but revoke or delete the malicious and recent ones.

Similarly it might be nice to tag or otherwise appended/identify notes with a ā€œrevoked nsubā€ or some identification so that readers know the 1000 notes were posted by a team member that was removed,

Or, I think it was Facebook did this for biz profiles, the admins could see what post was actually posted by another admin or moderator…I don’t Recall, if everyone could see that, or if it was only Admins that could, but in this case for Noster, it would be nice that whenever an in sub posted, it was identifiable with a particular person, perhaps as a tag or something so that viewers know it is from a representative and a real human in the organization instead of just the brand at large.

Reply to this note

Please Login to reply.

Discussion

you may just open the article and click on the comment icon it will pop up the comment section šŸ™

Ok I think I did that…

In the lower left corner of the app (on iOS) I pressed the comment button and added it there as well.

I see there are apparently 2 comments on the article now.

However in YakiHonne, when viewing the article, where / how should I see other comments? When I click the comment bubble it only slows me to write another comment

I’ll move this to a place that is better suited for discussion. Awaiting some advice as to where.

Long press the comments button, and you’ll see all the comments.

Thanks!

I must not be as smart as I thought LOL

These need cases match the existing intent of the NIP. But I was exploring the attack vectors, and there is too much vulnerability for this. Likely won’t work. And too much governance passed to the relay. I’m going to have to reapproach the solve, which is needed. But this may not be it and I’m stepping away from the NIP. I’m a noob on the protocol so sorry about my learning curve.