3.0.10

You really need to be clever on writing code when it comes to security. Sometime you think this would be fine, But one day it proves that your code has problem with it.

And that's what happened here. This is a bit serious if you use bostr only for private, So please update your bouncer as this is a major version for that.

what's new

• Fix bostr let everyone in even having authorized_keys being set when noscraper is set to true.

upgrading

• npm: npm upgrade bostr@3.0.10 and restart
• source: git pull && npm install and restart
• bun: git pull && bun install and restart

Full Changelog: 3.0.9...3.0.10

3.0.9

Fix http page doesn't work.

upgrading

• npm: npm upgrade bostr@3.0.9 and restart
• source: git pull && npm install and restart
• bun: git pull && bun install and restart

3.0.8

Preparing before the apple catastrophe for folks with compression enabled.

what's new

• exclusively disable compression ONLY for apple users.

upgrading

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

npm i -g bostr@3.0.8

or

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

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

git pull origin stable
npm i

For bun runtime installation, upgrading could be done with the following:

git pull origin stable
bun install

Then restart your bouncer to apply update.

Full Changelog: 3.0.7...3.0.8

3.0.7-1

package.json: bump revision to 1 for 3.0.7

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

3.0.7

Code cleaning and fix bug.

What's new?

• Code: Separated session event handlings code into separate function code.
• Fix NIP-42 authentication in bostr <-> upstream relay

Upgrading

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

npm i -g bostr@3.0.7

or

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

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

git pull origin stable
npm i

For bun runtime installation, upgrading could be done with the following:

git pull origin stable
bun install

Then restart your bouncer to apply update.

Full Changelog: 3.0.6...3.0.7

3.0.6

Major change on worker code that improves a little bit of performance.

Upgrading

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

npm i -g bostr@3.0.6

or

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

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

git pull origin stable
npm i

For bun runtime installation, upgrading could be done with the following:

git pull origin stable
bun install

Then restart your bouncer to apply update.

Full Changelog: 3.0.5...3.0.6

3.0.5

Instead of closing, Nuke. Just nuke.

If you just upgraded to 3.0.4-1, This update is major fix ONLY for 3.0.4-1.

Upgrading

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

npm i -g bostr@3.0.5

or

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

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

git pull origin stable
npm i

For bun runtime installation, upgrading could be done with the following:

git pull origin stable
bun install

Then restart your bouncer to apply update.

Full Changelog: 3.0.3...3.0.5

3.0.4-1

Be good.

What's new

• Closing websocket connections instead of terminating it.
• Worker.ref() being called. Making the worker never exit
• Some change on loading module. Just a change of name.

Upgrading

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

npm i -g bostr@3.0.4-1

or

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

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

git pull origin stable
npm i

For bun runtime installation, upgrading could be done with the following:

git pull origin stable
bun install

Then restart your bouncer to apply update.

Full Changelog: 3.0.3...3.0.4-1

3.0.3

Nothing really new here other than making it works with bun runtime.

Changelog from 3.0.2 to 3.0.3

• 14efdaf http & worker: handle max_client_subs properly
• 845aa5b worker: fix bug where subscription limit is not being handled properly
• d9d3b78 http page: handle x-forwarded-proto properly
• 014d469 bouncer connection to relays: tell ConnID in header
• b99795f worker: do not reconnect to cache relays/loadbalancer bouncers if status code ix 4xx
• 533f3e6 worker_bouncer: use .splice(, 1) for removing instead of just delete
• a187fed worker: newsess: rehandle loadbalancer config handling
• 701fbe6 index.js (keeper): Detect Bun runtime environment

Upgrading

You don't need to if you're in 3.0.2-5.

Full Changelog: 3.0.2...3.0.3

3.0.2-5

5th revision after failed attempt on 4th revision. This revision includes major bugfix.

What's new?

• Fix bug on crash after removing upstream relays to prevent further reconnection due to blocking.

Upgrading

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

npm i -g bostr@3.0.2-5

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...3.0.2-5