P858snake

Protecting your talkpage

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.

---

Since you have set your talkpage with liquid thread, do you think you should protect the talkpage header? A question about the wikitext; explain the {{#useliqiudtherads:1}} tag, or is there a page explaining it? Myrtonos^{Posting in liquid thead} 13:13, 30 December 2010 (UTC)

A. No, no point unless it gets repeatedly vandalism, which I or someone else will deal with, when and if it happens.

B. {{#useliqiudtherads:1}} is designed to call it on pages when LQT isn't forced to be activate in that area (which we don't here on mw wiki). Peachey88 23:52, 30 December 2010 (UTC)

But are any non-admins even supposed to edit the header. It seems to me that if no one is supposed to edit it, it should be protected, I have never understood the thinking otherwise. Myrtonos^{Try liquid theads} 08:42, 31 December 2010 (UTC)

Yes, we aren't very restrictive on this wiki, it's basically anything goes but vandalism and spam which we deal with if and when it happens. Peachey88 09:11, 31 December 2010 (UTC)

As for the {{#useliqiudtherads:1}}, what is that number after the colon? Myrtonos^{Posting in a liquid thread} 09:26, 31 December 2010 (UTC)

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

Block

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.

---

This post by Peachey88 was moved on 2010-12-31. You can find it at Thread:User talk:Peachey88/Block. Peachey88 09:09, 31 December 2010 (UTC)

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

OnWikimedia

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.

---

This post by Peachey88 was moved on 2010-12-31. You can find it at Thread:User talk:Peachey88/OnWikimedia. Peachey88 09:09, 31 December 2010 (UTC)

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

thank you

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.

---

This post by Peachey88 was moved on 2010-12-31. You can find it at Thread:User talk:Peachey88/thank you. Peachey88 09:09, 31 December 2010 (UTC)

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

CSRF != XSS

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.

---

This post by Peachey88 was moved on 2010-12-31. You can find it at Thread:User talk:Peachey88/CSRF != XSS. Peachey88 09:09, 31 December 2010 (UTC)

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

redirects

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.

---

This post by Peachey88 was moved on 2010-12-31. You can find it at Thread:User talk:Peachey88/redirects. Peachey88 09:10, 31 December 2010 (UTC)

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

One More

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.

---

Hello, Peachey. Maybe you want to delete this page too. I could not sent it to deletion. Regards.” T_eleS (T _{M @ C G}) 00:54, 9 April 2011 (UTC)

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

Upcoming developers' meetups

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! Just wanted to let you know about two upcoming events that you might be interested in:

Brighton Hackathon 2011

NOLA Hackathon

best, Sumana Harihareswara Sumanah 21:38, 13 September 2011 (UTC) Volunteer Development Coordinator Wikimedia Foundation Sumanah 21:38, 13 September 2011 (UTC)

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

Block on User:Suze

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.

---

Thanks for fixing the block - I see that you had to unblock and then reblock to change the setting. I'll try to remember that for next time :-) Ajraddatz 04:10, 28 September 2011 (UTC)

Yeah it's broken at the moment, I've filed a bug and its been fixed up in trunk so I have to make sure to remember get that tagged to be deployed. Peachey88 04:12, 28 September 2011 (UTC)

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

Change in Common.css

Using an unprotected image is not such a good idea. You can use "/skins" instead of "/skins-1.18"; that always points to the latest branch. — Edokter (talk) — 12:59, 17 October 2011 (UTC)

• /skins/ is unreliable (and come out of date) when there are new versions released, since it doesn't automatically link to the latest version (someone has to remember to update the symlink when if a new version is released.
• Brion wants (or at least wanted) to apparently get rid of the /skins/ symlink
• The image is only used like ~5 here, but is widely used else where (commons:Special:GlobalUsage/Icon_External_Link.png) so it would detect it rather quickly and reverted
• And I don't like protecting things (eg: local upload over the commons version) unless it really needs it (for example, shows a history of vandalism) Peachey88 04:07, 21 October 2011 (UTC)

LiquidThreads

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.

---

(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.

Thanks

O.K./Ironholds Community Liason, Product Development Wikimedia Foundation Ironholds 07:28, 22 October 2011 (UTC)

• 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. Peachey88 07:40, 22 October 2011 (UTC)

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

Template:Unmaintained extension

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 Peachey88, I have merged this template with Template:Maintainer sought-after. I figured that there is no need for simimar ones. I just added a second category to the template. Cheers [[kgh]] 18:05, 1 November 2011 (UTC)

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

User:Baru Addar

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.

---

Mind blocking this dude? He is continually spamming.

Nevermind, seems you already have. en:LikeLakers2 (en:talk) 04:43, 26 November 2011 (UTC)

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

Merry Christmas and Happy New Year

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 Peachey88,

Hope that so day somewhere on earth we shall meet in the same friendly manner in which we have interacted online for in connection with image filter referendum vote . I am very pleased with your friendly and welcoming attitude. Hindustanilanguage 10:35, 26 December 2011 (UTC).

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

Template:GithubDownload

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 Peachey88, the Git link needs to be corrected since it is not longer working. Thank you and cheers [[kgh]] 17:21, 1 February 2012 (UTC)

If you are talking about the 404, No that is not broken, that is a git:// link for git clients, It just doesn't server anything for over the web viewing, If you look at a github page and select the "Git Read-Only" link, You will see that it is correct (eg: https://github.com/torvalds/linux/) Peachey88 03:47, 9 February 2012 (UTC)

That was the one. Ah, I see... Thank you for the information. Cheers [[kgh]] 09:59, 9 February 2012 (UTC)

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

Template:Extension code in wiki

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.

---

I notice you've templated me with {{Extension code in wiki }} on a few pages, the latest being extension:logotipo. Are there any criteria to determine which extensions are worth including in SVN? This one already overlaps existing SVN code at Extension:LogoFunctions so its inclusion may be a bit redundant - even though it is still in use and does still work. --Carlb (talk) 20:55, 21 February 2012 (UTC)

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

HTFFanBrandon04

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.

---

He apparently did not heed your final "not done" warning on his user rights request with this, which I reverted because this is supposed to be archived. It should at least be fully protected, and you may want to follow up on your warning to block him. Jasper Deng (talk) 19:48, 28 March 2012 (UTC)

Done I've blocked him for a little cooling off period. Although technically we don't have a real archival system for those pages so I prefer not to protect them, But I will if it becomes a problem after he gets unblocked. Peachey88 (talk) 20:39, 28 March 2012 (UTC)

OK, now I've made an unblock offer for him, but I still have concerns about his maturity. You may want to check as the blocking sysop. Jasper Deng (talk) 04:36, 1 April 2012 (UTC)

User is unblocked. Peachey88 (talk) 02:55, 3 April 2012 (UTC)

If I'm not sysopped by then, I'll tell you if he needs to be blocked again. Thanks for helping. I'll try my best. Keep him watched though. Jasper Deng (talk) 02:58, 3 April 2012 (UTC)

Thank you for unblocking me. HTFFanBrandon04 (talk) 20:30, 3 April 2012 (UTC)

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

Woa, why all the deleted pages?

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.

---

I use several of the extensions you just deleted!

The ones I use can be used without a security problem, and the existing commentary spelled that out fairly well, I thought.

Why the authoritarian approach, instead of the more typically WikiPedian "caveat emptor" approach?

--Bytesmiths (talk) 18:15, 4 April 2012 (UTC)

If they didn't have XSS security issues then they shouldn't have been tagged as such.

It was hardly a authoritarian approach, All those extensions were tagged from 2008-2010, that is ~5 yrs at the oldest ~3 at the newest where the developers (and/or other contributors) didn't bother to address security issues that can compromise your wiki and/or security accounts. Peachey88 (talk) 22:01, 4 April 2012 (UTC)

So let me see if I understand. Someone -- not you -- tagged them as having XSS vulnerability. Someone else -- me -- explained in the text how to avoid the XSS vulnerability on one of those page, but being a timid sort of person, neglected to remove the XSS tag, and then someone -- you -- apparently without testing nor reading the page, deleted them, solely because they had an XSS tag?

If that is indeed the case, I will restore the extension in question (data tables) and remove the XSS tag. It's a highly useful extension whose vulnerability is very simply avoided. Bytesmiths (talk) 17:11, 19 May 2012 (UTC)

The end-user should have to do nothing in a default setup to avoid it. Jasper Deng (talk) 17:19, 19 May 2012 (UTC)

So, if the default setup includes making it "administrator-only" in LocalSettings.php, that should do it? Bytesmiths (talk) 20:15, 19 May 2012 (UTC)

Which extension are you talking about? I can check out its settings (since I'm an admin). Jasper Deng (talk) 20:18, 19 May 2012 (UTC)

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

Creating an abuse filter

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.

---

I've blocked two "Diablo" accounts as socks of User:Diablo3897. I'm not good with regex, though, even if an abuse filter would be the best way to combat this user's socking. Jasper Deng (talk) 03:49, 7 April 2012 (UTC)

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

Don't block me indefinitely

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.

---

I have great potential to contribute to this project. I'm HTFFanBrandon04, the user you blocked. I have great potential to contribute to this project. HappyTreeFriends (my home page or talk 2 me) 07:43, 9 April 2012 (UTC)

If you just listen to me consistently, you can reduce your chances of that. Jasper Deng (talk) 18:29, 9 April 2012 (UTC)

Unfortunately for him he's now blocked indefinitely. I don't intend for it to be permanent, but I need to make it clear to him that he must take this website seriously. Jasper Deng (talk) 01:13, 11 April 2012 (UTC)

and now it's been found that he's engaged in massive cross-wiki socking. Jasper Deng (talk) 05:40, 11 April 2012 (UTC)

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

Old username discussion issue

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.

---

I asked for the page to be deleted since it wasn't necessary here. It was about a username issue since I was offended, but as another user pointed out, it's probably not obvious. I'll look into it and see if other people have complained before I bring it up again. Инкуиситор Саша Ехренстеин аус дем Стурмкриг Сектор (Talk) (Contributions) 05:55, 20 July 2012 (UTC)

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

Git and Gerrit template

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, 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! Qgil (talk) 04:22, 31 March 2013 (UTC)

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. Peachey88 (talk) 05:26, 31 March 2013 (UTC)

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

Some WikiLove for you!

	Some WikiLove for you!
	:> —Emufarmers(T|C) 23:07, 31 March 2013 (UTC)

Extension:SpecialDeleteOldRevisions2

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.

---

I've forgotten why Extension:SpecialDeleteOldRevisions2 had a security problem. Choshi (talk) 08:36, 10 July 2013 (UTC)

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. Peachey88 (talk) 09:22, 10 July 2013 (UTC)

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

Deleted photo

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. Without any discussion you have deleted photo. The point is that photo is taken from archive of museum, the author is unknown, and I don't know which license I must use. I plan to download other photoes of this man (I am writing an article about him), mostly they are from his family album and collection of the music school - the same question about license will appear. Please be so kind to give me an advise.

Deleted photo was here:

http://www.mediawiki.org/wiki/File:Surmillo_S._D..jpg

P.S. Do you know russian?

Ли Дзю Ли Дзю (talk) 05:17, 1 September 2013 (UTC)

Please read Project:About which was linked in the deletion reason, To help in your understanding of why it was. Peachey88 (talk) 10:21, 1 September 2013 (UTC)

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

Extension:RevealEmail

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!

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 Joosep-Georg (talk) 16:16, 8 September 2013 (UTC)
12:08, 9 September 2013 (UTC)

Restored, I would also highly recommended getting the extension stored in our git repository if people actually have a desire to use it. Peachey88 (talk) 03:49, 11 September 2013 (UTC)

Thanks! Have also made a request now for git access as you suggested. Joosep-Georg (talk) 20:45, 9 November 2014 (UTC)

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

I'm just testing stuff.

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.

---

I also don't like LQT very much. Legoktm (talk) 11:40, 9 September 2013 (UTC) 12:09, 9 September 2013 (UTC)

And LQT doesn't like you! Peachey88 (talk) 03:49, 11 September 2013 (UTC)

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

My user talk page

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.

---

Hello, just out of curiosity, what did it actually say on my talk page that you deleted? I only just got the email notification that it had been changed (I check my email every few hours or so). Would you mind undeleting it and maybe replacing it with a welcome message or something? That's what I would have done had I noticed the page, anyhow. I'm an ultra-inclusionist when it comes to things like that on Wikipedia, you see. :-) Graham87 (talk) 08:16, 11 September 2013 (UTC)

it was just "§''''''" by a IP user, feel free to create your talk page if you want, I highly recommend enabling LQT on it (with {{#useliquidthreads:1}}). Peachey88 (talk) 09:23, 11 September 2013 (UTC)

Alright, thanks. No big deal. I've just created my talk page as you advised. Graham87 (talk) 07:06, 13 September 2013 (UTC)

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

A kitten for you!

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.

---

This should use LQT!

Legoktm (talk) 07:20, 13 September 2013 (UTC)
Legoktm (talk) 07:20, 13 September 2013 (UTC)

The real question is whether it can work with Flow, which is LQT's supposed replacement. Jasper Deng (talk) 07:28, 13 September 2013 (UTC)

From what I read, Flow is that restricted that nothing will work with it!, Hope no one wants to discuss math formulas on talk pages! Peachey88 (talk) 07:45, 13 September 2013 (UTC)

Hm, I just realized that it added my signature twice. That's pretty silly. Another bug! Legoktm (talk) 03:50, 14 September 2013 (UTC)

~~~~ should never be necessary with LQT. Jasper Deng (talk) 17:38, 14 September 2013 (UTC)

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

Undeletion request

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.

---

Please undelete my unblock templates. Almost every other wikimedia wiki has the unblock template! 179.210.38.88 10:48, 21 November 2013 (UTC)

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

Extension:Gnuplot

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, I would like to know what was the security issues with the extension. Can you tell me what the problems was or where I can look for it? Thanks --Sigbert (talk) 15:13, 4 December 2013 (UTC)

I've done some digging, and it appears that it could allow arbitrary shell commands to be executed, such as "rm -rf".

It's a shame this got deleted instead of fixed. They did the same thing to the SQL2Wiki extension that I use extensively, in a safe manner. Why does "momma wiki" think we need protection from ourselves? Wasn't the stern warning at the top of these extensions enough? Jan Steinman (talk) 21:00, 6 February 2014 (UTC)

Because you would think people pay attention when there is a security warning, But like most extension repositories people don't.

If someone was wanting to fix it, They can (I will even un-delete or give them the code sources), But when they were deleted they had the warnings for 12+ months with no action on it. Peachey88 (talk) 09:39, 9 February 2014 (UTC)

Thanks for the info. Actually I'am not interested to access the code (except maybe for study purposes :), but I'am thinking about adding access to Gnuplot to my Extension:R. If it is just shell access via the tickmarks then I have similar problem in R and octave too. The solution there could be applied for Gnuplot as well. Sigbert (talk) 17:51, 30 April 2014 (UTC)

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

Remove protection from MediaWiki 1.17

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 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. 86.135.250.172 17:45, 5 April 2014 (UTC)

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

Extension:FileIndexer

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 Peachey88, some time ago you deleted the page for the Extension:FileIndexer and replaced it with a warning saying that the extension has security issues, and that users should use some other equivalent extension. However there is no equivalent extension (to my knowledge), and the security issues are not explained in the talk page, nor in bugzilla, so we developers have no idea how to solve them. Could you please explain them in the talk page, or open a bug report? Thanks. LFS (talk) 14:14, 16 November 2014 (UTC)

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

Extension:Inline SVG

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.

---

Why does Extension:Inline SVG not solve security issues by do the same security checks as did in uploaded SVG files? Ans (talk) 12:03, 16 December 2019 (UTC)

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

Inactive bot account

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. At Project:Requests/User rights/Removal of inactive bot rights (2) there is a proposal to remove the bot rights of inactive bots. Since you appear to be the operator of one of the bots in question, I wanted to draw your attention to the discussion. Please let us know if the rights are still needed (or if they aren't). Thanks, --DannyS712 (talk) 02:45, 29 July 2020 (UTC)

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

How we will see unregistered users

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!

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) MediaWiki message delivery (talk) 18:17, 4 January 2022 (UTC)

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

Account blocking

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.

---

When you blocked my second account, you used a hardblock. Could you change it to a softblock instead? I see no reason for disabling account creation. Thanks. – Ilovemydoodle2 (talk) 20:54, 26 July 2022 (UTC)

Also, could you make it more clear that it was done for technical reasons, not for any 'bad behavior'? – Ilovemydoodle2 (talk) 21:21, 26 July 2022 (UTC)

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

Re: CrystalBot tasks

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.

---

I would be sorry if such action broke some rule here, as I previously see this site not actually have a active page discussing bot tasks for approval. If some sort of discussion for the redirect-create task is need, I'm happy start another discussion in Project:Requests. Stang 22:35, 30 July 2022 (UTC)

Overall most un-contiverstional requests are fine, but essentially sliding it in after the main request in what sort of looks like a comment to someone's support was not the best way forward.

Also the previous request was over 11 years old, Some considerations should be made before blinding performing old requests to see if the needs have changed over time and if its still needed. (In this case, our search system as vastly improved) P858snake (talk) 23:21, 30 July 2022 (UTC)

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

Re: AdminBot actions

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.

---

Such removal of permission is followed by an old tradition, like there's quite a lot of such action in Special:Log/rights. Stang 22:37, 30 July 2022 (UTC)

Those are mostly additions which is separate from removal, Overall Patrolled Edits is from my understanding a mostly unused feature on this wiki, I have opened a RfC to gather larger thoughts around this feature.

(Side note, You didn't need to create new topics on my talk page, Responding on yours would have pinged me with the new talk page tool) P858snake (talk) 23:16, 30 July 2022 (UTC)

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

I no longer have access to my email address connected to my account and I forgot my password

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.

---

Could you please change my email address if I give all you all of the information 121.200.5.51 (talk) 06:03, 5 February 2023 (UTC)

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

Filter 95

Was this discussed somewhere? I'm not aware of another wiki that takes such a punitive approach - while GlobalUserPages is a thing yes, it's fairly common for some to still want to create their own local pages. Leaderboard (talk) 12:31, 13 July 2024 (UTC)

Yes, It was discussed with numerous other admins on IRC, If a user really wants a local user page they can ask a admin to create the page and then they can edit as desired, There has only been 1 or 2 requests for it since 2022. P858snake (talk) 15:02, 14 July 2024 (UTC)

Is there a log somewhere where I can look at this discussion?

This strikes as quite a wrong move though - it's kind of established practice that we allow users to create a local userpage if they want (and in fact, many do have their own userpages on other WMF wikis). I don't see why MediaWiki should be any different - having to ask admins sounds like a very strange thing to me. I thought it was a spam problem that led you to impose this move, which is why I suggested allowing people with some global history to create their page here. Leaderboard (talk) 15:23, 14 July 2024 (UTC)

(Coming from a request at Project:Village pump)

First off, these sorts of discussions should be held on-wiki rather than on IRC for transparency reasons. Second, I agree entirely with Leaderboard on the merits here - the reason we have an abuse filter here at all is to prevent spamming, and the rest is simply your opinion on how to manage the wiki which other people, including myself, do not share. * Pppery * _{it has begun} 15:24, 7 August 2024 (UTC)