Witness Update @blue-witness - Re: Core Dev Meeting #7

in #witness-category4 years ago

My take on the Hive core developper meeting #7 update by @howo

Thoughts about the upcoming hard fork 24:

@blocktrades is arguing for only implementing business logic in the current fork and adding SMTs with a fork in the near future.

I like it for three reasons:

  • It cleans up boring infrastructure issues first.
  • The SMT hard fork should mainly be about SMT implementation. That sends a clear message to the outside world without being diluted by weird Hive particularities that nobody but we understands or cares about.
  • It makes it easier to attribute changes that will occur to their respective forks.

Sneaky minor fourth reason: I prefer frequent but minor forks over major, convoluted ones. It gets everybody used to a faster development cycle and makes changes and side effects more visible.


More ideas for a later date:

  • Adding downvote power delegations
    • Yes, please!
  • Adding a decay to pretty much any "hive power" operation (proxy, witness vote, proposal vote, delegation etc)
    • Sounds reasonable. I'm hoping for a sufficently long time period, e.g. 12 months + 6 months linear decay, or 18 months with no decay, because I can't imagine anything more tiring than being confronted with witness vote campagins every few months.
  • Reducing the number of daily votes
    • Great idea. Those 0.01% votes don't do much for most. Except for some extremely large whale accounts. Those will be forced to delegate to alts in order to not blow up rewards with every vote. Unless the number of votes is relative to account size - which adds more complexity to Hive. Or SMTs happened before and votes are decoupled from HP.
      Needs more discussion.

Vote for my witness: @blue-witness
Sort:  

Downvote power delegations?

I knew this had been mentioned in the past but didn't realize it was this close.

That could be helpful when I manage to get the @steemflagrewards replacement up. Interesting

It was the second thought I had after hearing about the introduction of a separate pool for downvotes.
The first was: great, now abusers get to be dicks for free.
The second was: if we can delegate HP, why not downvotes as well.
Especially because the risk reward structure of using downvotes for small accounts is terrible.
As a small account you won't survive retaliation and your downvote don't matter. So why not pool it and make it useful.

To be honest, I'm still surprised free downvotes worked as intended.

I missed this: why are you working on replacing SFR?

Absolutely right. The risks are there and those that downvote for even the right reason may suffer consequences, social and otherwise more often than not.

Like to think this problem as a sort of outworking of the type of ideology that supposes police could be replaced by private security. As a matter of fact, I think it gives us a sort of picture of how that sort of thing would pan out which is not particularly well considering human propensities but I'm going off on a bit of a tangent.

Some people may have the big picture thinking and consideration to work to moderate / negatively but I would say it's a minority for some of the reasons you outlined.

As for the last thing, I had lost interest and the chain split really derailed my motivation but there are still a few people that wanted to a hive version of SFR.

It's really something I want to offload and move on from because I don't really care to play "flag and robbers" much as there are more profitable or enjoyable uses of my time like game development.

It might be healthy do create a game for a change. But don't expect people to not be angry at your for no particular reason ;)

What kind of game are you thinking about?

The concept I had in mind is based on a tactical combat technique known as the buddy rush aka bounding overwatch.

Would also like Worms-esque projectile physics for weapons like mortars and think Clickteam Fusions's built in physics engine will help facilitate that.

That sounds like great fun.