Remember this for whenever you begin a serious rework of infobox item. I know that I said the other day there were a couple things to discuss, and they're fresh in my head:

Multiple parameter values

Particularly:

default (stuff like quest) could maybe use a list template like {{plist|1|2|3}} to spit out a ul with all the items. Mainly to keep things consistent with how multiple values are handled

value/high/low; For these, I'm thinking a template that would be like {{Vallist|1|2|3}}, and the first 2 params would automatically add "coins" after them, the last one wouldn't (because it's added by the infobox).

Weights (AFAIK this is just for items that reduce weight when equipped); Thinking similar to above, it would be {{Ekg|1|2}}, and it would spit out like '''Equipped:''' -1{{kg}}<br>'''Inventory:''' 2 (remember "kg" is added by infobox)

Make "noalch" a single param instead of "high=no" and "low=no"

I know we discussed value as just 1 param, and maybe pulling it from exchange pages for some items (discussed with cook too); we won't forget it, but might as well bring it up

None of this is important now, but I just wanted it to be somewhere because it's fresh in my head. You might see this message being edited a couple times if some things pop into my head that I forgot. MolMan 13:19, February 21, 2015 (UTC)

IP doing several attempts with bad random numbers then getting a legit looking one through

Because of this, I'd really like to keep the CVU page, just as an easy way to see what gets blocked. I don't really want to have to check the abuse log after every charm log edit when it's much easier to see that they've done several bad edits already without even leaving recent changes

A point for random discussion would be removing /Charm log pages. If we put all the numbers in the summary (e.g. Script submission: 100K 30Go/2Gr/20Cr/0Bl; /* Possible vandalism */), we may have no use for subpages if everything can be merged.

It might even be of benefit to have a project page that tracks *all* charm log edits; i dunno

Would you check over/code review User:Gaz Lloyd/rev.js? I'd like to get an it imported in common.js eventually. I'm not super familiar with JS best practices, or what we want on the wiki in terms of JS structure, so let me know if there's anything that needs changing, major or minor. You can test and see documentation on User:Gaz Lloyd/Sandbox 3 (though currently missing the implementation section). Between the docs and the liberal comments, you should be able to understand what's going on, but let me know if you need something explained.

I'm away until ~late UTC on Sunday, so I probably won't respond until then if you have any issues with understanding it or whatever.

At some point I'll probably get a YG thread up for feedback/rubber stamping too.

I took the close hover icon from , since it was closer to the size of the ability tab things. The extras one looks best like this (in comparison to current and extras centered), but I still think it looks a bit weird. Probably should still go with it though.

I assumed there isn't a mediawiki/wikia/simple method to convert imagename.png -> full URL needed for src; if there is, that'd be better (since the ability images aren't thumbnails).

I don't think our coverage of the data used is that great (particularly of minimum/average hits). Doesn't necessarily matter too much.

The last I heard from Jagex on adding CORS headers was the initial reply just before RuneFest, that it was being forwarded to the web team, so I imagine it fell through the cracks and might be worth pursuing again. Between college and a catpocalypse (cats multiply) I've been too busy to work on the calculators. That said, for my final project in Java I am writing a RS calculator, so I hope to use that experience for better wiki calculators. Have you had any luck with getting RSHiscores updated or is CORS the only feasible option going forward? - TehKittyCatTalkWikian-Book 21:36, March 28, 2015 (UTC)

RSHiscores is a kluge, so hopefully bringing up CORS at the meeting works out and we won't need to pursue it any further. Awesome news, hopefully the meeting works out. The meeting does sound like a good opportunity for bringing up CORS headers. The change is simple on their part, makes hiscores support much easier on our part and benefits all the fansites calculator-wise going foward by removing the need for the server-side hiscores lookups on the fansites, because even Flash requires a CORS-like mechanism now. - TehKittyCatTalkWikian-Book 22:23, March 28, 2015 (UTC)

I'm just letting you know that sometime after Sunday 5 April, 2015, we will have a meeting over Skype with Mod Matthe and the Community Team about our future relationship.

“

I was about to email you on a similar matter though – we are excited about the greater flexibility this change gives us with regards to how we work together. As part of this therefore we’re really keen to chat to yourselves about how we can better support you and work with your team much more closely.

”

— Mod Matthe

What I'd like to do first is have a meeting over IRC, Chat, or Skype about what we want out of this. During the meeting with Jagex, I'd want to explore what Jagex wants and what problems exist. Sincerely, RyanPM 10:40, March 30, 2015 (UTC)