Knowledge:Requests for comment/Memento

1174:

requirement for reading content from this site is not particularly high, and that is a good thing. That said, it takes an extra few clicks to see an old version of a page for a reason. If we wanted everyone to see the old version, we wouldn't have changed it. If someone wants to see the old version, it is possible, but the (minimal) extra time and effort help to weed out those who might inadvertently stumble across an old article (possibly vandalized or incomplete) and think it the current. To enable this, vandalism response would almost be required to include a revdel in essentially every case lest a vandalized page be what people see. Further, if we are simply enabling a standardized API (as I understand it), we lose that control over how easily one might accidentally see an old version of a page as the current (causing or reinforcing the revdel requirement). Absent giving everyone the ability to delete pages (at least from Memento), which would likely give quick rise to new, inventive forms of vandalism we generally don't have to deal with now, I cannot see this as a good thing. --

436:—Absolutely this is a good idea. In the first place the information is already available to anyone who wants to look for it. It can't hurt to standardize access through something like this extension. In the second place, and more importantly, Knowledge is itself an object of intense academic research, including research into the negotiation of revisions and the changes in articles over time. Academic interest in the social mechanics of Knowledge is growing rapidly as well. Since this would make it easier for researchers to understand the state of Knowledge at a given time I think it would be quite beneficial to them. The proposal states that this extension will make it easier to data-mine the history of Knowledge, and that will also enhance the availability of information for research. Yes, we are here to build an encyclopedia, but we are committed to building it through transparent processes as well. Let's not forget that either.— 2328:. Srsly. In principle we're supposed to; but in practice, once an edit has been reverted, the Bad Stuff is not visible to casual readers and the community relaxes a bit. Also, the number of editors with a revdel button is much lower than the number of editors with a revert button, and the latter group includes some highly active bots. Recently I found an editor who had a history of incoherent IP edits disclosing great personal detail - email address, credit card numbers, name, address, DOB &c - and requested oversight; then, trawling through article histories, I found lots more of these edits on other articles, which had simply been reverted rather than revdel'd. A tool like Memento would be a double-edged sword, in that it's easier to find the Bad Stuff that had simply been reverted - making it more visible to the wider internet but also making cleanup easier. 1233:--a work whose intended mode of use is humans reading articles--not an "ecosystem of open licensed, structured information." There are already companies sucking structured info out of WP content in order to undermine our share-alike licensing policies, recycling Knowledge's work into proprietary media. We don't have the legal means to stop them from doing that (assuming we wanted to), but it's not something we should be assisting as volunteers. They're getting the big bucks for it, let them do the work themselves. 457:, this probably doesn't affect you. It simply exposes what is already exposed by 'view history' but in a more computer-friendly manner. As for the argument that people are already breaking the intentions of Knowledge's share-alike licensing by extracting facts from it and then storing them in proprietary, copyrighted databases... yeah, well, the solution to that isn't to stop technological advancement until we have a way of cracking down on the big bad pirates. That way lurks 1120:(Re Shawn, Nouniquenames) The extension only makes pages that are already available accessible, via a standards based mechanism as well as the existing history pages mechanism. One of the main strengths of Knowledge is its openness and transparency about the editing process and history. Being able to see old revisions of a page is an important aspect of the credibility of the site. The Memento protocol and extension do not take any standpoint on what 1392:. To say otherwise is to misunderstand software development. By the same logic, we could have stopped at the first functional version of MediaWiki. There will always be bugs, bugfixes, new features, and testing against bloody everything that is added or tweaked later. Further, not only does it not help us, it duplicates an existing functionality. Also, it apparently has not even begun. Please read the intro: 582:

towards Web 3.0 aka the Semantic Web, it is crucial for WP to support it early on. This is what the Memento extension will do: To provide a well-defined interface between the Semantic Web and Knowledge's versioning system. In the Web 3.0 world of linked open data, it is state-of-the-art to maintain a revision history and to expose it to other technical systems in a standardized way.

936:. This will allow history browsing across websites in a consistent way, and we'll be the biggest participant, creating great value for Memento all by ourselves and also encouraging many others to participate. I would also find it personally interesting to browse Knowledge at a fixed time in the past, to get a "feeling" for how things have changed over time. Very much worthwhile. 2007:? And further, will this extension make it easier for other sites to save deleted contributions? In other words, even though a page is deleted, through the momento standardisation, will the bots now be able to copy any edits (deleted and otherwise) and install them at their own wiki, and now they can undelete at their site, etc. This has privacy ramifications etc. 2376:

a good criticism of Memento: it's like opposing a wheelchair ramp being added to the local school because it'll allow paedophiles in wheelchairs to break in. Making access to old edits is a good thing: they have substantial educational value for people wanting to understand the history and culture of Knowledge and the history of the subjects we cover. See the

126:). It will also allow bots, web services and applications to perform time series analysis by extracting information from the article (text mining, data extraction, etc) and to retrieve and integrate time-dependent information from different data sources. As such, it will contribute to building a key piece of infrastructure for the W3C 2375:

So, in response to your not caring about whether it makes life easier or harder for third parties: the point of Memento is that it makes it easier for readers to access Knowledge content as it was in the past. As for old edits that should have been revdelled: they are still accessible now. This isn't

2146:

You have made clear that hidden revisions would not be exposed by this new interface, so it does not amount to publishing any more information than is already available via the History tab. Also, users would presumably be well aware that they were not viewing the most recent versions of articles (and

1792:

It would retrieve the old version of the page exactly as in the history for the category. The links would not be rewritten to point directly into other history pages, but clients such as the MementoFox browser add-on, take care of this for you. Thus, if you set your datetime preference to be August

1410:

No, it hasn't been evaluated by Ops yet. The extension has been fully developed by the MementoWeb developers, and evaluated to make sure it's compatible. There seems to be a misunderstanding about how MediaWiki extension development works; the WMF doesn't write all of them (or even most of them); our

1101:

We take a very incremental approach to creating content, here. Early versions of articles may be unreliable, biased, wrong, spammy, flawed in any number of ways, which professionally written and edited content sites are not. While I'm sure there are many cases where valid content has been lost, such

746:

that there is no objection from the WikiMedia Foundation legal team. Opponents' concerns are met by the fact that readers will be aware that they are not looking at the current version and will therefore appreciate that pages will be more likely to contain inaccuracies which have since been corrected

589:

Historians and all other researchers (including citizen researchers and all Wikipedians) when taking a historical view on some subject need to investigate their subject in the light of resources as they were at the time, i.e. not only from hindsight. If I understand Memento correctly, then it aims to

2169:

Well, the RfC was started by a pair of staffers in their professional capacity - but you raise an excellent point. I don't see a problem myself, but I don't work for Legal; I'll check in with them today (if I can find them. It's Labour Day, apparently, which means the dang 'merkins get the day off).

1643:

If you use firefox, you can install the mementofox extension and see for yourself how it works. This works with wikipedia now. It makes all the links act as if they were in the chosen time period. I've found this to be useful for rescuing deadlinks; you look at a version of the page when the link

1557:

That depends a lot on which "us" you're talking about :) If you don't ever want to see old versions of articles, then it doesn't benefit or hinder you at all. On the other hand, if you want to browse wikipedia as it was in the past, it's a huge benefit to not have to go back through the history list

1335:

What leads you to believe - no need to answer, because the question is rhetorical - that it wins any hearts and minds for the Support side to rebut every single Oppose voter, any more than it's the case anywhere else on Knowledge? I stated my position. I am not minded to change it just because you

2150:

On the other hand, the interface is intended to make accessing non-revdeleted revisions easier, and inaccuracies are often simply reverted rather than revdeleted, so remain visible in the history page and under the proposed interface. On balance, I don't think that is objectionable, but it would be

1438:

I simply don't understand what value this will give us. Page histories are already viewable, except for where we wouldn't want them viewable. How will having another way to access old pages "help referencing"? We can already access old pages and Knowledge is not a reliable source. I'm open to being

581:

Ask yourself why Knowledge is not created on paper, like most encyclopedias before. It's because the Web lends itself well for collaboratively creating and using an encyclopedia. As the Web progressed towards Web 2.0, WP got a little bit left behind in technical terms. As the Web further progresses

2308:

However, I think it could have some advantages in dealing with problematic editing. Not the blatant vandalism, but the stuff we have more trouble dealing with - sneaky vandalism, long-term pov-pushing, subtle copyvio, &c - could perhaps be easier to handle if we had Memento in our toolbox. For

1453:

So, us turning it on does not directly help referencing. What it does do is lend extra support to the protocol - which already has orgs like the W3C behind it - and promote its adoption. If it gets adopted widely, it solves the perennial linkrot problem; sites that revise their pages but have this

1369:

And I agree that it should totally be discussed. Can I suggest you look at the discussion section, particularly the bit about server resources? Of particular interest is the line "The performance hit for a TimeGate request is significantly less than generating a history page, as it doesn't need to

1156:

My (potentially flawed) understanding is that visibility will be the same as for any current user without special rights. Any revdel might show up that a revision was deleted, but it would be impossible to see what that revision was or what it contained. If I'm wrong, someone please correct me.

307:

The performance hit for a TimeGate request (please give me this article at this time) is significantly less than generating a history page, as it doesn't need to build a list of revisions, just find the single version closest in time. As such this would be an advantage, performance wise, if people

252:

The version of the Knowledge article retrieved is the one that was live at the chosen datetime. MementoFox currently uses a proxy setup to retrieve revisions from wikipedia. This proxy uses Knowledge's XML interface and hence is slow; native support for Memento in Knowledge would yield much better

1580:

to see the latter article as it was on 1 Jan 2008 and so on? With transcluded templates and so on also as they were on 1 Jan 2008? If so, that would be great and I'd be a strong supporter. But if not, then providing only a partial solution has the potential to mislead people into thinking they're

1173:

I'm not against the ability to view past revisions. I'm against making it easier for any random passer-by to grab an old, potentially inaccurate version of a page without doing so via specific, deliberate, intentional, locally controlled steps. (I hope I stressed that enough.) The intelligence

1011:

If someone decides to make a copy of a page which is later revdeleted, Knowledge can't do anything about it. This wouldn't change with the new extension; so yes, there is a chance revdeleted content could be accessible if other websites choose to make a local backup of Knowledge. This would mean,

311:

The performance of the TimeMap request is almost identical to that of generating a page of History; they both need to know 500 revision ids, however the TimeMap does not include diffs or anything else, just the links. Furthermore, TimeMaps are able to be cached, which would reduce the load on the

1863:

The performance hit for a TimeGate request is significantly less than generating a history page, as it doesn't need to build the list, just find the version closest in time. As such this would be an advantage, performance wise, if people were to use it. The performance of the TimeMap request is

1194:

that the Memento extension is so important. When taking a historical view on any matter, it is crucial to be aware of the fact that Knowledge at the time may have had an article about it that was very different from what it is at present. See more of my reasons for supporting this request above.

275:

No. It only makes accessible those pages that are already accessible via the history pages and the existing revisions API. It does not (and can not) make deleted pages accessible. The earlier version of this extension had an option that allowed deleted revisions to be displayed. This feature was

109:

Memento solves these problems by developing a standard way for individual websites to expose their own revision histories and for clients to negotiate these histories. MediaWiki, of course, already provides access to old article revisions via page histories and via its API but it does so without

58:

This is a preliminary RFC to assess community interest among English Knowledge users for this functionality. No significant commitment of Wikimedia Foundation engineering resources has been made yet. An early pilot would likely run on the English Knowledge; hence the initial poll is taking place

1228:

versions of articles. Last thing we need is more wars about trying to rewrite the past (through revdel campaigns). More deeply, I disagree with the concept that we should "spearhead the linked data vision of an interoperable ecosystem of open licensed, structured information". We are here to

2186:

FWIW, we already note that "This is an old revision of this page ... it may differ significantly from the current revision." when you look at a history version. (I would love it if this box was more emphatic!) Readers using a complex opt-in web history tool are probably more likely than casual

1904:

Thanks for the quick reply Azaroth. I still support the idea but I have some trouble with the User namespace being a part of it. Sometimes people put person info on the User page, some with the understanding that it applies primarily to WP because most mirror sites don't pull that data in so I

1527:

Hi Victor. The protocol provides a method of making old versions of web pages available in the same way across different sites. It doesn't say anything about how the pages are stored (eg Wayback stores in special WARC files, Mediawiki in a database). The extension just turns on a more client

1266:

I find persuasive the argument that our purpose is to build an encyclopedia, and that Memento does not aid in doing so. The point of the Wayback Machine is to view webpages or content that have expired or been deleted. We already have the means to do so on Knowledge, but since our goal is to

1058:

ways for the public to view deleted content. For example, currently we have an informal gentleman's agreement with Google that they will very promptly remove deleted content from their caches. I'd be willing to support turning it on for now, but if it results in much easier access to deleted

551:

This is all a little over my head, and I had never heard of the Momento extension until now. However, if everything works as this proposal says it does, then I see no reason not to enable it on the English Knowledge. I have read the opposition and see no argument that seems compelling to me.

1994:

I've read over the extension several times. And get the idea that deleted revisions while standardised through momento, will not be viewable except by those with the ability to view deleted. Same with oversight, etc. (And does that mean we will be even more vulnerable to a compromised admin

1083:

this. Pages are often in a state of flux for a reason. In theory, they are being made progressively better and more reliable. If someone has a real reason for looking at a past revision, it can be done using the current system. I am against making that any easier for the casual reader.

453:. Standardising the process of getting old versions of documents seems a good idea. The opposes are unconvincing: this really is just technical plumbing, I don't see any particular reason why the community ought to be opposed. Put it this way: if you've never used the command line tool 712:

assuming that the extension won't be a significant detriment to the speed of the MediaWiki software. I don't know if the Memento protocol will catch on, but it certainly sounds interesting, and I believe that, as Wikipedians, we should always strive to be on the cutting-edge. ❤

162:

Memento makes no visible difference for editors. We're certainly not moving away from page histories or revisions. The difference is going to be that browsers that support Memento will be able to search our content using a format standardised with other parts of the Internet.

1124:

be accessible, and if a revision should not be accessible, then there are existing mechanisms to deal with that. The extension would simply make it easier for editors to find the older pages, in order to make the determination as to whether to restore previous text or not.

2304:

I doubt that improved access to prior versions will be a great advantage to conventional content-building. Maybe a little. We improve articles in a series of edits, each better than the last; in that context why would improved access to earlier (less good) versions be so

2320:

high since most third parties are interested in our current content rather than past content. Objecting on the basis that somebody might find it easier for somebody to use content, when our whole mission is to provide content that's open for others to use, seems odd to

110:

using a standardized protocol that other sites also use. Supporting Memento will allow readers to negotiate Knowledge's contents (and any other Memento-compliant website) to return the revision of a given article matching a specified time or time range (for example:

1924:

So will this include the revisions of a page for the month of its existence prior to speedy deletion as a BLP attack page? Being the encyclopedia that anyone can edit, means there are a lot of edits which occur which may be considered problematic to say the least.

1864:

almost identical to that of generating a page of History; they both need to know 500 revision ids, however the TimeMap does not include diffs or anything else, just the links. Furthermore, TimeMaps are able to be cached, which would reduce the load on the database.

1793:

22, 2006 and clicked on a link in a page, it would take you to the version of the new page closest in time to August 22, 2006. If you install the MementoFox browser add-on, you will see how it works via a (slow and computationally expensive) proxy based solution.

786:

The possibility to see a whole article the way it was — not just the wikitext of that article, without reflecting earlier versions of transcluded elemented as well — is a big feature. That alone makes it worthwhile even aside from the broader linked data ecosystem

1035:

This extension would definitely have to honor your user privileges on Knowledge: if you can't access a deleted revision, you won't be able to negotiate it via this extension either. JmaJeremy is totally right about third-party reuse of Knowledge data, check out

749:

Interested readers will benefit from support for a full point-in-time view of (non-revdeleted) pages, including any transcluded pages (unlike the limited existing functionality of History links, which misleadingly show the current version of any transcluded

256:

After navigating through a few wikipedia articles, we arrive at a memento in the Dublin Core wiki. This is a MediaWiki with the Memento extension installed. From here, we navigate to an external link, and the memento is fetched from the UK National

951:

I won't say I oppose it, but is it really such a great idea? Do we really want to make past versions of our pages (with all the vandalism, libel and unwanted personal details they may contain) any easier for the world to access than we do already?

789:

So it looks like the extension doesn't handle template histories without adding a hack to the parser. Still, maybe in the future (when parser performance isn't so critical an issue) that can be enabled. and in the meantime, there's still not much

180:, where sites archive their content or delete it from public view creating dead links and obsolete references. A standardized method to pull up what a page used to look like at a given point in time makes referencing easier and more reliable. By 171:

Knowledge and the Wikimedia movement projects are leaders in the field of open data, offering unmatched transparency and open licensed content. By making it easier for Knowledge to be syndicated by humans and machines alike we help spearhead the

678:. This project is an excellent idea for the web, and hopefully will be widely adopted. Knowledge has always been very open about making article histories available, this is simply a logical step to make them accessible in a standardised way. 822:. Promoting historianship and data archaeology is exactly the sort of thing that we should be doing as the world's largest knowledge project. The arguments presented below against this are nothing but handwaving and scaremongering. — 104:

it's limited to as many versions as the IA's servers can cache; specifically for Knowledge, the Internet Archive will only have a very spotty coverage of article versions, compared to the full article revision history accessible in

1977:). From our article, "Robots.txt is used as part of the Robots Exclusion Standard, a voluntary protocol the Internet Archive respects that disallows bots from indexing certain pages delineated by the creator as off-limits." -- 1854:

The extension is a generic MediaWiki extension. Sister projects would have to enable it themselves, based on their own discussions, one imagines. I defer to Knowledge folk as to different languages, but assume that it

1468:

I still don't quite understand this. We're told that Knowledge's having this protocol will merely make available, in some more robot-friendly way, the historical revisions that we make available already. But apparently

2361:

My understanding is the extension would not make any data public that is not already. However, it may make it easier to stumble across reverted revisions without trawling through long page histories looking for them.

1102:

as in edit wars or plain vandalism, I'd rather editors make a determination and restore it themselves, rather than allowing searches to sift through all the previous versions of articles for anything one might find.

1001:

Correct. It's a standards based way to get to pages in history, it doesn't make anything accessible that would not be otherwise. It is a very different question whether or not past pages should be removed completely.

2309:

instance, when dealing with neutrality problems which span several articles that touch on some controversial issue, I often find myself trawling through the histories of several articles. However, I'm not yet sure

2068:

2.) As I have already said, I've read the extension which notes that that is the intention. But a quote about a certain road being paved with good intentions, comes to mind. hence why I am asking these questions :

1542:

Let me get this straight... the proposal doesn't have any benefit whatsoever for us... it's about us setting an example for others to follow and if other sites that we use as RS ever follow suit, we will benefit?

1320:

No, the extension has already been developed. It's done. We're talking about how to turn it on. Yes, it'll take some server cycles - but this isn't going to be enabled unless Ops confirm that it scales.

2262:

This is exactly how it works. If you have your datetime preference set to 1/1/08 and you click from one article to the next, you'll end up at the version of the clicked on article from that same date.

97:", which allows you to view versions of websites as they were at certain points in time. While it is useful for broad coverage of the history of the web, the Wayback Machine has certain disadvantages: 2187:

browsers to be aware of this, but I think it would be quite reasonable to have a (click-to-dismiss?) banner across the top of all pages reminding them of the Knowledge-specific risks of older content.

590:

automate surfing the Web as it was at a given point in time. People who use this service will be aware that they are looking at historical versions -- this is just what they want from this service. --

2300:

I will either strongly oppose or strongly support this, but I haven't decided which yet :-) the implications are complex and I would urge people not to make reflex judgements on something like this.

1394:

This is a preliminary RFC to assess community interest among English Knowledge users for this functionality. No significant commitment of Wikimedia Foundation engineering resources has been made yet.

1991:

Thanks MZM. And nod, though also whether such revisions will now suddenly be open to be mirrored through bypassing robots.txt. I don't know enough about momento to knowhow this will affect things.

2234:

My vague memory of having Memento described to me in a web-archive context is that it would allow date preferences to carry through to linked pages (where supported) - you'd read the article on

766:, it seems that transcluded text is unlikely to be updated in the current implementation, so the rendered text will be the same as viewing the relevant History link. Still no downside though. — 1247:

How would this extension aid them at all, unless they really really wanted to publish a book on "every version of the article on physics ever" instead of a book on "the article on physics".

2316:

I don't care, much, whether Memento makes life easier or harder for third parties (ie. anything outside the sphere of enwiki content, editors, and readers). I don't think the stakes are

1835:

Does it include all namespaces (especially non article like File, User, Special, Mediawiki, etc.). If so how will it reflect images or articles that have been deleted due to copyright?

2147:

transcluded templates), and hence would appreciate that they might be more likely to see inaccurate or potentially libellous information than if they were reading the current website.

1037: 1838:

It does not include namespaces for which there is no history, such as Special. So it works for User (eg User:Azaroth42) and User_talk but not Special (eg not Special:Preferences).

2001:

Right now, At the internet archive (and other such places) I can look at a previous version of a page, which has since been deleted. Will this extension allow that from Knowledge

2350:

I agree with the above, and the last point is a big deal breaker for me. But as I yet dunno what's going on with deleted revisions, I'd like to see the test version first. -

695:. It's unlikely to make much of a difference to casual readers, but this is a very useful tool for the small community who use it, and the costs of implementation are low. 89:– aims to "make the history of the internet accessible" and bridge the gap between a current resource and its prior versions. At the moment, the closest analogy is the 2245:

Does the MediaWiki installation work like this? If so, it'd make a more compelling case for its usefulness than the examples above, which are all one-page scenarios.

1054:

I get the argument that anyone could be mirroring later-deleted content now. The concern that I and others share is whether this would lead to the creation of much

1851:

Is it for English Knowledge only? What about the other languages, commons or sister projects like Wiktionary and Wikinews? Each will have its own issues with this.

1012:

however, that each of those other websites would be responsible for any copyright violations and claims of libel, which are the primary reasons for revdeletion.

636:

Indeed. It is not possible from outside of the system. My point was that this (viewing historic versions...) is currently possible from the Knowledge site. --

2313:

Memento would help us with this - it might be helpful to explore some more use-cases &c..? The obvious answer to that is that a trial would help, of course.

987:

From what I understood, implementing this proposal will only make the already public information available in a format conforming to the Memento specification.

2021:

1) Access to crawlers is guided by robots.txt file. All the old revisions in wikipedia are in the /w/ path and the robots.txt file for en.wikipedia.org reads:

2408:

pilot of Memento on the English Knowledge, provided that it does not make content not already available through the History tab available to Memento users.

1644:

was live, click on it, and it takes you to the archived version of the page, which can then be inserted into the current version of the wikipedia article.—

362:

for all reasons mentioned above. Knowledge should continue to be a pioneer for open data. (Although would this not be a discussion better suited to Meta?)

1355:

oppose vote :). And I've not explained that I think this extension is Wicked Cool; I've explained that your one reason for opposing it is somewhat weak.

2065:

1.) Thanks for the clarifications concerning robots. Though I'll note that we've long seen that there are bots which ignore the exclusions in robots.txt

249:

After retrieving the archived copy (a memento) by choosing a particular datetime (07/12/2012) in MementoFox toolbar, we navigate to a Knowledge article.

2276:

Thanks. I suspected this was the case, but I was having trouble persuading Firefox to place nicely with a test MediaWiki installation to confirm it!

277:

lists.wikimedia.org mailing list. The extension had the following constraints to display deleted revisions in the previous version of the extension:

1598:

brought up on my talkpage the idea that it would be consistent; I can't verify directly (I'm not one of the devs!) but I'll ask them to jump in :).

239:

The video shows seamless web navigation in the past across multiple systems, each of which uses different methods to archive their past revisions.

1230: 1750:

With that patch it would be amazing. It's always been frustrating that we can't easily go back and see what heavily templated pages (such as

1286:

So, you oppose it because it doesn't contribute to our goal. What is the cost or undermining of that goal that this extension creates? :).

1234: 924: 2078:

how this would work? This was done prior to the implementation of the filter, and I think it would help deal with concerns about this. -

661:. Clearly we will have memento in other webapps integrated. Web of Data needs a fourth dimension. Again wikipedia would be leading edge. 1370:

build the list, just find the version closest in time. As such this would be an advantage, performance wise, if people were to use it".

478:: it's harmless. It duplicates the page history mechanics with the off-wiki standard way. That said, I would be more enthusiastic about 2010:(I'm hoping the response is: "Chuckle, and no, you don't understand what this will actually do, let me more clearly explain..." : ) - 113: 1454:

protocol will have "old" versions still stored that we can link to in a way standardised internet-wide. That's the ideal, anyway.

2242:

was president, and then click through to that article, where it would retain the date and give you a version as of 1/1/08, etc.

1024: 374: 319:

Will transcluded template content also be backdated? (At present, old article revisions always display current template text.)

150:

that would allow Knowledge and other Wikimedia projects to support this protocol. A working browser plugin for Firefox is also

1649: 441: 280:

The feature is turned off by default and if needed, it should be turned on in the LocalSettings.php file during installation.

82: 17: 2208:

I've spoken to Michelle Paulson over at legal; she has no objection as long as it doesn't make visible anything that isn't

574:. Some doubters were asking if Memento aids our purpose to build an encyclopedia. From what I understand, it clearly does. 39:

No further edits should be made to this discussion. A summary of the debate may be found at the bottom of the discussion.

1945:"It's a standards based way to get to pages in history, it doesn't make anything accessible that would not be otherwise." 1754:) looked like in the past. If it's really that simple, and wouldn't cause any problems performance-wise, I'm all for it! 1336:

think this extension is Wicked Cool. If you want to debate it, take it down to the section clearly marked "Discussion."

176:

vision of an interoperable ecosystem of open licensed, structured information. Memento also helps tackle the problem of

1774:

for 22 August 2006? Would it somehow show the pages that were in the category then, or the pages that are in there now?

2381: 1107: 722: 608:

Note that all of that is possible within the existing Knowledge system without adding to the concerns noted below. --

333:

to the MediaWiki core (tested on version 1.8) that would enable old articles to display their corresponding templates.

210: 499:. Wow. An amazing idea. It's virtually always good to standardise with other major websites, because building the 2143:

Have you consulted WikiMedia Foundation for confirmation that their legal staff have no objection to the proposal?

1581:

seeing a version that existed then whereas in fact it didn't, which might go against the spirit of the protocol(?)

184:

we pave the road for other projects and organizations to do the same. Some major players already have, including:

2093:. We'd have to stick it on test.wikimedia or prototype.wikimedia before deployment anyway - one of those, maybe? 1645: 458: 437: 388:- Although there are some discussions that need to be had about it I think its a good idea and worth supporting. 1966: 1771: 1709: 1238: 2194:

for those inaccuracies and oddities - "what was being reported about X on this day, before we knew about Y"?)

2056: 1667: 1807:

If you were replying to my question, I think you misunderstood it. If not, feel free to delete this comment.

1629:

Yes it will. We'll make a screencast to demonstrate it. Thanks (and to Andrew) for bringing up this aspect.

1401: 1311: 1179: 1162: 1089: 641: 613: 503:

is an important goal. This is only going to enable computers to do something that's already human-doable.

86: 2072:

Would it be possible to create a temporary wiki, port a few hundred edits of varying types to it, and show

1306:

It takes time and resources (of servers and developers) which could be put toward other issues, for one. --

2217: 2175: 2098: 1620: 1603: 1496: 1459: 1252: 1208: 1103: 904: 627: 595: 2052: 1998:

I don't understand how all this will work, and maybe it's because I don't quite understand the extension.

1663: 146:

aimed at interlinking resources with their archival/version resources. The Memento team have developed a

2281: 2250: 2199: 1473:

having this protocol will magically cause them to make available lots of historical revisions that they

1397: 1307: 1175: 1158: 1085: 811: 700: 637: 609: 622:

Not at all; there's currently no interaction between our versioning system and the wider semantic web.

2389: 2159: 1730: 1586: 1582: 1518: 1514: 1482: 1478: 1337: 1272: 973: 957: 953: 868:

I'm persuaded this will be useful and won't make it easier to access deleted articles and revisions.

771: 757: 466: 297:

This feature has been removed from the extension now and hence no deleted revisions will be accessed.

2337: 2267: 1982: 1892: 1798: 1634: 1563: 1533: 1416: 1375: 1360: 1326: 1291: 1130: 1019: 917: 885:. I see no reason why not, the opposers didn't convinced me why not to turn on this great feature! 873: 525: 402:

I don't see why not, provided deleted revisions or pages are not made visible using this protocol.

369: 322:

No, current MediaWiki API does not permit extensions to alter templates transcluded in an article (

139: 78: 2030:

Hence, no bots have access to these old revisions and memento does not change anything about this.

1843:

If an article or its content is deleted due to Copyright via how is that relayed through Memento?

1528:

developer friendly way to say "I want the version of (article) as it was at (date and time)." HTH

1712:

for 22 August 2006? This category contains a template which had been modified significantly (see

988: 795: 487: 2416: 2393: 2366: 2356: 2341: 2285: 2271: 2254: 2221: 2203: 2179: 2163: 2120: 2102: 2084: 2060: 2016: 1986: 1956: 1937: 1914: 1896: 1879: 1814: 1802: 1781: 1763: 1733: 1671: 1653: 1638: 1624: 1613: 1607: 1590: 1567: 1552: 1537: 1522: 1500: 1486: 1463: 1448: 1420: 1405: 1379: 1364: 1346: 1330: 1315: 1295: 1281: 1256: 1242: 1212: 1192:

arly versions of articles may be unreliable, biased, wrong, spammy, flawed in any number of ways

1183: 1166: 1151: 1134: 1111: 1093: 1068: 1049: 1030: 996: 982: 961: 940: 928: 908: 891: 877: 860: 843: 814: 799: 775: 730: 704: 687: 670: 645: 631: 617: 599: 565: 546: 529: 512: 491: 470: 445: 428: 411: 397: 380: 354: 283:

With the feature turned on, only users with appropriate privileges can view these deleted pages.

1931:

And what about robots.txt? will all those pages' revisions be included? Will all talk pages? -

1439:

persuaded, because I know I'm not a techie and I can't believe I'm understanding this right. --

747:(in some cases, it might even assist with spotting vandalism which has subsequently crept in). 233: 2213: 2171: 2094: 1951: 1910: 1875: 1758: 1616: 1599: 1548: 1492: 1455: 1444: 1248: 1204: 900: 739: 682: 666: 623: 591: 508: 393: 350: 151: 2277: 2246: 2195: 2116: 1811: 1778: 1595: 1045: 992: 887: 808: 696: 542: 407: 196: 147: 90: 51: 752:

Readers who don't want the new interface won't have to use it, so there is no detriment. —

323: 2385: 2155: 1727: 856: 767: 753: 719: 462: 121: 94: 1846:

As above, it is not retrievable via Memento if it is not retrievable via the History tab.

967:

Is there a mechanism that would prevent viewing of pages that have been rev-deleted ?

2333: 2263: 2239: 1978: 1888: 1831:

I support the idea but I do have some concerns about it in addition to the ones above.

1794: 1744: 1630: 1559: 1529: 1412: 1371: 1356: 1322: 1287: 1126: 1064: 1014: 1003: 869: 521: 479: 424: 364: 2108: 263:

Note that after MemenfoFox is turned off, the current version of the page is reloaded.

2363: 2235: 937: 828: 791: 563: 483: 30: 2377: 2410: 1948: 1906: 1871: 1755: 1720: 1544: 1440: 679: 662: 504: 500: 389: 346: 2047:

2) Deleted revisions will not be accessible using this extension. Please refer to

2112: 1808: 1775: 1041: 538: 403: 203: 173: 143: 127: 1970: 852: 807:; leading the way with Web standards like this is exactly where we should be. 714: 1491:

Because they'll have a standardised way of storing them they currently lack?

2352: 2080: 2012: 1933: 1751: 1147: 1060: 420: 1928:

And this doesn't even get into edit warring or patent nonsense or privacy.

1743:

TL;DR: It can work if a small patch is also included into the core parser.

1572:

So would this extension allow me to do that? I.e. look up the article for

1740: 823: 556: 330: 242:

The video starts with LANL's memento experiment page. This page uses a

236:

demonstrates Memento navigation using the MementoFox browser extension.

177: 1995:

account/admin tools gained on the sly just to robot-copy everything?)

1509:

a way of making them available, and Knowledge plans only to use the

537:. Please implement this important standard for others to follow. -- 276:

added after the feedback we received from the wikitech-l <at: -->

101:

it's limited to those sites the Internet Archive is able to access;

71:. A link typically takes you to the current version of a resource. 2190:(That said, I suspect many people will be reading it this way to 2423:

The above discussion is preserved as an archive of the debate.

2332:

Those are my principles; if you don't like them, I have others.

1905:

imagine some users are going to have some heartburn about that.

454: 1040:

if you are interested in the survival of revdeleted content. --

260:

We follow a link in this article to navigate back to Knowledge.

243: 181: 1411:

volunteer developer community is responsible for quite a few.

1139:

Whoa, wait. So deleted revisions will be shown, it's just the

189: 138:

Memento adds support for datetime negotiation (a variation on

1576:

as it was on 1 Jan 2008, and click a link in that article to

1974: 1860:

Will this cause any performance problems with the servers?

1770:

How well would it work for the actual category listing for

520:. Facilitates transparency and access to history a lot. -- 1577: 1573: 1505:

I see - so the protocol provides a way of storing pages

72: 1713: 1271:

format, exactly what good is this supposed to do us?

1201:

grab an old, potentially inaccurate version of a page

116:

article look like 24 hours after the protest started?

2429:

No further edits should be made to this discussion.

1741:

http://www.mediawiki.org/Extension:Memento#Templates

29:

The following discussion is an archived record of a

2107:Setting up a Memento-powered MediaWiki instance on 67:When searching information on the Web, you cannot 1726:looked like at the time), and then later moved. 2382:history of the Iraq War through Knowledge edits 345:Turn it on. For all the reasons stated above. 916:for every reason mentioned in the RfC itself. 1267:provide the best version of information in a 851:as long as rev-del material isn't available. 272:Will it make deleted pages accessible again? 8: 1973:(the English Knowledge's robots.txt file is 738:. No new information will be disclosed, and 461:! So, yeah, turn it on. No reason not to. — 124:article changed before and after his death? 2151:good to know whether WMF share this view. 1965:I believe he means that tools such as the 1947:Not sure what you mean about robots.txt. 1870:That's all I can think of at the moment. 1477:make available already. How's that then? 1059:content, I think we'd want it off again. 286:The pages were shown only in "Edit" mode. 158:How does it impact the editing community? 1920:Past revisions = pre-deleted revisions? 899:. Sounds right up Knowledge's alley. -- 829: 216:the British Government Web archive; and 1944: 419:See my message in the oppose section. 2238:, as of 1/1/08, which would say that 743: 219:the Government of Canada Web archive. 7: 2347:Mind if I join you on the fence? : ) 2326:we don't always revdel the bad stuff 2324:It's important to bear in mind that 1887:Thanks for the comments Kumioko :) 1658:We have added a screencast in the 142:), and new Relation Types for the 24: 760:) 15:10, 5 September 2012 (UTC) 304:How will it impact performance? 204:Dublin Core Metadata Initiative 49:(RFC) regarding turning on the 2367:07:20, 27 September 2012 (UTC) 2357:01:12, 26 September 2012 (UTC) 2342:11:07, 18 September 2012 (UTC) 2212:visible (which it shouldn't). 1224:We have enough edit wars over 941:00:51, 24 September 2012 (UTC) 929:09:16, 20 September 2012 (UTC) 909:16:27, 19 September 2012 (UTC) 892:17:04, 15 September 2012 (UTC) 878:19:29, 14 September 2012 (UTC) 83:Los Alamos National Laboratory 18:Knowledge:Requests for comment 1: 2286:16:29, 4 September 2012 (UTC) 2272:16:25, 4 September 2012 (UTC) 2255:16:09, 4 September 2012 (UTC) 2222:12:55, 5 September 2012 (UTC) 2204:11:59, 4 September 2012 (UTC) 2180:10:43, 3 September 2012 (UTC) 2164:10:33, 3 September 2012 (UTC) 2121:17:45, 5 September 2012 (UTC) 2103:01:04, 3 September 2012 (UTC) 2085:23:03, 2 September 2012 (UTC) 2061:14:36, 1 September 2012 (UTC) 1915:00:14, 1 September 2012 (UTC) 1672:20:00, 5 September 2012 (UTC) 1654:18:04, 4 September 2012 (UTC) 1639:16:52, 4 September 2012 (UTC) 1625:16:50, 4 September 2012 (UTC) 1608:16:49, 4 September 2012 (UTC) 1591:16:38, 4 September 2012 (UTC) 1568:16:12, 4 September 2012 (UTC) 1553:16:02, 4 September 2012 (UTC) 1538:15:53, 4 September 2012 (UTC) 1523:15:16, 4 September 2012 (UTC) 1501:14:33, 4 September 2012 (UTC) 1487:14:11, 4 September 2012 (UTC) 1464:13:05, 4 September 2012 (UTC) 1449:12:37, 4 September 2012 (UTC) 1421:10:49, 2 September 2012 (UTC) 1406:05:30, 2 September 2012 (UTC) 1380:23:58, 1 September 2012 (UTC) 1365:23:57, 1 September 2012 (UTC) 1347:17:47, 1 September 2012 (UTC) 1331:14:41, 1 September 2012 (UTC) 1316:14:26, 1 September 2012 (UTC) 1296:14:17, 1 September 2012 (UTC) 1282:09:57, 1 September 2012 (UTC) 1213:08:02, 3 September 2012 (UTC) 861:19:17, 9 September 2012 (UTC) 844:15:12, 9 September 2012 (UTC) 815:18:12, 5 September 2012 (UTC) 800:17:09, 5 September 2012 (UTC) 776:21:39, 5 September 2012 (UTC) 731:17:44, 4 September 2012 (UTC) 705:12:04, 4 September 2012 (UTC) 688:11:37, 4 September 2012 (UTC) 671:11:35, 3 September 2012 (UTC) 646:23:51, 3 September 2012 (UTC) 632:15:36, 3 September 2012 (UTC) 618:14:26, 3 September 2012 (UTC) 600:07:50, 3 September 2012 (UTC) 566:22:41, 2 September 2012 (UTC) 547:11:47, 2 September 2012 (UTC) 530:11:00, 2 September 2012 (UTC) 513:22:52, 1 September 2012 (UTC) 492:11:03, 1 September 2012 (UTC) 114:2011–2012 Egyptian revolution 2111:sounds like a no-brainer. -- 1513:part - would that be right? 1195:There I also explain why no 2417:22:58, 4 October 2012 (UTC) 2394:18:19, 2 October 2012 (UTC) 2017:23:25, 30 August 2012 (UTC) 1987:20:05, 30 August 2012 (UTC) 1957:09:42, 30 August 2012 (UTC) 1938:00:41, 30 August 2012 (UTC) 1897:22:45, 30 August 2012 (UTC) 1880:00:39, 30 August 2012 (UTC) 1815:23:55, 30 August 2012 (UTC) 1803:22:34, 30 August 2012 (UTC) 1782:01:55, 30 August 2012 (UTC) 1764:23:05, 29 August 2012 (UTC) 1734:20:05, 29 August 2012 (UTC) 1708:How well would it work for 1257:20:37, 31 August 2012 (UTC) 1243:09:32, 31 August 2012 (UTC) 1184:05:25, 31 August 2012 (UTC) 1167:05:41, 31 August 2012 (UTC) 1152:00:13, 31 August 2012 (UTC) 1145:that will remain hidden? - 1135:22:22, 30 August 2012 (UTC) 1112:20:23, 30 August 2012 (UTC) 1094:15:44, 30 August 2012 (UTC) 1069:15:35, 30 August 2012 (UTC) 1050:22:48, 29 August 2012 (UTC) 1031:22:29, 29 August 2012 (UTC) 997:19:41, 29 August 2012 (UTC) 983:19:38, 29 August 2012 (UTC) 962:19:32, 29 August 2012 (UTC) 471:21:34, 31 August 2012 (UTC) 446:18:24, 31 August 2012 (UTC) 429:15:37, 30 August 2012 (UTC) 412:00:49, 30 August 2012 (UTC) 398:00:34, 30 August 2012 (UTC) 381:21:50, 29 August 2012 (UTC) 355:21:39, 29 August 2012 (UTC) 211:UK Web Archiving Consortium 2446: 1558:for every single article. 77:– a project funded by the 2404:There is consensus for a 1612:Looks like the answer is 971:"....We are all Kosh...." 459:digital rights management 2426:Please do not modify it. 2051:for more information. -- 2048: 1967:Internet Wayback Machine 1772:Category:Virginia cities 1710:Category:Virginia cities 1659: 763: 329:We were able to write a 182:supporting this protocol 36:Please do not modify it. 229:How does Memento work? 87:Old Dominion University 1190:It is exactly because 587:Non-technical reasons: 85:in collaboration with 1511:making them available 1231:write an encyclopedia 417:Support provisionally 340:Support turning it on 244:Transactional Archive 2230:Behaviour of Memento 1646:alf laylah wa laylah 976:<-Babylon-5-: --> 947:Oppose turning it on 438:alf laylah wa laylah 69:navigate in the past 484:Dmitrij D. Czarkoff 246:to store revisions. 148:MediaWiki extension 140:content negotiation 79:Library of Congress 47:request for comment 31:request for comment 2378:heavy metal umlaut 1969:typically respect 1199:will accidentally 762:Edit: Per new FAQ 579:Technical reasons: 144:HTTP "Link" header 1827:A couple concerns 1388:It will never be 1104:Shawn in Montreal 890: 740:User:Okeyes (WMF) 727: 134:How does it work? 2437: 2428: 2413: 2139:WMF legal advice 1954: 1761: 1739:Addressed here: 1725: 1719: 1596:User:Andrew Gray 1343: 1278: 1197:random passer-by 1029: 1027: 1022: 1017: 981: 886: 841: 840: 836: 832: 826: 723: 685: 561: 379: 377: 372: 367: 197:Internet Archive 91:Internet Archive 63:What is Memento? 38: 2445: 2444: 2440: 2439: 2438: 2436: 2435: 2434: 2433: 2424: 2411: 2402: 2298: 2232: 2141: 1952: 1922: 1829: 1759: 1723: 1717: 1706: 1339: 1274: 1081:Strongly Oppose 1025: 1020: 1015: 1013: 968: 949: 927: 920:John Chrysostom 838: 834: 830: 824: 683: 557: 375: 370: 365: 363: 342: 308:were to use it. 226: 169: 167:Why support it? 160: 136: 122:Michael Jackson 95:Wayback Machine 65: 34: 22: 21: 20: 12: 11: 5: 2443: 2441: 2432: 2431: 2401: 2398: 2397: 2396: 2380:video and the 2372: 2371: 2370: 2369: 2348: 2330: 2329: 2322: 2314: 2306: 2297: 2294: 2293: 2292: 2291: 2290: 2289: 2288: 2240:George W. Bush 2231: 2228: 2227: 2226: 2225: 2224: 2188: 2183: 2182: 2140: 2137: 2136: 2135: 2134: 2133: 2132: 2131: 2130: 2129: 2128: 2127: 2126: 2125: 2124: 2123: 2089:That would be 2070: 2066: 2053:Hariharshankar 2038: 2037: 2036: 2035: 2034: 2033: 2032: 2031: 2028: 2025: 2022: 2008: 1999: 1996: 1992: 1960: 1959: 1921: 1918: 1902: 1901: 1900: 1899: 1868: 1867: 1866: 1865: 1858: 1857: 1856: 1849: 1848: 1847: 1841: 1840: 1839: 1828: 1825: 1824: 1823: 1822: 1821: 1820: 1819: 1818: 1817: 1785: 1784: 1768: 1767: 1766: 1747:(spec editor) 1705: 1702: 1701: 1700: 1699: 1698: 1697: 1696: 1695: 1694: 1693: 1692: 1691: 1690: 1689: 1688: 1687: 1686: 1685: 1684: 1683: 1682: 1681: 1680: 1679: 1678: 1677: 1676: 1675: 1674: 1664:Hariharshankar 1432: 1431: 1430: 1429: 1428: 1427: 1426: 1425: 1424: 1423: 1395: 1386: 1385: 1384: 1383: 1382: 1351:I'm rebutting 1301: 1300: 1299: 1298: 1264:Strong Oppose: 1261: 1260: 1259: 1235:69.228.170.132 1218: 1217: 1216: 1215: 1188: 1187: 1186: 1171: 1170: 1169: 1115: 1114: 1096: 1076: 1075: 1074: 1073: 1072: 1071: 1033: 1009: 1008: 1007: 948: 945: 944: 943: 934:Strong support 931: 923: 914:Strong support 911: 894: 880: 863: 846: 817: 802: 779: 742:has confirmed 733: 707: 690: 673: 655: 654: 653: 652: 651: 650: 649: 648: 603: 602: 569: 549: 532: 515: 497:Strong support 494: 473: 448: 431: 414: 400: 383: 357: 341: 338: 337: 336: 335: 334: 327: 316: 315: 314: 313: 309: 301: 300: 299: 298: 292: 291: 290: 289: 288: 287: 284: 281: 269: 268: 267: 266: 265: 264: 261: 258: 254: 250: 247: 237: 225: 222: 221: 220: 217: 214: 207: 200: 193: 168: 165: 159: 156: 135: 132: 107: 106: 102: 64: 61: 43: 42: 41: 25: 23: 15: 14: 13: 10: 9: 6: 4: 3: 2: 2442: 2430: 2427: 2421: 2420: 2419: 2418: 2415: 2414: 2407: 2399: 2395: 2391: 2387: 2383: 2379: 2374: 2373: 2368: 2365: 2360: 2359: 2358: 2355: 2354: 2349: 2346: 2345: 2344: 2343: 2339: 2335: 2327: 2323: 2319: 2315: 2312: 2307: 2303: 2302: 2301: 2295: 2287: 2283: 2279: 2275: 2274: 2273: 2269: 2265: 2261: 2260: 2259: 2258: 2257: 2256: 2252: 2248: 2243: 2241: 2237: 2236:United States 2229: 2223: 2219: 2215: 2211: 2207: 2206: 2205: 2201: 2197: 2193: 2189: 2185: 2184: 2181: 2177: 2173: 2168: 2167: 2166: 2165: 2161: 2157: 2152: 2148: 2144: 2138: 2122: 2118: 2114: 2110: 2106: 2105: 2104: 2100: 2096: 2092: 2088: 2087: 2086: 2083: 2082: 2077: 2076: 2071: 2067: 2064: 2063: 2062: 2058: 2054: 2050: 2046: 2045: 2044: 2043: 2042: 2041: 2040: 2039: 2029: 2027:Disallow: /w/ 2026: 2024:User-agent: * 2023: 2020: 2019: 2018: 2015: 2014: 2009: 2006: 2005: 2000: 1997: 1993: 1990: 1989: 1988: 1984: 1980: 1976: 1972: 1968: 1964: 1963: 1962: 1961: 1958: 1955: 1950: 1946: 1942: 1941: 1940: 1939: 1936: 1935: 1929: 1926: 1919: 1917: 1916: 1912: 1908: 1898: 1894: 1890: 1886: 1885: 1884: 1883: 1882: 1881: 1877: 1873: 1862: 1861: 1859: 1853: 1852: 1850: 1845: 1844: 1842: 1837: 1836: 1834: 1833: 1832: 1826: 1816: 1813: 1810: 1806: 1805: 1804: 1800: 1796: 1791: 1790: 1789: 1788: 1787: 1786: 1783: 1780: 1777: 1773: 1769: 1765: 1762: 1757: 1753: 1749: 1748: 1746: 1742: 1738: 1737: 1736: 1735: 1732: 1729: 1722: 1715: 1711: 1703: 1673: 1669: 1665: 1661: 1657: 1656: 1655: 1651: 1647: 1642: 1641: 1640: 1636: 1632: 1628: 1627: 1626: 1622: 1618: 1615: 1611: 1610: 1609: 1605: 1601: 1597: 1594: 1593: 1592: 1588: 1584: 1579: 1575: 1571: 1570: 1569: 1565: 1561: 1556: 1555: 1554: 1550: 1546: 1541: 1540: 1539: 1535: 1531: 1526: 1525: 1524: 1520: 1516: 1512: 1508: 1504: 1503: 1502: 1498: 1494: 1490: 1489: 1488: 1484: 1480: 1476: 1472: 1471:other sites' 1467: 1466: 1465: 1461: 1457: 1452: 1451: 1450: 1446: 1442: 1437: 1434: 1433: 1422: 1418: 1414: 1409: 1408: 1407: 1403: 1399: 1398:Nouniquenames 1393: 1391: 1387: 1381: 1377: 1373: 1368: 1367: 1366: 1362: 1358: 1354: 1350: 1349: 1348: 1345: 1344: 1342: 1334: 1333: 1332: 1328: 1324: 1319: 1318: 1317: 1313: 1309: 1308:Nouniquenames 1305: 1304: 1303: 1302: 1297: 1293: 1289: 1285: 1284: 1283: 1280: 1279: 1277: 1270: 1265: 1262: 1258: 1254: 1250: 1246: 1245: 1244: 1240: 1236: 1232: 1227: 1223: 1220: 1219: 1214: 1210: 1206: 1202: 1198: 1193: 1189: 1185: 1181: 1177: 1176:Nouniquenames 1172: 1168: 1164: 1160: 1159:Nouniquenames 1155: 1154: 1153: 1150: 1149: 1144: 1143: 1138: 1137: 1136: 1132: 1128: 1123: 1119: 1118: 1117: 1116: 1113: 1109: 1105: 1100: 1097: 1095: 1091: 1087: 1086:Nouniquenames 1082: 1078: 1077: 1070: 1066: 1062: 1057: 1053: 1052: 1051: 1047: 1043: 1039: 1034: 1032: 1028: 1023: 1018: 1010: 1006:(spec editor) 1005: 1000: 999: 998: 994: 990: 986: 985: 984: 980: 979: 978: 977: 972: 966: 965: 964: 963: 959: 955: 946: 942: 939: 935: 932: 930: 926: 922: 921: 915: 912: 910: 906: 902: 898: 895: 893: 889: 884: 881: 879: 875: 871: 867: 864: 862: 858: 854: 850: 847: 845: 842: 837: 827: 821: 818: 816: 813: 810: 806: 803: 801: 797: 793: 788: 783: 780: 778: 777: 773: 769: 765: 759: 755: 751: 745: 741: 737: 734: 732: 728: 726: 725:Contributions 720: 718: 717: 711: 708: 706: 702: 698: 694: 691: 689: 686: 681: 677: 674: 672: 668: 664: 660: 657: 656: 647: 643: 639: 638:Nouniquenames 635: 634: 633: 629: 625: 621: 620: 619: 615: 611: 610:Nouniquenames 607: 606: 605: 604: 601: 597: 593: 588: 586: 580: 578: 573: 570: 567: 564: 562: 560: 555: 550: 548: 544: 540: 536: 533: 531: 527: 523: 519: 516: 514: 510: 506: 502: 498: 495: 493: 489: 485: 481: 477: 474: 472: 468: 464: 460: 456: 452: 449: 447: 443: 439: 435: 432: 430: 426: 422: 418: 415: 413: 409: 405: 401: 399: 395: 391: 387: 384: 382: 378: 373: 368: 361: 358: 356: 352: 348: 344: 343: 339: 332: 328: 325: 321: 320: 318: 317: 310: 306: 305: 303: 302: 296: 295: 294: 293: 285: 282: 279: 278: 274: 273: 271: 270: 262: 259: 255: 251: 248: 245: 241: 240: 238: 235: 231: 230: 228: 227: 223: 218: 215: 212: 208: 205: 201: 198: 194: 191: 187: 186: 185: 183: 179: 175: 166: 164: 157: 155: 153: 149: 145: 141: 133: 131: 129: 125: 123: 117: 115: 112:what did the 103: 100: 99: 98: 96: 92: 88: 84: 80: 76: 75: 70: 62: 60: 56: 54: 53: 48: 40: 37: 32: 27: 26: 19: 2425: 2422: 2409: 2405: 2403: 2351: 2331: 2325: 2317: 2310: 2299: 2296:On the fence 2244: 2233: 2214:Okeyes (WMF) 2209: 2191: 2172:Okeyes (WMF) 2153: 2149: 2145: 2142: 2095:Okeyes (WMF) 2090: 2079: 2074: 2073: 2011: 2003: 2002: 1932: 1930: 1927: 1923: 1903: 1869: 1830: 1707: 1617:Okeyes (WMF) 1600:Okeyes (WMF) 1510: 1506: 1493:Okeyes (WMF) 1474: 1470: 1456:Okeyes (WMF) 1435: 1389: 1352: 1340: 1338: 1275: 1273: 1268: 1263: 1249:Okeyes (WMF) 1225: 1221: 1200: 1196: 1191: 1146: 1141: 1140: 1121: 1098: 1080: 1055: 975: 974: 970: 969: 950: 933: 919: 913: 901:Martin Wisse 896: 882: 865: 848: 833: 819: 804: 785: 781: 761: 748: 735: 724: 715: 709: 692: 675: 658: 624:Okeyes (WMF) 584: 583: 576: 575: 571: 558: 553: 534: 517: 501:Semantic Web 496: 475: 451:Support, duh 450: 433: 416: 385: 359: 253:performance. 170: 161: 137: 130:initiative. 119: 111: 108: 73: 68: 66: 57: 50: 46: 44: 35: 28: 2278:Andrew Gray 2247:Andrew Gray 2196:Andrew Gray 1943:See above. 1662:section. -- 1341:Ravenswing 1276:Ravenswing 1205:Thüringer ☼ 790:downside.-- 750:templates). 697:Andrew Gray 592:Thüringer ☼ 482:gateway. — 174:linked data 128:linked data 81:and run by 55:extension. 2386:Tom Morris 2156:Richardguk 1971:robots.txt 1731:Od Mishehu 1704:Discussion 1583:Victor Yus 1515:Victor Yus 1479:Victor Yus 1038:this paper 1016:—JmaJeremy 954:Victor Yus 768:Richardguk 754:Richardguk 463:Tom Morris 366:—JmaJeremy 234:Screencast 105:Knowledge; 45:This is a 2334:bobrayner 2264:Azaroth42 1979:MZMcBride 1889:Azaroth42 1795:Azaroth42 1752:Main Page 1745:azaroth42 1728:עוד מישהו 1631:Azaroth42 1560:Azaroth42 1530:Azaroth42 1413:Ironholds 1372:Ironholds 1357:Ironholds 1323:Ironholds 1288:Ironholds 1127:Azaroth42 1004:azaroth42 870:causa sui 787:benefits. 522:JakobVoss 312:database. 257:Archives. 152:available 2406:test run 2364:Dcoetzee 2311:how much 2305:helpful? 2004:directly 938:Dcoetzee 809:James F. 792:Ragesoss 554:Support. 120:how the 2412:MBisanz 2400:Summary 2210:already 2091:awesome 2075:exactly 1949:the wub 1907:Kumioko 1872:Kumioko 1756:the wub 1545:Dweller 1441:Dweller 1269:current 1226:current 1142:content 897:Support 883:Support 866:Support 849:Support 820:Support 805:Support 782:Support 736:Support 729:( 偉特 ) 710:Support 693:Support 680:the wub 676:Support 663:PascalC 659:Support 572:Support 535:Support 518:Support 505:Nyttend 476:Support 434:Support 390:Kumioko 386:Support 360:Support 347:Cielbie 324:bug 851 178:linkrot 74:Memento 52:Memento 2113:DarTar 1855:would. 1809:Anomie 1776:Anomie 1436:Oppose 1222:Oppose 1122:should 1099:Oppose 1056:easier 1042:DarTar 888:mabdul 812:(talk) 539:Acka47 404:Kurtis 59:here. 1716:what 1475:don't 853:Hobit 764:above 744:below 716:Yutsi 331:Patch 232:This 16:< 2390:talk 2353:jc37 2338:talk 2282:talk 2268:talk 2251:talk 2218:talk 2200:talk 2192:look 2176:talk 2160:talk 2117:talk 2109:Labs 2099:talk 2081:jc37 2057:talk 2013:jc37 1983:talk 1975:here 1953:"?!" 1934:jc37 1911:talk 1893:talk 1876:talk 1799:talk 1760:"?!" 1714:here 1668:talk 1650:talk 1635:talk 1621:talk 1614:yes! 1604:talk 1587:talk 1564:talk 1549:talk 1534:talk 1519:talk 1497:talk 1483:talk 1460:talk 1445:talk 1417:talk 1402:talk 1390:done 1376:talk 1361:talk 1327:talk 1312:talk 1292:talk 1253:talk 1239:talk 1209:talk 1203:. -- 1180:talk 1163:talk 1148:jc37 1131:talk 1108:talk 1090:talk 1065:talk 1061:Gigs 1046:talk 993:talk 989:Keφr 958:talk 905:talk 874:talk 857:talk 796:talk 772:talk 758:talk 701:talk 684:"?!" 667:talk 642:talk 628:talk 614:talk 596:talk 543:talk 526:talk 509:talk 488:talk 467:talk 455:cURL 442:talk 425:talk 421:Gigs 408:talk 394:talk 351:talk 209:the 202:the 195:the 188:the 93:'s " 2384:. — 2321:me. 2049:FAQ 1721:cfd 1660:FAQ 1507:and 1353:one 918:St 825:Hex 559:AGK 480:git 224:FAQ 190:W3C 118:or 2392:) 2340:) 2318:so 2284:) 2270:) 2253:) 2220:) 2202:) 2178:) 2162:) 2154:— 2119:) 2101:) 2059:) 1985:) 1913:) 1895:) 1878:) 1801:) 1724:}} 1718:{{ 1670:) 1652:) 1637:) 1623:) 1606:) 1589:) 1566:) 1551:) 1543:-- 1536:) 1521:) 1499:) 1485:) 1462:) 1447:) 1419:) 1404:) 1396:-- 1378:) 1363:) 1329:) 1314:) 1294:) 1255:) 1241:) 1211:) 1182:) 1165:) 1157:-- 1133:) 1110:) 1092:) 1084:-- 1079:I 1067:) 1048:) 995:) 960:) 925:τω 907:) 876:) 859:) 839:❞) 835:?! 831:(❝ 798:) 784:. 774:) 703:) 669:) 644:) 630:) 616:) 598:) 568:** 545:) 528:) 511:) 490:) 469:) 444:) 427:) 410:) 396:) 353:) 326:). 154:. 33:. 2388:( 2336:( 2280:( 2266:( 2249:( 2216:( 2198:( 2174:( 2158:( 2115:( 2097:( 2069:) 2055:( 1981:( 1909:( 1891:( 1874:( 1812:⚔ 1797:( 1779:⚔ 1666:( 1648:( 1633:( 1619:( 1602:( 1585:( 1578:Y 1574:X 1562:( 1547:( 1532:( 1517:( 1495:( 1481:( 1458:( 1443:( 1415:( 1400:( 1374:( 1359:( 1325:( 1310:( 1290:( 1251:( 1237:( 1207:( 1178:( 1161:( 1129:( 1106:( 1088:( 1063:( 1044:( 1026:✎ 1021:✆ 991:( 956:( 903:( 872:( 855:( 794:( 770:( 756:( 721:/ 699:( 665:( 640:( 626:( 612:( 594:( 585:• 577:• 541:( 524:( 507:( 486:( 465:( 440:( 423:( 406:( 392:( 376:✎ 371:✆ 349:( 213:; 206:; 199:; 192:;

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.

Knowledge

:Requests for comment/Memento - Knowledge

Index