On Sat, 22 Mar 2014 19:33:14 +0100, YT9TP Pedja yt9tp@uzice.net wrote:

On 22.3.2014 16:14, Geoff Joy wrote:

...

Wiki's are a collective effort, what have you done to fix the flaws you see there? Have you signed on as a Wiki editor? Have you written articles for inclusion on that Wiki? Links go stale, there has to be an "ugly bag of mostly water" behind the keyboard to keep a document tree fresh and healthy, otherwise off-site links go bad when someone drops dead or an organization folds. What are you doing in YOUR spare time.

I see a whole lot of room for improvement and a whole lot of networking experts who can "advance the state of the art" but who don't seem to be inclined to actually publish what they know.

What I see above from both of you is "this is a mess, someone needs to clean it up, but that someone isn't going to be me". I must boldly state that if you have the time to discern a problem and criticize a state of affairs, you have the time to take ownership of that problem and fix it.

I think you are on wrong track.

You might be right.

Don't you see the pattern. People who consider themselves knowledgeable about networking want to get involved in 44net but they cannot understand it because there is lack of proper documentation.

Those who understand networking would be most likely to be able to write proper documentation for 44net since the protocols involved are no different than any other internet. AX.25 is nothing more than a modified X.25. The only thing that changes is the medium of transmission and the latencies.

If they cannot understand and ask for better documentation, so they cannot learn, they are the last persons that should be advised to write that documentation.

I perceived hams criticizing other hams for not being "friendly" to newcomers, I have been a victim of unfriendly hams myself in the past and went out of my way to create a new environment in response to that. My Elmer was the father of a high school friend who took time out at the end of his workday to mentor us in Morse code. I didn't go on to get my license until college, however.

Documentation should be written by people who do have very good knowledge and experience with 44net.

I agree. And that experience best comes with experimentation. But is 44net so different that it's a completely different environment than hardwired networking? I learned what I know about the protocols by installing JNOS on a PC and poking and sniffing packets on air when Windows didn't have a TCP/IP stack. Why is the reverse so difficult?

Current Wifi technology follows directly from the original wireless development hams pioneered. Even SSID comes from us. The original development follows directly from the University of Hawaii's experiments with RF networking, which was well documented. Most of this isn't "webified", it's all plain text on the FTP site. But yes, my generation has let the new generation down, we left a plain text legacy where everyone wants it all on a searchable Wiki and color pictures.

73 Pedja YT9TP

p.s. I am posting this directly to you, besides sending it on the list as my message cannot go through the list - almost all my messages return back marked as blacklisted.

I'm posting my reply directly and also to the list so perhaps someone can review the list logs and fix the rejection. Thanks for your input.