true, ill prob switch to that now that i can see what its doing.. it could be used to fill up a relay with noise, but at least you wouldnt see comment spam..
you could also add special filters with auth, im unsure the nwc daemon can do auth but i will find out.. at least then, rando snoopers wouldnt see ALL the nwc calls.
i already have read-only access available to any query for profile metadata, follow, mute, delete, report and relay lists for #realy it would be simple for me to add an opening to allow publishing NWC events... if they are ephemeral, which i think they are, then the only really hard problem will be i will need to add a rate limiter on the socket when these kinds of connections are made
Is there a gateway where every operation costs sats? Then every post could be 1,000 sats, every search 5,000 sats, paid by your wallet to ... also your wallet. It would cost you fees, but if you kept getting spam you'd be making Bank.
usually youd have to write a client too, but, that reminds me, amethyst might be able to do things like this with the fancy notice 🤔
per-operation payment is a lot more complex to build than subscription based schemes... plus, the latency, i mean, ok, LN is fast but imagine waiting for an LN payment for every. fucking. event. and. query.
oo what if auth with lightning. so it doesnt know your pubkey, its per connection
yeah that would work too but how do you rate limit then? also isn't the lightning identity still like ... a pubkey?
just a thought, it wouldnt help make DMs secure, it wouldnt care about your lightning pubkey, it would just wait for a payment to open the connection. subsequent connections also would have to pay.
rate limits inside the websocket connection, still would need to build..
i kinda like it better than pay per message or etc.. all these things are fun to think about till you realize you have to also write a client for anything to matter.
