HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
freenode
jbnc
JavaScript2020–2021
freenode / jbnc

jbnc

IRC Bouncer with no registration/setup required written in nodejs with support for separate client buffers and always-on.

4Distinct people
5Mentions
0Explicit recommenders
31GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

IRC Bouncer with no registration/setup required written in nodejs with support for separate client buffers and always-on.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month5 dated mentions

Observed mentions: 2020-05-08 13:10:31 UTC to 2021-05-22 19:34:04 UTC.

01232020-05-01 00:00:00 UTC to 2020-06-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 commentsMay 20202020-06-01 00:00:00 UTC to 2020-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-07-01 00:00:00 UTC to 2020-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-08-01 00:00:00 UTC to 2020-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-09-01 00:00:00 UTC to 2020-10-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2020-10-01 00:00:00 UTC to 2020-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-11-01 00:00:00 UTC to 2020-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsNov 20202020-12-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2021-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-02-01 00:00:00 UTC to 2021-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-01 00:00:00 UTC to 2021-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-04-01 00:00:00 UTC to 2021-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-05-01 00:00:00 UTC to 2021-06-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMay 2021

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
May 20202020-05-01 00:00:00 UTC2020-06-01 00:00:00 UTC321
Jun 20202020-06-01 00:00:00 UTC2020-07-01 00:00:00 UTC000
Jul 20202020-07-01 00:00:00 UTC2020-08-01 00:00:00 UTC000
Aug 20202020-08-01 00:00:00 UTC2020-09-01 00:00:00 UTC000
Sep 20202020-09-01 00:00:00 UTC2020-10-01 00:00:00 UTC110
Oct 20202020-10-01 00:00:00 UTC2020-11-01 00:00:00 UTC000
Nov 20202020-11-01 00:00:00 UTC2020-12-01 00:00:00 UTC000
Dec 20202020-12-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
Jan 20212021-01-01 00:00:00 UTC2021-02-01 00:00:00 UTC000
Feb 20212021-02-01 00:00:00 UTC2021-03-01 00:00:00 UTC000
Mar 20212021-03-01 00:00:00 UTC2021-04-01 00:00:00 UTC000
Apr 20212021-04-01 00:00:00 UTC2021-05-01 00:00:00 UTC000
May 20212021-05-01 00:00:00 UTC2021-06-01 00:00:00 UTC101

What Hacker News says

5 sources
Not to defend rasengan (my opinion of him and his freenode tyrancy is severely negative and I fully support the actions of the ex-freenode now-Libera.Chat team) but as someone who previously had access to the Snoonet servers and as the developer of the open source IRC server software that Snoonet uses (InspIRCd) I can confirm that there was no message intercept ability on Snoonet as of a few months ago when I resigned. No SSH access was given to rasengan on any servers all of which were locked down pretty heavily to a small subset of staff including formerly myself. I think it is very unlikely that any surveillance capacity has been added since I resigned given that the remaining volunteers (who were not appointed by rasengan and many of whom predate rasengan's ownership of the network) are decent people who would not tolerate that. InspI
Read the rest
RCd also makes it very hard to surveil users without them knowing (and I've made it harder since becoming the lead maintainer) as it sends notices to all users on connect if rawio debug mode is enabled and all loaded modules are listed in `/MODULES` which is explicitly exempt from being disabled in the config. Being open source it's technically possible to disable these checks by editing the source but from what I have seen rasengan is not a very good programmer[1] so he would probably not be able to do that without being caught. [1] This mess seems typical of his programming abilities: https://github.com/toc-irc/jbnc/blob/master/bouncer.js
In Freenode IRC operators now engaging in routine abuses of power
tocirc·May 9, 2020Submission

Having fun with IRC, making a simple bouncer, offering $10 per detailed bug

Having fun with IRC again lately, group is making a simple bouncer https://github.com/toc-irc/jbnc Simply connect to the port with a password and a bnc account is made for you. Yes we know it's open to abuse; all IP addresses are hashed through our webirc setup in gateway mode, so users are still unique. We'll add flood checks later; i'm sure a million connections making always on connections would crash it, I got it to crash at 7,500 connections This is all experimental as to have a foundation to build off of; other bouncer projects are great too (kiwi, znc etc) we're just looking to have fun and create. But the other stuff, such as bugs between bouncer and client and things not forwarding right/crashing for other reasons we are offering $10 per detailed bug (with description and suggestion on fix), and $20 for fixes coded I believe the
Read the rest
budget is up to $2,000 - so for contributors we'll consider a bonus if the 2k isn't met We're in #jbnc on irc.bitcoin.com / irc.imperialfamily.com Long live IRC!
3 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.