You are viewing a single comment's thread from:

RE: Hive core developer meeting #22

in #meeting3 years ago

at 5:58 Why re-invoke voting on old post? Is the vote burned? Does the author get a reward from past payout votes now?

at about 9:20: One and a half months til hard fork so around middle of June? I like the whole month idea for people to test then the two week warning to the exchanges.

at 12:25 good to hear that the UI's are also being thought about and giving the front end builders time to prepare for changes such as the witness expiration approaching

at 23:10, glad to hear "Keep it simple", and then if needed complicate it.

at 27:30, that left me a bit confused code freeze and testing to start Wednesday then two weeks notify exchanges, a little bit different than earlier in the broadcast.

Thank you for the post and helping keep us informed.

I am still a bit confused over the HF time frame and order, but it still seems like early to mid June for HF 25, and that there will be sufficient time for people to do testing.

Sounds like RC issue still may be up in the air for this hard fork, but also sounds as if progress is being made and I like the keep it simple attitude and then if needed make adjustments.

Did the blocking of votes on old post cause issues? I do not understand why the return to votes on already paid out post.

Sort:  

at 5:58 Why re-invoke voting on old post? Is the vote burned? Does the author get a reward from past payout votes now?

The vote does nothing to the rewards, but the voter does "burn" some voting power. It's almost exclusively an UX change so that people can vote as they want.

at about 9:20: One and a half months til hard fork so around middle of June? I like the whole month idea for people to test then the two week warning to the exchanges.

Yes around june.

at 27:30, that left me a bit confused code freeze and testing to start Wednesday then two weeks notify exchanges, a little bit different than earlier in the broadcast.

Yes, we decided to add some last minute small features (hbd interest only on savings) which pushed the date by two weeks.

Sounds like RC issue still may be up in the air for this hard fork, but also sounds as if progress is being made and I like the keep it simple attitude and then if needed make adjustments.

It was decided to not put it to this hard fork but more about putting it as a soft fork (25.1 basically)

Did the blocking of votes on old post cause issues? I do not understand why the return to votes on already paid out post.

I don't remember why it was blocked @blocktrades can probably chime in, I think it had something to do with hivemind.

Thanks again, I guess people should be allowed to vote on what ever they want even if it means no rewards, I know I have in the past voted on so-called expired post, but I still wanted to let the person know I enjoyed the content.

Yeah, I agree with this change. I onboarded someone recently and they were a bit confused/offput as they found they couldn't even like all the stuff they were discovering which was past payout but of course new to them! It's maybe admirable to try and keep people from wasting voting power, but social considerations should come first & money second! Now, if the blockchain or front ends could somehow detect a vote on an expired post & automatically default to a 1% weight... that would be ideal.

PeakD used to tell you a post was past payout, I imagine they will just bring that back, and then offer leaving a tip or the vote anyway.