3 ms·
Funny, everything you describe as a positive I see as a negative. The 11th, 12th, and 13th editions of the Encyclopedia Britannica were from 1911, 1922, and 19
by crazygringo 3y ago
Funny, everything you describe as a positive I see as a negative.
The 11th, 12th, and 13th editions of the Encyclopedia Britannica were from 1911, 1922, and 1926.
So if, as a researcher, you were interested in the state of knowledge in 1916, you're out of luck (if you're limiting yourself to a particular encyclopedia, for example).
I don't know what value you see in "stability", when the world's knowledge changes on a second-to-second basis. It's equally arbitrary whether you freeze knowledge at 1911 or in any given point in time since Wikipedia began.
When you say "A Wikipedia snapshot proves nothing", I have no idea what that means. If you're worried about vandalism or quick edits, it's trivial enough to compare with earlier and later versions of the page to ensure you're looking at relatively stable text. Heck, most of that could even be automated if you wanted.
And while Wikipedia articles are full of errors, so too were the articles in every edition of Britannica. The difference is that Wikipedia errors tend to get fixed a lot quicker, while the Britannica errors just remained on the paper they were printed on.
I genuinely don't see what difference there is between the "stability" of the Britannica 1911 edition, and the "stability" of Wikipedia at some arbitrary timestamp. Both capture a similarly arbitrary moment in time -- Wikipedia just gives you so many more to choose from.
- UltimateEdge 3y ago> Heck, most of that could even be automated if you wanted. I've had the idea of building something like this. The concept being that you would select an article and a time interval, and be shown the "best/most stable" revision of the article within the given window. The tool could use any number of metrics for determining which revision is best, the most reasonable one I've managed to come up with is "highest number of views during a state where the article was not locked/available to edit".
- crazygringo 3y agoYeah, the idea had never occurred to me until now, I'm glad to hear someone else has already thought of this. I wasn't thinking as much as identifying any single best revision, but utilizing more of a diff-like tool to identify the text/changes that remained most stable over time -- where a brand-new edit doesn't count for much, but the longer it stays around as other edits are made, the more trustworthy it presumably is. I think the biggest problem comes as articles get rearranged and expanded -- a section gets split into two or three, something gets moved from one section to a more appropriate one, and so forth. Or heck, sometimes entire articles get split into multiple ones, or vice-versa. I'm not aware of any diff-like tool/algorithm that handles these situations well, to accurately track how the same information gets moved when it's not just a simple case of insertion.
- UltimateEdge 3y agoHuh, so a bit like git blame? And then you would merge together the chunks/edits which are most stable? That sounds awesome!! I suppose you can't really count on the same text/markup being shifted around as articles get split and modified in the ways you've described. Also I suppose there is no such thing as a cross-article edit in MediaWiki terms iirc. Use vector embeddings? Throw an LLM at the problem? Rate editors on their familiarity with a given topic area (and track how that evolves over time)? The idea of using edit information in addition to the raw text written by editors seems like it's extracting additional bits of information from human interactions. I might have read some idea in a HN comment of training AI not just on code, but on how that code is edited in a git repo, or maybe I am just imagining it.
- jquast 3y agoYou should especially consider the role of a historian or the person who wishes to set out to correct facts and figures that are in error in Wikipedia, this is precisely what they need to correct it, to be able to trace the lineage of the error and correct the associated facts and figures like an excel sheet would, it’s very important especially with LLM’s that can’t cite their sources and google having gone to shit to find them, errors are quickly propagated across the web like some kind of crypto mixer, it becomes difficult to verify A non-historian mathematician does a good job explaining the issue of census data errors, https://m.youtube.com/watch?si=ySApTldsYVf3jv0W&t=1630&v=GVhFBujPlVo&feature=youtu.be https://m.youtube.com/watch?si=ySApTldsYVf3jv0W&t=1630&v=GVh...