Replying to Avatar jb55

using nostr relays and ephemeral events as a generic tcp proxy mechanism would be an incredibly slow, as it would have to sign and verify every packet as a nostr note, not to mention it would likely be rate limited and blocked on most public relays so it would be very unreliable. Please don’t do that, there is no good reason, and it just wastes the bandwidth of already bandwidth-constrained relays. Just use a regular proxy server.

There are some really cool QUIC based proxy mechanisms that are crazy fast and are e2e encrypted (MASQUE, etc). nostr doesn’t have to do everything, use the right protocol for the job.

gm nostr
Avatar
Cameri🐦‍🔥 1y ago

Can we do something about it?

Web proxies with Nostr identity based AUTH that allow you to connect to Nostr-first services just using the service's npub?

Seems like there’s a need for this kind of thing.

Cc nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg

Reply to this note

Please Login to reply.

Discussion

Avatar
fiatjaf 1y ago

I don't know much about any of that, nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s is probably right. Nostr events are definitely not the best fit. It would be cool to reuse Nostr keys in a separate system better suited for this task, but that would require forking QUIC or whatever, which would be too hard and I can't really think of a concrete benefit for that right now anyway.