This meeting was pushed back a few times because most of the team was in the middle of developments or busy improving the api nodes/gitlab so there weren't much to sync on.
Meeting points:
Dev sync
It's better to listen to this one.
Rc delegations and potential performance hog
RC delegations, is now pushed and ready to be reviewed by blocktrade's team. Should this review be positive, I'll probably spin up a small testnet for everyone to play with it.
There is one thing regarding rc delegations (that was also present in the RC pools implementation) that can be worrysome, we discuss some of the potential solutions to it. But we didn't go too much in depth as blocktrades team didn't see the code yet so it's hard for them to truly discuss the solutions.
HAF progress and communities migration to it
(some expected times + is it worth to wait for the migration to do some developments on it)
I working on communities after rc delegations, so since there was a plan to migrate hivemind to HAF, and as per this comment by @blocktrades: https://peakd.com/hive/@blocktrades/qxdi2b
In my opinion, it would be a mistake to start this work [work on communities] before we complete HAF work. The next step in hivemind's evolution is to port it to HAF. After that, it should be no big deal for someone to enhance communities further.
I wanted to confirm the best way forward, ultimately after discussing we decided that porting hivemind onto HAF would not be a blocker to some development on communities right now.
Gitlab issues
The gitlab instance where most of the code, issues etc suffered a failure and all the backups also failed, so we didn't lose code but some of the metadata (issues/merge requests/comments) from may to august were lost. If you submitted something in that timespan, make sure to resubmit it.
Sounds like a lot of small optimization cures helped with the speed up, very nice to hear about the increasing traffic and no slow down.
Can you remind me what HAF stands for?
Also for @blocktrades; Are you still looking at or working on a change/new user reputation system?
Sounds like there are still a few things being worked on optimization wise for Hive, any time frame for beginning discussions on HF 26 needs, wants and desires for changes from the community? or is there already a place for people to go and leave their thoughts for changes to the foundation layer of Hive? if so I may have missed that psot.
Hive Application Framework
Yes, I'm hoping to get started on a completely new type of reputation system later this year.
This time, I am thinking about doing a relatively small hardfork, feature-wise, in order to reduce the time to test and deploy it a bit, but not at all sure yet. Hopefully, I'll be able to include some of my ideas for the hardfork in our next update post. Two I can think of right off hand are option for accelerated power down for a fee and a change to speedup transaction finality.
But you can post about ideas for new changes anytime you like. While I don't always comment, I always look over the ideas posted in the "Hive Improvements" community.
Thank you I will look in the community, and if I have some ideas, will make a post there. Also looking forward to see what you come up with for a reputation system.
Love this team. Keep it up.
Great work, really excited to see it implemented!
🤣
Great article.
Is wonderful all this work. Thanks for share.
@howo I admire their dedication, they make a great team.
Congratulations @howo! Your post has been a top performer on the Hive blockchain and you have been rewarded with the following 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
STOP