Several people have sent this post to me on Discord, so I figured that I post a follow-up on my resignation from Avalon leader.
I'm a (now former) third-party developer on Avalon, and the only remaining active developer leading up to my resignation. I was the one who implemented the Hive integration on the frontend due to high demand when the blockchain forked that lead to the creation of Hive.
This was the first platform that I joined that lead me to participate on Hive (formerly Steem) in many forms, including being a witness and API node operator here.
On the 22nd February 2023, I disabled my Avalon leader node and resigned as a block producer and consequently DAO member. This was the short speech I posted here:
Dear DTube community,
Today I will be resigning as an Avalon leader and consequently as Avalon DAO member. It is an unfortunate circumstance as I will no longer be able to fulfil my responsibilities as a block producer on Avalon going forward. The @techcoderx Avalon leader will be disabled effective immediately.
I would like to take this opportunity to express my gratitude to all of you for your support during my time as an Avalon leader. Please accept my decision to leave, by unvoting my leader and voting for someone else that can make Avalon better.
Thank you.
I have subsequently assigned myself the "Former Block Producer" title on the Hivemind community here.
@aliveprotocol.There are several reasons, I will only highlight a few of the serious ones here.
The very main reason of my resignation.
The original implementation of Avalon when mainnet was launched was extremely buggy and nodes were replaying very slowly and completely unmaintainable. Over time I have optimized the replay which lead to improved stability, however at its current state it is still unacceptable.
The Avalon blockchain halts as often as Solana, except that most of the blocks are empty. I will not get into the details of what happened that caused these events though.
Being the only active (now former) dev, I will be expected to investigate and fix these issues if I remain a leader as it is one of the responsibilities. Unfortunately this will be cost prohibitive to me (mostly in terms of opportunity cost) and the DAO that will be expected to fund the work. I would rather spend my time and resources on Hive-related projects instead of Avalon which is also plagued with other non-code issues.
Basically the context of the post that people were sending me, linked above. Before getting into it, I have to get this statement out:
I'm very sure many counter-abuse Hive projects (which shall not be named) have known this years ago. I have also raised this issue in the official Discord server months ago.
From the DM with 
As you can see, the curators have zero clue about it. For context, I do not (and never) have access to the curation rooms throughout the entire history of the project.
Only the current sole owner of the Hive account, heim, knows about what is going on here.
@dtube account on Avalon is under control of Avalon leaders with 2/3 vote to execute certain transactions.
@onelovedtube at that time) was against hyperlinking ThemTube videos as just an embed to the centralized platform (that dominate DTube now) people are trying to move away from. This feature was part of v0.9 update that also introduced Avalon. The members that voiced out against this were mainly me, 
@gray00 and 
@vaultec. At that time, the @onelovedtube curation only allowed curating IPFS/Skynet videos which then became unfeasible over time.Now that I'm no longer participating, I can finally have more time for my personal issues that needs my immediate attention and time for working on Hive projects.
Thank you for all your support.