Gregory's Server@dansup hiding public timelines makes sense for pixelfed but not for mastodon imo. mastodon sites have more of a community niche because of being primarily text posts, whereas pixelfed is generalistic due to being more oriented to media sharing
|
5 comments
 @dansup It's not a firehose on most Mastodon sites, is the point. We're on one of the few sites that is an exception to that ;)  @trwnh @dansup That’s not even true. There are plenty of large servers around. And the federated feed is garbage even on small ones. People don’t seem to understand it’s not even “bad moderation” problem sometimes but a middle aged person coming across a perfectly allowed hypersexual shitpost, or a perfectly allowed, CW’d nude.  @Gargron I would agree that the federate timeline is not great. I rarely look at it, and when I do it's by accident. I love my local timeline though, and I've been told many times that the local feed is one of the best things about the instance. I agree. We work really hard to keep our local timeline relevant and accessible.  @Gargron @trwnh @dansup The fed timeline might be a hot mess, but it's a real honest representation of the userbase. I could argue it's not only the ethical but cultural thing to show hypersexual shitposts to middle aged people. This is about expanding peoples perceptions. "Death to the filter bubble" as in giving us a unmoderated and pure feed is a matter of principle to me. Protecting the easily scared WASP isn't a good thing. If you want to focus on discoverability or relevancy. do that! |
@trwnh One could argue that it would be more important to focus on discovery and relevancy than a firehose of randomness that may overwhelm people. The medium is irrelevant.