TASBot Wiki:Village pump

NEED MORE CONTENT in general (historians wanted). Fill out redlinks or add to existing articles (and category pages).

Categories are arguably a direct upgrade to articles in that pages can have multiple parent categories, and categories have a nice UI for navigating to subpages. The longer URI is why you shouldn't just use them for everything.

Embrace hypertext—link to other pages (and also other sites, such as [[wikipedia:]] and {{TASVideos}}), but do also follow Wikipedia's linking guidelines: only link first mention, avoid adjacent links, don't over-link common concepts/entities (TASBot, in our case).

Use redirect shorthands wherever you feel they fit, with one exception: tagging pages with a category will not work if you use a redirect. You may still use the redirect when making a normal/inline link to the category page, such as [[:Category:SGDQ|]] ⟶ SGDQ.

On that note, when tagging pages for appearances with categories, put the year category first, then the event category if it exists (or will later i.e. a redlink). {{infobox appearance}} handles this for you.

Familiarise yourself with what templates exist. Hit up User:YoshiRulz if you want help making new ones.

For consistency (TODO move this to a style guide page):

• Where an event's name has a short form, the expanded form is the canonical one e.g. Summer Games Done Quick 2016, with e.g. SGDQ 2016 being a redirect to it.
  • For ESA, short names follow this (ESA YYYY through 2017, ESA {Summer,Winter} YYYY from 2018).
  • LI Retro YYYY is the short name for that.
  • BSG Annual YYYY is the short name for that.
  • AGDQ/SGDQ/GDQx and LTX are trivial.
  • May Contain Hackers (Galactic Hacker Party's 2022 incarnation) was special-cased and has been given 2 redirects.
  • No other events need abbreviating at present.
• Event categories should also be expanded, with redirects in the main namespace only and following the above rules.

TODOs for admins

• There are 5 pages to delete
• There are 19 images/files missing copyright metadata
• upload images (list existing media)
  • please try reducing filesize with WebP: magick convert input.png -define webp:lossless=true output.webp
• consider adding {{#babel:}} template for user pages
• fix quick search API
  • I researched as far as 'Generators' + prefixsearch and gave up --yoshi
• can the PortableInfobox link an image's media page rather than hotlink?
  • bonus points if clicking it opens a preview with the file's description as the caption, like on Wikipedia
    • this feature is part of mw:Extension:MultimediaViewer
• if semantic citation markup is desired, mw:Extension:Cite needs to be installed
• I haven't looked into how to do this, but I'm really missing the "Purge" button beside "Move" and "Watch" in the top-right it's mw:Extension:Purge, but TIL it doesn't affect pages' references lists, which is what I wanted it for --yoshi
• consider adding mw:Extension:CodeMirror and/or setting $wgWikiEditorRealtimePreview = true; for an enhanced source editor

TODOs

• finish moving event pages to Category namespace, and cleaning up names
  • GDQ (split and/or rename and/or merge w/ Category:Summer Games Done Quick)
  • MAGFest (split and/or rename and/or merge w/ Category:Super MAGFest)
  • MAGWest Go
  • ...then clean up {{prevnext appearance}} data
    • could copy the start date from the infoboxen to comments in the data
• infobox for individuals
  • Done, but it doesn't render correctly close enough now thanks to TheMas
  • consider adding fields for country/flag and for pronouns
    • Copied over a template from Wikipedia, and while it currently only works for users of this wiki, I have an idea for extending it if that ends up being necessary. In the meantime I suggest not making dummy accounts for people. --yoshi
  • could add email, but I'd like to have it deobfuscate on click (with JS) if it's going to be included, and with a personal site field it's kind of redundant --yoshi
  • consider adding field for (programming) languages spoken
    • for natural languages, there's mw:Extension:Babel, and it may be possible to hack in programming languages as qxx or something --yoshi
• consider redirecting (not sure how when #REDIRECT only allows local links) e.g. desync to TASVideos.org/Glossary#Desync
  • - introduces chance for link-rot
    • + can leave notes for TASVideos editors
  • - not everyone can add to that glossary
    • + yet
  • counter-proposal: could instead make a {{TASVideosGloss}} and use {{TASVideosGloss|term}} instead of [[term]]
    • + easy on a technical level
    • - no way to see valid link targets without visiting TASVideos
    • - same problems as above re: "delegating" content to TASVideos
• it seems reference lists e.g. Special:WhatLinksHere/Template:TASVideos don't differentiate between direct and transitive transclusions (that is, where the template is used as itself vs. where it's only used via another template)
• I believe MediaWiki:Noarticletext is used for 404 pages and it needs the TASBot spinning eye GIF --yoshi
• check this nonsense actually worked (IIUC a "null edit" should be updating WantedPages, but it just isn't, so I'll wait); if so copy TemplateData
• why are category pages wider than articles?
• use shorthand redirects in {{prevnext of type}} (just the outputs)? what about {{prevnext appearance}}?

---

Qs for dwango:

• I take it the focus here is on history, so how much technical information should be here vs on TASVideos?
  • tl;dr: we should put [technical info] on TASVideos. However, I have one pause here; there is a huge barrier to entry for TASVideos [wiki] at this time [...]
  • In essence, we should first and foremost ensure things like replay device and console verification documentation is complete (enough) on the TASVideos wiki. As CompuCat pointed out however, our needs and perspective is a bit different, and there's no harm in us also having technical details on the TASBot wiki with a perspective more geared toward live presentations at charity events. In fact, that's where I see the TASBot community as differentiated from the TASVideos side when it comes to on-hardware work; the TASBot community is centered around having our cute robot mascot play video games during public presentations, and our needs are going to involve things like proper presentation with visualization on camera that aren't relevant for just seeing if something syncs on hardware. To that end, I think there's room to have the core concepts explained from the different perspectives even if some of it may end up overlapping documentation on the TASVideos side. More documentation (so long as it isn't wholly inaccurate) is always better. There's another caveat here - despite my best efforts, it's still a lot harder for folks to edit wiki entries on TASVideos whereas anyone willing to share an email address is able to edit the TASBot Wiki
• apart from Ambassadors, how should individuals be categorised?
  • DWYW
    • pages can be in multiple categories, so I guess could just have one cat per role/specialty?
  • to that end, a definition of "notability" for inclusion here would be helpful
    • anyone who was credited for any event/showcase