Team Fortress Wiki talk:Technical requests
- 1 Jeff
- 2 EmbedVideo
- 3 Update to MediaWiki version 1.16.0
- 4 Move?
- 5 Moved requests off the page
- 6 Extra file formats
- 7 Auto-Translate?
- 8 Not sure if this belongs here, but it's worth pointing out.
- 9 Sharp Dresser Weapons Demonstration is marked as Private on YouTube.
- 10 Special:RandomPage
- 11 Semantic MediaWiki
- 12 Enabling search autocomplete
- 13 SearchLog extension
- 14 Update the Autoconfirmed user group
- 15 Update MediaWiki to 1.20.5
- 16 Anti-spam stuff
- 17 GeeQuBox
- 18 Flood flag
- 19 RevQuery
- 20 thank
- 21 Spell Check?
- 22 Beep boop
- 23 Formatting Extension for Mobile Devices
- 24 Auto add "update trans" template
- 25 Fix the "spy sapping my wiki" easter egg
Is there any way that we can make Special:RandomPage not redirect to subpages? Obviously the primary language of the wiki is English, and there's really no point presenting the majority of people with a Russian page who then might click again to get a German page. -- Pilk (talk) 09:45, 21 August 2010 (UTC)
- WindPower has created an extension for use. It's quite brilliant! He's made it so that if you're on an English page, then random page returns only English pages, if you on a localized page then it will only return pages of the same language. Pretty fancy! -- Smashman... (t • 10:37, 22 August 2010 (UTC)
- Source to WindPower's extenstion. – Smashman (talk) 20:24, 29 August 2010 (UTC)
- The extension requires the SpecialRandomGetRandomTitle hook that was added in 1.16.0. I have successfully installed it on the Alien Swarm Wiki, which also runs on 1.15.4, by simply overwriting 1.15.4's SpecialRandompage.php with the version from 1.16.0, and it seems to work fine. So either an upgrade to 1.16.0 or simply overwriting this file would work. Thanks~ — Wind 20:27, 29 August 2010 (UTC)
- Source to WindPower's extenstion. – Smashman (talk) 20:24, 29 August 2010 (UTC)
- Comment Given the age of this request I think WindPower should make the decision here; I tested the extension, but it only stuck to English pages because I couldn't enable the /wiki/$1 url-shortening on my test wiki; if it can be tweaked to apply on index.php?title=$1 as well as /wiki/$1 then I'm okay with it. -RJ 20:58, 13 May 2013 (PDT)
The SMW framework would be extremely useful for this wiki. There is a lot of data on the wiki that can be collated or filtered as lists, making a lot of manual categorization unnecessary. —Moussekateer·talk 04:34, 12 May 2013 (PDT)
- Support though SMW confuses my head. -RJ 20:58, 13 May 2013 (PDT)
I think one easy change would be installing AbuseFilter; You can write regex filters to block based on a user's age, number of links in an edit, etc.
A second extension that might be useful is SpamBlacklist. WMF has a huge list of sites globally blocked on their sites, and it tends to be pretty useful.
Nuke lets admins mass-delete pages, making cleanup a bit easier.
SimpleAntiSpam just adds a form in the signup page that users don't see, but blocks registration if a bot were to add text to it. 
One change that doesn't require an extension is to add something like this bit of code in LocalSettings.php: [snip] $wgAutoConfirmAge = 86400*5; //Set autoconfirmed age to 5 days... $wgAutoConfirmCount = 5; //...and 5 edits $wgGroupPermissions['user']['createpage'] = false; //Don't allow new users to create pages $wgGroupPermissions['autoconfirmed']['createpage'] = true; //Allow autoconfirmed users create pages $wgGroupPermissions['user']['upload'] = false; //Don't allow new users to upload $wgGroupPermissions['autoconfirmed']['upload'] = true; //Allow autoconfirmed users upload files [/snip]
I'm not a MediaWiki expert... But I've run quite a few wikis that have been spammed a lot worse than this, and mitigated it to the point where we got almost no spam anymore. Pilif12p 15:49, 13 May 2013 (PDT)
- Only way this will happen is if Valve actually does it. But knowing valve. They will take forever. So Good luck with this. Ashes 16:47, 13 May 2013 (PDT)
- We have server access now Ashes; right now we're figuring out our workflow before we implement anything, but things should clean up soon. -RJ 16:54, 13 May 2013 (PDT)
- Splitting each proposition in to its own discussion section: -RJ 20:58, 13 May 2013 (PDT)
- Oppose We have AbuseFilters on the Dota 2 Wiki, but it's a lot of effort to set up, and (with the Dota 2 WIki set up) there are often false positives which can easily go unnoticed unless the Abuse logs are constantly being reviewed; I'm opposed to abuse filters right now, but if other efforts to counter spam aren't successful I'd reconsider this opinion. -RJ 20:58, 13 May 2013 (PDT)
- Wikipedia has a lot of their filters public, and in production. You can just copy the regex from there and set the same options, then you shouldn't have too many false positives. This is a pretty good example. It's not like you have to enable any filters if you do install it, though. Pilif12p 14:54, 14 May 2013 (PDT)
- Support -RJ 20:58, 13 May 2013 (PDT)
- Support Worth having in case of any mass-edit attack / vandalism, though spambots we face right now just do a single edit and disappear, so it's not necessary for spam handling. -RJ 20:58, 13 May 2013 (PDT)
- Support Sounds simple, I think it's worth trying. -RJ 20:58, 13 May 2013 (PDT)
- Comment Worth discussing. It seems we did have AutoConfirmAge and AutoConfirmCount set to what you proposed, but they were later reduced to lower values for some reason. I think these permissions may be too aggressive right now, and the spambots we're facing are waiting to be autoconfirmed before they hit anyway - so these changes might not have any impact. -RJ 20:58, 13 May 2013 (PDT)
- Turns out I'm wrong with the above statement, spambots are editing with only "user" permissions, so it's certainly worth discussing if we should limit users aggressively until they're autoconfirmed. -RJ 10:57, 14 May 2013 (PDT)
- Comment Recommended by Bsadowski1, it seems pretty powerful with what we can do with it. —Moussekateer·talk 18:34, 31 May 2013 (PDT)
Instead of having people fill up RC with the same repetitive changes, why not have them use alternate "flooder" accounts with the flood flag? They won't show up in RC, nor flood IRC... I don't remember the exact right you have to add to LocalSettings, but I'm sure somebody else does. Pilif12p (talk) 07:52, 4 June 2013 (PDT)
Could any possible misspelled word be underlined with a red line? I find it difficult to use auto correct on my iPad, as it could auto change words spelled rihgt (and it has) and the arrangment pf the keyboard make me hit the wrong keys frequently. Please add? ScottishDrunkard (talk) 12:04, 27 December 2014 (PST)
I am a robot. -RJ 07:41, 23 March 2019 (UTC)
Formatting Extension for Mobile Devices
Currently, viewing information on the wiki via a mobile device is rather clunky. Implementing some form of solution to this, such as the MobileFrontend extension used by Wikipedia would be very helpful in making information more accessible to users. I'm not sure how this would impact wiki formatting, but if it could properly implemented it would definitely be of huge benefit to the wiki InfernalShroom (Talk) 20:54, 25 April 2020 (UTC)
Auto add "update trans" template
I find few translators have the habit of updating their works. And I have told Chinese regulars to use Watchlist well for updating, however, it seems most of them won't listen.
Let me stress the importance of updating translation here: English pages, or should I say, orginal pages may be updated by anyone at anytime, and the translation sub pages won't update themselves. For those translators who work here frequently, maintaining the timeliness of translated pages is as important as creating new ones.
I have been thinking about this for 2 days, although it's possible to track the newest versions by using Watchlist (while many translators have yet to do so), searching for other pages which need updating could be very time consuming. We already have "update trans" template for this, but it's a fact that many outdated pages haven't been marked for it.
So, my request is whether if we can have a bot to add "update trans" template automatically based on difference between the last editing dates of the original pages and the translation pages, which would make it eaiser to find outdated translation pages? The difference could be set to half a year or other value.
I know that this change will spam our Wiki, but as long as it can attract translators' attention to updating, it will be worthy.
Dereko, a TF Wiki translator 07:24, 3 May 2020 (UTC)
- Starg and I worked on a project that had a similar idea. It's not maintained anymore, but it shouldn't be hard to get it working again.
- Here's the pages: Weapons, Taunts. — Tark lm(pt-br) 11:22, 4 August 2020 (UTC)
Fix the "spy sapping my wiki" easter egg
I'm having a problem with TF2 Wiki on Android, Chrome browser v. 84.0. The 'spy sappin muh wiki' easter egg shows up too often and is too easy to trigger unintentionally, which causes severe confusion and unwanted sound effects.
I believe the problem is within the JS code which triggers the effect. It seems to detect the swipes and taps combination not only when it is produced in continuous succession, but generally when I do all the actions in the right order, possibly alternating them with other gestures.
Moreover, after the easter egg is triggered once, every single tap on the page will trigger it again, until I reload the page.