Low-cost multi-wiki solution for D&D game?

Plugins
#1

I play D&D in a party with 6 players and 1 DM. I am looking into moving my (personal, player) notes from Obsidian to TiddlyWiki. I want to be able to host, for our party, a wiki where we can each keep our personal notes on various topics as well as shared group notes. Some information, such as character backstories, for example, should only be visible to the user playing that character and the DM. Or we have notes on each other’s characters that are only for us. Or information only one character knows, etc.

Basically, I want us to be able to share knowledge but also have clear delineation of ownership and viewing rights of that knowledge, and be able to group information about a topic together while only showing people what they should be allowed to see. Of course if I were the one running the wiki (which is my plan) I could just go into the MWS database and look myself, or change my rights, but I would ideally be using a non-privileged account for day to day stuff.

#2

From my point of view, that multi-wiki-server MWS plugin still is highly experimental. Especially the access handling is still in flux and subject to change in backwards incompatible ways.

I think your usecase can be solved with MWS, but you would be an early adopter.Which means there will be breaking changes in the code, which may set you back several steps, or even to “sqare one”.

The access control list (ACL) configurations in TW is “role” based. But at the moment this system only knows how to handle Admins, Users and Guests

It can only allow “read/write/delete” as WRITE and “read only” as READ privileges.

Guests are “anonymous” … By default Guests have full WRITE access to the whole database.

If the Admin defines roles for recipes and bags, they will take effect. There is no “MANAGE” right at the moment. So the Admin has to do the whole rights management.

I do not know, how much you know about TW “bags” and “recipes”

Bags … are tiddler containers and can belong to several recipes.
Recipes … are lists of bags

In recipes the order of bags has a meaning. So the “last bag wins”. That means: Tiddlers with the same title will overwrite tiddlers from “lower” bags.

So a “player” recipe may contain several bags eg:

recipe pmario-private may contain the following bags

  1. system … eg. TW plugins / themes that every user needs
  2. default-npc … Default info about NPCs
  3. dm-global … global info the DM has created. So the DM can “clone” default-npc data and change it, without modifying the initial default
  4. <player>-public … public player data
  5. <player>-private … player specific bag. … Only the player can see that one.

In this example the “player” can only write to the player-private (5)

  • At the moment there is no mechanism to move a tiddler from 5 to eg: 4, even if the user would have the rights to do so.
    • This will make management complex at the moment.
    • So players will have to manage 2 wikis atm, which IMO is inconvenient.
  • At the moment there is no visual indication, where a tiddler comes from – so all tiddlers from different bags visually look the same.

As you can see the bags 1,2 and 3 will be the same for every player

Every player may have 2 player-bags with a different names. eg:

  • pmario-private which only I can see and
  • pmario-public which everyone can see, but only I can write to

By default the recipe above will write new content to bag 5 player-private by default.

There may be a recipe: pmario-public which contains those bags:

  1. system … eg. TW plugins / themes that every user needs
  2. default-npc … Default info about NPCs
  3. dm-global … global info the DM has created. So the DM can “clone” default-npc data and change it, without modifying the real default
  4. pmario-public … public player data

This is just an example. So your configurations may vary.

Hope that makes sense

2 Likes
Testing the Multi Wiki Server Plugin