Viewing a response to: @jesse2you/re-minnowsupport-importan-changes-to-minnow-support-upvote-bot-behavior-20180120t175523522z
We can look into this. We want to see where the numbers lay, but I suspect the best short term fix is to wait a bit longer on one cool-down and set the new 'time' each day to be earlier. Will take many days to slide to a time that is too late.
| author | discordiant |
|---|---|
| permlink | re-jesse2you-re-minnowsupport-importan-changes-to-minnow-support-upvote-bot-behavior-20180120t182038537z |
| category | minnowsupportproject |
| json_metadata | {"tags":["minnowsupportproject"],"app":"steemit/0.1"} |
| created | 2018-01-20 18:20:36 |
| last_update | 2018-01-20 18:20:36 |
| depth | 2 |
| children | 4 |
| last_payout | 2018-01-27 18:20:36 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.114 HBD |
| curator_payout_value | 0.024 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 243 |
| author_reputation | 12,231,722,608,778 |
| root_title | "Important Changes to Minnow Support Upvote Bot Behavior" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 30,923,255 |
| net_rshares | 12,591,880,280 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| jesse2you | 0 | 9,435,721,605 | 100% | ||
| jerrytsuseer | 0 | 3,156,158,675 | 10% |
<center>I found it problematic, and I didn't notice this being an issue until **after** this recent update. <br> Here is how I had been proceeding with posting to minnowsupport/$upvote. I would open Discord in the morning/evening, I would click in the search area, the drop-down would show my _**UPDATE**_ posts or mentions. Click update, and it shows the most recent upvote. So, I set the timer in my phone to alert me when **12 _(twelve)_** hours + one minute **after** that last upvote occurred. I would be denied the upvote because the bot was counting the SECONDS since the last upvote. "Can't upvote, you're in cooldown for another 5.4 seconds" (for example) ~ Now how in the heck can we, as simple minnows, know the EXACT SECONDS of our previous post? I thought this was NITPICKING in the extreme. I was already adding a **whole sixty seconds** to the previous post time ie... previous upvote at 7 am, I set my timer for 7:01 PM, 12 hrs + one minute. Still got denied for *blah blah* number of seconds. 😜 All that being said @minnowsupport and @discordiant, I have no problem with a 24 hr cooldown period, I just didn't know about the change. Thanks for pointing me to this post. </center>
| author | jerrytsuseer |
|---|---|
| permlink | re-discordiant-re-jesse2you-re-minnowsupport-importan-changes-to-minnow-support-upvote-bot-behavior-20180121t121339928z |
| category | minnowsupportproject |
| json_metadata | {"tags":["minnowsupportproject"],"users":["minnowsupport","discordiant"],"image":["https://steemitimages.com/DQmY7nHH7FERsFiEJrj14UQEqcFE4QzRJAoCxS4BvGRSfyj/image.png"],"app":"steemit/0.1"} |
| created | 2018-01-21 12:13:39 |
| last_update | 2018-01-21 12:15:03 |
| depth | 3 |
| children | 2 |
| last_payout | 2018-01-28 12:13:39 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 1,299 |
| author_reputation | 214,823,599,639,537 |
| root_title | "Important Changes to Minnow Support Upvote Bot Behavior" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 31,091,409 |
| net_rshares | 0 |
We are working to add a command like $cooldown that will help you to see in HH:MM:SS when your next $upvote can occur. We think this should be a matter of picking your best post from the ones you have already made, not making a post just for the purpose of using our $upvote on it. We really were draining the bot, so the 24hrs had to happen. If you have to wait an extra minute or even several hours after your cooldown to have a convenient time to do $upvote, that is fine. You aren't missing something by doing it later than right on cool-down. Steemit won't go anywhere in that time.
| author | discordiant |
|---|---|
| permlink | re-jerrytsuseer-re-discordiant-re-jesse2you-re-minnowsupport-importan-changes-to-minnow-support-upvote-bot-behavior-20180121t121716893z |
| category | minnowsupportproject |
| json_metadata | {"tags":["minnowsupportproject"],"app":"steemit/0.1"} |
| created | 2018-01-21 12:17:15 |
| last_update | 2018-01-21 12:17:15 |
| depth | 4 |
| children | 1 |
| last_payout | 2018-01-28 12:17:15 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.036 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 588 |
| author_reputation | 12,231,722,608,778 |
| root_title | "Important Changes to Minnow Support Upvote Bot Behavior" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 31,092,041 |
| net_rshares | 3,156,158,675 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| jerrytsuseer | 0 | 3,156,158,675 | 10% |
<center>I agree, but I say again, I didn't/don't have a problem other than ## I didn't know.</center> <br> I really like the idea of a $cooldown command to show me exactly when the last upvote occurred. Even though I am small potatoes, I would consider delegating a small amount, _**IF**_ I understood delegation better ha ha... Thank you for your time and effort in all this. 
| author | jerrytsuseer |
|---|---|
| permlink | re-discordiant-re-jerrytsuseer-re-discordiant-re-jesse2you-re-minnowsupport-importan-changes-to-minnow-support-upvote-bot-behavior-20180121t122951907z |
| category | minnowsupportproject |
| json_metadata | {"tags":["minnowsupportproject"],"image":["https://steemitimages.com/DQmYS4qc5AtcqR2oqyvgTfFcNprHWdzV1LnNHfWaunQe2AE/image.png"],"app":"steemit/0.1"} |
| created | 2018-01-21 12:29:51 |
| last_update | 2018-01-21 12:29:51 |
| depth | 5 |
| children | 0 |
| last_payout | 2018-01-28 12:29:51 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 466 |
| author_reputation | 214,823,599,639,537 |
| root_title | "Important Changes to Minnow Support Upvote Bot Behavior" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 31,094,523 |
| net_rshares | 0 |
So every month,or two you are posting an hr. later... :-) I an not one to post at same time,I know there are better times to post,and a lot of people try to post at peak use times,I can see were this would hinder those attempts. I believe it would be harder to manipulate a two vote in one day w/ 22 hr window ,than having to time it right to post at same time each day. thank you for your response! and for considering my input. Namaste!
| author | jesse2you |
|---|---|
| permlink | re-discordiant-re-jesse2you-re-minnowsupport-importan-changes-to-minnow-support-upvote-bot-behavior-20180120t185021129z |
| category | minnowsupportproject |
| json_metadata | {"tags":["minnowsupportproject"],"app":"steemit/0.1"} |
| created | 2018-01-20 18:50:21 |
| last_update | 2018-01-20 18:50:21 |
| depth | 3 |
| children | 0 |
| last_payout | 2018-01-27 18:50:21 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 446 |
| author_reputation | 2,060,285,142,662 |
| root_title | "Important Changes to Minnow Support Upvote Bot Behavior" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 30,928,790 |
| net_rshares | 0 |
hiveblocks