• 0 Posts
  • 42 Comments
Joined 5 years ago
cake
Cake day: June 28th, 2020

help-circle




  • It’s nice that this exists, but even for this I’d prefer to use an open source tool.

    And it of course helps with migration only if the old HS is still online…

    I think most practically this migration function would be built inside some Matrix client (one that would support more than one server to start with), but I suppose a standalone tool would be a decent solution as well.


  • Wish the homeserver portability would be worked on more. The ability to change homeserver would really allow people to more easily move on from matrix.org.

    Myself included ;).

    Optimally it would even allow the switch “after the fact”, so after your original homeserver is down, assuming your client has a local copy of the server-side secret storage. It would need to be based on some cryptographic identity then, I suppose.




  • I’m also in a one-party consent country, and I’ve found it sometimes useful to get back to some calls just to find out some details, such as agreed date/time or some detail of a discussion I had with my mother. I would enjoy an automatic text translation to be stored alongside them.

    I miss the feature now that I have Pixel 8.

    I used syncthing to sync them to PC. Size-wise I have so few phone calls (work meetings excluded, which they are as they are over Slack/Teams) that all of them will fit most any modern phone easily.











  • I just noticed https://lemmy.ml/u/giloronfoo@beehaw.org had proposed the same, but here’s the same but with more words ;).

    I would propose you try to split the data you have manually into logically separate parts, so that you could logically fit 0.8 TB on one drive, 0.4 TB on another, and maybe sets of 0.2TB+0.2TB on a third one. Then you’d have a script that uses traditional backup approaches with modern backup apps to back up the particular data set for the disk you have attached to the system. This approach will allow you to access painlessly modern “infinite increments” backups where you persist older versions of data without doing full and incremental backups separately. You should then write a script to ensure no important data is forgotten to be backed up and that there are no overlapping backups (except for data you want to back up twice?).

    For example, you could have a physical drive with sticker “photos and music” on it to back up your ~/Photos and ~/Music.

    At some point some of those splits might become too large to fit into its allocated storage, which would be additional manual maintenance. Apply foresight to avoid these situations :).

    If that kind of separation is not possible, then I guess tar+multi volume splitting is one option, as suggested elsewhere.