Sometimes I have to start what I write with something like that, or it may seem like I'm being sarcastic or insulting when I'm not (see tagline). :)
I've never used either, so I didn't realize the difference. Could (or is) the above even used with multiple "hubs" that can still connect to each other? Or is there still one designated hub that everyone chooses to connect to?
Well, yes and no (and no offense taken). With IBOL, the local mod still runs and displays and accepts wall posts just fine regardless of the state of the hub. Then once the hub comes back online, any new posts get exchanged during polling. The user doesn't know (or care) that some other system is down.
because it's trying to connect in real time to something that isn't there. I've seen it take a long time (a minute or more) to time out in such cases, doing nothing but display a black screen. Most users aren't that patient and assume the board isn't working right and hang up.
Codefenix wrote to Accession <=-
I've never used either, so I didn't realize the difference. Could (or is) the above even used with multiple "hubs" that can still connect to each other? Or is there still one designated hub that everyone chooses to connect to?
Do you mean for prolonged hub downtimes which might prompt a NC change?
I imagine what holds true for standard hub-node polling holds true for this, since it's just messages sent through an echo.
With multi-node software running binkp, we could re-arrange networks
quite easily. Fidonet could be one zone, I've thought. I always worry
about how many nodes are on auto-pilot and would fall off the network
if you made a "flag day" change. But, then again, were those nodes
were contributing to the network?
I've never used either, so I didn't realize the difference. Could
(or is) the above even used with multiple "hubs" that can still
connect to each other? Or is there still one designated hub that
everyone chooses to connect to?
Do you mean for prolonged hub downtimes which might prompt a NC change?
I imagine what holds true for standard hub-node polling holds true for
this, since it's just messages sent through an echo.
Some of the Fidonet wonks rave about the "fidoweb", which is another
word for having multiple network feeds, then using your BBS software's
dupe detection to weed out the duplicates. Apparently someone felt
censored once by a hub filtering messages and this became a workaround.
this is why i like the qwk setup better in some ways.. it doesn't really matter if systems go away because they just stop polling and their
account gets pruned. if they come back, they create an account and are
right back where they were.
this is why i like the qwk setup better in some ways.. it doesn't
really matter if systems go away because they just stop polling
and their account gets pruned. if they come back, they create an
account and are right back where they were.
With multi-node software running binkp, we could re-arrange networks
quite easily. Fidonet could be one zone, I've thought. I always worry
about how many nodes are on auto-pilot and would fall off the network
if you made a "flag day" change. But, then again, were those nodes
were contributing to the network?
Accession wrote to poindexter FORTRAN <=-
Some people don't like single points of failure, that's all.. and for
the record, it was an entire zone being censored.. not just "someone".
You seem to be having a hard time keeping your facts straight lately,
it seems. :|
| Sysop: | John F Kennedy |
|---|---|
| Location: | Quebec, Canada |
| Users: | 39 |
| Nodes: | 15 (0 / 15) |
| Uptime: | 176:03:52 |
| Calls: | 799 |
| Calls today: | 799 |
| Messages: | 14,619 |
| Posted today: | 2 |