Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to Support Echo For JAMNNTPD NNTP S...  <--  <--- Return to Home Page
   Networked Database  Support Echo For JAMNNTPD NNTP S...   [84 / 238] RSS
 From   To   Subject   Date/Time 
Message   Rick Christian    mark lewis   JamNNTPd that WORKS   November 4, 2016
 1:30 PM *  

   Hello mark!

03 Nov 16 20:48, you wrote to Nicholas Boel:

 ml> the main thing that strikes me in all of this is that fidonet is and
 ml> always has been a hobby network for those wanting to experiment with

You, others, and I are ovbiously in this for a far different reasons!

Even in the 90's when I started originally..

I don't think of this as mainly a hobby.

And NO WAY is this an "experiment!" This is a means to a goal.

Example:

Echos are essentially "support groups" or maybe discussion groups for a topic
be it software, golded, binkd, jamnntpd, crashmail.....etc...

They exist to *help* others get things going or resolve a problem.. at least
thats the goal, as *I* see it...

Then as now, I operated my node to get access to those echos primarily, and to
send emails all over the place via FTN tech... I later setup a UUCP gate for
emails from the local net to go out via my UUCP account. I setup and maintained
 a private FTN net to get a very old niche group into the at the time cutting
edge stuff. That group doesn't exist... run over by ... nevermind.. suffice it
.. run over by the web....

I prefer echos v. web forums.. I am just not into that...never was.. part of
some of the things I do right now via some Yahoo things are going to move to
FTN based stuff, or more aptly RETURN to it. As I know VZW will start chopping
off the dead wood, and this is definitely one of them.

 ml> store-and-forward networking... i really have to wonder, sometimes, if
 ml> some folks just don't know that or if they may have lost that
 ml> vision... this especially pertains to some of our Z2 brethern who are

I don't know what the issue or schizim is with Z2 and/or others v. Z1.. and
honeslty I don't care.... but what I do see is that in this there is the same
issue..as here.

Simply, you, others and I are on different ends of the spectrum of things.. I
am not here to exeriment, and this aint no hobby!

If that is how you view it, then that is your take...

Just as many things have an impact on how I view compiling.... and bluntly this
 fiasco has done nothing to change, but only enhance my ill view of it! And
since the resolution to this was to use *PRE-COMPILED* binaries anyway... I
think that speaks volumes enough.


Rick


--- GoldED+/LNX 1.1.5-b20160322
 * Origin: Vina's Talos Moon Base Alpha (1:135/377)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to Support Echo For JAMNNTPD NNTP S...  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0996 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_4v1354s0thcqvoq45o5fpbjaq5, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_4v1354s0thcqvoq45o5fpbjaq5, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_4v1354s0thcqvoq45o5fpbjaq5, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0