When times are good, it’s everyone for themselves, and individuals can entertain various identities and alliances. But when times are tough, community is protective, and individuals have to pick a side.
They were not so aligned until the 20th-century when Jews from all communities mixed again. I am not disputing that Jewish practices today and for the last two millennia are connected to practices in Judea at the turn of the first millennium and to texts that had been written even earlier. What I'm saying is that strict and regulated adherence by large parts of the population came relatively late. That, as far as I can tell from the research, is not at all controversial.
I recently switched from Fedora to Linux Mint Debian Edition (I work mostly with Debian servers so I am more comfortable with apt than dnf), and the switch has been smooth for me.
I keep my home directory organized and backed up on my NAS, so for me reinstalling is straightforward. Also I use Flatpaks whenever possible, so reinstall them is just looking at ~/.var/app and reinstalling what is there.
Other files to back up might be custom /etc confs, and maybe lists of packages you need (dpkg -l or rpm -qa are your friends).
I also use Linux brew for some more up to date software (e.g. golang) and just brew list is your command to get what you have installed.
In general, keep a backup of your home folder (I suggest skipping backing up ~/.cache to save some time and space) and you are mostly good to go.
- `brew list` doesn't include apps you install from 3rd party taps, or casks, so `brew list --full-name` + `brew list --full-name --cask` is better
- Many apps store their config and user data outside of the home dir. I always find it dishonest when people say backing up home is enough on Linux. You did say "mostly ready to go", but that's exactly the tricky and important part that most people pretend doesn't exist
E.g. Docker volumes are in /var/lib/docker
So /etc/... and /var/lib are generally worth checking as well, but that probably still doesn't cover everything, as not all apps behave as maybe XDG specifies.
Ideally you shouldn't have to backup /var/lib/docker, as your docker configs should live in your docker-compose.yaml or whatever you use to start your docker containers.
Also I have included backing up /etc confs in my original post.
I agree on the brew list being incomplete, totally forgot about casks. Not even sure if they work correctly under Linux to be honest. I literally just use brew for golang and awscli :P
Re Docker I said volumes, not config. Some volumes you might have mapped to the host and maybe picked a home subdirectory, but others maybe not. For example the Ollama 3rd party UI `open-web-ui` suggests to run it like this in their documentation:
Then "open-webui" will be in `/var/lib/docker/volumes/open-webui/`.
Sure you can change it, but what I mean is that a lot of software by itself, or by you following documentation, puts data that you usually want to back up outside of your home.
What is meant is that instead of ~/.app/config, you are getting now ~/.config/app/config.
It’s much cleaner and it comes with a more logical and useful split of config and cache stuff, e.g. you can just skip .cache when rsync-ing to a remote storage instead of having a long list of per-app escapes…
Not really. Now when I want to uninstall something, I have to look in multiple places for its artifacts, rather than just nuking .<appname>. And there is no universal pattern of use. It's even worse than /usr vs /opt.
This is an issue that really can't be fixed imo.
If use the scheme "app/storage" then migration/deletion of singular apps is easy, but if you want to touch just a part of every program (e.g. delete the cache) then its filled with the same tedium you were initially complaining about with regards to uninstalling.
On the other hand, the scheme "storage/app" allows you to "nuke" the cache for every installed program without touching the config at all (while lessening the ease of complete removal).
As I don't usually remove programs (or install new ones, for that matter) the scheme that works best for me and many others is "storage/app". In an ideal world a hybrid scheme might be possible, but as it stands now it is not an option and one way has to be chosen over the other.
Similar experience for me. Facebook groups, WhatsApp groups and telegram groups. Some years ago somebody tried to move people to signal groups, but it went nowhere… and this is Germany, where there is no sympathy for Meta and in general people are quite privacy aware.
The only “problem” bsky solves is choosing a server. But if ATProto becomes widely used, the problem will appear as in Mastodon today. The only way to avoid it is for bsky to never become really decentralised. So yet another VC-backed social media company.
I think this is why this is in truth, an aesthetic choice masquerading as a conversation about technical implementation.
I think there's no two ways around it, @stephenking.bsky.social looks better than @stephenking@mastodon.social.
Blue Sky does the names better and opts people into a default server at the moment, and I would say their desktop and mobile experience is a bit better, and that feels like they've solved something specific and technical even though, as you pointed out, the issue with domains is the same in each case.
Mac OS X Server (Rhapsody) was using the classic Mac OS look over a NextStep base. You can find x86 versions online which work in VM, for nostalgia and research.
To be a bit more specific, Mac OS X Rhapsody DR2 (1998) was the last x86 Mac OS build to ship until the x86 Developer Transition Kit shipped with Mac OS X Tiger 10.4.1 in 2005, and Rhapsody DR1 was the first, and only other, pre-Tiger x86 Mac OS release, though unreleased x86 ports of earlier, pre-NEXTSTEP Mac OS releases were demonstrated internally[1].
Additionally, NeXT shipped several x86 releases of NEXTSTEP and its successor OpenStep (NEXTSTEP 3.1–3.3, 1993–1995; OpenStep 4.0–4.2, 1996–1997) prior to the acquisition, all of which also run under virtualization with some effort — though I'd personally recommend the Previous emulator[2] for running older NEXTSTEP builds, as it runs reasonably fast on modern hardware and quite a bit of historically interesting NEXTSTEP software exists that was never released for versions of NEXTSTEP running on non-NeXT hardware (Mathematica 1.0, Lotus Improv, WordPerfect, and the original CERN WorldWideWeb browser come to mind, though source ports of the latter exist).
Archeology tells us that common people of ancient Judea/Israel were more flexible in their practice than post-Roman orthodoxy implies.
From Asherah statues to an entire Temple (Elephantine island on the Nile) working in parallel to the Jerusalem Temple.
The matter of strict adherence as a National identity/religious practice became important following the Diaspora following the Rome-Jewish wars.