User Details
- User Since
- Jan 24 2020, 2:12 AM (224 w, 6 d)
- Availability
- Available
- LDAP User
- Unknown
- MediaWiki User
- Albertoleoncio [ Global Accounts ]
Tue, May 14
Fri, May 10
Fri, May 3
Wed, Apr 17
I miss some documentation about executing commands in non-interactive mode and deployment integration with, say, GitHub Actions. I found a use here, but it's not very clear how it works and how to reuse it in other tools. This could be useful for, for example, automatic database migrations via Django, building applications using NodeJS frameworks, etc...
Mar 31 2024
Mar 9 2024
Mar 4 2024
FYI: We noticed a small bug in the pt.wiki MediaWiki:Deletereason-dropdown as {{ns:2300}}/{{ns:2301}}/{{ns:2302}}/{{ns:2303}} was no longer valid. It may be worth doing a scan to identify whether those is still used in other wikis.
Mar 2 2024
Feb 21 2024
@Slst2020 I'm having a problem with credentials. I don't know if I'm running it incorrectly, or if I'm missing some permission.
Feb 17 2024
@abi_ @Nikerabbit Hello! I submitted this patch after reading a complaint via Telegram, but it is still awaiting review. Are there any blockers or concerns against approving this request?
Feb 16 2024
Feb 11 2024
Feb 5 2024
Jan 31 2024
Jan 26 2024
Nov 6 2023
Oct 25 2023
Oct 23 2023
Oct 12 2023
Oct 6 2023
Well... It didn't. Is there any way I can activate it manually? Or can I just download the JSONs?
Another thing: I had published the Brazilian Portuguese translations as "pt", but I noticed that they had started translating as "pt-br". To avoid duplication, I renamed the file on GitHub but the change was not replicated on TranslateWiki.
Oct 3 2023
Oct 2 2023
@abi_ I saw that the translations were already published today on GitHub, but not to WikiScore. Something went wrong?
Sep 25 2023
- The project is missing the message documentation (qqq.json file). You can read more about it here: https://translatewiki.net/wiki/Translating:Localisation_for_developers#Message_documentation and you can see an example of how this file looks here: https://github.com/toolforge/video2commons/blob/master/video2commons/frontend/i18n/qqq.json
I never did documentation for each variable. Would it be possible to do it directly on TranslateWiki?
Sep 24 2023
Aug 15 2023
Jul 28 2023
Jul 23 2023
Jul 6 2023
This too. We have:
- Two scripts that directs the logged out user to the login screen when he clicks on the edit link.
- The filter that prevents logged-out users from editing and
- Several IP range blocks that block the busiest ranges, "alleviating" the abusefilter.
Allied to these measures, we modified some messages in the MediaWiki (example) so that it does not appear that our future editor is "blocked" or that he is "prevented from editing", just that he needs to create an account first.
It sounds confusing, but works like a charm.
I've been thinking about this for a while now, but today I'm not sure it's a good idea. Everyone is happy with the way it's working and moving to a server-side configuration could break some part of the current workflow (special attention to T287228).
Also, Farsi Wikipedia was allowed a configuration change in T291018: Temporarily disable article editing by anonymous users on fawiki
And we had different results, where part of that could be attributed to the way it was implemented.
Jun 20 2023
Done!
Jun 14 2023
Done!
Jun 13 2023
Oh, OK. It does less than I thought.
Personally, I’m skeptical of changing the interpretation from “it’s fine if there’s no connected item” to “it’s mandatory that there’s no connected item” – but that’s for Product to decide.
I've modified the description a bit to make the issue clearer. It's not that I want to be mandatory, but that at least the pages that have this magic word don't have that "appearance of incompleteness" because they don't have a connection to Wikidata.
Jun 12 2023
Jun 2 2023
Just to contribute some post-deployment ideas, I recently made an accessory tool to ptwiki's SBL that provides some relevant information about the inclusion of an URL, mainly the timestamp, the author of the inclusion and a link to their edits on that day (sometimes the author's explanation is a bit hollow, while their before/after edits helps providing some context about that URL).
@SCherukuwada I have an interesting one: [[:s:pt:O Movimento Modernista]]
May 23 2023
May 22 2023
May 21 2023
Example:
May 20 2023
What was initially requested has already been done, so...
May 19 2023
May 16 2023
Apr 17 2023
Apr 16 2023
Mar 15 2023
- Editor is FlaggedRevs' user group, once we remove it from wiki, it will disappear. Patrolling edits is better and easier mechanism than FlaggedRevs for small and not really active wikis.
- Do you want patrolling option (like on Wikipedia) to be enabled back? With autopatrol, patroller and rollbacker rights.
I myself don't believe it's necessary, as we don't even have users to patrol edits. However, I think it's useful to keep the editor group and associate it with an intermediate level of protection for pages (between autoconfirmed and sysop). I imagine this requires another ticket, but the group could be maintained without any special privileges until then.
- If extension won't be enabled again, do you want FlaggedRevs tables from database to be removed?
Could we do the same thing as T209761#4812733, but keep the tables for like... 6 months? The extension would be unlikely to be reactivated again, but there wasn't exactly a big discussion and the tables are small in terms of storage, so I think keeping them for a reasonable amount of time would be convenient, just in case.
Mar 11 2023
Mar 7 2023
Mar 6 2023
Not sure if it's the same bug or something else.
Mar 3 2023
Feb 21 2023
Dec 19 2022
Including SRE as it involves Google Search Console
Nov 8 2022
Sep 6 2022
Jul 26 2022
Jul 7 2022
May 31 2022
Jan 19 2022
Jan 13 2022
I just did a 5.62 BRL donation by Pix and it worked! I noticed other things that may be addressed:
Jan 12 2022
There has been an error processing your request. Please contact Donor Services at donate@wikimedia.org.
Error reference: 117500188.1
Oct 30 2021
Oct 18 2021
Our need is basically to stop the flow of requests from the list and enforce the use of VRTS. The first option is good enough for this.
The autoresponder can be something as simple as:
Sep 5 2021
May 23 2021
May 20 2021
May 5 2021
May 4 2021
Apr 22 2021
Can we use it as a workaround? I've seen many complains about this error at pt.wiki.