Is there a fix in the work for this?

nostr:npub18na8n7phl8r3sz67nqh3zhdzslj24qc5ramuq9tdka4a4qhrk4pqpjnmgn

Reply to this note

Please Login to reply.

Discussion

Don’t use Nostr for DMs 😂

SimpleX integration

DDos attack it by letting two npubs with bots talk back and forth within milliseconds apart

then there will be a bot that filters the bots

Then it will start dming the first bot

and on and on…

sounds tiresome to continuously try to filter new npubs nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj what you say?

just do an approved list

To break correlation as to whom is messaging whom, use ephemeral private+public keys for private conversation instances and optionally exchange the pubkeys via a series of intermediaries.

---

To mitigate metadata about sizes of messages, add padding

---

To mitigate frequency which may reveal time of activity of participants, automate regular message transmissions (empty padded, ignored), and limit how often real messages are sent to the same interval

y nobody talking bout disss ss

private zap messages do this already on notes, no?

yes but integrated somehow

so the private zap msgs slot becomes default slot

dont know if possible to make it run on millisatoshis and coded away so noone has to rly do anything for it

Semi said I was highly regarded for discussing this and that SimpleX integration makes so much more sense

we are all highly regarded, first of all

second, i hab no idea ab simplex so no idea

Each DM costs 1 sat to send, consider it a private zap each time.

for me np

problem for ppl who dont necessarily want to make use of ln (new nostriches)

i’d argue it’s a relatively simple solution for now until they integrate SimpleX into clients (or make it Nostr native even 🤔)

Not a complete fix, but nevertheless a good defense in depth measure: https://nips.be/42

Basically, an authentication scheme so that relays wouldn't serve DM notes to anyone unless they can cryptographically prove that they're the intended recipient.