mstdn.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A general-purpose Mastodon server with a 500 character limit. All languages are welcome.

Administered by:

Server stats:

12K
active users

If you're wondering how to stop seeing the same boosts 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 github.com/mastodon/mastodon/i

Pitch The falloff for the "group boosts" feature is currently hard-coded to 40 but should be an option to be set by the user. Motivation The setting "group boosts" hides multiple boosts, but after ...
GitHubOption to limit boosts in timeline better by setting the falloff in "Group Boosts" · Issue #18693 · mastodon/mastodonBy 31SFX4

@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

FediTips has moved!

@orsinov

Clicking on a thumbs up isn't spam. That's how you vote for an issue.

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

@feditips@mstdn.social No, the tumbs are great!

Well i don't know
I persinally have just observed a lot of very unqualified hate and soam in mastodons github issues especially

Not saying it's your fault at all
But that's why i bring it up

It can be pretty bad to read through it as a dev and feel like
These people are all hating and suggesting 10 conflicting things, criticising every single technical decision and demanding extremely expensive solutions to niece problems and want to configure every last detail

At some point you just go through the slog and think
Damn this issue tracker is absolutely unusable
And the combined cost of all the tickets probably exceeds the means of any team <100 ppl

I guess if you find a problem, report it, if the ticket doesn't exist, else upvote the existing one!
It's just that sometimes unneccesary comments and non technical doscussions kinda grind issues to a complete halt
So resist the urge to write a small commebt essay why it really really is required
At least when all your points have been mentioned already

If your comment does not bring the issue any closer to completion
I myself am guilty of this too but
Yeah