Conversation

Notices

1. Fedi.Tips 🎄 (feditips@mstdn.social)'s status on Wednesday, 30-Aug-2023 05:27:11 JST Fedi.Tips 🎄

   If you're wondering why certain boosts get shown again and again, there is a feature built into Mastodon called "Group Boosts" which prevents you seeing the same boost twice. This is switched on automatically for everyone, you do not need to do anything to switch it on.

   Unfortunately, it is also set to allow boosts to repeat after 40 other posts, and this number cannot be adjusted by users or admins.

   If you're comfortable using github, vote for this to be fixed at https://github.com/mastodon/mastodon/issues/18693

   • Fedi.Tips 🎄 (feditips@mstdn.social)'s status on Wednesday, 30-Aug-2023 05:40:43 JST Fedi.Tips 🎄

     in reply to

     • Joshix

     @joshix

     They can, if they are installing manually and have the needed coding skills. A lot of people aren't able to do these things though.

     It would be better if there was some official way of adjusting the setting from the admin's preferences page?

   • Joshix (joshix@fosspri.de)'s status on Wednesday, 30-Aug-2023 05:40:45 JST Joshix

     in reply to

     @feditips admins can always edit the source code

   • Fedi.Tips 🎄 (feditips@mstdn.social)'s status on Wednesday, 30-Aug-2023 07:01:58 JST Fedi.Tips 🎄

     in reply to

     • [Yaseenist] Nikola Orsinov [Joseph Grimaldi]

     @orsinov

     Clicking on a thumbs up isn't spam.

     What should non-technical people do when they discover a significant problem in FOSS?

   • [Yaseenist] Nikola Orsinov [Joseph Grimaldi] (orsinov@our.unknowing.dance)'s status on Wednesday, 30-Aug-2023 07:02:15 JST [Yaseenist] Nikola Orsinov [Joseph Grimaldi]

     in reply to

     @feditips@mstdn.social
     Honestly you should not signal boost github issuesy at least not to tell people to "vote"
     
     I don't think the Mastodon Team cares to much about Github "+1" Comments
     
     If you're not gonna make a PR, or add anything original and technical to the conversation, it's just spam

   • Fedi.Tips 🎄 (feditips@mstdn.social)'s status on Wednesday, 30-Aug-2023 07:18:15 JST Fedi.Tips 🎄

     in reply to

     • SpaceLifeForm

     @SpaceLifeForm

     I'm not sure what you mean, as the feature exists already?

     This is about being able to adjust the number "40", not about creating the feature?

     Guess there's possibly a resource issue with higher numbers, but shouldn't that be up to the instance owner to decide?

   • SpaceLifeForm (spacelifeform@infosec.exchange)'s status on Wednesday, 30-Aug-2023 07:18:16 JST SpaceLifeForm

     in reply to

     @feditips

     Unfortunately it is not that simple.

     The server could do it based upon age of when the user last saw the boost. The problem is that this adds more complexity to the server to manage. And, there is no guarantee that the user actually saw (eyeball read) the boost in the first place.

     I think this is best managed client-side, and that requires the client to track which post was boosted, and then would likely not be over 24 hours before it is aged out of a cache. Though, if you have the ram, you could make the expiry time longer.

     Needs to be client side, but continue to waste bandwidth as happens now.

     It is important that the original post creation timestamp is NOT a factor.