Thread | Plain Text Nostr

thread · root 8769fdef…159d · depth 2 · · selected b4b3c859…c12d

thread

root 8769fdef…159d · depth 2 · · selected b4b3c859…c12d

566c166f3ada -- 200d [root] 
|    *sigh* I was careless with my security and someone got ahold of the nsec private key for this account. Please
|    unfollow and ignore and don't respond to DMs. I'll make a new one with video proof of identity tomorrow. -Adam
|    Soltys
|    reply

vinney...axkl -- 200d
Can Brainstorm help this guy today/tomorrow
nostr:npub1u5njm6g5h5cpw4wy8xugu62e5s7f6fnysv0sj0z3a8rengt2zqhsxrldq3 ?
reply [1 reply]

e5272de914bd -- 200d [parent] 
     Given Brainstorm as it is currently implemented, if a handful of people use NIP-56 to report this nsec, it will
     only take a small handful of reports to knock the GrapeRank score down to zero, which will prevent this profile
     from showing up on profile keyword searches in the future, once we have a few search engines using the GrapeRank
     metric to filter results. Unfollowing helps too but as a general rule, you’re never going to get enough people
     to unfollow a compromised nsec. Muting will also reduce the 🍇-Rank score but not as much as reporting.
     
     NIP-56 does not specify a reportType for “compromised” — maybe we should update the nip? For now, reportType
     “other” would work best; or just put “compromised” as the reportType even if it’s nonstandard.
     
     https://nostr-nips.com/nip-56
     reply