Bèr Kessels 🐝 🚐 🏄 🌱's latest activity

@dansup I understand your position.

But feel rather uncomfortable when such choices are made "on gut feelings" and won't be reconsidered once there is actual data to make these decisions on.

(Do note I'm not for or against your choice. I'm merely hoping you'd make such choices on their merits and not "feelings". And do note that I realize we currently lack these "merits". So I understand and respect your choice and stance!)

@dansup will you be reviewing your consideration when you have data?

E.g. the amount of your users that manually unblock. Or amount of interactions with threads? Or when you have a statistical significant amount of "reports" or "flags" over various domains, incl Threads?

@dansup there's different vectors in performance.

Mastodon performs well for large (and huge) communities. But it performs terrible for single person setups. E.g. #gotosocial is the reverse. It performs very well for a tiny community, but far worse for a (ten) thousand user instance.

I'm still convinced the fediverse should push for many small instances.

@dansup gotosocial performs far, far beyond mastodon. It mighn't *scale* as well, but it *performs* much better.

This difference is very important. Mastodon might serve thousands of users well, it is the worst of all options for a selfhosted -one-man- server.

And IMO fediverse software should optimize for small to tiny servers. Mastodon optimizes for big to huge servers.

@dansup this only fights spam accounts on large centralized instances.

And we don't want large, centralized instances.

We want to encourage many, small, federated instances. So IMO any effort to improve spam fighting, should go to tools and tech for fighting spam in a world with many, small, federated instances.