| |
ZL3AI > APRDIG 23.04.03 19:49l 265 Lines 9511 Bytes #999 (0) @ WW
BID : 64022_ZL3VML
Read: GUEST
Subj: TAPR Digest, Apr 14, 1/3
Path: DB0FHN<DB0RGB<OK0PPL<OK0NAG<9A0BBS<VK6BBS<VK3AVE<LU6DTS<W4JAX<EA2RCF<
EB8BBM<EA5DVS<EA3RKU<EA1URF<EC1K<CT1ARB<CS1AAS<CT1EJC<CT4DK<ON0BEL<
SP7MGD<VK7AX<ZL2BAU<ZL3VML
Sent: 030416/1107Z @:ZL3VML.#80.NZL.OC #:64022 [Chch-NZ] FBB7.00i $:1166-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Monday, April 14, 2003.
1. Re: findU2 down
<LYR30130-128528-2003.04.13-11.34.49--andrew.rich#bigpond.com@lists.tapr.org>
2. Re: findU2 down
3. aprs server status database
4. Re: findU2 down - Now Calendar
5. Symbols spreadsheet
6. Opening up the proverbial can o' worms
7. RE: Opening up the proverbial can o' worms
8. Re: Opening up the proverbial can o' worms
9. And again in PDF format...
10. Re: Mixing up the proverbial can o' worms
11. Re: Opening up the proverbial can o' worms
12. Re: Opening up the proverbial can o' worms
13. Re: Opening up the proverbial can o' worms
14. Re: Opening up the proverbial can o' worms
15. Re: Opening up the proverbial can o' worms
16. Re: Opening up the proverbial can o' worms
17. Re: Opening up the proverbial can o' worms
18. Hiking/Backpacking symbol...
19. Re: Opening up the proverbial can o' worms
20. RE: Hiking/Backpacking symbol...
21. AEA PK-12 settings
22. Re: Opening up the proverbial can o' worms
23. Re: Opening up the proverbial can o' worms
24. APRS+SA v2.21 Patch File for EchoLink Tab
25. Re: Opening up the proverbial can o' worms
26. Re: Opening up the proverbial can o' worms
----------------------------------------------------------------------
Subject: Re: findU2 down
<LYR30130-128528-2003.04.13-11.34.49--andrew.rich#bigpond.com@lists.tapr.org>
From: Andrew Rich <andrew.rich@bigpond.com>
Date: Mon, 14 Apr 2003 17:39:46 +1000
X-Message-Number: 1
I can do that for you Bob, what fields do you want ?
On Mon, 2003-04-14 at 01:43, Bob Bruninga wrote:
>On Sat, 12 Apr 2003, Guy Story, KC5GOI wrote:
>
>>Once again, we were not aware of this event and I no longer have time to
>>watch each and every email that goes through the APRSSIGs to watch for
>>every event that may be happening.
>
>This is a problem we have wanted to solve for years. What we need is
>someone to write an APRS-SCHEDULE WEB page so that users can self-log
>upcoming events. None of us can keep track of it all. For years, I
>tried to keep an updated events calandar, but APRS is just too vast to
>keep up with manually.
>
>So here is what we need someone to do with a WEB page:
>1) It presents to users a time-sequenced schedule of events.
>2) It allows people to post schduled events and to list a point of
>contact and a WEB page link.
>3) It sorts daily and puts old events in a HIstory link.
>
>Anyone?
>
>Bob, WB4APR
--
Andrew Rich <andrew.rich@bigpond.com>
----------------------------------------------------------------------
Subject: Re: findU2 down
From: Bob Bruninga <bruninga@usna.edu>
Date: Mon, 14 Apr 2003 08:33:50 -0400 (EDT)
X-Message-Number: 2
On Mon, 14 Apr 2003, Andrew Rich wrote:
>I can do that for you Bob, what fields do you want ?
I'd imagine:
Start Date/time
End Date/time
City, State, Country
WEB page
Email of Point of COntact
COmments
And I'd prefer that it be kept concise and not too wordy so that you see
a lot of the schedule on one screen...
Bob
----------------------------------------------------------------------
Subject: aprs server status database
From: wes@johnston.net
Date: Mon, 14 Apr 2003 11:51:45 -0400 (EDT)
X-Message-Number: 3
I've added a database to my web site for aprs server status. If you know
of a down server, please log in and report it, or if you are planning to
take down your server at some time in the future, log the incident here.
You will be emailed a password at signup, nothing fancy.
http://wes.johnston.net/aprs
When visitors first open the web site, they are presented with a list of
servers which are down today. Future entries are not shown, and past
entries are kept in the database but also not shown. The database is
searchable for those wishing to log in.
As usual, if I missed anything or you'd like another field added, let me
know.
Note that if you know of something new and interesting, visitors to the
site are welcome and encouraged to add information and articles related to
APRS.
Wes
----------------------------------------------------------------------
Subject: Re: findU2 down - Now Calendar
From: Bill Vodall <wa7nwp@jnos.org>
Date: Mon, 14 Apr 2003 08:59:42 -0700
X-Message-Number: 4
>This is a problem we have wanted to solve for years. What we need is
>someone to write an APRS-SCHEDULE WEB page so that users can self-log
>upcoming events.
>
>So here is what we need someone to do with a WEB page:
>1) It presents to users a time-sequenced schedule of events.
>2) It allows people to post schduled events and to list a point of
>contact and a WEB page link.
>3) It sorts daily and puts old events in a HIstory link.
There are several calendar programs available. Here's an example of one
we use:
http://www.wetnet.net/cgi-bin/Calcium36?Op=ShowIt&CalendarName=WETNET&Amount=Moh
nt&NavType=Absolute&Type=Block
Personally I just keep events in a Wiki page.
http://www.jnos.org/cgi-bin/moin.cgi/ComingEvents
Soon I'll have a dedicated Wiki set up for the PNW APRS group
(http://www.nwaprs.org) and then our group will have a page to use. The
Wiki gives easy tables, hot links and anybody can update it.
Another option is to use a Yahoo Group but that's like dropping shields
when you see a Borg ship approaching. The more we do independent from the
major services - the better.
73,
Bill - WA7NWP
----------------------------------------------------------------------
Subject: Symbols spreadsheet
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Mon, 14 Apr 2003 21:49:23 -0000
X-Message-Number: 5
I've posted the first (far from complete) draft of the OpenTRAC symbol set
at http://www.opentrac.org/symbols.xls. Pretty much everything in the APRS
symbol tables is covered, with the exception of generic markers like X and
dot. Those might go under a separate category, but I prefer not to use them
- the purpose of the symbol set is to indicate the nature of the object, not
to choose which picture you want to display.
If you have suggestions for additions or changes, just email me. Preferably
with a hierarchy showing how it should be organized - it's one thing to
think up lists of items that you'd like to display, and another to try to
figure out a logical structure to put them in.
Also, keep in mind that things like HAZMAT are separate attributes,
identified elsewhere in the message. It's up to the client program to
modify the displayed symbol appropriately.
Scott
N1VG
----------------------------------------------------------------------
Subject: Opening up the proverbial can o' worms
From: "Wes Johnston" <wes@johnston.net>
Date: Mon, 14 Apr 2003 17:56:20 -0400
X-Message-Number: 6
Since we haven't had a good flame war about NO-ID/ID and power poles
recently.....<grin>
If I am sending health and welfare traffic during some storm or other
catastrophe over a packet channel. I want to obsure the names of , say,
recently deceased people before the families can be notified.... and I
obscure the name with a well known code such as ROT13, does that violate the
FCC rules about cyphers on the ham bands?
FWIW, I'm a member of the local State Guard (militia), and we'll do
something like this on "our" assigned frequency with a different not so well
known method. My question is more specific to ham radio.
And yes, this has to do with APRS b/c we could be sending names as aprs
messages.
Wes
----------------------------------------------------------------------
Subject: RE: Opening up the proverbial can o' worms
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Mon, 14 Apr 2003 22:08:04 -0000
X-Message-Number: 7
From what I remember of the Extra exam, the wording had something to do with
the intent to conceal the meaning of a message. The only exception is
satellite control links.
There's also something about any reasonably technically competent user being
able to figure out a mesasge based on published standards, so maybe ROT13
would get around that. I have my doubts, though, since it's still your
intent to conceal.
----------------------------------------------------------------------
Subject: Re: Opening up the proverbial can o' worms
From: "Curt Mills, WE7U" <hacker@tc.fluke.com>
Date: Mon, 14 Apr 2003 15:10:09 -0700 (PDT)
X-Message-Number: 8
On Mon, 14 Apr 2003, Wes Johnston wrote:
>Since we haven't had a good flame war about NO-ID/ID and power poles
>recently.....<grin>
>
>If I am sending health and welfare traffic during some storm or other
>catastrophe over a packet channel. I want to obsure the names of , say,
>recently deceased people before the families can be notified.... and I
>obscure the name with a well known code such as ROT13, does that violate the
>FCC rules about cyphers on the ham bands?
My vote would be yes, even though that's about as simple a cipher as
you can get.
Use simple compression rather than a cipher. That still makes it
unreadable to the general populace. Serves your purpose, and a worthwhile
purpose it is!
Perhaps you want something that can be human-translated rather than
computer-translated on both ends though?
--
Curt Mills, WE7U hacker_NO_SPAM_@tc.fluke.com
Senior Methods Engineer/SysAdmin
"Lotto: A tax on people who are bad at math!"
"Windows: Microsoft's tax on computer illiterates!" -- WE7U
"The world DOES revolve around me: I picked the coordinate system!"
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
