Team Fortress Wiki talk:Technical requests

The following discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Jeff

Jeff should know this page exists now. -- Pilk _(talk) 21:33, 6 August 2010 (UTC)

The preceding discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

The following discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

EmbedVideo

I'm under the impression that we're already using this extension, but also, I believe Jeff said he won't upgrade to the latest version because it has security issues or something. We should look into this and find a better Extension. This one is quite annoying. -- Smashman... _{(t • s)} 23:33, 6 August 2010 (UTC)

The preceding discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

The following discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Update to MediaWiki version 1.16.0

Could we update to MediaWiki version 1.16.0, please? It contains a number of fixes and also, the new Vector skin which should help with usability. Thanks. -- Smashman... _{(t • s)} 10:43, 22 August 2010 (UTC)

Valve are most likely keeping to legacy releases at the moment (1.15.*). Vector would be cool, but I assume they have security and compatibility issues to keep in mind. seb26 [talk] 11:06, 22 August 2010 (UTC)

Why would they do that? 1.15.4 was the latest version when this wiki was released and if Wikipedia are using it, then it won't have security concerns. Believe me, Wikipedia are more likely to be worried about security, and if they're good with it, then it'll be more than secure enough for our requirements. -- Smashman... _{(t • s)} 11:31, 22 August 2010 (UTC)

That's what I think, but then again, we aren't running the server. There may be other reasons involved. seb26 [talk] 21:29, 22 August 2010 (UTC)

If you look at the patch-notes, the only changes we could really benefit from are a couple of new interface strings (such as ones that appear below talk page editnotices) and the Vector skin. This needs to be weighed up with the possible issues that could arise with the style sheets or other things, and the fact it would delay the other requests for real things like extensions because upgrading is not a simple process. -- Pilk _(talk) 11:28, 30 August 2010 (UTC)

I'm going to chime in here and also request that Valve is pressured into upgrading the wiki to the 1.16 branch, as I believe given the number of edits these days, that getting the "grouping" functionality of edits to the same page on the Recent Changes list, and in the Watchlists is almost essential at this stage. TheChrisD ^{Rants•Edits} 01:39, 25 January 2011 (UTC)

The preceding discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

The following discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Move?

Why, oh, why did you do that? I sent an email to Jeff YESTERDAY to take a look at these. Put them Goddamn back.  – Smashman _(talk) 10:13, 30 August 2010 (UTC)

Smashman seb doesn't need your attitude, seriously. If you want it back you should do it. Discussion on the usefulness of a particular request should be on the talk page itself though. Jeff shouldn't have to go through the discussion to determine what we came to the conclusion of. At the moment this upgrade is contentious anyway. It shouldn't be up til we agree on it. -- Pilk _(talk) 10:50, 30 August 2010 (UTC)

Well I can't do it, hence my asking to do it. I didn't wish it to be a discussion, it was meant to be a request, but seb decided to have a discussion. I do not see a reason why we wouldn't wish to upgrade. And the RandomPage thing was your request that Wind fulfilled and it merely needs an upload.  – Smashman _(talk) 11:02, 30 August 2010 (UTC)

I want 1.16 too, but it's unlikely to happen at all. It's clear that Valve are sticking to legacy releases, and that they have their own reasons for it, and are unlikely to listen to our opinions on it, regardless of how big a site Wikipedia is or whatever. And Wind's random page thing says it needs an updated .php file or something, so that seems even more unlikely to be done. seb26 [talk] 11:08, 30 August 2010 (UTC)

Making it a discussion was important. You do not see a reason why they wouldn't want to upgrade, but seb does and I do. Adding that extra touch of "goddamn" isn't fair or called for either. -- Pilk _(talk) 11:10, 30 August 2010 (UTC)

Well we might as well request on this page. Valve don't seem to be using legacy releases at all. The version we have here was the most current version at the time of our set up, so I don't see why they wouldn't update. Jeff was also telling me about the next update having the Vector skin, and this meaning that the current Valve skin will need fixing. This definately seems like he had updating in mind. Could we merely request it and see Jeff's opinion? Thanks.  – Smashman _(talk) 11:26, 30 August 2010 (UTC)

It's stuff like this that you shouldn't keep to yourself. -- Pilk _(talk) 11:31, 30 August 2010 (UTC)

Come on IRC / Steam more man, we could have avoided this whole thing lol seb26 [talk] 11:32, 30 August 2010 (UTC)

I'm for update :D I like updates -- Nightbox _{(t s)} 11:34, 30 August 2010 (UTC)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘ Believe me seb, I would if I could. Mobile IRC program anyone?  – Smashman _(talk) 11:37, 30 August 2010 (UTC)

On it. seb26 [talk] 11:42, 30 August 2010 (UTC)

The preceding discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

The following discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Moved requests off the page

Why did you remove requests of the page? I maybe understand why rejected requests were moved, but the accepted requests were here so Jeff/anyone can view them. Did Jeff acknowledge that he had these on his own todo list? -- Pilk _(talk) 20:04, 31 August 2010 (UTC)

I doubt Jeff would want to see them again. As he's already reviewed them. If he wants, he can click the tick at the top.  – Smashman _(talk) 21:20, 31 August 2010 (UTC)

But spread over seven pages? What's the point? You moved them because you think Jeff doesn't want to see them again? -- Pilk _(talk) 21:24, 31 August 2010 (UTC)

Well if he's going take a look at the page again, why would he want to see requests that he's already reviewed?  – Smashman _(talk) 21:42, 31 August 2010 (UTC)

But seven pages? Seriously? How is that better? -- Pilk _(talk) 02:36, 1 September 2010 (UTC)

The preceding discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

The following discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Extra file formats

SVG images won't happen. For starters, they have to be rendered into PNG by a separate plugin. It's not something the software can do by itself. When you consider the difficulty involved in getting a smaller extension added, and you couple that with the fact that there isn't anything special SVG images can do (that scaling down a high res PNG can't do), then it just won't happen. A video format is also out of the question too. Hosting video files means additional unnecessary bandwidth for Valve: why the bother when you can just use YouTube? As for .cfg files, I don't particularly understand. Not too long ago we deleted all of the class scripting pages, and one of the justifications was that "we shouldn't be competing with modding sites like fpsbanana". If we were to bring them back, then hosting .cfg files will only complicate maintenance further, as you must download the file to see what's in it (and none of the scripts we could host wouldn't be very long anyway).

As for the other file formats (mp3, ogg & compression formats), they seem like reasonable suggestions, I'll re-add them to the page. seb26 [talk] 20:19, 13 October 2010 (UTC)

SVG should be supported for scaling. SiPlus 07:31, 13 July 2011 (PDT)

The preceding discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

The following discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Auto-Translate?

Hi, there! Should a auto-translate (for all languages) be helpful? (Then with a added "help with translating" tag.) [] /shadow/sShaD'OhsS 11:30, 16 October 2010 (UTC)

By 'auto-translate', I hope you don't mean Google Translator. This was discussed at length somewhere else, but put simply, there isn't any way that a computer can translate into another language better than a native speaker can. seb26 [talk] 11:39, 16 October 2010 (UTC)

i agree with seb here i was myself going to do the auto translate (google translate) as a tester i translated somthing into swahili and back to eglish again and didnt get the right results --Iaindude 10:21, 17 November 2010 (UTC)

The preceding discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

The following discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Not sure if this belongs here, but it's worth pointing out.

So I'm not sure if this is my broswer's (Google Chrome) problem. When I zoom in on the page, the header is white, as normal. Although, when I zoom out, it glitches and turns to a dark grey. Any ideas? - MLGM 14:45, 17 May 2012 (PDT)

The preceding discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

The following discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Sharp Dresser Weapons Demonstration is marked as Private on YouTube.

• When you try to watch the demonstration, it comes up saying "This video is private." You need to fix that on the YouTube account.

The preceding discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Special:RandomPage

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 • s)} 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)

 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)

Semantic MediaWiki

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)

The following discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Enabling search autocomplete

This would be immensely useful and has the side effect of making a huge amount of redirects unnecessary. —Moussekateer·talk 04:34, 12 May 2013 (PDT)

 Comment MediaWiki 1.20+ contains search autocomplete by default, and that page says $wgEnableMWSuggest was broken pre 1.20 which makes me wary of it; I think we can skip this and wait until we upgrade. -RJ 20:58, 13 May 2013 (PDT)

The preceding discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

The following discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

SearchLog extension

If search autocomplete is not viable for whatever reason the SearchLog extension would be a useful tool. It generates a table of searches and their frequency. —Moussekateer·talk 04:34, 12 May 2013 (PDT)

 Oppose Sounds pretty slick, but I'm opposed as its beta and only lists support up to 1.17. -RJ 20:58, 13 May 2013 (PDT)

 Comment We now have autosuggest so this is unnecessary —Moussekateer·talk 05:49, 2 June 2013 (PDT)

The preceding discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

The following discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Update the Autoconfirmed user group

Remove the captcha for users with 10 (or whatever) or more edits in the mainspace. —Moussekateer·talk 04:34, 12 May 2013 (PDT)

 Support but we should wait for more input before changing. -RJ 20:58, 13 May 2013 (PDT)

This has actually always been present but wasn't working due to being put on the wrong line in the settings file. —Moussekateer·talk 10:50, 6 June 2013 (PDT)

The preceding discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

The following discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Update MediaWiki to 1.20.5

Critical bug fixes everywhere. —Moussekateer·talk 04:34, 12 May 2013 (PDT)

The preceding discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Anti-spam stuff

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. [4]

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)

AbuseFilters

 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)

SpamBlacklist

 Support -RJ 20:58, 13 May 2013 (PDT)

Nuke

 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)

SimpleAntiSpam

 Support Sounds simple, I think it's worth trying. -RJ 20:58, 13 May 2013 (PDT)

Permissions changes

 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)

Edit filter

 Comment Recommended by Bsadowski1, it seems pretty powerful with what we can do with it. —Moussekateer·talk 18:34, 31 May 2013 (PDT)

That would be abuse filter. Wikipedia just calls it "Edit Filter", same thing though. Pilif12p (talk) 09:47, 2 June 2013 (PDT)

The following discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

GeeQuBox

GeeQuBox displays gallery images in a pretty lightbox viewer. See example on the portal wiki. —Moussekateer·talk 05:49, 2 June 2013 (PDT)

After much testing I went with SlimboxThumbs instead. Is now installed. —Moussekateer·talk 17:20, 5 June 2013 (PDT)

The preceding discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Flood flag

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)

RevQuery

See here. Written by seb26 for our image caching issues. —Moussekateer·talk 11:26, 6 June 2013 (PDT)

thank

I like the feature in other wikis in the history view to thank editors for specific edits, and I would appreciate having that feature here, if possible. Mikado282 (talk) 19:47, 29 April 2014 (PDT)

Spell Check?

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)

Beep boop

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)

 Support I literally made the same request on the wiki talk page, not realizing it'd go better here. so uhh yeah, what he said. Kestrelguy (talk) 02:05, 29 September 2021 (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.

Ashpool (talk) 14:24, 1 August 2020 (UTC)

 Should be fixed. [1] — Tark lm(pt-br) 11:17, 4 August 2020 (UTC)

Taking requests for converting talk pages back to regular 'ol wikitext

Hi folks, I've switched off the flow talk page thing for new talk pages. Digging in, it doesn't appear there's an easy way to automatically convert existing talk pages that are using Flow back to regular wiki text. There is a maintenance script to give me the wikitext for a particular page, but it's a manual job to then delete the existing talk page and create a new one with that wiki text. That could be automated but as it involves deletions it'd end up being pretty risky, and hell to clean up if anything goes wrong. I'll spend some time thinking about whether that's worth exploring.

In the mean time, if there are any pages you'd like converting please drop them below. I'll check back regularly (Valve time) and work through them.

Ta, -RJ 15:20, 3 October 2020 (UTC)

I would say to backup the saved data from the current talk system, and restore it back to the regular text. Keep the saved info from the current system somewhere, so we don't lose something important. The current talk system has replaced a ton of talk pages and talk user pages with nothing. We thought it would be a good idea implement it, but it's full of bugs and made things even worse. - ▪ - 16:07, 3 October 2020 (UTC)

god please save my talk page -- Boba 17:35, 3 October 2020 (UTC)

Hope you are still around, please fix my talk page, thanks! --Alex┋T 03:31, 15 July 2021 (UTC)

Howdy! Could you please do something about mine? I wouldn't even mind it using the flow, just want for messages to display there (lol). foxbite ^{(talk) ⨯ (contribs)} 12:11, 12 June 2022 (UTC)

Mine too! Qwertyxp2000 (talk) 01:33, 22 June 2022 (UTC)

Pages such as the following should be changed: Talk:Cheater's Lament, Talk:Anti-Demoman strategy, Talk:Anti-Pyro strategy, Talk:Anti-Soldier strategy, Talk:Anti-Heavy strategy, Talk:Anti-Medic strategy, Talk:Anti-Engineer strategy, Talk:Anti-Sniper strategy, Talk:Anti-Spy strategy, Talk:Frenchman's Beret, Talk:ÜberCharge. I might list more later but here's a non-comprehensive list of some of the pages that should be changed into traditional talk page format. Qwertyxp2000 (talk) 00:28, 11 March 2023 (UTC)

Hey — here's another page! Talk:Customize items
Tiagoquix (talk) 17:35, 21 June 2023 (UTC)

Request: Talk:Soldier_voice_commands/zh-hans (Further requests will be added here).
Thanks.--BEUFK - Contributions-Talk 12:00, 26 June 2023 (UTC)

Talk:Power Up Canteen also needs it Jh34ghu43gu (talk) 11:50, 13 November 2023 (UTC)

I concur with this, when it comes to wiki stuff as a veteran editor on the main Wikipedia, classic generally better.-- Akolyth (talk) 02:49, 3 August 2023 (UTC)

Another one! Talk:Description Tag. Thanks in advance.
Tiagoquix (talk) 18:01, 27 November 2023 (UTC)

Take that! Talk:Voting.
Tiagoquix (talk) 16:04, 29 February 2024 (UTC)

I have a list of potential pages, if that helps . Although there are other requests on the main page that deserve more attention Mgpt (talk) 17:33, 29 February 2024 (UTC)

Configuring Extension:ParserFunctions

Extension:ParserFunctions is an already super useful extension. It can be made even more useful by configuring it to set $wgPFEnableStringFunctions to true. This would allow the extension to also utilize many of the features of Extension:StringFunctions with a quick configuration change. ~ Boba 20:39, 23 July 2021 (UTC)

+1  Wookipan (talk | contribs) 00:23, 24 July 2021 (UTC)

+1 — Tark 18:03, 8 March 2022 (UTC)

"Random page" button sends you to pages with different languages

So I've recently discovered that the button that says "Random page" will take you to not just a random page on this wiki, but a random page written in a different language as well. If this isn't intentional, can someone please fix it so that it will take you to a random page in the same language as the page you're currently on? GoodMudkip (talk) 17:04, 13 September 2021 (UTC)GoodMudkip

Unfortunately, it's not possible to fix this issue. — Tark lm(pt-br) 17:13, 13 September 2021 (UTC)

I mean, this issue shouldn't really be too hard to circumnavigate. If a page you randomly go to isn't English, then you can clink on a small link just below the page's title, which will bring you to the original, English version of that page.

Lolimsogreat21 (talk) 17:26, 13 September 2021 (UTC)Lolimsogreat21

Tooltip template on mobile devices

We uses a lot of {{tooltip}} in this Wiki, but you can't see the text on phones and tablets without a mouse. I see there's this thing that could maybe solve this? Or is there other ways to let you tap on the text and show the tooltip? --Alex┋T 15:03, 26 August 2021 (UTC)

Make this wiki's theme dark by default

I'm tired of being blinded by flashbangs using this wiki.
The Dark Reader extension does not work properly (ugly colors and breaks some elements), and the suggestion of the MediaWiki's Dark Mode extension for this wiki has been rejected.
I think the best thing then would be to make the TF Wiki dark by default, just like Discord and Steam are. White could be an option, but not the default option. Tiagoquix (talk) 23:00, 27 September 2022 (UTC)

I think a compromise maybe fitting with the TF aesthetic would a sepia/beige-yellow-orangeish theme?-- Akolyth (talk) 02:56, 3 August 2023 (UTC)

Twinkle

See Team_Fortress_Wiki:Discussion#Twinkle_in_TF2wiki.3F. — Tark 00:48, 25 June 2023 (UTC)

Page for Blender?

The de facto standard for all but the most pro community creators making hat and item models. And really in the past decade, Blender is becoming the universal 3D modeler with Maya etc. just retaining prestige. Should there be a short page for it directing to the other wiki or whatever? Indirectly encouraging more community creations.-- Akolyth (talk) 02:58, 3 August 2023 (UTC)

Hm, these pages are created only when we link directly to them, which is not the case here. I wouldn't mind having an in-depth tutorial on how to create cosmetic items or a simple list of popular tools on Steam Workshop though. — Tark 04:25, 3 August 2023 (UTC)

I'd be in favour of linking to other guides (IIRC NeoDement had a link to that on their profile for ages but I can't find it anymore) and popular tools on Steam Workshop over us making a page for a tutorial. Seeing as most active people don't know how to cosmetic items, it would essentially just be a copy of an existing outside guide or one person's method of doing things.
| s | GrampaSwood (talk) 12:15, 3 August 2023 (UTC)

Mandatory Show Preview Requirement.

Chinese Wikipedia has implemented a feature that forces non-autoconfirmed users to use "Show Preview" before they saving the changes. Should we get one?
By the way, I've seen someone else has proposed the removal of CAPTCHA for autoconfirmed users, but when will it work?--BEUFK - Contributions-Talk 14:50, 6 August 2023 (UTC)

Not sure about the CAPTCHA thing, but the forced SP will not really do much imo, except for make people think the edit saved.
| s | GrampaSwood (talk) 15:18, 6 August 2023 (UTC)

We currently don't have the means to do anything about the CAPTCHA, unfortunately. — Wookipan (talk | contribs) 21:02, 7 August 2023 (UTC)

It works like this and I'm fully sure that no one will misunderstand it. --祝编安/Best Regards ||| BEUFK the nonsense - contrib. - have a talk 15:31, 6 August 2023 (UTC)

Concerning CAPTCHA, it admittedly has been one of my greatest pet peeves for Wikis and internet in general for years, at least with Google's version, which I swear doesn't register correct inputs at least half the time. The slow "fade in" images are the worst and can be quite discouraging. For now I try the audio option when that isn't incomprehensible. I think a simple text or short audio fill-in (or solve a simple arithmetic equation or something) should stop bots regardless and I want Google to lessen its monopoly anyway. I understand though.-- Akolyth (talk) 02:37, 8 August 2023 (UTC)

Speak of the devil, I just got this problem worse than ever for using an external link in an edit (did many times before). And Google so set the captcha in an apparent endless loop. This is madness, I can't take it, something has to make this easier please!-- Akolyth (talk) 03:45, 8 August 2023 (UTC)

 Support — Tark 16:17, 6 August 2023 (UTC)

 Support. I was experimenting a little with something of that nature a while back. Should be relatively easy to develop, and I might also have a better way for it to grab users' attention. — Wookipan (talk | contribs) 21:02, 7 August 2023 (UTC)

 Support I misunderstood what it meant, I thought it meant that when hitting "save" it forced a show preview first.
| s | GrampaSwood (talk) 10:49, 9 August 2023 (UTC)

 Against the main idea, but no captcha requirement for autoconfirmed users is fine IMO.
Tiagoquix (talk) 18:06, 27 November 2023 (UTC)

 Support both the mandatory show preview idea and the removal of captcha for autoconfirmed. Forcing show preview seems like a good tactic on paper, as it would minimize mistakes and imperfections that users sometimes make when editing, but it might trip a few people up if done incorrectly. The removal of captcha for us autoconfirmed users is an immediate yes, since it's annoying, especially Google's variation of it. ♡ JupiterSphere ♡ ( ◡‿◡ *) ⊱✿⊰ Talk To Me! ⊱✿⊰ 02:11, 16 June 2024 (UTC)

Adding images to searches

Hello. I was thinking of adding Images right next to the search results like Wikipedia does. It makes sure that people know what page to go to, and it will overall improve the wiki. ---- Talk Contribs Steam 16:33, 12 April 2024 (UTC)

I think many don't even get to the actual Search page but maybe the proposed extension on the main page has this option? I'm not sure Mgpt (talk) 16:22, 13 April 2024 (UTC)

Remove captcha requirement for autoconfirmed users

Hello there.
Google Captcha is a terrible service and I would like to kindly request the user right skipcaptcha for users in the group Autoconfirmed users.
I believe this wouldn't cause any considerable trouble as only users that are/were active would be able to skip the captcha. (The wiki URL filter (such as social media URL filtering) would still apply. This is only about the captcha.)
For more information, see Special:ListGroupRights.
Many thanks for your attention.
Tiagoquix (talk) 00:24, 16 June 2024 (UTC)