Is it possible to make a lemmy instance private were no communities, posts, user profiles and the homepage is not available unless your logged in?

  • Saik0@lemmy.saik0.comEnglish
    101·
    1 year ago

    Used to be possible by ticking both federation and private on the admin page. But now they made it where you can’t toggle both simultaneously.

    I’d like to see that return as a feature. I’d like to have my local instance have private communities for my users but still provide my users the ability to go out to the rest of the fediverse. My instance is friends of friends sort of stuff. So I have no reason to host communities out to the whole of the fediverse.

    • comcreator@lemmy.worldOPEnglish
      01·
      1 year ago

      By leaving the federation box unchecked and having the private box checked off, will the instance not be visible to the public unless your logged in?

      • Saik0@lemmy.saik0.comEnglish
        21·
        1 year ago

        Federation unchecked and private unchecked. An instance that is publicly accessible, but doesn’t talk to other instances
        Federation checked and private unchecked. An instance that is publicly accessible, and does federate with others. (Most of the big instances are this)
        Federation unchecked and private checked. An instance that is private and requires logins to access the communities and other parts, but doesn’t federate.

        Federation checked and private checked… Used to work. communities hosted on the server would require a local account and would still federate out. This was outright blocked from 0.17.4 I believer…

        The last case is perfect for me. I want to setup communities for my friends around particular topics on my instance, and still use my instance across the rest of the fediverse.

        • BlueÆtherAEnglish
          1·
          1 year ago

          I wonder what the consequences would be if you updated the database?

          • Saik0@lemmy.saik0.comEnglish
            1·
            1 year ago

            On boot, with both options selected, the server locks up.

            Updating it after boot? I don’t know.

            • BlueÆtherAEnglish
              1·
              1 year ago

              I guess it was worth the test to find out https://github.com/LemmyNet/lemmy/pull/3237

              https://github.com/LemmyNet/lemmy/issues/3073

              On start-up Lemmy checks if both the private_instance and federation_enabled flags are set. If they are, it raises and error which stops start-up meaning administrators are unable to edit the settings which cause the error.

              As a means of prevention, I’ve added some validation when editing or creating a site to ensure that both options are never selected at the same time.

              I thought about adjusting start-up behaviour to disregard one of the flags (like ignore federation if the private flag is set) but I thought it would be easier to just prevent the invalid state from being saved.

              This could probably coincide with a change to the UI as well but I can do that after.

        • comcreator@lemmy.worldOPEnglish
          01·
          1 year ago

          Before when you can check off federation and private instance, you could not view the instance unless you were logged in but could you view the instance from another instance being logged into another instance or no being logged into another instance?

          Or does it only federate in a way were users inside the private instance can access the fediverse but the fediverse cannot access the private instance?

          • Saik0@lemmy.saik0.comEnglish
            01·
            1 year ago

            So private checked means that you have to be signed into the local instance to see the content.

            Federation means that you can interact on the fediverse.

            With both checked, it meant the communities INSIDE the instance would not transmit out… but the rest would work as normal.

            • comcreator@lemmy.worldOPEnglish
              01·
              1 year ago

              it meant the communities INSIDE the instance would not transmit out… but the rest would work as normal.

              Lets say you have a private federated instance named salk.world. salk.world users can access, post and comment on other instances like lemmy.world but other instances and users cannot view content on salk.world?