GitHub - balzack/databag: A tiny selfhosted federated messenger for the decentralized web.
github.com
A tiny selfhosted federated messenger for the decentralized web. - GitHub - balzack/databag: A tiny selfhosted federated messenger for the decentralized web.

Just a hint for people searching a tiny selfhosted messenger with encryption and apps for iOS and android.

  • sbv@sh.itjust.worksEnglish
    221·
    1 year ago

    End-to-End encryption (the hosting admin cannot view sealed topics, default unsealed)

    oh no

    • u_tamtam@programming.devEnglish
      13·
      1 year ago

      It says it’s federated. When you are your own provider, e2ee doesn’t matter nearly as much (you probably have a bunch of personal files, backups, services running on the same box anyway).

      Edit: I would gladly take constructive comments with the downvotes. For a moment I thought we were on “selfhosted”, where “you are your own provider” should resonate in with most

      • IAm_A_Complete_Idiot@sh.itjust.worksEnglish
        4·
        1 year ago

        The point of federation means your content doesn’t only stay on your server. The person you’re talking too can be on a different one and their admin can see them too. Also, I wouldn’t want to be able to access content from any user - it’s a “no trust needed” thing.

    • Samsy@lemmy.mlOPEnglish
      91·
      1 year ago

      Dumbest answer: I didn’t find a one click solution on casaOS.

        • Samsy@lemmy.mlOPEnglish
          1·
          1 year ago

          casaOS is a docker-compose simplified one click solution, like unraid or heimdall.

          Sure I tried to add xmpp to my apps, but finding the right one on xmpp is like the first experience with Linux … too many alternatives. I tried openfire because it sounds good with a compose file and proxy all to my caddy server. But I am stuck actually (the last 10 min), and I am unable to decide if ejabberd is better.

          • u_tamtam@programming.devEnglish
            1·
            1 year ago

            If your system is based on docker, couldn’t you just use the official docker image I linked? Besides, I wouldn’t recommend openfire, not because it’s not a capable server (it’s been to long since I tried it to have a meaningful opinion), but because it has less widespread usage than ejabberd/prosody, and by extent, probably less resources to help you configure it to your needs.

            I know it’s not the topic of this thread, but you are not making a convincing case (to me!) for a “docker-compose simplified one click solution” that pulls you away from the most popular and well maintained alternatives :)
            And you will also likely encounter things down the road pertaining to firewall configuration, domain name resolution and port multiplexing that containerization will turn into a configuration and troubleshooting nightmare, so… enjoy! (or not)