|
|
|
|
|
by mossTechnician
624 days ago
|
|
Does that mean that to the users of these wikis, the switching costs[1] of the backend would basically be zero (one day they might just end up on a different server with the same content), while on the administrators' side the switching costs are at a reasonable minimum? [1] a variable in whether something can be enshittified, via https://en.wikipedia.org/wiki/Enshittification#History_and_d... |
|
Observant users might notice the removal of any Weird Gloop branding but otherwise the only way people would know if the wiki itself announces the move or performance of the wiki becomes noticeably worse.
And Weird Gloop won't do what Fandom does and keep a zombie copy of your wiki online. So you won't be competing with Weird Gloop wiki traffic to reclaim your traffic. In fact, the obligations they agree to forbid it.
Reading the Minecraft.wiki Memorandum: https://meta.minecraft.wiki/w/Memorandum_of_Understanding_wi...
Upon termination by either party, Weird Gloop is obligated to:
- Cease operating any version of the Minecraft Wiki
- Transfer ownership of the minecraft.wiki domain to the community members
- Provide dumps of Minecraft Wiki databases and image repositories, and any of Weird Gloop's MediaWiki configuration that is specific to Minecraft Wiki
- Assist in transferring to the community members any domain-adjacent assets or accounts that cannot reasonably be acquired without Weird Gloop's cooperation
- This does not include any of Weird Gloop's core MediaWiki code, Cloudflare configuration, or accounts/relationships related to advertising or sponsorships
This sort of agreement means Weird Gloop is incentivized to not become so shit that wiki would want to leave (and take their ad revenue with them) because they've tried to make leaving Weird Gloop as easy as possible.