2.0.7

Nothing so big. Only some configurable bouncer limitations that were once only configurable on admin side. It's now possible for users too.

What's new?

• Bouncer session reworking. Bouncer will only connect to relays after user do REQ or EVENT for the first time.
• Configurable connection limit for client side by connecting with various URL parameters such as accept, reject, accurate, and save>

What's removed

• [Permanent] Orphan session

Recommended changes

For admin

To make it actually reduce client bandwidth by default, It's suggested to not enable accurate mode, which was on by default by editing config file and change the following:

{
  pause_on_limit: false,
}

as:

{
  pause_on_limit: true,
}

For user

Check your connected bouncer information by visiting it's page. If the default bouncing method was accurate, You could connect to us with ?save=1 in the end of bouncer URL:

wss://bostr.example.com/?save=1

Updating

Source code

git pull
npm i

And restart your bostr bouncer.

npm / bostr CLI

npm i -g https://github.com/Yonle/bostr

And restart your bostr bouncer

Full Changelog: 2.0.4...2.0.7

---

Yonle