A wiki farm
is a website, which may or may not itself be a wiki
, that allows for free or pay creation and hosting
Wiki farms vs. commercial web hostsEdit
The structure of a wiki farm offers a turnkey solution, which may be convenient for operators of small wikis with limited intentions to expand.
- As the web and wiki software is already configured for you, you avoid the tasks of technical system administration. In some cases, this may enable you to get your initial wiki online more quickly. It also relieves you of the responsibility of updating the software to protect against vulnerabilities.
- These sites tend to group a large number of different communities on different topics under one roof, which may prove to be of use in drawing traffic to a small project that might otherwise be difficult to obtain.
- Cost often appears nominally to be lower, as the task of obtaining advertising revenue has already been handled by the wiki farm.
- Wiki-specific technical support tends to be available, although response time may vary between providers. This is often preferred to commercial hosts, whose role is solely to provide server space and not to support specific database applications (such as a wiki).
- Some wiki farms provide automatic backup of individual wikis, with said backup 'dumps' available to download and store the file elsewhere.
- In most cases, you are not free to switch an existing project from one wiki farm to another, or from a wiki farm to a commercial web host, without great difficulty.
- Your project is not a separate, independent site – but merely (usually) a sub-domain of the wiki farm's main domain. This is an issue if your once-small project grows large enough to stand on its own.
- Depending on the wiki farm, you may or may not be able to choose the license terms for your content. Ability to download content and database also varies widely.
- In most cases, the choice of whether to depend on advertising revenue to fund a site, or to pay your own way is taken away from you. Where servers are funded by advertising, you have little or no control over the source or content of advertisements; some of which may be inappropriate. This may mean that your gaming community could be sponsored by vendors of tools to cheat at those games, or that your kids-oriented site is exposed to age-inappropriate sales pitches.
- Using a wiki farm can cost you control of your ideas, your project, and your intellectual property. Read the fine print; while wiki farms talk as if the project is "owned by the community", you may find that any domain names, project names and logos are the property not of the individual project, but of the wiki farm. The license on the content of your wiki is also likely to be one in which the wiki farm either takes control itself, or licenses your content for commercial for-profit distribution elsewhere on the internet. This can lead to problems where websites mirror incomplete or outdated copies of your content in order to draw traffic away from your project, and to a copy on which outside advertisers keywords, ads, and links have been placed.
- In many cases, your project does not have your own user list if your wiki is one among many in a wiki farm environment. This both limits your choice of username (as many will already be in use elsewhere on the site), and poses an obstacle should you later wish to move your project to some other host.
- Wiki farms typically do not provide the ability to seamlessly mix wikis with non-wiki applications, such as message boards, portals, blogs, forums and galleries. The configuration is typically a predefined one used across all wikis on the farm, which does not afford you the same levels of access to customisation as would installing the wiki software of your choice on a regular commercial web-host.
- ScribbleWiki went offline without warning in early Autumn 2008, and ElWiki went down in 2007. There is no guarantee that such disasters won't recur.
Key questions to askEdit
- Who owns any domain names? Can you use your own domain registration (and keep it), without turning over its ownership to a wiki farm?
- Who owns the content? Under what license, and does that license allow unrestricted commercial use of your content by others?
- Who owns the project name, logo and any other identifiers? Can you be confident that the wiki farm doesn't plan to take them from you and own them themselves?
- What happens if you attempt to move (aka fork) your project to another site? Do you have access to download both your database and your user list? Will the wiki farm continue to operate your old site in direct competition with your wiki on your new provider?
- What is the response time, and capacity of the server (or servers)? Wiki (and dynamic content in general) are database-intensive, leading wiki farms to often be much slower than the average for most other internet sites.
- What is the quality of technical support? Are existing wiki farm users getting speedy resolution of problems, or waiting months for resolution of minor issues? As a wiki farm typically does not provide the same sysadmin-level access as an ordinary commercial web-host, you are relying on others to maintain your server for you - how do they rate?
- Where are the backups of your project-critical data? Are you free to download a copy as a precaution, and will that copy be up-to-date and complete?
- What software, plugins and extensions are available? If the setup is a cookie-cutter duplicate of every other wiki on the site, is the choice of wiki software one that meets your needs?
- What are the restrictions on topics or content on each site? Is the wiki farm willing to operate your wiki as you originally envisioned it, or will they reject your topic outright for any number of arbitrary reasons, varying from your choice of name and license to overlap with other existing projects on the site?