4 ms·

Thanks for the insight, and had completely missed the blog! On dendrite: What's your impression of friction needed to migrate an existing synapse home server t

Thanks for the insight, and had completely missed the blog! On dendrite: What's your impression of friction needed to migrate an existing synapse home server to dendrite? Would bridges like the mautrix family be API compatible or would they have to add additional support for dendrite? And how far away would you say you feel it is until dendrite is stable and ready for individuals as personal production server? Not looking for dates, just a feeling for how worth it is to invest getting deeper into synapse if one intends to migrate to dendrite eventually.

Arathorn 6y ago
The best way to migrate from synapse to dendrite will probably be by decentralised accounts. We have plans (driven by p2p) to let your account exist on multiple servers at the same time. The sort of way to do this would be to have @alice:example.com sign something on @alice:elsewhere.com to prove that she’s the same person. She then participates in all the same rooms from both accounts, which are presented as a single logical identity to everyone else. So example.com could be synapse and elsewhere.com could be dendrite, and she would automagically replicate her account over between the two. If she turned off example.com, she’d have migrated over. This is scifi right now, but it’s getting closer, as P2P isn’t very usable if you can’t sync your account across multiple devices/nodes. Alternatively someone could write a script to migrate synapse’s db into dendrite’s schema (or dendrite’s kafka logs), but it’s be pretty fragile given how rapidly both synapse and dendrite evolve. tl;dr: jump in with Synapse today - the water’s great (even if others have been scalded in the past). Migration to Dendrite or Conduit or whatever in future should be transparent, one way or another.
- ndarilek 6y ago
  Will it be possible to temporarily turn off example.com, let its absence propagate across the network a bit, then turn it back on under a new server? Synapse has been good to me, but I know Rust more than Python, and Conduit's use of Sled is one less moving part for me to maintain for my single-user server. Looking forward to migrating to a lighter server I can potentially hack on, and would rather not change the underlying DNS infrastructure much.
  - Arathorn 6y ago
    No, the idea is that to migrate you would have to run both servers side by side and then kill the old one. We haven’t yet figured out how you’d point the old matrix id to refer to the new server (as I assume your concern is keeping the same mxid as before), but presumably there will be a way to do so.
- Shared404 6y ago
  Will this work to migrate from the matrix.org homeserver to a self hosted one? I want to run my own homeserver, but I've already got an account on matrix.org and would rather avoid losing my contacts + rooms if possible.
  - Arathorn 6y ago
    once it exists, yup. you can migrate today though with https://ems.element.io/tools/matrix-migration https://ems.element.io/tools/matrix-migration tho
    - Shared404 6y ago
      Oh, neat. I somehow missed that. Many thanks, both for this and for your work on Matrix.

Arathorn 6y ago

The best way to migrate from synapse to dendrite will probably be by decentralised accounts. We have plans (driven by p2p) to let your account exist on multiple servers at the same time. The sort of way to do this would be to have @alice:example.com sign something on @alice:elsewhere.com to prove that she’s the same person. She then participates in all the same rooms from both accounts, which are presented as a single logical identity to everyone else. So example.com could be synapse and elsewhere.com could be dendrite, and she would automagically replicate her account over between the two. If she turned off example.com, she’d have migrated over. This is scifi right now, but it’s getting closer, as P2P isn’t very usable if you can’t sync your account across multiple devices/nodes. Alternatively someone could write a script to migrate synapse’s db into dendrite’s schema (or dendrite’s kafka logs), but it’s be pretty fragile given how rapidly both synapse and dendrite evolve. tl;dr: jump in with Synapse today - the water’s great (even if others have been scalded in the past). Migration to Dendrite or Conduit or whatever in future should be transparent, one way or another.

ndarilek 6y ago
Will it be possible to temporarily turn off example.com, let its absence propagate across the network a bit, then turn it back on under a new server? Synapse has been good to me, but I know Rust more than Python, and Conduit's use of Sled is one less moving part for me to maintain for my single-user server. Looking forward to migrating to a lighter server I can potentially hack on, and would rather not change the underlying DNS infrastructure much.
- Arathorn 6y ago
  No, the idea is that to migrate you would have to run both servers side by side and then kill the old one. We haven’t yet figured out how you’d point the old matrix id to refer to the new server (as I assume your concern is keeping the same mxid as before), but presumably there will be a way to do so.
Shared404 6y ago
Will this work to migrate from the matrix.org homeserver to a self hosted one? I want to run my own homeserver, but I've already got an account on matrix.org and would rather avoid losing my contacts + rooms if possible.
- Arathorn 6y ago
  once it exists, yup. you can migrate today though with https://ems.element.io/tools/matrix-migration https://ems.element.io/tools/matrix-migration tho
  - Shared404 6y ago
    Oh, neat. I somehow missed that. Many thanks, both for this and for your work on Matrix.