Order Tray | Contact Us | Home | SIG Lists

[aprssig] Tier 2 Status

Steve Dimse steve at dimse.com
Thu Jun 22 13:15:48 UTC 2006


On Jun 22, 2006, at 7:25 AM, AE5PL Lists wrote:

>> -----Original Message-----
>> From: Steve Dimse
>> Posted At: Wednesday, June 21, 2006 10:10 PM
>> Subject: Re: [aprssig] Tier 2 Status
>>
>> On Jun 21, 2006, at 10:50 PM, AE5PL Lists wrote:
>>
>>> I'm sorry to the SIG, but I have to ask: "Who are these
>> powers that be
>>> you speak of?"
>>
>> You have made it very clear from your comments I am not a to
>> be considered a power in the APRS IS. Who is? As far as I am
>> concerned, it is you because you write the code (and as I've
>> said many times "he who writes the code, rules"), and the
>> three core sysops.
>
> Steve, you control who is in the core.  Period.

That is untrue. The only way a server  can be added to the core is if  
you give them the software, and the existing core sysops add the  
appropriate interconnects to their configuration. I cannot do any of  
those tasks.

>>> Seems to me that you still own the aprs.net domain and that you are
>>> still the sole purveyor of core server domain names...
>>
>> You know very well I've always added any aprs.net name people
>> have asked for, including for the core servers.
>
> Have you?

Yes. Name one single time I have not done this. Just one, in the 8  
years 11 months this domain has been mine. If you can't, I demand an  
apology for this unjustified attack on my stewardship of the aprs.net  
domain.

> Then where are all of these core servers you say should
> exist.  You control the domain; you control who is going to be one of
> the core servers.

This is simply not true. If I give an existing hub the name  
fourth.aprs.net and add it to roatate.aprs.net, dose that make it a  
core server? Certainly not, no one knows better than you what makes a  
server a core server, it is the interconnects between them, not the  
name. Take the reverse situation, say you give the software to a  
user, who adds 1313 interconnects to the existing core servers and  
the core servers add the interconnect to their configuration.  
Regardless of whether I make changes in the  aprs.net domain, that  
server is now a core server. Certainly the new server would get more  
traffic with the name changes, but it is not the name that makes it a  
core server. And as I say, I would never not update the aprs.net  
name. Never have, never will.

Steve K4HG




More information about the aprssig mailing list