Edit history

In the current deployment model, federation (in the future) will require deploying an entire Fluxer instance. This includes community-centric components and features that require deliberate configuration through multiple variables to disable, to achieve the "identity-only" goal.

A slimmed down "identity-only" deployment option for an instance that would only contain the infrastructure components and software components necessary to sustain connecting to/federating with other instances. Those other instances would offer "the full experience". My local identity-only instance would just allow me to operate in the federation network as my user e.g. astromahdi@fluxer.host. Some user-centric design notes: My identity-only instance would not support creating communities of any kind. I do not have the time to moderate an entire instance. I just want to federate and access the fluxerverse using my own identity. I would want to create multiple users on my identity-only instance (e.g. friend@fluxer.host). Ideally, I wouldn't need to deploy a voice server with an identity-only instance. The entire identity-only instance should be servable over e.g. cloudflare tunnels (i.e. no UDP) to aid in ease of deployment at home for most users.