If you're listening to the whole thing, please post timestamps as a comment, the first one to do so (and correctly) will get a 100% upvote from me :)
meeting points:
Dev sync:
as usual listen to this part
testnet-based testing (involvement of Hive apps as testers)
We are finally done with all the changes and expect to code freeze and launch the final testnet by wednesday
API v2, coinbase's rosetta api as a new api plugin or as a separate service ? (https://www.rosetta-api.org)
Some discussion regarding whether we should implement this as a plugin in hived or as a wrapper around it, we are leaning towards a wrapper service.
Big feature contribution process for independent devs (review an Hive improvement proposal before starting to code, assess performance impacts etc, goal being to reduce re-doing the work and reduce the amount of review
I proposed a format where devs write a hive improvement proposal with specs (similar to this: https://gitlab.syncad.com/hive/hive/-/issues/152) before starting to work in order to reduce the amount of back and forth and fixes needed when for instance the spec is not fully agreed upon at the beginning.
the conversation then derives into basically how we would need to get a "how to contribute" guide with the expectations in regards to the tests, the performance etc.
Direct RC delegation spec (hive#152) and RC pools or maybe a mix of the two:
We have decided to implement direct RC delegations using a posting auth, if you don't know what I'm talking about you can get more infos in this post: https://peakd.com/rc/@howo/direct-rc-delegations-vs-rc-pools-and-tentative-direct-rc-delegations-spec
from @arcange some discussions on the implementation on the api v2
Quite a few discussions but ultimately it's deemed too early to work on it. It's something that will have to wait 1/2 months when we are past hf25.
Amazing a five year old issue, testing is obviously going pretty good to find some issues in the pre-Hive software. I can see in the future that people may look to the Hive software for building their own block chains.
I like how you all discuss not only the present but also are looking to the future, of what people might want and tools they may want. A solid foundation is not only built on the present needs only, the past has to be looked at, (as in finding pre-hive issues), and planing the foundation layer to support the future needs.
I really like blocktrades idea for wanting to keep it simple simple makes it easier to see what broke.
The api talk was a bit hard to hear anyone but blocktrades, but it sounds like a good thought on the modular hivemind being done first and prior to adjusting the api. Also hf 25 may show some new things not thought about for the new api.
Once again thank you for providing this @howo, I do appreciate the work and time it takes to put together. Biggest takeaway for me was the finding and fixing of an overlooked issue from pre-hive days. The testing people seem to be doing a great job.
Hello and greetings, I don't know much about blockchain, I can't quite understand when you say, timestamp... but I say timestamp is hive.
Hive is the future.
Timestamp of youtube video.
Ex:
0:00 Start
1:00 Blabla...
amazing job
Final Testnet will be launch Wednesday this week.
Thank you for the efforts and thank you for sharing this information. Hive on.
Took a bit for me to get around to this, but I have posted timestamps on the video with my YT user:
Hope this helps. I'll work on doing #24 in a more timely manner.