A nostr relay bouncer
BSD-3-CLAUSE License
Bot releases are hidden (Show)
Code cleaning and fix bug.
function
code.For npm installation, upgrading could be done with the following:
npm i -g [email protected]
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: https://github.com/Yonle/bostr/compare/3.0.6...3.0.7
Published by Yonle 5 months ago
Major change on worker code that improves a little bit of performance.
For npm installation, upgrading could be done with the following:
npm i -g [email protected]
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: https://github.com/Yonle/bostr/compare/3.0.5...3.0.6
Published by Yonle 5 months ago
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.
For npm installation, upgrading could be done with the following:
npm i -g [email protected]
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: https://github.com/Yonle/bostr/compare/3.0.3...3.0.5
Published by Yonle 5 months ago
Be good.
Worker.ref()
being called. Making the worker never exitFor npm installation, upgrading could be done with the following:
npm i -g [email protected]
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: https://github.com/Yonle/bostr/compare/3.0.3...3.0.4-1
Published by Yonle 5 months ago
Nothing really new here other than making it works with bun runtime.
You don't need to if you're in 3.0.2-5.
Full Changelog: https://github.com/Yonle/bostr/compare/3.0.2...3.0.3
Published by Yonle 5 months ago
5th revision after failed attempt on 4th revision. This revision includes major bugfix.
For npm installation, upgrading could be done with the following:
npm i -g [email protected]
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: https://github.com/Yonle/bostr/compare/3.0.2-3...3.0.2-5
Published by Yonle 5 months ago
This is a small revision that contains minor bug fix and introduction to ConnID in user agent header.
x-forwarded-proto
is not being handled properlyFor npm installation, upgrading could be done with the following:
npm i -g [email protected]
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: https://github.com/Yonle/bostr/compare/3.0.2-2...3.0.2-3
Published by Yonle 5 months ago
This is a small revision for bugfix on subscription limit handling. 3.0.0 to 3.0.2-1 is affected to this bug.
For npm installation, upgrading could be done with the following:
npm i -g [email protected]
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: https://github.com/Yonle/bostr/compare/3.0.2-1...3.0.2-2
Published by Yonle 5 months ago
This is a revision for grammar fixes in version 3.0.2. See full changelog at version 3.0.2
For npm installation, upgrading could be done with the following:
npm i -g [email protected]
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: https://github.com/Yonle/bostr/compare/3.0.2...3.0.2-1
Published by Yonle 5 months ago
It's a small release that contains improvements and option for setting limit. Useful for public bouncer.
User-Agent
. This tells the upstream relay of what bouncer we are connecting from and what is the maintainer of the bouncer servermax_conn_per_ip
. Set maximum incoming connections per IP.For npm installation, upgrading could be done with the following:
npm i -g [email protected]
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: https://github.com/Yonle/bostr/compare/3.0.1...3.0.2
Published by Yonle 5 months ago
It's an small release that contains bugfix and improvements.
loadbalancers
in config.authorized_keys
should work properly now)For npm installation, upgrading could be done with the following:
npm i -g [email protected]
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: https://github.com/Yonle/bostr/compare/3.0.0...3.0.1
Published by Yonle 5 months ago
This is a major bostr release after version 2 with massive code changes, including tweaks, performance improvements, more efficiencies, and also bugfixes.
bouncer.js
as a worker code, allowing for multithreading which consume less CPU performance than the previous singlethreading.ws
dependencies that could improve performanceMap()
as Objects. Just to try busting myth whenever object is actually faster than Map. Let's see.noscraper
being set. Now should works.broadcast_ratelimit
, incomming_ratelimit
max_known_events
configuration. See config.js.example
for detailsFor npm installation, upgrading could be done with the following:
npm i -g [email protected]
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: https://github.com/Yonle/bostr/compare/2.1.5-6...3.0.0
Published by Yonle 6 months ago
Just an small release that seems helpful for bouncer that has a configured cache relay.
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: https://github.com/Yonle/bostr/compare/2.1.5-5...2.1.5-6
Published by Yonle 6 months ago
Error in internal nostr-tools code that causes bostr crashes on certain filters.
Added a code to handle error in nostr-tools function.
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.
Published by Yonle 6 months ago
Published by Yonle 7 months ago
This is an statistics fix release for 2.1.5.
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: https://github.com/Yonle/bostr/compare/2.1.5...2.1.5-1
Published by Yonle 7 months ago
So, How many events you've got for months, Mr. Bouncer?
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: https://github.com/Yonle/bostr/compare/2.1.4...2.1.5
Published by Yonle 7 months ago
Little code improvement, small but major bugfix (again), And to combat scraper that consume server bandwidth, too.
noscraper
option in config to only allow client that support NIP-42 to use bouncer. This was used for combat scraperFor 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: https://github.com/Yonle/bostr/compare/2.1.3...2.1.4
Published by Yonle 7 months ago
Just a small update for adding the old feature.
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: https://github.com/Yonle/bostr/compare/2.1.1...2.1.3
Published by Yonle 7 months ago