What is a Wiki, and why does Hive need one of its own?

A few days ago I started looking for collaborators on the Hive wiki I am currently developing. So far there have been very few responses, and one of them triggered this post. Maybe it's just not as clear to everyone else as to me why this is something we should have available since a long time already.

What is a wiki?

The term wiki refers to a web2-era tool to collaboratively create and maintain a knowledge database. The most well-known example for a project using this technology is Wikipedia of course, but there are countless small wiki instances for all kinds of projects that require a lot of information to be public. There have been several attempts to set up wikis for information around Hive, but they're all based on the old web2 tech and none of them is really maintained.

How can Hive bring wikis to web3?

Hive allows for accounts to give posting authority to other users. While the initial prototype will require authorization to post, in the long term that will switch to give permission to create and edit articles to a wider base of hive accounts (maybe based on reputation, to be decided).
Each language will have a dedicated wiki user, which is used to publish all articles. While it's prefered to use the dedicated wiki GUI to access articles due to formatting differences between the current hive GUIs and what the wiki will display, but the information will be available on each platform. The wiki software will be open source, and the keys to the account will be available to a group of trustworthy users. It'll always be possible to set up a new instance by anyone holding the keys. And even if they should be lost completely, it'd be easily possible to set up a new account and copy over all information.

What type of content could a Hive wiki host?

Theoretically, everything.
Starting out to replace wikipedia is a bit much of a challenge though. There won't be rules what kind of information can be published, as long as it's not plagiarized of course.

What it would really be useful for though, is documentation about Hive. Want to know how RCs work, what a certain Splinterland rule means, how actifit knows how many steps you did, how to set up a Hive API node? Right now this requires googling around in the hope to find a post which isn't outdated. A wiki would keep all information in an always accessible place, the information will stay available as long as the blockchain exists, and everything can be updated by the community to reflect latest developments.

Okay sounds great, I'm in, what now?

Before going live, I'm looking for a small initial core team. There needs to be content to start with, and a few people believing in the idea and wanting to help steer it in the right direction before it enters the open ocean. If you feel like you can help with that, join the wiki Discord and head to the team-applications channel. I'm looking forward to work with you!

Actually, I don't feel like I could contribute writing or moderating. Anything else to do?

Any help by coders and designers is appreciated a lot, right now a node/ts mage would be especially useful. If that's also not your thing, consider a witness vote and share this post around please!

H2
H3
H4
3 columns
2 columns
1 column
41 Comments
Ecency