<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 06/07/2021 04:54, rin JG1VGX via
Dxspider-support wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CANbv8NM2y7ozSOskdJ=+o+9-0=7zToNwQHoTckMCx4rDxKrf9A@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">Hi All,</div>
<div dir="auto"><br>
</div>
<div dir="auto">I have played with filters myself and here is a
summary.</div>
<div dir="auto"><br>
</div>
<div dir="auto">What I wished to do:</div>
<div dir="auto">- Allow Q:1 spots system-wide</div>
<div dir="auto">- Set Q:2-9 as default for a new user</div>
<div dir="auto">- Users can allow Q:1 as necessary</div>
<div dir="auto"><br>
</div>
<div dir="auto">What I have done:</div>
<div dir="auto">- set $minqual = 1 as Andy G4PIQ has suggested</div>
<div dir="auto">(But this cannot be a permanent solution because
/local/RBN.pm needs to be updated manually each time
/perl/RBN.pm is updated)</div>
<div dir="auto">- then played with various user filters, eg.
acc/rbn, rej/rbn, user_default, node_default</div>
<div dir="auto"><br>
</div>
<div dir="auto">What I have found:</div>
<div dir="auto">- 'node_default' This looks like a different
animal and serves no purpose in this case?</div>
<div dir="auto">- 'user_default' This does the job, but cannot be
overriden by users' own filters. Not useful?</div>
</blockquote>
<br>
This is news to me. The thing about user_default is that is applies
*only until* a user defines a personal filter for a category, it
then will <u>override</u> the user_default with their preferences.
The only caveat is that there seems to be a bug (in all branches)
where "frequently" the user filter does not "take" until the user
logs out and then in again.<br>
<br>
"Frequently" in this context means: "never - when I am trying to
find the fault" or "often enough for users to get confused and
annoyed so that they logout, fume, wait a day or two and then login
again when it now (magically) works".<br>
<br>
<blockquote type="cite"
cite="mid:CANbv8NM2y7ozSOskdJ=+o+9-0=7zToNwQHoTckMCx4rDxKrf9A@mail.gmail.com">
<div dir="auto">- finally got the gist that a single 'acc/ A' and
a 'rej/ not A' mean the same, but multiple 'acc' filters works
like additive (A OR B) while 'rej' works like multiplicative (A
AND B).</div>
<div dir="auto">- if no /rbn filter is defined, /spots filters
apply for both regular and RBN spots. But once any /rbn filter
is defined, filters must be defined separately for both regular
and RBN spots.</div>
<div dir="auto"><br>
</div>
</blockquote>
<br>
Please do "help filter" or read it on the wiki. It's meant to be
"intuitive", but then it would be - to me. It's not quite as you
describe it. But in essence it's this:<br>
<br>
<br>
0. If there is no filter for this "thing" then nothing is filtered.
It is just passed on.<br>
1. For every type of thing you can filter (spots, announcements etc)
there as 10 filter slots.<br>
2. You can have a different filter in each slot.<br>
3. Each slot is tried in the order 0 -> 9. This is "ladder
logic".<br>
4. Empty slots are ignored.<br>
5. For every slot that matches: if it is a REJ filter it immediately
rejects that "thing"; if is an ACC filter it will accept that
"thing". No further processing on that "thing" occurs for that
filter.<br>
6. REJ filters are tried first; if it falls out of the bottom then
the ACC filters are tried and if it falls out of the bottom then
that "thing" is rejected.<br>
<br>
The point of this is that nobody gets negative logic right the first
time (nor the second or third time) however good one might be. Hence
the REJ filters - they throw away everything you DON'T want. The ACC
filters (only) give you what you DO want. You are therefore using
positive logic to get what you want (much more of the time). <br>
<br>
As we are all consenting sysops here, you should be made aware of
the implications of input filters on your feeds (or node_default
file for that "thing"). Any input filter will affect what gets into
your node for onward processing. It is dumped at source. BTW a more
efficient way of reducing what your users can see is to
rcmd/<node partner> acc/spots by_zone 1,2,3 (for instance) and
your node will never see any spots from spotters in other zones.
Saves <strike>a lot</strike> some bandwidth. <br>
<br>
<blockquote type="cite"
cite="mid:CANbv8NM2y7ozSOskdJ=+o+9-0=7zToNwQHoTckMCx4rDxKrf9A@mail.gmail.com">
<div dir="auto">So far my purpose was not fulfilled but currently
I have at my node:</div>
<div dir="auto">- Set $minqual = 1</div>
<div dir="auto">- In case users bothered by busted Q:1 spots, I
would suggest them to use</div>
<div dir="auto"> acc/rbn info {q:[2-9]}, or rej/rbn info {q:1} <br>
</div>
</blockquote>
<br>
I agree with this. But it is not a perfect answer to the problem. At
the moment, I don't know what the processing issues might be for
"per user" $minqual settings. <br>
<br>
<blockquote type="cite"
cite="mid:CANbv8NM2y7ozSOskdJ=+o+9-0=7zToNwQHoTckMCx4rDxKrf9A@mail.gmail.com">
<div dir="auto"><br>
</div>
<div dir="auto">If there are better solutions, please let me know!</div>
<div dir="auto"><br>
</div>
<div dir="auto">73 rin JG1VGX</div>
<br>
</blockquote>
<br>
</body>
</html>