No it's perfect for personal use, but I have some other problems. We should discuss about them together guys #[4] #[5]
NIP 65 => If you save only your proxy with this NIP, all other people will try to fetch events from your proxy. If it's a localhost or local network url, they will not reach your proxy. But if it's not, they could add your proxy in their relays list.
This brings up a new problem: Authentication on the proxy. NIP-42 is probably the best solution to only allow your pubkey for using the proxy, but 0 client currently support it.
You will have the same problem as me in https://github.com/Dolu89/nostr-proxy
When many clients are connected, you will get "REQ limits reached" from relays and you clients will not get any events.
Thank you. Spend as much as you can and participate creating a circular economy
Publish and read events to connected relay, not like Blastr that does only publish.
Nostr-Proxy is still experimental, but it works fine if you launch it for yourself (just be careful on consumed RAM, there is still some issues on this)
Moi. Mais j'ai toujours pas compris l'intérêt, ils sont affichés quelque part, à part sur le site badges.page ?
What clients support NIP 42?
It depends of each relay configuration. Some have a default to 10 concurrent REQs. So if 2 users made 5 REQs each, max is reached fast
I'll probably shutdown Nostr proxy at both nproxy.zerologin.co and nproxy.cc.
It's not usable for many users because of "notice ERROR: too many concurrent REQs from relay XXX".
It's only great as personal proxy. I'll continue to work on it to reduce used memory and also provide an easy way to deploy it (cc #[0])
Unless relay admins allow me unlimited REQ?
Happy to see my tools here!
Oh no… we still have some… come on
Memory leaks should be fixed in Nostr Proxy, I merged all the code in the master branch, you can now use it yourself
Nostr Proxy: see you in 6 hours
It looks better, a lot
Yes sorry about that...
Proxy is currently using nostr-tools which has a lot of memory leaks.
I fixed some of them but it's not enough. nostr-tools is too hard to update.
I'm switching to https://github.com/adamritter/nostr-relaypool-ts which is easier to understand and update.
I'll deploy a test later today.
Nice!
Just be careful, the relay pool consumes a lot of RAM after few hours :(
I'm still on it
Oh ok, yes custom relays is planned!
I just have to fix perf issues before opening to new relays
