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!
Actually above is similar to my ideas on moving developers.hive.io on chain, but I have not enough bandwidth for that.
Ideal way is to have dedicated front end to make it easy to navigate as a documentation site / wiki, but it should be also have be usable while browsing through general purpose frontend such as hive.blog.
It would be possible to do onchain by authoring users via posting authority but it would be a nightmare to deal with and wouldn't provide any auditing which is critical for wikis.
Hive Multisig to the rescue?
Would be very cumbersome. Posting auth is easier but no way to audit updates. It's just not a good medium for a wiki without a front end app layer.
Well, maybe there's room for some innovation. Combine all these concepts into something that works.
For my idea it is not going to be worse than it is, i.e. compare access control to whatever you have on developers.hive.io, if you want to edit that you go to code repository and you can make your change, submit PR, maintainer then can accept it. Same here, even using mostly what we already have (community, tags, etc.).
Auditing is just extending UI to have history of edits etc.
I was hoping to start with those https://github.com/openhive-network/hive/tree/develop/doc/devs/operations for MVP, but again, lack of bandwidth and higher priorities related to upcoming new version.
Yes, when possible hive flavoured markdown should be used. There are a few cases where the wiki will require additional syntax or functionality though. References are one such case, and I also added latex support (more as a step towards pevo, but useful in a wiki too I think).
Finally, an upgrade from this:
Well, that's a very good idea. Wiki pages are very well indexed in all search engines and AI bots. I would like to participate but the time component does not allow me to do so now. Maybe I will in the future. I imagine it as a kind of Hivepedia, with descriptions of the blockchain, communities, and tribes with their tokens, contests, and competitions, and all the games here. It could also include an LMAC gallery, a public domain Hive image indexer, and so on.
Great. I'm glad my previous post triggered this full explanation -
I think having a "holly book" for Hive or type of Wiki it's amazing idea and something necessary - this could functionally work as a full set of most important things we got on hive. It's seems like extremely long process and all those terms like RCs , nodes , forks , delegations or even user names should be explained - and words should be in one place where anyone can access and get nicely educated around the topic and new terms in the blockchain which for most people outside the crypto it's woo woo magic stuff.
I'm pretty much sure you can also find somewhere deep in the chain some of the explanations.
But things what is RC and how it works it need to be somewhere visible to explain, other way people got confused.
As an example - me being long term user of hive, being on platform for many years when after 7 years I created secondary acc, I blogged something and wanted to edit because misspelling happen - then obviously I've had error shown - but zero explanation, nothing obviously I could ask more experienced person what is happening to only found out that I don't have enough RC ... So yeah - I've had person to ask, but I can imagine if someone from outside come to the platform and face this problem, I'm pretty much sure that this person will just be frustrated and leave this behind and never come back.
Any error, any issue should be explained then perhaps linked with wiki page which would explain what, why and how..... I hope you'll be able to start with the project and we will be able to link everything together.
I'm happy to put my input but not entire sure what I could offer really.
I had almost the same experience. Joined Steem a while ago, came back with Hive. The delegation I started with made me think there were no limits. It was expired and I hit that RC limit over and over. Found out I had to claim rewards manually (something in steemit had this automated before) and finally someone just gave me $10 of HIVE so I had a sufficient RC to post like a normal user.
Wait a minute. This is HP.... same thing? If only there was a wiki....
The Steem wiki is still up and running, a lot of it would be relevant.
https://www.steem.center
It's an excellent idea and plan. Best of luck 🤞 and that would be awesome.
I'd be happy to write about Saturday Savers Club, also to be part of a general planning group, if that's helpful.
Very much, yes! Do you use Discord?
Yes, I have the same user name :)
Looks great, I'd be happy to help a bit ;) I've already applied on Discord.
You came on my mind while reading @pharesim 's post...
https://inleo.io/threads/godfish/re-godfish-2tz1mbo8n
The rewards earned on this comment will go directly to the people ( godfish ) sharing the post on LeoThreads,LikeTu,dBuzz.
What level of programming knowledge could help you and what language? ✌️
Anything past basic is fine as long as there's the will to learn!
The current stack is Python and JavaScript
Up!! I know something but about php with the Symfony Framework, not as I could contribute since the base is python, It seems that Python is widely used here in the ecosystem, almost everyone uses it
Programming is way less about the language than about the concepts. Python is very commonly used, not only here, because it has a very simple syntax. I started with php myself, and worked with frameworks for many years, but since I got into python I barely use it any more.
If you want to check out a small webapp and figure out how it works I can provide you with the code and help you get it up and running on your local machine, and you can play around a bit. And who knows, maybe in a few weeks you'll be able to contribute something!
I understand, it's true, the point is that I lived in a region that is increasingly complex in terms of exploiting development tools, the connection is terrible, everything is blocked and when using VPN everything gets slower
Add to that that I have a very obsolete computer, Windows 7 with a mouse and a keyboard with problems 😅
More than a thousand things that threaten venturing into another language, one time I made a bot in Python that connected to a proxy and added rules via ssh and I liked it With PHP, obsolescence has not affected me so far, and with Symfony I practically make a website with five commands with very good development standards However, I greatly appreciate your kindness, and I am interested, I have not found much information about the development of hive
There are 2 PHP libraries I know of
https://gitlab.syncad.com/hive/hive-php-lib
https://gitlab.com/mahdiyari/hive-php
Congratulations @pharesim! Your post has been a top performer on the Hive blockchain and you have been rewarded with this rare badge
You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word
STOPHast du dich schon geboostert?
Noch nicht, aber mach ich bald
Thank you for your witness vote!
Have a !BEER on me!
To Opt-Out of my witness beer program just comment STOP below
Is there an existing open source wiki platform that you can add in a back-end implementation that uses Hive? That is where I'd start.
And a good candidate would be tiddlywiki. One could start with their Tiddly Web Adapter plugin and modify it to use the HIVE API instead of the tiddlyweb server.
I am coming from little knowledge of what a good wiki should be able to do, so plugging into an existing one makes sense and saves re-inventing the wheel. This would not need a server, other than the Hive API, of course.
The Hive API doesn't provide standard calls, a lot of information has to be saved in a separate db. User management is also completely different. That's a huge amount of changes to an existing platform, which makes building from scratch seem way less scary. Especially as a simple version is completely sufficient for us to start with.
I'd love to have a chat about your wiki knowledge though, to see what functionality I didn't even think about yet. Do you use discord?
I joined on the channel you posted. Same handle.
The Condenser API states that it is production ready. Can we use this? My main question is how do we want to map wiki entries to hive posts. Maybe those tagged "wiki" with some convention.
!LUV
pharesim, thehockeyfan-at sent you LUV. 🙂 (1/4) tools | trade | connect | wiki | daily
Made with LUV by crrdlx.
I thought we already have one ❤️
https://hive-learn.wiki/de/home
I like this explanations, it was really helpful.
This is a good explanation on this topic at last ... and, at last the community would have a place to refer people for essential Hive knowledge.
Hello, I am from Venezuela, I know more about the project and know how I could help. Thank you.
Congratulations @pharesim! You received a personal badge!
You can view your badges on your board and compare yourself to others in the Ranking
Check out our last posts: