Inkipedia talk:Ink Pump

The Ink Pump Welcome to the Ink Pump. Similar to Wikipedia's village pump, the Ink Pump serves as a general place for the Inkipedia community to discuss the wiki as a whole, whether it be ideas, proposals, technical issues, or notices.

Remember to put new discussion sections at the bottom of the page.

You may also wish to view recent talk page discussions.

Archives available here. Inactive topics should be archived when this page reaches 40 topics or 50,000 bytes. Any Inkipedia user can archive the page.

Current page size is bytes.

Establishing User Content Policy
I've been mulling this over for awhile now, but I believe now it is time to act: There is a lot of user-only content on Inkipedia. More specifically, there is a subsection of users that are using the platform more as a social platform or a fanon-driven sandbox than are actually developing the site and the important mainspace content. This doesn't fall in our scope, nor does it make sense in the broader sense of the platform to host these projects as they exist themselves. A bulk of the issue stems around the high volume of user images, although not exclusively. I propose that we push the site into a new direction, with one of the following three outcomes: Alternatively, we could do nothing, or, if someone else has a better suggestion, could be used instead. There could also be a hybrid of the options above. The long term goal is to encourage mainspace editing, and—with multiple users having 30% or fewer edits for the wiki compared to their user pages—it appears this is not the focus. This is a good way to get back on track to content based edits. This is not supposed to be a specific attack on any one user, nor is it saying that the work being done has no value, however I believe it is time to evaluate its purpose on Inkipedia itself and where it should possibly move. Please feel free to vote or offer suggestions/responses below. Trig Jegman - 19:18, 26 January 2023 (UTC)
 * (1) Establish a formal limit for personal content per user. The specific details of this can be established more specifically if people opt for this answer, although I suggest 10 files plus signature materials. This is the format near all affiliate NIWA wikis opt to use. (For example, WiKirby allows five files per user)
 * (2) Expand/revitalize the 'Blog:' namespace to be supportive of Fanon content, establishing specific rules and guidelines on how those posts are made, managed, and maintained. User pages that meet the criteria would be integrated into this space. As an example, Fallout Wiki has an independent namespace for user projects and content.
 * (3) Create a completely separate Fanon/social wiki space akin to Pikmin Fanon and the Fanon Wiki network.


 * Option 1 definitely seems to be the most drastic, with many user pages and sandboxes consisting of many more than 10 images, however, it would also get the job done very well if your goal is to reduce the amount of user-only content on the wiki (which I'm assuming is the goal). Option 2 is my personal favorite. Bringing back the "Blog:" namespace is long overdue and it is definitely the least harsh option on here. Option 3 is a little confusing if I'm being completely honest. Like, I understand the point, but, why would we pick this option over the other two? It's outclassed in both ways because it accomplishes neither of the goals as well as the other two. Thank you for listening to my TED talk, and have a great rest of your day! 21:43, 26 January 2023 (UTC)
 * Option 1 would be best; Option 3 is decent, but the creation of a fanon wiki isn't Inkipedia's business. I don't think it'd be fair to the bureaucrats to have them host and/or manage a separate looser wiki unless it's something they're on board with.
 * I strongly agree that this is an issue that needs to be addressed. Often I'll see users repeatedly make very long edits detailing the stories they have for their Splatoon OCs, or things like their extensive opinions about various Splatoon lore/updates/popular interpretations, to the point the amount of content on those userpages is better suited for a personal website (or, as you proposed, a separate fanon style wiki). I think restricting the amount of user images allowed per user in addition to the permitted length a user page can reach would help keep Inkipedia tidier, while encouraging new users to not turn their pages into what is essentially their own webpage, fully removed from being related to editing Inkipedia.
 * Wikipedia's policy on the matter is perhaps too strict for a videogame encyclopedia's standards, but worth consulting in the process of addressing this. I am personally very disheartened every time I see massive edits to userpages when I check Recent Changes. Inkipedia is not a host for people's opinions.
 * Option 2 is interesting and worth considering, but I fear allowing users to create blog posts (even within guidelines) would further enable the types of users that focus on editing their userpages to continue posting unrelated content. The best use of the blog namespace on other wikis I've seen have been blogposts regarding massive updates being made to the related wiki or wiki software, rather than being directly related to the content the wiki covers. I fear ushering the current unusual use of userpages towards the blog namespace might devolve into the style of Fandom wikis' talk board pages, which are notoriously full of users posting whatever's on their mind, wiki related or not. Yoshifan52 (talk) 22:24, 26 January 2023 (UTC)
 * Reminds me of the SmashWiki's probation thing, which I think should be somewhat implemented here in order to encourage mainspace edits. — Exaskliri (talk | contribs) 22:51, 26 January 2023 (UTC)
 * The only things that concern me are Options 2 & 3, as the former I'm wondering if the blogs will be protected from spam changes/reviews, as I'm very protective of my Fanon and don't want to see it discriminated. For the latter, I agree with some comments about it. This wiki is more organized and filled to the brim with official info to research on, while Fandom wikis, I feel, are a goldmine for spammy users and fan-generated content some might be uncomfortable with of disagree to. Yes, my Canon Sandbox is "so" dang big, as I may plan on dividing it into parts. The current one becoming the introduction to the world, battle rules and Splatfests. While the characters and story parts will become individual sub-pages (as they take up the bulk of my Sandbox now...), and have links to them in the former page. OR, as Yoshifan52 said, make some sort of form or private website to contain that content and have a link to it on my User page. But right now, I don't have the time, money "and" tech to do it yet, as I'm busy with irl stuff (finding a comfortable job, house chores, etc.) AND grinding in Splatoon 3 on the daily.
 * PS; I apologize that most my recent edits here were in userspace. I haven't had the time to add new info to mainspace or it has already been added. Sincerely,  23:47, 26 January 2023 (UTC)
 * You have edited your userpage almost 900 times; this, combined with the amount of content on it, is the exact kind of userspace editing behavior I think should no longer be allowed. Yoshifan52 (talk) 00:13, 27 January 2023 (UTC)
 * I don't mean to be subjective and begin an argument, but are you mentioning my user page or my Sandbox about the amount of edits? If its the latter, I can agree and possibly plan on either dividing its content into separate sandboxes or copy it into a private website or Google Form when I aquire my preferred tools to do it.  00:20, 27 January 2023 (UTC)
 * Your userpage's statistics page (not the sandboxes') says there have been 841 edits made to it, the vast majority of which were made by you. That is an extremely high number of userspace edits. Your main sandbox page has been edited 743 times, and its contents seem to be an extension of your userpage, rather than a proper sandbox; it is full of fanon information rather than tests of wiki features or prototypes of mainspace articles. Yoshifan52 (talk) 00:45, 27 January 2023 (UTC)
 * @Yoshifan52; That may be because of my system of updating my game stats weekly (Might change it to seasonal rn), grammar/spelling fixes, removal of might-be offensive content and my Splatfest/Big Run results. So should I ditch my ongoing Weapon Ideas table and delete it and trim-down some stuff? Also, this may be off topic but, should I split my Sandbox Page to separate Sandboxes each for an Intro/details, Characters, and Story pages respectively, or copy it over to a Google Dock/Drive or a private website? I'd be glad to have some help with that. Sincerely,  02:06, 27 January 2023 (UTC)
 * I like the probation idea mentioned by Exaskliri. I like option 1. I don't think option 2 or 3 would help. So, I want to go with some combination of option 1 and SmashWiki's probation process. Heddy (talk) 23:52, 26 January 2023 (UTC)
 * I'm in a similar mind, though I don't feel strongly for implementing a Probation-like policy. User image limit, yes. As noted, I don't really have additional energy to start/maintain a fanon wiki. I do think we need some policies that says what Inkipedia is not, and some guidelines on userspaces in a slightly more lenient way to the Wikipedia policy linked above. A quick reminder that you can filter out userspace edits from the recent changes (though obviously this can't be done for patrolling edits). 00:17, 27 January 2023 (UTC)
 * Would a decision here be made by a vote or a consensus? (As a side note, a personal image limit would be good, but maybe we could make a template for things like splatfests? Perhaps something like the translation template, where you can't click on the flags, but it still has the image? We could change out the flags for the splatfest icons, and we could have different parameters be options of [just going off what I see on other's pages] a personal choice, a synopsis, and stats? Just spitballing). Xando  (ping) 21:31, 27 January 2023 (UTC)
 * There would need to be a consensus for any major change, per the consensus policy. Heddy (talk) 00:57, 31 January 2023 (UTC)
 * I like option 1 the most, I'd need a better explanation of what further guidelines other than limiting the number of files you can upload. I think the discord lately has been very focused on community matters than wiki matters so any socials can go there or to any other social media/blog/forum website. Shahar (talk) 14:19, 28 January 2023 (UTC)
 * I love option 1. Mostly just because I feel like I have too much userspace stuff. I end up using the time I have to edit that, anyway, so that should be limited. (Basically, I'm an amazing example of being too immersed in my userspace edits. :,) ) 18:35, 28 January 2023 (UTC)
 * Although I'm not very active on here at the moment, I think this is a great idea. The purpose of this wiki it to provide info on the franchise, not to be a social media platform for fans. 17:21, 5 February 2023 (UTC)
 * I am also a very immersed Sandbox editor, and I definitely could use a push to make Inkipedia a better place. Option 1 seems like a "cold turkey" way to limit these actions from happening, and would be a quick route out. I would be fine with any of these options, but it seems rather extensive to create another website to cater to us canon sandbox creators and similar folks of the wiki. I don't really think the probation seems necessary unless someone is continuing to push the limits. All in all, I think that this is a great idea.
 * S3 Frye Render.png Clarinet.octo Marina.png  ( talk )S3 Tableturf Card Murch.png 03:13, 6 February 2023 (UTC)

To continue this effort, here is the semi-formal definition of a user image as well as three individual feedback points (number, subpages, lock to ac) for debate. I would like to know what you think will work best for the finalized policy so that way the proposed policy is the most supported option.

A user file is a personal file belonging to a user for the purpose of being used on their userpage or a related userspace page. Examples include images of personal Inklings, stats, gear, or fanart.

What constitutes a user file is purpose. Some files uploaded may be used on a namespace draft page—these are not user files as their end goal is to be integrated into a mainspace or wiki policy page. User files specifically are intended to remain in User: and Blog: namespaces.

A user may also have images to use for their signature. These files, given their unique usage, will also not be considered as a user file, although their amount should be kept minimal.

(1) Limiting user files seeks to increase efforts editing on-wiki. Here are several proposed guidelines (in general order from least to most strict):


 * Ten user images, no greater.
 * Seven user images, no greater.
 * Five user images, no greater. This is the most common policy held by affiliate wikis.
 * Three user images per year of active contribution (min of 36 constructive edits per calendar year).
 * Ten user images plus a probation status akin to SmashWiki—if edit to userspace ratios don't line up, be unable to edit userspace until mainspace is addressed.
 * Five user images plus a probation status akin to SmashWiki—if edit to userspace ratios don't line up, be unable to edit userspace until mainspace is addressed.

No account will have user content grandfathered in. All files exceeding the limit will be deleted on November 1st, 2023 (example date, but an established hard number with exceptional advance) at administration's discretion. Users will be asked to remove content prior as to only preserve the most important files for their space.

(2) Additionally, non-draft and non-maintenance user subpages should never exceed five regardless of the option voted on above.

(3) Lastly, a third proposal to lock the creation of User pages to autoconfirmed is suggested.

Please let me know your thoughts on all three policy changes as suggested above. Trig Jegman - 17:06, 11 February 2023 (UTC)


 * I think putting a limit on the amount of user files one can have is a great idea. Five user images sounds like the best choice.
 * I would like to point out that some new users are uploading random Splatoon memes and fanart without putting them on their user page. New users have also been uploading duplicate files. If there was anyway we could make it so only autoconfirmed users could upload files that would be a major help. By doing so we could lower the chances of unneeded files being uploaded.  17:45, 11 February 2023 (UTC)
 * @Oddlilgoof If someone is having difficulty learning to use Inkipedia and uploads duplicates as a result, I don't see how an autoconfirmed requirement would change that. If anything, it would just delay them learning file management until later.
 * An autoconfirmed requirement would not help the wiki, it would hurt the wiki by preventing people from uploading the files they joined the wiki to submit. When this autoconfirmed-to-upload requirement was tested in the past for Inkipedia, users would come to the Discord and complain that they can't contribute files. Just imagine the users who hit that wall and don't even have the energy to complain on Discord or on wiki, we would be missing valuable contributions without even knowing it.
 * Besides, an autoconfirmed requirement would be such a major change that I believe it would need a separate policy proposal anyways. My opinion is that the user content policy should focus on what content users can upload and maintain on their user pages, it should not focus on access restrictions. Heddy (talk) 04:45, 16 February 2023 (UTC)
 * @Heddy That does make sense. We can always just splat the duplicates and tell the user not upload duplicate files having them learn from their mistake. Many users come here to do good. I didn't really think about how if we put a restriction on uploading files people would still upload duplicates by accident. Thank you for bringing this to my attention :)  12:17, 16 February 2023 (UTC)
 * Five images per user alongside a hard deadline by which everyone needs to tidy up their current user images sounds best to me. I'm still a fan of the probation period concept, but that's ultimately up to the admins, since they'll be the ones with that additional workload. I'm 100% for both file uploading and user page editing being limited to autoconfirmed users; another wiki I work on implements that, and I find it excellent at helping block out spam/obvious mistakes/users that create an account, then a user page, then never make any edits. Yoshifan52 (talk) 22:49, 11 February 2023 (UTC)
 * @Yoshifan52 autoconfirmed is too restrictive as an upload requirement. Imagine joining to make an important contribution and being told you need to wait 4 days + 10 edits for your account to be confirmed. Many users would just silently give up and we would be missing out on valuable contributions without even knowing it.
 * If someone is learning to use Inkipedia and uploads obvious mistakes as a result, I don't see how an autoconfirmed requirement would change that. If anything, it would just delay them learning file management until later. Heddy (talk) 04:49, 16 February 2023 (UTC)
 * Oh hmm, good point. Yoshifan52 (talk) 06:21, 16 February 2023 (UTC)
 * I should mention that we have the ability to create requirements completely separate from the autoconfirmed process. For example, 2-hour account age required to upload, or 2 edits required to create a user page. Though I do think such a discussion should be separate from this user content policy proposal. Heddy (talk) 02:23, 17 February 2023 (UTC)
 * The problem with locking user pages to autoconfirm is that autoconfirm is a very easy status to reach. Only 5 edits and 1 day are required to become autoconfirmed. With vandalism, this is very easy to do. I fear that users who want to use this wiki as a social media platform will simply make unhelpful edits in order to unlock the userspace. If we were to gatekeep the userspace like this, we would need to raise the autoconfirm requirements. (Additionally, I've only ever seen ads in the userspace, which is another sign of it being way too full) 02:08, 12 February 2023 (UTC)
 * Between it being relatively easy to become autoconfirmed, and blocks placed upon misbehaving editors only lasting a day or two, maybe Inkipedia needs to become a touch more strict when it comes to new users. Altering the autoconfirmation process (which I believe is handled by the system, not by staff going through lists of recently registered users) and/or directing less knowledgeable editors towards the rules a bit better on something like the main page could potentially help a lot. Yoshifan52 (talk) 07.24, 12 February 2023 (UTC)
 * I've been on and off about 20 or so wikis in my time and from what I have personally observed, I don't really believe in harsher autoconfirm=ensuring quality edits mentality. I think it only creates a more elitist spin and dissuades new or inexperienced editors from making attempts to make changes or contribute at all because the tools are not provided to them. This rings doubly true because Inkipedia is just kinda one of those places where it is people's first real wiki experience. If there's a unanimous agreement to restrict image uploading to AC, then I can add it in, but I'm pretty staunchly against the notion of increasing the AC requirements too significantly. Trig - 18:27, 12 February 2023 (UTC)
 * Good point, the resulting elitism could definitely be a problem. Yoshifan52 (talk) 23:41, 15 February 2023 (UTC)
 * I have not seen much discussion regarding the choice of image limit. I think I would like to start with an image limit of 10. 5 seems too restrictive, because the moment Splatoon 6 comes out, people who want an image of their character from each game will be devastated! Yeah probably not the best reason, but since this is already such a huge change I'd like to go with the least restrictive option. Though I'm not certain if that's the best choice. Can everyone please discuss what is the best choice? Heddy (talk) 12:41, 16 February 2023 (UTC)
 * Both odd and yoshi have stated 5, and I would agree. When hypothetical Splatoon 6 Return of the Octavians comes out, people can grid together the files or be old enough to have an alternative off-platform social media account dedicated to the sharing of personal content. Five allows for a brief summary and a bit of shine without becoming egregious. I've two files in use already, which would still allow me to show off an inkling for all three games. Trig - 13:00, 16 February 2023 (UTC)
 * I concur with 5 images per user; and if enough users don't like it, then a discussion about 7 or 10 might be good. I think there should definitely be no more than 10, though, because there's just no reason that I can see at this moment in time. -Xando (ping) 13:06, 16 February 2023 (UTC)
 * Alright then, seeing as there is a lot of support for a 5-image limit we may need to go with that. Once the policy proposal draft is finalized, I will open a vote to pass the policy if the vote shows a consensus.
 * Note: I looked at staff user pages and found that Shahar, P.J. GT, and StarAdamStar would all have to reduce their image count if this 5-image limit were to become policy. Do any of you object to this proposed limit? Heddy (talk) 02:31, 17 February 2023 (UTC)
 * Five is not enough considering we have three games already. Ten is a safe number and more flexible to allow some sort of creativity in the user page. Shahar (talk) 09:55, 17 February 2023 (UTC)
 * @Shahar: Have you reviewed the reasoning above from the people who prefer 5 as a limit? Summarized:
 * You could use unlimited images as long as they are already-existing wiki images, or sandbox/draft images intended to create an article. And on top of that, 5 personal images.
 * Personal images could be combined together to reduce the image count.
 * Each subpage would have its own personal image limit, so you could create a subpage which could have another 5 personal images.
 * If someone needs to have excess images beyond 5 on a single page, they may want to consider using a blog such as Tumblr or Twitter. Heddy (talk) 16:18, 18 February 2023 (UTC)
 * Disagree with subpages having image limits—you only just have unlimited images than can be transcluded. I've raised my written draft to go to seven, as a compromise between the users suggesting five and some administrators suggesting ten: Two images per game (one of inkling, one of gear, perhaps?) and a seventh for whatever you want. That is more than plenty appropriate in addition to already existing files or external websites. Trig - 16:44, 18 February 2023 (UTC)
 * Disagree with subpages having image limits—you only just have unlimited images than can be transcluded. I've raised my written draft to go to seven, as a compromise between the users suggesting five and some administrators suggesting ten: Two images per game (one of inkling, one of gear, perhaps?) and a seventh for whatever you want. That is more than plenty appropriate in addition to already existing files or external websites. Trig - 16:44, 18 February 2023 (UTC)

'''Voting has started! Please use the following link to vote: Inkipedia talk:Voting:User content policy''' Heddy (talk) 00:33, 19 February 2023 (UTC)

Gender in infobox
I remembered that InfoboxCharacter uses "gender" as a parameter. I'd like a small vote on what we should do, as we're: de-emphasizing gender in favor of style; with the recent merging of male and female people into ; and Shiver discussion.

Change gender parameter to pronouns
 e.g. change gender=Male to pronouns=he/him etc.

Remove gender from the infobox entirely
Since it should be obvious from the article's writing what the character's pronouns are
 * 1) Well someone's gotta vote at some point. I think it should be pretty easy to integrate this information into the main article itself (ex: Goggles is a male inkling found in the Splatoon Manga series) if not otherwise derived from quotes pages, general appearance, or the page referring to the character inherently. Trig - 11:34, 28 February 2023 (UTC)
 * Okay, but why not both? Infoboxes are intended for at-a-glance information, and gender is certainly something people expect to find in the infobox. Any further details can be explained in the article's paragraphs. Heddy (talk) 13:59, 28 February 2023 (UTC)
 * 1) If we keep gender, another whole shiver thing could happen. But if we put pronouns, then characters will feel like real people, and that'd be weird. Kinda like a pronoun pin on a computer... it's just odd. So just remove it in general and put it into writing. -Xando (ping) 12:36, 28 February 2023 (UTC)
 * When you say "whole shiver thing", do you mean the period of time where Shiver's gender was unknown? Because, if so, I don't see how that justifies removal of gender for every single character in the game. The period of time where it was unknown could/should have been settled by just leaving it blank, providing pronouns and other details elsewhere. Shiver currently has a gender listed, as do most characters, and if the gender is truly unknown then I feel that leaving the field blank (and stating every detail known in the article's paragraphs) would be the best solution. Heddy (talk) 13:59, 28 February 2023 (UTC)

Discussion
23:32, 27 February 2023 (UTC)


 * I'm in favor of adding a "pronouns" parameter in addition to the existing "gender" parameter, the former which should only be used in cases where the gender of the character is ambiguous or undefined (as with Commander Tartar, O.R.C.A., the Smallfry buddy, etc). The only reason to do so is because there is no official information on the matter; using concrete terms on those characters' pages would be a large assumption on the wiki's part (as we are not given the precisely relevant language). It's simpler and more correct to list that they are exclusively referred to with it/its. I don't see why the entire infobox used on 50+ pages needs to be revamped for just a handful of characters, when adding an additional, more descriptive parameter to use exclusively on their specific infoboxes solves the issue.
 * I'm against outright replacing "gender" with "pronouns" as I feel as if that's lending Nintendo more credit than they are due in terms of how they gender their characters. The majority of Splatoon characters are explicitly gendered, so implementing a big change such at switching the Squid Sisters' listings from "female" to "she/her" creates a bit of unintended ambiguity on the matter, which is inaccurate.
 * Additionally, the playable agent characters are currently listed as "gender: any"; if the infobox module swaps the "gender" parameter for "pronouns", these characters would have to be listed as "pronouns: they/them", as thats what official material uses, when that's not really correct. The agents are stand-ins for the player, rather than "canonically" going by they/them. Yoshifan52 (talk) 23:54, 27 February 2023 (UTC)
 * I don't see a reason to remove this information. The player select screen using "style" instead of gender is not at all a valid reason to remove content from the wiki. All it means is that the player character doesn't have a gender. It means nothing more. It definitely doesn't mean that the Splatoon universe as a whole retroactively no longer has gender. I'm fine with adding pronouns for those cases where the gender is not known. Heddy (talk) 05:23, 28 February 2023 (UTC)
 * Gender is already an optional parameter and is not listed on O.R.C.A.'s infobox, and I think it's fine that way - playable characters being referred to as "any" is the simplest way to say that their gender is determined by the player, and all other characters' genders are either clear or not listed. I can think of very few cases where characters with ambiguous genders (i.e. not Captain 3) are referred to using any pronouns at all, so adding it as a separate thing from gender has remarkably few use cases. 08:09, 28 February 2023 (UTC)
 * +1, no reason to remove, seconding everything said above. Everyone's points are extremely well-articulated, and all solid, objective, supporting reasons. Characters still do/can have gender (and you know saying "style" is just pretty much a euphemism when it's so 1:1 correspondent – to the Inkling/Octolings girls/boys wearing a sports bra vs. not, having shorter vs. longer shorts, having pointed vs. non-pointed triangles in their eyes, having higher vs. lower voices and different voice lines… right?) Doesn't this, like, feel all a bit pretend? And ultimately unnecessary to have some big discussion about? The concept of gender in the world is not "bad" – and it's also not something the series has always shied away from, either. This infobox field can always be left blank; there is no reason that merits modifying the entire template. This discussion is a bit silly. –Eli (talk) 12:29, 28 February 2023 (UTC)

I've added the optional pronouns parameter to the template as suggested but seems that there's no quorum to make any article changes, be it removal or additions. 23:37, 2 March 2023 (UTC)

Formatting for titles of works of art
Wikipedia does italics for major works of art such as video games titles (like: Splatoon), and quotation marks around minor works of art such as song titles (like: "Calamari Inkantation"). Currently, Inkipedia does use italics for major works, but Inkipedia doesn't have an agreed-upon treatment of minor works.

I am proposing that Inkipedia adopt a more fresh, stylish, easier-to-follow approach: all works of art, major and minor, should be italicized. Further, I am proposing that conjectural names should not be italicized. Quotation marks would not be used. Bold would continue to be used only for the first mention of a subject in its own article, and bold would continue to be combined with italics as appropriate.

If there is a consensus here, I will go ahead and update Inkipedia's Manual of Style. If there is not a consensus (for this proposal I will define consensus as at least 80% of people voting the same way) within two weeks, the Inkipedia community's strongest arguments will be analyzed to create a new proposal that everyone is more likely to agree with. Heddy (talk) 14:13, 28 February 2023 (UTC)

I support italics for all works of art (Heddy's new proposal)

 * 1) Heddy (talk) 14:13, 28 February 2023 (UTC)
 * 2)  14:17, 28 February 2023 (UTC)
 * 3)  14:18, 28 February 2023 (UTC)
 * 4) Adrmcr (talk) 14:25, 28 February 2023 (UTC)
 * 5) Trig - 14:25, 28 February 2023 (UTC)
 * 6)   14:28, 28 February 2023 (UTC)
 * 7) I'd like to say that quote marks would mix official and conjectural song names in navboxes. — Exaskliri  (talk | contribs) 14:32, 28 February 2023 (UTC)
 * There isn't a rule that says conjectural names should be quoted, so I don't think it matters. Harimaron (talk) 14:45, 28 February 2023 (UTC)
 * 1)  15:46, 28 February 2023 (UTC)
 * 2) Harimaron (talk) 16:20, 28 February 2023 (UTC)
 * 3) GloverMist (talk) 19:26, 28 February 2023 (UTC)
 * 4)   00:40, 2 March 2023 (UTC)
 * 5) This makes most sense to me given our current position on conjectures  23:39, 2 March 2023 (UTC)
 * 6) Yoshifan52 (talk) 00:14, 3 March 2023 (UTC)
 * 7) Lofiguy (talk) 17:36, 8 March 2023 (UTC)
 * 8) Woomy? (talk) S2_Weapon_Main_Sploosh-o-matic_7.png S2_Ability_Main_Power_Up.png 18:38, 8 March 2023 (UTC)
 * 9) S3 Tableturf Card Toni Kensa.png ℂ𝕝𝕒𝕣𝕚𝕟𝕖𝕥.𝕠𝕔𝕥𝕠 S3 Tableturf Card Annaki.png  ( ℙ𝕣𝕒𝕥𝕥𝕝𝕖 ) 01:35, 11 March 2023 (UTC)

I support italics for major works and quotation marks for minor works (Wikipedia's approach)

 * 1) StarAdamStar (talk) 14:23, 28 February 2023 (UTC)

Comments

 * An implication of this would be, no more leaving parts of a title out of the italics. Like, I guess some people felt that "Expansion Pass" was more of a minor work so it didn't get italics while the "Splatoon 3" right next to it did get italics. Sure, expansions or DLC may be minor, but they are a formal title of a work of art, so I believe they would qualify for italics under my new proposal. Heddy (talk) 15:37, 28 February 2023 (UTC)
 * Though I have always seen Octo Expansion italicized on the wiki. In my view this reflects the existing practice. Harimaron (talk) 16:16, 28 February 2023 (UTC)
 * Do we also want to italicize titles in the foreign languages box or not? Wikipedia:MOS:NOITALIC suggests the following: "Italics should not be used for foreign-language text in non-Latin scripts, such as Chinese characters and Cyrillic script, or for proper names, to which the convention of italicizing non-English words and phrases does not apply; thus, a title of a short non-English work simply receives quotation marks." Harimaron (talk) 09:16, 2 March 2023 (UTC)
 * I don't want to impose English style norms on other languages. For now, let's not change anything about how names in other languages are handled. It's up to foreign language editors to decide in a separate discussion, if they want to change something. Heddy (talk) 00:39, 7 March 2023 (UTC)