By active voting stake, my guess is there is enough to pass 13 week + instant powerdown with fee, at the moment. But it seems like a discussion of the exact mechanics is still going on, and there's no

I agree.

Voted for Keep 13 weeks AND 10% burn mechanism

Generally, I prefer for other teams to work on UIs, mainly because there's so many types of UIs that can be created to do many different things. I do have two guys that make occasional contributions to

The fee for instant powerdown would discourage exchanges from powering up their customer's funds without their permission. On the security side, there's been discussion in mattermost for various mitigation

Some variation of this sounds much better to me than the proposal to simply change the powerdown time from 13 weeks to 4 weeks. I don't believe a simple change to 4 weeks would have much impact, because

Very little time core dev time from my team has been spent on curation rewards changes (maybe two weeks) or the apr savings change (this latter was 2-3 days probably). No core dev time has been spent on

To be honest, I would never characterize the sound of my voice that way. I'm always vaguely annoyed with it when I hear it recorded, but I'll take the compliment anyways :-)

I suspect it does qualify me as a philanthropist. It was always one of my long term goals, and I finally made it.

For a while, the easiest way to make money in crypto was to raise money for a new project. That's probably still true now, although the regulatory risk for such activity has been steadily increasing. Nor

EOS code was originally being developed as an upgrade to Steem. How is it that people haven't figured this out by now? It was just determined to be more lucrative to launch an ICO instead.

Hive sent to the DHF is instantly converted, so when the stabilizer sends Hive to the DHF, this becomes HBD immediately. Unfortunately, due to specification change to the proposal system, only 1% of this

The downward pressure from the stabilizer proposals is increasing at a fairly rapid rate as the DHF budget increases. By the time we're ready for the hardfork, it wouldn't surprise me if the price of HBD

Actually, I forgot one more change in HF25:

We're doing our best to avoid "surprise" new features as we prepare for HF :-)

I think the primary use case is to ease onboarding for Hive apps that create accounts for new users. This will enable them to create new accounts and delegate RC rather than HP, which lowers the incentive

Here's posts that describe hardfork changes (written for Hive enthusiast, not for devs):

No, it's not like that at all. No analogy is perfect and they should often be avoided, IMO, but if the complexities of the actual mechanism are too complicated, here's a simplifying analogy: it's like

Each person makes up their own personal list (assuming they want to).

It's already been proven on any number of social media platforms that automated bots can spam them to death if there's no way to stop the spam. Decentralized blacklists allow an individual to choose to