zfec VS restic

We used reflex-frp, so our app was a webview that worked on localhost and Android. The docs say it also works on iOS but we don't have an iPhone.

The process was learning Functional Reactive Programming, then learning reflex-frp, then getting a contract with obsidian (creators of reflex) for one hour a week where we could ask questions.

( https://github.com/reflex-frp/reflex-platform )

We had a grant requirement to create a phone client for Tahoe-LAFS, a Python application with a bunch of dependencies, including ZFEC, a forward error correction library.

( https://tahoe-lafs.readthedocs.io/ )

( https://github.com/tahoe-lafs/zfec/ )

We needed bug for bug compatibility with the Python codebase, so I ran Tahoe on localhost and tested the Haskell client against the Python server. We used servant to build the API, since it builds both client and server side from the same description.

( https://hackage.haskell.org/package/servant )

I disagree with the premise of the article. Archive formats are all inadequate for long-term resilience and making them adequate would be a violation of the “do one thing and do it right” principle.

To support resilience, you don’t need an alternative to xz, you need hashes and forward error correction. Specifically, compress your file using xz for high compression ratio, optionally encrypt it, then take a SHA-256 hash to be used for detecting errors, then generate parity files using PAR[1] or zfec[2] to correct errors.

[1] https://wiki.archlinux.org/title/Parchive

[2] https://github.com/tahoe-lafs/zfec

Restic - GitHub

I religiously use Google contacts. It's the simplest way to keep people contacts up to date on Android.

I archive all important documents in specific folders by subject and date. This is backed up to back blaze with restic. https://restic.net/

I use https://ente.io for pictures. I convinced my wife to use it, and she agreed to auto share her photos so I don't nag her for copies. It had simple import from Facebook and Google.

I also keep extensive journals, which really helps to tie it all together. I can basically grep for hangouts, conversations, etc.

I also separate work journal from personal, and have essentially a journal for each project. https://jodavaho.io/tags/bullet-journal.html for how.

I religiously use Google calendar for all plans, you can easily search it for past events to get dates.

I also use monicahq for some notes about things I should remember about people but the habit never stuck.

After Borg, I switched to Restic:

https://restic.net/

AFAIK, the only difference is that Restic doesn't require Restic installed on the remote server, so you can efficiently backup to things like S3 or FTP. Other than that, both are fantastic.

I'm curious, too. I know they've had some issues in the past:

https://github.com/restic/restic/issues/3268#issuecomment-78...

On the other hand, I tested around 15,000 backups last year (multiple hourly backups, daily tests) and they all passed.

I use and recommend restic. I use it for about 60 machines on my LAN, and it's absolutely fantastic.