Thread - Nostr Hypermedia

Vitor Pamplona _@vitorpamplona.com 1 week ago

Multiple simple things have been suggested already to fix this but in the end no one saw it as that important for users. But it can be super simple because users just need to know that one other user is gaslighting everyone and kick him out. Tagging all IDs at least once in the conversation on new DMs can make a complete record of what the user has seen. Bloomfilters of messages in the past month/week can also help and fully solve it. It's not just theater. After all, it is possible to apply the same gaslighting tactics in every single nip in nostr. The simple fact that we can create content in the past can be used to gaslight everyone. They don't need the DM spec for it.

↑ Parent

Replies (2)

JOE2o 1 week ago

NIP17 groups are the only space in Nostr where this is code red. Both technically and socially. Technically other Nostr kinds are more transparent, have *some* exposed metadata handles, are not fanned out one by one, etc. But most importantly socially. Few people are going to get conned or socially engineered in kind1 threads or discord style NIP28 chats or whatever else. A closed Signal-style chat group, and one boasting best-in-class privacy, is a totally different risk space. If you're an attacker looking to expose this nostr gaslighting quirk, then NIP17 groups are straight where you'd head.

1 replies ↓

Vitor Pamplona _@vitorpamplona.com 1 week ago

Again, it's an easy fix if what you saying truly matters. But something tells me you are not interested in fixing it. Other nips are not "more transparent". You can literally do the same thing in almost all of them with the same level of metadata. I know because I have debugged things like that in almost every nip Amethyst implements. Right now, my friends gaslight me on Signal and Whatsapp by editing and deleting messages as well or playing with push notification timing attacks. So, not even Marmot actually solves this.

1 replies ↓