Difference between revisions of "Category:Miraheze"
Reception123 (Talk | contribs) |
(Semantic MediaWiki is disallowed, VE/Flow are just extensions so they don't need to be listed separately. Also emphasizing the negatives of this service so that future users don't end up in the same boat I did) |
||
| Line 10: | Line 10: | ||
|status = Active | |status = Active | ||
|engine = MediaWiki | |engine = MediaWiki | ||
| − | + | }} | |
'''Miraheze''' is a free {{tag|MediaWiki}} {{tag|WikiFarm|wiki farm}}, built on the defunct [[:Category:Orain|Orain]] [[wiki farm]]. | '''Miraheze''' is a free {{tag|MediaWiki}} {{tag|WikiFarm|wiki farm}}, built on the defunct [[:Category:Orain|Orain]] [[wiki farm]]. | ||
| Line 17: | Line 17: | ||
*have no [[:Category:Advertising|ads]] | *have no [[:Category:Advertising|ads]] | ||
*be 100% open-source (code) | *be 100% open-source (code) | ||
| − | *to run the most recent version of {{tag|MediaWiki}}, offering a competitive collection of optional extensions | + | *to run the most recent version of {{tag|MediaWiki}}, offering a competitive collection of optional extensions |
*offer possibility for custom domains | *offer possibility for custom domains | ||
| − | * | + | *have HTTPS for all wikis |
| − | + | ||
| − | + | ||
<!--{{WikiEngineFeatures}}--><!--if the wiki farm is also a wiki engine, as in Wikia--> | <!--{{WikiEngineFeatures}}--><!--if the wiki farm is also a wiki engine, as in Wikia--> | ||
| − | Miraheze does not allow wiki [[founder]]s to fully manage their [[wiki]]; tools such as [[ | + | Miraheze does not allow wiki [[founder]]s to fully manage their [[wiki]]; tools such as [[CheckUser]] and [[Oversight]] are only used by Miraheze [[Steward]]s, as they reveal personal information. Any extension at Miraheze can be requested, but it requires a security review before being installed. |
| + | |||
| + | Miraheze has been negatively compared to the Wikimedia Foundation, as it uses [[mw:Extension:CentralAuth|CentralAuth]] account unification, which means that usernames cannot be reused on multiple wikis, even if an account only exists on one wiki and is inactive. Additionally, both Miraheze stewards and sysadmins have the ability to read and perform many administrative tasks on all wikis globally. Therefore, "private" wikis aren't really private in the true sense of the word, and access to basic functions like blocking, protecting, deleting, etc. is not restricted to only whom the bureaucrats select. Furthermore, Miraheze stewards have refused to create a wiki set allowing individual wikis to opt-out of the global groups (like the Wikimedia Foundation has done with many of its global groups). | ||
| + | |||
| + | Miraheze staff have also been known to have a very strict and rigid "your account, your actions" policy. Basically, the staff members say that getting hacked or otherwise compromised is unacceptable and that any actions done under your account are deemed to have been done by you. While this rule/practice is often seen on many websites, such websites include that statement in their Terms of Use or other license agreement, which Miraheze does not. Additionally, Miraheze staff has already inappropriately banned a user who was causing no harm due to her account being compromised by a vandal. | ||
| + | |||
| + | Some staff members have also been known to engage in personal attacks against users with whom they do not agree. | ||
==Staff members== | ==Staff members== | ||
Revision as of 19:29, 8 August 2017
Template:Wiki Farm Miraheze is a free MediaWiki wiki farm, built on the defunct Orain wiki farm.
Miraheze commits to:
- be free of charge
- have no ads
- be 100% open-source (code)
- to run the most recent version of MediaWiki, offering a competitive collection of optional extensions
- offer possibility for custom domains
- have HTTPS for all wikis
Miraheze does not allow wiki founders to fully manage their wiki; tools such as CheckUser and Oversight are only used by Miraheze Stewards, as they reveal personal information. Any extension at Miraheze can be requested, but it requires a security review before being installed.
Miraheze has been negatively compared to the Wikimedia Foundation, as it uses CentralAuth account unification, which means that usernames cannot be reused on multiple wikis, even if an account only exists on one wiki and is inactive. Additionally, both Miraheze stewards and sysadmins have the ability to read and perform many administrative tasks on all wikis globally. Therefore, "private" wikis aren't really private in the true sense of the word, and access to basic functions like blocking, protecting, deleting, etc. is not restricted to only whom the bureaucrats select. Furthermore, Miraheze stewards have refused to create a wiki set allowing individual wikis to opt-out of the global groups (like the Wikimedia Foundation has done with many of its global groups).
Miraheze staff have also been known to have a very strict and rigid "your account, your actions" policy. Basically, the staff members say that getting hacked or otherwise compromised is unacceptable and that any actions done under your account are deemed to have been done by you. While this rule/practice is often seen on many websites, such websites include that statement in their Terms of Use or other license agreement, which Miraheze does not. Additionally, Miraheze staff has already inappropriately banned a user who was causing no harm due to her account being compromised by a vandal.
Some staff members have also been known to engage in personal attacks against users with whom they do not agree.
Staff members
Former staff
To do:
- permanentfuturelab.wiki
- source.miraheze.org
- undisconnect.miraheze.org
- worldpedia.miraheze.org
- gen.miraheze.org
Subcategories
This category has the following 30 subcategories, out of 30 total.
*ABC |
C cont.DEFGHM |
M cont.NRTVW |
Pages in category “Miraheze”
The following 69 pages are in this category, out of 69 total.
Media in category "Miraheze"
This category contains only the following file.
- Error creating thumbnail: /bin/bash: /usr/bin/convert: No such file or directory
Error code: 127
