2.1.5

So, How many events you've got for months, Mr. Bouncer?

What's new?

• Bouncer statistics
• Fix ratelimit handling

Upgrading

For npm installation, upgrading could be done with the following:

npm i -g bostr@latest

or

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

For source code installation, upgrading could be done with the following:

git pull
npm i

You will need to change approved_publishers as allowed_publishers in your config.

Then, restart your bouncer to apply update.

Full Changelog: 2.1.4...2.1.5

2.1.4

Little code improvement, small but major bugfix (again), And to combat scraper that consume server bandwidth, too.

What's new?

• noscraper option in config to only allow client that support NIP-42 to use bouncer. This was used for combat scraper
• Fix improper bouncing with save mode
• Small code improvement

Upgrading

For npm installation, upgrading could be done with the following:

npm i -g bostr@latest

or

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

For source code installation, upgrading could be done with the following:

git pull
npm i

and then restart your bouncer.

Author comment

雪花飘飘北风啸啸
天地一片苍茫
一剪寒梅傲立雪中
只为一人飘香
爱我所爱无愿无悔
此情常留心间

Full Changelog: 2.1.3...2.1.4

2.1.3

Just a small update for adding the old feature.

What's new

• Reintroduced cache_relays. You could use it to speed up event deliveries.
• Fix on bostr closing an already opened subscription.

Upgrading

For npm installation, upgrading could be done with the following:

npm i -g bostr@latest

or

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

For source code installation, upgrading could be done with the following:

git pull
npm i

and then restart your bouncer.

Full Changelog: 2.1.1...2.1.3

2.1.2

RELEASE: 2.1.2

Signed-off-by: Yonle <yonle@lecturify.net>

2.1.1

A small speed up and major bugfix for the bouncer code.

What's new?

• [New] Idle blank session
• [Note] Removed orwarding client IP address to upstream relay due to usage of idle session.
• [MajorFix] Fix repetitive EOSE being sent to client even after being paused

Idle session

In this release, bostr will now initialize a blank session which connects to the configured relays first. This idle session will then used for new incomming connection by client, allowing client to be able to interact with relays in a instant.

Back then, bostr only connect to bunch of relays once a client was connected. This does not do much but has some impact on performance, notably some nostr client may not be able to receive certain events from some relays.

This feature works almost similarly to the old orphan session feature. However that approach proved terrible as it reuses previously used session. It could be the ratelimited session, so i ditched it at the beginning.

By default, bostr only initialize 1 blank idle sessions. To configure how many idle sessions to be initialized during startup, Edit config.js and change idle_sessions integer value (Default: 1). It's suggested to initialize more than a single idle sessions in public bouncer.

Upgrading

For npm installation, upgrading could be done with the following:

npm i -g bostr@latest

or

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

For source code installation, upgrading could be done with the following:

git pull
npm i

and then restart your bouncer.

Full Changelog: 2.0.10...2.1.1

2.1.0

RELEASE: 2.1.0

2.0.10 - Disappointment

Haaaaaaaaaiyaaaaaaaaaaaaaaaaa

What's new?

• Revert two commits that conflicts the bouncing process: 20aab1a, 2bf91f8 (I have no idea what the hell was ruining it at all. It worked almost pretty much the same as with client.relays but things just go WEIRD)

Upgrading

For npm installation, upgrading could be done with the following:

npm i -g bostr@latest

or

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

For source code installation, upgrading could be done with the following:

git pull
npm i

and then restart your bouncer.

Full Changelog: 2.0.9...2.0.10

2.0.9

Small fix, Small improvements.

What's New?

• Fix bugs on the following:
  • handle error on missing config field for blocked_publishers
  • fix AUTH request is being sent even with empty private_keys
• Improvements on handling EOSE.

Upgrading

For npm installation, upgrading could be done with the following:

npm i -g bostr

or

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

For source code installation, upgrading could be done with the following:

git pull
npm i

and then restart your bouncer.

Full Changelog: 2.0.8...2.0.9

2.0.8

RELEASE: 2.0.8

small and useful improvements and a little bit touch on moderations.

what's new?

• improvements on receiving new events in save mode (a.k.a. pause_on_limit)

firewall / moderation things:

• a way to block an event owner's pubkey to have the event published into your bouncer. Useful to stop annoying actors to abuse your bouncer or in moderated nostr relay.

• ability to block an IP address to connect into the bouncer's websocket. Useful to stop scrappers to constantly dig in your bouncer

upgrading

for npm installation, upgrading could be done with the following:

npm i -g bostr

or

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

for source code installation, upgrading could be done with the following:

git pull
npm i

and then restart your bouncer.

after upgrading, please check your config for new optional configuration by running bostr check config.js for npm, ./bostr_cli.js check config.js for source installation.

comment

i am not going to focus much on moderation however. So please bear in mind that if you ask too much to add moderation stuffs into bostr, It will be an different project. Because that's not what the goal of this project for.

as of now i am still focusing to improve the save mode (pause_on_limit).

full changelog: 2.0.7...2.0.8

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