Thread

Bostr is a new Nostr relay that bounces your Nostr read and write events to multiple relays, allowing users on metered or mobile connections to save on bandwidth. You could run one for yourself, your community, or for the general public. Example: You run a Bostr relay at home and configure your mobile client to only use your home Nostr relay. While out and about, you utilize one relay, saving your mobile data, while the Bostr relay at home handles the heavy lifting and data intensive internet traffic for you, sending your notes and events out to the world.
GitHub
GitHub - Yonle/bostr: A nostr relay bouncer
A nostr relay bouncer. Contribute to Yonle/bostr development by creating an account on GitHub.

Replies (37)

Ok, not to diss this project or anything, but relay-proxy from earlier this year does the same thing. Multiplextr does as well, but using a wrapper protocol so clients can make non-static relay selections. Proxies like this hurt the ability for clients to intelligently route. They also have significant privacy drawbacks, especially if proxying AUTH (they can exfiltrate protected data). I'd love to see more work in this area, especially since proxies have the ability to improve routing without clients having to do anything by inspecting filters coming through. I recently wrote a bit about this, see below:
Habla
Relays, Encryption, and Groups - hodlbod
On relays, encryption, and how they work together to create a "good enough" private group solution.
↩ replying to ι˜Ώη”˜
In config.js, You put your public key in `authorized_keys` array. After restart, bostr will only allow users in `authorized_keys` to use the bouncer. However, You need to ensure that NIP-42 is supported in your client. Otherwise the bouncer will not doing anything for you during authentication. Additionally, You could enable internal NIP-42 for NIP-42 relays for your own use by inserting public & private key in `private_keys`.