Edit history

Earlier versions of Fluxer Peer to Peer and other suggestions for High Availability Instances, newest first.

Current version | Edited by Rex
Changes
- Using the federation system to somehow to keep up other servers' users in your own instance, as currently federation would still mean if your main server goes down, all users from that specific server go down with it.Removed: ### NotesRemoved: Removed: _No response_Removed: Removed: ### ChecksRemoved: Removed: - ☑ I searched existing discussions.Removed:
Show

Fluxer Peer to Peer and other suggestions for High Availability Instances

Problem

The clients being directly connected to the homeserver means that if your homeserver goes down, access to comms is unavailable until the problem is fixed.

Proposal

Some solutions to mitigate such issues would be:
  • Having a peer to peer solution for the platform
  • Using the federation system to somehow to keep up other servers' users in your own instance, as currently federation would still mean if your main server goes down, all users from that specific server go down with it.
Original by Rex
Show

Fluxer Peer to Peer and other suggestions for High Availability Instances

Problem

The clients being directly connected to the homeserver means that if your homeserver goes down, access to comms is unavailable until the problem is fixed.

Proposal

Some solutions to mitigate such issues would be:
  • Having a peer to peer solution for the platform
  • Using the federation system to somehow to keep up other servers' users in your own instance, as currently federation would still mean if your main server goes down, all users from that specific server go down with it.

Notes

No response

Checks

  • ☑ I searched existing discussions.