[CQ-Contest] Cluster network update - was: Reverse BeaconNetwork - too much success?
david.kopacz at aspwebhosting.com
Sat Mar 6 09:26:02 PST 2010
It's a great idea to design a new system, but completely unnecessary.
The existing system already handles connectivity. All that needs to be done to stop abuse is to add in user authentication, replication and the ability for nodes to reject packets (spots, messages, announcements, etc) that are unauthenticated.
If centralized data storage is necessary, I am sure a few other amateurs, other than myself, would donate services to host master authentication lists.
David Kopacz, CTO
Rational Certified Developer, MCSE+I
Microsoft Certified Partner
4044 Fort Campbell Blvd, #308, Hopkinsville, Kentucky 42240 1.888.277.9320 U.S. & Canada
SIP: dial at freecall.aspwebhosting.com
The information contained in this electronic transmission is PRIVILEGED and CONFIDENTIAL information intended only to be viewed by the individual, entity or entities named as recipient(s). You are hereby notified that any dissemination, distribution or copy of this communication is strictly prohibited and a violation of your service agreement. If you have received this communication in error, please notify ASPwebhosting.com, LLC immediately by electronic mail or by telephone and permanently delete this message from your computer.
From: cq-contest-bounces at contesting.com [mailto:cq-contest-bounces at contesting.com] On Behalf Of Luc PY8AZT
Sent: Friday, March 05, 2010 8:25 AM
To: K1TTT; CQ-Contest at contesting.com
Subject: Re: [CQ-Contest] Cluster network update - was: Reverse BeaconNetwork - too much success?
You put DXCluster future in perspective. Yes, I agree, This 40 years old tecnology developed to run over packet radio has no fixing fo nowadays.
> The only way I can see the existing network going away is to design a
> new system from the ground up that includes strong backbone security,
> not too complicated but secure user identification, and all the other
> features that everyone wants to enable opting in/out of spotting,
> filters, larger volumes of spots, elimination of bottlenecks and
> loops, must run on various versions of windows, linux, mac's, must
> include telnet, rf, web, and some kind of new secure user access for
> future expansion, must include localized language capabilities and
> built in translation of talk/announce/comments, use the new non-ascii
> url system, accommodate skimmer spots automatically, allow Unicode
> character sets, email and bulletin distribution, emergency disaster
> overrides, etc, etc, etc. And then of course all the user logging and
> other access programs will have to update to handle whatever the
> authentication system is. This is obviously not a simple project...
> and it won't make the
I'm not a Geek (ah, I'm ham radio anyway), but reading this requirements for the new network, it looks like something that has been arround for while: Twitter network.
So, I wonder if we can use a Twitter API to setup a parallel network to transport DX Spots. It is very well docummentaded and integrated it to log software won't be hard.
140 caracters is just enough to send a spot, just like it is now.
ZY7C Team member
PT7AG (also PY8AZT, PX8C, ZZ8Z)
LABRE, ARRL, Uirapuru DX Club & ADXG Member __
Participe da Lista DXBrasil: dxbrasil+subscribe at googlegroups.com
CQ-Contest mailing list
CQ-Contest at contesting.com
More information about the CQ-Contest