i should be able to re-boost posts without unboosting them first

[blogdiva@mastodon.social]

@eniko like, we should be able to reboost after a certain period of time. maybe a week or month?

[fromthefourthplanet@mas.to]

@eniko
is *that* how it's done????

[orca@nya.one]

@eniko@mastodon.gamedev.place I heard Misskey can do that.

[thomasjwebb@mastodon.social]

@eniko yes! The one loophole I use is do a quote toot each time (even if I type the same thing each time). Feels like a bug that this is missing.

[steter@mastodon.stevesworld.co]

@blogdiva @eniko @catsalad Hm. Spitballing here. It sounds like it could be done by adding a grayed-out ReBoost button next to the Boost which changes to functional once a boost is observed by the software. That has slim chance because of small screen width requirements. Or the Boost could change to ReBoost when you boost a post, as long as there is an UnBoost option in the drop-down. I'd go for that, myself.

[nawer_rapter@mastodon.social]

@eniko me, if this is allowed: did I-? Wait didn't I? But didn't I-? Did they change? Wait what? Well just to be sure *this is the 10nth time I boosted the same post*

[jandi@mastodon.social]

@AcornSquashbuckler Tracked here for Mastodon, with an interesting discussion: https://github.com/mastodon/mastodon/issues/15219

[jandi@mastodon.social]

@eniko I agree.

It seems doable client-side (unlike the queue mentioned in other post), maybe my favorite clients @pachli & @phanpy are interested in the idea?

[lisamelton@mastodon.social]

@eniko This.

[delilahtech@tech.lgbt]

@eniko
Scheduled boosts is where it's at (depending on your client, I suppose)

[eniko@mastodon.gamedev.place]

@FromTheFourthPlanet yep

[eniko@mastodon.gamedev.place]

@blogdiva I mean I think I should be able to do it as much as I want. Not sure why you'd limit it

[utterlymundane@hachyderm.io]

@eniko @blogdiva
Cons: tumblr-style “50 reboosts in as many seconds for comic effect”
Pros: tumblr-style “50 reboosts in as many seconds for comic effect”

[oblomov@sociale.network]

@eniko @blogdiva yeah, there's no reason to limit. At the spec level it's not limited (you can have multiple Announce for the same object from the same actor, and the “shares“ collection on which they get recorded should be able to hold multiples). This is entirely a Mastodon limitation, and I suspect it's mostly due to UI limitations (how do you cancel an announcement if there can be multiples? The boost button ceases to be a toggle.)