Several months ago, and as we got access to broader development resources, we found a great opportunity to start helping out with some of the amazing work being done by @blocktrades and team in developing essential hive-focused tools and projects.
As of mid June 2024, we assigned several developers to start working on HAF Block Explorer UI, and then progressed tackling some aspects of the backend components of HAF BE, and more recently with Denser project, the front end replacing condenser (current hive.blog code).
Contribution view across last few months on gitlab
Some of our recent updates regarding our work on that front:
- Development Updates - Issue 1
- Development Updates - Issue 2
- Development Updates - Issue 3
- Development Updates - Issue 4
- Development Updates - Issue 5
While this effort to date has been funded by ourselves, and as we continuously expand our involvement here, funding the devs on our own will not be realistic as dev costs are pretty substantial, so we wanted to reach out to the Hive community so that we can continue and increase our involvement in building great tools for our Hive ecosystem.
In addition to actual development/coding, we have been engaged and working towards increasing our efforts in product feature ideas, improvements, testing/QA, and fixing issues to expand into larger-scale ownership in Block Explorer through its various components.
The work is essentially focused on the below hive projects:
We will have 4 full-time resources for the time being. Some of those resources have been working on the above projects for a much longer time as part of @blocktrades team, and will continue working now as part of our team and be paid by this proposal. The others are developers who recently started working or are kicking off the work now with us.
We are requesting 390 HBD/day to cover the payments to the team.
As we have in the prior few months, we will continue providing continuous updates on our development progress.
Support This Proposal (325):
- Vote for our proposal on peakd
- Vote for our proposal on ecency
- Vote for our proposal on Hive wallet
- Vote for our proposal via hivesigner
Thank you for your support in helping us improve Hive and its ecosystem.
I'm not sure how I feel about it. I'd very much prefer if some features were completed "in the house", so I can physically poke the responsible developer, when they don't do what I want or something is buggy - it is a lot harder to do that remotely :o)
<p dir="auto">There are some important things that are still missing: <ul> <li>comment page, similar to hiveblocks - personally I only use it to see what people use to format their posts, so all the vote details etc. are not so important for me <li>supplementation of wallet tab with all balances, so when I make some financial operation, the asset does not disappear only to emerge after a while, but just moves from one row to the other (or to some other account's balance in case I transfer funds out); now funds in open orders, pending conversions and incoming escrow transfers are not visible anywhere <li>perspective tracking - when I'm looking at account page I'm in perspective of that account, which should influence how operations are visualized, f.e. <code>"alice voted 100% on bob/hello-there", but <code>"alice/introduction received 50% vote from bob" - the latter would be formatted as <code>"bob voted 50% on alice/introduction" when viewed from neutral perspective like block page; perspective tracking also allows indication of outgoing transactions f.e. with slightly different background color compared to incoming transactions <li>operation visualizers need a lot of fixing; couple weeks ago I've discussed many cases with jlachor, but I'm not sure if anything was finished; for example it should not be <code>"alice set recurrent transfer of 0.000 HBD, 5 executions every 26 hours to bob", but <code>"alice canceled recurrent transfer #3 to bob"Thank you for the feedback and sharing your thoughts.hey @andablackwidow,
The problem with writing issues is that they are good if the potential solution requires investigation, discussion or documentation on why certain way of handling was chosen. But in cases like point 4 it is actually easier and faster if I make changes myself than to describe it for others to do. I'd have done that long ago if I had an environment ready where I could test such changes before proposing them (and the last time I did anything on front-end was 25 years ago). So next best thing is to stand on top of the dev who can show result of the changes locally before they are committed :o)
By the way, point 4 issue is only here because people that made those visualizers in the first place are not actually using Hive, so they are not familiar with fine details. I'm sure it does not apply to you.
Hello! I'm an actifit supporter since the very early days. You do quality dev work. I'll likely support this.
But wondering about the 5 work items you will be focusing on.
What do the first 2 add to the existing block explorer at https://hiveblocks.com/ ?
What do the 2 trackers do that will be helpful to Hivers like me? I see that the
but maybe you can say more these trackers' utility.
As for Denser, I use @peakd which I prefer, and which also has periodic upgrades. I guess it is good to have choices and decentralization in front ends, but is this duplication of work? Will what is done for Denser be helpful for eccency and inleo and peakd and hive-engine outpost tribes? I guess it will since the code seems to be open source at https://gitlab.syncad.com/hive/denser.
Just trying to understand what's going on behind the scenes. Again, I like and respect your work! Have a nice day :)
"Behind the scenes", I approached mcfarhat last week and asked if he would be interested in taking over management of the UI for the block explorer (and later the backend too, once their group has more experience there).
This was because our team has accomplished the main things I wanted to accomplish with the block explorer at this point (fast and lightweight enough for all the API nodes to deploy it, giving us a truly decentralized block explorer). But of course there are many useful features that can be added, and mcfarhat's team was proactively adding some nice features, so his team seemed to be the best one to take on maintenance of this project, allowing me to free up some resources to work on other projects.
The balance and reputation trackers are actually core Hive APIs that the blocktrades team developed. They are designed to be used by all Hive apps (haf block explorer uses both APIs, hivemind uses the reputation API). But again, I think it is good if more teams know how to work on these services, and there is one feature for sure that should be added to balance tracker to serve the needs of both the block explorer and other apps, so this seemed like a good opportunity for another team to contribute to balance tracker. Probably in the future there could be more features as well, it really depends on what needs Hive devs may have.
Regarding Denser, I should clarify that most of the work on Denser will still be done by my team at least in the near term and I am funding it out of my own pocket (well, technically it is Blocktrades the company that is funding it). The actifit team is just getting their feet wet on this project, as we think its good to have multiple teams who are familiar with the code and can contribute to it, and it can give his team some work to do at times when there is no particular feature being added to the block explorer (new feature inspirations often just "happen" unpredictably).
As to Denser's purpose, we are developing it to replace Condenser (the code used for hive.blog and several other sites), using more modern libraries for web design. As you noted, it is open source, so anyone can freely take the code and use it for their own web site, and we are specifically designing to make it easy for people to do this.
Thanks @blocktrades for responding, saved me some typing lol
Thanks for the comprehensive answer to my question. I appreciate your time and effort on small things like this and of course on the big things you and your company do that really got HIVE to where we are today. Looking forward to our bright shared future!
Ok, let's do this....
You have my sword
You have my support
Saya sangat senang bisa mengembangkan proyek ini, dan semoga saya bisa berada dalam proyek anda ini, sebagai pemula di hive. Sukses untuk program ini
Thank you for your witness vote!
Have a !BEER on me!
To Opt-Out of my witness beer program just comment STOP below
Very worthy projects. It appears I may have been the first to vote for your proposal. Mine is a small vote but I hope it is the first of many.
!PIZZA
Congratulations @mcfarhat! Your post has been a top performer on the Hive blockchain and you have been rewarded with this rare badge
<table><tr><td><img src="https://images.hive.blog/60x60/https://hivebuzz.me/badges/toppayoutday.png" /><td>Post with the highest payout of the day. <p dir="auto"><sub><em>You can view your badges on <a href="https://hivebuzz.me/@mcfarhat" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">your board and compare yourself to others in the <a href="https://hivebuzz.me/ranking" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">Ranking<br /> <sub><em>If you no longer want to receive notifications, reply to this comment with the word <code>STOPThe Hive.Pizza team manually curated this post.
$PIZZA slices delivered:
(1/10) @danzocal tipped @mcfarhat
Please vote for pizza.witness!