The more it hurts, the more you innovate.
I'm building this out of respect for your phone's battery. It will be a noob-proof LNbits extension that you can run on your own server with a few clicks.
The nostrclient multiplexer.
Discussion
Might also save a ton of your mobile data plan, but it's still unclear to me if nostr melted away my gigabytes by fetching duplicate data from relays or if it was the jpgs.
Isn't it the same that nostr.wine is already doing?
Actually don't know. From what I can see, it looks like some sort of aggregator with an actual stateful relay you can subscribe to. This thing will not store any data, just do websocket stuff.
Thats a great idea! 💪
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.
This is intended for personal use though. Will that also cause the same problem?
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.
Yeah let's do that!
I'm also seeing the social clients not working properly with the current version of this multiplexer. My own stupid CLI nostr client that does only DMs and Posts works great, but hamstr and iris expect something different.
While we are at it can we add header auth to NIP-42? Seems absurd to have to open the web socket connection first before auth in cases like a private personal relay.
♥️
Your post is getting a lot of engagement.
Added to the https://member.cash/hot feed