3.0.2-3

This is a small revision that contains minor bug fix and introduction to ConnID in user agent header.

What's new?

• ConnID in User Agent. See 014d469. Don't worry, It does not expose your IP.
• Fix for HTTP page where handling x-forwarded-proto is not being handled properly

Upgrading

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

npm i -g bostr@3.0.2-3

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

Then restart your bouncer to apply update.

Full Changelog: 3.0.2-2...3.0.2-3

3.0.2-2

This is a small revision for bugfix on subscription limit handling. 3.0.0 to 3.0.2-1 is affected to this bug.

Upgrading

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

npm i -g bostr@3.0.2-2

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

Then restart your bouncer to apply update.

Full Changelog: 3.0.2-1...3.0.2-2

3.0.2 revision 1

This is a revision for grammar fixes in version 3.0.2. See full changelog at version 3.0.2

Upgrading

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

npm i -g bostr@3.0.2-1

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

Then restart your bouncer to apply update.

Full Changelog: 3.0.2...3.0.2-1

3.0.2

It's a small release that contains improvements and option for setting limit. Useful for public bouncer.

What's new?

• Reveal who we are in User-Agent. This tells the upstream relay of what bouncer we are connecting from and what is the maintainer of the bouncer server
• Config option: max_conn_per_ip. Set maximum incoming connections per IP.

Upgrading

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

npm i -g bostr@3.0.2

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

Then restart your bouncer to apply update.

Full Changelog: 3.0.1...3.0.2

3.0.1

It's an small release that contains bugfix and improvements.

What's new?

• For loadbalancer only mode, List bounced relays from other bouncers that provided in loadbalancers in config.
• Fixed NIP-42 in bostr (authorized_keys should work properly now)
• Fix deflate compression still being enabled even after disabled in config

Upgrading

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

npm i -g bostr@3.0.1

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

Then restart your bouncer to apply update.

Full Changelog: 3.0.0...3.0.1

3.0.0

This is a major bostr release after version 2 with massive code changes, including tweaks, performance improvements, more efficiencies, and also bugfixes.

What's new?

• Performance: Separated one of CPU intensive code in bouncer.js as a worker code, allowing for multithreading which consume less CPU performance than the previous singlethreading.
• Performance: Added 2 optional ws dependencies that could improve performance
• Code: Replace codes that utilizes Map() as Objects. Just to try busting myth whenever object is actually faster than Map. Let's see.
• Bugfixes: auth.js did not worked properly with only noscraper being set. Now should works.
• Improvement: Removed some code that only consumes memory and do exactly nobody would like to do. These config is now deprecated as it's now doing nothing: broadcast_ratelimit, incomming_ratelimit
• Feature: Added max_known_events configuration. See config.js.example for details

Upgrading

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

npm i -g bostr@3.0.0

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

There are new configuration that you could configure for reducing memory usage. Check config.js.example, edit your existing config,

Then restart your bouncer to apply update.

Full Changelog: 2.1.5-6...3.0.0

2.1.5-6

Bostr version 2.x.x and below is deprecated

Just an small release that seems helpful for bouncer that has a configured cache relay.

What's new?

• Improved EOSE handling for cache relays.

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.5-5...2.1.5-6

2.1.5-5

Error in internal nostr-tools code that causes bostr crashes on certain filters.

Added a code to handle error in nostr-tools function.

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.

2.1.5-4

package.json: bump revision to 4

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

2.1.5 revision 1

This is an statistics fix release for 2.1.5.

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.5...2.1.5-1