At the moment I'm not going to join in any bulletin discussion of UI-
View on the packet network, because I think it's only a matter of time
before the usual wreckers get at the topic. However, I have been keeping
an eye on the comments being made.
The idea that has been suggested of setting the unproto address to UI-
View is potentially a good one, because I realised some time ago that
there was a problem of telling who was running the program and who was
just putting out compatible beacons. The one slight problem is that an
unproto address of UIVIEW isn't APRS compatible.
That is, of course, only a problem for APRS users! UI-View will accept
beacons sent to any address, because it looks at the structure of the
frame, not the address. I've always thought that APRS has got it wrong,
at least as far as usage in the UK is concerned, by recognising only a
few unproto addresses. However, I thought it was worth mentioning it,
before some APRS users pointed it out.
Someone suggested using an unproto address of APRS - I would definitely
not recommend that, because UI-View is not compatible with most of what
APRS does, and should not be regarded as an APRS program.
One thing that has occurred to me is that using different unproto
addresses could be used as a filter between different groups of UI-View
users sharing the same frequency. Perhaps it's looking too far ahead,
but I will make it possible, in the next update, to exclude by unproto
address besides excluding by callsign.
--
Roger Barker, G4IDE roger@...
Boston, UK
