@sethmlarson That's an interesting concept. One problem might be to determine the "time of last boost", because that's not a part of Mastodon's status entity, and thus might have to rely on incomplete information the client happens to have about the status.

Other than that, "delayed boosts" and a "boosting queue" that gets evenly spread in time are great ideas!