Mastodon has a built-in system to prevent you seeing the same post boosted again and again.
-
Mastodon has a built-in system to prevent you seeing the same post boosted again and again. However, it allows boosts to reappear if 40 other posts have passed through your main timeline, and this is why you may see the same boost repeated.
As the Fediverse is now much busier, Mastodon's devs are raising this number to 80 other posts (technical details are at https://github.com/mastodon/mastodon/pull/39784). This should hopefully be in the next update.
(Thanks to @nitrml for pointing this out
) -
Mastodon has a built-in system to prevent you seeing the same post boosted again and again. However, it allows boosts to reappear if 40 other posts have passed through your main timeline, and this is why you may see the same boost repeated.
As the Fediverse is now much busier, Mastodon's devs are raising this number to 80 other posts (technical details are at https://github.com/mastodon/mastodon/pull/39784). This should hopefully be in the next update.
(Thanks to @nitrml for pointing this out
) -
@atarifrosch @FediTips @nitrml This – I'd set my limit way higher.
-
@atarifrosch @FediTips @nitrml how about using a timelimit instead of (or maybe in addition to) a post count?
I really don't want to see multiple boosts of the same post within 24 hours. But maybe after 168 hours would be acceptable.
-
@atarifrosch @FediTips @nitrml or just make it a % of the posts per hour on the given server or timeline.
-
@atarifrosch @FediTips @nitrml or just make it a % of the posts per hour on the given server or timeline.
@masukomi @atarifrosch @jernej__s @hyc
These suggestions have already been made by many people (including myself) on the related issue at https://github.com/mastodon/mastodon/issues/18693 so the developers are aware of them.
I'm not sure why they are going with a simple number change, but guessing that this is quicker and easier to do (and possibly uses fewer server resources?).
-
@masukomi @atarifrosch @jernej__s @hyc
These suggestions have already been made by many people (including myself) on the related issue at https://github.com/mastodon/mastodon/issues/18693 so the developers are aware of them.
I'm not sure why they are going with a simple number change, but guessing that this is quicker and easier to do (and possibly uses fewer server resources?).
@FediTips @atarifrosch @nitrml Speaking as a Rails dev, there are many ways to do this calculation and have it be trivial. Not only wouldn't it be much during the query, but you could also have a process that runs daily to calculate the average posts per hour in local and federated feeds and just go off of that pre-calculated number for the rest of the day.
This is just a lazy short-sighted solution.
-
@atarifrosch @FediTips @nitrml This – I'd set my limit way higher.
@jernej__s @atarifrosch @FediTips this deduplication work is consuming server memory, which is why they released the feature with a conservative limit of 40 items and are increasing it now. Allowing users to raise it a lot could cause instances to crash.
This should indeed be configurable by the instance admins instead of hardcoded, but that's unfortunately a common thing in the Mastodon code (max post length, pool option count... changing them requires modifying the source code).
-
Mastodon has a built-in system to prevent you seeing the same post boosted again and again. However, it allows boosts to reappear if 40 other posts have passed through your main timeline, and this is why you may see the same boost repeated.
As the Fediverse is now much busier, Mastodon's devs are raising this number to 80 other posts (technical details are at https://github.com/mastodon/mastodon/pull/39784). This should hopefully be in the next update.
(Thanks to @nitrml for pointing this out
) -
Mastodon has a built-in system to prevent you seeing the same post boosted again and again. However, it allows boosts to reappear if 40 other posts have passed through your main timeline, and this is why you may see the same boost repeated.
As the Fediverse is now much busier, Mastodon's devs are raising this number to 80 other posts (technical details are at https://github.com/mastodon/mastodon/pull/39784). This should hopefully be in the next update.
(Thanks to @nitrml for pointing this out
) -
Mastodon has a built-in system to prevent you seeing the same post boosted again and again. However, it allows boosts to reappear if 40 other posts have passed through your main timeline, and this is why you may see the same boost repeated.
As the Fediverse is now much busier, Mastodon's devs are raising this number to 80 other posts (technical details are at https://github.com/mastodon/mastodon/pull/39784). This should hopefully be in the next update.
(Thanks to @nitrml for pointing this out
) -
Not really, it's just an option at Preferences > Other > Group Boosts which you can switch off or on. You still see the same boosts either way, it just determines how often you see them
Technically anything running on a computer is an algorithm, but most people don't use that meaning?
