[Dxspider-support] Interesting Problem with spots format and N1MM

[Björn Ekelund]

Not counting DXSpider, obviously, this colon has been there since forever.

I am on the development team of DXLog and we learned about this
inconsistency some time ago
by pure accident and after a minor redesign, DXLog has no problem with it

I am sure the N1MM guys can do the same, once they are informed.

As a logger developer I vote to either include it in all spots or remove it
entirely.
If it is not always there, I see no reason to have it at all.

Having semi-random elements in a protocol is just a source of problems.

Björn SM7IUN

Den sön 23 jan. 2022 kl 09:10 skrev Ian Maude via Dxspider-support <
dxspider-support at tobit.co.uk>:

> From my point of view, the DXCluster has to keep pace with the times.  RBN
> is a prime example.  There is only so much space on a line and callsigns
> get ever more complicated.  I remember the fun when Australia released
> novice calls with an extra character.
>
> The logging programs out there that connect to the clusters need to be
> able to access those facilities.  It is not up to the cluster software
> authors to change their software to suit the logging programs.  If logging
> software is no longer supported, then you either need to live with it or
> change program.
>
> If nothing changed, we would still be using DOS and AK1A.  Whilst I
> appreciate the frustration of logging program authors, the cluster is a
> server and the logging programs the clients.  You don’t change the server
> to suit the clients.
>
> There is a mailing list (cluster-tech) set up for discussion between
> cluster and logging program authors.  I am sure that everyone can work
> together to improve things for the end user, which is why all this is done
> in the first place.
>
> 73 Ian
>
> On 23 Jan 2022, at 07:57, Rob Harrison via Dxspider-support <
> dxspider-support at tobit.co.uk> wrote:
>
> Seems strange that the worlds number one cluster program and worlds number
> one contest logging program are incompatible with each other
>
> 73
>
> Rob Harrison
> 07826 958358
>
> Sent from my iPhone
>
> On 23 Jan 2022, at 07:26, Iain Philipps via Dxspider-support <
> dxspider-support at tobit.co.uk> wrote:
>
> 
> Question:
>
> Who set this “de facto standard”, exactly?
>
>
> 73 de WR3D
>
>
> *From:* Dxspider-support [mailto:dxspider-support-bounces at tobit.co.uk
> <dxspider-support-bounces at tobit.co.uk>] *On Behalf Of *Björn Ekelund via
> Dxspider-support
> *Sent:* 23 January 2022 05:25
> *To:* The DXSpider Support list
> *Cc:* Björn Ekelund
> *Subject:* Re: [Dxspider-support] Interesting Problem with spots format
> and N1MM
>
> DXLog used to have exactly the same problem and we ended up redesigning
> the spot parsing just because of this.
>
> DXSpider omits the colon after the spotter's callsign if it is longer than
> 7 characters. As I have pointed out to Dirk,
> I think this is a very unfortunate deviation from the de facto standard
> formatting of spots. Many software software
> rely on the colon being there and some of them are no longer maintained.
>
> Björn SM7IUN
>
> Den lör 22 jan. 2022 kl 14:28 skrev Rob Harrison via Dxspider-support <
> dxspider-support at tobit.co.uk>:
>
> Hi,
>
> I am trying to do the BARTG RTTY SPRINT today, but noticed that many spots
> are being filtered that should not be in N1MM
>
> If you look at the attached image you will see spots greyed out
> ((filtered) that shouldn't be. I have noticed that every spot that N1MM
> deems OK has a : (colon) at the end...but spots that don't have the colon
> such as OH9GHV are filtered...... looks like DXspider doesn't have room for
> the colon.
>
> Help
>
> 73 de Rob G4UJS
>
> *Rob Harrison*
>
> Green Lane House, Whixall, Shropshire, SY13 2PT.
> *M:* *07826 958358*
> *E: g4ujs at outlook.com <g4ujs at outlook.com>*
>
> *_________________________________________________________________________________________________*
>
> *This e-mail and any attachments are not guaranteed to be free from
> viruses, and are for the intended addressee(s) only*
> *and may contain confidential and/or privileged material, so if you are
> not a named or intended addressee, do not use,*
> *retain or disclose such information. *
> P *Consider the environment. Please don't print this e-mail unless you
> really need to.*
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
> <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.tobit.co.uk%2Fmailman%2Flistinfo%2Fdxspider-support&data=04%7C01%7C%7Cce4c1c707a054e641d7408d9de4193c3%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637785195702002362%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=l70bl94zTtgf4inh%2BM1wj17BnVSmRsGvU0YsggKJE78%3D&reserved=0>
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20220123/0a597e7d/attachment.htm>