Wikipedia:Village pump (proposals)/Persistent proposals

From Wikipedia, the free encyclopedia
Jump to: navigation, search
  Policy   Technical   Proposals   Idea lab   Miscellaneous  

In a nutshell: If you are concerned that a proposal at Village pump (proposals) is in danger of being (or has already been) automatically archived, despite having demonstrated consensus, simply move it here. This page is not automatically archived. Discussions can continue on this page. This is not an archive.

Rationale: The purpose of this page is to provide safe haven to proposals that show consensus, but that would otherwise become (or stay) automatically archived due to inactivity before they can be implemented. It is an effort to ensure that potentially valuable proposals are not forgotten simply because there is currently no time to implement them. Developer intervention is required in order to implement most proposals, so this page is especially necessary while the developers are particularly busy with long-term projects.

This page is not an archive, so feel free to contribute to any of the discussions you see below.

Move a proposal to this page only if it meets all of the following criteria:

  • The proposal discussion has not had any replies in at least 5 days.
  • The proposal has already been described and discussed at Wikipedia:Village pump (proposals).
  • The proposal seems to have gained community consensus.

Note: This is not the place to post new proposals that have not been discussed at all yet. Post new proposals at Wikipedia:Village pump (proposals). Also, do not confuse this with perennial proposals, which are "persistent" in that they are frequently made, but have all been rejected. Proposals here, conversely, show some degree of consensus.

How to move a proposal here:

  1. If a proposal meets the stated criteria, copy its entire discussion and paste it at the end of this page.
  2. Remove the discussion from its original location, but leave its section header (== ==).
  3. In place of the discussion, post a notice of the move. Be sure to include a link to this page, as well as your signature. For example:   ''Moved to [[WP:VPR/Persistent proposals]].'' ~~~~   This is to ensure that redundant discussions don't exist or continue in multiple locations.
« Older discussions, 1, 2, 3
Centralized discussion
Proposals Discussions Recurring proposals
  • An RfC on the captitalisation of bird names.
  • An RfC about whether or not the opt-in requirement should be removed from the enwiki edit counter.
  • A proposal to reimplement the Main Page with an alternative framework.
  • An RfC regarding changing the username policy to allow role accounts.
  • A discussion on ways to improve the "Today's featured article requests" system.

Note: inactive discussions, closed or not, should be archived.

Perennial proposals in discussion[edit]

"Categorised (user defined)" or "split (user defined)" watchlists; an idea previously proposed as "multiple watchlists"[edit]

Greetings fellow volunteers.

I'd like to propose an innovation to watchlists. This is an idea that has, in fact, been discussed here before (see discussion reproduced below). I want to take up where that left off and expand on the idea a bit.

The idea is to allow users to categorise or split their watchlists. A user will still be able to view their watchlist as a whole, like now, but will also be able to view a sub-set of their list as defined by them.

Instead of a binary choice (choosing either to watch or not watch) users would be able to "add new watchlist tag/category" via a drop down menu then add a an article/page to that tag or category.

Use case #1[edit]

  • User:Janine Bloggs has two primary interests in life; the first is science fiction and the second is psychology.
  • As things stand now, Janine watches pages covering both those topics. When she visits her watchlist both her areas of interest are mingled together.
  • The proposal is to allow Janine not merely just to watch her pages of interest but to add them to sub-categories of her watchlist and view them separately if she wishes. In this way, if she's in a psychology mood she can choose to view changes only to articles she has categorised/tagged as psychology.

Use case #2[edit]

  • User:John Doe knows that some of the articles he watches are controversial in nature. The articles are unstable and there have been edit wars and a great deal of activity and discussion on the talk pages. However, there's many other articles he is interested in monitoring that are much quieter. John knows that, when viewing the controversial articles, he has to be in a certain mindset; things can get pretty ugly with personal attacks and sometimes he recognises that he might lose his cool. As such, he prefers only to view articles in his Controversial topics watchlist when he feels level-headed. If he feels he is grumpy that day he can choose to view his Other topics watchlist and stay out of heated debates. He can still view all his watched articles as one list, as now, if he chooses.

Use case #3[edit]

  • User:Dizzy tends to end up with a lot of pages on his watchlist; he habitually likes to follow up on pages that he has edited recently. However, after a while, he drifts away from them. With the new interface Dizzy sets up a category/tag for himself called "Temporary August" (the current month). As he edits he adds articles to "Temporary August". In September he checks that watchlist from time to time. In October he unwatches all the articles in that category/tag with one click.

Ideas of how the user interface would look[edit]

There's three elements; the first is a change to the user interface when viewing an article; the second is a change to the 'editing' screen; the third is new options available when viewing the watchlist.

When viewing an article[edit]

At the moment the user sees a 'star' icon; this is a binary switch which can be clicked to watch/unwatch an article. The new interface would display a down arrow next to the star. When clicked this would display the user's Watch Categories/Tags and the user can choose a category/tag to add the article to. There would be an additional option to "Create new category/tag". Alternatively the user can click the star, as now, and the watched page will just enter into his 'uncategorised/untagged' pot by default. If the article is already being watched the user can just click the star to unwatch.

When editing[edit]

At the moment a user can tick a checkbox to add a page they're editing to their watchlist. In the new interface there is an additional drop-down menu next to the checkbox which, when clicked, shows the user's Watchlist Categories/Tags and one can be chosen to assign the currently edited page to. There would be an additional option to "Create new category/tag". By default the page will be left Uncategorised/Untagged.

When viewing the Watchlist[edit]

At the moment a user will see all their watched pages together and this is still what the user will see when they click My watchlist. Currently, the user can choose from a menu and decide to view only changes to a particular namespace such as articles, project pages or books.

In a new interface there would be some mechanism to view pages assigned to the user's Categories/Tags; these could appear as additions to the namespace drop-down. But I would prefer to see them have their own mechanism. A drop-down menu requires two clicks; one to display the menu, another to choose a menu item. I think I may prefer it if the watchlist had tabs which would mean displaying all the user's categories/tags in the watchlist interface and a user can just use one click to display changed pages in that category/tag.

Things to consider[edit]

1. What is the best term to describe these 'subset areas'? Categories? Tags? Both 'category' and 'tag' already have interface meanings on Wikipedia. Perhaps something like "WatchCat" or "WatchTag"?

2. Should there be a limit to how many categories/tags a user can create for themselves?

3. Many users will already have a highly populated watchlist; how could we make it easy for them to categorise/tag their currently watched pages?

That's the end of my proposal - the earlier discussion on a similar idea follows. --bodnotbod (talk) 08:12, 13 August 2010 (UTC)

Related discussion that had previously been archived[edit]

Multiple watchlists[edit]

For organizational purposes, it would be nice to be able to maintain more than one watchlist. I've been cleaning up my watchlist every couple months but I usually end up deleting things I actually want to keep, just to get the list cut down to a more manageable size. I'm tempted to maintain an external text file or something so I can move chunks of listings in and out of the raw watchlist editor depending on what I want to look at, but would it really be so difficult for the wiki have that kind of functionality already built-in? I can't see it being an additional resource hog. Equazcion /C 15:23, 12 Mar 2008 (UTC)

See m:Help:Watching pages#Related changes feature for "additional watchlists". Although they do have some drawbacks: such a list is not private, you have to explicitly put links to talk pages, there are less options to filter the changes. —AlexSm 15:30, 12 March 2008 (UTC)
Thanks, that is helpful. However, still, I think multiple watchlists for each user is a good idea. It would offer a lot of convenience and benefit for very little performance cost, if any at all. Equazcion /C 15:38, 12 Mar 2008 (UTC)
I was going to propose something like this! I suggest that each item on a watchlist have a "flag" or parameter which could be a bit, an integer or a short piece of text which the user associates with the item.
Suppose you're going to be really busy for a few weeks. Then you want only the few articles most important to you to show on your watchlist during that time. But then afterwards, when you have some time and want to see what's happening in the general areas you're interested in, currently you have to start from scratch rebuilding your watchlist. Under my proposal, you'd only have to click one setting, "show all items" or "show all items with priority level of 5 or fewer" etc. If it's a text parameter, you could click "show all items that I've tagged with "medicine" etc. depending on what your interests are at the moment. You could also label things as "watchlisted during RC patrol" or "watchlisted when I posted a message there" so you'd know why the heck things are on your watchlist. It might also be useful if the date the item was placed on your watchlist could be (optionally) displayed. --Coppertwig (talk) 01:23, 14 March 2008 (UTC)
Yeah, similar solution, probably even better since you'd be able to see all "watchlists" at once if you chose to, but also be able to filter based on user-defined tags. I actually like that better. Equazcion /C 01:28, 14 Mar 2008 (UTC)
I like that, too. However, I think I ought to mention an already existing tool: the ability to monitor changes in all the pages that link to a specific page. John Carter gave me the idea, and applied it on SBS's Templates page; all changes made on pages linked to from that page can be seen in a list accessible from a box in SBS's main page. I can tell you, it helped me clear my watchlist a long way. One can create a subpage in one's userspace with all the pages one is interested in watching; one may categorise its contents as one wishes (with headings and sections) and has the ability to hide links (or, indeed, entire groups of links) whenever one wishes by turning them into HTML comments. This tool, which I have only recently learnt about, has many potentials in my opinion. Waltham, The Duke of 20:33, 14 March 2008 (UTC)
Yeah that's the related changes feature, see the first response to the original post above. It's a good temporary solution but the watchlist is so much more functional, easier to use and read. I think it should be expanded to include this functionality. Equazcion /C 12:30, 16 Mar 2008 (UTC)
I guess I missed that. Yes, I quite agree, it is a good provisional solution, but it definitely won't cover all of our needs. Waltham, The Duke of 17:50, 20 March 2008 (UTC)
I really like this idea. I have articles on my watchlist that I'm actively editing, but others that I just want to monitor because they've been subject to vandalism before. To have different watchlists for the different reasons you watch an article just makes sense. But in lieu of multiple watchlists, I like Coppertwig's tags idea. Elle (talk) 00:00, 25 March 2008 (UTC)
Add me to the list of people who would find this really useful.Doug Weller (talk) 13:46, 31 March 2008 (UTC)
I've been wanting something like this for a while and am glad that others do too. I like the tagged watchlist idea best. Maybe there could be an expandable list of all the different tags that you have with checkboxes between the namespace selector (has that always been there? I just noticed it now) and the most recent changes. We would have to figure out an interface for adding tags, but that should be relatively simple. -- Imperator3733 (talk) 21:52, 19 May 2008 (UTC)
I too would very much like to have them. I would like to be able to separate a/the articles I take a personal interest in as an editor or potential editor, such as my high school, because they deal with things of central interest to me, from b/the articles with problems where I have left talk page messages or otherwise want to make sure the problems are addressed, c/the articles I have tagged for deletion or deleted & want to check that they are not reconstructed, or the articles I have rescued to check if someone nonetheless marks them for deletion, and d/the general pages where I follow discussions on policy or XfDs or clean up & administrative tasks. Of course there are multiple ways around this. Besides related changes, if there are pages I know I want to go to regularly I can simply have a list of links--or keep a list of links on an external document or use bookmarks. If there are pages I want to check whether or not they get deleted I can keep a list of them, and see whether they are red or blue. None of these are as satisfactory as multiple watchlists. I have seen a few editors using a declared additional account for this purpose, but if I did this, I would have to go back to my own account to edit them. I see no reason why it would be impossible to implement multiple watchlists. DGG (talk) 14:15, 22 April 2008 (UTC)

This may or may not relate to this but how about something like this?. I still wanted to add another feature, which probably would be of greater interest to you but if there's too many changes, the whole thing will never pass. The feature would be to have a clean up button next to each change in your watchlist which when clicked, deletes the entry in your watchlist until another change is made to it. That way your watchlists is always clean. -- penubag  (talk) 02:51, 24 April 2008 (UTC)

I too like this Idea. Let each user use each list for for different "levels" of monitoring, eg. "susceptible to EL SpamLinks List" seperate from my "way to often edited talkpages List". Exit2DOS2000TC 05:57, 16 August 2008 (UTC)

~~ end of discussion as previously archived ~~

since 2008, my activity here has increased to such an extent that the watchlist is now useless--it is simply to large to deal with. I now have no regular method except to keep multiple tags open whee I have asked a particularly critical question and go back the following day, and a list of bookmarks for the pages I check daily if I possibly can, such as PRODSUM and AN/I and DELREV. (Like many admins, I check Cat:CSD almost always as the first thing whenever I start a work session.) I do point out one problem: I use automated tools now, which offer or assume I will add the page to my 'watchlist", and it would be a nuisance to modify them so they offered to each person a choice of their various watchlists unless it became routine to have them-so we'd still each need some sort of unlabeled basic watchlist. DGG ( talk ) 09:08, 13 August 2010 (UTC)
Could something like the following work for you?
Add * to your particularly critical questions. Find outstanding questions at Special:WhatLinksHere/User:DGG/Particularly_critical_questions_link_here. Remove the link when satisfied. --SmokeyJoe (talk) 12:26, 13 August 2010 (UTC)
Smokey, thanks for the idea of a work-around. But, like Equazcion, I find myself tempted to bookmark some of my more active discussions rather than rely on the Watchlist. Or I leave the tab concerned open in my browser; but that too is unwieldy and uses system resources on one's PC. Setting up a page in one's user space does work, but it is a little time consuming. So I'd still like to see something new happen with Watchlists. If I were able to categorise my Watchlist I could have a category called something like "Urgent" or "Ongoing" (or both!); being able to remove items from a category with one-click would also be key. I'm going to place a link to this discussion on this project's main page to see if it generates any further (hopefully supportive) input. --bodnotbod (talk) 09:20, 16 August 2010 (UTC)
Strangely, I came to the VP to ask a very similar question to this. I don't fully understand why it's considered "perennial", given that it's happening for the second time in three years, possibly ever. At WP:FOOTY, an indefinitely banned user (for gross incivility to the point of harrassment, vandalism, bad-faith accusations of racism against others, and pushing the definition of racism himself), is causing a kerfuffle on otherwise stable articles, using a dynamic IP. What I actually want to do is in breach of WP:NLT, but as a solution, what I would like to do is create a watchlist only account, add pages that he is disrupting to a separate watchlist, so that I can keep track and revert at a moment's notice, but as DGG says, have a useful watchlist. The problem is, I don't know how to do that without logging in- having to log out of my account and into another would defeat the entire object. --WFC-- 22:10, 21 August 2010 (UTC)
I also don't understand exactly why this is here under "perennial", and I'm confused as to the function of this page (it's different than say, a list of common CSD reasons that shouldn't be proposed). That being said, I would find user-defined watchlists to be invaluable. Anyone who patrols new pages or vandals or prods could use multiple lists. Sometimes pages are on my watchlist and I have no idea why. User-defined categories of watchlist are the solution. I'm confused: has this idea been declined multiple times? Also, isn't this a MediaWiki request, not a WP request? — Timneu22 · talk 15:11, 7 September 2010 (UTC)
Hi, Timneu. Thanks for your contribution. I've done a bit more digging. I've discovered that something along these lines has been a a feature request at Bugzilla going back to 2006! There is a long back log at Bugzilla. So I think the story is that there just isn't anyone willing and able to take this further. I would encourage everyone to go to Bugzilla, sign up and add to the comments for the bug, see if we can gain some attention. --bodnotbod (talk) 18:39, 8 September 2010 (UTC)

This would be extremely useful, and seems to be something that many people are interested in (and I haven't seen anyone who is opposed to it). What would be the best route to get this thing going again? -- Mesoderm (talk) 02:08, 31 January 2011 (UTC)

Heey great! I'm happy that I'm not alone. I am searching for something like this for years. I am low intensity contributor acros the span of 6 years and it is pain to remember exactly all important pages I need while editing. So I tended to put them on watchlist. Well, then, it was pain to use watchlist for its intended use. And of course, I would be happy to store in the mean time (by some easy way) some of the most interesting pages I visited, basically for few more future visits (either for reading or some possible edits in future or for inspiration how to approach edit in another unrelated page). In sum - many reasons to put pages fast in some avareness-list. Of course I had to trim that list, after few years. My compromise now is 867 pages in watch list. It is not full list of all important or interesting pages I need to know, I wanted to see again, but it is sometimes still too long, when really working with watch-list, especially after long time of inactivity (well I'am quite bussy in real life).
Two watchlist would be fine - with possibilty to trade items between them, if possible. The possibilty to flag - parameter the items in one's one watchlist would be also fine, maybe even better.
Whatever. Thank you for the request number in bugzilla - I am going to hum there too. --Reo + 00:13, 27 May 2011 (UTC)

Archived discussions[edit]

Below is a list of proposals whose discussions have been archived. To revive, continue, or restart discussion, copy the topic from the archives into the 'proposals in discussion' section above.

See also[edit]

Bookmarks page[edit]

Can we get this to work? There have been at least a couple past proposals for bookmarks, as well as support. What is needed in order for a proposal to turn into action? I was surprised that there was none already; the main reason I created an account. —Preceding unsigned comment added by Zhulia (talkcontribs) 14:47, 12 June 2010 (UTC)

Abbreviated Wikipedia or Childrens' Wikipedia[edit]

My first suggestion was for a 'Childrens Version' but there would be obvious difficulties in deciding the age / level at which to aim the abbreviated version.
My amended suggestion is that there should be a one-page (or two-page maximum) version for as many articles as possible. The quality and variety of the million+ wikipedia articles is phenomenal but often there is a need for a brief version. This is particularly true when homework is being done or when an overview os required.
What do other people think?? Nojoking (talk) 16:52, 4 October 2011 (UTC)

We do have the Simple English Wikipedia. Edokter (talk) — 16:59, 4 October 2011 (UTC)
Simple English Wikipedia is suitable for adults who have English as a second language, A children's Wikipedia if one were created would have articles which are consistent with a primary/middle school level of education. It would be designed to compliment the education a typical child (Age 5-12) should have and be a valuable aid for homework assignments. Washuchan (talk) 13:31, 4 February 2012 (UTC)

I am a college educated adult and I struggle with the highly technical level of many articles. The Simple English version is too basic. I would suggest creating a version or options within pages that allow for newspaper level English (not sure of what that age level or term is called) language. So many articles are only understandable to others who specialize in that topic, defeating the purpose of having Wikipedia accessible to the average user. I often want to know more about a topic in depth but do not understand all the scientific or technical language. Does anyone else agree? — Preceding unsigned comment added by Silverlockschic (talkcontribs) 16:28, 11 April 2013 (UTC)

Wikipedia articles are supposed to be understandable by anybody: see WP:AUDIENCE. There are various templates such as Template:Technical and Template:Context that can be used to mark articles that fail to be comprehensible for non-experts. It may seem a good idea to create another, less technical Wikipedia, but if people can't or don't improve articles here, it's unlikely they'll create a whole new Wikipedia of more comprehensible articles. --Colapeninsula (talk) 10:08, 15 April 2013 (UTC)
I haven't realized (until now) that Simple English Wikipedia can be looked at like a children or a less technical version of English Wikipedia. I was just thinking that it's for people who don't understand English very well. If this is the case, then the link to the Simple English Wikipedia article should be somewhere on the top, more visible, so the readers will know they can read an easier version of articles. For example the DNA article should have the link to simple:DNA somewhere near the disambiguation notes, with a text like this "Click here to see a less-technical article about DNA". Or maybe someone can create a gadget to show the link of simple:DNA at the top of the DNA article (and for all the other articles), making the readers understand that they can read a children version of articles. Anyway, in this case, only the English Wikipedia has a children's version, and other languages don't have it.
Another possible implementation is to create another namespace (like for example UnTechnical:DNA), and the page can be accessed between the article and it's talk page links. This namespace will be like an "extra" talk page if you want, and therefore it won't be needed to have it's own talk pages.
Another option is to create, for those articles that qualify, an article with the same name but with a prefix like "_simple". For example the DNA_simple article, also advertised at the top of the DNA article - either after the disambiguation note, or it can be (smartly) linked between article and it's talk page. Might be easier to implement since it doesn't imply the creation of a new namespace, which might need serious modifications in the MediaWiki sources. —  Ark25  (talk) 07:58, 7 September 2013 (UTC)
Or it can be a subpage like: DNA/Simple. This way it will be easy to implement "Did You Know" sections too: DNA/DYK, or various other points of view. —  Ark25  (talk) 08:32, 7 September 2013 (UTC)
Childrens' Wikipedia should not exist. Already existing articles should be made to explain stuff more clearly. Perhaps they could be expanded to explain what some of the terms that most children don't understand are. If that makes the article cumbersomely long for readers who don't want to see all those explanations they already know, then those terms that childern don't understand should insted give a link to an article that explains them. 5 year olds aren't even interested in reading Wikipedia anyway. It's not Wikipedia's job to add a childrens' version. It's the teachers' job not to assign homework for children of searching Wikipedia articles about a topic that's too hard for them. Children won't stay children for ever. They will get a chance later on of being smarter and able to understand Wikipedia articles more easily. There's no need to create a childrens' wikipedia just to have the freedom to lie to kids in an article to make it easier to understand, for example lying to kids that phisical objects follow Newton's laws when they really follow Einstein's laws. Children could instead be told in a regular Wikipedia article that except for really high speeds, physical objects are so close to following Newton's laws that no observations of low level experiments on Earth are ever affected by not following Newton's laws. Blackbombchu (talk) 00:50, 13 November 2013 (UTC)
...Why would a child-level Wikipedia be set up to lie? (Not that I really support this proposal when it comes up.) - Purplewowies (talk) 04:13, 8 January 2014 (UTC)

Automatically archive all reference links when an article gets FA nominated[edit]

Linkrot of online sources is a problem for all articles on Wikipedia. I think, it is especially serious, if it affects featured articles, as this damages the hard work that has gone into an article that actually becomes featured. Therefore I propose when an article gets promoted to FA status, all online sources should be archived as part of the FA process, using a system such as WebCite or the Wayback Machine. This could perhaps be handled using a bot or giving people such as the FA director User:Raul654 or his delegates access to a tool they can use on FACs, when the promotion takes places. This would help to preserve the quality of featured articles and the work that has gone into them. Toshio Yamaguchi (talk) 14:29, 5 August 2011 (UTC)

Understand that these archive sites will honor web site settings that don't allow archiving; the New York Times is one such site. ---— Gadget850 (Ed) talk 16:37, 5 August 2011 (UTC)
Anything would be better than the current system. Ideally Wikipedia itself would archive all sources irrespective of any no-spider tagging, but that's not practical here. Providing links at the very least would help with a good 50% or more of sources. Keep in mind that paywalls aside, major institutions like the New York Times are not likely to be inaccessible or disappear forever. Other websites are far more likely to poof. HominidMachinae (talk) 02:57, 6 August 2011 (UTC)
If this goes through, we should respect individual websites' noindex / noarchive settings (especially when archiving is already something you have to opt out of). Building an encyclopaedia does not trump copyright or respect for content owners' wishes. wctaiwan (talk) 14:22, 6 August 2011 (UTC)
Why should other spider operators respect our noindex settings if we don't respect theirs? Happymelon 11:00, 7 August 2011 (UTC)
  • Support - Our featured content is our most valuable content, but it is only as good as the references that support it. When the references go dead, the content is in question so it makes sense to archive as much as we possibly can. I believe WP:Checklinks is helpful with this, but a fully automated process would be much better. Automating the archiving of references would not only be helpful for our featured content, but all of our other content as well. - Hydroxonium (TCV) 03:05, 6 August 2011 (UTC)
  • Support - if it's technically feasible then it's a very good idea.Volunteer Marek (talk) 05:05, 6 August 2011 (UTC)
  • Support Who is making this happen? We can support all we want, but if someone isn't doing the job, then this goes nowhere. ---— Gadget850 (Ed) talk 11:25, 6 August 2011 (UTC)
I agree and I guess this is kind of a problem. If we reach a consensus here to do this, I know a person I could ask to bring this to the foundations attention. And if the foundation chooses to ignore this and instead continues to rule stuff out that is (in my opinion) much less useful than this would be (just mentioning these rectangular boxes at the bottom of articles) then I think something goes awfully wrong here. Just my other 2¢. Toshio Yamaguchi (talk) 15:50, 6 August 2011 (UTC)
  • Why just FAs? Why not every article? Why not just encourage (not require) all links to be archived using WebCite when added as refs? /ƒETCHCOMMS/ 17:50, 6 August 2011 (UTC)
The reason for this is, because tons of previous discussion regarding this issue led virtually nowhere. I think this more specific proposal might have better chances to actually gain consensus and reach the stage of an implementable solution. If this is successful, I see no problem with expanding this to other articles as well. Again, even after tons of previous discussions, only very little has been achieved. Therefore I am happy if we can achieve anything in that area. This does in no way imply that I am not open to expanding this to every article in the future, but we have to start small in my opinion. Toshio Yamaguchi (talk) 18:06, 6 August 2011 (UTC)
  • Support, but for any and all cited references (if they already aren't using the |archiveurl= and |archivedate= parameters). This could be accomplished by a bot or two (it would take some catching up, for sure, but it could be done). ···日本穣? · 投稿 · Talk to Nihonjoe · Join WikiProject Japan! 17:58, 6 August 2011 (UTC)
  • Strong Support. I've long considered link-rot of sources to be Wikipedia's most pressing problem that's not getting the urgent attention it deserves. User:WebCiteBOT was my last hope as everything was going so good but the project keeps stalling. I'm really hoping the partnership proposal thing below goes through.. -- œ 10:33, 7 August 2011 (UTC)
  • Strong Support Well, that's a good idea! Pesky (talkstalk!) 09:43, 9 August 2011 (UTC)
  • Support This is just so very yes. Sven Manguard Wha? 04:45, 10 August 2011 (UTC)
  • Question - Is the support we have so far enough to move this forward? - Hydroxonium (TCV) 05:01, 17 August 2011 (UTC)[edit]

I think that it would be appropriate for MediaWiki to join the Internet Archive as an Archive-It partner. This would cover all of the MediaWiki projects including all of the language-specific Wikipedias and Wiktionary, among others. --User:Ceyockey (talk to me) 14:59, 6 August 2011 (UTC)

Rather, "Wikimedia Foundation", not "MediaWiki". --User:Ceyockey (talk to me) 15:01, 6 August 2011 (UTC)
I believe this is already being investigated, among other possibilities. --Cybercobra (talk) 01:04, 7 August 2011 (UTC)
Yep, it's Kevin's ArchiveLinks project overseen by the WMF and mentioned on their tech blog. - Hydroxonium (TCV) 21:20, 7 August 2011 (UTC)

Resurrected from archives[edit]

This proposal had 100% support but not much participation. I've resurrected it in hopes that it will move forward. All comments are welcome. - Hydroxonium (TCV) 05:05, 20 October 2011 (UTC)

  • I fully support it, I think everyone does, but there's the matter of how it works. I would wish it upon no person that they be forced to do manual archiving--that's a dreadfully monotonous task that, if it can't be done automatically, should be done by the primary authors--especially as depending on the article, it's not as simple as adding the archiveurl field (Harvard citations and all that.) Der Wohltemperierte Fuchs(talk) 13:54, 24 October 2011 (UTC)
Agreed, manually archiving links is not fun. There are some automated tools for archiving though. I believe WP:Checklinks and tools:~betacommand/webcite.html make the process mostly painless. - Hydroxonium (TCV) 05:10, 25 October 2011 (UTC)
  • Question - If the archival of references is deemed to be essential for a Featured Article, then why would it not be made part of the FA criteria obligating the editors to do the archival work as part of bringing an article up to FA status? -- Whpq (talk) 14:58, 3 November 2011 (UTC)
Support - there must be a way of ensuring that references are not lost. — Preceding unsigned comment added by Wer900 (talkcontribs) 23:13, 6 March 2012 (UTC)
  • Support, no-brainer. Interchangeable 22:31, 4 April 2012 (UTC)
  • The French Wikipedia has used an external auto-archival service for their reference links for years, if I understand correctly. Might be a good idea to ask around whether the same system could be used here. Jafeluv (talk) 10:45, 27 August 2012 (UTC)
  • Support. This would help Featured Articles gain more credibility among the general public. Andrew327 20:05, 27 August 2013 (UTC)