No more configuring auto-scaling, load balancers, or paying for capacity you don’t use. Traffic is automatically routed and load balanced across thousands of servers. Sleep well as your code scales effortlessly.”
My loose understanding of that is if the pubkey is on the paid whitelist of a certain relay then they should accept the forwarded message from this relay. But there's also an "authenticated" flow for some paid relays and that I believe won't work.
Yeah nice work, I saw that last week. I think it's important to have something like that. Have you gotten a lot of use out of yours? I do worry of too much spam. Also, I should probably keep a list of other proxies to ignore sending to.
Yes it has been used by with an average of ~30 connections and it's a problem.
A proxy shouldn't be public unless relays remove REQ limit for proxy. The next step for nostr is probably a relay market to disable limits for specific clients.
I also have to add limits on my side to not be spammed
Nostr relay operators are not going to like this sort of software, because it will be used to magnify spam. In response, relays will likely block connections from Cloudflare IP addresses.
I'll likely implement some spam deterrents on the cloudflare side, but if they block IPs anyways, I'll just implement other proxies until everyone eventually becomes a paid relay.
The nostr wait list and automatic DM we did for Mutiny was kind of cool. Plus I'm experimenting with cloudflare serverless stuff and thought open sourcing what we did would be kind of fun.
I still don't care for social media and I think there's a lot of problems, but there's some thing we may need to use it for which prompted building this proxy.
Yeah I think my next step will be to aggregate events from all the relays and proxy the subscription part too but that starts to be a lot of a bigger effort. It feels like serverless works well in the publish side but not intended for sub, but just need to think through it more.
This is awesome! I am interested in the POST endpoint. Can you show example code how to interact with it. Is the endpoint https://nostr.mutinywallet.com/event ? What do you expect in the body?
sick! thanks for open sourcing this.
Towards understanding Cloudflare….
“Automatic scaling
No more configuring auto-scaling, load balancers, or paying for capacity you don’t use. Traffic is automatically routed and load balanced across thousands of servers. Sleep well as your code scales effortlessly.”
https://workers.cloudflare.com/
Good for privacy, I assume, but won't probably work with paid relays
My loose understanding of that is if the pubkey is on the paid whitelist of a certain relay then they should accept the forwarded message from this relay. But there's also an "authenticated" flow for some paid relays and that I believe won't work.
Ok, thanks. I saw the paid relay nostr.wine in your code. This is good.
https://github.com/MutinyWallet/blastr/blob/master/src/nostr.rs
That's just a few fallback relays, need to add some more. We mostly use the list from nostr.watch which has hundreds of proxies.
Happy to see I'm not alone with a proxy project! I've made https://github.com/Dolu89/nostr-proxy. If you want to discuss about proxies in the future, you can DM me npub1txukm7xckhnxkwu450sm59vh2znwm45mewaps4awkef2tvsgh4vsf7phrl or on twitter @Dolu_web
Yeah nice work, I saw that last week. I think it's important to have something like that. Have you gotten a lot of use out of yours? I do worry of too much spam. Also, I should probably keep a list of other proxies to ignore sending to.
Yes it has been used by with an average of ~30 connections and it's a problem. A proxy shouldn't be public unless relays remove REQ limit for proxy. The next step for nostr is probably a relay market to disable limits for specific clients. I also have to add limits on my side to not be spammed
Nostr relay operators are not going to like this sort of software, because it will be used to magnify spam. In response, relays will likely block connections from Cloudflare IP addresses.
I'll likely implement some spam deterrents on the cloudflare side, but if they block IPs anyways, I'll just implement other proxies until everyone eventually becomes a paid relay.
Who won you over? I thought you were a nostr bear like Nick
The nostr wait list and automatic DM we did for Mutiny was kind of cool. Plus I'm experimenting with cloudflare serverless stuff and thought open sourcing what we did would be kind of fun.
I still don't care for social media and I think there's a lot of problems, but there's some thing we may need to use it for which prompted building this proxy.
Sounds like Carman won you over. I bet the automatic mutiny dm was his idea.
yuuup @benthecarman spawned the idea and then built it, I simply took his work and packaged it here :P
this is a heartfelt story
powerful!
hell yeah
Wow nice.
I was wondering if it was possible to implement a full relay using workers/SQLite/kv. I reckon it might be.
Yeah I think my next step will be to aggregate events from all the relays and proxy the subscription part too but that starts to be a lot of a bigger effort. It feels like serverless works well in the publish side but not intended for sub, but just need to think through it more.
Is there a public blaster relay that I can add to my primal client?
could you list on the README all the relays you send the event to. Thx
Well done! The future is here!
This is awesome! I am interested in the POST endpoint. Can you show example code how to interact with it. Is the endpoint https://nostr.mutinywallet.com/event ? What do you expect in the body?
Yup, it's the same body type as nostr client messages for wss. Like
[{"EVENT", {msg}}]or something like that.Awesome, I will give it a try. I hope you keep it running for a bit.
Very nice
Another step towards larger scale. Good thing, keys with a profile and daily use keep growing!
Yes Nostr thé future