User talk:Peachey88
- [History↑]
Contents
| Thread title | Replies | Last modified |
|---|---|---|
| Old username discussion issue | 0 | 09:33, 8 June 2013 |
| Some WikiLove for you! | 0 | 23:11, 31 March 2013 |
| Git and Gerrit template | 1 | 05:50, 31 March 2013 |
| Woa, why all the deleted pages? | 5 | 20:18, 19 May 2012 |
| Don't block me indefinitely | 3 | 05:40, 11 April 2012 |
| Creating an abuse filter | 0 | 03:49, 7 April 2012 |
| HTFFanBrandon04 | 5 | 20:30, 3 April 2012 |
| Template:Extension code in wiki | 0 | 20:56, 21 February 2012 |
| Template:GithubDownload | 2 | 09:59, 9 February 2012 |
| Merry Christmas and Happy New Year | 0 | 10:45, 26 December 2011 |
| User:Baru Addar | 0 | 04:45, 26 November 2011 |
| Template:Unmaintained extension | 0 | 18:05, 1 November 2011 |
| LiquidThreads | 1 | 07:41, 22 October 2011 |
| Change in Common.css | 1 | 08:46, 21 October 2011 |
| Block on User:Suze | 1 | 04:12, 28 September 2011 |
| Upcoming developers' meetups | 0 | 21:38, 13 September 2011 |
| One More | 0 | 04:09, 1 June 2011 |
| Protecting your talkpage | 4 | 09:26, 31 December 2010 |
| redirects | 0 | 09:10, 31 December 2010 |
| CSRF != XSS | 0 | 09:09, 31 December 2010 |
 First page |
 Previous page |
 Next page |
 Last page |
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.
 |
Some WikiLove for you! |
| :> —Emufarmers(T|C) 23:07, 31 March 2013 (UTC) |
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!
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.
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.
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.
The end-user should have to do nothing in a default setup to avoid it.
So, if the default setup includes making it "administrator-only" in LocalSettings.php, that should do it?
Which extension are you talking about? I can check out its settings (since I'm an admin).
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.
If you just listen to me consistently, you can reduce your chances of that.
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.
and now it's been found that he's engaged in massive cross-wiki socking.
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.
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.
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.
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.
User is unblocked.
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.
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)
Hi Peachey88, the Git link needs to be corrected since it is not longer working. Thank you and cheers
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/)
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).
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
(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
- 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.
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.
- /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)
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 :-)
Hi! Just wanted to let you know about two upcoming events that you might be interested in:
best, Sumana Harihareswara Sumanah 21:38, 13 September 2011 (UTC) Volunteer Development Coordinator Wikimedia Foundation
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?
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).
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.
First page |
Previous page |
Next page |
Last page |
