Consider not updating for small restoration time changes #62

Closed
opened 2024-10-27 10:25:22 -07:00 by buckbanzai · 1 comment
Owner

Blocks #21

We might not want to post a reply/edit the post for every time estimate that the feed has, like we currently do. This is a little less of a problem while they're just replies, but once we move to editing the post, each edit triggers a notification for anyone who's liked/boosted the post.

Potential Solutions

  • Delay posting estimated time updates until they've remained the same for some time (30m or so?) - this has the downside of if it keeps bumping by small intervals, it'll never get updated
  • Only post an estimated time update when the estimated time is some time (30m-1h?) different than the currently posted one - I think this is likely the better route forward

Current Behavior
time_updates.png

Blocks #21 We might not want to post a reply/edit the post for every time estimate that the feed has, like we currently do. This is a little less of a problem while they're just replies, but once we move to editing the post, each edit triggers a notification for anyone who's liked/boosted the post. **Potential Solutions** - Delay posting estimated time updates until they've remained the same for some time (30m or so?) - this has the downside of if it keeps bumping by small intervals, it'll never get updated - Only post an estimated time update when the estimated time is some time (30m-1h?) different than the currently posted one - I think this is likely the better route forward **Current Behavior** ![time_updates.png](/attachments/a8f22e79-3f7f-4a98-86de-bf313ea4913e)
buckbanzai added reference quieter-restoration-time 2024-10-27 10:28:12 -07:00
Author
Owner

Going to bump it up to an hour minimum, we could likely add some logic to make it do more frequently/etc if the current time is close to the estimated time to make sure we never run over/past it without posting about it if there's a newer one, but this can likely be a future improvement if it proves to be an issue regularly.

Going to bump it up to an hour minimum, we could likely add some logic to make it do more frequently/etc if the current time is close to the estimated time to make sure we never run over/past it without posting about it if there's a newer one, but this can likely be a future improvement if it proves to be an issue regularly.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: buckbanzai/seattlecitylight-mastodon-bot#62
No description provided.