- cross-posted to:
- meta
- fediverse@lemmy.world
- cross-posted to:
- meta
- fediverse@lemmy.world
Two days ago, I deployed the official wiki for lemmy.dbzer0.com. It’s using django-wiki as a software, which other than being markdown-based and therefore helping lemmings easily migrate documentation over, provides python hooks for doing some really cool stuff.
For example my current version is tied to my lemmy instance. This means that while everyone can read the wiki, only registered users of my instance can edit articles. This helps prevents the usual problem of open wikis, which is drive-by spam articles, and ensures that only people with interest in the wiki can use it.
I plan to extend this integration in the future. I am thinking things like minimum account age to edit all or some pages, profile pages which enable even tighter integrations, being able to specify “trusted instances” which would allow edits from their users as well, and so on.
But that’s not all, the same approach I used, can also be used to integrate with any fediverse software, like mastodon. This means each instance could theoretically have its own wiki to extend the information adjacent to it.
I’ll soon (I hope) will provide an ansible playbook that anyone can use to deploy it which will also provide my custom code to integrate with lemmy.
Yes, there’s no current hooks provided by django-wiki for user registration etc. I have opened requests to add them and I’m planning to adjust the procedure further then. I could also extend the django-wiki myself, but I have my hands full already with my other projects.
Ultimately the best would indeed be some sort of lemmy oauth system to register. I’m hoping this might be possible at some point in the future. This kind of thing requires more developers jumping in and this is partly why I make these posts as well.
That would be great, I have been looking at alternatives for the trans surgery wiki on Reddit in case they go the way of Tumblr.