User talk:P858snake

About this board

How we will see unregistered users

MediaWiki message delivery (talkcontribs)


You get this message because you are an admin on a Wikimedia wiki.

When someone edits a Wikimedia wiki without being logged in today, we show their IP address. As you may already know, we will not be able to do this in the future. This is a decision by the Wikimedia Foundation Legal department, because norms and regulations for privacy online have changed.

Instead of the IP we will show a masked identity. You as an admin will still be able to access the IP. There will also be a new user right for those who need to see the full IPs of unregistered users to fight vandalism, harassment and spam without being admins. Patrollers will also see part of the IP even without this user right. We are also working on better tools to help.

If you have not seen it before, you can read more on Meta. If you want to make sure you don’t miss technical changes on the Wikimedia wikis, you can subscribe to the weekly technical newsletter.

We have two suggested ways this identity could work. We would appreciate your feedback on which way you think would work best for you and your wiki, now and in the future. You can let us know on the talk page. You can write in your language. The suggestions were posted in October and we will decide after 17 January.

Thank you. /Johan (WMF)

18:17, 4 January 2022 (UTC)

Reply to "How we will see unregistered users" (talkcontribs)

Hi can you please remove protection from MediaWiki 1.17 this please. Because I doint think it needs to be protected any more nor do I think it is high Visable due to it no longer being supported. And it is not the latest Mediawiki version so please remove protection from it thanks.

Reply to "Remove protection from MediaWiki 1.17"
DannyS712 (talkcontribs)
Reply to "Inactive bot account"
Ans (talkcontribs)

Why does Extension:Inline SVG not solve security issues by do the same security checks as did in uploaded SVG files?

Reply to "Extension:Inline SVG"
P858snake (talkcontribs)


Noticed, that you have deleted my extension. The security risk with the extension is intentional! The extension is intentionally made to reveal user's email, so it is not possible to remove the security risk without rendering the extension pointless... Some wikis were using the extension and they need the (possibly updated) extension code to be available in order to restore their installations.

Hope to hear from you very soon as people are waiting! -- Joosep-Georg

This post was posted by Peachey88, but signed as Joosep-Georg.

P858snake (talkcontribs)

Restored, I would also highly recommended getting the extension stored in our git repository if people actually have a desire to use it.

Joosep-Georg (talkcontribs)

Thanks! Have also made a request now for git access as you suggested.

Reply to "Extension:RevealEmail"
P858snake (talkcontribs)

I also don't like LQT very much.

This post was posted by Peachey88, but signed as Legoktm.

Reply to "I'm just testing stuff."
P858snake (talkcontribs)
Reply to "Some WikiLove for you!"
Qgil-WMF (talkcontribs)

Hi, about a month ago I spent a bunch of hours sorting out the Git/Gerrit in order to declare this bug fixed. One of the things I proposed and nobody opposed was to get rid of the Git and Gerrit template. If you have good reasons to bring it back please discuss at Template talk:Git and Gerrit. Otherwise it would be great if you could revert your changes. I didn't delete just because I thought it would be ok to leave some time until the pages still using it could clean it up, but maybe it will be good to remove it altogether to avoid confusion and extra work. Thank you!

This post was posted by Qgil-WMF, but signed as Qgil.

P858snake (talkcontribs)

1. Having a logical template (which has the same links as the Gerrit page) personally seems to be a-lot more logical then having a large context-less gerrit logo (Which in most cases linked to the Gerrit page, Although at least once linked Externally to the Gerrit interface) and personally I would view that as helping resolve #36437.

2. Almost all of the terms on that template are directly linked from the Gerrit page anyway and most of those are or will be useful to those that want to look at and learn about Gerrit.

Reply to "Git and Gerrit template"
Peachey88 (Flood) (talkcontribs)

(Moving from email to talk page where it should have gone) Hey; can I ask you to not turn on any more LiquidThreads instances on the talkpages relating to the new Article Feedback Tool and the Zoom interface - and, if possible, to turn the existing ones off? We're trying to get a lot more community members to participate, and many aren't comfortable with LQT, meaning there is another hoop for them to jump through before they get involved.


O.K./Ironholds Community Liason, Product Development Wikimedia Foundation

This post was posted by Peachey88 (Flood), but signed as Ironholds.

P858snake (talkcontribs)
  • I have a talk page where this should have gone in the first place (which is where I've now moved it)
  • Consensus (or what we class as consensus for this wiki in the irc channel) for this wiki seems to be we went it used where possible unless utterly broken
  • If they aren't comfortable posting in LQT, They most likely wouldn't be in a non LQT page, I can easily tell what Talk:Article feedback would be like without it and that would be even scarier, and that is hardly a loop for them to get involved, because in most cases it's even easier.
    • I also know some of the new users that have posted to Talk:Article feedback and they wouldn't have gotten involved if LQT wasn't involved, Which is one of the exact hurdles that LQT is designed to overcome when it comes to editing talkpages because of the mess and wall of text they become in the edit window.
  • But if you want to disable it, feel free but it will be up to whoever disables it to copy and paste every one of the comments over to the talk page.
Reply to "LiquidThreads"


Choshi (talkcontribs)
P858snake (talkcontribs)
Warning: This extension assumes that only the revisions and archives tables use our text storage. If any extension you have installed makes use of our text storage on its own then this extension will purge all content that is being used by that extension and break it.

Is what was posted on the page.

Reply to "Extension:SpecialDeleteOldRevisions2"