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 :)

  • RoundSparrow@lemmy.ml
    5·
    11 months ago

    How exactly do I deactivate the “All Feed” to not pollute my server and avoid distractions to the users, but let them comment on external posts

    How would they ever find the external posts to comment on in the first place?

    • maxmoon@lemmy.mlOP
      15·
      11 months ago

      Like normal people! :D

      Go to another instance, if you find something interesting, copy the link and paste it to the search field of your instance. After that federation starts and you can post.

      There must be at least one person doing this, because otherwise ALL wouldn’t contain anything from other instances.

      But it’s a little bit sad, that you’ve never done this and only look at all. It means you watch only stuff other people on your instance have seen but you don’t get further.

      • RoundSparrow@lemmy.ml
        4·
        11 months ago

        Like normal people! :D Go to another instance, if you find something interesting

        So “normal people” would go read another instance just to bring a single comment or post over. They may as just well join the other instance. Which is what I see actually happening… Many of these lemmy accounts are the same person duplicated to route around crashes.

        But it’s a little bit sad, that you’ve never done this and only look at all.

        If you had any clue what I have been personally doing with lemmy for the past 90 days, you would laugh at yourself. I’ve been logging in to several different Lemmy servers every single day for months and posting about my observations… such as when a big instance put new user interfaces online, upgrade their backend, crash on their home page, etc.

        • kense@lmmy.dkEnglish
          2·
          11 months ago

          If you had any clue what I have been personally doing with lemmy for the past 90 days, you would laugh at yourself.

          Hey, we are someone who notices, and do not laugh at all, but appreciate everything you do!

        • maxmoon@lemmy.mlOP
          1·
          10 months ago

          At this point it sounds like you don’t know how federation work, otherwise you wouldn’t have different accounts.

          • RoundSparrow@lemmy.ml
            1·
            10 months ago

            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.

            • maxmoon@lemmy.mlOPEnglish
              1·
              10 months ago

              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!

              • RoundSparrow@lemmy.ml
                2·
                10 months ago

                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.

                • maxmoon@lemmy.mlOPEnglish
                  1·
                  10 months ago

                  Do you know a good programmed forum software? Because one of the reasons I chose Lemmy was, that it was content based, like a classical forum and that’s what I need.

                  But the second thing what I need is, to be able to access the posts/comments via an API, like REST to process them.

                  I am at a point where I will throw away the work of the last 3 weeks to get some useful software, because it looks like Lemmy will just create unnecessary work, which could have been avoided, if it would have been clean programmed.

                  I already checked phpBB, it doesn’t have a REST API :/

                  • RoundSparrow@lemmy.ml
                    2·
                    10 months ago

                    I haven’t looked around at alternatives.

                    Lemmy has a lot of front-end app development going on and I think that’s one of the big strengths. The API can be bloated with a lot of duplicate data in JSON responses but it is usable.