Always hated the ads and thought it would make sense for different fandoms to have their own instances.
this is one of the capabilities that would be nice for piefed/lemmy/mbin. So many communities could use a wiki and if your running the community its going to be way more convenient to manage the wiki in the same space with the same login. Would definately need a download upload thing.
Mirahaze doesn’t have ads
Federation makes little if any sense for a wiki. They are intended to be a sorta singular source-of-truth, and having different likely disjoint copies does not really provide any advantage than simply having a mirror doesn’t already give (and, overall, mirrors are easy to make).
If what you worry is sharing user accounts across wikis, that is not really a good idea anyway, but if they still want it it is already solvable with things like SSO, OpenID and similar, though each wiki would have to adopt and adjust them on their own.
I guess the self hosted open source aspect was more appealing. Servers could have more control over how their content is displayed than they do going through fandom. Being able to integrate wiki sections into posts in lemmy/mastodon could be cool. Reddit does have a wiki, and lemmy being a reddit clone, It would make sense to have a wiki for each community just for that reason. I remember that being useful when I frequented Reddit.
Normal wiki software already handles the “have more control over how content is displayed” part, and they can be offered as services for example Miraheze exists. Self-hosting makes sense for small stuff (and “small” here can quite reasonably mean “somewhat large” because the useful information in wikis is text and text is lightweight) but, aganin, that’s something normal wiki software already does.
Fandom wikis are pretty exclusive to their fandom tho, like they don’t have much overlap with each other? Different instances would be for different fandoms. If you mean multiple wikis being made for the same group, that is already a thing.
Fandom wikis are pretty exclusive to their fandom tho, like they don’t have much overlap with each other?
We have the Wikipedia founder to blame for that: he threw a Trumpy fit because people were documenting Buffy the Vampire Slayer, IIRC. Otherwise we could really have had an Encyclopaedia of Everything.
Still, hosting “different instances” is technically exactly the same as hosting a normal DokuWIki / MediaWiki software and offering the service on a farm setup, like eg.: Miraheze does, and that still doesn’t need any sort of “federation”. Federating contents of a wiki does not really make sense, basic and normal mirroring / archiving suffices.
This is a browser extension that shows you the non fandom instances of wiki’s, if they exist. Or, it can also use breezewiki as a privacy preserving frontend to fandom pages.
The indie wiki’s aren’t usually federated, though.
hubzilla has wiki feature but its federated over zot protocol, you can share updates via activitypub(it has both) as status updates but to collaborate on a wiki people will need to be on zot supported platforms.
I haven’t tried it yet, but there’s ibis, a federated wiki made by one of the Lemmy devs.
Is there a reason for it to be federated? Like, would you want to follow the change log for each page?
The Reddit wikis were also useful at one point like for each lemmy community.
What has that got to do with federation though?
PieFed communities do have reddit-style wikis attached. They work pretty well but don’t federate. Like somebody else mentioned, i think Ibis is closest we’ve got.
What would federation do for a wiki, specifically? Like, every instance can have <some> pages and you can browse all of them from anywhere?
yes, and display consensus or divergence, something that is visible in Wikipedia as bans to edits.
Or integrated with lemmy communities like reddit wiki
There’s things built for entirely different reasons that can be used as a federated Wiki if you wish, like Fossil (a federated version control system with a Wiki)
https://www2.fossil-scm.org/home/doc/trunk/www/index.wiki
Note that Wiki federation has a whole bunch of potential issues if you try to allow automatic updates from arbitrary users. Wiki servers rely heavily on antispam measures which often require a lot of analysis of the user’s connection, data which often isn’t available over federation, so submissions by others have to be validated manually. Fossil being a version control system means it is more of a mirroring friendly Wiki than truly federated, but you can set it up so that mutually trusting mirrors can replicate each other’s validated commits/updates.




