<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
<div>
<div>
<div dir="ltr">Brilliant Dirk!!! I will reboot my system today. Think I’m on build 444 of the Mojo distribution</div>
</div>
<div id="ms-outlook-mobile-signature">
<div><br>
</div>
Sent from <a href="https://aka.ms/o0ukef">Outlook for iOS</a></div>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Dxspider-support <dxspider-support-bounces@tobit.co.uk> on behalf of dxspider-support-request@tobit.co.uk <dxspider-support-request@tobit.co.uk><br>
<b>Sent:</b> Thursday, November 24, 2022 8:52:16 AM<br>
<b>To:</b> dxspider-support@tobit.co.uk <dxspider-support@tobit.co.uk><br>
<b>Subject:</b> Dxspider-support Digest, Vol 238, Issue 27</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Send Dxspider-support mailing list submissions to<br>
dxspider-support@tobit.co.uk<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
or, via email, send a message with subject or body 'help' to<br>
dxspider-support-request@tobit.co.uk<br>
<br>
You can reach the person managing the list at<br>
dxspider-support-owner@tobit.co.uk<br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Dxspider-support digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. DXSpider mojo update (Dirk Koopman)<br>
2. Re: DXSpider mojo update (Danilo Brelih)<br>
3. Re: DXSpider mojo update (Jan)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 23 Nov 2022 23:57:53 +0000<br>
From: Dirk Koopman <djk@tobit.co.uk><br>
To: Dxspider-Support <dxspider-support@dxcluster.org><br>
Subject: [Dxspider-support] DXSpider mojo update<br>
Message-ID: <21a333ec-0374-1795-db76-3aac98e87e04@tobit.co.uk><br>
Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>
<br>
In the light of some nastiness that seems increasingly to happen during <br>
major contests, and after several requests, I have revamped the <br>
"BadWords" system to be all "regex" based (a.k.a badw_regex) and done <br>
away with both the badword and badw_regex files. These have been <br>
replaced with a file called badword.new which now contains a simple list <br>
of? "words", some of which are instantly recognisable and others which <br>
look misspelled - as they don't seem to have enough consonants. They are <br>
what I call word "stems".<br>
<br>
This file is interesting, but is not (normally) sysop maintained. It is <br>
maintained and generated by the set/badword and unset/badword commands <br>
which will take words that you think are bad; which add or remove them <br>
from the system. You can list the current ones with show/badwords. There <br>
is a default list of words that is installed by the update automatically.<br>
<br>
Internally these word "stems" are converted in perl regexes which will <br>
match this sort of thing:<br>
<br>
So the stem "SOD" regex looks like:<br>
<br>
SOD = \bS+[\s\W]*[O0]+[\s\W]*D<br>
<br>
This will match: sod SOD s0D sods Sodding s0dd1nnnng etc<br>
<br>
Another example might be:<br>
<br>
TERORIST = <br>
\bT+[\s\W]*E+[\s\W]*R+[\s\W]*[O0]+[\s\W]*R+[\s\W]*[I1]+[\s\W]*S+[\s\W]*T<br>
<br>
This will obviously match the very bad spelled 'terorist', but also: <br>
TERRORIST terr0r1st 'TeeeErro0r 11ii1sts' etc.<br>
<br>
***<br>
<br>
It would be good to get as many sysops to update ASAP (i.e. before the <br>
weekend) as this will cut down on the distribution of some quite <br>
offensive (mainly Spanish at the moment) entirely made up spots.<br>
<br>
***<br>
<br>
There is (English) help available for the {set,unset,show}/badword <br>
commands. There are also some remarks worth reading in the Changes file. <br>
The command 'load/badword' still does what always did, but you should <br>
not need to use it any more. These commands are all sysop only and <br>
cannot be accessed remotely.<br>
<br>
If a user "swears" then a message will appear in the debug file which <br>
can be tracked with 'watchdbg swore'. By default, if a user uses three <br>
swear words they are automatically disconnected. This count persists <br>
during the whole session, so a user can use them up by using three <br>
(different) bad words in one announce command or use the same (or <br>
different) one over three commands minutes or hours apart over a <br>
session. This limit can be changed with a 'set/var <br>
$DXCommandmode::maxbadcount = <number>' command at runtime or in the <br>
startup file. This limit only affects locally connected users. Incoming <br>
PC protocol that trigger a badword are just dropped.<br>
<br>
As far as a locally connected user is concerned, it appears as though <br>
the offending commands have worked, in that they appear on their screen. <br>
Well, at least until they use too many and are logged out.<br>
<br>
If you are a sneaky sort of sysop you can set maxbadcount to 0, which <br>
will not log the user out, thus giving the impression that all is fine - <br>
but nothing is sent out to other locally connected users or nodes.<br>
<br>
Enjoy.<br>
<br>
73 Dirk G1TLH<br>
<br>
PS This is the first on my list of fixes / enhancements, so there will <br>
be further updates for other known issues over the next few weeks.<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20221123/b2a52fb4/attachment-0001.htm">https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20221123/b2a52fb4/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Thu, 24 Nov 2022 08:27:00 +0100<br>
From: Danilo Brelih <danilo.brelih@siol.net><br>
To: Dirk Koopman via Dxspider-support <dxspider-support@tobit.co.uk><br>
Subject: Re: [Dxspider-support] DXSpider mojo update<br>
Message-ID: <cff7bc26-de51-ed86-4423-df91084f2d22@siol.net><br>
Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>
<br>
Dirk Koopman via Dxspider-support je 24.11.2022 ob 0:57?napisal:<br>
<br>
Brilliant. We have the biggest cqww cw contest this weekend hopefully a lot of <br>
dxspiders will be updated as soon as possible. As I am not a system uptime freak <br>
I usually do a cluster reboot before a major contest whether it is necessary or not.<br>
<br>
GL Dan S50U<br>
<br>
<br>
<br>
<br>
> In the light of some nastiness that seems increasingly to happen during major <br>
> contests, and after several requests, I have revamped the "BadWords" system to <br>
> be all "regex" based (a.k.a badw_regex) and done away with both the badword <br>
> and badw_regex files. These have been replaced with a file called badword.new <br>
> which now contains a simple list of "words", some of which are instantly <br>
> recognisable and others which look misspelled - as they don't seem to have <br>
> enough consonants. They are what I call word "stems".<br>
><br>
> This file is interesting, but is not (normally) sysop maintained. It is <br>
> maintained and generated by the set/badword and unset/badword commands which <br>
> will take words that you think are bad; which add or remove them from the <br>
> system. You can list the current ones with show/badwords. There is a default <br>
> list of words that is installed by the update automatically.<br>
><br>
> Internally these word "stems" are converted in perl regexes which will match <br>
> this sort of thing:<br>
><br>
> So the stem "SOD" regex looks like:<br>
><br>
> SOD = \bS+[\s\W]*[O0]+[\s\W]*D<br>
><br>
> This will match: sod SOD s0D sods Sodding s0dd1nnnng etc<br>
><br>
> Another example might be:<br>
><br>
> TERORIST = <br>
> \bT+[\s\W]*E+[\s\W]*R+[\s\W]*[O0]+[\s\W]*R+[\s\W]*[I1]+[\s\W]*S+[\s\W]*T<br>
><br>
> This will obviously match the very bad spelled 'terorist', but also: TERRORIST <br>
> terr0r1st 'TeeeErro0r 11ii1sts' etc.<br>
><br>
> ***<br>
><br>
> It would be good to get as many sysops to update ASAP (i.e. before the <br>
> weekend) as this will cut down on the distribution of some quite offensive <br>
> (mainly Spanish at the moment) entirely made up spots.<br>
><br>
> ***<br>
><br>
> There is (English) help available for the {set,unset,show}/badword commands. <br>
> There are also some remarks worth reading in the Changes file. The command <br>
> 'load/badword' still does what always did, but you should not need to use it <br>
> any more. These commands are all sysop only and cannot be accessed remotely.<br>
><br>
> If a user "swears" then a message will appear in the debug file which can be <br>
> tracked with 'watchdbg swore'. By default, if a user uses three swear words <br>
> they are automatically disconnected. This count persists during the whole <br>
> session, so a user can use them up by using three (different) bad words in one <br>
> announce command or use the same (or different) one over three commands <br>
> minutes or hours apart over a session. This limit can be changed with a <br>
> 'set/var $DXCommandmode::maxbadcount = <number>' command at runtime or in the <br>
> startup file. This limit only affects locally connected users. Incoming PC <br>
> protocol that trigger a badword are just dropped.<br>
><br>
> As far as a locally connected user is concerned, it appears as though the <br>
> offending commands have worked, in that they appear on their screen. Well, at <br>
> least until they use too many and are logged out.<br>
><br>
> If you are a sneaky sort of sysop you can set maxbadcount to 0, which will not <br>
> log the user out, thus giving the impression that all is fine - but nothing is <br>
> sent out to other locally connected users or nodes.<br>
><br>
> Enjoy.<br>
><br>
> 73 Dirk G1TLH<br>
><br>
> PS This is the first on my list of fixes / enhancements, so there will be <br>
> further updates for other known issues over the next few weeks.<br>
><br>
><br>
><br>
> _______________________________________________<br>
> Dxspider-support mailing list<br>
> Dxspider-support@tobit.co.uk<br>
> <a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
<br>
<br>
-- <br>
Gorje, Cerkno h=604m <<a href="https://s50e.si/gorje.html">https://s50e.si/gorje.html</a>><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20221124/1eab4045/attachment-0001.htm">https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20221124/1eab4045/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Thu, 24 Nov 2022 09:51:57 +0100<br>
From: Jan <cluster@pa4jj.nl><br>
To: Dirk Koopman via Dxspider-support <dxspider-support@tobit.co.uk><br>
Subject: Re: [Dxspider-support] DXSpider mojo update<br>
Message-ID: <ae86c5d4-58dc-9946-1b41-eb4a00bab23f@pa4jj.nl><br>
Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>
<br>
Maybe a silly question but<br>
how / where do I update the mojo branch?<br>
<br>
<br>
Op 24-11-2022 om 00:57 schreef Dirk Koopman via Dxspider-support:<br>
> In the light of some nastiness that seems increasingly to happen <br>
> during major contests, and after several requests, I have revamped the <br>
> "BadWords" system to be all "regex" based (a.k.a badw_regex) and done <br>
> away with both the badword and badw_regex files. These have been <br>
> replaced with a file called badword.new which now contains a simple <br>
> list of "words", some of which are instantly recognisable and others <br>
> which look misspelled - as they don't seem to have enough consonants. <br>
> They are what I call word "stems".<br>
><br>
> This file is interesting, but is not (normally) sysop maintained. It <br>
> is maintained and generated by the set/badword and unset/badword <br>
> commands which will take words that you think are bad; which add or <br>
> remove them from the system. You can list the current ones with <br>
> show/badwords. There is a default list of words that is installed by <br>
> the update automatically.<br>
><br>
> Internally these word "stems" are converted in perl regexes which will <br>
> match this sort of thing:<br>
><br>
> So the stem "SOD" regex looks like:<br>
><br>
> SOD = \bS+[\s\W]*[O0]+[\s\W]*D<br>
><br>
> This will match: sod SOD s0D sods Sodding s0dd1nnnng etc<br>
><br>
> Another example might be:<br>
><br>
> TERORIST = <br>
> \bT+[\s\W]*E+[\s\W]*R+[\s\W]*[O0]+[\s\W]*R+[\s\W]*[I1]+[\s\W]*S+[\s\W]*T<br>
><br>
> This will obviously match the very bad spelled 'terorist', but also: <br>
> TERRORIST terr0r1st 'TeeeErro0r 11ii1sts' etc.<br>
><br>
> ***<br>
><br>
> It would be good to get as many sysops to update ASAP (i.e. before the <br>
> weekend) as this will cut down on the distribution of some quite <br>
> offensive (mainly Spanish at the moment) entirely made up spots.<br>
><br>
> ***<br>
><br>
> There is (English) help available for the {set,unset,show}/badword <br>
> commands. There are also some remarks worth reading in the Changes <br>
> file. The command 'load/badword' still does what always did, but you <br>
> should not need to use it any more. These commands are all sysop only <br>
> and cannot be accessed remotely.<br>
><br>
> If a user "swears" then a message will appear in the debug file which <br>
> can be tracked with 'watchdbg swore'. By default, if a user uses three <br>
> swear words they are automatically disconnected. This count persists <br>
> during the whole session, so a user can use them up by using three <br>
> (different) bad words in one announce command or use the same (or <br>
> different) one over three commands minutes or hours apart over a <br>
> session. This limit can be changed with a 'set/var <br>
> $DXCommandmode::maxbadcount = <number>' command at runtime or in the <br>
> startup file. This limit only affects locally connected users. <br>
> Incoming PC protocol that trigger a badword are just dropped.<br>
><br>
> As far as a locally connected user is concerned, it appears as though <br>
> the offending commands have worked, in that they appear on their <br>
> screen. Well, at least until they use too many and are logged out.<br>
><br>
> If you are a sneaky sort of sysop you can set maxbadcount to 0, which <br>
> will not log the user out, thus giving the impression that all is fine <br>
> - but nothing is sent out to other locally connected users or nodes.<br>
><br>
> Enjoy.<br>
><br>
> 73 Dirk G1TLH<br>
><br>
> PS This is the first on my list of fixes / enhancements, so there will <br>
> be further updates for other known issues over the next few weeks.<br>
><br>
><br>
><br>
> _______________________________________________<br>
> Dxspider-support mailing list<br>
> Dxspider-support@tobit.co.uk<br>
> <a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
<br>
-- <br>
73<br>
Jan<br>
PA4JJ<br>
______________________________________________________<br>
<br>
My dxspider clusters running 24/7 on a raspberry pi 2<br>
pa4jj-2 telnet 77.174.195.163 port 7300<br>
pa4jj-3 telnet 77.174.195.163 port 7388<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20221124/e7e01300/attachment.htm">https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20221124/e7e01300/attachment.htm</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
Dxspider-support mailing list<br>
Dxspider-support@tobit.co.uk<br>
<a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
<br>
<br>
------------------------------<br>
<br>
End of Dxspider-support Digest, Vol 238, Issue 27<br>
*************************************************<br>
</div>
</span></font></div>
</body>
</html>