Talk:Community Portal

Back to page

1,900,902pages on
this wiki
Add New Page

…to the Community Forum's talk page! This is the place to talk about the site with other editors, make plans for future changes, discuss problems and discover solutions.

Have fun, keep a cool head in discussions, and remember to always sign your posts!

  • Topics are in relative chronological order, top to bottom, so please add your post at the bottom of the page.
  • For questions about editing, see the Help Pages. If you still can't find what you're looking for, post your question at the Help Desk.
  • Current projects with links to discussions: [edit]
Project Link Page/s
Policy change for root pages LyricWiki:Proposal For Root Pages Policy

Appeal to adepts of African languagesEdit

Please, help me to clean finally the Category:Songs Needing Language Identification, containing atm 4 songs by Deep Forest, - all from their album Deep Africa (2013).
Baie dankie by voorbaat! --Senvaikis (talk) 08:35, November 13, 2015 (UTC)

WrongTitle template - is it redundant now? Edit

Hey guys, I was wondering, due to latest change of {{Song}} template, is {{WrongTitle}} even necessary? SongHeader's title display looks really nice and I'm not sure that we need that anymore. Same goes for AlbumHeader and ArtistHeader, they all cooperate really well with displaying titles that are not permitted by LW:PN. There's always {{DISPLAYTITLE}}, though I'm not sure that it's allowed (I saw that on few pages but I don't know that case is resolved by policy). What do you think? --Ozpl (talk) 13:26, March 15, 2016 (UTC)

Formatting of RTL albums Edit

What is the correct way to format album titles in a right-to-left script? For example, the titles in Category:Albums Hebrew don't look quite right, but that seems to be how text editors try to group the conflicting directions. Should we force it into "tsitra:mubla (year)"? ~Bobogoobo (talk) 10:25, March 20, 2016 (UTC)

HebCat in TextEdit --ES (talk) 13:26, March 20, 2016 (UTC)
@ES: Your picture is very nice and helps a lot ;) --Senvaikis (talk) 16:46, March 20, 2016 (UTC)
I skipped the video, my bad ;-). Copying the properly formatted and displayed text from OSX TextEdit to this edit box transforms it into:
	▪	הבילויים:הבילויים (2003)
	▪	רונה קינן:לנשום בספירה לאחור (2004)
	▪	רונה קינן:עיניים זרות (2007)
	▪	מוניקה סקס:פצעים ונשיקות (1995)
	▪	הבילויים:שכול וכישלון (2007)

Wikia's bad. You don't recall your editions of a Hebrew artist page that looked crazy either way...?--ES (talk) 21:01, March 20, 2016 (UTC)

P.S. This is why Kiosk albs are en-titled, even though per alb cvrs, fa was an option. --ES (talk) 21:47, March 20, 2016 (UTC)

I think this problems needs two solution:

  1. A template that displays the binary file (Album Art/YT) aligned left, and the text aligned right, so the test wrap around the binary f.e.:here (and on artist & alb pages) will get fixed. 6?
  2. (the tough one) The page names with bidirectional text (Album pages, or any song pages containing #s), Bob's example on cat pages.
Might be our luck and 6 can apply some wizardry, otherwise this 2nd one has to come down from Wikia. Best I know, non of the RTL wiki(a)s have our page naming convention and if they do, they can use arabic/hebrew script numbers to avoid Bidirectional text in page names. Or our templates (did I say 6/۶?!) might have to be modified so they can deal with Arabic/Hebrew #s;
(هایده:شانه هایت (۲۰۰۸ instead of (2008) هایده:شانه هایت (<-If you create this page, in preview you will notice the mess). But to get it to work, it has to be هایده:شانه_هایت_(2008), and the associated categories are a mess. Happy Easter! --ES (talk) 18:58, March 25, 2016 (UTC)

Collaborations v. 'Featured' on Artist PagesEdit

Following up on a long conversation I've been having with ES on my talk page, wouldn't it be better to have separate section for 'Collaborations' (ie, songs where multiple artists have a roughly even contribution) and 'Songs Featuring [This Artist]?' Apparently there's a previous discussion on this, but I can't find it.

These things just seem very different. A featured artist is sometimes just providing backing vocals or a couple of lines; it's totally different to a full-scale duet. This seems like information which is useful to viewers, and especially appropriate to LW, on which users actually listen to the songs and can make a judgement about whether the song is a collaboration or a single-artist song with a featured artist.

The case in point here is the artist page for Ricky Skaggs, which (in line for the 'featured' format) currently lists 'Friendship by Ray Charles'. But this song is a full scale duet; although it appears on a Ray Charles album (an album of duets), there's no sense in which this is 'by' Ray Charles any more than it is 'by' Ricky Skaggs.

That this distinction is industry-recognised can be seen in the example, from the same album, of Ray Charles & George Jones:We Didn't See A Thing, which is a duet but Charles and Jones, but also features Chet Atkins. This is actually written on the disc.

--RWDCollinson (talk) 08:53, March 30, 2016 (UTC)

In this case, I'd say you're correct in terms of whether the songs are "dual-credit" collaborations or songs with features.
However, "users actually listen to the songs and can make a judgement about whether the song is a collaboration or a single-artist song with a featured artist" rubs me the wrong way, because some artists credited as featured have a substantial part in the song too (see any song by a producer featuring a vocalist), so I'd prefer if we stick to what's written on the album/in sources, as opposed to the opinion of the editor.
In regards to collab vs. feature on the artist page, I think only one "Collaborations" header would suffice, as technically a featured artist is still collaborating with the lead artist, they way it's written can change though, depending on whether it's a joint credit or featured credit (e.g. "with" and "by" respectively). - Patzilla777 (talk - contributions) 14:35, March 30, 2016 (UTC)
Thank you for your response. My current query is about the titles that should appear on album pages, rather than the categorisation of songs. The docs currently don't list 'Collaborations' as a valid subsection title, although that title is used on a substantial number of artist pages.
But on the point you raise (which I am discussing with ES at the bottom of my talkpage), couldn't we just set out one rule for clear-cut cases (50/50 division of vocals for collabs, backing vocals only for featured), and leave the rest to external sources? Even that seems a little dependent to me; if LW is supposed to go on 'the lyrics as sung', it seems very strange to be relying on potentially fallible external sources for this. Relying on external sources seems more suited to a site that transcribes 'official' lyrics where possible.
--RWDCollinson (talk) 15:01, March 30, 2016 (UTC)
I'd prefer the idea that we go with "featured artist unless otherwise specified" (either by majority of sources saying it's a joint-credit collab, or the album/back cover shows "and" or "with" instead of "featured"), as this avoids relying too much on opinions, like I mentioned earlier.
E.g. some songs have a featured artist who does arguably more than the lead artist (e.g. rappers featured on a song by a singer: rapper has far more words in most cases). - Patzilla777 (talk - contributions) 15:15, March 30, 2016 (UTC)
Hmmm. Rap makes everything complicated! I think from the casual viewer point of view what they really want to know is a person's actual contribution to the song, but in most cases it doesn't seem to make a huge difference. While I'm here, do you have an opinion on Tanya Tucker:I Won't Take Less Than Your Love? The (compilation) album back cover says 'With Paul Overstreet and Paul Davis', and the song is evenly divided (three verses, three choruses, one each per singer), but none of the external sources acknowledge this except for Indeed, most of them don't even mention the other two artists! This is part of my difficulty here; a lot of our external sources are sadly of dubious accuracy.
--RWDCollinson (talk) 09:27, April 1, 2016 (UTC)
Does anybody have an opinion/enlightenment on the original issue? Since posting, I have noticed that the George Strait page that ES held up as an exemplar seems to distinguish between songs recorded 'with' and songs 'by', so it is possible to make a subtle distinction between collaborations and songs in which the artist is only featured in the 'Songs Featuring X' section. But I still think it would be helpful to have a separate section for collaborations.
PS: I've realised that this was actually what Pat was referring to at the end of his first response. Fair point!
--RWDCollinson (talk) 09:27, April 1, 2016 (UTC)
For deciding credits "and" and "featuring" are pretty clear, but "with" seems to mean either. In the case of that Tanya Tucker song, IMO Tucker is clearly seen as the lead artist, otherwise it would be credited as "Tanya Tucker, Paul Overstreet & Paul Davis". Not to mention the back cover doesn't even seem to list them (at least not clearly - the image quality isn't excellent). - Patzilla777 (talk - contributions) 11:59, April 1, 2016 (UTC)

About Romanization rules for Japanese Edit

I'm copying these suggestions of mine from Help talk:Romanization as that Talk page seems to be inactive at this point. I was referring to Help:Romanization#Romanization rules for Japanese.
I found some of the rules here a bit inconsistent and in one case, misleading, so I would have a series of proposals, in order of how they appear on the help page.

  • This is a minor thing, but wouldn't lines starting with a capital letter be more visually pleasing? A mass of lowercase letters are just as hard on the eyes as a mass of uppercase letters. This wouldn't necessarily bring the assumption that every line is its own sentence since punctuation is missing (except in really specific cases where the original lyrics has some sort of punctuation like exclamation marks), so it wouldn't really mess with how people perceive the lyrics.
  • Current rules for particles, double consonants, and the romanization of ん are inconsistent. In case of particles, wo is traditional Hepburn, and so is rendering the syllabic n as m before labial consonants, but putting an apostrophe between n and vowels or y is modified Hepburn. In the meantime, the current rule for double consonants that doesn't list exceptions is practically not Hepburn. Either go with one or the other, and since traditional Hepburn was made in 1886, I would definitely recommend we go with modified, from 1954. You can read up on the similarities and differences on the very extensive Wikipedia page it has: [1] (As a personal note I would like to add that I absolutely abhor some of the butchery Hepburn does with Japanese, such as こっち being kotchi, but if anyone here expects anyone else to be consistent, it certainly has to start with consistent policies.)
  • As for "contractions", that rule is entirely made-up, has nothing to do with romanization, and is generally a misunderstanding of how Japanese works. It assumes that the difference between 走っている (hashitteiru) and 走ってる(hashitteru) is the same as between "it is"->"it's", whereas it is more along the lines of "going to"->"gonna", and even that might be stretching it. All in all, this "rule" should be deleted.
  • We should add that English or other foreign but not Japanese words written in katakana should still be romanized properly instead of using the intended foreign word. For example, "ライフ" would be "RAIFU" and not "life".
  • Latest accepted romanizations for obsolete kana should be added to the kana table just in case. Japanese artists are notorious for using uncommon... things in lyrics simply for the sake of being, I'm not even sure, maybe edgy? So having them there would certainly not hurt.

I think this is pretty much it. If I notice a possible rule missing I will post it here later for discussion, but for the time being, I would like to see others' input on these proposals. --SpecB (talk) 00:48, June 2, 2016 (UTC)

Kana only section for Japanese lyrics Edit

On lyrics pages where the lyrics are in Japanese, using both kanji and kana, I would recommend having a kana-only version for easier reading. If having multiple <lyrics> tags would cause problems, <poem> could be used instead, in the case of the kana-only part, as it would not be the main feature of the page, but it is visually almost the same as <lyrics>. --SpecB (talk) 18:59, June 20, 2016 (UTC)

There's a {{ruby}} template which adds the kana on the upper side of the kanjis. Using it takes a lot of work, but there are ways of having both kanji and kana for reading. Take for example "Ayumi Hamasaki:Carols". You have to upsize the page to see it right though. ~Steffy13~ > talk > contribs 09:36, June 26, 2016 (UTC)
I'm aware of that template, but then we'll need to make it a general policy to always use it on every kanji, following the lyrics' way of reading them. Would that work? --SpecB (talk) 22:50, June 28, 2016 (UTC)

System for custom scripts now available Edit

Hi all! A system for choosing and loading custom scripts (helpful tools to add extra functionality, written in JavaScript Wikipedia16) is now available via the "Script preferences" link in the bottom toolbar tools menu (or in the Toolbox if using the MonoBook skin).A link to the page can also be found in the Shortcuts window (press the . key, or click "Shortcuts" in the bottom toolbar). This system is very similar to the Gadgets feature available on Wikipedia Wikipedia16.

Currently, there are three scripts available, and they all add extra buttons to the editor:

  • Add Albums: Lw btn disc will try to find any album pages that link to the current song page and add them to the SongHeader template, also sorting them by their release year.
  • Selection Tools: Button_lowercase.png will change the selected text to lowercase, Button_uppercase.png will change it to uppercase, and Button_replace.png will replace all occurrences of the selected text on the page with text of your choice (useful for badly-formatted lyrics).
  • Tidy Templates: Lw Button TemplateTidy will sort template parameters by their default order and align spacing, though it'll only run on a few major templates by default (namely {{CreditBox}}, {{ArtistInfo}}, and the various page headers and footers). It can be used on any template by first selecting the template's name in the editor, then clicking the button.

Some more scripts (currently floating around in user pages) should be added soon. Feel free to try them out (though make sure to check any changes made by the buttons before saving a page, just in case!), and leave a message here if you notice any problems. Hopefully they will come in handy! - OneTwoThreeFall talk 17:53, November 16, 2016 (UTC)

Explicit images/textEdit

Hi all,

You may have seen that staff check images on Fandom, and delete those that are outside our Terms of Use. That includes images containing nudity, overly sexual images (including fetishes), and shock images. Fictional violence is usually okay, although we are harsher on sexual violence. But if violence is very extreme, or if it's real violence, then that's outside the ToU too.

We reviewed our policy a while back, and decided that album covers should be classed under art, which allows us a bit more leeway. That means we now alow simple nudity if it's on an album cover. I think that covers the vast majority of covers that would have been a problem in the past.

However, we still have limits and some of the images here are over the line.

When we have deleted images in the past, some have been restored, meaning that they have gone through the review process several times. That needs to stop. If you have a problem with a deletion then you are welcome to contact us to discuss that. But if an image is outside our Terms of Use, then it must stay deleted.

Of course, the easy solution is often an alternative or censored version. Although in the case of sex acts and sexual violence there often isn't a way to hide the image enough to remove the problem while still leaving it meaningful to show. In those cases a placeholder or alternative cover is the solution.

There is also a problem with some of the extreme lyrics on this wiki. For example, the songs of Funeral Rape are way over the line. I'm afraid those need to go. I'm happy to work with you to decide which ones go over the line.

This is something we should have come to you about some time ago, so apologies for springing this on you. Please let me know if you have any questions about all this. Thanks - Sannse @fandom (help forum | blog) 22:17, January 4, 2017 (UTC)

Glad to hear this, as it was a tad frustrating having to figure out what alternate images to use for the deleted album covers. Some albums didn't even have any alternate covers, so they needed to be manually pixellated/censored. Knowing that there's now more leeway on this means that this will have to be done less often. I am, however, a bit mixed on this decision to delete songs with extreme lyrics, as I didn't realize this was an issue (explicit album covers make sense, but song lyrics shouldn't have to be deleted as LW allows all types of songs - shouldn't lyrics be considered art as well?). If we deleted Funeral Rape's songs, we'd also have to go and delete just about every other goregrind song on here (the genre is known for its explicit lyrics in the first place) and it would just be way too much to have to "review" with the staff. Not to mention there's some gory lyrics from more well-known metal bands such as Cannibal Corpse that would harm searchability if they were deleted. As surprising as it is to some people, extreme metal does have its fans, so having the lyrics here helps them.
I understand that Staff's word is above all, however, so you likely will be deleting a bunch of lyrics either way, I'm just putting in my two cents because I'm not sure how you guys will manage to go about it. XxTimberlakexx (talk) (contribs)22:46, January 4, 2017 (UTC)
User:Sannse, User:XxTimberlakexx: I created Template:Deleted and Category:Deleted content to try to take a stab at this. You'll notice that I have already applied it to pages. I recommend that maybe admins go along and lock pages that meet this criterion. -Justin (koavf)·T·C·M 03:01, January 5, 2017 (UTC)
Edit Barring more input, I'm not going to apply it anywhere else just yet. But I figured I would give it a start. -Justin (koavf)·T·C·M 03:06, January 5, 2017 (UTC)
I appreciate the start and the template looks good, but what is the criterion here? What exactly makes lyrics "too gory" or "too sexual"? It seems rather ill-defined to me. If we start adding this template to pages, there's a lot to sift through to be deemed "too" explicit. Let's see what Sannse has to say regarding my post above before we start mass-adding that to pages or anything. We need to find an efficient way to do it and this "criterion" needs to actually be defined. XxTimberlakexx (talk) (contribs)03:11, January 5, 2017 (UTC)
I'm not sure how to go about it either :) In most cases of problem text on wikis, we just delete what we can find and rely on the community doing any maintenance needed afterwards. We simply don't have time to be more subtle. But I want to be more sensitive than that here and allow you to come up with the best alternatives. I think the template is a good solution, along with deletion of the actual lyrics pages of course. Note that in some cases, even the list of songs on the artist page is too obscene.
From those I've checked in Category:Genre/Goregrind... yes, all of those will have to go. As to where the line is, that's a very difficult question. There is a level of "I know it when I see it" here, but to try and give better guidelines, you need to remove text and images that include:
  • Graphic descriptions of sexual acts
    • Saying that sex is happening is okay, but not descriptions of how it's happening
  • Sexual violence
  • Racist/homophobic/anti-semitic/etc language (hate speech Wikipedia16)
    • There's an exception here for the n-word if not in a racist context (for example in some rap)
  • Strong gore that reaches the level of a shock image Wikipedia16
    • For example, maybe showing cannibalism and visible guts
Basically we are talking about any content that you think the average viewer is likely to recoil from in horror. I know that's vague but I think the main culprits are pretty obvious.
Do you want help in deleting the lyrics and marking the artist pages with the template? -- Sannse @fandom (help forum | blog) 19:48, January 5, 2017 (UTC)
Help wanted I'm just an average user here--more active than most but probably not a "power user" or anyone with advanced user rights. I would imagine that if you provided a handful of examples, then that would probably be helpful. Again, it's probably best if other users see this as well and that we wait awhile before widespread deployment/deletion. Simply put, if this site is violating the Terms of Use, either the site or the Terms need to change. I can understand arguments for either. The one thing that we can't let happen is for one subdomain to be out of step with all of the others--either everyone has the freedom to post shock images and racial slurs or none of us do (and if some users find that unacceptable, they can fork content, etc.) Would linking to external sources which provide that content violate the ToU as you understand them? -Justin (koavf)·T·C·M 20:24, January 5, 2017 (UTC)
Makes sense to me. I can't imagine this goregrind stuff is intended to be pleasurable to listen to. You can't sing along either, I would imagine. Since their only intention is to be offensive and receive censorship, I don't have any objection to removing lyrics that break the ToU. Placing templates that state why they were removed sounds good to me. Would it be acceptable to keep the lyric pages and edit-protect them, but with the lyrics replaced with the template (i.e. keep the SongHeader and SongFooter, including links to external sources)? ~Bobogoobo (talk) 01:32, January 6, 2017 (UTC)
> I can't imagine this goregrind stuff is intended to be pleasurable to listen to.
I'm sure people have said that about every genre at some time! - OneTwoThreeFall talk 09:08, January 6, 2017 (UTC)
> We reviewed our policy a while back, and decided that album covers should be classed under art ... That means we now alow simple nudity if it's on an album cover.
Thank you for more leniency in this regard, but I must ask what is the definition of "simple nudity"? After posting the above comment, you deleted this album art image, a photo of a shirtless woman standing next to a clothed man which I personally wouldn't even consider "sexual". It definitely doesn't meet your criteria listed above.
> a problem with some of the extreme lyrics on this wiki … I'm afraid those need to go.
I strongly disagree with this. From what I've read of the talk page archives, the wiki has always been fairly critical of censorship (our policy is specifically not to censor lyrics), and I don't think we should start censoring (let alone completely removing) pages now, especially based on the undefinable criteria of "I know it when I see it". - OneTwoThreeFall talk 09:08, January 6, 2017 (UTC)
To add to 123F's point, rather than removing the more "heinous" lyrics, surely we could instead hide them behind some sort of content warning template, rather than deleting them, so people who happen to come across the lyrics won't be able to read them unless they choose to. I doubt younger or more easily upset users are going looking for these lyrics, this will just end up punishing the fans of these artists (regardless of how questionable their lyric content will be). - Patzilla777 (talk - contributions) 13:26, January 6, 2017 (UTC)
This is going to be a loooog reply.
Koavf: Would linking to external sources which provide that content violate the ToU as you understand them?
Sadly, yes it would. We have the same policy on links to nudity/porn/ect. on other wikis. Presenting it via links is fundamentally the same as showing readers the content directly. The same goes for images behind a warning screen (it's something we tried for some more adult wikis in the past).
Bobogoobo: Would it be acceptable to keep the lyric pages and edit-protect them, but with the lyrics replaced with the template (i.e. keep the SongHeader and SongFooter, including links to external sources)?
In many cases, the titles of the songs are a problem in themselves, explicit text falls under the ToU too.
OneTwoThreeFall: I must ask what is the definition of "simple nudity"?. After posting the above comment, you deleted [image], a photo of a shirtless woman standing next to a clothed man which I personally wouldn't even consider "sexual". It definitely doesn't meet your criteria listed above.
Simple nudity is nudity without a sexual element. For example a woman standing naked in a neutral way, rather than an image with the woman in a sexual pose or (for example) obviously in the midst of an orgasm. For men, an example of "non-simple" would be an erection.
On the specific image, that doesn't appear to be an album cover, so doesn't fall in to the exception. If that were a cover, it would be allowed. Also, in similar cases on covers, it's easy for us to miss that an image is an album cover from this wiki. We don't directly see the name of the source wiki when reviewing, we have to look at a link to the wiki. So a misclick is possible. You can ping me on my talk page if that happens.
OneTwoThreeFall: I don't think we should start censoring (let alone completely removing) pages now, especially based on the undefinable criteria of "I know it when I see it".
I'm afraid this is something that needs to happen. Neither of us have a choice. But on the good side, this applies to a very small proportion of the pages here, the deletions should be minimal.
I will have to start (re)deleting some images soon. I'll leave it until Monday so that I'm around for any questions ect.
Apologies if I missed any points, please let me know if so -- Sannse @fandom (help forum | blog) 16:42, January 6, 2017 (UTC)
Is the purpose of this censoring to protect (a subset of) users from seeing things they don't want to see, or to prevent users from seeing certain things even if they want to? Because if it's the former, we can present links to external resources in a way that makes it obvious they will show offensive content.
RE: the deleted image: how do we make it obvious that an image is an album cover, if the presence of an {{AlbumCover}} template, the Album Covers category and the backlink from an album page aren't enough? — 6×9 (Talk) 16:59, January 6, 2017 (UTC)
Oops! Sorry, I missed this last comment.
We want Fandom to be a family friendly site. That makes us a resource for everyone, including our younger readers (and, more importantly, their parents). We also have some advertisers, for example Google, who have rules on what their ads can be shown next to. I realize that second reason will be controversial, but I wanted to be open with you.
On recognising album covers - we use tool for reviewing images that brings the image to us, rather than showing it to us on a wiki. We can click a link to go to the wiki, but certainly can't do that for all of the many thousands of images checked each day. That means we don't see any categories, templates and so on, just the image and the name of the wiki. When doing many images at a time, it's easy to miss which wiki the image is on, we are concentrating on the images themselves. We generally catch that it's an album cover from the shape and the general design, but I can't guarantee that we will always get it right. -- Sannse @fandom (help forum | blog) 17:47, January 11, 2017 (UTC)

I need to mention again that explicit text is as much of a problem as explicit images. That includes some song titles. I need to delete the cover of Funeral Rape - Porn Afterlife again. Sorry -- Sannse @fandom (help forum | blog) 22:48, January 12, 2017 (UTC)

I hope Lw's uploading of redacted images, following deletions by Fandom staff, and the existing censored lyrics on lw (from past contributions) shows that the fixation on "deletion" (as in removal of entire images and lyric pages) is not well grounded. It seems that this slow process of "delete >> redact" is here to stay.
As for the case of advertisers not wishing to show our explicit image beside their products, a "Viewer Discretion is Advised" template on such pages may have merit.--ES (talk) 04:46, April 22, 2017 (UTC)

Youtubers Edit


I just added a page for A Capella Science, a singer who makes videos on YouTube. Of course I set to put a link to him on this page. Since Template:ArtistHeader doesn't have a specific line for YouTube I put the link in the "homepage" field. User:EchoSierra then removed it because a YouTube channel is "not a real homepage". I have to say I don't see the point of having a criterion for "homepage" any stricter than "the guy says that's where he is on the Web", and I don't see such a criterion written anywhere. That said I'd be happy to oblige if anybody has any suggestion for better displaying such a link...?

Before anybody points it out, yes technically the link already exists on the page, right at the bottom hidden below a list of mediocre generic links, so practically invisible. This is a bit silly when by contrast the links to his Facebook and Twitter accounts (so, not his main pages) appear in the top template with big logos. --Rinaku (talk) 20:34, March 30, 2017 (UTC)

I am a mere user of the site and not an administrator who can set policy, but my view is that the model for how artists create and distribute their music is changing. I am aware of several musicians who started on YouTube rather than going through the normal “sign with a record label, make a record” model. For many of these artists YouTube was their home page to begin with and they only created their own website later in their career or when they eventually did sign with a label. So, in my opinion, if an artist says that their homepage is YouTube, then why not make it so on LW? As long as the YouTube section of the template on page is also populated in case they eventually create their own website, I see no harm in this practice. DesPhagues (talk) 06:34, April 22, 2017 (UTC)

Musical Disneys and the like Edit

Musical animated movies such as Disneys are released in many languages, along with as many versions of each song they contain. The many versions of a song are part translations, part rewriting of the original. Is there an existing pattern for presenting and linking all the songs of all versions of such movies? --Rinaku (talk) 14:47, April 2, 2017 (UTC)

Song TranslationsEdit

The {{Translation}} template has been updated (credit to Bobogoobo): if used with the |lyrics= parameter it will automatically fetch the original lyrics to display side-by-side with the translation; no more copying & pasting. See the template documentation for usage and a link to a working example. (Usage as before without any parameters is still possible.) — 6×9 (Talk) 21:55, April 14, 2017 (UTC)

Dispute about how to handle edits Edit

User:EchoSierra has asked me repeatedly to post here, so I will oblige him: As you may see per my edits to E, my approach to this page was to edit it so that several of the Other Songs were commented out in HTML. I took the opportunity to figure out what those songs were and while I was figuring out which needed to be redirected, deleted, etc., EchoSierra blocked me for a month with the edit summary "Kovafian [sic] edit to artist page, uncommented and unjustified". He later clarified on my talk that his understanding was that this constituted vandalism. He has encouraged me to post to the Community Portal regarding this incident. Do other users have the same perspective that this is vandalizing the wiki? Would other admins suggest a month-long block? Please read the exchange on User talk:Koavf for more information. Per his user page, he also actively solicits suggestions, so I posted to User talk:EchoSierra--do others have suggestions for his behavior as an admin? Thanks for your time and happy Easter. -Justin (koavf)·T·C·M 04:09, April 16, 2017 (UTC)

You hid the OS listings without an edit summary; we can't assume that even a good faith edit will be followed up on, as evidenced by many editors' unfinished projects and artist pages full of redlinks. My best advice to editors is to make good use of the Preview function and not use live wiki pages as a notepad. There are much looser guidelines on what anyone can do in their own userspace. Given your edit count and talk page history, I might expect you to be at least somewhat familiar with artist page guidelines. Happy Easter, ~Bobogoobo (talk) 04:33, April 16, 2017 (UTC)
EchoSierra's talk page history is a long, sad list of users trying to contribute and who got their work deleted with little or no explanation. And they are so sorry if only one would tell them what they did wrong, and then sometimes ES will give them the link to the appropriate existing policy, and sometimes there is no such link so he will just make up is own policy, and sometimes there is an existing policy directly contradicting ES' policy and he will ignore it until another admin steps in and tells him he has no idea what he's talking about. Good for me in that case but... *magic*.
When I pointed out a wrong typo fix, the reply was not "Yeah that was a mistake" but that of course I cannot expect his bot to know about such a corner case; what was I thinking? Someone before me got pages deleted because he did not create them in the right order. Sure, ban imperfect work, isn't that the whole point of a wiki, yay. And this recent blog post, and the first comment. Delete first and ask questions later. Then you ask questions about unclear policy here on the Community Portal and someone may or may not care to reply. In my case not.
What a sad state of affairs compared to Wikipedia where you have Please do not bite the newcomers, Ignore all rules, a Deletion process, and documented governance processes. That's the difference between a state of law and being subject to the arbitrary. --Rinaku (talk) 09:43, April 16, 2017 (UTC)

Secondary matter: deletionEdit

Per my understanding of consensus here in the above discussion instigated by Wikia staff, I created Category:Deleted content which EchoSierra deleted. Was I mistaken about the community consensus and the utility of this category? What should we do about content which breaks the Terms of Service for Wikia? -Justin (koavf)·T·C·M 04:13, April 16, 2017 (UTC)

The template {{deleted}} that was created has not been approved, documentation that explains it's application criteria does not exist. The only instances that this template was applied was by yourself:
  1. On Image file: reverted, a new redacted version of the file was uploaded.
  2. On Song page: reverted the deleted category page was a mis-creation. hth --ES (talk) 04:07, April 20, 2017 (UTC)
And can you show me some policy page about approval of templates? Alternately, do you have any better suggestions for how this community can meet the Terms of Service that it is breaking? -Justin (koavf)·T·C·M 04:54, April 20, 2017 (UTC)
I'd suggest a careful read of the Policy page on LyricWiki:Deletion. The issue, is not a case of a mere template creation/approval. The original thread seems like a more appropriate thread to pursue this matter. --ES (talk) 05:19, April 20, 2017 (UTC)
It seems like you paid no attention: I did post this as a suggestion at the above thread and the reason the above thread was posted at all is because the guidelines that you linked to are in violation of the Terms of Service of Wikia in general. As posted above by admin User:XxTimberlakexx "I appreciate the start and the template looks good" and per the staff member User:Sannse "yes, all of those will have to go". So--again--how do you propose resolving this? -Justin (koavf)·T·C·M 05:24, April 20, 2017 (UTC)
Does it not seem likely that content removal may requires a change of policy? That is my opinion. --ES (talk) 05:30, April 20, 2017 (UTC)
You are correct, since the editorial policies at this local wiki can't really override the policies of Wikia at large. So are you going to amend that policy page and undelete the work that I did? -Justin (koavf)·T·C·M 05:34, April 20, 2017 (UTC)
Please be aware that at this point in time, even if an admin applied the template and removed content, such action will be reverted, for the same reasons explained above--ES (talk) 05:47, April 20, 2017 (UTC)
Who would be doing that and why? There is content here that needs to be removed. We've known about this for several months and unless I am mistaken, no one seems to want to do anything to fix this problem. -Justin (koavf)·T·C·M 06:11, April 20, 2017 (UTC)
(outdent) Not sure that I'd call a Wikia employee stating we must delete objectionable content, "community consensus". Don't know about others, but as far as I'm concerned, enforcing terms of service is up to Wikia themselves (it's not the responsibility of us volunteer editors to enforce their corporate censorship rules for them).
Also, per the Wikia Migration FAQ (emphasis mine):
Will the site content or policies change?
Some functionality will change due to requirements dictated by Wikia's arrangement with GraceNote; however, the core features of LyricWiki will remain the same. Except as is necessary due to licensing, decisions about content and policy are in the hands of the community.
- OneTwoThreeFall talk 09:57, April 20, 2017 (UTC)
I've been asked to comment here.
Howyou deal the extreme content is up to you. A template, a simple removal, a standard disclaimer... whatever does the job. My only concern here is that content outside the Terms of Use cannot be on the wiki.
OneTwoThreeFall, that line probably should have included "subject to the Wiki Terms of Use" . But I think that most people would have assumed that, just as they would assume it was "subject to US law" (although the only time I expect that would be an issue is in cases of sexual images of minors). -- Sannse @fandom (help forum | blog) 20:53, April 21, 2017 (UTC)

Maximum Image Sizes Edit

As suggested by User:OneTwoThreeFall in the comments section of my blog post (User_blog:DesPhagues/Enhancements²), I am bringing this topic to the community portal for suggestion to change the text on the Special:Upload page of the site.

Currently album image cover sizes are restricted to a maximum of 500x500px and 150kb under the Uploading an albumcover section, supposedly due to “fair use policy”. The same text is not displayed on the Uploading an artistphoto section. Combined with the text below the Source file section Upload button (Maximum file size: 10 MB), this could lead to the interpretation that an artist photo can be of any size (Example User_talk:EchoSierra#Wham.21.jpg).

I am no lawyer, but I did a little googling and read the following articles:


It seems complicated and much of it is a grey area but my bottom-line interpretation is that we are at risk no matter what images we post.

  • “Fair use” seems to refer mainly to items that have fallen out of copyright (older than 20 years with some exceptions where it has been extended).
  • “Pictures already in the public domain” seems to be mainly aimed at use by the news media or academia.

So, not being a lawyer, I am making the assumption that, at some point in the past, someone checked the legality of the terms used on this page.

It is important to have a process for DMCA requests to be filed (which the parent site has Special:DMCARequest [2] and that those requests are acted on promptly (which I have witnessed to be the case with Chad_Siwik:Red_Flag_(2007)). It takes quite a few clicks to get to this page, so it may be prudent to add a shortcut to the dropdown menus.

Seeing as how the site does not really use large images, in the end, I feel like it would be easiest to standardize and limit both album and artist images to the same 500x500px/150kb limit.

So, I would like to propose that the following changes be made to the Special:Upload page:

  • Under “Uploading an albumcover”, point 1, the text is changed from
"Source filename": Licensing and size of the file Albumarts are included under the "Fair use"-license and therefore may not exceed a measurement of 500×500 pixels or a file size of 150 KB. If your cover image has a higher resolution or bigger file size, please resize it before uploading.
"Source filename": Licensing and size of the file Album art is included under the "Fair use"-license and may not exceed a measurement of 500×500 pixels or a file size of 150 KB. If your cover image has a higher resolution or bigger file size, please resize it before uploading.
  • Under “Uploading an artistphoto”, point 1, the following text is added:
Artist art may not exceed a measurement of 500×500 pixels or a file size of 150 KB. If your artist image has a higher resolution or bigger file size, please resize it before uploading.
  • In the “Source file” box directly underneath the choose file button, the text is changed from
Maximum file size: 10 MB (a file on your computer)
Maximum file size: 500 x 500 pixels and 150kb (a file on your computer)
  • In the “File Description” box directly under summary, there is a dropdown box for Licensing. It currently only has “None selected” as an option. If this information is saved somewhere I would propose that the box is changed to include the following:
None selected; Fair Use; I Own the Copyright; I have Permission from the Copyright Holder and Public Domain.

I appreciate that this has been a long read and apologize, it is due to the complexity of this seemingly simple topic.

What are your thoughts on the proposals? Do you have any other suggestions?

Thanks in advance. DesPhagues (talk) 18:06, April 17, 2017 (UTC)

Help Text Clarification on What NOT to add an album page for Edit

The text under the sub-heading "Do not create pages for the following": at Help:Contents/Editing/Formatting/Artists#Album_List can, in my view, be clarified to prevent possible confusion as I have experienced and seen on occasion.

I would also like to propose to add a section specifically for singles.

I propose that the text be changed to read:

Do not create album pages for the following:

  • Bootlegs and other unofficial/fan-made albums
  • Singles, EPs, live albums or single-artist compilations only containing songs already listed elsewhere, or only containing a single song not listed elsewhere, unless they are highly noteworthy (e.g. platinum-selling)
These songs should be added to the following sections of the Artist Page instead:

Any opinions before I make this change to the help documentation?

Thanks in advance. DesPhagues (talk) 09:58, April 18, 2017 (UTC)

That's basically rehashing the content of the section below. I'd rather add a single sentence like "Please see the following section on how to handle these songs" and possibly expand that section instead. — 6×9 (Talk) 10:48, April 18, 2017 (UTC)
So, how about I add the sentence: "Please see the Non-Album Songs section of the Artist Page on how to handle these songs". I could then add "Singles" as the first topic on the Help:Contents/Editing/Formatting/Artists#Non-Album Songs page? DesPhagues (talk) 11:16, April 18, 2017 (UTC)
I've gone ahead and added a section on singles. Feel free to edit if you think it needs clarification. — 6×9 (Talk) 09:34, April 19, 2017 (UTC)
And I see that you have also added the text to Help:Contents/Editing/Formatting/Artists#Album_List. Perfect, Thank You ! DesPhagues (talk) 09:44, April 19, 2017 (UTC)


Since the site appears to be down, the SongFooter links have been disabled. Please do not remove existing goear parameters: should the site ever come up again, they will be re-enabled, if not, a bot will eventually take care of them. — 6×9 (Talk) 10:27, April 18, 2017 (UTC)

Mashups Edit

I have been looking and can't find a template to replace the {cover} template in the case of a mashup[3]. I have created Sam Harris:I Gotta Right To Sing The Blues / Stormy Weather using a {cover} template for each song, but this is not a medley, the lyrics are interspersed rather than following on each other as would be the case of a medley. Any advice would be appreciated. (The same would apply to Straight No Chaser:I'm Yours / Somewhere Over The Rainbow). DesPhagues (talk) 08:41, April 20, 2017 (UTC)

There is a similar template, {{Sample}}, for songs including portions of other songs. Giving the song a quick listen, though, it seems to me more of a cover of the two songs (even though the lyrics are interspersed). Wouldn't a mashup be created from portions of the other songs? - OneTwoThreeFall talk 10:03, April 20, 2017 (UTC)
[edit conflict] Strictly speaking, it's still a cover of those two songs. I could however add a parameter to {{Cover}} to change the word "cover" to anything else, if people would find that useful. — 6×9 (Talk) 10:05, April 20, 2017 (UTC)
I think that using the following might just do the trick for me:
{Cover |song1 = Lillian Shade:I Gotta Right to Sing the Blues |addtext1 = blended with |song2 = Ethel Waters:Stormy Weather}
I have applied it to Sam Harris:I Gotta Right To Sing The Blues / Stormy Weather, is this OK with both of you ? DesPhagues (talk) 10:27, April 20, 2017 (UTC)
Fine with me, probably the simplest solution. — 6×9 (Talk) 20:53, April 20, 2017 (UTC)

Future albums Edit

How should we mark albums that are scheduled to be released in the future, if at all? At first I didn't create them until release, but they got created anyway. Later an admin added a note above the tracklist on the artist page, but another admin removed it the next time I used it. The latest suggestion (from ES) is a page notice on the album page, but yet another admin is against it. Right now I'm thinking of a template to display such a notice and add the album to a hidden category for "Albums to be released" or some such. To alleviate the latter concern there could be another category for templates needing removal, or it could just not show the notice past the release date and it could be cleaned up later. That is, if we need to differentiate such albums at all. ~Bobogoobo (talk) 01:46, April 21, 2017 (UTC)

I just don't see a point to doing this, personally. It adds an extra thing to deal with when the album comes out, and what if it gets overlooked and stays there months after it gets released? We'd be both inaccurate and behind if it stayed there longer than it needs to be. I know you're saying we could possibly set the release date on the template, and then when the album comes out, it removes itself by way of bot, or is added to a category for removal. But to me, this is just an extra step that doesn't have much of a purpose, and it's easier to simply cut out the middle man.
The way I see it, the album will get released eventually, and when it does, the other songs from it can get created. Until then, it serves as a placeholder, or a "home" for the singles from it that have been released so far. After all, most people can figure out whether an album is released or not. I create future albums quite often and I never feel the need to make any indication that they're a future album. Good examples are The Weeknd:Starboy (2016) and Depeche Mode:Spirit (2017). I created these pages quite some time before they actually got released, and someone eventually created all of the songs on them when they came out. XxTimberlakexx (talk) (contribs)02:01, April 21, 2017 (UTC)
The History of this artist from Feb 2015 up to Feb 2017 may illustrate the necessity for a template. Bob's album page is on solid ground with multiple external refs, an infobox/template is for those who may overlook the external links to verify, while the album is still not in the market. A template that expires like {{RealityCheck}} and flags the content page for attention may have merit, in case nuclear war indefinitely delays the release of a solid album and we need to remove it, The Day After. --ES (talk) 02:45, April 21, 2017 (UTC)
For what it's worth, I don't create pages for future albums unless a) the full tracklist is confirmed and b) there's a set release date. In the vast majority of those instances I've seen, that means the album is indeed getting released. But then we have special cases like the infamous Tha Carter V that has been continuously getting pushed back for years. Albums that only have a partial tracklist confirmed are the ones I don't create, which is what that example seems to be. I only list partial tracklists on the artist page itself (with asterisk'd tracks instead of numbered tracks), leaving the album page red until the tracklist is confirmed.
If there's a need for such a template, though, then perhaps we can make it work. If there's a definite way for the template to remove itself on the actual release date, I might be okay with it. I just can't see this being used on every single upcoming album since there's already a bunch of them out there. XxTimberlakexx (talk) (contribs)02:52, April 21, 2017 (UTC)
Not exactly remove itself, but you can hide the notice once the release date has passed:
{{#if:{{{1|}}}|{{#ifexpr:{{#time:U}} > {{#time:U|{{{1}}}}}||(page notice)}}
~Bobogoobo (talk) 03:02, April 21, 2017 (UTC)
So then what? Would it be added to a category to be checked on? XxTimberlakexx (talk) (contribs)03:09, April 21, 2017 (UTC)
Yes, category. But I admit I'd prefer if album pages weren't created before release, or at least until release and final tracklist are beyond doubt, in which case there'd be no need for a template. — 6×9 (Talk) 17:12, April 21, 2017 (UTC)

Clarification on use of ndashes etc. in templates/info Edit

Continuing on my quest to clarify help documentation as suggested by User:OneTwoThreeFall in the comments section of my blog post (User_blog:DesPhagues/Enhancements²)...

There seems to be some confusion about the uses of ndashes (or other special characters) in templates as can be seen from this User_talk:Koavf#Undoing_admin_edits discussion, hence I thought I would bring it to the community portal to gain clarity and update the help docs if necessary.

At issue is the fact that Help:FS#Lyrics and LyricWiki:Page_Names#Common_Misspellings.2FIncorrect_Tagging requires that ndash/emdash/ellipse etc characters be converted to the normal ASCII equivalent, but the template documentation and examples use ndashes at:

i.e.|members =<<Member 1>> <<Instruments played>> (<<Membership years>>) and <<Former Member 1>> <<Instruments played>> (<<Membership years>>)


|members = George Helper Guitar, keyboards (2005current); |fmembers = John Helper Saxophone (2005)

There may be more examples, I am just using the those from the above discussion.

So the question is: Does the requirement for character transformation apply only to lyrics and page names, or to template contents and song and album title as well?

Any official guidance on this would be appreciated, thanks in advance. DesPhagues (talk) 11:34, April 21, 2017 (UTC)

For what it's worth, I think it should be obvious that my preference is that we use typographically correct characters. It's 2017 and inputting an ndash is not difficult to do. If someone inputs a hyphen, that's fine but it should be changed when someone else notices it and has the opportunity. -Justin (koavf)·T·C·M 15:56, April 21, 2017 (UTC)
There are good reasons for not allowing them in pagenames and lyrics. I don't see any real-world reasons for the rest of our content, and use ndashes myself in ArtistInfo and CreditBox. — 6×9 (Talk) 17:07, April 21, 2017 (UTC)
I don't see what those reasons would be: can you explain them? For pagenames, I can see how that would be tricky to insert and consequently, we would need to create a lot of redirects. That I see as a potential nuisance but fairly solvable by bot. But in the lyrics themselves, why would we prefer only ASCII characters...? -Justin (koavf)·T·C·M 17:44, April 21, 2017 (UTC)
As I understand it, it is to make searching standard (and therefore easier for users), so plain ", ', - etc. characters are used DesPhagues (talk) 18:06, April 21, 2017 (UTC)
MediaWiki search is hardly perfect but it's smart enough to know that if I'm searching for "she loves me--but she broke my heart" it can return results that include "she loves me—but she broke my heart". If that's the only concern, it's misplaced. I think we should conform to proper, standard typography. The big exception might be file names where there is very little to be gained with the form File:Artist – Album cover.png (versus using a hyphen) and a huge pain to have to maintain. Note, of course, that we have tens of thousands of non-ASCII titled pages, e.g. Si*Sé:Slip Away or 宇徳敬子:あなたが世界一 or Cali≠gari. -Justin (koavf)·T·C·M 18:22, April 21, 2017 (UTC)
There are also reasons related to external site's use of the API if I understood correctly.
Also, as per User:OneTwoThreeFall's comment on my blog mentioned above, have a look at the LyricWiki:Scripts script? It's added as a button on the editor toolbar, and clicking it will attempt to tidy the lyrics (doing everything you've mentioned). Not ideal for your other points, but it has worked great for me so far. DesPhagues 2017-04-21T15:49:03

So, to close off the topic then I am going to assume that there is no change needed in the documentation. The special character replacement rules apply to pagenames and lyrics, but these characters can be used (optionally) elsewhere (like in the info boxes). DesPhagues (talk) 06:47, April 22, 2017 (UTC)

so all i did here was wrong: Madison (SE) (and other pages). I always used - never knew about ndash. This need to be written in some part to clarify. Songsbr (talk) 16:16, April 22, 2017 (UTC)
I believe that it is optional to use ndashes etc. The normal ASCII characters are absolutely OK to use, this topic was just clarifying when using 'non-standard' ASCII characters is OK... So you have done nothing wrong, your edits should be fine if you have used standard ASCII and not ndases etc. I have added the term (optionally) to the closing paragraph and hope this clarifies things... DesPhagues (talk) 17:10, April 22, 2017 (UTC)

Unexplained reverts Edit

Evidently, User:EchoSierra wants to discuss this here. Why are you reverting dozens of edits such as this? Is there something you know about Michael Stipe whispering "last date" on this recording that I don't? -Justin (koavf)·T·C·M 20:44, April 21, 2017 (UTC)

As I already explained on my talk page; The need for such a category (or any number of similar categories that anyone may think up) has not been explained. And per past experience, we keep manual categories to a minimum and only those that we need. And I see no explanation yet for such a need. --ES (talk) 21:41, April 21, 2017 (UTC)
You actually said no such thing on your talk page but I didn't create the category: I'm just populating it. It's been here for seven years, so I don't see why it's controversial for me to add (appropriate) entries to it. If you think it should be deleted that's a different story but it's not at all what you suggested on your talk. If you have no more reason than that and no one else objects, I'm going to continue populating it in 24/48 hours. -Justin (koavf)·T·C·M 21:47, April 21, 2017 (UTC)
The need for such a category = "Adding the category to the pages". --ES (talk) 21:55, April 21, 2017 (UTC)
And as I said there, the need to add it is self-evident. The addition doesn't need any further justification per se--although there may be specific incidences that do. Either we keep the category and populate it or we delete it but there's no point in having it for the better part of a decade and then one person stonewalling on actually fleshing it out for no apparent reason. Either make a justification for deleting it and thus emptying the current contents or stand aside--why remove just some of them and then complain that you don't understand why someone would add an article to a category when it clearly belongs on that category? -Justin (koavf)·T·C·M 22:03, April 21, 2017 (UTC)
From my talk page: What is the purpose of your edits? not clear what you mean by such edits. Never discussed anywhere.
Example: In the above thread Future albums a possible need for marking pages and possible categorizing of such pages is discussed. A rough outline of a template (instead of manual categories) is displayed. The template has not been applied on any pages, yet. --ES (talk) 22:10, April 21, 2017 (UTC)
Okay, but that is prospective. Again, I didn't make this category--it's been here for seven years and no one else has seemed to have a problem with it until you and now. So again, if you think it should be deleted, go ahead and propose that. Otherwise, there is no point in it being partially filled but only new additions to it are removed. What is the purpose of that? What value is there in retaining a category that you know is deliberately underpopulated because one person is responsible for mass-reverting? This is my question and in this case, it is you that needs to justify your behavior, not me. -Justin (koavf)·T·C·M 22:22, April 21, 2017 (UTC)
Please note above: Discussion about Marking pages, before actually making such edits. hth --ES (talk) 22:29, April 21, 2017 (UTC)
PS: And per past experience: example of such edits being removed (my own edit): here, was removed here. --ES (talk) 22:44, April 21, 2017 (UTC)
I'm confused about what is supposed to be relevant at the above section: #Future_albums asks, "How should we mark albums that are scheduled to be released in the future, if at all?" It is about an album page, not a lyrics page and is clearly about something relevant to a potential reader--namely, "This album is not yet released, so expect some content here to change". Other users responded with their concerns, etc. Individual songs are not going to have their lyrics change to include the title, so what would be marked? How would a lyrics page be marked? You'll have to be more explicit for me to understand what you're aiming at here. -Justin (koavf)·T·C·M 22:39, April 21, 2017 (UTC)
Re: your personal examples... Category:Artists born in 1944 and Category:Harmonica players are redlinks and as best as I can tell never existed. They are also outside the scope of a lyrics repository. Again, this is a category which has existed for several years without any particular problem and is actually related to lyrics. So my question remains: what is the point in having it partially filled but disallowing new entries after seven years of it being here? -Justin (koavf)·T·C·M 22:47, April 21, 2017 (UTC)
I hope you have understood the difference between marking pages to become members of a category (example of your and my edit that I illustrated above) and...
the category page itself, created or not. cheers. --ES (talk) 23:14, April 21, 2017 (UTC)
No. Also, what is the point in having it partially filled but disallowing new entries after seven years of it being here? If you have no answer for that and no one else objects to continuing a project that has been ongoing here for the majority of the site's existence, I'm going to keep on doing what I was doing (as I said above). -Justin (koavf)·T·C·M 23:22, April 21, 2017 (UTC)

Back on track...there are only 13 songs in the category right now. Unless there were hundreds to thousands before this week, then I think the category's deletion was simply overlooked until now. As said above, we try to keep manual categories to a minimum, and the same with lyric-trivia categories. They really don't serve much of a purpose on the scale of LW, other than to add unnecessary work. ~Bobogoobo (talk) 00:33, April 22, 2017 (UTC)

No, there were not previously many other songs. I happened to come across it as an accident. -Justin (koavf)·T·C·M 00:54, April 22, 2017 (UTC)
Just nuked the category for you. While we're on the subject, should we clean out One-Hit Wonders and Top 40 Hits in the United States? Both are manual categories I've seen around a little bit. The former only has 60 songs in it, whereas the latter has over 400. Like Bob said, on the scale of LW these categories are just unneeded work (and will basically be perpetually incomplete), so I don't see a use for them since they're not tied to a specific template (e.g. Billboard Hits). XxTimberlakexx (talk) (contribs)01:48, April 22, 2017 (UTC)
See also Category:Dis. -Justin (koavf)·T·C·M 02:05, April 22, 2017 (UTC)
Just cleared out Dis, and looks like ES cleared out the other two I mentioned. I also cleared out the Christmas Songs category, so hopefully that was the last of them. Wouldn't be surprised if there's others floating around, though... XxTimberlakexx (talk) (contribs)02:46, April 22, 2017 (UTC)

Request for GooglePlay Store Link in AlbumFooter Template Edit

Would it be possible to add GooglePlay store to the Template:AlbumFooter Template (and perhaps also add a {GP|<albumid>|<extra text>} template like Template:IT) ?

From what I can see, the link to albums on the Google Play store is quite straight forward:<GooglePlay Album ID>

For example:

I personally prefer to purchase my digital music from GooglePlay as it is generally at near-CD quality 320kbps vs. Apples' 256kbps and, well, it's not Apple. We already have a link for Amazon, so it seems only reasonable to have one for Google also ? Thanks in advance for any thoughts DesPhagues (talk) 09:52, April 22, 2017 (UTC)

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.