• Hub 3 rate limiting

    From deon@21:2/116 to All on Tue Mar 24 09:00:54 2026
    Howdy,

    Over the last week I've implemented rate limiting on clrghouz. I noticed recently quite a few polls coming from the same IP address every minute - some of them probably script kiddes, some of them BBSes that are on auto-pilot.

    The rate limiting will impose the following limits:

    * Maximum 2 concurrent connections,
    * Maximum 5 connections in a 60 min period.

    If your BBS is crash capable - most of you should be, then clrghouz can be set to poll you when it has mail available for your system.

    If you dont want mail immediately, you can be set to poll mode "normal", which means clrghouz will poll you twice a day, if it has mail waiting for you.

    If polling to your system fails 10 times in a row, your system will be put on auto-hold and no longer poll until you poll in and collect mail. That poll will reset/clear the auto-hold status. You'll also get a netmail telling you about it - which might be helpful if you recently changed hosts/ports and didnt update the hub.

    For CRASH bbses, I recommend having a manual poll (if you want) no more freqently than 6 hrs to clear any backlog in case either side puts the other side on hold.

    If your BBS is not crash capable, really only for CGnat systems, you can be set to hold, and poll in to collect mail. I recommend not polling any more frequently than hourly.

    If you collect multiple networks from me, some of you do, then I suggest you set your BINKP session password to be the same for all networks, and present all your AKAs in the session - then you will receive all mail (for all networks) waiting for you in that session.

    Happy to review the hourly limit as appropriate - I'm not wanting to hinder mail flow or slow it down - I'm trying to target the script kiddies or the BBSes that are on auto-pilot that poll every minute.

    Any questions, please ask.

    ...лоеп
    --- SBBSecho 3.29-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
  • From fusion@21:1/616 to deon on Mon Mar 23 19:18:24 2026
    On 24 Mar 2026, deon said the following...

    Over the last week I've implemented rate limiting on clrghouz. I noticed recently quite a few polls coming from the same IP address every minute
    - some of them probably script kiddes, some of them BBSes that are on auto-pilot.

    did you have any measurable degredation of service with the connection frequency? or did it just bother you?

    so many people in the bbs hobby freak out over a few meaningless connections

    how large is the entire session in bytes? are you worrying about 100mb a
    year? 500mb? starts to feel a bit silly..

    --- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
    * Origin: cold fusion - cfbbs.net - grand rapids, mi (21:1/616)
  • From Vorlon@21:1/195 to fusion on Tue Mar 24 10:42:16 2026

    Hello fusion!

    23 Mar 26 19:18, you wrote to deon:

    Over the last week I've implemented rate limiting on clrghouz. I
    noticed recently quite a few polls coming from the same IP
    address every minute - some of them probably script kiddes, some
    of them BBSes that are on auto-pilot.

    did you have any measurable degredation of service with the connection frequency? or did it just bother you?

    so many people in the bbs hobby freak out over a few meaningless connections

    how large is the entire session in bytes? are you worrying about 100mb
    a year? 500mb? starts to feel a bit silly..

    There is no need what so ever to poll a hub/uplink every minute. If you are that desperate to get mail, then your in the wrong
    network (FTN's). Polling a system every 15 minutes is also way to much.

    The sweat spot is every half an hour. This is a hobby, not a commercial operation, and all hub's are providing this service for
    *free*. If a system is polling a hub system this much, they are pretty much being a dick!



    Vorlon


    --- GoldED+/LNX 1.1.5-b20250409
    * Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (21:1/195)
  • From deon@21:2/116 to fusion on Tue Mar 24 10:58:22 2026
    Re: Re: Hub 3 rate limiting
    By: fusion to deon on Mon Mar 23 2026 07:18 pm

    Howdy,

    did you have any measurable degredation of service with the connection frequency? or did it just bother you?

    I think about scaling in everything I do - and while I doubt scaling will be a (big) issue in this (dying) hobby I still apply those principles. Thus there is no reason for (potentially) everybody to poll to get mail, when a) mail flow is low and b) it would be sent to them anyway when there some.

    There was occassionally issues, especially with me debugging something, and the port being hounded by another system. I was debugging a "too many transactions" issue being reported by the DB that lead me to implement this.

    But it was also bothering me - I think somebody who polls every minute or so to pick up mail, when their system is capable of getting mail from me via the designed "CRASH" capability when i have mail for them is riduculous and a waste of time.

    And while I could live with that, its the systems that are on auto-pilot, who fall into the set and forget category I figured wouldnt mind, nor notice that their frequent polls were unsuccessful anyway, thus leaving free "slots" for those who do.


    ...лоеп
    --- SBBSecho 3.29-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
  • From fusion@21:1/616 to Vorlon on Mon Mar 23 21:47:34 2026
    On 24 Mar 2026, Vorlon said the following...

    There is no need what so ever to poll a hub/uplink every minute. If you are that desperate to get mail, then your in the wrong
    network (FTN's). Polling a system every 15 minutes is also way to much.

    on the contrary, i think that type of polling could be just fine. your phone wakes up from sleep to ask if you've received messages non stop forever. the design concept is specifically (to borrow fido wording) polling and not crash.

    The sweat spot is every half an hour. This is a hobby, not a commercial operation, and all hub's are providing this service for
    *free*. If a system is polling a hub system this much, they are pretty much being a dick!

    this is irrelevant. you're basically saying the equivalent of "this is a
    hobby, you can't expect them to tie up their phone for the bbs during the
    day. they need to make phone calls" it doesn't fit modern times.

    --- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
    * Origin: cold fusion - cfbbs.net - grand rapids, mi (21:1/616)
  • From The Wanderer@21:3/233 to fusion on Wed Mar 25 07:49:46 2026
    Re: Re: Hub 3 rate limiting
    By: fusion to Vorlon on Mon Mar 23 2026 09:47 pm

    There is no need what so ever to poll a hub/uplink every minute. If you
    on the contrary, i think that type of polling could be just fine. your

    Multiple people have just said this isn't fine. Just because systems are modern and/or on the internet doesn't mean being wasteful is OK.

    phone wakes up from sleep to ask if you've received messages non stop forever. the design concept is specifically (to borrow fido wording)

    These systems aren't Google - that's a bizarre and unfair false equivalence.

    day. they need to make phone calls" it doesn't fit modern times.

    Being wasteful isn't OK - there's limited resources, and it's wise to manage things accordingly.
    --- SBBSecho 3.37-Linux
    * Origin: Yak Station - Some yakkin' happenin'... (21:3/233)
  • From fusion@21:1/616 to The Wanderer on Wed Mar 25 12:16:52 2026
    On 25 Mar 2026, The Wanderer said the following...

    Re: Re: Hub 3 rate limiting
    By: fusion to Vorlon on Mon Mar 23 2026 09:47 pm

    There is no need what so ever to poll a hub/uplink every minute. If
    on the contrary, i think that type of polling could be just fine. you

    Multiple people have just said this isn't fine. Just because systems are modern and/or on the internet doesn't mean being wasteful is OK.

    concensus (especially here) does not equate to reality. while i agree this might matter on a 486 running some extremely crusty software, the majority of people don't fit in that category anymore.

    my node1.log file on mystic here is currently at 263k lines long. 99% bot traffic and 1% a few calls every day. the bbs is set to just hang up on non-ANSI users.

    could i set up a fancy firewall? mess around with fail2ban and a myriad of ip blacklists? limit my bbs only to certain regions? sure

    or i could do absolutely nothing whatsoever. let them connect all day long. doesn't affect me. not my ability to stream video, or download, or upload max speed.

    the result is the same. the computational resources would be basically the same too. effectively nothing. in the case of an ip blacklist it might be *more* because i'm connecting outward to check an ip, or searching a file for whether an ip is from russia or not. something a *real person* could perceive and be annoyed by.



    as an aside:

    where does this connection rate limit data get stored? i'm guessing it has to be cached somewhere. if it's in the database too we're talking:

    check associated account (done for both rate limited and valid anyways)

    check if the connection is too recent (only for rate limited)

    scan for new messages in subscribed echos. this would be expensive. EXCEPT that it already has to be done for every single crash message. if the account is one that polls just set a "has new mail" flag to 1. if the flag is 1 you hand over messages, if it's 0 you just close out as usual

    they can poll all day long every minute which they do anyways, the transaction and cpu effort is likely the same (gotta ask for the user data table anyways), and they can get their mail "seemingly" as frequently as a crash user would.


    Being wasteful isn't OK - there's limited resources, and it's wise to manage things accordingly.

    i can't say i agree that there are "limited resources" the way you think
    there are.

    --- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
    * Origin: cold fusion - cfbbs.net - grand rapids, mi (21:1/616)
  • From GRiM@21:3/234 to fusion on Wed Mar 25 11:55:31 2026
    where does this connection rate limit data get stored? i'm guessing it
    has to be cached somewhere. if it's in the database too we're talking:

    if we're gonna get technical here... caching the connection data would be trivial and most likely in memcached, redis hash table or something similar. It wouldn't need to persist in a db or disk unless he really wants to be a stickler about denying people after a restart and in that case it could be synced up periodically not in real-time.

    --- Mystic BBS v1.12 A49 2023/01/27 (Raspberry Pi/32)
    * Origin: The Dark Side (21:3/234)
  • From Warpslide@21:3/110 to deon on Wed Mar 25 13:56:00 2026
    On 24 Mar 2026, deon said the following...

    Over the last week I've implemented rate limiting on clrghouz.

    The rate limiting will impose the following limits:

    * Maximum 2 concurrent connections,
    * Maximum 5 connections in a 60 min period.

    These seem like sane limits.

    I have Mystic configured to send messages as I save them (they'll get tossed/sent within ~60 seconds of being saved). About the only way I could see myself making more than 5 connections in a 60 minute period is if I wrote and sent that many messages, which is unlikely.

    If that were to happen frequently, I could just have Mystic toss all of those messages once after I logged off rather than after each save.

    Any questions, please ask.

    How is the rate limit implemented? Would the connection attempt be dropped or rejected at the network level (fail2ban style) or would binkp still answer and reply with a rate limit error message?


    Jay

    ... Why yes, that IS a banana in my pocket!

    --- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
    * Origin: Northern Realms (21:3/110)
  • From Vorlon@21:1/195 to fusion on Thu Mar 26 09:45:10 2026

    Hello fusion!

    23 Mar 26 21:47, you wrote to me:

    [Drivel deleted]

    The sweat spot is every half an hour. This is a hobby, not a
    commercial operation, and all hub's are providing this service
    for *free*. If a system is polling a hub system this much, they
    are pretty much being a dick!

    this is irrelevant. you're basically saying the equivalent of "this is
    a hobby, you can't expect them to tie up their phone for the bbs
    during the day. they need to make phone calls" it doesn't fit modern times.


    Noted: You like acting like a "dick" to other sysops and hub operators.

    Good thing you have announced it to the network, so others can take note as well.



    Vorlon


    --- GoldED+/LNX 1.1.5-b20250409
    * Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (21:1/195)
  • From Vorlon@21:1/195 to fusion on Thu Mar 26 09:50:58 2026

    25 Mar 26 12:16, you wrote to The Wanderer:

    There is no need what so ever to poll a hub/uplink every
    minute.
    If on the contrary, i think that type of polling
    could be just fine. you

    Multiple people have just said this isn't fine. Just because
    systems are modern and/or on the internet doesn't mean being
    wasteful is OK.

    concensus (especially here) does not equate to reality. while i agree
    this might matter on a 486 running some extremely crusty software, the majority of people don't fit in that category anymore.

    Do you really think that *everyone* here is running a BBS on modern hardware and systems?
    There are plenty of bbs systems that are running on older systems and os's.

    Polling every minute, means that someone else is missing out.
    I *have* seen connections get rejected due to not enough slots on the hub system(s).
    Now I know that there might have been someone acting like a dick.

    Being wasteful isn't OK - there's limited resources, and it's
    wise to manage things accordingly.

    i can't say i agree that there are "limited resources" the way you
    think there are.

    So you like abusing sysops systems that are run from there home internet connection and system.
    So you like abusing the other sysops by being a dick.
    So you like abusing the freely provided connections from other sysops and being a dick.

    You polling every minute has this term applied to it from another FTN. "Excessively Annoying Behavior"

    Here's a hint for you. Not everyone has a huge upload connection to the internet.


    Vorlon


    --- GoldED+/LNX 1.1.5-b20250409
    * Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (21:1/195)
  • From deon@21:2/116 to Warpslide on Thu Mar 26 11:28:22 2026
    Re: Re: Hub 3 rate limiting
    By: Warpslide to deon on Wed Mar 25 2026 01:56 pm

    Howdy,

    * Maximum 2 concurrent connections,
    * Maximum 5 connections in a 60 min period.

    These seem like sane limits.

    Thanks, I was going for that :)

    I have Mystic configured to send messages as I save them (they'll get tossed/sent within ~60 seconds of being saved). About the only way I could see myself making more than 5 connections in a 60 minute period is if I wrote and sent that many messages, which is unlikely.

    I'm not 100% happy with implementing these - as it does drive a behaviour that I didnt want to drive - ie: an interactive chat via echomail/netmail that does sometimes happy. Thus, if you sent more than 5 message in an hour, the 6th wouldnt make it until the first connection "expired".

    I'll probably relax it if I can, ie: dont count a connection if you send something to the hub.

    How is the rate limit implemented? Would the connection attempt be dropped or rejected at the network level (fail2ban style) or would binkp still answer and reply with a rate limit error message?

    Haproxy is doing it for me - so its not getting to clrghouz at all.

    If you exceed the limit on the BINKP port, you should get an M_BSY message and the connection will drop. If you exceed it on the EMSI port, you'll get a "I'm busy message" on connect and then it will be dropped.


    ...лоеп
    --- SBBSecho 3.29-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
  • From fusion@21:1/616 to Vorlon on Thu Mar 26 08:50:19 2026
    On 26 Mar 2026, Vorlon said the following...

    concensus (especially here) does not equate to reality. while i agree this might matter on a 486 running some extremely crusty software, th majority of people don't fit in that category anymore.

    Do you really think that *everyone* here is running a BBS on modern hardware and systems?
    There are plenty of bbs systems that are running on older systems and os's.

    yes. almost everyone. does this surprise you? do you want to see screenshots of me blasting the living heck out of my crummy windows 7 laptop to show you what it's capable of?

    by the time people had access to multi-core cpus in the early 2000's it was fairly easy to support a thousand users on a single server (usenet server as an example.. the same type of complexity!)

    even if i give you a concession.. scale that back to a few hundred (windows & limited ram mostly) .. i think your little core2duo will do just fine..

    you know what has a few hundred.. nodes.. ? ;)

    Polling every minute, means that someone else is missing out.
    I *have* seen connections get rejected due to not enough slots on the hub system(s).

    the concept of a "slot" is *dumb*. simple as that. i also think it's incredibly stupid that modern BBSes have "nodes" still at all. it's a fake artificial concept that doesn't match the underlying system that supports it. you might as well make the node number the user's number from the user database.. it means nothing.

    there's no technical reason to set a max number of nodes at all anymore. if you managed to get 40 callers, let them all on. if you need to make doors work, max out the door game's config and assign a fossil port from a pool until they're gone.

    Here's a hint for you. Not everyone has a huge upload connection to the internet.

    this is a reach.. if you're hubbing for a message net i bet you have decent internet. not to mention the median upload speed for the US is like 10mbit, australia is 30-something. and it's getting difficult to get worse internet because it's /mandated by law/ in many places now.

    So you like abusing sysops systems that are run from there home internet connection and system.
    So you like abusing the other sysops by being a dick.
    So you like abusing the freely provided connections from other sysops
    and being a dick.

    don't let your emotions get to you man it's kind of weird. we just don't agree

    --- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
    * Origin: cold fusion - cfbbs.net - grand rapids, mi (21:1/616)
  • From Gamgee@21:2/138 to fusion on Thu Mar 26 08:21:47 2026
    fusion wrote to Vorlon <=-

    <SNIP garbage>

    So you like abusing sysops systems that are run from there home internet connection and system.
    So you like abusing the other sysops by being a dick.
    So you like abusing the freely provided connections from other sysops
    and being a dick.

    don't let your emotions get to you man it's kind of weird. we just
    don't agree

    Nobody else agrees with you either. You see anyone here agreeing with
    you? Take the hint.




    ... He does the work of 3 Men...Moe, Larry & Curly
    === MultiMail/Linux v0.52
    --- SBBSecho 3.37-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (21:2/138)
  • From fusion@21:1/616 to Gamgee on Thu Mar 26 09:30:20 2026
    On 26 Mar 2026, Gamgee said the following...

    fusion wrote to Vorlon <=-

    <SNIP garbage>

    So you like abusing sysops systems that are run from there home inter connection and system.
    So you like abusing the other sysops by being a dick.
    So you like abusing the freely provided connections from other sysops and being a dick.

    don't let your emotions get to you man it's kind of weird. we just don't agree

    Nobody else agrees with you either. You see anyone here agreeing with you? Take the hint.

    you don't convince anyone by saying nothing ;)

    --- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
    * Origin: cold fusion - cfbbs.net - grand rapids, mi (21:1/616)
  • From The Wanderer@21:3/233 to fusion on Thu Mar 26 07:12:51 2026
    Re: Re: Hub 3 rate limiting
    By: fusion to The Wanderer on Wed Mar 25 2026 12:16 pm

    Multiple people have just said this isn't fine. Just because systems are
    modern and/or on the internet doesn't mean being wasteful is OK.
    concensus (especially here) does not equate to reality. while i agree this

    Your perceived reality = the way things are everywhere for all software, hardware and network scenarios?

    Do you hear yourself? You've taken what people have said are actually going on and said "Well akshully"

    The arguments sound very much like someone who would have no idea how a DoS works. Resource starvation is very much a real thing, there are absolute limits on all computing platforms new and old, and being wasteful exacerbates performance problems and resource starvation.

    Working to protect against these kinds of issues well in advance is actually a smart thing to do. It has no relevance to your ability to watch Yootoob.
    --- SBBSecho 3.37-Linux
    * Origin: Yak Station - Some yakkin' happenin'... (21:3/233)
  • From fusion@21:1/616 to The Wanderer on Thu Mar 26 10:47:08 2026
    On 26 Mar 2026, The Wanderer said the following...

    concensus (especially here) does not equate to reality. while i agree

    Your perceived reality = the way things are everywhere for all software, hardware and network scenarios?

    i didn't say that. but the significant majority of them are, in fact, not resource limited in any way with regard to a BBS and all associated functionality.

    Do you hear yourself? You've taken what people have said are actually going on and said "Well akshully"

    "what people have said" .. who? you? Vorlon? are you two the two man team that dictates reality? what did you say is "going on" ?

    The arguments sound very much like someone who would have no idea how a DoS works. Resource starvation is very much a real thing, there are absolute limits on all computing platforms new and old, and being
    wasteful exacerbates performance problems and resource starvation.

    i'm acutely aware of how they work. my suggestion was that the mitigation proposed isn't any different from letting the user poll every minute. using resources to block vs using resources to just fulfil the request. they're both equivalent at this point. meaningless. some cycles on the cpu. we're taling about using a nuke to kill ants here.

    Working to protect against these kinds of issues well in advance is actually a smart thing to do. It has no relevance to your ability to
    watch Yootoob.

    there are two groups of connections involved in this conversation:

    users connecting *once a minute* to poll - there's a maximum of what, 56 people possible in this group? i take it back, that 486 could probably handle this amount of connections once a minute.

    bots that connect over and over non-stop - ban them outright

    i didn't have much of an opinion of it originally (my first post wasn't very long either) but now i think i'd personally optimize for allowing that connection per minute user. strive for excellence.

    and heaven forbid, don't connect to your sync web interface.. the web browser makes six connections at once. scary! ;)

    --- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
    * Origin: cold fusion - cfbbs.net - grand rapids, mi (21:1/616)
  • From GRiM@21:3/234 to fusion on Thu Mar 26 10:25:22 2026
    On 26 Mar 2026, fusion said the following...

    i didn't have much of an opinion of it originally (my first post wasn't very long either) but now i think i'd personally optimize for allowing that connection per minute user. strive for excellence.


    Or maybe just respect the limits requested by the man who provides a FREE service for a very niche and dying technology to a small group of users. You're expecting him to do more work because of your *opinion*? It's easier and cheaper to block these bad actors entirely. Deon is being overly gracious with these limits in my opinion.

    These echos do not get enough traffic to warrant polling once per minute - hard stop. Crash delivery reduces the need to poll unless you've been offline for awhile. There's no reason to poll more than once per hour.

    Even the most scalable APIs have rate limits. If you exceed the limits too frequently, you get blocked and eventually banned.

    --- Mystic BBS v1.12 A49 2023/01/27 (Raspberry Pi/32)
    * Origin: The Dark Side (21:3/234)
  • From Gamgee@21:2/138 to fusion on Thu Mar 26 10:51:41 2026
    fusion wrote to The Wanderer <=-

    users connecting *once a minute* to poll - there's a maximum of what,
    56 people possible in this group? i take it back, that 486 could
    probably handle this amount of connections once a minute.

    Any user or linked node that polled here once a minute would be
    immediately banned forever. End of conversation.

    Your claim that that is "OK" shows how little you know about the "real
    world" of BBSing.

    How about you just stop your trolling.


    ... Ignorance can be cured. Stupid is forever.
    === MultiMail/Linux v0.52
    --- SBBSecho 3.37-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (21:2/138)
  • From Gamgee@21:2/138 to GRiM on Thu Mar 26 10:51:41 2026
    GRiM wrote to fusion <=-

    On 26 Mar 2026, fusion said the following...

    i didn't have much of an opinion of it originally (my first post wasn't very long either) but now i think i'd personally optimize for allowing that connection per minute user. strive for excellence.

    Or maybe just respect the limits requested by the man who provides a
    FREE service for a very niche and dying technology to a small group of users. You're expecting him to do more work because of your *opinion*? It's easier and cheaper to block these bad actors entirely. Deon is
    being overly gracious with these limits in my opinion.

    These echos do not get enough traffic to warrant polling once per
    minute - hard stop. Crash delivery reduces the need to poll unless
    you've been offline for awhile. There's no reason to poll more than
    once per hour.

    Even the most scalable APIs have rate limits. If you exceed the limits too frequently, you get blocked and eventually banned.

    Absolutely correct on all counts.

    Maybe we can all just stop responding to the troll entirely.



    ... Gone crazy, be back later, please leave message.
    === MultiMail/Linux v0.52
    --- SBBSecho 3.37-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (21:2/138)
  • From fusion@21:1/616 to GRiM on Thu Mar 26 11:58:21 2026
    On 26 Mar 2026, GRiM said the following...

    On 26 Mar 2026, fusion said the following...

    i didn't have much of an opinion of it originally (my first post wasn very long either) but now i think i'd personally optimize for allowin that connection per minute user. strive for excellence.

    Or maybe just respect the limits requested by the man who provides a FREE service for a very niche and dying technology to a small group of users. You're expecting him to do more work because of your *opinion*? It's easier and cheaper to block these bad actors entirely. Deon is being overly gracious with these limits in my opinion.

    eh there's a reason i'm not messaging him directly. his response was to the point and that was that. no colorful words involved.

    everyone else, well, they got butthurt and responded to me first.

    --- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
    * Origin: cold fusion - cfbbs.net - grand rapids, mi (21:1/616)
  • From fusion@21:1/616 to Gamgee on Thu Mar 26 12:02:36 2026
    On 26 Mar 2026, Gamgee said the following...

    fusion wrote to The Wanderer <=-

    users connecting *once a minute* to poll - there's a maximum of what, 56 people possible in this group? i take it back, that 486 could probably handle this amount of connections once a minute.

    Any user or linked node that polled here once a minute would be immediately banned forever. End of conversation.

    it's nice to know your how you'd handle that situation.

    Your claim that that is "OK" shows how little you know about the "real world" of BBSing.

    i feel like this is the type of thing people said before binkd existed, and hpt, and his Clearing Houz. the list goes on. always someone defending the status quo

    How about you just stop your trolling.

    no trolling

    --- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
    * Origin: cold fusion - cfbbs.net - grand rapids, mi (21:1/616)
  • From The Wanderer@21:3/233 to fusion on Thu Mar 26 09:59:08 2026
    Re: Re: Hub 3 rate limiting
    By: fusion to The Wanderer on Thu Mar 26 2026 10:47 am

    Do you hear yourself? You've taken what people have said are actually
    going on and said "Well akshully"
    "what people have said" .. who? you? Vorlon? are you two the two man team that dictates reality? what did you say is "going on" ?

    It might be helpful to familiarize yourself with the reading functions of your BBS so you can go to the beginning of the topic to find out exactly what was meant. Deon would be the first that you're "Well akshully"ing

    i'm acutely aware of how they work. my suggestion was that the mitigation proposed isn't any different from letting the user poll every minute. using resources to block vs using resources to just fulfil the request. they're both equivalent at this point. meaningless. some cycles on the cpu. we're taling about using a nuke to kill ants here.

    *sigh*

    It's not just CPU bound - if you don't think there's memory involved and drive activity due to logging (if nothing else) and network time (however small), then I don't see how you're 'acutely aware' of what's being said.

    that connection per minute user. strive for excellence.

    That might be an exercise you could tickle yourself with - find out how efficient BINKP or EMSI are? You could always rip apart Deon's code and tell him how few resources it should require on a 486.
    --- SBBSecho 3.37-Linux
    * Origin: Yak Station - Some yakkin' happenin'... (21:3/233)
  • From The Wanderer@21:3/233 to fusion on Thu Mar 26 10:15:36 2026
    Re: Re: Hub 3 rate limiting
    By: fusion to GRiM on Thu Mar 26 2026 11:58 am

    eh there's a reason i'm not messaging him directly. his response was to

    So all the "just asking questions" bit wasn't in response to him? Must be a bug on my system here where it says it was from fusion to Deon. I'll get that looked at.

    everyone else, well, they got butthurt and responded to me first.

    Criticism of the disrespect and justifications for how you *think* the resource issues aren't actually a thing isn't being 'butthurt'.

    But I think you've shown where the end of this discussion is. Thanks.
    --- SBBSecho 3.37-Linux
    * Origin: Yak Station - Some yakkin' happenin'... (21:3/233)
  • From fusion@21:1/616 to The Wanderer on Thu Mar 26 13:31:08 2026
    On 26 Mar 2026, The Wanderer said the following...

    It might be helpful to familiarize yourself with the reading functions
    of your BBS so you can go to the beginning of the topic to find out exactly what was meant. Deon would be the first that you're "Well akshully"ing

    nope. just read it. no "well actually" there.

    It's not just CPU bound - if you don't think there's memory involved and drive activity due to logging (if nothing else) and network time
    (however small), then I don't see how you're 'acutely aware' of what's being said.

    lol what a joke. this is what you've got for "denial of service" ?

    --- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
    * Origin: cold fusion - cfbbs.net - grand rapids, mi (21:1/616)
  • From fusion@21:1/616 to The Wanderer on Thu Mar 26 13:38:59 2026
    On 26 Mar 2026, The Wanderer said the following...

    Re: Re: Hub 3 rate limiting
    By: fusion to GRiM on Thu Mar 26 2026 11:58 am

    eh there's a reason i'm not messaging him directly. his response was

    So all the "just asking questions" bit wasn't in response to him? Must
    be a bug on my system here where it says it was from fusion to Deon.
    I'll get that looked at.

    yes, please do. look at the list.

    also, you've never asked rhetorical questions to walk readers through a point you're trying to make?

    everyone else, well, they got butthurt and responded to me first.

    Criticism of the disrespect and justifications for how you *think* the resource issues aren't actually a thing isn't being 'butthurt'.

    i think i've been quite civil really. yet here we are. Vorlon thinks i'm acting like a "dick" Gamgee thinks i'm a "troll" .. you've managed to derail this conversation from the topic to *me* ..

    it's all good though :)

    --- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
    * Origin: cold fusion - cfbbs.net - grand rapids, mi (21:1/616)