Return-Path: X-Spam-DCC: paranoid 104; Body=2 Fuz1=2 Fuz2=2 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on lipkowski.org X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00,DNS_FROM_AHBL_RHSBL, HTML_MESSAGE autolearn=no version=3.1.3 Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by paranoid.lipkowski.org (8.13.7/8.13.7) with ESMTP id u0OIrox7011206 for ; Sun, 24 Jan 2016 19:53:50 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1aNPjN-0008NN-BN for rs_out_1@blacksheep.org; Sun, 24 Jan 2016 18:49:45 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1aNPjM-0008NE-S8 for rsgb_lf_group@blacksheep.org; Sun, 24 Jan 2016 18:49:44 +0000 Received: from mail-vk0-f41.google.com ([209.85.213.41]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.86) (envelope-from ) id 1aNPiM-0003SX-O4 for rsgb_lf_group@blacksheep.org; Sun, 24 Jan 2016 18:49:43 +0000 Received: by mail-vk0-f41.google.com with SMTP id k1so63933589vkb.2 for ; Sun, 24 Jan 2016 10:48:27 -0800 (PST) X-DKIM-Result: Domain=gmail.com Result=Good and Known Domain DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=U+DbA5t1Ho2yiD4Fih9YgPJu8oQ0Aku0NhV1r09dFJs=; b=DKT/k8dDHEYwZITYduwxiP20RrZ0YeNCD0Dt3cF38P/SOA3ltyC+lCY/gO1d901Y3i c/7Jzy52CDfmBLdibvK6QyoSlKVaV5fWkzSna5R9QQ3fLKxO/ZBcJYfn5Or0ucV/m0yi QjnelqvTb8EEJCRU7JP5lZiqJuA7cRsdFgwa1iJ6gWVz+/WGD8gOhoyr8hKrIkLTf5h4 3QuTC+44FFM8o/9h8SsewXwREFfJSq2xGDXZCYMsf9s7+P0cWaL9cLMAGtCWJ8VECOub WszLBPP6PEK6hRSuxCsdGvwzyMuGbJE6yZLBF9kbMjR40T00GcDopnC/+6xtlrQml21U sicw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=U+DbA5t1Ho2yiD4Fih9YgPJu8oQ0Aku0NhV1r09dFJs=; b=gfVilrwUDlpYsTFP9uIdF0K07RSn3RdTkkOW3ZynFCbEFkOe1EMXWMUsgl5UjVpukk N4TUJLnkE66rTIpHAE1vy4X9jok+YPa/BJspmLHjqRFbL8OSeum7I4t+fI/FroNECsd/ 4lKWTXkeGa5Rdfwxh+keNgze8s2FCUU2lsi2LKl/Ye5Y2MtFeHtj3dd72wDBxkOS1iM3 WSl5Xgrys3UCTnr3MedAYxHeQzylyK9BZzWnPuQZlKjlv6mILIYbesFLLfw/XMWBCZm5 Y5fOreZMwrIQ+f3GxtvoRS9LzPGEkqt3F04iIInNvCeELytuht8jG7+9+aRl2oJd/vg6 jkLQ== X-Gm-Message-State: AG10YOQiQTnEfeo/iuAeH1hthzjduh3VNxmALDjqRq0lQSHkgBQOg0TYBcyFjBztCydPhgrTsk87lCiyg9qOOA== MIME-Version: 1.0 X-Received: by 10.31.170.196 with SMTP id t187mr8275681vke.66.1453661261084; Sun, 24 Jan 2016 10:47:41 -0800 (PST) Received: by 10.31.67.3 with HTTP; Sun, 24 Jan 2016 10:47:41 -0800 (PST) In-Reply-To: <56A51769.80605@gmx.net> References: <56A51769.80605@gmx.net> Date: Sun, 24 Jan 2016 12:47:41 -0600 Message-ID: From: John Langridge To: rsgb_lf_group@blacksheep.org X-Scan-Signature: fb42d311bf65eb51bbb8124890b4f977 Subject: Re: LF: WSPRnet problems Content-Type: multipart/alternative; boundary=001a114325ec173e66052a18e34e X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false X-Scanned-By: MIMEDefang 2.56 on 10.1.3.10 Status: O X-Status: X-Keywords: X-UID: 6491 --001a114325ec173e66052a18e34e Content-Type: text/plain; charset=UTF-8 I didn't really want to get into these details but the fact is that many of us have made efforts to contact Bruce over several months to no avail. That's not intended to be a criticism - real life gets in the way sometimes and that's ok. I, and others, are focusing on the fact that we need a solution. Resources in the form of money, hardware and brainpower have been offered by a number of people and have gone unacknowledged for a very long time. So this was not a "shoot from the hip" response. During the last major outage in December (not as bad as this one, mind you), there was talk about having discussions about the future of the system and where it needs to go. To my knowledge, that was the last time there was any mention of any talks about the direction of the system. The good news is that this system will still feed the WSPRnet site data in much the same way that WSPRnet feeds the PSKReporter site. The difference is that WSPR will feed the new system first, before passing the data on to WSPRNet which passes the data on the PSKreporter (in theory). SO WSPRnet does not go away, it just ceases to be the "bottle neck" for those who choose to use the new system. Hopefully this clarifies things. I am not the point person for this venture. I am only a frustrated user. 73! John On Sun, Jan 24, 2016 at 12:26 PM, Tobias DG3LV wrote: > Hi John ! > > The website owner(s) can be found at : > > http://www.whois.com/whois/wsprnet.org > > There is a lot of information on how you can get into contact with them. > It would be better hamspirit to help them solve the(ir) problems than to > think about establishing alternatives. Unless we know more exactly about > the true nature of the problems at wsprnet.org we cannot be of help. > > 73 de dg3lv Tobias > > Am 24.01.2016 um 17:38 schrieb John Langridge: > >> Good morning, >> >> As most ops already know, the WSPRnet website has been down more than up >> over the last several days. There do not appear to be any updates to >> the status posted any where, at least nothing current. Its almost as if >> a "take it or leave it " attitude is now the status quo. Its a free, >> volunteer-driven web site that I pay nothing for, so I can't argue. >> >> An alternate data warehousing and rendering system and website is being >> developed and tested by a father/son team but its not ready yet. >> Details will be forthcoming once appropriate. as well as instructions on >> the new data entry point. >> >> In the mean time, if you find spots in your WSPR console RX window that >> are noteworthy, please be sure to post them or send me a direct email >> with the details. I use this information as part of my daily 630-meter >> band report. As you can imagine, the WSPRnet outage has complicated the >> data gathering and reporting. >> >> Thanks for your assistance. 73! >> >> John KB5NJD / WG2XIQ.. >> >> >> > --001a114325ec173e66052a18e34e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I didn't really want to get into these details bu= t the fact is that many of us have made efforts to contact Bruce over sever= al months to no avail.=C2=A0 That's not intended to be a criticism - re= al life gets in the way sometimes and that's ok.=C2=A0 I, and others, a= re focusing on the fact that we need a solution.=C2=A0 Resources in the for= m of money, hardware and brainpower have been offered by a number of people= and have gone unacknowledged for a very long time.=C2=A0 So this was not a= "shoot from the hip" response.=C2=A0 During the last major outag= e in December (not as bad as this one, mind you), there was talk about havi= ng discussions about the future of the system and where it needs to go.=C2= =A0 To my knowledge, that was the last time there was any mention of any ta= lks about the direction of the system.=C2=A0

The good ne= ws is that this system will still feed the WSPRnet site data in much the sa= me way that WSPRnet feeds the PSKReporter site.=C2=A0 The difference is tha= t WSPR will feed=C2=A0 the new system first, before passing the data on to = WSPRNet which passes the data on the PSKreporter (in theory).=C2=A0=C2=A0= =C2=A0 SO WSPRnet does not go away, it just ceases to be the "bottle n= eck" for those who choose to use the new system.

Hop= efully this clarifies things.=C2=A0 I am not the point person for this vent= ure.=C2=A0 I am only a frustrated user.
73!

John

On = Sun, Jan 24, 2016 at 12:26 PM, Tobias DG3LV <DG3LV@gmx.net> wr= ote:
Hi John !

The website owner(s) can be found at :

http://www.whois.com/whois/wsprnet.org

There is a lot of information on how you can get into contact with them. It= would be better hamspirit to help them solve the(ir) problems than to thin= k about establishing alternatives. Unless we know more exactly about the tr= ue nature of the problems at wsprnet.org we cannot be of help.

73 de dg3lv Tobias

Am 24.01.2016 um 17:38 schrieb John Langridge:
Good morning,

As most ops already know, the WSPRnet website has been down more than up over the last several days.=C2=A0 There do not appear to be any updates to<= br> the status posted any where, at least nothing current.=C2=A0 Its almost as = if
a "take it or leave it " attitude is now the status quo.=C2=A0 It= s a free,
volunteer-driven web site that I pay nothing for, so I can't argue.

An alternate data warehousing and rendering system and website is being
developed and tested by a father/son team but its not ready yet.
Details will be forthcoming once appropriate. as well as instructions on the new data entry point.

In the mean time, if you find spots in your WSPR console RX window that
are noteworthy, please be sure to post them or send me a direct email
with the details.=C2=A0 I use this information as part of my daily 630-mete= r
band report.=C2=A0 As you can imagine, the WSPRnet outage has complicated t= he
data gathering and reporting.

Thanks for your assistance.=C2=A0 73!

John KB5NJD / WG2XIQ..




--001a114325ec173e66052a18e34e--