In T372124#10055271, @Ladsgroup wrote:

I actually object, second column looks much better to me.

there are several issues mentioned here which could be solved without the need of converting the table back to a list:

1. the "review" link should be closer to the page
   • solution: this will be done via T372124
2. the vertical space is too large (this has also been critisized by several power users at dewiki).
   • solution: reduce padding or line-height per CSS.
3. there's too much whitespace between the columns without any benefit (this has also been critisized by several power users at dewiki).
   • solution: don't use min-width: 100%; or set .cdx-table {max-width: fit-content;} in order to let the table fit the content (as in https://de.wikipedia.org/wiki/Spezial:LintErrors/fostered for example)

sounds good:

1. review-symbol
2. page
3. size
4. since
5. watching

yes, please use iso time format and no local formats.
iso has a lot of advantages, e.g., it's alpha-sortable, it's international, it's easily readable by spam-fighters from other wikis, it begins with the most important part (the year).

It looks like the behavior has already changed, but not for the better. Now
https://web.archive.org/web/20140914080957/https://support.google.com/adsense/answer/176201?hl=de is not blocked anymore?

thanks for the precise and helpful answers!

hi!
thanks for your comment. but i don't see where it answers any of my questions.

formerly i used two cronjobs

*/5 * * * * jsub -once -j y -quiet -v LC_ALL=en_US.UTF-8 -release buster -mem 4g /data/project/camelbot/bot/camelbot.pl --rc-monitoring=db --username=CamelBot
*/30 * * * * jsub -once -j y -quiet -v LC_ALL=en_US.UTF-8 /data/project/camelbot/bot/camelbot_copy_for_cat_dead.pl --cat-dead --username=CamelBot

resolved via

webservice stop
webservice --backend=kubernetes perl5.32 start

i did

webservice stop
webservice --backend=kubernetes perl5.32 start

and it seems to work. so maybe this could be closed now?

ah, great! thanks! it works! 👍

i guess, this gets some kind of urgent, as buster is the new default now.
my script at toolforge is only running if i use the -release=stretch param.

i'm not sure.
as we deleted a lot of superfluous entries in the last years, the sizes of the SBLs are now the same (meta: 290kB) or even smaller (w:en: 140kB) than 2010.
as computers got faster during that time, it might be a not-so-big issue right now. however, i don't know what the situation will look like in the next years.
at least i'd say that this issue is of low priority.

'spam' should not be replaced by 'url', because only linked urls are harmed by the lists. 'website' would not be correct, because the list entries do not necessarily block whole websites, but can also block single webpages. so i think 'link' or even 'external link' should be part of the name.

• 2019-11-06: diff, discussion (faz.net)
• 2019-11-06: diff, discussion (faz.net)
• 2019-11-11: diff, discussion (faz.net)
• 2019-12-05: diff, discussion (faz.net)
• 2019-12-05: diff, discussion (faz.net)
• 2019-12-15: diff, discussion (faz.net)
• 2020-01-18: diff, discussion (archive.*)

that's strange. now it works for me, too.
i tried it several times, about 30 minutes ago. and i always got strange different error messages.
however, now it works. so i guess this issue can be closed.
thanks!

Oops, ok, I understand. Then I totally agree with both of you. Sorry for the interruption and thanks for the explanation. I should have read the php manual.

Of course, it is legal in some programming languages, but then the array would be converted into something reasonable, e.g. into the length of the array (as in perl).
Do you know any common languages, where array arr in
arr > 3
would be converted to a string by default? And if so, will then the '3' also be converted to a string? And the '>' will do a lexicographical comparison than?
Im my opinion this is far to much magic and the abuse filter language should not be contra-intuitive for programmers.

Right now I had a problem with
added_links > 10
Because of the implicit type casting, the syntax is correct, but this code does not do what one could expect, i.e.,
length(added_links) > 10.

I've used CPAN locally at the old toolserver (ran by DaB.). Since there is labs, I just asked for some packages, and the admins installed them. For me this is an easy way.

i'd like to test somehow, which perl-modules are missing.

A similar (or actually the same) problem occurs with translate.google.[^\/]{2,5}/translate.
Right now, google-translate-urls can be used to circumvent the SBL, and we don't know a good way to cope with that problem via SBL or edit filter.
It would be better, if the SBL finds the blocked URLs inside the google-translate url.

Hi!
Sorry, but I can't confirm, because during the last months I used the edit filter very(!) rarely. (So I can't confirm the opposite, too.)

That sounds great! Do we/I have to trigger anyone? Or do I just have to wait now?

I'm afraid, bdb808's answer does not help here, because the first part is just a repetition of what has been said already. And the API will not help, as Umherirrender already said.

In T119463#2939686, @gerritbot wrote:

Change 332037 had a related patch set uploaded (by Harjotsingh): [...]

https://gerrit.wikimedia.org/r/332037

In T15619#2900369, @Fomafix wrote:

I think such a content processing should be done on edit time not on parser time.

as said already (above in this thread), you could use

https://tools.wmflabs.org/searchsbl

I used the Parser.php changes mentioned at https://de.wikipedia.org/wiki/Wikipedia:Typografie/Automatische_Leerzeichen#Regexps and it seems to work. I had to replace the order of a few entries (I've already done that at the wiki page).

If there is a problem with condition limit, you should see whether there is room for improvement in the filters before changing this.

great, thanks! :-)

However, it would be great, to set the number of printed changes per page...

The method I use with CamelBot is quite simple:

The extension was meant to stop abusing behaviour, but it's also used to stop e.g. edits, that would have been destructive by accident. And of course, sometimes there are false positive hits, that cause a harmless edit by a harmless user to be logged forever. There are many users who dislike any public entry of theirselves in an "abuse log".

I'm not the 'seth', who started this topic. :-)

Actually the instructions at mw:Extension:SpamBlacklist#Blacklist syntax <s>are</s>were wrong, because all blacklisted domains will be php-joined like https?://[a-z0-9.-]*(sbl0_|sbl_1|...|sbl_n).
So if one want's to block an exact domain, the code
(?<=//|\.)t\.co\b
can be used, i.e., "a 't\.co\b' which is preceded either by two slashes or a dot".
We do that already at w:de, w:en and at meta for years now. I agree, it's better to fix the instructions rather than changing the code. I've done that now. -> won't fix?

we made a few regexps for the German part of the problem:
see https://de.wikipedia.org/wiki/Wikipedia:Typografie/Automatische_Leerzeichen#Regexps