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 🤔

Reply to this note

Please Login to reply.

Discussion

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.

Payment per pubkey?

per connection might be better..

When you're paying yourself it's all relative

yeah, paying to store events is a bit silly if it's your own relay

Paying to store events on your own relay is free *to you*, but will cost spammers real money.