User talk:ToBeFree
2409:408C:8D49:BD9C:B90A:CC26:DBB6:2535/64
[edit]TOBeFree, need your help regarding an issue this IP range is engaged in making so many disruptions.[1] I've repoted this IP at WP:AVI[2] but still have not received a result. IP might be conducting block evasion, but I'm not sure their belonging.®asteem Talk 09:03, 11 October 2024 (UTC)
- HJ Mitchell was faster. Thanks! ~ ToBeFree (talk) 10:57, 11 October 2024 (UTC)
- No problem. I just worked my way down the list at AIV. HJ Mitchell | Penny for your thoughts? 11:01, 11 October 2024 (UTC)
- HJ Mitchell Thanks for the quick handling at AIV. ®asteem Talk 02:57, 12 October 2024 (UTC)
- ToBeFree Thank you very much.®asteem Talk 02:55, 12 October 2024 (UTC)
- No problem. I just worked my way down the list at AIV. HJ Mitchell | Penny for your thoughts? 11:01, 11 October 2024 (UTC)
Monsieur Patillo
[edit]Hello, ToBeFree,
I looked through all of those diffs on the AIV report and not only do they not seem like vandalism but they are some of the most polite and diplomatic "personal attacks" I've seen before. I'm glad you are discussing the block with the editor as your response to the AIV report didn't seem like an obvious choice to me. There is clearly a dispute going on in a few articles but I don't see any of the editors as blameless and it's hard to see any editor as more responsible than another, at least reading over the dispute that found it's way to AN.
With ongoing talk page discussions and dispute resolution discussions, I'm not sure it had reached the level of an indefinite block yet. It's obvious that the editors are very frustrated with each other but it also seems like multiple editors are trying to eliminate their editorial opponents by painting them in the worst possible light. I'm not in the position to advise you what to do and I'll just reiterate what I said that I'm glad that you are open to discussing the situation with Monsieur Patillo on their User talk page. Thanks. Liz Read! Talk! 03:13, 13 October 2024 (UTC)
- ~ ToBeFree (talk) 03:33, 13 October 2024 (UTC)
- Unblocked. Thanks, Liz. ~ ToBeFree (talk) 14:35, 13 October 2024 (UTC)
Tech News: 2024-42
[edit]Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Updates for editors
- The Structured Discussion extension (also known as Flow) is starting to be removed. This extension is unmaintained and causes issues. It will be replaced by DiscussionTools, which is used on any regular talk page. A first set of wikis are being contacted. These wikis are invited to stop using Flow, and to move all Flow boards to sub-pages, as archives. At these wikis, a script will move all Flow pages that aren't a sub-page to a sub-page automatically, starting on 22 October 2024. On 28 October 2024, all Flow boards at these wikis will be set in read-only mode. [3][4]
- WMF's Search Platform team is working on making it easier for readers to perform text searches in their language. A change last week on over 30 languages makes it easier to find words with accents and other diacritics. This applies to both full-text search and to types of advanced search such as the hastemplate and incategory keywords. More technical details (including a few other minor search upgrades) are available. [5]
- View all 20 community-submitted tasks that were resolved last week. For example, EditCheck was installed at Russian Wikipedia, and fixes were made for some missing user interface styles.
Updates for technical contributors
- Editors who use the Toolforge tool Earwig's Copyright Violation Detector will now be required to log in with their Wikimedia account before running checks using the "search engine" option. This change is needed to help prevent external bots from misusing the system. Thanks to Chlod for these improvements. [6]
- Phabricator users can create tickets and add comments on existing tickets via Email again. Sending email to Phabricator has been fixed. [7]
- Some HTML elements in the interface are now wrapped with a
<bdi>
element, to make our HTML output more aligned with Web standards. More changes like this will be coming in future weeks. This change might break some tools that rely on the previous HTML structure of the interface. Note that relying on the HTML structure of the interface is not recommended and might break at any time. [8]
In depth
- The latest monthly MediaWiki Product Insights newsletter is available. This edition includes: updates on Wikimedia's authentication system, research to simplify feature development in the MediaWiki platform, updates on Parser Unification and MathML rollout, and more.
- The latest quarterly Technical Community Newsletter is now available. This edition include: research about improving topic suggestions related to countries, improvements to PHPUnit tests, and more.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
MediaWiki message delivery 21:18, 14 October 2024 (UTC)
Cebu etc.
[edit]Thank you for protecting all those pages! I thought about requesting protection for them as a group but worried it was too big an ask. AntiDionysius (talk) 22:03, 14 October 2024 (UTC)
- Hi AntiDionysius, no worries! I think semi-protection of these pages won't hurt much and ends the easiest way for the sockpuppeteer to just continue "fighting" and getting attention. ~ ToBeFree (talk) 22:05, 14 October 2024 (UTC)
Inquiry related to IP you blocked
[edit]Hello ToBeFree. This IP strikes me as the same person as this LTA which you recently blocked (for context see: [9])
They are exhibiting the same nationalistic and aggressive behavior as the LTA. Stylistically quite similar in their edit summaries. For example: 78xx and 216xx; 78xx, 78xx and 216xx.
What's really interesting is they both make an edit, then revert themselves, and revert themselves again so that they can use the edit summary to rant.
- 78xx: Makes edit, reverts themselves and reverts again to rant in their edit summary
- 216xx: Makes edit, reverts themselves and reverts again to rant in their edit summary
The geographic location is different but the proxy check tool on 216xx reveals it is a proxy. So it seems they are using a proxy to evade block. --Griboski (talk) 15:55, 15 October 2024 (UTC)