Experimental new bucket-style queues for feeds. #911
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is more of a thought-experiment-as-code more than something I think works, but anyway. Off the back of #910, I was trying to think of why you'd want to set different refresh periods. It feels like Hookshot should have enough information to figure out an "optimal" refresh period, which in turn would reduce the need for user involvement.
The ultimate goal being that feeds that are active refresh more often than ones that are not, making hookshot feel faster. Some thoughts remain thought: