Thread:Karuberu/@comment-195370-20180225140318/@comment-195370-20180226202003


 * 1) lst in Nov 2011 and #dpl in Feb 2012 as part of 1.18 and 1.19 respectively? In a list of a hundred other extensions, I wouldn't even have known what I was looking at let alone where to find them and what they could do. I got there backwards by having a design in mind, then trying to find out how I could make it possible!

I thought the same about processing cost - as the #dpl call is 'targeted' and not crawling the entire 50k articles of the wiki (like my previous effort at SeeAlso), it should have no deeper impact than a single pageload server-side at most for each.

I noticed, though I'm not sure what/how it works, that on the Tooltip there's an 'ajax' option that ensures tooltips are only loaded on mouseover, not on pageload. Could that go someway to mitigating server impact? Each Item Image is average about 75KB though.

I was wondering was how much, since Mediawiki came about and these extensions were designed, the real effect of costly code such as this has, both on the end user and on Wikia's servers.

Considering the former, I know I often run two MMOs, TV streaming, remote desktop, two video streams, browser/app use on 2-6 devices and Discord all concurrently without my minimum-spec broadband batting an eyelid. I'll find a couple of larger 'summary' pages and place the templates in them to see if there's any slowdown.

Considering the latter, I'd be surprised if in the six years since they rolled it out, Wikia haven't upgraded their own hardware substantially (especially with the FANDOM redesign and the tendency to spread other sites' materials around); I also think that as one of the lesser-visited sites and what with their objective to actively encourage every user to set up a Fandom wiki to any tiny aspect of popular culture, we should accept that they can handle anything we throw at them until the day they send us an e-mail about it! :)

Apologies for not looking at this in Monobook (or Mobile for that matter). I shall endeavour to see if there's a way to grant it slightly more appeal, though cross-format display is something I've yet to even start to look at past my initial fumblings to have tables represented better on Red Mage - I've certainly not delved into the css of it.

Last - I chose 'I' and 'In' simply because, if used, it would be used a lot, and that's less keystrokes and screen space for editors! I have no problem with renaming it, if that's your preference.