RexSystem1 voteoriginally by @Shanesan on GitHub1 reply
Though I love this idea in concept, in practice I can't imagine a lay person to be owning a domain, let alone running a docker container. SSL? Can't see it.
However what might work is supporting the dozen different Drive systems, like Proton, or Dropbox, or whatever to start, and then expanding beyond that to personal storage containers - or even better, locally hosted Drive systems users might already have, like Synology or Nextcloud, would be really cool.
Another issue with local, individually hosted solutions is that if their computer is off (if they're hosting it there - lay people, right?) a lot of the context of the conversation has now 404'd.
RexSystem1 voteoriginally by @lexifuzzpup on GitHub OP
I agree that it's a major drawback. I was imagining sort of "the techy person of the friend group" setting up a server for a few people, but it might be easier to integrate with third-party services like that.
Maybe, in the beginning, third-party services could be supported, and once development settles a bit, the self-hosted option for individuals and servers could be implemented. I see the idea of self-hosting storage and privacy to be on-brand for Fluxer, since the author has mentioned federation and E2EE chats in their roadmap.
Thread
Comment by @Shanesan
Comment by @lexifuzzpup