• 0 Posts
  • 10 Comments
Joined 1 year ago
cake
Cake day: August 1st, 2023

help-circle





  • It’s not about competing, it’s about providing an alternative. GNU/Linux isn’t really competing with windows as a desktop OS for the masses, but people who want more freedom and privacy get the alternative. Fairphone isn’t competing with Samsung or Apple either.

    I feel like if we follow your line of thought, then we should never try to do things better because the existing is too big.



  • I already have another account I only use on beehaw, so I wouldn’t mind a compkete defederation or software change. Safer/nicer spaces are really hard to maintain without moderation control, and lemmy clearly isn’t there yet and might not be there for some time. If staying federated/on lemmy means beehaw administration/moderation ends up burnt out, I feel like it’s the right move to move.

    As a personnal aside, the only thing that would prevent me from staying on beehaw is if you chose a closed-source platform (eg discord).

    Anyway, thanks for the things you do and the way you do them !



  • I haven’t tried any of the following, just my 0.02.

    Idea0: is there any way to install your instance without using the setup wizard ?

    Idea 1: installing and older version (below 6.x) and upgrading it to current version ?

    The official documentation page about registration states:

    When deploying a self managed Rocket.chat >=6.x workspace you are automatically required to register your workspace upon completing the Setup Wizard

    According to the same page, for versions below 6.x you have to manually register your instance.

    Idea 2: I noticed a few references to air-gapped installations, and I guess they can’t be connected to anything from Rocket.chat HQ. Could Iistalling your server as air-gapped and completing a bogus registration work ?

    Official documentation page about Air-gapped installs registration

    Hope any of this helps. I’m quire surprised (and not in a good way) to see this mandatory requirement from Rocket.chat. Even if kt means functionality loss (access to their push notif framework for example) you should be able to decline it.