4 ms·
> the foundation's main goal is still to host a centrally maintained site Wikimedia universe is way bigger than one site. There's Wikidata, Commons, Wikisourc
by smsm42 10y ago
> the foundation's main goal is still to host a centrally maintained site
Wikimedia universe is way bigger than one site. There's Wikidata, Commons, Wikisource, Wiktionary, Wikivoyage, Wikibooks and so on. And there's a lot of language versions too - English is not the only way to store knowledge, you know.
> The goal of Wikipedia should be to spread the content as far & wide as possible
The requires a) creating the content and b) presenting the content in the form consumable by the users. Creating tools for this is far from trivial, especially if you want it to be consumable and not just unpalatable infodump accessible only to the most determined.
> Instead it's still run as one massive monolithic website
This is not accurate. A lot has changed since 2004. It's not one monolithic website, it's a constellation of dozens, if not hundreds, of communities. They are using common technical infrastructure (datacenters, operations, etc.) and common software (Mediawiki, plus myriad of extensions for specific projects), but they are separate sites and separate communities, united by common goal of making knowledge available to everyone.
> it's still hard to get any sort of machine readable data out of it
Please check out Wikidata. This is literally the goal of the project. You can also be interested in "structured Commons" and "structured Wiktionary" projects, both in active development as we speak.
> This IMO should have been the main focus of Wikimedia's development efforts.
It is. One of focuses - for a project of this size, there's always several directions. BTW, right now Wikimedia is in the process of formulating movement strategy, with active community participation. You are welcome to contribute: https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2017 https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/...
Disclosure: working for WMF, not speaking for anybody but myself.
- derefr 10y ago"One massive monolithic website" is, I think, meant to be read as referring to the WMF sites being a thing that have a shared telecommunications Single Point of Failure—a "choke point" where a given piece of information can only get from a given WMF site, to a user, by travelling through WMF-managed Internet infrastructure. Remember Napster, back in the day? It was able to be shut down because it had an SPOF: Napster-the-corporation owned and maintained all the "supernodes" that formed the backbone of the network. Or consider the Great Firewall of China. If the Great Firewall can block your site/content entirely with a single rule, you have an SPOF. The answer to such problems isn't simple sharding-by-content-type into "communities" like you're talking about; this is still centralized, in the sense of "centralized allocation." Instead, to answer such problems, you need true distribution. This can take the form of protocols allowing Wiki articles to be accessed and edited in a peer-to-peer fashion with no focal point that can be blocked; this can take the form of Wikipedia "apps" that are offline-first, such that you can "bring Wikipedia with you" to places where state actors would rather you don't have it; this can take the form of preloaded "Wikipedia mirror in a box" appliances (plus a syncing logistics solution, ala AWS Snowball) which can be used by local libraries in countries with little internet access to allow people there access to Wikipedia.
- smsm42 10y ago> WMF sites being a thing that have a shared telecommunications Single Point of Failure In fact, one of the long-term projects in WMF is making sure the infrastructure is resistant to single-point-of-failure problems - up to whole data center going down. We are pretty close to it (not sure if 100%, but if not close to it). Of course, if you consider existence of WMF to be point of failure, it's another question, by that logic existence of Wikipedia can be treated as single point of failure too. Anybody is welcome to create a new Wikipedia, but that's certainly not a point of criticism towards WMF. > It was able to be shut down because it had an SPOF: Napster-the-corporation owned and maintained all the "supernodes" WMF does not own the content or the code, both are in open access and extensively mirrored. WMF does own the hardware - I don't think there's a way to do anything about it, unless somebody wants to donate a data center :) > If the Great Firewall can block your site/content entirely with a single rule, you have an SPOF. True, though there are ways around it. Currently witnesses with Turkey blocking Wikipedia. See e.g. https://github.com/ipfs/distributed-wikipedia-mirror https://github.com/ipfs/distributed-wikipedia-mirror for ways around it. > Instead, to answer such problems, you need true distribution. I am skeptical about the possibility of making community work using "true distribution". Even though we have good means to distribute hardware and software, be it production or development code, we still do not have any ways to make a community without having gathering points. I won't say it is impossible. I'd say I have yet to see anybody having done it. But if somebody wants to try, all power to them. You can read more about Wikimedia discussions on the topic here: https://strategy.wikimedia.org/wiki/Proposal:Distributed_Wikipedia https://strategy.wikimedia.org/wiki/Proposal:Distributed_Wik... > such that you can "bring Wikipedia with you" That already exists, there are several offline wikipedia setups and projects: https://strategy.wikimedia.org/wiki/Offline/List_of_Offline_Wikimedia_projects https://strategy.wikimedia.org/wiki/Offline/List_of_Offline_... > this can take the form of preloaded "Wikipedia mirror in a box" appliances We are pretty close to this - you can install working Mediawiki setup very quickly (vagrant or I think there are some other containers too, I use vagrant), dumps are there. Won't be 100% copy of true site since there are some complex operational structures that ensure caching, high availability, etc. which kinda hard to put into a box - they are in public (mostly as puppet recipes) but implementing them is not out-of-the-box experience. But you can make a simple mirror with relatively low effort (probably several hours excluding time to actually load the data, that depends on how beefy your hardware is :) Most of this, btw, is made possible by the work of WMF Engineers :)
- jessriedel 10y ago> The goal of Wikipedia should be to spread the content as far & wide as possible >> The requires a) creating the content and b) presenting the content in the form consumable by the users. Creating tools for this is far from trivial, especially if you want it to be consumable and not just unpalatable infodump accessible only to the most determined. Yes, and as emphasized in the article, WMF has done a terrible job at building better tools. For crying out loud, we are still typing in by hand the complete bibliographic information for each cited reference. Your other comments are similar. The fact that "WMF is trying", or have a named task force whose formal mission includes a complaint, is not enough justify years of high spending.
- smsm42 10y ago> Yes, and as emphasized in the article, WMF has done a terrible job at building better tools. I respectfully disagree. I think WMF has done pretty good job. Could it be better? Of course, everything could. Is it "terrible"? not even close. > For crying out loud, we are still typing in by hand the complete bibliographic information for each cited reference. https://www.mediawiki.org/wiki/Citoid https://www.mediawiki.org/wiki/Citoid ? In any case "it misses my pet feature" and "the whole multi-year effort is terrible" are not exactly the same thing. > is not enough justify years of high spending. I think the work that has been done and is being done justifies it. All this work is publicly documented. You think it's too much and you have the ideas how to do it better - you're welcome to comment. I can not comment on your value judgements - you may seem some projects are more valuable and not done, you are entitled to it. There's a process which gets some things done and some things left out, and by nature not everybody will be satisfied. I only want to correct completely factually false claims in the Op-ed, and I believe I have done so. If I can help with more information, you are welcome to ask. As for value judgements, I think we'd have to agree to disagree here.
- jessriedel 10y ago> In any case "it misses my pet feature" and "the whole multi-year effort is terrible" are not exactly the same thing. It's clear from context that this is just an example. The issues with the Wikipedia editing UI are legion and described in many other places. > You think it's too much and you have the ideas how to do it better - you're welcome to comment Clean house. Put the people who built Zotero in charge.