User talk:GhostAvatar14130



MediaWiki:Noscript.css
Nothing in the vain of "it doesn't work"; the main reason I've not used it so far is that I consider using the .client-js/.client-nojs CSS classes to be superior. As of MW 1.18, these classes are dynamically assigned to the html element depending on whether JS can be executed or not - and since that happens before the document is fully loaded, they can be used to get rid of popup effects just as well. My common.css has some rules for common scripts/pages which I've been testing.

The reason why I think the classes are superior is that MediaWwiki:Noscript.css is likely only loaded if the client has JS turned off in the browser preferences - I don't think it covers e.g. the use of script blockers (with script blockers, JS is enabled as far as the browser is concerned). The classes should not rely on the browser setting - if a script blocker prevents site JS from being executed, the .client-nojs class should be assigned as expected. In addition, using the classes allows us to keep all the CSS in the usual places instead of adding yet another MW page to check/maintain when working with CSS.

Finally, for UI elements (like the action buttons) there is another complication which affects both the use of the classes and Noscript.css: On certain pages (like Special:Preferences), MW loads only the MW core JS but not any custom site JS - and at the same time assigns the classes (or loads Noscript.css) solely based on whether JS is enabled for the client in general. Probably sounds a bit complicated, so here's an example: Let's say we use CSS to initially hide the action buttons for clients which have JS enabled. The button script then unhides the buttons after the button text has been modified (to get rid of the popup effect). On those "core-JS-only" pages (like the preferences) this would mean that the buttons become inaccessible; the "hide initially" CSS would be applied since the client has JS enabled, but MW doesn't load our custom button script which unhides them. Unfortunately it doesn't seem like there's some class or other indicator assigned to "core-JS-only" pages, and I'm not sure whether I've found all of them yet; so far I know of Special:Preferences, Special:UserLogin and Special:UserLogout.

Anyhow, these are my (lengthy) thoughts regarding the whole noscript CSS thing :P -- Porter21 (talk) 17:32, 6 June 2012 (UTC)


 * Interesting. I had assumed they'd simply use  tags for loading Noscript.css; seems like the most obvious approach even though those tags are deprecated as of HTML5. In any case I find using the classes more handy, but it seems we're in agreement there anyway. -- Porter21 (talk) 05:29, 15 June 2012 (UTC)

Wikilogs
Yeah, there are a couple of things we'll need to try and tackle with JS, AbuseFilter and/or namespace access restrictions. I hadn't noticed the comments thing yet, but the same applies to the blogs themselves - even anons can edit them. There are also issues with comments when moving/deleting blogs, for example. I suppose we should collect a list of issues and then try to work out how to solve them.

Don't think it's possible to properly disable the anon pseudonyms, but I suppose we could hide the input field via CSS - if no pseudonym can be entered, only the IP should be displayed. The "signature being left behind" thing seems like a proper bug - I don't see an immediate way to get rid of them either.

And yeah, I didn't have the time to work on the blog/comment CSS a whole lot before I had to leave. I'll take a look at your formatting changes :) -- Porter21 (talk) 05:31, 15 June 2012 (UTC)


 * Regarding the persistent signatures, if you set up the styling slightly different it's possible to have the outer container be "invisible" when only the signature is present (see my personal CSS for the modifications - needs some little tweaks but demonstrates the principle). I can't think of a way to properly address the bug, so I guess sweeping it under the carpet is the best we can hope for at this point.


 * For the comment editing restrictions AbuseFilter is probably a better option than JS - every kind of JS-based access restriction is inherently flawed since it can be circumvented by disabling JS. Your suggestion seems like a good solution to me.


 * As far as disabling anon commenting is concerned, I'm not opposed to it; it might result in a somewhat increased level of maturity for the comments. On the other hand, I believe Wikia's reasoning for allowing anon comments (roughly "so people do not get the wrong impression they need an account to edit the wiki") does have some merit, so I think we should get some community input if we want to take this route. From my point of view, the alternatives are:
 * A slight variation of your suggestion:
 * For anons with JS disabled, disallow commenting (by hiding the pseudonym and comment boxes and displaying a message explaining that they either need to log in or have JS enabled).
 * For anons with JS enabled, hide only the pseudonym box and automatically fill in their IP "behind the scenes" via JS when they press the "submit" button.
 * Enable anon comment moderation. Comment/post moderation doesn't work so well in my experience, but maybe we'll have more luck here.
 * Do not display the entered pseudonym. If we simply alter we can set the anon sigs to whatever we like. Might confuse people having to enter a pseudonym which is not displayed anywhere though.
 * There might be other alternatives, but I'll need some time to look into this more extensively. -- Porter21 (talk) 18:52, 16 June 2012 (UTC)


 * Sorry, I had a rather busy week and didn't have time to reply sooner. It should certainly be possible to further improve the "only edit own comments" mechanic with JS - we can have JS add a class ("wl-comment-mycomment" or something) to a user's "own" comments and display/hide the edit button based on that (with exceptions for sysops and anons, of course). I'll look into it when I get the chance.


 * As for the bug with blocked users - I'm suspecting that might be caused by the anon comment moderation functionality, so I think we should test whether this bug also applies to blocked registered users or only to anons. I don't really see a way to circumvent this deficiency via "inbuilt" means right now, at least not for anons (for registered users,we might be able to work something out based on $wgAutopromote). Considering all the complications, maybe we should start a discussion about simply disabling anon commenting after all. To alleviate the "do not give wrong impression" problem we could explicitly state in the "you must be logged in" message that this restriction only applies to blog comments ("While you do not need an account to contribute to other parts of the wiki..."). -- Porter21 (talk) 08:00, 24 June 2012 (UTC)


 * I've added the CSS/JS which should hide the "edit" button for a given comment unless one of the following is true:
 * It's the user's own comment.
 * The user is a sysop.
 * The user has JS disabled.
 * -- Porter21 (talk) 09:48, 24 June 2012 (UTC)


 * Blocked registered users can post comments as well. I guess Wikilog's comment functionality completely circumvents the usual blocking mechanic. -- Porter21 (talk) 16:42, 25 June 2012 (UTC)


 * Well, short of getting the bug fixed I don't see a real alternative to disabling anon commenting altogether. Blocked registered users we could place (automatically) in a special user group via $wgAutoPromote and then block that user group from editing/creating pages in the "Blog talk" namespace via access permissions, but that doesn't work for anons since they naturally have no user groups. -- Porter21 (talk) 05:20, 4 July 2012 (UTC)


 * That's not good. I'll need some time to think about possible solutions; unfortunately, patching up the extension is above my paygrade in PHP. Maybe we should try contacting the author, ask whether he's still updating the extension and see whether we can get it fixed that way? -- Porter21 (talk) 08:30, 7 July 2012 (UTC)


 * Might also be worth it to report the bugs at http://code.google.com/p/mediawiki-wikilog/issues/list - what do you think? That aside, I'd at least give him a week or so to notice the talk page post, otherwise it might indeed seem a little pushy in my opinion. -- Porter21 (talk) 23:05, 9 July 2012 (UTC)

Regarding flagged edit to "The Pitt bugs"
From our conversation on my talk page, I got the impression that you guys have logs of blocked edits (earlier I just assumed that such edits were discarded outright). If this is the case, would you mind helping me out with article The Pitt bugs? I redid the page a bit, and I found some good sources to cite, but since I'm new, the filter was flagging the links I was putting in REF tags. For the moment, I've submitted the edit sans links; when you find the time, would you be able to re-add the links for me? DavidJCobb 00:49, 20 June 2012 (UTC)

"No need"
Why isn't that quote needed? Its a spacific advertising slogan.--Ant2242 01:53, 23 June 2012 (UTC)

Autumn (Senior) /Senior
In regards to the Darkwaters should we add the Autumns as well? The only reference to him I could find is on the page now.--Ant2242 04:11, 30 June 2012 (UTC)

Abuse filter 11 (new user/anon adding external link)
Do you think we could risk testing whether that filter is still needed with the Asirra captcha? -- Porter21 (talk) 05:25, 4 July 2012 (UTC)


 * I know anon edits do not trigger a captcha, but for non-admins edits adding external links should trigger it (and they do, just tested it). Regarding the other thing, I don't think you can choose the type of captcha on a "per-trigger" basis, as far as I can see you can only choose one globally. -- Porter21 (talk) 08:25, 7 July 2012 (UTC)


 * Well, I'll agree that Asirra is not the most professional-looking captcha I've seen, but as you've said one can't really argue its effectiveness. I couldn't quite gather what your opinion on disabling filter 11 is (maybe I'm just tired), so - disable it for a while and see whether its role can be filled by Asirra? -- Porter21 (talk) 23:25, 9 July 2012 (UTC)


 * See, that's what I was asking again - I was suspecting we were not quite on the same page regarding the current captcha setup ;) What I meant to say in my message from the 7th is that, with the current settings, the captcha is triggered when an anon adds an external link to a page. I tested this by disabling the filter temporarily and logging out; when I tried to add an external link to a page, the captcha was triggered.


 * Let me quote the relevant part of the extension's documentation, maybe that'll make things clearer:


 * Basically we're talking about the "addurl" case here, and that's set to "true" already. I.e. with the current setup, the exact circumstances triggering filter 11 would also trigger the captcha if the filter was disabled.


 * I'd agree with you regarding the IE bug if we were really going to enable the captcha for all anon edits. However, if we simply disable filter 11 and let the captcha handle that specific case (which is what I was suggesting), I don't think we need to wait for the IE bug to be fixed (if that's going to happen at all...). Basically we'd go from "anons cannot add external links" to "anons using IE cannot add external links, all other anons can if they pass the captcha". -- Porter21 (talk) 07:25, 15 July 2012 (UTC)

Character images
Feel free to crop them if you feel it is better. A compromise would be asking Porter to use his wiki magic and make the images automatically crop themselves (like it works in Template:Map zoomed) in character infoboxes, allowing us to use just one character image, instead of several). My primarily concern is over location images: do you approve? Tagaziel 11:32, 9 July 2012 (UTC)

Spliting
Articles like Yakuza or Oregon's cannibals should be split into 2 yep? --Languorous_Maiar 14:28, 10 July 2012 (UTC)

Shady Sands
"The layout" Mariposa layout also is diffrent, maybe not like SS/NCR but still. "inhabitants" Mariposa inhibitants also are diffrent. Shady Sands have Tandi from FO1. "loot, quests, etc. are all different (along with the name)." Too same, but still, mariposa is in 1 article. Also, while name is diffrent, in F:NV soldiers and people from NCR still refer to Shady Sands under that name, not NCR like that was in Fallout 2. (thats why I changed your last edition in Shady Sands article) "(based on the game they are playing)" Not really imho, just redirect NCR (town) to Shady Sands and it will be ok. Now it makes more problems, because NCR (town) is total blank. For now, how it helps more towards new people, than if they were together? --Languorous_Maiar 17:49, 10 July 2012 (UTC)
 * Your argument about Hoover Dam makes no sense. Shady Sands are from FO1/FO2, and they are canon locations, and in both games it's exactly the same location. Hoover Dam from Van Buren is total non-canon. About readers, it's funny you recall them, because now Vault have only writers (with a few exceptions of course), this wiki can't be even find by using google, every guest looking for the Fallout wiki will found ugly Nukapedia, unfortunately. About question, no, but still, both artciles can be merged and give us the same ammount of informations if they were separate. And as I said before, it's exactly the same location... --Languorous_Maiar 19:35, 13 July 2012 (UTC)
 * But the idea and continuity of ​​history is diffrent in Hoover Dam in F:NV and in that one in VB. History of Hoover Dam from VB isn't in any way continued in F:NV. (The exception are Chinese spies, but it's smal reference and it's pre-war action, that have occurred regardless of the game.) Story of Shady Sands is developed and continued, what is most important when it comes to comparing these two examples. Also, New Canaan story and all arc can be (not must ofc.) continued in F:NV. And if we linked both stories, there is no contradiction between them, like beetwen Hoover Dam from VB and F:NV. Arcade arc from VB/F:NV contradict themselves, so they are not together.
 * For each section there is distinction for Fallout 1 text and Fallout 2 text. How this can confuse the reader, if it is clearly written that one part is about Shady Sands in Fallout 2, not 1 for example. If NCR (town) will be completed, still, there will be only more informations in merged article, nothing more. --Languorous_Maiar 20:29, 13 July 2012 (UTC)
 * But every thing, which is separated due to game informations etc. have common artice. For example, Minigun. There is a direct link to Fallout/Fallout 2 article, Fallout 3 article and Fallout: New Vegas article. Shady Sands and NCR (town) do not have a common article. --Languorous_Maiar 13:15, 19 July 2012 (UTC)

Yes and I know there was overview article for SS/NCR in Nukapedia, deleted at some point. If only background and appearances will be given, ideally. I always want to see in article that mighty town from F:NV era, not from location from F1/F2 if u know what I mean. You can also write your own opinion in Forum:Old Fallouts Segments? Each admin at the end ingored that thread, while I really want to clean up these empty or with repeated informations pages. Admin approval is really needed. ;p --Languorous_Maiar 18:02, 28 July 2012 (UTC)

Infobox location
Any particular reason for this change? Not sure why the image columns need to be configurable on a per-page-basis for this particular infobox (it's not for any of the others), and even if they do, one image per column seems to be a more sensible default than 2 to me seeing as most images in location infoboxes tend to have landscape orientation. -- Porter21 (talk) 16:57, 14 July 2012 (UTC)


 * Ok, I've changed the default to 1. -- Porter21 (talk) 07:25, 15 July 2012 (UTC)

Harmful changes
2 times when I wanna do some changes, Wiki prevent me from this. First was giving a rank to Gregory, second, deleting layout from Vault 43 (we can't write anything about that). Did something went wrong here? --Languorous_Maiar 19:18, 15 July 2012 (UTC)
 * Thanks. --Languorous_Maiar 19:45, 15 July 2012 (UTC)

Terminal edit screen
I've turned the terminal edit screen thingie you guys were discussing into a gadget. I've combined the two images you were using into one for the gadget version for better cross-browser compatibility; just a heads-up that you can delete File:Image.png and File:Gterminal.png if you no longer need them :)

By the way, please let me know if the gadget doesn't work right for you; I removed the font-size you had in your version because it was causing the text to be too large in non-FF browsers for me (without font-size it's fine in all browsers), but somehow I'm suspecting you had it in there for a reason... -- Porter21 (talk) 09:56, 17 July 2012 (UTC)

FO1/2 Character project
The Vault:Fallout 1 and 2 characters project, can u clear that place of Tagaziel failed links? Also, for now there is more inactive participants. Thanks. --Languorous_Maiar 13:48, 19 July 2012 (UTC)

JSawer Item packs
Is there any place in particular these items spawn? I don't own a PC version to cheak this out. If so then should we add pictures as well?--Ant2242 20:39, 22 July 2012 (UTC)

Bots
How are you, Ghost? I am Aleroth Sarenford, Founder and Admin of\on many wiki, Clyde and Denis, recently told me that you are the best bet for me to contact about how to get my own bot, i would be very thankful if you can help, Thanks for setting aside the time. --37.238.239.246 20:55, 24 July 2012 (UTC)

Dialogue Project
By using GECK. Search for the desired character, expand the window of character and then expand his dialogue. On the left is "ExportDialogue". --Languorous_Maiar 18:14, 10 August 2012 (UTC)

Wikia Mishaps
Hi GhostAvatar, I understand you are a Admin on The Fallout Wikia so to save a problem I plan to 'paste' the problem on this. I say this in the most less attitude way I can but I prefer to solve this problem with you instead of Scarface who initiated the ban. Hopefully we can come to some understand and move on from it.

Talkpage: NukaFlickers - Title: Recent Mishaps --- "I would like to start things off by saying I live with my cousin who shares the same laptop as me. So it comes to no surprise, he shares my Fallout game with me as well, also enjoying this very Wikia. Recently, Andrew (my cousin) used my Wikia account 'MattoSnap' and caused a verbal argument with a Moderator. Though the Moderator 'may' have taken it out of proportion and kicked Andrew; Andrew did react quite badly. Once he was banned he created a New Account 'NukaFlicker' to cause havoc on the Wikia. Though Andrew has given me the password to this account, which I am now going to use (though I don't like the name), I have still been banned from making a new account, speaking on the chat for something like 10 days, and editing pages. I apologize to Scarface for my cousin, though you probably think 'Andrew' doing this is a load of Bull' and unrealistic, I would beg to differ. Thank you.

Scarface11235- Making separate accounts to avoid bans is not allowed by Wikia policy, so this account is banned for 9001 years. Wait until the ban on MattoSnap is over please. Hugs "Say 'ello to my little friend!"

NukaFlicker- Scarface11235, I just explained that I hadn't even been involved with my cousin's mishap for whatever reason, yet this account just got blocked when I was trying to explain it wasn't even my mishap. Can we let it all pass and allow me to move through this and use the Wikia for what it was made for; communicating, community and editing, etc.

ScarFace11235- It's your responsibility, and yours alone, to control your account. If you happen to let a person on it who fucks everything up for you, that's too bad. Liken the situation to a child vandalising - or committing any crime for that matter -, it's the responsibility of the parent(s)'s. Your account is your child in the sense that you have full responsibility of your account, so if someone breaks rules on it, the account is penalised accordingly. Good night, hugs "Say 'ello to my little friend!"

NukaFlicker- I understand what you are saying, however, I have taken post-responsibility over this account today. Thanks to my cousin I have had to use this fake account instead of the other. I'm asking that you give me a chance to take responsibility another time as my password has been changed accordingly to the event that took place. Please, lift the block which disables me to use basically none of the wiki, and let me move on as well as you, or if this doesn't matter to you then the 'you' isn't relevant. Please consider it, unless you can appoint another to help me fix this situation"

I hope we can be mature about this, Thank you.