Forum:Exchange page protection
For reference: Forum:New bot and protection for Exchange namespace, Forum:Restore manual update of Exchange prices, Forum:Allow users to edit Exchange namespace, Forum:Exchange namespace guidelines, Forum:GED not updating 1, Forum:GED not updating 2.
As it stand, TyBot updates each exchange page with the most up to date price, aquired through Jagex's API (simplistically, a series of pages on Jagex site that gives us info on items for those who don't understand the term). However, this isn't completely foolproof. TyBot can go offline (luckily we have backups for this), it can malfunction, or the source of the prices can develop bugs. When the latter happens the prices stay the same, and with thousands of prices to update we start to lose the edge on our competition.
When everything is working fine I have no problem with the namespace being semi-protected. It allows our users to update prices when they feel the bot is lagging behind, and for those that aren't so necessary TyBot will eventually get there. However, when this fails we need to move as quickly as possible to keep our prices up to date. Emailing Wikia staff to get the protection removed isn't the fastest process in the world, even more so if bugs occur on Friday and the member of staff who replies requests clarification. It could take 4-5 days for something as simple as a quick edit to a few lines of code.
Far more flexible are abusefilters. Granted, they may require a little more work: we'd likely want to remove the edit/save buttons and add a notice of explanation when everything is working fine, but for when things break we can react that much faster.
To make it a little easier for the less technically-minded sysops to alter things, I'd like to keep things simple. Use the abusefilter to prevent non-autoconfirmed users from editing the namespace which can be turned on/off without having to edit the filter. Any extra actions required when the namespace is not protected can be taken to another filter which can be activated as required.
Tl;dr Move the Exchange namespace protection to abusefilters.
Support - I can't think of any downsides to doing this. Hide the edit button on Exchange: pages (preferably in MW) as well. If it's not possible to restrict it to non-autoconfirmed users, just do it for everyone. ⁓ Hello71 21:26, October 20, 2013 (UTC)
Support - Because this year alone, the official Jagex GE database has failed 3 times: April, July, and recently two weeks ago. Each downtime was roughly 5-7 days. So it would be helpful if users can edit the Exchange pages as soon as possible whenever a downtime is detected at Jagex.
p.s. If this passes, additional instructions at RS:EXCHANGE would be helpful. 01:41, October 22, 2013 (UTC)
Moo - It'd be cool if we could have the freedom to protect this specific namespace as a whole as we please. After all, we are important enough. Until then, we're better off with ABF. MolMan 13:46, October 22, 2013 (UTC)
- I don't think that will ever happen though, :( 02:17, October 23, 2013 (UTC)
- It probably requires access to our LocalSettings.php which is definitely never going to happen. It contains passwords to a load of servers and there's no chance anyone that isn't staff is going to see that. cqm 08:38, 23 Oct 2013 (UTC) (UTC)
- More likely, it requires access to WikiFactory, which staff aren't going to give us access too. 12:31, October 23, 2013 (UTC)
- I know it's never going to happen. Shut up and let me dream. MolMan 12:33, October 23, 2013 (UTC)
- Let's go. 02:03, November 2, 2013 (UTC)
Closed - The abusefilter has been enabled. Wikia has been contacted to remove the protection on the Exchange namespace. The instructions on RS:EXCHANGE will also be updated to reflect these changes. cqm 10:52, 2 Nov 2013 (UTC) (UTC)