A nostr relay bouncer
BSD-3-CLAUSE License
Bot releases are visible (Hide)
Published by Yonle 7 months ago
A small speed up and major bugfix for the bouncer code.
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.
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.0.10...2.1.1
Published by Yonle 7 months ago
Published by Yonle 7 months ago
Haaaaaaaaaiyaaaaaaaaaaaaaaaaa
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)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.0.9...2.0.10
Published by Yonle 8 months ago
Small fix, Small improvements.
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: https://github.com/Yonle/bostr/compare/2.0.8...2.0.9
Published by Yonle 8 months ago
RELEASE: 2.0.8
small and useful improvements and a little bit touch on moderations.
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
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.
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: https://github.com/Yonle/bostr/compare/2.0.7...2.0.8
Published by Yonle 8 months ago
Nothing so big. Only some configurable bouncer limitations that were once only configurable on admin side. It's now possible for users too.
REQ
or EVENT
for the first time.accept
, reject
, accurate
, and save
>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,
}
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
git pull
npm i
And restart your bostr bouncer.
npm i -g https://github.com/Yonle/bostr
And restart your bostr bouncer
Full Changelog: https://github.com/Yonle/bostr/compare/2.0.4...2.0.7
Yonle
Published by Yonle 8 months ago
blocked_hosts
for blocking an host from connecting into bouncerThis is a short release for 2.0.5. Please check https://github.com/Yonle/bostr/releases/tag/2.0.5
Published by Yonle 8 months ago
Release: 2.0.5
Recoding, improvements, and temporary features removal.
REQ
subscription.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.
Published by Yonle 8 months ago
Release: 2.0.5
Recoding, improvements, and temporary features removal.
REQ
subscription.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.
Published by Yonle 8 months ago
Release: 2.0.5
Recoding, improvements, and temporary features removal.
REQ
subscription.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.
Published by Yonle 8 months ago
Release: 2.0.5
Recoding, improvements, and temporary features removal.
REQ
subscription.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.
Published by Yonle 8 months ago
Release: 2.0.5
Recoding, improvements, and temporary features removal.
REQ
subscription.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.
Published by Yonle 8 months ago
Release: 2.0.5
Recoding, improvements, and temporary features removal.
REQ
subscription.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.
Published by Yonle 9 months ago
Small improvements, Small new features that i never use.
User-Agent
"use strict"
has been applied.max_orphan_sess
is 0
.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: https://github.com/Yonle/bostr/compare/2.0.3...2.0.4
Published by Yonle 9 months ago
Small improvements, Small new features that i never use.
User-Agent
"use strict"
has been applied.max_orphan_sess
is 0
.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: https://github.com/Yonle/bostr/compare/2.0.3...2.0.4
Published by Yonle 10 months ago
Ironically, Frontend could be cruel or accidentally brutal to relays sometime.
incomming_ratelimit
and broadcast_ratelimit
is now there to ratelimit a client. Check config.js.example
for configuration example.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: https://github.com/Yonle/bostr/compare/2.0.1...2.0.3
Published by Yonle 10 months ago
Fast connect and disconnecting is brutal sometime.
Full Changelog: https://github.com/Yonle/bostr/compare/2.0.1...2.0.2
Published by Yonle 10 months ago
Fast connect and disconnecting is brutal sometime.
Full Changelog: https://github.com/Yonle/bostr/compare/2.0.1...2.0.2
Published by Yonle 10 months ago
Nothing so big today. Just improvements on reliabilities.
Full Changelog: https://github.com/Yonle/bostr/compare/2.0.0...2.0.1
~ Merry Christmas ~