I’d like to create a safe space without distraction and a focus on specific topics.
But as soon as a user from my instance posts or reacts to something outside of my instance, a lot of data gets transferred and everyone from my instance will see the post in the “All” timeline.
This could lead to a lot of distraction pretty fast, especially people with ADHD could lose track if they see some interesting stuff from other instances. I want to avoid this and give them a safe space to be able to focus.
The only way I figured out was to deactivate federation at all. There is only one button in the settings.
But I would like to keep the feature that people could comment from other Fediverse tools like Mastodon, Kbin, Peertube, etc., but it doesn’t work anymore, if federation is deactivated.
Is there a way to keep away all federated content from other instances, which got in touch with my users (proactively cross-posted stuff is okay), but keep the feature so people from other instances could post something?
And it would be okay if my users comment on external posts, too, but not all people on my instance have to know it or get distracted by it.
Thank you for your help :)
At this point it sounds like you don’t know how federation work, otherwise you wouldn’t have different accounts.
You really have blind faith that federation even works, when I’ve been validating data and highlighting that delivery is not reliable when it has so much overhead it crashes servers.
Sorry about my last post. After reading it again, it sounded rude.
Sorry! I am a little bit stressed right now, because I was working the last 2-3 weeks to set up a Lemmy instance, working every day on it and one issue after another appeared and now it even looks like that comments don’t even reach me, because they land in the void because of the reinstall problem.
I could cry!
Lemmy is pretty immature as code to actually run in production. It may be well over 4 years old, but the whole thing seems to have very little in the way of information that a server operator can look at to check the health and problems under the covers. It also doesn’t deal with unrecognized data very well and hides a lot of errors in a log where the messages are often not very much of a hint what is going on.
Lemmy surely is unique, as I almost never see people using it actually criticize the code for quality assurance and testing. More often than not, I see people cheering and defending it. I’ve had to look through this experience and code as it is more run like an art project or a music band than any serious focus on data integrity or performance concern.
