GuildWiki

GuildWiki has been locked down: anonymous editing and account creation are disabled. Current registered users are unaffected. Leave any comments on the Community Portal.

READ MORE

GuildWiki
Advertisement

"removing unneeded checks"[]

I disagree with the regexp being an unnecessary check. As the original requester for the exception, and the first draft writer of this script, I recognize the possible room in bias for my points of views. Verbatim tags are restricted to the MW namespace for a reason, and I believe that is to ensure that the Admins take responsibility for all usage of verbatim, no matter who added it where. If a vandal can add it to any random content page and violate TOS, then the admins have responsibility in its usage. One way such responsibility can manifest is the loss of our requested exception privilege. The scripts in MW namespace need to ensure other people cannot abuse verbatim tags to load scripts that violates the Wikia TOS. Thus I believe we need to embed into the script itself a check to ensure it is under a subpage of Main Page, before the rest of it alters the appearance of the page.

As for the Oasis check, I also think it's a better idea to have that, but this issue is one of programming practices and matter a lot less to me. -User:PanSola (talk to the Follower of Lyssa) 19:06, November 10, 2010 (UTC)

I know you want the regexp check to protect you. I think that we can protect you and the wiki the way we usually do (e.g. against vandalism), and that the name of the message and the changed page appearance will alert RC patrol that something strange is going on when it's not a mainpage preview. The benefit to removing this check is that the mainpage drafts can be e.g. in user space, and that the script won't break if we rename the mainpage (it's often renamed to the name of the wiki).
For the skin check, it would protect a handful of of monobook users from two DOM accesses, while removing that check removes a string comparison for everyone else and makes the code easier to read. --◄mendel► 21:09, November 10, 2010 (UTC)
The original request did not extend exception to pages in the user space. If individual users want to experiment, they are welcome to create Main Page/editcopy2, Main Page/editcopy3, Main Page/editcopy/PanSola etc. And if desired, we should request explicit permission for the use of the script in user space (the script can easily be modified to check for being a subpage of main page OR in userspace). Renaming of the main page is a major enough event that if it happens the cost of having to modify the regexp is insignificant. I argue the benefit provided by the removal of the check is not worth the potential of losing the exceptional permission should it become abused. -User:PanSola (talk to the Follower of Lyssa) 21:31, November 10, 2010 (UTC)
Flexibility concedes to caution. Put it back, then. (It sucks that we have to be afraid of our Wikihost that much.) --◄mendel► 22:22, November 10, 2010 (UTC)
It does suck, and reflects partly of the new perception between the wikis and Wikia. Anyways, if you think users would appreciate being able to do Main Page previews on their own subpages, the check in the script is easy to modify to increase flexibility. I just want to first get explicit and specific official permission when it comes to exceptions to TOS violations. They gave us some degree of trust when permitting an exception to us, I want to be very careful with that trust. (alternately, users can install the sub-script into their own user js, and ask anyone who previews to also add the sub-script) -User:PanSola (talk to the Follower of Lyssa) 22:47, November 10, 2010 (UTC)

OASIS!!!![]

This is the kind of thing why I am very very reluctant to fix anything in this skin: it's horribly badly designed. Why would there be two different triggers to make the page wide? On a skin that Wikia designed from the ground up? This skin is fated to go the way of Monaco, it already has more bugs than Monaco did, acquires more fixes than Monaco did, and I predict it won't be two years until it's as unmaintainable as Monaco was, so any effort that goes into it is going to be very much short-lived. Grrrrrr. That's why I initially advocated to rather work around Oasis than try to fix it - if you start doing that, it won't stop. (Proof: see memory alpha). --◄mendel► 08:37, November 11, 2010 (UTC)

Advertisement