Comment by loktarogar
3 years ago
I hate having to join discord servers just to see a certain bit of information. It's been especially bad with some open source projects.
I've seen a couple of discord servers using a service called disc.wiki[0]. even though all their actual info is stored and edited in discord, it's then pushed to that service and they can share it without having to invite people into their servers.
Came across it first with a world of warcraft guild who collated a bunch of raid resources there
[0]: https://disc.wiki
This comes pretty darn close to what the author is asking!
> Right now every channel is meant to be both transient and permanent. I know that’ll never change, so create a new “Lore” or “Archive” channel where the moderators tap on wisdom and preserve-forever statements or threads, and they get added over there. Think of it as “Pinning” but they’re pinned forever and there’s a bunch of them.
Disc.wiki seems to literally provide a similar feature, check!
> Make it possible to export this Lore/Archive channel to a reasonable file, like JSON or any other text format.
Disc.wiki provides a web interface for browsing "pinned" messages. HTML is a mostly parse-able text format, so check!
> At the very least, consider some sort of “FAQ” feature/contingency that does a similar function to the old-style FAQs, so people can contribute sets of knowledge in a structured manual instead of an endless search for terms from everyone who ever touched a server.
Ok, there's still some room for improvement. Disc.wiki's homepage claims their docs[0] are built on disc.wiki, so something similar could work.
There could be an open source version of both the cms and the bot but that's at least a step in the right direction.
[0]: https://disc.wiki/docs
It's better, but it still doesn't solve the preservation of "lore" issue : only preserving curated "knowledge".
For instance the failure mode of a detail that might not make it from discussed lore to actually preserved knowledge, but might be critical years later.
To be fair in practice I can't think of a good methodology to automate this selection.
This is probably something that would be determined much later, on a case-by-case basis... which is ideally solved by manually curating such knowledge. You lose some in the process but I'd argue something "critical" should bring attention to the necessity of its archiving.
1 reply →
Ooh, I've never heard of this before, thanks a lot for the heads-up. It's still messy but it's a great base.
Wish it were open source though.