Jump to content

User talk:Thryduulf

Add topic
From Meta, a Wikimedia project coordination wiki
Latest comment: 5 days ago by MediaWiki message delivery in topic Tech News: 2024-25

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)Reply

Thank you[edit]

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


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)Reply

  • 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)Reply
    • You're welcome. --Michaeldsuarez (talk) 18:14, 10 December 2014 (UTC)Reply
    • 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)Reply
      • @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)Reply
  • 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)Reply

Suppression of personal attack[edit]

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)Reply

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

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 (gvarnum@wikimedia.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 languageHelpReply

Next steps for the wish “confirmation prompt for the rollback link”[edit]

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)Reply


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)Reply

Tech News: 2023-22[edit]

MediaWiki message delivery 22:03, 29 May 2023 (UTC)Reply

Tech News: 2023-23[edit]

MediaWiki message delivery 22:52, 5 June 2023 (UTC)Reply

Tech News: 2023-24[edit]

MediaWiki message delivery 14:51, 12 June 2023 (UTC)Reply

Tech News: 2023-25[edit]

MediaWiki message delivery 20:09, 19 June 2023 (UTC)Reply

Tech News: 2023-26[edit]

MediaWiki message delivery 16:19, 26 June 2023 (UTC)Reply

Tech News: 2023-27[edit]

MediaWiki message delivery 22:51, 3 July 2023 (UTC)Reply

Tech News: 2023-28[edit]

MediaWiki message delivery 19:54, 10 July 2023 (UTC)Reply

Tech News: 2023-29[edit]

MediaWiki message delivery 23:08, 17 July 2023 (UTC)Reply

Tech News: 2023-30[edit]

MediaWiki message delivery 02:20, 25 July 2023 (UTC)Reply

Tech News: 2023-31[edit]

MediaWiki message delivery 23:54, 31 July 2023 (UTC)Reply

Tech News: 2023-32[edit]

MediaWiki message delivery 21:21, 7 August 2023 (UTC)Reply

Tech News: 2023-33[edit]

MediaWiki message delivery 05:59, 15 August 2023 (UTC)Reply

Tech News: 2023-34[edit]

15:25, 21 August 2023 (UTC)

Tech News: 2023-35[edit]

MediaWiki message delivery 14:00, 28 August 2023 (UTC)Reply

Tech News: 2023-36[edit]

MediaWiki message delivery 23:33, 4 September 2023 (UTC)Reply

Tech News: 2023-37[edit]

MediaWiki message delivery 21:08, 11 September 2023 (UTC)Reply

Tech News: 2023-38[edit]

MediaWiki message delivery 19:19, 18 September 2023 (UTC)Reply

Tech News: 2023-39[edit]

MediaWiki message delivery 16:51, 26 September 2023 (UTC)Reply

Tech News: 2023-40[edit]

MediaWiki message delivery 01:27, 3 October 2023 (UTC)Reply

Tech News: 2023-41[edit]

MediaWiki message delivery 14:39, 9 October 2023 (UTC)Reply

Tech News: 2023-42[edit]

MediaWiki message delivery 23:47, 16 October 2023 (UTC)Reply

Tech News: 2023-43[edit]

MediaWiki message delivery 23:16, 23 October 2023 (UTC)Reply

Tech News: 2023-44[edit]

MediaWiki message delivery 23:21, 30 October 2023 (UTC)Reply

Tech News: 2023-45[edit]

MediaWiki message delivery 21:06, 6 November 2023 (UTC)Reply

Tech News: 2023-46[edit]

MediaWiki message delivery 23:52, 13 November 2023 (UTC)Reply

Tech News: 2023-47[edit]

MediaWiki message delivery 00:55, 21 November 2023 (UTC)Reply

Tech News: 2023-48[edit]

MediaWiki message delivery 23:08, 27 November 2023 (UTC)Reply

Tech News: 2023-49[edit]

MediaWiki message delivery 23:50, 4 December 2023 (UTC)Reply

Tech News: 2023-50[edit]

MediaWiki message delivery 02:12, 12 December 2023 (UTC)Reply

Tech News: 2023-51[edit]

MediaWiki message delivery 16:18, 18 December 2023 (UTC)Reply

Tech News: 2024-02[edit]

MediaWiki message delivery 01:19, 9 January 2024 (UTC)Reply

Tech News: 2024-03[edit]

MediaWiki message delivery 00:13, 16 January 2024 (UTC)Reply

Tech News: 2024-04[edit]

MediaWiki message delivery 01:04, 23 January 2024 (UTC)Reply

Tech News: 2024-05[edit]

MediaWiki message delivery 19:31, 29 January 2024 (UTC)Reply

Tech News: 2024-06[edit]

MediaWiki message delivery 19:22, 5 February 2024 (UTC)Reply

Tech News: 2024-07[edit]

MediaWiki message delivery 05:49, 13 February 2024 (UTC)Reply

Tech News: 2024-08[edit]

MediaWiki message delivery 15:37, 19 February 2024 (UTC)Reply

Tech News: 2024-09[edit]

MediaWiki message delivery 19:23, 26 February 2024 (UTC)Reply

Tech News: 2024-10[edit]

MediaWiki message delivery 19:47, 4 March 2024 (UTC)Reply

Tech News: 2024-11[edit]

MediaWiki message delivery 23:04, 11 March 2024 (UTC)Reply

Tech News: 2024-12[edit]

MediaWiki message delivery 17:39, 18 March 2024 (UTC)Reply

Tech News: 2024-13[edit]

MediaWiki message delivery 18:56, 25 March 2024 (UTC)Reply

Tech News: 2024-14[edit]

MediaWiki message delivery 03:36, 2 April 2024 (UTC)Reply

Tech News: 2024-15[edit]

MediaWiki message delivery 23:37, 8 April 2024 (UTC)Reply

Tech News: 2024-16[edit]

MediaWiki message delivery 23:29, 15 April 2024 (UTC)Reply

Tech News: 2024-17[edit]

MediaWiki message delivery 20:28, 22 April 2024 (UTC)Reply

Tech News: 2024-18[edit]

MediaWiki message delivery 03:33, 30 April 2024 (UTC)Reply

Tech News: 2024-19[edit]

MediaWiki message delivery 16:44, 6 May 2024 (UTC)Reply

Tech News: 2024-20[edit]

MediaWiki message delivery 23:58, 13 May 2024 (UTC)Reply

Tech News: 2024-21[edit]

MediaWiki message delivery 23:04, 20 May 2024 (UTC)Reply

Tech News: 2024-22[edit]

MediaWiki message delivery 00:15, 28 May 2024 (UTC)Reply

Tech News: 2024-23[edit]

MediaWiki message delivery 22:35, 3 June 2024 (UTC)Reply

Tech News: 2024-24[edit]

MediaWiki message delivery 20:20, 10 June 2024 (UTC)Reply

Tech News: 2024-25[edit]

MediaWiki message delivery 23:49, 17 June 2024 (UTC)Reply