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.
Jason Ansley | Fractional COO | $BTC
npub1ur…xdx2w
2024-11-29 11:56:20
in reply to nevent1q…ks5x
Author Public Key
npub1ur5ju4pd0xegu7wxal543ywn3aykxmjg2c9gucvtj5aaa43sm74qcxdx2wPublished at
2024-11-29 11:56:20Event JSON
{
"id": "0813ddd6fe6ca4de9ce734dd0a55b62c3b57000faea4c85697cb29608d587daf",
"pubkey": "e0e92e542d79b28e79c6efe95891d38f49636e48560a8e618b953bded630dfaa",
"created_at": 1732881380,
"kind": 1,
"tags": [
[
"p",
"45904b28ffe0e5cb9132f9a08e976ed7f0fc57d8387781ea9c80f256c412c1b4",
"",
"mention"
],
[
"p",
"20986fb83e775d96d188ca5c9df10ce6d613e0eb7e5768a0f0b12b37cdac21b3",
"",
"mention"
],
[
"e",
"05575666891a5fb6e152ad101da2e45d6b203ce6fda2faecf76a64d5b7ddda58",
"",
"root"
]
],
"content": "Not sure how to comment on the article itself so I’ll put my brief thoughts and suggestion (use case) here.\n\n1. I love the idea and it would be very useful and valuable to Nostr.\n\n2. Use case. Re: delegation (ie team members posting content)\nIt would be great if there is a way during the revocation process to identify which post of the delegatee should be kept vs removed.\n\nSince I haven’t yet seen a delete or edit and rebroadcast function for Nostr, this may not be possible to delete malicious notes.\n\nBut 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.\n\nSimilarly 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,\n\nOr, 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.",
"sig": "666a20780a07fcd986d21543743fc0cb54160c3f8185a26102d57d7b9e710e60b22875106e6740b162e430eb0cb9a0cd45b7806d0c07c5822c44c9e06136b197"
}