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

2.0.6

Nothing big here.
Just introduction of bostr CLI.

You could install it via npm:

npm i -g bostr

or

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

And see available commands by running:

bostr

---

Yonle

2.0.5-a

• Added blocked_hosts for blocking an host from connecting into bouncer

This is a short release for 2.0.5. Please check https://github.com/Yonle/bostr/releases/tag/2.0.5

2.0.5

Release: 2.0.5

Recoding, improvements, and temporary features removal.

What's new?

• Dependencies bump
• Use of requesting different subscription ID rather than using
  subscription ID from client. Fixes late-close problems.
• Filter validation is now checked with nostr-tools instead, Fixes issue
  with conflicting client that puts more than single filter in a single
  REQ subscription.
• Reworked session code.
• Allow possibility to only accept and reject receiving some specific kind of events.

What's removed?

• EOSE Timeout
• Cache to local relay (unreliable)
• [Temporary Removal] Orphan session

Upgrading

No new configuration / feature was made. As usual, You will always need to run git pull and run npm upgrade to upgrade dependencies, And finally restart your bostr instance.

2.0.4

Version Deprecated

bostr version 2.0.4 or below is no longer recommended and therefore is suggested to upgrade to latest version.

Small improvements, Small new features that i never use.

What's Changed

• WEBSOCKET: Enabled deflate compression
• HTTP: Favicon support
• HTTP: Explicitly tells which address to connect to without putting two addresses (ws:// or wss:// depending on what user were connected)
• HTTP: Standalone HTTPS support by @ftkro in #11
• BOUNCER: Numerous upstream ratelimit handlings
• BOUNCER: Expose the current running bostr version in User-Agent
• BOUNCER: Make orphan socket termination faster
• CODE: "use strict" has been applied.
• LOGGER: Show the connected IP addresses when disconnected
• LOGGER: No need to tell that it is cleaning orphan sessions when max_orphan_sess is 0.

New Contributors

• @ftkro made their first contribution in #11

Updating

Run git pull inside bostr directory. A new feature is available in this version and needs to be enabled manually. Please read config.js.example and add new parameter to config.js. Finally restart your bostr server to apply update.

Full Changelog: 2.0.3...2.0.4

2.0.3

Ironically, Frontend could be cruel or accidentally brutal to relays sometime.

What's new?

• Updated NIP-01 compliance as per Jan 4th 2024
• Improved memory usage (7% less than before)
• Enabled connection with TCP_NODELAY
• incomming_ratelimit and broadcast_ratelimit is now there to ratelimit a client. Check config.js.example for configuration example.

Updating

Run git pull inside bostr directory. A new feature is available in this version and needs to be enabled manually. Please read config.js.example and add new parameter to config.js. Finally restart your bostr server to apply update.

Full Changelog: 2.0.1...2.0.3

2.0.2

Fast connect and disconnecting is brutal sometime.

What's new?

• An whitelist to only allow some event authors to be published with this bouncer.
• Orphan sockets feature to make idle sessions to reduce the amount of reconnections.

New Contributors

• Takuro Fukuda https://github.com/ftkro at #8

Full Changelog: 2.0.1...2.0.2

2.0.1

Nothing so big today. Just improvements on reliabilities.

• Added caching feature.
• Fixbugs, Including a fix for orphan socket

New Contributors

• @akiomik made their first contribution in #4
• @ryogrid at #7

Full Changelog: 2.0.0...2.0.1

~ Merry Christmas ~

2.0.0-r1

This only bring a small fix in release 2.0.0. Check the v2.0.0 changelog here

2.0.0

Finally a release that entirely no longer depends on sqlite3 for storing temporary informations as per 0f76628

What's New?

• Mandatory: Mode 1 has been removed
• Mandatory: Major EOSE handling bugfix (also impacts v1.0.0) at b518022
• Performance: No longer depending on sqlite3, Making the bouncer 2x faster than previous version (1.0.0) and not very CPU intensive as before
• NIP-42 could be used for bouncer admin in public bostr relay
• Handle since and until from client internally
• New config for bouncing settings for fixing common bouncing issues: wait_eose, pause_on_limit, eose_timeout, max_eose_score

New Contributors

• @HolgerHatGarKeineNode made their first contribution in #2 by fixing my mistake in config.js.example. great. i am really in rush than i expected.

People could be in the Contributor list by fixing small mistakes these days huh? What a hack....

Updating

Updating was simple and short. Simply do the following command inside the bostr directory:

git config pull.rebase true
git pull

And finally, restart the bostr server to apply the update.

Conclusion

Performance improvements, important bugfixes, and new internal features. That's the summary of this update.

Anyway, That's only all i could tell for today. Wish you have a good day, and happy posting.

---

Yonle
November 26th 2023

Full Changelog: 1.0.0...2.0.0