Hello, My name is Anthony Borba. I work in QA at the foundation. I was looking at this ticket and I currently do not have access to an account with an apostrophe in the username. I was wondering if you have an account that you used to discover this issue? If so, could I ask you for some help testing the potential fix? Thanks
User talk:Daimona Eaytoy/Flow
Hey there, this issue was reported on itwiki by actual users with an apostrophe in their username. I don't have such an account, but I think you could just create an account with an apostrophe in the name, the rest of the username shouldn't matter.
Hello Daimona, thanks for responding to my message. Right now, it is not possible for me to create an account with the needed characters. The reason is related to some of our newer policies around testing accounts. We believe this issue to be fixed, and the current Wikipedia app build on the app store should contain that fix. Could I ask you a big favor? Can you contact the user who reported this issue, and ask them to try it again on the latest version of the Wikipedia app? Thank you
Hey there, I did so, and apparently the issue was not resolved in the latest version.
Thank you for following up on this. I will pass this info on to the team.
Hello, there, I am translating meta:Event_Center, and came up with /Registration subpage where your CampaignEvents extension is introduced to start with. The Event Center itself is for organizers/participants aiming at new events, and you extention is a basis for their start up.
That said, don't you agree that it is serving to wider audienced when we internationalize the Extension:CampaignEvents page?
FYI, when I attended zoom meeting for Hubs, I sensed demand to maintain events much easier is raising in regions where we are welcoming newcomers. Your extension is very helpful for those event organizers, who are not always Senior editors themselves (1,000+ edit counts), but passionate to be on the drivers' seats.
Thank you again to draw up a very helpful extension. I am so happy to learn there are people who cares big (: Cheers,
Hi!
You get this message because you are an admin on a Wikimedia wiki.
When someone edits a Wikimedia wiki without being logged in today, we show their IP address. As you may already know, we will not be able to do this in the future. This is a decision by the Wikimedia Foundation Legal department, because norms and regulations for privacy online have changed.
Instead of the IP we will show a masked identity. You as an admin will still be able to access the IP. There will also be a new user right for those who need to see the full IPs of unregistered users to fight vandalism, harassment and spam without being admins. Patrollers will also see part of the IP even without this user right. We are also working on better tools to help.
If you have not seen it before, you can read more on Meta. If you want to make sure you don’t miss technical changes on the Wikimedia wikis, you can subscribe to the weekly technical newsletter.
We have two suggested ways this identity could work. We would appreciate your feedback on which way you think would work best for you and your wiki, now and in the future. You can let us know on the talk page. You can write in your language. The suggestions were posted in October and we will decide after 17 January.
Thank you. /Johan (WMF)
18:17, 4 January 2022 (UTC)
 |
The Technical Barnstar |
| Thank you very much Daimona to took Using AbuseFilter extension to combat vandalism on a wiki workshop for Indic communities. We will grateful to you for such a wonderful workshop :) |
Thank you Jay, and everyone other who has dedicated some of their time to listen to my chatty self :-)
Hello Daimona, Greetings! I am reaching out to ask for your help with a technical workshop on the AbuseFilter extension.
A few months ago, through a workshop series as part of the Small wiki toolkits initiative, we learned that one of the Indic community's challenges is a lack of knowledge of tools to fight vandalism on wikis. Indic community involves 25+ smaller language wikis. We are considering organizing a workshop in December for the community. The focus would be on counter-vandalism tools, specifically on AbuseFilter extension and how to use it.
As you currently seem to be one of the active maintainers on this extension and may also know best how to use it, I wonder if you would be interested in running a hands-on workshop around this topic? If not, who else would you recommend I should reach out to? I would much appreciate your thoughts. Thanks!
Hi Srishti! Yes, I might be interested in this proposal. However, before I can give a final answer, I'd like to know a little bit more about the workshop. Specifically: 1) Is there a planned date on which this is going to happen? I want to make sure it doesn't collide with my personal agenda. 2) How long is the workshop going to be? This is just so I can get an idea on the topics that will be covered. And, 3) is there a list of (proposed) topics, or a place where people may ask for specific topics to be covered? Thank you!
Thanks Daimona for your willingness!
> 1) Is there a planned date on which this is going to happen? I want to make sure it doesn't collide with my personal agenda.
We are considering organizing this workshop sometime in the first weekend of December, on the 5th or 6th. But, we can be flexible if you want to propose a date and time that works best for you.
> 2) How long is the workshop going to be? This is just so I can get an idea on the topics that will be covered.
I imagine this topic would require 1-2 hours. Ideally, we envision this workshop to be hands-on; the goal is for participants to learn the necessary skills needed to combat vandalism and apply on their wikis immediately after the workshop. Also, some or all participants who will attend might not have a technical background, which also needs to be kept in mind while designing it. Having said that, feel free to design it as you feel right.
> 3) is there a list of (proposed) topics, or a place where people may ask for specific topics to be covered?
There isn't a list of proposed topics, only that in a recent conversation with Indic community members, they shared a need to learn about the tools to fight vandalism on their wikis. And, after talking with a few folks, we learned that AbuseFilter is the recommended option. So, we would like to keep this focus, but feel free to include the topics that would be relevant. If you have a specific ask from participants, we would be willing to share that with them when we promote this workshop. I don't know much about this topic, but I can imagine that we can ask participants, for example, to bring instances of vandalism that they face on their wikis or share them with us in advance, so you can help write filters to address those during the workshop. Is this possible?
> We are considering organizing this workshop sometime in the first weekend of December, on the 5th or 6th. But, we can be flexible [...]
Great, thank you. I think that should be a relatively quiet period of the year, so it's likely OK.
> I imagine this topic would require 1-2 hours.
Hm, pretty long then. Perhaps we might have 2 parts, even on different days; say, 1h theory, 1h practice.
> Ideally, we envision this workshop to be hands-on; the goal is for participants to learn the necessary skills needed to combat vandalism and apply on their wikis immediately after the workshop.
This makes sense. We're still going to need some theory about how it works (generally speaking), but I'll keep in mind to focus on practice.
> Also, some or all participants who will attend might not have a technical background, which also needs to be kept in mind while designing it.
This is not a problem, especially if we agree on that beforehand. I can reserve some time for a brief introduction, e.g. to regular expressions.
> If you have a specific ask from participants, we would be willing to share that with them when we promote this workshop.
Not really, no, except for the level of technical background to assume. Specifically, the only real background we're going to need is about regular expressions, so my only question would be: "should we have a quick overview of what regular expressions can do?"; note, however, that this is not a simple topic, as it would require a full talk to be explained properly, so I'd expect participants to try and read something in advance, then answer their questions about that.
> we can ask participants, for example, to bring instances of vandalism that they face on their wikis or share them with us in advance, so you can help write filters to address those during the workshop. Is this possible?
Totally! In fact, that would be a great source of examples.
Thank you! We can organize the workshop in 2 parts then. We can do both on the same weekend, one on each day. Or, we can do one the following weekend. Whatever your preference would be. Time-wise, would 6 pm CEST work for you?
To your question about regular expressions, I think yes! It would make sense to assume that participants knowledge might be limited on this topic.
> We can do both on the same weekend, one on each day. Or, we can do one the following weekend. Whatever your preference would be.
I think both on the same weekend is fine, although it really depends on the precise date
> To your question about regular expressions, I think yes! It would make sense to assume that participants knowledge might be limited on this topic.
Makes sense. I'm probably not the best person for a full talk about regular expressions, but I can try preparing an introductory talk for the limited features that people might need when writing filters.
I have added the details on the date & time here. As of now the workshop is scheduled for 2:30 pm your time (which would be 6 pm for participants joining from India). I realized the time I proposed earlier will be too late for participants. Hope it still works for you!
Rest all sounds good to me. If participants share information ahead of the workshop, I will pass that on to you. If not, then we can sync-up here a week or so before the workshop.
> I have added the details on the date & time here.
Unfortunately, I have to decline availability for Dec 5. We can do both talks on the 6th, if that works. Or perhaps a single talk lasting 90 minutes?
> As of now the workshop is scheduled for 2:30 pm your time [...] Hope it still works for you!
Sure!
> Rest all sounds good to me. If participants share information ahead of the workshop, I will pass that on to you. If not, then we can sync-up here a week or so before the workshop.
Nice! Just to get an insight and prepare a couple of slides, I'm assuming that we're going to have an introduction to regular expressions, and an overview of AbuseFilter, followed by hands-on examples (I'll propose some, and include any request). Assuming a duration of 90 minutes it might be 60+30. Would that work?
Yes, I think a single 90-minute session on December 6th covering the topics you shared makes total sense to it! I've made changes to date and time on the wiki..
@Daimona Eaytoy Hope you have received the calendar invitation for the workshop already. You can also see the workshop details and the meeting link here. In our initial announcement, we asked participants to share any particular problems they would like to focus on during the workshop, but we haven't heard any replies. So, you may plan the workshop as you would like. If you have any questions, please let me know. I hope the timing still works for you; thank you for willing to mentor!
@SSethi (WMF):: Yes, thank you! The date still works, but I became a bit unsure about the timings. This really depends on the background of the participants, and how much we want to go in detail, but I think that 30 minutes for regular expression might not suffice, since I'd include an interactive part. Or they might suffice, and the talk could fit the 90 minutes timeframe. In doubt, I wonder if it would be possible to allocate 30 minutes more, to be used only if necessary (and also for questions etc.).
@Daimona Eaytoy Sorry, I missed the notification for your message. If you feel that there is an interest from participants to stay for longer during the workshop, or focus on specific areas, feel free to take 30 minutes extra.
The translation extension actually uses blank lines to separate translation units. As smaller translation units are usually better (especially splitting headings from content and paragraphs from content from each other), it would be nice if you used a little more whitespace adding new information to translatable pages.
Hey, thanks for the advice. I confess I'm a complete ignorant for what concerns the Translate extension (which is why I didn't ask for transladmin rights). I'll try to pay attention to whitespace for my future edits. Thanks again!
Special:AbuseLog/171380 The creator of the page attempted to blank the page they created in error but get blocked.
Can I add & !(page_first_contributor == user_name) to the rule to allow page creators blank pages? Also, I expect to add & !(lcase(new_wikitext) rlike "{{[ _]*(speedy|delete)" to allow blanking with only deletion templates left (With reference to m:Special:AbuseFilter/117).
Can you please give some suggestions? Thanks!
Hi, the false positive happened before a global filter had warned the user at their first attempt. I'd advice against using that variable because it's really slow. Anyway, I've tweaked the filter to avoid triggering if the user was just warned, and implemented the {{speedy}} part. However, I strongly recommend avoiding to talk publicly about private filters. Feel free to send me an email next time.
Noted with thanks. I will avoid talking about private filters in public. Best regards.
Thank you for reporting it :-)
Hi!
Thanks for your huge work on AF!
I'm surprised by this strange filter catch fr:Spécial:Filtre_antiabus/examine/log/2533647. The filter itself contains only one rule, user_blocked. But I can't find any reference to such block in block log. Perhaps I've missed something?
Thanks!
Hello @Framawiki! I checked the link, but user_blocked is false for it. Could you please link the affected filter? Thanks!
Oops, not the good link. That is fr:Spécial:Journal_du_filtre_antiabus/2533646 & fr:Spécial:Filtre_antiabus/examine/log/2533646 for fr:Spécial:Filtre_antiabus/176. I also see here too no value for user_blocked.
@Framawiki Huh, that looks very bad... I strongly suspect it has something to do with the recent refactors of the Block class. I've merged this patch 15 minutes ago, let's see if that helps somehow. Please do write me again if you notice this bug again with the new version of MediaWiki. Thanks!
Thank you for your quick answer!
@Framawiki I checked the filter again, and looking at the last hits it seems like the problem is fixed, could you please confirm? Note that user_blocked is true for partially blocked users, but that's known (phab:T201815).
I'll try to monitor and will ping you if needed. Thanks!
|
The Technical Barnstar |
| For your amazing hard work in overhauling AbuseFilter and making it not suck in general. You have single-handedly addressed most of the major bugs and feature requests that have been left unattended for years. To top it off, it looks really nice on the frontend now, too! We all can't thank you enough. You. are. awesome. :D |
Many thanks, I really appreciate your words :-) I love to help with it, and I hope we'll get even better results in the future pulling ourselves together.
Hey,
I wanted to reach out to you rather than have a discussion within a bug where its not really right to do so.
I managed to get the call to work using:
$result = Shell::command(
self::getPygmentizePath() .
' -l ' . $lexer .
' -f ' . 'html' .
' -O ' . implode( ',', $optionPairs )
)
Note that I had to add spaces before and after each - (dash)
But I then have the problem you described However, this isn't a complete solution, as another problem pops out: the process starts running, but never stops.
I wondered if you had any further suggestions on how to complete this solution?
I have also tried adding < NUL to the end:
[exec] MediaWiki\Shell\Command::execute: "C:\Python27\Scripts\pygmentize.exe -l sql -f html -O cssclass=mw-highlight,encoding=utf-8 < NUL"
But this (as expected) results in no output, so the code block is empty in the wiki page when being viewed by the user.
@Quinnj09 Right, I forgot the spaces :-) Anyway, there's nothing we can do with the "new" problem. See https://phabricator.wikimedia.org/T199989 for a little more of explanation.
@Daimona Eaytoy this leaves me in an annoying place (I know no fault to the mediawiki developers or yourself) in that I cannot upgrade from mediawiki 1.27.0 to 1.31.0 until I find a solution for this, as we require this to work once upgraded.
Now I know it works using PHP version 5.6.30 (cgi-fcgi) (because my production system uses this) but then its broken in PHP version 7.0.15 (cgi-fcgi) (which is my test system for testing mw 1.31.0)
Im wondering, if theres a way I can get the call:
"C:\Python27\Scripts\pygmentize.exe -l sql -f html -O cssclass=mw-highlight,encoding=utf-8"
to explicitly use version 5.6.30, if I had both versions installed.
Unfortunately PHP version 7 or higher is required for mw 1.31.0 from what I understand (but feel free to correct me)
@Quinnj09 I understand, and I hope this will be fixed soon. MW 1.31 requires PHP 7+ (see Compatibility) and I can surely say that SyntaxHighlight did work on an older MW release (can't recall which one, maybe 1.30). Unfortunately, I can't give any more help at the moment.
@Daimona Eaytoy thats fine, thanks for your assistance though. One last question, at a guess do you think it would be this year a solution/fix will be found?
@Quinnj09 I don't know :-) It depends on whether someone is planning to work on this soon. Any further update will be tracked on the phabricator task.