Help:Comparing Miraheze to other services

From Miraheze Meta, Miraheze's central coordination wiki
This page contains changes which are not marked for translation. Please make a request at Meta:Administrators' noticeboard or contact any translator or administrator via their user talk page to mark the updated page for translation.
Comparing Miraheze to other services

You may be considering your wiki option hosts. We want to help. We've compiled some points to consider about both services which may aid in comparing services. This is not intended to be an advertisement and editors are free to point out Miraheze's flaws.

Aspect Miraheze Fandom ShoutWiki Other free services
Autonomy [1] [2] [3] Depends[4]
Advertisements [5] [6] [7]
Bureaucrat access Depends[8]
Customization restrictions [9] [10] [11] Depends[12]
Configuration changes [13] [14] [15]
Custom domains [16]
Custom namespaces
Custom user groups
Extensions 51 by default; over 200 can be added by admins through ManageWiki 27 by default; 11 can be added upon request with a valid reason 38 by default; 22 can be added upon request Varies from few (like ~5) to ~20. More might be addable upon request
Ability to request extensions [17] [18] [19] [20]
JavaScript restrictions and review [21] [22]
MediaWiki version  1.42 (Latest)[23]  1.39 (Latest LTS)  1.35 (Unsupported LTS)  Varies from as old as 1.15 to 1.39[24]
Motives Good will Profit Profit Profit
Private wikis
SEO   [25] [26] [27]
Skins 5 by default; 28 addable via ManageWiki 2 (1 desktop, 1 mobile) 8 Varies from 1-<10
System message editing restrictions [28] [29] Depends
VisualEditor support


  1. See FAQ#To what degree are wikis autonomous?. Miraheze will not get involved in local affairs unless a global policy is being broken.
  2. Officially, Fandom staff only intervene with local wiki communities in certain circumstances, such as Terms of Use violations, but are known to take actions outside of that scope, including forcibly enabling extensions without community input, changing URLs for SEO purposes without notification (see here) and removing local wiki administrators that object to forced changes (see here). Wiki communities do not hold all the power over their wikis. If a wiki wishes to begin migration discussions with the local community, they must get approval from Fandom staff. Upon forking (or even learning of the intent to fork), Fandom Staff will remove all administrators involved in the fork and will appoint new ones.
  3. ShoutWiki staff do not typically get involved in any wiki affairs (in part due to their inactivity).
  4. Some wiki hosts impose higher level of control than others such as customization policies or the inability to appoint local bureaucrats who can appoint admins.
  5. Fandom uses banner and inline advertisements, usually inserted at the sides of articles or the very top of the page. Fandom derives its income from advertising and selling content. Some of these advertisements appear to collect extensive personal information to target advertisements towards specific people cf. Fandom's ad engine code.
  6. Wikis can pay to remove advertisments
  7. Most wiki services serve some form of ads. Some take approaches closer to Fandom's of reducing the number of ads shown to logged-in editors.
  8. On some services, you are not allowed bureaucrat access. On services like that, only service staff can appoint new administrators.
  9. Wikis are free to customize their wikis as they wish, so long as their customizations (particularly JavaScript) do not infringe on user security.
  10. Fandom has a customization policy in place which restricts what wikis can do. They may not radically change parts of the default (and only) skin and are prohibited from touching certain parts.
  11. Most wiki services serve some form of ads. Some take approaches closer to Fandom's of reducing the number of ads shown to logged-in editors.
  12. Some services have customization policies that may restrict what you may customize. Others do not allow administrators to customize their wikis.
  13. Wiki administrators can change almost every aspect of their configuration via ManageWiki.
  14. While some basic configuration changes might be requestable through Fandom staff, the majority of requests are denied.
  15. Many free services either offer little customization or no changes at all.
  16. See Custom domains
  17. Extensions pass a security and performance test first. If they pass, they are added.
  18. While you can request extensions, Fandom will typically deny your request "mainly due to the amount of rewriting an extension would require to live on the Fandom codebase servers".
  19. While extensions may be requested, ShoutWiki does not actively act upon these requests due to their older codebase.
  20. Many wiki hosts will not allow you to request new extensions for a variety of reasons. Some may be running MediaWiki versions that are extremely old, others may simply lack the ability to add new extensions.
  21. So long as JavaScript modifications do not infringe on user safety and security, administrators can freely edit JavaScript pages. Through the use of a Content Security Policy, Miraheze mitigates the risk of dangerous JavaScript code, but still allows free editing of sitewide JavaScript.
  22. Fandom restricts what you may do with JavaScript and requires the code to be reviewed first which may take from hours to days.
  23. Miraheze is committed to staying on the latest MediaWiki version and upgrading as soon as it comes out.
  24. Some wiki hosts may modify their codebase to the point of being unable to easily upgrade. Others delay updating versions because they would rather wait on the latest LTS release.
  25. Miraheze does not have a dedicated SEO team but has experience in the field and actively applies techniques that have been shown to boost SEO. Miraheze also offers users tools to help improve SEO further, including access to the Google Search Console. Some community members may step in to assist. SEO guides for Miraheze users are available on these pages:
  26. Fandom, being a multimillion-dollar company that thrives exclusively off ad traffic, has a team that is dedicated to SEO and as a result, generally fares well on search engines. Fandom applies specific SEO techniques on all their wikis to ensure they have a good search engine ranking which is why they only offer one skin and why they restrict page formats. Fandom has historically used its anti-spam filter to prevent wiki administrators from accessing the Google Search Console.
  27. Most wiki services do not do much to improve wiki SEO other than some basics, if anything.
  28. Wiki operators may freely edit system messages, but Trust and Safety or Stewards will intervene if system message edits are used for malicious activity, like violations of the Content Policy or Terms of Use
  29. Fandom has a small list of system messages that admins can edit. Some edits to JavaScript pages will require Fandom staff to review.