Bjorn,

You have inserted a new node in the nodelist with a non-permissable entry. I have under the table discussed this with you but you simply seem adamant to not comply and play a weird game.

You have given said node the dynamic-IP of "eljaco.se" which makes it impossible to reach as a call to it will land on your system...

You have been very uncooperative to solve this ... every call destined for 2:203/910 landing on your system received a "No such AKA" warning.


? 18 Jun 21:54:54 [24796] called 2:203/910@fidonet, but remote has no such AKA

To solve that, you have added 2:203/910 to your own list of AKA's, which to my mind is non-permissable as well, and which doesn't work either ... it gives a password-error ... so, an hour later it read ...

? 18 Jun 22:54:55 [26472] rerror: Bad password

My last request, with multiple usage of the word "please", was greeted with the mention you couldn't deal with it as we are nearing the summer solstice. In the same message you formulated it with a lot of disdain as if I were a novice-sysop.

In Belgium we have a saying "Met alle Chinezen, maar niet met den dezen" ... try thatone on someone else, but not on me.

For all intents and purposes, said node cannot be contacted. To preserve the attempt to join by a new sysop, this entry should be 'Pvt' with the IBN/INA-part dropped. After your refusal to cooperate in private, I'm now telling you this openly.

As an encore, impersonating a sysop by hi-jacking his/her nodenumber and faking the symbolic-IP address makes you vulnerable for a formal complaint should anyone get any wild ideas about trying.

Take care,

\%/@rd

--- DB4 - 20230201
* Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)

Hello Ward!

20 Jun 26 23:20, you wrote to Bjorn Felten:

As a newcomer to RC, I strongly support maintaining standards, and I am surprised that experienced Fido representatives are unable to handle these basic matters. I wonder why someone would act this way. I recall seeing that sysop name in the St. Petersburg nodelist in the past, and I have a feeling that Bjoern may have been trying to help someone who had lost their connection to FidoNet for some reason.

To be honest, we have several similar cases in R42. For example, the most recent one involved 2:463/0 (Andrei Dzedolik). Usually, we assist such individuals in improving their connection rather than assigning a new node number. Is it possible that Bjoern was trying to help someone, but simply handled it in an improper way?

Karel

--- GoldED+/LNX 1.1.5-b20240209
* Origin: Plast DATA (2:423/39)

Karel,

I recall
seeing that sysop name in the St. Petersburg nodelist in the past, ...

Then you have a very good memory because the node in St.Petersburg was lifted from the nodelist 23 years ago. And I had to look it up ...

I have a feeling that Bjoern may have been trying to help someone who had lost their connection to FidoNet for some reason.

Well, you are wrong in that assumption.

Aleksey contacted me with a request for help in getting a point-number somewhere ... anywhere ... As he is living in Sweden now, a Swedish point therefor made sense and I refered it to Bjorn ... who wasted no time in making a circus out of it.

Bjorn alternates stubbornness with genius and has already demonstrated this more than once in the past. When he's obviously wrong, he'll never admit.

His current behavior is one of his less inspired moments ... and I don't like being addressed as if I only got my node number last week. That approach is well known by other ZCs as well when odd stuff is involved.

Enjoy the remainder of the week-end ... a good day in Belgium, sunny, we're not frying ... surviving ... BBQ-ed ribs and beer is an asset to overcome the shortfallings of summer.

And I got a football indigestion...

\%/@rd

--- DB4 - 20230201
* Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)