User talk:Werdna/Flow

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)

Previous page history was archived for backup purposes at User talk:Werdna/LQT Archive 1 on 2015-06-03.

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?

Yes, you should file a bug. I'm not sure what the deal is with translation, I'll have to ask somebody from translatewiki.

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?

The namespace translation is fixed now. You should post a bug with your preferred translations.

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)

Hi, today your admin flag has been removed.

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.

There is a discussion on it here. Do you, as one of the developers of this extension have anything to say on it?

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.

Further deployments of LiquidThreads are indefinitely on hold because we don't have the resources to support it.

Hi could you make this Extension:GlobalBlocking extension available for global blocking of a user account please

Hi. I'm not a developer, can't do that. Best regards.

This was aimed at User:Werdna who is the developer of the extension

The standard way to do this is to use Special:CentralAuth to lock the account.

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!

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.

Hi. What do you think about this request?

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.