User talk:Werdna

Hello

Is it me you're looking for? 216.38.130.168 20:27, 2 August 2012 (UTC)

A barnstar for you!

	The Brilliant Idea Barnstar
	Yet more barnstars all around to those on the Echo team. Genius. TortoiseWrath (talk) 04:16, 4 May 2013 (UTC)

LiquidThreads is awesome

This post by Werdna was moved on 2009-11-08. You can find it at LiquidThreads Test Page#LiquidThreads is awesome. Andrew Garrett 09:21, 8 November 2009 (UTC)

just testing... 171.67.129.29 00:35, 16 December 2009 (UTC)

Liquid Threads rocks. Thanks for creating it. Wonder what bump this thread means though. I will unclick it. I know eventually it will include a "what's this". 128.111.96.144 04:41, 14 February 2011 (UTC)

I WANTS POST

This post by Werdna was moved on 2009-11-08. You can find it at LiquidThreads Test Page#I WANTS POST. Andrew Garrett 09:21, 8 November 2009 (UTC)

Just testing...

This post by Werdna was moved on 2009-11-08. You can find it at LiquidThreads Test Page#Just testing.... Andrew Garrett 09:21, 8 November 2009 (UTC)

Just testing to see whether the thread works 171.67.129.29 00:32, 16 December 2009 (UTC)

Testing again this time with firebug open

This post by Werdna was moved on 2009-11-08. You can find it at LiquidThreads Test Page#Testing again this time with firebug open. Andrew Garrett 09:21, 8 November 2009 (UTC)

SocialProfile, RenameUser and RenameUserSQL hook

Hi Werdna,

I've been trying to make my SocialProfile extension support user renaming, which it does not currently. I decided to ask for your help because you added the useful RenameUserSQL hook to SpecialRenameuser_body.php in r55189.

Here's the patch I came up with:

Index: SocialProfile.php
===================================================================
--- SocialProfile.php	(revision 59581)
+++ SocialProfile.php	(working copy)
@@ -216,4 +216,47 @@
 		$wgExtNewTables[] = array( 'user_system_messages', "$dir/UserSystemMessages/user_system_messages.sql" );
 	}
 	return true;
+}
+
+// For Renameuser extension
+$wgHooks['RenameUserSQL'][] = 'efSystemGiftsOnUserRename';
+$wgHooks['RenameUserSQL'][] = 'efUserBoardOnUserRename';
+$wgHooks['RenameUserSQL'][] = 'efUserGiftsOnUserRename';
+$wgHooks['RenameUserSQL'][] = 'efUserRelationshipOnUserRename';
+$wgHooks['RenameUserSQL'][] = 'efUserStatsOnUserRename';
+$wgHooks['RenameUserSQL'][] = 'efUserSystemMessagesOnUserRename';
+
+function efSystemGiftsOnUserRename( $renameUserSQL ) {
+	$renameUserSQL->tables['user_system_gift'] = array( 'sg_user_name', 'sg_user_id' );
+	return true;
+}
+
+function efUserBoardOnUserRename( $renameUserSQL ) {
+	$renameUserSQL->tables['user_board'] = array( 'ub_user_name_from', 'ub_user_id_from' );
+	return true;
+}
+
+function efUserGiftsOnUserRename( $renameUserSQL ) {
+	$renameUserSQL->tables['user_gift'] = array( 'ug_user_name_to', 'ug_user_id_to' );
+	$renameUserSQL->tables['gift'] = array( 'gift_creator_user_name', 'gift_creator_user_id' );
+	return true;
+}
+
+function efUserRelationshipOnUserRename( $renameUserSQL ) {
+	// <fixme> This sucks and only updates half of the rows...wtf?
+	$renameUserSQL->tables['user_relationship'] = array( 'r_user_name_relation', 'r_user_id_relation' );
+	$renameUserSQL->tables['user_relationship'] = array( 'r_user_name', 'r_user_id' );
+	// </fixme>
+	$renameUserSQL->tables['user_relationship_request'] = array( 'ur_user_name_from', 'ur_user_id_from' );
+	return true;
+}
+
+function efUserStatsOnUserRename( $renameUserSQL ) {
+	$renameUserSQL->tables['user_stats'] = array( 'stats_user_name', 'stats_user_id' );
+	return true;
+}
+
+function efUserSystemMessagesOnUserRename( $renameUserSQL ) {
+	$renameUserSQL->tables['user_system_messages'] = array( 'um_user_name', 'um_user_id' );
+	return true;
 }
\ No newline at end of file

As noted in function efUserRelationshipOnUserRename it doesn't work like I'd want it to. All other functions do work as they should, however. Here's some example data (and the table structure of user_relationship table) from my local testing wiki:

CREATE TABLE IF NOT EXISTS `user_relationship` (
  `r_id` int(11) NOT NULL AUTO_INCREMENT,
  `r_user_id` int(5) unsigned NOT NULL DEFAULT '0',
  `r_user_name` varchar(255) NOT NULL DEFAULT '',
  `r_user_id_relation` int(5) unsigned NOT NULL DEFAULT '0',
  `r_user_name_relation` varchar(255) NOT NULL DEFAULT '',
  `r_type` int(2) DEFAULT NULL,
  `r_date` datetime DEFAULT NULL,
  PRIMARY KEY (`r_id`),
  KEY `r_user_id` (`r_user_id`),
  KEY `r_user_id_relation` (`r_user_id_relation`)
) ENGINE=MyISAM  DEFAULT CHARSET=utf8;

-- This signifies that User:Bar (user ID #2) is a friend of User:Foo (user id #1)
-- and the other way around
INSERT INTO `user_relationship` (`r_id`, `r_user_id`, `r_user_name`, `r_user_id_relation`, `r_user_name_relation`, `r_type`, `r_date`) VALUES
(1, 2, 'Bar', 1, 'Foo', 1, '2009-12-03 22:28:33'),
(2, 1, 'Foo', 2, 'Bar', 1, '2009-12-03 22:28:33');

When User:Bar is renamed to User:Baz, only one of the above entries is changed from 'Bar' to 'Baz' (can't remember which one) instead of both entries being changed. Is there a way to fix this and if so, how would I fix it?

Thanks in advance for your help! Jack Phoenix _(Contact) 15:00, 27 December 2009 (UTC)

Hi, I'm sorry for the late reply — I've been on vacation since December 20 last year.

I've just taken a peek at my own code, and it looks like the format for the array is $sql->tables['tablename'] = array( name_field, id_field, index_field ).

name_field is the field to update, id_field is a field with a user_id, and index_field is some sort of index for splitting up the job into manageable chunks (this may be only for tablesJob, I don't know).

I'm not quite clear on where you're going wrong, though. Any chance you could intercept the queries being used to update the rows? This might help us get a better idea of what's really going on in that crazy old class. Andrew Garrett 01:23, 1 February 2010 (UTC)

I renamed User:Bar to User:Baz under my "Foo" account. My user profile still shows "Bar" as my friend instead of "Baz". Here are the related queries from MySQL's query log:

		  123 Connect	root@localhost on 
		  123 Init DB	phasethree
		  123 Query	SET /* DatabaseMysql::open Foo */ NAMES utf8
		  123 Query	SET /* DatabaseMysql::open Foo */ sql_mode = ''
		  123 Query	SELECT /* SqlBagOStuff::get Foo */  value,exptime  FROM `objectcache`  WHERE keyname = 'phasethree:messages:en'  LIMIT 1
		  122 Query	SELECT /* LCStore_DB::get Foo */  lc_value  FROM `l10n_cache`  WHERE lc_lang = 'en' AND lc_key = 'messages:renameuser'  LIMIT 1
		  122 Query	SELECT /* LCStore_DB::get Foo */  lc_value  FROM `l10n_cache`  WHERE lc_lang = 'en' AND lc_key = 'magicWords'  LIMIT 1
		  122 Query	SELECT /* LCStore_DB::get Foo */  lc_value  FROM `l10n_cache`  WHERE lc_lang = 'en' AND lc_key = 'messages:renameuser-summary'  LIMIT 1
		  122 Query	SELECT /* LCStore_DB::get Foo */  lc_value  FROM `l10n_cache`  WHERE lc_lang = 'en' AND lc_key = 'linkPrefixExtension'  LIMIT 1
		  122 Query	SELECT /* LCStore_DB::get Foo */  lc_value  FROM `l10n_cache`  WHERE lc_lang = 'en' AND lc_key = 'messages:renameuserold'  LIMIT 1
		  122 Query	SELECT /* LCStore_DB::get Foo */  lc_value  FROM `l10n_cache`  WHERE lc_lang = 'en' AND lc_key = 'messages:renameusernew'  LIMIT 1
		  122 Query	SELECT /* LCStore_DB::get Foo */  lc_value  FROM `l10n_cache`  WHERE lc_lang = 'en' AND lc_key = 'messages:renameuserreason'  LIMIT 1
		  122 Query	SELECT /* LCStore_DB::get Foo */  lc_value  FROM `l10n_cache`  WHERE lc_lang = 'en' AND lc_key = 'messages:renameusermove'  LIMIT 1
		  122 Query	SELECT /* LCStore_DB::get Foo */  lc_value  FROM `l10n_cache`  WHERE lc_lang = 'en' AND lc_key = 'messages:renameusersubmit'  LIMIT 1
		  122 Query	SELECT /* LCStore_DB::get Foo */  lc_value  FROM `l10n_cache`  WHERE lc_lang = 'en' AND lc_key = 'messages:blocklogpage'  LIMIT 1
		  122 Query	SELECT /* LCStore_DB::get Foo */  lc_value  FROM `l10n_cache`  WHERE lc_lang = 'en' AND lc_key = 'messages:double-redirect-fixer'  LIMIT 1
		  122 Query	SELECT /* User::idForName Foo */  user_id  FROM `user`  WHERE user_name = 'Bar'  LIMIT 1
		  122 Query	SELECT /* User::idForName Foo */  user_id  FROM `user`  WHERE user_name = 'Baz'  LIMIT 1
		  122 Query	SELECT /* User::edits Foo */  user_editcount  FROM `user`  WHERE user_id = '5'  LIMIT 1
		  122 Query	SELECT /* User::edits Foo */  user_editcount  FROM `user`  WHERE user_id = '5'  LIMIT 1
		  122 Query	SELECT /* SiteStats::doLoad Foo */  *  FROM `site_stats`   LIMIT 1
		  122 Query	UPDATE /* RenameuserSQL::rename Foo */  `user` SET user_name = 'Baz',user_touched = '20100207170600' WHERE user_name = 'Bar'
		  122 Query	UPDATE /* RenameuserSQL::rename Foo */  `ipblocks` SET ipb_address = 'Baz' WHERE ipb_user = '5' AND ipb_address = 'Bar'
		  122 Query	UPDATE /* RenameuserSQL::rename Foo */  `logging` SET log_title = 'Baz' WHERE log_type IN ('block','rights')  AND log_namespace = '2' AND log_title = 'Bar'
		  122 Query	UPDATE /* RenameuserSQL::rename Foo */  `image` SET img_user_text = 'Baz' WHERE img_user_text = 'Bar' AND img_user = '5'
		  122 Query	UPDATE /* RenameuserSQL::rename Foo */  `oldimage` SET oi_user_text = 'Baz' WHERE oi_user_text = 'Bar' AND oi_user = '5'
		  122 Query	UPDATE /* RenameuserSQL::rename Foo */  `revision` SET rev_user_text = 'Baz' WHERE rev_user_text = 'Bar' AND rev_user = '5'
		  122 Query	UPDATE /* RenameuserSQL::rename Foo */  `archive` SET ar_user_text = 'Baz' WHERE ar_user_text = 'Bar' AND ar_user = '5'
		  122 Query	UPDATE /* RenameuserSQL::rename Foo */  `logging` SET log_user_text = 'Baz' WHERE log_user_text = 'Bar' AND log_user = '5'
		  122 Query	UPDATE /* RenameuserSQL::rename Foo */  `recentchanges` SET rc_user_text = 'Baz' WHERE rc_user_text = 'Bar' AND rc_user = '5'
		  122 Query	UPDATE /* RenameuserSQL::rename Foo */  `user_system_gift` SET sg_user_name = 'Baz' WHERE sg_user_name = 'Bar' AND sg_user_id = '5'
		  122 Query	UPDATE /* RenameuserSQL::rename Foo */  `user_board` SET ub_user_name_from = 'Baz' WHERE ub_user_name_from = 'Bar' AND ub_user_id_from = '5'
		  122 Query	UPDATE /* RenameuserSQL::rename Foo */  `user_gift` SET ug_user_name_to = 'Baz' WHERE ug_user_name_to = 'Bar' AND ug_user_id_to = '5'
		  122 Query	UPDATE /* RenameuserSQL::rename Foo */  `gift` SET gift_creator_user_name = 'Baz' WHERE gift_creator_user_name = 'Bar' AND gift_creator_user_id = '5'
		  122 Query	UPDATE /* RenameuserSQL::rename Foo */  `user_relationship` SET r_user_name = 'Baz' WHERE r_user_name = 'Bar' AND r_user_id = '5'
		  122 Query	UPDATE /* RenameuserSQL::rename Foo */  `user_relationship_request` SET ur_user_name_from = 'Baz' WHERE ur_user_name_from = 'Bar' AND ur_user_id_from = '5'
		  122 Query	UPDATE /* RenameuserSQL::rename Foo */  `user_stats` SET stats_user_name = 'Baz' WHERE stats_user_name = 'Bar' AND stats_user_id = '5'
		  122 Query	UPDATE /* RenameuserSQL::rename Foo */  `user_system_messages` SET um_user_name = 'Baz' WHERE um_user_name = 'Bar' AND um_user_id = '5'
		  122 Query	COMMIT

Jack Phoenix _(Contact) 19:40, 11 February 2010 (UTC)

Signing up as a GSoC mentor

Hi there! I see your name on the list of possible mentors on Summer of Code 2010. Thanks! If you're still interested, be sure to also sign up at http://socghop.appspot.com/gsoc/mentor/request/google/gsoc2010/wikimedia . Official deadline for doing so is April 21 but we'll need you on the roster there beforehand in order for you to be part of the evaluation process. Thanks! RobLa 18:18, 1 April 2010 (UTC)

AbuseFilter actions

Hi Werdna,

I'm evaluating Extension:AbuseFilter for use on our internal wiki, and trying to learn how it all works. When configuring a filter, under Actions taken when matched, I see a Flag the edit in the abuse log checkbox, but it's disabled (greyed out) so I can't click on it to clear the checkbox, and I can't figure out how to enable it. Is there any way to enable this option so I can clear the checkbox and prevent posting a triggered event to the Abuse log?

Thanks for the great extension! Obliquemotion 18:13, 11 June 2010 (UTC)

All events will be posted to the abuse filter log. This is by design. Andrew Garrett 08:59, 13 June 2010 (UTC)

Thanks very much! Obliquemotion 20:15, 25 June 2010 (UTC)

You're welcome. Andrew Garrett 00:13, 26 June 2010 (UTC)

AbuseFilter blocks edit when two warnings trigger

One more question. I have two filters defined:

• Filter 1 ("orange"): article_namespace == 0 & "orange" in lcase(added_lines)
• Filter 2 ("green"): article_namespace == 0 & "green" in lcase(added_lines)

Both are configured ONLY to warn and tag. If I make an edit that triggers either independently (for example, add a line with the word "green" in it), AbuseFilter behaves as I expect (warns, then when I click Save a second time, it tags it in the edit history).

However, if I add lines that would trigger both filters, only filter #1 warning displays, and prevents the edit altogether. For example, here is the attempted two-line edit:

* The grass is green
* I love oranges

When I click Save, the filter 1 warning displays above the edit box, and the log shows:

• 15:12, June 25, 2010: Obliquemotion (Talk | contribs | block) triggered filter 1, performing the action "edit" on Sandbox 2. Actions taken: Warn; Filter description: orange (details) (examine)
• 15:12, June 25, 2010: Obliquemotion (Talk | contribs | block) triggered filter 2, performing the action "edit" on Sandbox 2. Actions taken: tag; Filter description: green (details) (examine)

Then, if I click Save again (to override), I get the filter 1 warning again, and the log shows:

• 15:12, June 25, 2010: Obliquemotion (Talk | contribs | block) triggered filter 1, performing the action "edit" on Sandbox 2. Actions taken: Warn; Filter description: orange (details) (examine)
• 15:12, June 25, 2010: Obliquemotion (Talk | contribs | block) triggered filter 2, performing the action "edit" on Sandbox 2. Actions taken: tag; Filter description: green (details) (examine)
• 15:12, June 25, 2010: Obliquemotion (Talk | contribs | block) triggered filter 1, performing the action "edit" on Sandbox 2. Actions taken: Warn; Filter description: orange (details) (examine)
• 15:12, June 25, 2010: Obliquemotion (Talk | contribs | block) triggered filter 2, performing the action "edit" on Sandbox 2. Actions taken: tag; Filter description: green (details) (examine)

It seems like each time I click Save AbuseFilter adds the same two log entries, but prevents the edit (even though I didn't enable the Prevent the user from performing the action in question checkbox on either filter.

1. Can you please explain this behavior? Is it a bug, or have I misconfigured something?
2. Do the filters run in the order of their filter IDs (e.g. filter #1 runs before #2), and if so, how do I resequence them?

BTW, I'm running the 1.15.x snapshot of the extension on a 1.15 MediaWiki server.

Thanks very much for your patience. Obliquemotion 20:52, 25 June 2010 (UTC)

I've fixed this bug now. Andrew Garrett 21:45, 28 June 2010 (UTC)

LiquidThreads for Czech Wikipedia

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Hi Andrew,

at the Czech Wikipedia we are thinking about enabling LT for selected pages. Is Czech translation ready or can I help somehow? How do I ask for LT to be enabled? Should I file a bug? Kozuch 12:01, 31 July 2010 (UTC)

Yes, you should file a bug. I'm not sure what the deal is with translation, I'll have to ask somebody from translatewiki. Andrew Garrett 12:42, 31 July 2010 (UTC)

The translation is ready, but a bug in namespaces hinders the installation. Can you fix it or does the chunk of code you pasted in comment of that bug make that work with some special wiki-setting? Kozuch 14:00, 31 July 2010 (UTC)

The namespace translation is fixed now. You should post a bug with your preferred translations. Andrew Garrett 05:25, 20 August 2010 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

AbuseFilter and moved text

Hi Werdna,

could you please have a look at w:hu:Speciális:Vandálszűrő/20? My purpose was to filter when somebody puts a NOEDITSECTION (or one of its Hungarian translations) on a page in namespaces 0 to 1 (this works well) OR moves a page that contains NOEDITSECTION into these namespaces. But this does not work. First I tried with new_wikitext, then corrected to old_wikitext, but none of them works. Perhaps a pure "wikitext" would be necessary when the text stays unchanged, but there isn't any. Bináris 20:27, 16 March 2011 (UTC)

can you explain what this extension does?

can you explain what this extension does a little more on the page: http://www.mediawiki.org/wiki/Extension:DeleteQueue

Thanks. Igottheconch 20:28, 14 July 2011 (UTC)

It does nothing, at the moment. It exists mostly as a record of a failed/abandoned attempt to implement the functionality in question. Andrew Garrett 20:30, 14 July 2011 (UTC)

thank you for your response. Igottheconch 18:36, 20 July 2011 (UTC)

nice thing about wikis is that someone could always pick up from where you left off. So it does have value. Igottheconch 18:38, 20 July 2011 (UTC)

global AbuseFilter?

Conceptually, is there scope to have a global abuse filter? XWiki we are seeing bots appearing and dropping accounts with one-time spam, and then move on. We can see it through a number of sites, it is not high intensity, but regularly there. At this moment, due to the nature of the bot and a simplicity to its account names we can minimise aspects where we see it, the problem is we won't see it all. Currently AbuseFilter does allow a means to identify accounts, though that is a wiki by wiki approach, so the obvious question is there the scope for global AbuseFilter, even in some limited format. Thanks. — billinghurst sDrewth 06:59, 19 February 2012 (UTC)

Yet Another LiquidThreads Request

Hello. I want to know if, by reaching community consensus and of course a bug report, there's a possibility to enable LQ in the Arabic Wikipedia, since there is no fixed date for the redesign, and the extension is already in use in the Hungarian Wikipedia but put on hold for the Chinese Wikipedia. Zack (talk) 16:23, 18 March 2012 (UTC)

Further deployments of LiquidThreads are indefinitely on hold because we don't have the resources to support it. Andrew Garrett (talk) 01:41, 19 March 2012 (UTC)

AbuseFilter questions

Hello. I've got two questions I couldn't find the answers to.

1. Is there a log about abusefilter imports where it is possible to find out when and where the filter was imported from?
2. If its possible to have one filter which does the same thing as two filters do, which is preferable computationally and for speed?

Thanks and regards. Siddhartha Ghai (talk) 17:31, 28 March 2012 (UTC)

Test subject

test content 216.38.130.168 19:57, 2 August 2012 (UTC)

AbuseFilter Request?

Is there any way AbuseFilter could instead prevent anonymous edits from showing up until an admin approves them? Much like how the AbuseFilter can "tag" bad edits, instead this system would make it so the edits are blocked until approved by someone? Taylor 18:47, 29 October 2012 (UTC)

AbuseFilter Extension page update Version by MW Version

Hi Andrew, just a suggestion for the AbuseFilter page. Make it a little clearer on what version to download for specific MW versions. I downloaded and used master with a 1.19 MW install. Everything seemed fine untill I went to delete a page created by a spammer and then it threw a Fatal Exception error:

Warning: Missing argument 5 for AbuseFilterHooks::onArticleDelete() in ...extensions/AbuseFilter/AbuseFilter.hooks.php on line 271
Notice: Undefined variable: status in ...extensions/AbuseFilter/AbuseFilter.hooks.php on line 282
Fatal error: Call to a member function merge() on a non-object in ...extensions/AbuseFilter/AbuseFilter.hooks.php on line 282

After going back, with some looking I found the head for the REL1_19 and downloaded it. Installed this version and AbuseFilter is now working, page deletions aren't throwing the Fatal Exception error. I think what is confusing, the Extension page shows MW 1.13+, but doesn't distinguish working versions for specific MW versions. Tags page is empty at git too.

Extension is really cool, thanks for making it! Take care-- Hutchy68 (talk) 15:47, 24 February 2013 (UTC)

Extension:GlobalBlocking

Hi could you make this Extension:GlobalBlocking extension available for global blocking of a user account please 90.218.199.164 17:32, 1 July 2013 (UTC)

Hi. I'm not a developer, can't do that. Best regards. LlamaAl (talk) 03:02, 4 July 2013 (UTC)

This was aimed at User:Werdna who is the developer of the extension 90.212.81.76 09:48, 12 October 2013 (UTC)

The standard way to do this is to use Special:CentralAuth to lock the account. Andrew Garrett (talk) 02:28, 14 October 2013 (UTC)

contributions 213.55.73.35

find serves my talk werdna-metawiki

  Nurhusien 213.55.73.35 22:35, 22 September 2013 (UTC)

LiquidThreads 3.0

Hi could you please restart the develemont of LiquidThreads 3.0 this please because since you last stop developing LiquidThreads 3.0 more resources have been avalible due to updates Mediawiki such as Mediawiki 1.20 and Mediawiki 1.21 and Mediawiki 1.22 so please restart the develemont 90.212.81.76 09:46, 12 October 2013 (UTC)

LiquidThreads will be replaced by Flow. There will be a migration path available. Andrew Garrett (talk) 02:27, 14 October 2013 (UTC)

Requests for comment/Configuration database

Hi, Requests for comment/Configuration database is being considered as one of the RFCs to be discussed at the RFC review on 2013-11-06 via IRC. You are receiving this notification because you edited or discussed this RFC. We hope to see you there. Qgil (talk) 00:31, 5 November 2013 (UTC)

bugzilla:58954

Hi. What do you think about this request? πr² (t • c) 02:51, 25 December 2013 (UTC)

int unsigned vs. bigint unsigned for primary keys

Hi Andrew, I notice that git blame abusefilter.tables.sql says that you made abuse_filter.af_user a bigint unsigned. Was that in anticipation that user.user_id might one day become a bigint unsigned? I recently filed bug 61111, "Change log_id, page_id, rc_id, rev_id, and user_id to bigint unsigned" to do just that. However, it will require dozens, if not hundreds, of changes to the core, since there are lines of code all over the place saying, e.g., $this->mId = intval( $this->mId ); Intval maxes out at 2147483647. Do you think it's a good idea to make this change? Thanks. Leucosticte (talk) 16:42, 9 February 2014 (UTC)

An important message about renaming users

Dear User talk:Werdna/An important message about renaming users,

I am cross-posting this message to many places to make sure everyone who is a Wikimedia Foundation project bureaucrat receives a copy. If you are a bureaucrat on more than one wiki, you will receive this message on each wiki where you are a bureaucrat.

As you may have seen, work to perform the Wikimedia cluster-wide single-user login finalisation (SUL finalisation) is taking place. This may potentially effect your work as a local bureaucrat, so please read this message carefully.

Why is this happening? As currently stated at the global rename policy, a global account is a name linked to a single user across all Wikimedia wikis, with local accounts unified into a global collection. Previously, the only way to rename a unified user was to individually rename every local account. This was an extremely difficult and time-consuming task, both for stewards and for the users who had to initiate discussions with local bureaucrats (who perform local renames to date) on every wiki with available bureaucrats. The process took a very long time, since it's difficult to coordinate crosswiki renames among the projects and bureaucrats involved in individual projects.

The SUL finalisation will be taking place in stages, and one of the first stages will be to turn off Special:RenameUser locally. This needs to be done as soon as possible, on advice and input from Stewards and engineers for the project, so that no more accounts that are unified globally are broken by a local rename to usurp the global account name. Once this is done, the process of global name unification can begin. The date that has been chosen to turn off local renaming and shift over to entirely global renaming is 15 September 2014, or three weeks time from now. In place of local renames is a new tool, hosted on Meta, that allows for global renames on all wikis where the name is not registered will be deployed.

Your help is greatly needed during this process and going forward in the future if, as a bureaucrat, renaming users is something that you do or have an interest in participating in. The Wikimedia Stewards have set up, and are in charge of, a new community usergroup on Meta in order to share knowledge and work together on renaming accounts globally, called Global renamers. Stewards are in the process of creating documentation to help global renamers to get used to and learn more about global accounts and tools and Meta in general as well as the application format. As transparency is a valuable thing in our movement, the Stewards would like to have at least a brief public application period. If you are an experienced renamer as a local bureaucrat, the process of becoming a part of this group could take as little as 24 hours to complete. You, as a bureaucrat, should be able to apply for the global renamer right on Meta by the requests for global permissions page on 1 September, a week from now.

In the meantime please update your local page where users request renames to reflect this move to global renaming, and if there is a rename request and the user has edited more than one wiki with the name, please send them to the request page for a global rename.

Stewards greatly appreciate the trust local communities have in you and want to make this transition as easy as possible so that the two groups can start working together to ensure everyone has a unique login identity across Wikimedia projects. Completing this project will allow for long-desired universal tools like a global watchlist, global notifications and many, many more features to make work easier.

If you have any questions, comments or concerns about the SUL finalisation, read over the Help:Unified login page on Meta and leave a note on the talk page there, or on the talk page for global renamers. You can also contact me on my talk page on meta if you would like. I'm working as a bridge between Wikimedia Foundation Engineering and Product Development, Wikimedia Stewards, and you to assure that SUL finalisation goes as smoothly as possible; this is a community-driven process and I encourage you to work with the Stewards for our communities.

Thank you for your time. -- Keegan (WMF) talk 18:24, 25 August 2014 (UTC)

--This message was sent using MassMessage. Was there an error? Report it!

MediaWiki message delivery (talk) 18:24, 25 August 2014 (UTC)

Conversion of talkpages to structured discussions

There is a discussion on it here. Do you, as one of the developers of this extension have anything to say on it? Myrtonos (talk) 11:54, 24 January 2019 (UTC)

RfC

Hello. There is an RFC for the removal of inactive bureaucrats and interface administrators. As this might affect you, your input at the RfC is greatly appreciated. Minorax (talk) 04:03, 29 February 2020 (UTC)

Notice: Admin activity review

Hello Werdna,

I hope that this message finds you well.

I am writing to inform you that you may lose your adminship (and other advanced permissions) on mediawiki.org because of inactivity.

A policy regarding the removal of advanced permissions (e.g.: administrator, bureaucrat, interface-admin, etc.) was adopted by community consensus in 2013. While initially that policy did not apply to this site, the mediawiki.org community decided in August 2020 to opt-in.

You are being notified because we have identified that your account meets the inactivity criteria stated in the policy: no edits and no administrative log actions for the last 2 years.

• If you want to keep your advanced permissions, you should inform the community (at Project:Current issues) about the fact that the stewards have sent you this information about your inactivity. A community notice about this process has been also posted on said page. If the community has a discussion about it and then wants you to keep your advanced permissions, please contact the stewards at the stewards noticeboard, and link to the discussion of the local community, where they express their wish for you to continue to maintain your advanced permissions.
• If you wish to resign your advanced permissions, you may do so by filing a request for removal on Meta-Wiki.
• If there is no response at all on one month after this notification, the stewards will proceed to remove your advanced permissions without further notice.

In ambiguous cases, stewards will evaluate the responses and will refer a decision back to the local community for their comment and review.

If you have any questions, please let me know or feel free to message us at the stewards. If you feel we've made a mistake and your account is active, we'd also appreciate to let us know, and please accept our apologies.

Best regards,
--MarcoAurelio (talk) (via MassMessage) 22:13, 9 January 2021 (UTC)

MediaWiki message delivery (talk) 22:13, 9 January 2021 (UTC)

Hi, today your admin flag has been removed. Einsbor (talk) 11:08, 9 February 2021 (UTC)