Totally never saw this site until I read about it in your post.
Let’s look to why? There are 4 key links on that about page.
- …https://faucet.1hive.org/#/
- …https://honeyswap.org/#/swap
- …https://info.honeyswap.org/ link to docs takes one to …https://about.1hive.org/docs/honeyswap/
- …https://1hive.org/#/
The only one that even has a link to the above is the info.honeyswap.org and this one while there and findable is somewhat hidden under ‘docs’. Which I would have thought would be docs - for honeyswap and not 1Hive.
Look at the above key links and as far as I can tell there is no consistent high level menu that has the key links to 1Hive. I want to point out I am not ‘mad’ or bitching here I am just pointing this out, because I had the same experience with Maker and suggested some time ago that they make a kind of global menu bar that every sub-domain or approved Maker site (where users DO Maker stuff on) or documentation, etc. HAVE.
I see this lack of high level organization throughout the DAO landscape, Maker, /r/ethtrader on reddit, sourceCred, and 1Hive so it isn’t like this is just a 1Hive problem. It is a DAO bootstrapping legacy where anyone works on stuff but no-one is really guiding a higher level experience, vision and unifying the information and access experience for users.
This literally is the result of the ‘bizarre’ model of development being applied to DAO’s. Linux documentation and standardization as far as I can tell took a good 5-10 years to put together. Fortunately the operating system itself helped, and the user only needed to download a package and install it - there were no linux ‘dapps’ or ‘defi’ there were just software packages, drivers, etc. to install and these generally would use the operating system itself to fill out the documentation available in man pages etc. We have no such formalized operating system that DAOs could structure themselves within that could provide the higher level organizational characteristics (like an operating system) to focus ‘bizarre’ community development into one of a number of forms of ‘cathedral’ organizational features access and documentation.
Literally one can look at a DAO as a kind of software package for users - our problem is that we have no concept of an operating system (crypto/defi) that unifies this functionality in terms of standardized I/O ports, drivers, protocol services (so any service using a particular protocol is interoperable), etc.
1Hive doesn’t need to solve what I see as a growing problem in this space (just like I saw it as a growing problem in the opensource community at the time) but it simply needs to put some organizational order to the chaos.
I do think this is an open problem in the space RIPE for a new approach. In effect unifying not just what we do in the crypto/defi space, but how it is done, and how it is all presented to the operator/user.