crux

For config files, I use tarsnap. Each server has its own private key, and a /etc/tarsnap.list file which list the files/directories to backup on it. Then a cronjob runs every week to run tarsnap on them. It's very simple to backup and restore, as your backups are simply tar archives. The only caveat is that you cannot "browse" them without restoring them somewhere, but for config files it's pretty quick and cheap.

For actual data, I use a combination of rclone and dedup (because I was involved in the project at some point, but it's similar to Borg). I sync it to backblaze because that's the cheapest storage I could find. I use dedup to encrypt the backup before sending it to backblaze though. Restoration is very similar to tarsnap:

    
dup-unpack -k keyfile snapshot-yyyymmdd | tar -C / -x [files..] .

  

Most importantly, I keep a note on how to backup/restore: Backup 101

Ok that was my initial fear, and you just confirmed it. Thanks a lot !

I suppose you dual boot them because postmarketOS isn't usable as a daily driver right ?

I liked Sailfish UI a lot, and the fact it was a "standard" Linux with coreutils, git, rsync, etc... by default was the main reason I switched to it. But yeah, I've been quite deceived by their recent "updates". I now have an Xperia 10 III, but there doesn't seem to be much custom ROMs that support it unfortunately (which is also why sailfish support isn't great anyway).

Thanks for sharing your experience ;)

Then you should definitely check it out: vis.

Its original goal was to be a vim clone with 90% of the features in 10% of the code. Then it grew into being the bastard son of Vim and Sam editors (plan9's structural regex based editor).

The result is vis, an editor with vim like navigation and text manipulation mechanics, but with access to Sam's powerful structural regex commands which works selection wise, rather than likewise like vim. Check this paper to learn about it: struct-regex.pdf.

My experience with the XA2+ was pretty great, and the phone camera wasn't that bad for my use case. I truly enjoyed the experience and wanted the same with the 10 III, but it seems worse than with the XA2

I made a cool exercise some time ago: checking my top 10 used commands, to see how I can "optimize" them, and maybe create a few aliases to save a few keystrokes. Turns out I don't need that much aliases in the end:

    
alias v='vis' # my text editor
alias sv='doas vis'
alias ll='ls -l'

  

And that's pretty much it ^^ I do have a lot of scripts though, some of them being one-liners, but it makes them shell independent, which I like :)

For reference, here is my analysis of my top 10 most used commands.

edit: I do have a bunch of git aliases though for common subcommands I use. I prefer using them as git <alias> over using she'll specific aliases so I can always type "git" and not mentally think wether I need a git command or a shell alias.

^D my dude.

What do you do with all the process you save with that trick ?

I used to put them all under version control until 2017. I have well over 200 scripts now, so I stopped bothering with version control ^^

But there are a few things I use every now and then that I find "fun":

temporary workspace

tempsh starts a new shell in a temporary directory, and destroy it when you exit the shell. I use it to test code snippets, open tar bombs, whatever task that don't need to save my work.

emojis !

I have an emoji script, which prompts me for all emojis of the spec using dmenu, so I can search them by name, and put them in my clipboard. It's a stupid script but I use it a lot (much more than those :shortcut: style selector you have in messaging software!).

love

I have a love script, which simply outputs "♥️" to the terminal. Most important script of my workflow!

That's from my own experience. I had a self-hosted matrix server running with Dendrite, and the mautrix-whatsapp bridge running. The bridge was running in puppeted mode, so upon synchronizing contacts, the bridge created "fake" users on the matrix server, one for each of my whatsapp contacts. The matrix username of these contacts is (by default) whatsapp_<phone_number>:domain.tld. And these users are visible (at least) by other users on the same server. It was my own instance and I was the sole user so I didn't really care. But when a friend of mine wanted to try matrix, I created an account for him on the server, and when he joined, he could see all the fake whatsapp/telegram/discord users created by the bridge on the server. And as the default username includes the phone number, he basically had access to my whole phone contact list in real time.

Bridges were not that easy to manage in my case (regarding process management, and ease of config deployment/reproductibility). It was on OpenBSD though, so your mileage may vary. And still, it leaks all of your contact informations to the other users of the server (like their phone number eventually), so definitely not suited for public instances.

From my experience (with Dendrite, not synapse, so keep that in mind), bridges create "fake" users to replicate your contacts on these platform as matrix users, and they are visible on the whole instance by all their users (but you might not be able to talk to them). Also, in puppeted mode (which is what you want to "replace" your app with matrix), only a single user can use the bridge at a time, so the other users cannot use it.