Hi,
I don't know if Aftershock only works with zone 1-6 for fidonet addresses because I don't seem to be able to get it to allow me to make an outbound connection to my 21:x system.
I have a 21:2/153.1 entry defined in my system, but do not see any connections being made into it.

Thanks,
--- SBBSecho 3.20-Linux
* Origin: 21:2/153 (21:2/153)

I don't know if Aftershock only works with zone 1-6 for fidonet addresses because I don't seem to be able to get it to allow me to make an outbound connection to my 21:x system.
I have a 21:2/153.1 entry defined in my system, but do not see any connections being made into it.

I think it does but Aftershock can only have one uplink.

My Aftershock is setup for Fidonet and it works well for me. I use it when I am away from home.

When you hit the "poll uplink" button in Aftershock you should be able to see the log on that screen saying what node it connected to and what files (if any) where tranfered in or out.

Have you been heard back from anyone in fidonet and got your node running now?

--- BBBS/Li6 v4.10 Toy-6
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

I think it does but Aftershock can only have one uplink.

I will check into this.
When I last looked the poll button was disabled.

Have you been heard back from anyone in fidonet and got your node running now?

Not yet. I feel as if I have been forgotten about or ignored entirely.
It has been 2 weeks at least since I reached out.
It seems that there doesn't seem to be any type of fall back system for when the primary person who can't do the tasks they have agreed to provide to the communityisn't abletoo.
If the people agree to provide such services tire of their positions they need to han them off to people who are able to pick up the slack.
Maybe this is one of the reasons why this net has the user base and traffic levels in the groups that it does over Fido.
The only real advantage that fido has at this moment is in its ability to route netmail to more systems than this network does.
I could be incorrect on this fact because I am a new sysop though.

Tom
--- SBBSecho 3.20-Linux
* Origin: 21:2/153 (21:2/153)

Khronos wrote to Al <=-

Have you been heard back from anyone in fidonet and got your node running

now

Not yet. I feel as if I have been forgotten about or ignored
entirely. It has been 2 weeks at least since I reached out.
It seems that there doesn't seem to be any type of fall back
system for when the primary person who can't do the tasks they
have agreed to provide to the communityisn't abletoo. If the
people agree to provide such services tire of their positions
they need to han them off to people who are able to pick up the
slack. Maybe this is one of the reasons why this net has the user
base and traffic levels in the groups that it does over Fido.

This issue is being discussed and hopefully fixed soon. Stay tuned.



... Pros are those who do their jobs well, even when they don't feel like it. === MultiMail/Linux v0.52
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (21:2/138)

Hi Avon,

On Wednesday May 03 2023, Avon said to Vorlon:

Avon to start pulling his hair out and yelling at the dog!

My dog and I are on quite good terms at the moment (phew)

Untill you give him a bone for a treat, then it's game on... #-)


\/orlon
aka
Stephen

Rocking FSXnet with an Amiga 4000 and Zeus BBS.

--- Zeus BBS 1.5
* Origin: -:-- Dragon's Lair --:- dragon.vk3heg.net Prt: 6800 (21:1/195.5)

According to the FSX Nodelist, you're in Winter Park? Not sure of the
state (I know of one in Florida and one in Colorado at least).

I might be able to shoot something up from another direction.

--- RATSoft/FIDO v09.14.95 [JetMail 1.01]
* Origin: STar Fleet HQ BBS - bbs.sfhqbbs.org:5983 (21:3/171)

According to the FSX Nodelist, you're in Winter Park? Not sure of the
state (I know of one in Florida and one in Colorado at least).

Hi,
I am in FL.
Based on the fact that fidonet does not have as many systems as it use to I wonder if things shouldn't just be controled by tge region level instead of by the net level.
I bet there are even some states that do not have any fidonet nodes at all.
At this point it is probably safe to say that there are more nodes out there than actual users. Either that or each user has setup their own node at this point or close to that.
--- SBBSecho 3.20-Linux
* Origin: 21:2/153 (21:2/153)

On 04 May 23 09:18:43, Khronos said the following to Commodore Clifford:

Based on the fact that fidonet does not have as many systems as it use to I wonder if things shouldn't just be controled by tge region level instead of the net level.

I have Netmailed you about this and did not receive a reply, but find you discussing this here. Before someone usurps this into something negative because "they can", let me respond in the most helpful way.

Fido has a Policy which is structured around the concept of Nets, Regions and Zones. While I agree with you that a lot of it is outdated... fact is thats how it is, its likely never to change. The application process is clear in that you must have a mailer which can demonstrate the ability to exchange Netmail. I assume you run a Synchronet system judging from your taglines.

For that you need a nodelist, no matter how much Rob Swindell complains or takes it upon himself to write rediculous application scripting nonsense that emails my personal address rather than Netmailing the appropriate NC or RC
just because "he can".

So you would merely examine the recent nodelist I publish to determine the appropriate Net to belong to and apply directly via Netmail. In this case NC135, then RC18... then if all fails, me, ZC1.

The problem is NC135 recently moved due to work and is still "settling in". The other problem is that this settling in has been weeks now, RC18 is well aware of that.

But another problem is RC18 also has some health issues, serious enough that I would not blame him for not making Fido a life priority but removing him from the role places a serious challenge on me to find a reliable replacement.

Lets give this another week or so then I will step in and list you manually.

Also, the sands of time for Fido moves a bit slower than FSX or Other Nets because it is not one person calling the shots. For this reason your patience is greatly appreciated.

Atreyu

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (21:1/176)

I have Netmailed you about this and did not receive a reply, but find you discussing this here.

Hi,
I was unsure what echo to post a conversation in about this topic in on fido so I thought I might discuss it here with some people who might be able to give me some insite into how some of the fidonet technologies work in general.
I did not intend to bash fidonet or anyone personally involved. I was just a bit fustrated with not knowing what I should do.

Before someone usurps this into something negative because "they can", let me respond in the
most helpful way.

Fido has a Policy which is structured around the concept of Nets, Regions and Zones. While I
agree with you that a lot of it is outdated... fact is thats how it is, its likely never to
change. The application process is clear in that you must have a mailer which can demonstrate
the ability to exchange Netmail. I assume you run a Synchronet system judging from your
taglines.

Yes, I run a Synchronet system here.
From the couple of systems I have tried this one seems to work the best with my screen reader.

For that you need a nodelist, no matter how much Rob Swindell complains or takes it upon himself
to write rediculous application scripting nonsense that emails my personal address rather than
Netmailing the appropriate NC or RC
just because "he can".

>

So you would merely examine the recent nodelist I publish to determine the appropriate Net to
belong to and apply directly via Netmail. In this case NC135, then RC18... then if all fails,
me, ZC1.

I agree having a nodelist is important.
In the ideal situation would I send netmail to Eric_Renfro@1:135/300 for requesting another node in Florida or some other address.
From reading the list manually this is what I could pick up, but I am still a bit unsure.

The problem is NC135 recently moved due to work and is still "settling in". The other problem
is that this settling in has been weeks now, RC18 is well aware of that.

I hope his move went well and I know how hard moving can be.
In my case their going to have to burn this place down to get me out even though I don't own. I have everything with in a 5 mile drive of me here.

But another problem is RC18 also has some health issues, serious enough that I would not blame
him for not making Fido a life priority but removing him from the role places a serious
challenge on me to find a reliable replacement.

It wouldn't be right to remove him unless he was ok with this or if he decided to step away himself and requested you do this.
I am new to this community so I need to stick around a while and learn from others before I feel it is right for me to step in and start accepting tasks from others to do.

Lets give this another week or so then I will step in and list you manually.

That's fine another week won't hurt.

Also, the sands of time for Fido moves a bit slower than FSX or Other Nets because it is not
one person calling the shots. For this reason your patience is greatly appreciated.

I don't mind waiting. I just didn't know that there were major issues going on in the lives of two people in the chain at the same time.
It was just bad timing on my part as to how long it would take to get a node created in my net.

Tom
--- SBBSecho 3.20-Linux
* Origin: 21:2/153 (21:2/153)

Re: Re: Point systems
By: Khronos to Atreyu on Thu May 04 2023 07:20 pm

So you would merely examine the recent nodelist I publish to determine the appropriate Net to
belong to and apply directly via Netmail. In this case NC135, then RC18... then if all fails,
me, ZC1.

I agree having a nodelist is important.
In the ideal situation would I send netmail to Eric_Renfro@1:135/300 for requesting another node in Florida or some other address.
From reading the list manually this is what I could pick up, but I am still a bit unsure.

<SNIP>

We are in the process of reorganizing things a bit... as of today I am the new NC for Net135. If you could netmail me from your FSX address, and include your email address in that message, we can take this to email and get you going in FidoNet. Please netmail me at: Dan Clough@21:2/138

Thanks and look forward to hearing from you.
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (21:2/138)

We are in the process of reorganizing things a bit... as of today I am the new NC for Net135.
If you could netmail me from your FSX address, and include your email address in that message,
we can take this to email and get you going in FidoNet. Please netmail me at: Dan
Clough@21:2/138

Hi,
Sent you netmail this morning.
Just writing here public wise incase my netmail function didn't work.
--- SBBSecho 3.20-Linux
* Origin: 21:2/153 (21:2/153)

Khronos wrote to Gamgee <=-

We are in the process of reorganizing things a bit... as of today I am the new NC for Net135.
If you could netmail me from your FSX address, and include your email

address

in that message, we can take this to email and get you going in FidoNet. Please netmail me at: Dan Clough@21:2/138

Hi,
Sent you netmail this morning.
Just writing here public wise incase my netmail function didn't
work.

I haven't seen any netmail arrive...

I see your email to me and RC18, it's late and I'm just getting home,
will reply to that email in the morning and we'll proceed. Thanks.


=== MultiMail/Linux v0.52
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (21:2/138)

Am 02.05.23 schrieb Khronos@21:2/153 in FSX_NET:

Hallo Khronos,

Does this network support point systems like fidonet does?

Yes, it does.
I'm primarily using an OpenXP setup for echomail instead of the BBS
interface or sth. linke GoldEd.

If you are searching for a boss node (ie. uplink), just send me a mail
:)

Regards,
Anna

--- OpenXP 5.0.57
* Origin: Imzadi Box Point (21:3/127.1)

Re: Re: Point systems
By: Atreyu to Khronos on Thu May 04 2023 10:42 am

For that you need a nodelist, no matter how much Rob Swindell complains or takes it upon himself to write rediculous application scripting nonsense that emails my personal address rather than Netmailing the appropriate NC or RC
just because "he can".

If it's a problem, just say so. There is or was a page at fido-z1.darkrealms.ca (your site) that directd FidoNet Zone applicants to that email addess. That's why my script sends applications there.
--
digital man (rob)

Synchronet/BBS Terminology Definition #92:
UTF-8 = 8-bit Unicode Transformation Format
Norco, CA WX: 63.3øF, 54.0% humidity, 13 mph S wind, 0.00 inches rain/24hrs
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (21:1/183)

Hi all,
Does this network support point systems like fidonet does?
I would like to play around with the After Shock client for Android with my bbs and I am wondering what is the best way to have this setup as.
Currently I am only connected to this net, but some day I will be added to fidonet when ever my NC gets around to processing my application.

Any thoughts will be great!
--- SBBSecho 3.20-Linux
* Origin: 21:2/153 (21:2/153)

Re: Point systems
By: Khronos to All on Tue May 02 2023 02:54 pm

Does this network support point systems like fidonet does?

Yes - many nodes have points...


...ëîåï
--- SBBSecho 3.15-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

On 02 May 2023 at 02:54p, Khronos pondered and said...

Any thoughts will be great!

Yes points are welcome, a number of nodes use one of their systems to fly their main fsxNet aka e.g. 21:1/101 and then run a few BBS that they feed as point systems from it, so BBS #2 may have a point address of 21:1/101.1

Point addressed netmail is routed by the HUBs to the main address and that system needs to route netmail onto it's points.

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Hi Khronos,

On Tuesday May 02 2023, Khronos said to All:

Hi all, Does this network support point systems like fidonet does? I

[...]

to fidonet when ever my NC gets around to processing my application.

It's your system, so you can do what you like as long as it dosn't cause
Avon to start pulling his hair out and yelling at the dog!

Btw: This system is running as a point of my main FTN hub...


\/orlon
aka
Stephen

Rocking FSXnet with an Amiga 4000 and Zeus BBS.

--- Zeus BBS 1.5
* Origin: -:-- Dragon's Lair --:- dragon.vk3heg.net Prt: 6800 (21:1/195.5)

On 03 May 2023 at 10:58a, Vorlon pondered and said...

Avon to start pulling his hair out and yelling at the dog!

My dog and I are on quite good terms at the moment (phew)

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)