User talk:Beetstra/Archives 2018

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search


Hi. mw: is being for some time getting targeted by spambots. If not already, could it be possible to monitor its local (black|whitelists) and IRC feed? Thanks! —MarcoAurelio (talk) 10:45, 6 February 2018 (UTC)[reply]

@MarcoAurelio: not sure if it is, I will check when I have access to putty. --Dirk Beetstra T C (en: U, T) 12:11, 6 February 2018 (UTC)[reply]
Thanks :-) —MarcoAurelio (talk) 12:11, 6 February 2018 (UTC)[reply]
COIBot is sitting in the channel in IRC, though I note that if I run a "findrules" for a url known to be in mw's blacklist, it does not return that result.  — billinghurst sDrewth 11:39, 15 February 2018 (UTC)[reply]

COIBot significant backlog ...

The backlog queue is into the many 0000s, do you think that we may need some more analysers working the queues?  — billinghurst sDrewth 11:35, 15 February 2018 (UTC)[reply]

Hmm, there were only 2 running (should be 6). I've added 4, will take some time to catch up .. --Dirk Beetstra T C (en: U, T) 13:22, 15 February 2018 (UTC)[reply]

Linkwatchers MIA  — billinghurst sDrewth 12:46, 17 March 2018 (UTC)[reply]

Thanks.  — billinghurst sDrewth 00:17, 18 March 2018 (UTC)[reply]
@SDrewth: kicked them on the server. No clue what happened. --Dirk Beetstra T C (en: U, T) 06:48, 18 March 2018 (UTC)[reply]

User encoding problems on lisankom report

Hello Dirk

When creating User:COIBot/LinkReports/ COIBot had some problems encoding a couple of user names (encoded twice as utf-8?). These are shown in the wiki page as “سعيد عيسى الٔ and “عزوزي”, although they seem to have been by MediaWiki, from the recent changes, it seems to have been using “سعÙ<U+008A>د_عÙ<U+008A>سÙ<U+0089>_اÙ<U+0084>Ù<U+0085>عزÙ<U+0088>زÙ<U+008A>“ (hexadecimal: c3 98 c2 b3 c3 98 c2 b9 c3 99 c2 8a c3 98 c2 af 5f c3 98 c2 b9 c3 99 c2 8a c3 98 c2 b3 c3 99 c2 89 5f c3 98 c2 a7 c3 99 c2 84 c3 99).

U+0084, U+0085, U+0088, U+0089, U+008A are control characters (formerly known as INDEX, NEXT LINE, CHARACTER TABULATION SET, CHARACTER TABULATION WITH JUSTIFICATION, LINE TABULATION SET) and, -not only are forbidden in MediaWiki usernames- but are also problematic to insert in a text.

In case it helps, attempting to decode the string from COIBot fails (illegal input sequence), but encoding in utf-8 the already-in-utf-8 bytes of the reported user (سعيد عيسى المعزوزي) leads to the following output similar to what COIBot provided:

  • COIBot: c3 98 c2 b3 c3 98 c2 b9 c3 99 c2 8a c3 98 c2 af 5f c3 98 c2 b9 c3 99 c2 8a c3 98 c2 b3 c3 99 c2 89 5f c3 98 c2 a7 c3 99 c2 84 c3 99
  • Output: c3 98 c2 b3 c3 98 c2 b9 c3 99 c5 a0 c3 98 c2 af 5f c3 98 c2 b9 c3 99 c5 a0 c3 98 c2 b3 c3 99 e2 80 b0 5f c3 98 c2 a7 c3 99 e2 80 9e c3 99 e2 80 a6 c3 98 c2 b9 c3 98 c2 b2 c3 99 cb 86 c3 98 c2 b2 c3 99 c5


Platonides (talk) 21:20, 9 April 2018 (UTC)[reply]

@Platonides: Yes, I know it seems to have problems there. I though I forgot to en/decode somewhere .. but maybe it is a double encoding. It does seem to have the same problem with the domains (report names) sometimes. I'll try and dig through the code once more, see what happens. Problem is that the console (putty) does not seem to understand the encoding either, and throws garbage at me, and perl has a nasty tendency to convert stuff when it shouldn't - which makes it difficult to check where it goes wrong. But it might very well be that I encode the name-string, and then finally encode the whole text again. Thanks for the analysis! --Dirk Beetstra T C (en: U, T) 07:54, 10 April 2018 (UTC)[reply]

LinkWatchers missing

Hi. COIBot is hanging around, though its mates the LiWas are missing. When you are next around and available, it would be great if you could kick whatever needs kicking. Thx.  — billinghurst sDrewth 11:49, 18 May 2018 (UTC)[reply]

All functioning. If you did something, thx.  — billinghurst sDrewth 00:06, 19 May 2018 (UTC)[reply]
I did, all bots were misbehaving at the moment. XLinkBot was basically dead, COIBot half blind, LiWa3 mute and UnBlockBot crashed. —Dirk Beetstra T C (en: U, T) 08:28, 19 May 2018 (UTC)[reply]

Link analyser issue?

COIBot is whining that linkanalyser is haning and restarting. It is also building up a backlog of reports, with none from the backlog processing.

Report of status

  • 2018/06/09 08:49 UTC

<COIBot> Syslogs: case: 226243 secs. coibot: 178 secs. commander: 0 secs. diffreader: 1179 secs. linksaver: 1 secs. output: 1 secs. parser: 2496 secs. script: -1 secs. special: 1937131 secs.

<LiWa3_1> Syslogs: diffreader: 83018 secs. linkanalyser: 15 secs. linkparser: 1262 secs. linkreporter: 232630 secs. linkwatcher: 25 secs. output: -1 secs. script: -1 secs.

<LiWa3_3> LW: 2 days, 16:37:15 hours active; RC: last 4 sec. ago; Reading ~ 825 wikis; Queues: P1=0; P2=7; P3=35 (537 / 613); A1=50; A2=0 (24 / 1509); M=0 - In LinkWatcher edit-backlog: 0 files (0 lines) and in analyser backlog: 854 files (213605 lines).

  • 2018/06/10 05:37 UTC

<COIBot> Syslogs: case: 301111 secs. coibot: 6 secs. commander: 1 secs. diffreader: 3438 secs. linksaver: 1 secs. output: 50 secs. parser: 5619 secs. script: -1 secs. special: 2011999 secs.

<LiWa3_2> Syslogs: diffreader: 41520 secs. linkanalyser: 216 secs. linkparser: 23149 secs. linkreporter: 307497 secs. linkwatcher: 1676 secs. output: -1 secs. script: -1 secs.

<LiWa3_3> LW: 3 days, 13:25:02 hours active; RC: last 4 sec. ago; Reading ~ 825 wikis; Queues: P1=0; P2=0; P3=0 (763 / 613); A1=235; A2=1301 (1084 / 1046); M=0 - In LinkWatcher edit-backlog: 0 files (0 lines) and in analyser backlog: 1238 files (309653 lines).

 — billinghurst sDrewth 05:46, 10 June 2018 (UTC)[reply]

I’ll try and have a look. —Dirk Beetstra T C (en: U, T) 08:49, 10 June 2018 (UTC)[reply]

User:COIBot/Local/êµ¬ë¯¸ì†¡ì •ì„œí¬ìŠ¤íƒ€ížìŠ¤.net

Can you have a look at this? Bot seems to be unhappy with punycodes... — regards, Revi 08:34, 12 July 2018 (UTC)[reply]

It is. I have to check this. There are more problems like this. —Dirk Beetstra T C (en: U, T) 13:32, 12 July 2018 (UTC)[reply]

Next steps for the wish “confirmation prompt for the rollback link”

Logo Feedback round in the Technical Wishes project.png

Hello, a while ago you participated in a feedback round about a proposal how accidental clicks on the rollback link could be avoided. Thanks again for sharing your thoughts and ideas!
Looking at the feedback and the rollback situation in different wikis, the development team decided how to approach this wish: As a default, most wikis won’t have a confirmation. But users who wish to have one, can enable it in their preferences, which will add a confirmation prompt to the rollback link on the diff page and on the list pages. The prompt won’t be a pop-up, but an inline prompt like for the thanks confirmation. You can read more about the planned solution and what influenced this decision on the project page. -- Best, Johanna Strodt (WMDE) (talk) 09:45, 16 July 2018 (UTC)[reply]

Encoding issues

Hello & hope that you're okay. I think the bot has some encoding issues at User:COIBot/Local/ I'm afraid I cannot be more specific :-( Regards, —MarcoAurelio (talk) 16:07, 16 July 2018 (UTC)[reply]

Yep, also see two threads up. I'll have another look at this, but debugging this on a terminal is near impossible. XLinkBot has the same problem, and I hope that my db does not have the same problem too... --Dirk Beetstra T C (en: U, T) 16:35, 16 July 2018 (UTC)[reply]
Thank you. Maybe some InnoDB or encoding? On our tools we did to fix some encoding issues. Maybe that helps? Best regards, —MarcoAurelio (talk) 09:51, 17 July 2018 (UTC)[reply]

webdetail link issues

I just clicked on the webdetail link for a link report, and it looks like that domain is being used by spammers. Link in the report is this. Something's not right - would you mind double-checking? Thanks! Ravensfire (talk) 02:38, 15 August 2018 (UTC)[reply]

@Ravensfire: I replaced it with the template from en.wikipedia, but notice now that reverseinternet also does not work anymore (but that is just a 404). We'll have to find some other places to get information on adsenses, webbugs and similar (@MER-C:. --Dirk Beetstra T C (en: U, T) 03:26, 15 August 2018 (UTC)[reply]
Thank ya, sir! Ravensfire (talk) 03:29, 15 August 2018 (UTC)[reply]
Found three sites, though only one overtly shows it as part of a url post
 — billinghurst sDrewth 04:21, 15 August 2018 (UTC)[reply]

COIBot: revertlist command jiggered

Hi. When trying "revertlist" the bot does not respond to start that it has been added to the list. Thanks.  — billinghurst sDrewth 12:46, 5 September 2018 (UTC)[reply]

@Billinghurst: Did you try to 'restart commander'? --Dirk Beetstra T C (en: U, T) 12:58, 5 September 2018 (UTC)[reply]

I hadn't, though no change when doing so.

<sDrewth> restart commander
<COIBot> Attempting to restart Commander.
<COIBot> Commander seems to have died - attempted to start one - see 'show processes'.
<sDrewth> revertlist
<sDrewth> revertlist
<sDrewth> show processes
<COIBot> Running processes: .
<sDrewth> revertlist

 — billinghurst sDrewth 13:01, 5 September 2018 (UTC)

Stupid iadmin stuff .. can you try again (and then also restart the linksaver). It should be back up now. --Dirk Beetstra T C (en: U, T) 14:04, 5 September 2018 (UTC)[reply]

The Community Wishlist Survey


You get this message because you’ve previously participated in the Community Wishlist Survey. I just wanted to let you know that this year’s survey is now open for proposals. You can suggest technical changes until 11 November: Community Wishlist Survey 2019.

You can vote from November 16 to November 30. To keep the number of messages at a reasonable level, I won’t send out a separate reminder to you about that. /Johan (WMF) 11:24, 30 October 2018 (UTC)[reply]


Are you available to provide admin help for me? I am new to this project, and in need, if you can. Thanks.John Cline (talk) 06:00, 31 October 2018 (UTC)[reply]

@John Cline: My admin work here is almost exclusively with the spam-blacklist. Other tasks I can see, but I am not proficient (or necessarily competent) there on this project. --Dirk Beetstra T C (en: U, T) 13:54, 1 November 2018 (UTC)[reply]
Thank you for that reply. I should have followed-up on my request by telling you that my situation had been resolved, which it has. Nevertheless, I do appreciate your reply. Best regards--John Cline (talk) 14:02, 1 November 2018 (UTC)[reply]