User talk:Thryduulf

I only look at the this page very occasionally, so you are better off leaving any messages for me at my Enlgish Wikipedia talk page. Thryduulf (en.wikt,en.wp,commons) 22:28, 17 October 2013 (UTC)

Thank you

Thanks for your input, I've fixed the double redirect on Foundation wiki. --M/ 23:50, 14 December 2005 (UTC)

Ottava

Ottava is requesting "immediate action" against you. You're safe. They won't take action, but I figured you should know that Ottava wants you banned. --Michaeldsuarez (talk) 16:03, 10 December 2014 (UTC)

• Thanks for the heads up. I kind of suspected they might do something like this - it's always a risk when asking for NPOV in this topic area. Thryduulf (en.wikt,en.wp,commons) 17:21, 10 December 2014 (UTC)
  • You're welcome. --Michaeldsuarez (talk) 18:14, 10 December 2014 (UTC)
  • It's not "they," it's Ottava Rima. "He," though I suppose you can use the gender-neutral "they." The area is very hot, to be sure, but Ottava has long been obsessed by it. --Abd (talk) 03:12, 12 December 2014 (UTC)
    • @Abd Indeed in my comment I'm using the word "they" as a gender-neutral singular pronoun (as I don't know Ottava's gender). As for your comment on Sj's talk page, I have requested Ottava's comments be oversighted (I stand by my description of accusing someone of having paedophilic secrets as libellous) but as yet the oversight team have not responded to me. If this were en.wp I would indeed expect a user making such accusations to be banned (but of course Ottava is already banned from there for similar behaviour). Thryduulf (en.wikt,en.wp,commons) 14:23, 12 December 2014 (UTC)
• Yes. There is precedent. There was a flap on en.wikiversity. A user wanted to discuss "child protection" issues, on my user talk page. I shut that down immediately -- the user is cooperative -- but, long story short, a probationary custodian blocked the user anyway, and when another custodian handled that (routinely, making sure that all legitimate concerns were addressed before unblocking), he came to meta and made accusations. The filing was a repeat of what was on Wikiversity, doomed from the start. His later comments were oversighted.[1]. I'll mention that the oversighting followed from my emailed complaint to stewards-l, as I recall. It can take some time.
• Upshot: he was desysopped. He had zero support, beyond an IP comment. Notice he mentions OR. Mostly OR has stayed out of trouble, but he did comment in this affair.[2][3].
• OR was also blocked on Commons for similar highly tendentious behavior. (I'd say he's really banned, but they did not make it formal, though he had clearly "exhausted the patience of the community.") --Abd (talk) 19:44, 12 December 2014 (UTC)

Suppression of personal attack

As per your request, the off-topic comment aimed at you has been suppressed. Apologies for a tardy response, another oversighter had asked for comment about your request and I was presuming that they were taking action, however, apparently not.  — billinghurst sDrewth 12:24, 14 December 2014 (UTC)

Thank you. I hope that is now the end of that matter. Thryduulf (en.wikt,en.wp,commons) 22:50, 16 December 2014 (UTC)

Reminder: Please sign new Wikimedia confidentiality agreement for nonpublic information by 31 December

This is a message from the Wikimedia Foundation. Translations are available.

I wanted to follow-up on an message I sent you in September regarding the need for you to sign a confidentiality agreement by 31 December 2015 in order to maintain your access from Wikimedia to nonpublic information, and specifically to the OTRS system.

As you may know, the Wikimedia Foundation Board of Trustees approved a new "Access to nonpublic information policy" on 25 April 2014 after a community consultation. The former policy has remained in place until the new policy could be implemented. That implementation work is now being done, and we are transitioning to the new policy.

An important part of that transition is helping volunteers like you sign the required confidentiality agreement. All Wikimedia volunteers with access to nonpublic information are required to sign this new agreement, and we have prepared some documentation to help you do so.

The Wikimedia Foundation is requiring that anyone with access to nonpublic information sign the new confidentiality agreement by 31 December 2015 to retain their access. You are receiving this message because you have access to nonpublic information by way of the OTRS system and are required to sign the confidentiality agreement under the new policy. If you do not sign the new confidentiality agreement by 31 December 2015, you will lose your OTRS access.

Signing the confidentiality agreement for nonpublic information is conducted and tracked using Legalpad on Phabricator. We have prepared a guide on Meta-Wiki to help you create your Phabricator account and sign the new agreement: Confidentiality agreement for nonpublic information/How to sign

If you have any questions or experience any problems while signing the new agreement, please visit this talk page or email me (gvarnumwikimedia.org). Again, please sign this confidentiality agreement by 31 December 2015 to retain your access to nonpublic information. If you do not wish to retain this access, please let me know and we will forward your request to the appropriate individuals.

If you wish to stop receiving these notices, you may remove yourself from this list. Please note that doing so will not prevent you from losing OTRS rights and access after the 31 December 2015 deadline.

Thank you,
Gregory Varnum (User:GVarnum-WMF), Wikimedia Foundation

Posted by the MediaWiki message delivery, 06:23, 22 December 2015 (UTC) • Please help translate to your language • Help

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

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:51, 16 July 2018 (UTC)

DiscussionTools

Hi, Thryduulf,

The Editing team has scheduled a major update to mw:Extension:DiscussionTools (the new Reply tool) for next week's deployment train. Since you invoke the feature from a script (I do, too), you're probably going to see that update next week, before it's officially released in the mw:Beta Feature system. The new update will use a similar system for starting a ==New discussion==. As before, full-page wikitext editing will not be affected. There is more information on the project page at mw:Talk pages project/New discussion.

If you encounter problems next week, please ping me or leave a note on the talk page for the project. Thanks, Whatamidoing (WMF) (talk) 22:08, 12 January 2021 (UTC)

Tech News: 2024-47

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

• Users of Wikimedia sites will now be warned when they create a redirect to a page that doesn't exist. This will reduce the number of broken redirects to red links in our projects. [4]
• View all 42 community-submitted tasks that were resolved last week. For example, Pywikibot, which automates work on MediaWiki sites, was upgraded to 9.5.0 on Toolforge. [5]

Updates for technical contributors

• On wikis that use the FlaggedRevs extension, pages created or moved by users with the appropriate permissions are marked as flagged automatically. This feature has not been working recently, and changes fixing it should be deployed this week. Thanks to Daniel and Wargo for working on this. [6][7]

In depth

• There is a new Diff post about Temporary Accounts, available in more than 15 languages. Read it to learn about what Temporary Accounts are, their impact on different groups of users, and the plan to introduce the change on all wikis.

Meetings and events

• Technical volunteers can now register for the 2025 Wikimedia Hackathon, which will take place in Istanbul, Turkey. Application for travel and accommodation scholarships is open from November 12 to December 10 2024. The registration for the event will close in mid-April 2025. The Wikimedia Hackathon is an annual gathering that unites the global technical community to collaborate on existing projects and explore new ideas.
• Join the Wikimedia Commons community calls this week to help prioritize support for Commons which will be planned for 2025–2026. The theme will be how content should be organised on Wikimedia Commons. This is an opportunity for volunteers who work on different things to come together and talk about what matters for the future of the project. The calls will take place November 21, 2024, 8:00 UTC and 16:00 UTC.
• A Language community meeting will take place November 29, 16:00 UTC to discuss updates and technical problem-solving.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 02:01, 19 November 2024 (UTC)

Tech News: 2024-48

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

• A new version of the standard wikitext editor-mode syntax highlighter will be available as a beta feature later this week. This brings many new features and bug fixes, including right-to-left support, template folding, autocompletion, and an improved search panel. You can learn more on the help page.
• The 2010 wikitext editor now supports common keyboard shortcuts such Ctrl+B for bold and Ctrl+I for italics. A full list of all six shortcuts is available. Thanks to SD0001 for this improvement. [8]
• Starting November 28, Flow/Structured Discussions pages will be automatically archived and set to read-only at the following wikis: bswiki, elwiki, euwiki, fawiki, fiwiki, frwikiquote, frwikisource, frwikiversity, frwikivoyage, idwiki, lvwiki, plwiki, ptwiki, urwiki, viwikisource, zhwikisource. This is done as part of StructuredDiscussions deprecation work. If you need any assistance to archive your page in advance, please contact Trizek (WMF).
• View all 25 community-submitted tasks that were resolved last week. For example, a user creating a new AbuseFilter can now only set the filter to "protected" if it includes a protected variable.

Updates for technical contributors

• The CodeEditor, which can be used in JavaScript, CSS, JSON, and Lua pages, now offers live autocompletion. Thanks to SD0001 for this improvement. The feature can be temporarily disabled on a page by pressing Ctrl+, and un-selecting "Live Autocompletion".
• Tool-maintainers who use the Graphite system for tracking metrics, need to migrate to the newer Prometheus system. They can check this dashboard and the list in the Description of the task T350592 to see if their tools are listed, and they should claim metrics and dashboards connected to their tools. They can then disable or migrate all existing metrics by following the instructions in the task. The Graphite service will become read-only in April. [9]
• The New PreProcessor parser performance report has been fixed to give an accurate count for the number of Wikibase entities accessed. It had previously been resetting after 400 entities. [10]

Meetings and events

• A Language community meeting will take place November 29 at 16:00 UTC. There will be presentations on topics like developing language keyboards, the creation of the Mooré Wikipedia, the language support track at Wiki Indaba, and a report from the Wayuunaiki community on their experiences with the Incubator and as a new community over the last 3 years. This meeting will be in English and will also have Spanish interpretation.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 22:42, 25 November 2024 (UTC)

Tech News: 2024-49

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

• Two new parser functions were added this week. The {{#interwikilink}} function adds an interwiki link and the {{#interlanguagelink}} function adds an interlanguage link. These parser functions are useful on wikis where namespaces conflict with interwiki prefixes. For example, links beginning with MOS: on English Wikipedia conflict with the mos language code prefix of Mooré Wikipedia.
• Starting this week, Wikimedia wikis no longer support connections using old RSA-based HTTPS certificates, specifically rsa-2048. This change is to improve security for all users. Some older, unsupported browser or smartphone devices will be unable to connect; Instead, they will display a connectivity error. See the HTTPS Browser Recommendations page for more-detailed information. All modern operating systems and browsers are always able to reach Wikimedia projects. [11]
• Starting December 16, Flow/Structured Discussions pages will be automatically archived and set to read-only at the following wikis: arwiki, cawiki, frwiki, mediawikiwiki, orwiki, wawiki, wawiktionary, wikidatawiki, zhwiki. This is done as part of StructuredDiscussions deprecation work. If you need any assistance to archive your page in advance, please contact Trizek (WMF). [12]
• This month the Chart extension was deployed to production and is now available on Commons and Testwiki. With the security review complete, pilot wiki deployment is expected to start in the first week of December. You can see a working version on Testwiki and read the November project update for more details.
• View all 23 community-submitted tasks that were resolved last week. For example, a bug with the "Download as PDF" system was fixed. [13]

Updates for technical contributors

• In late February, temporary accounts will be rolled out on at least 10 large wikis. This deployment will have a significant effect on the community-maintained code. This is about Toolforge tools, bots, gadgets, and user scripts that use IP address data or that are available for logged-out users. The Trust and Safety Product team wants to identify this code, monitor it, and assist in updating it ahead of the deployment to minimize disruption to workflows. The team asks technical editors and volunteer developers to help identify such tools by adding them to this list. In addition, review the updated documentation to learn how to adjust the tools. Join the discussions on the project talk page or in the dedicated thread on the Wikimedia Community Discord server (in English) for support and to share feedback.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 22:23, 2 December 2024 (UTC)