[Dxspider-support] LU9DA-6 and QRZ.COM

David Spoelstra davids at mediamachine.com
Sat Jun 18 22:20:20 BST 2011


I just tried "sh/qrz n9kt" and I find that the command in no longer
working on my node and it has been up till now...
-David, N9KT

On Sat, Jun 18, 2011 at 3:34 PM, Anthony (N2KI) <n2ki at hvc.rr.com> wrote:
>
>  I emailed Fred and asked about the function of QRZ as a subscriber. If you are a subscriber (like myself) your sh/qrz function should work. I make my registered users aware of the fact that the sh/qrz functions works off of my personal subscription. However, non- registered users (I believe) also can use the sh/qrz command.
> Anthony (N2KI)
> www.n2ki.com
> Sent from BlackBerry
>
> -----Original Message-----
> From: "Ricardo Suarez" <eleu9da at ciudad.com.ar>
> Sender: dxspider-support-bounces at dxcluster.orgDate: Sat, 18 Jun 2011 18:47:20
> To: The DXSpider Support list<dxspider-support at dxcluster.org>
> Reply-To: The DXSpider Support list <dxspider-support at dxcluster.org>
> Subject: Re: [Dxspider-support] LU9DA-6 and QRZ.COM
>
> Hi, Dirk
>
> this new rules.....
>
>
> ***********
>
>
> QRZ Callsign Database Policy Change
>  Effective today, the QRZ Callsign database is changing the way we serve
> callsign data to our web (browser) based users. These changes have been
> brought on by a steadily increasing number of automated systems that access
> the QRZ data in so-called hidden or stealth mode. Such systems create a
> significant load on the QRZ servers and in doing so, deprive ordinary users
> of the performance that they deserve.
>
>  These robots (or 'bots') come in many forms. Some are designed to scrape
> the entire website for every piece of information we have. Others, known as
> "log checkers" are programs written by hams that repeatedly query the QRZ
> servers while working through lists of 10's of thousands of callsigns, doing
> it as rapidly as possible. Finally, some logging programs provide "auto
> fill" features that use the QRZ servers in the background to fetch callsign
> data as soon as the user types in a callsign.
>
>  For the past several years, QRZ has provided an XML Data service that was
> specifically designed to serve automated requests such as those described
> above. The XML service is an extremely lightweight and flexible system that
> places less than 1/10 of the load on our database that a "stealth" callsign
> lookup does on our regular pages. In addition, our advertisers are being
> deprived of ad exposures by these programs which routinely ignore or discard
> all such non-callsign data as they scrape our site.
>
>  Today's changes address these issues with a new set of constraints that we
> have developed with the goal of providing fast and fair access to all QRZ
> users. The following is a summary of what these measures mean:
>
>    a.. Callsign data, including name, address, and other QSL and logging
> information will be shown only to registered users of QRZ who are logged in
> at the time of the request. Guests that have not logged in will still see
> the callsign Bio page and pictures, but no callsign information will be
> shown.
>    b.. Registered users who are logged in will see the full detail on
> callsign pages.
>    c.. Ham users, i.e. those whose user name matches a callsign in our
> database, are limited to 150 callsign page lookups per day, not including
> their own callsign page.
>    d.. Non-ham users, i.e. users who aren't hams or don't have a username
> that matches one of our callsigns, will be limited to 25 callsign lookups
> per day.
>    e.. QRZ subscribers, of any type, are granted unlimited daily access to
> the QRZ callsign data.
>
>  These limits are designed for fairness and the vast majority of our ham
> users will never be affected by them, aside from the new requirement that
> you must be logged in to see callsign data. Note as well that when looking
> up or viewing your own callsign page that the act does not count against
> your daily lookup limit.
>
>  We ask for your support in accepting these changes and understanding that
> they were necessary in order to maintain the high level of service and
> support that our users have grown accustomed to.
>  Fred Lloyd, AA7BQ
>  Publisher, QRZ.COM
>  aa7bq at qrz.com
>
>
>
>
> ******
>
>
> Rick LU9DA
> ----- Original Message -----
> From: "Dirk Koopman G1TLH" <gb7tlh at dxcluster.org>
> To: "The DXSpider Support list" <dxspider-support at dxcluster.org>
> Sent: Saturday, June 18, 2011 6:25 PM
> Subject: Re: [Dxspider-support] LU9DA-6 and QRZ.COM
>
>
>> On 18/06/11 18:37, Ricardo Suarez wrote:
>>> Hello all
>>>
>>> Because the new rules from AA7BQ for the access to qrz.com's database,
>>> the node lu9da-6 have blocked the qrz search engine, sh/qrz.
>>>
>>
>> Er... what new rules?
>>
>>> Maybe in this days (holydays), I work in a new replacement, based in
>>> other ham radio callsing database.
>>>
>>
>> Which other databases are there that have the coverage of qrz.com?
>>
>> Dirk
>>
>> _______________________________________________
>> Dxspider-support mailing list
>> Dxspider-support at dxcluster.org
>> http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at dxcluster.org
> http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at dxcluster.org
> http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>



More information about the Dxspider-support mailing list