Daimona Eaytoy

Welcome to Meta!

Hello, Daimona Eaytoy. Welcome to the Wikimedia Meta-Wiki! This website is for coordinating and discussing all Wikimedia projects. You may find it useful to read our policy page. If you are interested in doing translations, visit Meta:Babylon. You can also leave a note on Meta:Babel or Wikimedia Forum if you need help with something (please read the instructions at the top of the page before posting there). Happy editing!

TonyBallioni (talk) 21:07, 4 May 2018 (UTC)

Link to your itwiki talk page doesn’t work

Hi, I just happened to notice that the link to your itwiki talk page in the section ”Contact me” (on your user page here) goes to enwiki. Should work without w: or with w at the beginning of the link, as you know. –Ejs-80 00:34, 22 December 2018 (UTC)

@Ejs-80: Right you are, thanks :-) I just fixed the link. --Daimona Eaytoy (talk) 10:13, 22 December 2018 (UTC)

The Affiliate-selected Board seats process welcomes your support

Hello. You are receiving this message because you are active in the field of translations <3 The movement needs you! The Nominations phase has started for the ongoing selection process of two Board members, and the timeline is quite tight.

A Translation Central is available to help translators figure out what's been covered and what's left to do. Over the course of the next few weeks, your attention on candidates' profiles is particularly welcome.

While there are four languages that are especially relevant for multiple affiliates (namely Arabic, French, Russian and Spanish), we are asking your help for Chinese, Ukrainian, Bengali, Czech, Hungarian, Romanian, Italian, Korean, Portuguese, Polish, Farsi, German, Cantonese, Finnish, Hindi, Thai, Dutch, and Greek, as these also matter to affiliates! If you can't help: please see if you know anyone in your circle who could, and spread the word :) Thank you! Elitre (WMF) and Facilitators of ASBS 2019, 21:35, 24 April 2019 (UTC)

Massblock script

Ciao. I've found a couple of issues with the massblock script. Do you keep a dedicated page where we can report those? Thanks! —MarcoAurelio (talk) 19:31, 19 July 2019 (UTC)

@MarcoAurelio: Hey! I don't have a dedicated page, so feel free to report anything you find here, or in the gadget talk on itwp, or wherever you prefer :-) Just please ping me so that I'll be able to see it. --Daimona Eaytoy (talk) 08:58, 20 July 2019 (UTC)

Thank you. I've found that the script always end blocking talk page access even if "Remove talk page access" is unchecked (cfr. b:es:Especial:Contribuciones/FloyHrw9569058). As a suggest I'd say that the protect options should be disabled by default as it is not very usual for most projects to use them -or- allow a local override. That's all for now :-) Thanks, —MarcoAurelio (talk) 17:19, 20 July 2019 (UTC)

Just tested it again. If I mark the checkbox, then TP access is not revoked, so we might want to reword that part of the script. Thanks, —MarcoAurelio (talk) 17:30, 20 July 2019 (UTC)

@MarcoAurelio: I developed the script with itwiki in mind, which curiously is the only wiki where blocks will always remove talk page access, so it's not surprising that the option isn't working. I'm going to fix it anyway. As for the protect options, it's almost the same :-) On itwp, the standard practice is to protect pages of indefinitely blocked users. But yes, it doesn't make sense as default, so I'm going to make it unchecked. Thanks for your suggestions, --Daimona Eaytoy (talk) 15:03, 21 July 2019 (UTC)

Range

Questa volta ho bloccato per 7gg, tanto è lo stesso. —Wim b 10:24, 11 August 2019 (UTC)

@Wim b: Ottimo, grazie. Se passi in chat ora sono pronto per quel che ti avevo detto. --Daimona Eaytoy (talk) 11:32, 11 August 2019 (UTC)

non credo, forse stasera per una cosa velocissima. Casomai ci vedremo. —Wim b 13:53, 11 August 2019 (UTC)

AbuseFilter & exclude spam blacklist

Hi. Ages ago there was discussion in phabricator about being able to exclude the spam blacklist from an abuse filter, so we could lessen the hits on our filters where we had dealt with that type of spam. Has that, or will that, be progressing so we can have that advantage? Thanks.  — billinghurst sDrewth 23:59, 9 December 2019 (UTC)

@Billinghurst: Hey! No, there's been no progress about that (which would anyway be tracked at phab:T211680). Implementing a spam_blacklist variable turned out being more complicated than it seemed at first. OTOH, I don't think it would be possible to swap the order of AbuseFilter and SpamBlacklist. --Daimona Eaytoy (talk) 11:03, 11 December 2019 (UTC)

Road blocks, road blocks, road blocks for spam and spambot management. Cannot stop them getting in the front door; cannot easily see where they are managed and the pieces that we have in place cannot communicate intra or trans. Just ppl putting in the hard yards. Thanks anyway.  — billinghurst sDrewth 13:38, 11 December 2019 (UTC)

UTF characters into equivset

I just saw the phabricator ticket for the update of the equivset. One of our favourite PITA is stepping through charsets to create, ping and pester, and I have been adding mini regex to title blacklist (search for Fuerdai). Would you be so kind to see if all those characters sets are covered by this update so I can resolve this by better means, or whether we have more steps to undertake. Thanks for your help.  — billinghurst sDrewth 05:46, 22 December 2019 (UTC)

@Billinghurst: Hi, I've verified all characters used in the "fuerdai" lines, and I can confirm that they were all included in that update. The only exception are the characters in "ｕｅｒ|ｄａｉ", but they were already part of the normalization set. In general, if you find some new "weird" characters, you can use this list and ctrl+f to see if they're already included. If not, please feel free to open a task on phabricator and I'll add the missing characters. As an aside, I don't think this is fuerdai-exclusive. Lately, more and more people have been coming up with these weird characters sets. I suspect there's some online tool or app that gives you these characters back. But anyway, antispoof (and, consequently, TitleBlacklist and AbuseFilter) can handle them now. --Daimona Eaytoy (talk) 14:20, 22 December 2019 (UTC)

There are such tools for mobile social media user names. I am guessing these are being utilised.

At that gerrit page the log says that the page is over a year old. Do I presume that this will update with the next wmf version update? If that is the case, I will try to remember to update the subsidiary page mw:Extension:AntiSpoof/Equivalence sets. As a question that page references the github page, would it be better referencing the gerrit page?  — billinghurst sDrewth 22:38, 22 December 2019 (UTC)

Yes, such tools are likely the cause here. As for that page, well, it is indeed one year old. The characters were added last year, but the new version was deployed on WMF wikis (and added to AntiSpoof) only a few weeks ago. That page is the master version, which means it's always up-to-date. As for the page on MW.org, yes, it should indeed be referencing gerrit, not github. Thanks! --Daimona Eaytoy (talk) 12:24, 23 December 2019 (UTC)

Thanked in AF?

Hi. HNY. Question. Is "thanked" available as an action in AF? It isn't mentioned in the MW: extension pages, and obviously it isn't showing in certain logs. One of our LTAs is using that as a means to lightly pursue xwiki. Thanks for the info.  — billinghurst sDrewth 21:08, 6 January 2020 (UTC)

@Billinghurst: Hey, HNY. No, right now it's not available, but a proposal exists at phab:T235873. This feature was requested various times during the years, but no progress has been made. This is mostly because "thanks" is very different from "edit", "move", etc. For instance, there's no clear way to show the warning/disallow/block message to the user. Also, Thanks makes several assumptions when sending thanks (e.g. that it will always succeed, while an AF rule could prevent that), so we'll also have to make some changes to the Thanks extension. Long story short, Danny is probably working on it, but it won't be easy at all. --Daimona Eaytoy (talk) 11:05, 7 January 2020 (UTC)

Talk:Requests for comment/Creating abusefilter-manager global group

Pinged, but not leaving it up to chance as it is easy to miss notifications. ~riley (talk) 02:26, 17 January 2020 (UTC)

Resolving status of the two new variables

I am seeing "wiki_name" and "wiki_language" in examining normal edits /examine/nnnnnn, though I don't see this in abusefilter log /examine/log/nnnnnn

At c:Special:AbuseFilter/examine/1331776142 it shows "wiki_name" and "wiki_language"

Database name of the wiki (wiki_name)	commonswiki
Language code of the wiki (wiki_language)	en

which I came across through a normal edit tested rather than through abusefilter log.

Is it that the phabricator ticket that I saw only partial for this ultimate task, or am I missing something that I need to be doing. Thanks.  — billinghurst sDrewth 04:56, 16 February 2020 (UTC)

@Billinghurst: This is kind of expected. When you examine a normal edit, all variables are computed on the fly, including wiki_* variables. However, when you examine an AbuseLog entry, it will just pull the variables that were computed at the time the edit was logged. wiki_* variables are not computed by default, so they'll only be available in /examine/log/XXX if any active filter computed them while checking the edit. HTH, --Daimona Eaytoy (talk) 14:56, 16 February 2020 (UTC)

A note

Hello Abuse Filter helper, we had recently have a new group Abuse filter maintainer which allows the same level of access with additional rights to edit the filters yourself among other things. If you are interested after reading the documentation, do apply at SRGP. Thanks.Camouflaged Mirage (talk) 08:52, 4 April 2020 (UTC)

• Great work on seeing this through to creation, Daimona! ~riley (talk) 09:14, 4 April 2020 (UTC)

@Camouflaged Mirage and ~riley: Great, thanks! However, I think we shouldn't encourage applications that much. The use cases are very limited, and the right is temporary, so I don't think anyone would really need it right now... --Daimona Eaytoy (talk) 09:27, 4 April 2020 (UTC)

Yes, true. This is just a FYI send to all abuse filters helpers just in case they need the additional access (which we have the first application now). Yeah, my wording can be better though to make it more FYI-ish rather than encouraging. Camouflaged Mirage (talk) 09:30, 4 April 2020 (UTC)

Pre-conflict: Note, I probably didn't explain well. I didn't mean to discourage applicants, but just make it very clear that the right is probably less useful than one may expect at first.

Post-conflict: @Camouflaged Mirage: Don't worry, I think your message is good :) I was thinking that perhaps we should clearly point out this fact at the top of Abuse filter maintainer, to avoid any possible misunderstanding. --Daimona Eaytoy (talk) 09:34, 4 April 2020 (UTC)

Yeah, happy to add something to the effect, do you have any suggested wording? Camouflaged Mirage (talk) 09:37, 4 April 2020 (UTC)

@Camouflaged Mirage: Uhm, perhaps something along the lines of "This group is **only** allowed non-controversial filter edits dictated by upcoming software changes. Please read carefully below.", inside a template like Template:Note on mw.org. Other use cases (like edits on community's request) can be mentioned later on, the note should just say "this might not be the group you're looking for". --Daimona Eaytoy (talk) 12:23, 5 April 2020 (UTC)

Thanks. @~riley: any objections, if no, I will add it. Thanks.Camouflaged Mirage (talk) 12:34, 5 April 2020 (UTC)

Sorry, but I cannot support adding "This group is **only** allowed non-controversial filter edits dictated by upcoming software changes. Please read carefully below." to the page. Besides the fact that it is now policy and changes of that nature need to be discussed on the talk page, that line is only one example of when using the right is appropriate (hence the page saying "such as") and significantly changes the scope of the right to "only allow" changes of that nature. ~riley (talk) 20:28, 5 April 2020 (UTC)

I think there isn't much applications (even after I send it to all AFHs) at this moment and yes, I sort of agree we should't be that restrictive in the usage of this right (per ~riley it is one of the acceptable). After thinking, I think it will be best to keep such policies clear, definitive but at the same time allow some room to allow us to grant the access to some unique situation. Hence, the status quo will be better. Thanks all for the inputs. Camouflaged Mirage (talk) 09:21, 6 April 2020 (UTC)

Question re AF v Spam blacklist

Hi. A quick question. With all the AF changes occuring, are we going to be able to have the spam blacklists acting prior to the abuse filters, so that we are not getting blacklist'd sites appearing in the filter log? If not, are we then going to be able to have that ability to have abuse filters ignore blacklisted domains? Thanks if I am re-asking old questions, or re-addressing old issues. Thanks.  — billinghurst sDrewth 01:25, 30 January 2021 (UTC)

@Billinghurst: Hey. That specific issue is not on the list of bugs that were planned to be addressed as part of the overhaul. OTOH, we still haven't focused on the merely-bugfixing part, so things might change. However, I'm not sure that this is an issue that can be entirely resolved within AbuseFilter -- the order in which extension handlers are triggered is alphabetical, I believe, and I don't know how easy it would be to change that. --Daimona Eaytoy (talk) 12:36, 30 January 2021 (UTC)

k, thanks. Alphabetical is my understanding. What hope do I have in renaming mw:Extension:Spamblacklist to Extension:AaaaaaaaaaaSpamBlacklist? :-) No harm in hoping.  — billinghurst sDrewth 12:53, 30 January 2021 (UTC)

@Billinghurst:Or perhaps AbuseFilter to ZabuseFilter. Sounds pretty good to me! Now that I think about it again, T211680 is the task. I've just left another comment there, it might be possible to resolve this with a hack inside the WMF-specific config. --Daimona Eaytoy (talk) 14:16, 30 January 2021 (UTC)

Cool. Thanks.  — billinghurst sDrewth 14:25, 30 January 2021 (UTC)

In /examine/ means to load global filter at a local wiki?

Is there a means to be at a local wikis and import a global filter using the LOAD function? I have tried various forms of syntax for a fail. I know that I can do that analysis at meta, just sometimes I am at the local wiki and ... Thanks. Also part of the reason for asking is that I am pushing a little hard for local wiki to use the helper functionality, and if they can load the globals easily to review, then all the better.  — billinghurst sDrewth 23:22, 8 April 2021 (UTC)

@Billinghurst: Hey, this is currently not possible, but only because it was never requested. I think implementing this feature would be trivial. I've just filed T279772, and will take a closer look at it shortly. --Daimona Eaytoy (talk) 11:03, 9 April 2021 (UTC)

I just saw it come through. :-) I am guessing that lack of request more relates to not many people having either of the helper or writer right. Thanks.  — billinghurst sDrewth 11:05, 9 April 2021 (UTC)

@Billinghurst: I've just posted the results of my closer look there. I was spectacularly wrong. This is essentially impossible to implement because several things in MediaWiki core can currently only work with the local database. --Daimona Eaytoy (talk) 11:54, 9 April 2021 (UTC)

C'est la vie. Thanks for looking.  — billinghurst sDrewth 11:55, 9 April 2021 (UTC)

Are global rights visible to AF?

Hi When I examine a blocked post, the staff user group doesn't show in a report. Is because it is not visible, or that it wasn't used in the filter? I looking at an easy way to manage (WMF) staff not getting caught and it not being based on a stem in the user name. Thanks.  — billinghurst sDrewth 03:33, 28 April 2021 (UTC)

Not to worry, MA pointed me to global_user_groups Missed it right there at the top of the list. :-/  — billinghurst sDrewth 04:07, 28 April 2021 (UTC)

@Billinghurst: Indeed :-) I should also note that the variable is lazy-loaded, so you might not see it when examining AbuseLog entries if no filter is already using that. --Daimona Eaytoy (talk) 15:06, 28 April 2021 (UTC)

Definitely lazy loaded, though there is a filter using it and it wasn't showing. <shrug> Blindness by me and the machines. Anyway, resolved. Thanks.

Will the laziness be an issue in AF v.2?  — billinghurst sDrewth 15:14, 28 April 2021 (UTC)

@Billinghurst: Well, strictly speaking, a filter using it is not enough. That filter also has to compute the variable. For instance, if it was something like false & ("staff" in global_user_groups) the second condition would never be reached and global_user_groups not computed. I guess this might've happened for the filter you was referring to. This is by design though, to avoid consuming server resources when unneded (and computing the global groups can be expensive). --Daimona Eaytoy (talk) 15:26, 28 April 2021 (UTC)

AbuseFilter Throttle

Hi Daimona. Can you explain to me what the AbuseFilter throttling does? I don't have it clear. I know that it can't block, blockautopromote or degroup, but what happens when these actions are not activated? Kind regards.--SRuizR 00:22, 4 May 2021 (UTC)

@SRuizR: Hey! Throttling is indeed a bit complicated, and not easy to understand at first. Here is a short guide about that. Essentially, throttling only makes sense when other actions are also enabled, as those actions will be delayed until the throttle limit is reached. If no other action is enabled and the throttle limit is reached, the filter will be triggered, and no action would be taken. HTH, --Daimona Eaytoy (talk) 18:03, 4 May 2021 (UTC)

Oh sorry, I didn't mean that throttling. I was asking about the automatic emergency throttling. Kind Regards.--SRuizR 00:32, 5 May 2021 (UTC)

@SRuizR: Whoops, sorry. This is an ambiguity that I'd hope to resolve some day. That throttling is easier to understand. As you might already know, it is triggered once certain conditions are verified (i.e. the filter matches "too many" recent edits, where "too many" can be adjusted via configuration variables). When throttling is triggered, the most dangerous actions are disabled for the filter. These are the ones you mentioned, although they can also be customized via wiki config. If those actions aren't enabled, throttling does nothing. Every other action is taken as expected, so it's effectively a no-op. Also, the UI might be a bit confusing right now, because it says that a filter is throttled even if no actions are being disabled (see T200036). --Daimona Eaytoy (talk) 09:43, 5 May 2021 (UTC)

Thank you very much!--SRuizR 15:50, 5 May 2021 (UTC)

La chat

ancora non funziona :)! Non che mi voglia far sbloccare, anzi, solo che volevo passare la mia chat se serve aiuto per cose tipo eurovision 2022.. --2.226.12.134 16:43, 30 May 2021 (UTC)

Uhm... Cosa di preciso non funziona? --Daimona Eaytoy (talk) 15:21, 1 June 2021 (UTC)

ho provato ad usare la funzione connettiti qui ma non connette nulla.. immagino che ci sia da scaricare qualcosa, a questo punto, solo che così non è per niente intuitivo e non si può più usare se uno deve usare un altro pc, perché non si può andare ovunque ed ogni volta scaricare software su pc di altre persone.. --2.226.12.134 17:25, 1 June 2021 (UTC)

Quei link usano il protocollo IRC, e per aprirli occorre avere un client IRC installato. Se ne usavi già uno per freenode va ancora bene, qualsiasi client IRC va bene per tutti i server, freenode e libera inclusi. Se invece prima utilizzavi l'interfaccia web, hai ancora la possibilità di utilizzarla, però da un sito diverso, vedi qui. In quel caso basta inserire il nome del canale manualmente. --Daimona Eaytoy (talk) 10:01, 2 June 2021 (UTC)

You've got mail

Thanks, --DannyS712 (talk) 03:01, 18 June 2021 (UTC)

abusefilter and reupload

Hi. Looking for a test for reuploads. Only thing that I can find reliably is page_age and page_id, and would prefer to avoid those if possible. I cannot see that we have ready ability to check for an reupload directly. And I don't see that I can check against the upload logs for defined text that appears there for new versions of files. Can you please guide me in case I am missing the obvious. Thanks.  — billinghurst sDrewth 13:37, 2 October 2021 (UTC)

@Billinghurst: Hey! I don't think it's possible to detect a reupload. page_id/page_age are probably the best options currently available. Something like searching the upload logs (or similar capabilities for other actions) are not implemented, and I'm not sure if they should be, given the potential for slowdowns. --Daimona Eaytoy (talk) 13:48, 2 October 2021 (UTC)

Okay, thanks for that reassurance.  — billinghurst sDrewth 13:50, 2 October 2021 (UTC)

Abusefilter edit window

Hello Daimona,

I hope you are fine. (Sorry for my rusty english.) Daily user of abusefilters on fr-wp, I have a couple ideas (+ a bug) to enhance a lot the Abusefilter edit window, which is really a chore right now. I didn't find those ideas/bug on Phab, but beforme submitting them there, I prefer to check that with you, as you must be the wikimedian who better knows Abusefilter.

1. [idea] Editing a filter is a chore because for long lines of regex, we have to scroll a lot. Idea: implementing automatic line wrap, as there is on coding softwares.
2. [idea] For the same reason, idea: the edit window should be larger (it is ridiculously small on my 21.5 inchees screen) and resizable.
3. [bug] There are two edit software in Abusefilter. With the first one, sometimes (apparently because of some special letters) the mouse cursor is not shown where it is really. This is super-annoying, obviously.

Best, — Jules* ^Talk 09:54, 31 October 2021 (UTC)

@Jules*: Hey :) Replying to each bullet:

1. I think implementing line wrap might be doable. As a workaround, what I usually do is to break down regexps using string concatenation ("+"), which, I recognize, has some drawbacks.
2. This is a good point, in particular making it resizable. However, I'm not sure if Ace editor (the one with syntax highlighting) is resizable, I'd have to check the docs.
3. Yep, this is a known bug. And actually, this is also a bug in Ace editor, see for instance here and here. OTOH, I just tried to reproduce the bug but I haven't been able. I'm sure it used to happen more frequently in the past, and for more special characters. Unfortunately, there's not much we can do about that :-/

I copied your proposals to T294856. Thanks, --Daimona Eaytoy (talk) 18:58, 2 November 2021 (UTC)

Abuse filter maintainer

Hello Daimona! I'd like to let you know I assigned the abuse filter maintainer permissions to you. You should now be able to edit filters across all wikis. As set by the policy, the assignment is temporary, and the rights will expire on 2023-04-17 (a year from now). Thank you for volunteering and have a nice day, Martin Urbanec (talk) 13:40, 17 April 2022 (UTC)

@Martin Urbanec: Thank you :) --Daimona Eaytoy (talk) 13:50, 17 April 2022 (UTC)

Congratulations, dear administrator!

Congratulations, Daimona Eaytoy! You now have the rights of an administrator on Meta-Wiki. Please take a moment to read the Meta:Adminstrators page and watchlist related pages (in particular Meta:Requests for help from a sysop or bureaucrat, and Meta:Requests for deletion, but also Talk:Spam blacklist and Talk:Interwiki map), before launching yourself into page deletions, page protections, account blockings, or modifications of protected pages. The majority of the actions of administrators can be reversed by the other admins, except for history merges which must thus be treated with particular care. Please feel free to join us on IRC: #wikimedia-adminconnect. You may find Meta:Admin handbook to be useful. Please also check or add your entry to the Template:List of administrators. You're also allowed to subscribe to the metawiki-admins private mailing list (subscription instructions on that page). Again, congratulations and welcome to the team.—MarcoAurelio (talk) 13:05, 16 July 2023 (UTC)

Noting here that the adminship is a regular one, since this is what you applied for and the community supported it. As such, please note that Meta:Administrators/Removal requires regular administrators to make at least 10 edits each 6 months or adminship is revoked automatically no matter how many admin actions you have done. Best regards, —MarcoAurelio (talk) 13:05, 16 July 2023 (UTC)

Congrats Daimona, great to have you on board. @MarcoAurelio: I do hope that the checking tools have been updated so that edits to abuse filters are now able to be counted, as that has not been the case previously, and this is where this new administrator has indicated is their proposed area of activity.  — billinghurst sDrewth 15:19, 16 July 2023 (UTC)

@MarcoAurelio and Billinghurst: Thanks :-) I'll do my best to help as I can! --Daimona Eaytoy (Talk) 12:29, 23 July 2023 (UTC)

Notice of removal of adminship (April 2024)

Hello Daimona Eaytoy,

I regret to inform you that pursuant to Meta:Administrators/Removal (inactivity), and because you have not made at least 10 edits in the last six months, your administrator and associated permissions have been removed from your account. Please see Meta:Administrators/Removal (inactivity)/April 2024 for details.

Kind regards, --MF-W 14:54, 3 April 2024 (UTC)

You might want to consider applying for limited adminship (e.g. like this one [1][2]). That way you wouldn't lose your rights automatically if you've made less than 10 metawiki edits, it only requires a signature every 6 months stating you want to keep your permissions. Johannnes89 (talk) 15:16, 3 April 2024 (UTC)

Yup, I knew this was coming, thanks for the notice. @Johannnes89: It's a fun period and I don't think I will apply for limited adminship now, as I don't have plans of using it. I will keep that in mind for the future though, so thank you! --Daimona Eaytoy (Talk) 16:23, 3 April 2024 (UTC)

Edit filter 161

Could you exclude the addition of CSD templates? JayCubby (talk) 03:23, 19 December 2024 (UTC)