[Dxspider-support] R: DXSpider mojo update
Howard Leadmon
howard at leadmon.net
Thu Nov 24 18:43:22 GMT 2022
It did the same to me, I just let it set, in about 10 min it finally
connected and updated..
73's de WB3FFV
---
Howard Leadmon - WB3FFV
PBW Communications, LLC
http://www.pbwcomm.com
On 11/24/2022 7:12 AM, iz6fxs--- via Dxspider-support wrote:
>
> sysop at cluster:/spider$ git pull -v
>
> Looking up scm.dxcluster.org ... done.
>
> Connecting to scm.dxcluster.org (port 9418) ... ^C
>
> It hangs there… Am I the only one?
>
> Norm IZ6FXS
>
> *Da:* Dxspider-support <dxspider-support-bounces at tobit.co.uk> *Per
> conto di *Joaquin via Dxspider-support
> *Inviato:* giovedì 24 novembre 2022 11:57
> *A:* dxspider-support at tobit.co.uk
> *Cc:* Joaquin <joaquin at cronux.net>
> *Oggetto:* Re: [Dxspider-support] DXSpider mojo update
>
> Yes, build 448 is the latest.
> The capture is the response to the sh/ver all command
>
> Kin
>
> El 24/11/2022 a las 11:31, Ian Maude via Dxspider-support escribió:
>
> Both GB7MBC and G4ELI-9 were updated first thing this morning, or
> is 448 not the latest?
>
> 73 Ian
>
>
>
> On 24 Nov 2022, at 10:24, Joaquin via Dxspider-support
> <dxspider-support at tobit.co.uk>
> <mailto:dxspider-support at tobit.co.uk> wrote:
>
> The tests with the new build 448 have been more than satisfactory.
>
> Now to wait for the nodes to be updated. In the last query
> there are still few updated:
>
> DL8FCL-7 5457 448 Yes Yes
> DU3TW-1 5457 448 Yes Yes
> EA2CW-2 5457 448 Yes Yes
> EA3CV-2 5457 448 Yes Yes
> EA3CV-3 5457 448 Yes Yes
> EA4URE-2 5457 448 Yes Yes
> EA4URE-3 5457 448 Yes Yes
> EA4URE-5 5457 448 Yes Yes
> G4ELI-9 5457 448 Yes Yes
> GB7MBC 5457 448 Yes Yes
> IK5ZUK-6 5457 448 Yes Yes
> IK7NXU-6 5457 448 Yes Yes
> IK8HJC-6 54 448 Yes Yes
> IZ5FSA-6 5457 448 Yes Yes
> JG1VGX-9 5457 448 Yes Yes
> VE3CGR-5 5457 448 Yes Yes
> W8BS-2 5457 448 Yes Yes
> WB3FFV-2 54 448 Yes Yes
>
> Thank you very much Dirk.
>
> Kin EA3CV
>
> El 24/11/2022 a las 0:57, Dirk Koopman via Dxspider-support
> escribió:
>
> In the light of some nastiness that seems increasingly to
> happen during major contests, and after several requests,
> I have revamped the "BadWords" system to be all "regex"
> based (a.k.a badw_regex) and done away with both the
> badword and badw_regex files. These have been replaced
> with a file called badword.new which now contains a simple
> list of "words", some of which are instantly recognisable
> and others which look misspelled - as they don't seem to
> have enough consonants. They are what I call word "stems".
>
> This file is interesting, but is not (normally) sysop
> maintained. It is maintained and generated by the
> set/badword and unset/badword commands which will take
> words that you think are bad; which add or remove them
> from the system. You can list the current ones with
> show/badwords. There is a default list of words that is
> installed by the update automatically.
>
> Internally these word "stems" are converted in perl
> regexes which will match this sort of thing:
>
> So the stem "SOD" regex looks like:
>
> SOD = \bS+[\s\W]*[O0]+[\s\W]*D
>
> This will match: sod SOD s0D sods Sodding s0dd1nnnng etc
>
> Another example might be:
>
> TERORIST =
> \bT+[\s\W]*E+[\s\W]*R+[\s\W]*[O0]+[\s\W]*R+[\s\W]*[I1]+[\s\W]*S+[\s\W]*T
>
> This will obviously match the very bad spelled 'terorist',
> but also: TERRORIST terr0r1st 'TeeeErro0r 11ii1sts' etc.
>
> ***
>
> It would be good to get as many sysops to update ASAP
> (i.e. before the weekend) as this will cut down on the
> distribution of some quite offensive (mainly Spanish at
> the moment) entirely made up spots.
>
> ***
>
> There is (English) help available for the
> {set,unset,show}/badword commands. There are also some
> remarks worth reading in the Changes file. The command
> 'load/badword' still does what always did, but you should
> not need to use it any more. These commands are all sysop
> only and cannot be accessed remotely.
>
> If a user "swears" then a message will appear in the debug
> file which can be tracked with 'watchdbg swore'. By
> default, if a user uses three swear words they are
> automatically disconnected. This count persists during the
> whole session, so a user can use them up by using three
> (different) bad words in one announce command or use the
> same (or different) one over three commands minutes or
> hours apart over a session. This limit can be changed with
> a 'set/var $DXCommandmode::maxbadcount = <number>' command
> at runtime or in the startup file. This limit only affects
> locally connected users. Incoming PC protocol that trigger
> a badword are just dropped.
>
> As far as a locally connected user is concerned, it
> appears as though the offending commands have worked, in
> that they appear on their screen. Well, at least until
> they use too many and are logged out.
>
> If you are a sneaky sort of sysop you can set maxbadcount
> to 0, which will not log the user out, thus giving the
> impression that all is fine - but nothing is sent out to
> other locally connected users or nodes.
>
> Enjoy.
>
> 73 Dirk G1TLH
>
> PS This is the first on my list of fixes / enhancements,
> so there will be further updates for other known issues
> over the next few weeks.
>
>
>
>
> _______________________________________________
>
> 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
>
>
> _______________________________________________
> 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/20221124/cc14387e/attachment.htm>
More information about the Dxspider-support
mailing list