RE: Retrospective for the first year of Hive - leave your feedback !!

[gaottantacinque]

Categories _{(for further discussions)}   👇

 

Comments

[gaottantacinque]

Communities

[gaottantacinque]

Documentation for developers

[inertia]

If we're talking about the whole year, on the topic of documentation ...

1. Went well:
   • The team did an excellent job setting up the initial space for devportal: https://developers.hive.io/
   • Communicated the goals for devportal and executed branding transition.
2. Went wrong:
   • We lost @originate along the way.
3. Shout outs:
   • @rolandp, @good-karma, and @therealwolf for establishing the hosting, repositories, CI/CD protocols, and branding assets.

[gaottantacinque]

Frontends

[enforcer48]

1. Went well:
   • PeakD, Ecency, Dapplr, etc. rose from the splitting mess.
   • Continual developments on the said front ends are still happening.
2. Went wrong:
   • Some community features are broken, but that's more on the Hivemind end, I believe.
   • Results of voting have delays now.
3. Shout outs:
   • @peakd, especially @jarvie and @asgarth and those who helped along the way.
   • @dapplr for jumping into the ecosystem and trying
   • @ecency for being a mobile staple for folks.

[phage93]

1. Went well:

• PeakD, Ecency, leofinance, nftshowroom

1. Went wrong:

• synchronization with some nodes is difficult, I do not know who is to blame, but it is very cumbersome to change the nodes by hand for a normal user.

1. Shout outs:

• Good job to @asgarth and @jarvie

[gaottantacinque]

I agree on the nodes issue. For instance on peakd when you get a 404 page due to node issues, it lets you choose the node to use but the url parameter (url?node=chosen-node) does not follow you around. I know that you can specify a different node in the settings but most of the times I only want to temporarily switch to a different node (I know, I’m lazy). That should be an easy fix though - cc: @asgarth @jarvie

[gaottantacinque]

Games

[enforcer48]

1. Went well:
   • @splinterlands made it to Hive.
   • More games such as @dcitygame and @cryptobrewmaster continued to expand in the ecosystem.
2. Went wrong:
   • The split from Steem really threw a monkey wrench into the flow of things.
3. Shout outs:
   • @yabapmatt and the team for keeping @splinterlands strong.
   • @gerber for continuing on with dCity.
   • @rollie1212 for being the communication head for @cryptobrewmasters.
   • @risingstargame for being a fun addition to the chain.

I'm sure there are others, but this is the best I can think of on the top of my head.

[phage93]

1. Went well:

• splinterlands, cryptobrewmaster,dcity

1. Went wrong:

• nothing that is not resolved by the teams

1. Shout outs:

• splinterlands@yabapmatt and @aggroed about
• cryptobrewmaster@rollie1212 and his team about

[gaottantacinque]

Tribes

[enforcer48]

1. Went well:
   • Most major tribes migrated over to Hive
   • One of them excelled: LeoFinance
   • Cool utilities such as @hiveonboard debuted thanks to events like Hive Hackathon, which was partially sponsored by the STEMGeeks tribe.
2. Went wrong:
   • Some tribes got devastated by JSun's takeover (i.e. SteemAce, Upfundme, Photo); they basically ceased to function the way they did before.
   • Other tribes lost the momentum due to the chaos of the takeover (i.e. CreativeCoin)
3. Shout outs:
   • To all the tribe owners who kept their tribes running after the migration: @khaleelkazi, @themarkymark, @neoxian, @jongolson, etc.

[jarvie]

Sad there is no section for communities since this is a Hive recap and it's where peakd has seen the biggest growth on our site. But I guess you'll get some scot-bot users to comment here about their tribe.

[keys-defender]

As written in the post, these Categories were only added to get the ball rolling and I expected the users to add many more. I will add it myself then 👍

[keys-defender]

Do you think there is anything positive about tribes?

And do you have a suggestion on how the issue you mentioned could be mitigated?

[keys-defender]

@jarvie Eg. Do you think it would be feasible to have bots request an api key that has to be approved by 1 or 2 top 40 witnesses and revoked if abused?

[gaottantacinque]

Security

[keys-defender]

• unmaintained apps with known and unfixed security issues should be removed from the wall of featured Hive apps

[gaottantacinque]

Onboarding

[jarvie]

WENT WELL
Hiveonboarding made it incredibly simple and fast to get keys.
PeakD and others integrated it

NOT GOOD YET
New users still don't know how to use those keys effectively

SHOUT OUT
@roomservice @cardboard

[gaottantacinque]

LEO / CUB

[gaottantacinque]

Price

[jarvie]

WENT WELL
We spent the year focusing on projects and products and tying them to things other than price... so we could have a foundation for more than a momentary boom.

WENT WRONG
We saw that many many people came only for the money and thus we had many many people leave because that was what they were sold.