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

help-circle




  • gaael@lemmy.worldtoRPGMemes @ttrpg.networkPeak D&D 6e
    link
    fedilink
    arrow-up
    11
    arrow-down
    2
    ·
    edit-2
    3 months ago

    Iirc it’s more of a lexical change: until now, half-something automatically assumed the other half was human, making the human race central in the setting. To allow for more liberty, most (all?) humanoid species will become interbreedable and you can choose the traits from one ancestry or the other.









  • I’ve been using DeltaChat (available on F-Droid) for a few months now.

    What I like about it is that because it’s email based, it uses OpenPGP for encryption, making it easy to have compatibility with other email-based solutions.

    If you want to go the extra-secure route, you and your contacts can even self-host your emails - as long as you’re not going to send messages to people on Gmail or other big providers, you can avoid your messages being treated as spam.

    The multi-device support is still a bit rough around the edges, but has gotten better in the last few months since the app is under active development.




  • 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.