I think Lightning is ingredient that promotes spam resistance and incentives just like Nostr could be an ingredient in some capacity.

Ultimately the ideal topology is onion routing or another solution that conceals the content source and destination of all messaging. That is the holy grail.

Reply to this note

Please Login to reply.

Discussion

Yes, I think I agree. It will be interesting to see what form that takes. I can imagine lots of permutations related to transport, storage, note wrapping, etc. It would be awesome to come up with a transport-based solution that would be orthogonal to the data format, to get nostr-over-whatever.

You mistyped PoW there.

LN promotes spam resistance only for the sender and receiver, cause only they can tell if a payment (zap) is real or not. Any 3rd party cannot tell the difference between a payment and a self-payment.

Outside of direct connections, distingushing spam from non-spam becomes exponentially harder, the further you go down the social graph.

Problem is, there will always be good content voiced through anons. Any platform with a spam filter that ignores this is self-limiting.

A good way for anons to cut through the bot noise is with PoW.

Zaps are not cybil resistant so we agree there. It really doesn’t even matter who gets the funds you just need to make sure an anon sender has some cost to send or stake a message as non spam at least when onboarding

In a group context I see no problem with somebody being the Uncle Jim ensuring there’s no foul play on behalf of the group. Once funds are received sign an attestation. I don’t see that as exponentially difficult.

That's one hop away (you trust Uncle Jim).

But if one of Uncle Jim's friends (2nd hop) signs the attestation? What if its 3 hops away?

It gets real tricky real fast.

Not really. You either have Uncle Jim custody the group chat, have a DM. Or go on Nostr or something else if you want a public facing permissionless system where anything goes.