greenicon

At least in the past the default import-export route did not move attachments, be careful!

Windows gives you recovery keys for each encrypted drive. With those you can even access tpm-protected drives on another machine.

I'd say it's mandatory today to encrypt drives. In the age of SSDs it's not really possible anymore to delete files and to be sure they are in no way recoverable by an adversary.

Docker (Compose) has some quirks compared to Podman (Compose), e.g. when using gvisor or a lot of internal networks. Depending on what you do your milage will vary, though.

I'm using jj exactly this way, but `jj commit -i` is still somewhat backwards compared to `git commit -i`: jj displays the commit timestamp by default instead of the author timestamp like git. In addition, in jj the author timestamp of a commit is set to the time you started and not ended a commit/change. This results in unexpected timestamps when working with git-using people or tools. Also, it's rather weird if you use a previously empty commit for your work which was created months earlier by a previous `jj commit`, resulting in a timestamp neither correlating to when you started nor ended your work.

I guess the idea of jj's authors is that jj's commits are far more squishy and can always be changed, so a fixed finished timestamp makes less sense. I still prefer git's behaviour, marking work as finished and then keep the author (but not commit) timestamps on amends.

I use this jj alias to get git's timestamp behaviour:

  [aliases]
  c = ["util", "exec", "--", "bash", "-c", """
  set -euo pipefail
  change_id=$(jj log -r @ --no-graph -T 'change_id')
  desc=$(jj log -r $change_id --no-graph -T 'description')
  commit_author=$(jj log -r $change_id --no-graph -T 'author.email()')
  configured_author=$(jj config get user.email)
  
  jj commit -i "$@"
  
  if [ -z "$desc" ] && [ z"$commit_author" = z"$configured_author" ]; then
      echo "Adjusting author date"
      jj metaedit --update-author-timestamp --quiet $change_id
  fi
  """]
  
  [templates]
  # display author timestamp instead of commit timestamp in log
  'commit_timestamp(commit)' = 'commit.author().timestamp()'

In German you use en-dashes with spaces, whereas in English it’s em-dashes without spaces. Some people dislike em-dashes in English though and use en-dashes with spaces as well.

git absorb works surprisingly well. I was quite skeptical in the beginning, but it really turned into something I used daily (until I switched to jj, where I haven't found a replacement yet). If you use stepwise commits I can really recommend it.

small edit: It seems that jj supports `jj absorb` now as well. Wonderful!

Yes, depending on your highlighting scheme. Not every highlighting scheme shows this by default, unfortunately.

To me, this seems initially like some very minor thing, but I find this very helpful working with non-trivial code. For larger methods you can directly discern whether a not-as-immutable-declared variable behaves immutable nonetheless.

Passkeys cannot be phished.

Other than that they shouldn't have a big advantage for a more professional user with unique, long, and random passwords. For the common user it should be a great upgrade, giving all these advantages with better UX.

I'd say that the basic sailing knots should fit your bill pretty well. I can't recommend an online source, but you should find plenty resources on Youtube. It shouldn't take longer than an evening or two to learn them.

Wireguard does not re-resolve dns when your dyndns ip changes. This ip change is common in parts of Europe where it usually changes daily. To circumvent this you need a jumphost or similar. This again brings additional issues when you don’t want to go through the jumphost when at home (I use nftables-magic on the router, but it’s not very nice).

It seems the EU laws for this have changed last year [1], to allow Erdbeermarmelade again.

1: I was only able to find something in German: https://www.wiwo.de/politik/ausland/realsatire-aus-bruessel-...

That’s exactly what prefix delegation is for. Your ISP ought to give an /56 or more, so you can then have multiple /64.

I get an /56 by my ISP and have 6 or so different /64 in my residence.

Modern CPUs are mostly limited by their energy budget/heat and smaller cores are more efficient. Also, if you have a workload scaling to, say, 8 cores chances are good that it also scales to 20+, allowing the usage of many small cores. Hence, having a few fast and then several smaller, more efficient cores should be also useful for workstations and servers.

For a networked Time Machine restore you can reinstall MacOS without restoring first and then use the migration utility to restore from a remote Time Machine. That seems to use a different smb binary which works. Still, I find it infuriating that restoring, one of the most important things you do on a machine, is broken and was not caught by QA.

These are all valid issues.

Germany addresses them by doing a FPTP pass and then filling the remainder of the parliament such that the overall parliament has PR according to a second, independent vote given at the same time. This creates some other issues again, but works surprisingly well for the most part.

Yes, the battery drain on iOS is also the thing stopping me from having it on my iPhone. Wireguard is way better in that regard, but has other issues (e.g. no split dns, no dns re-resolve for dyndns or for network changes).

Other than that tailscale is really great. It just works.

You can easily use this for digital documents as well. The only difference in my setup is a tag showing whether the document id maps to a physical document in a binder or not.

Just a side note to this and the other replies: You can also keep the original documents and add scans to paperless for indexing, etc. Since I switched to paperless I keep my originals in binders just ordered by the paperless id, so I can retrieve the original when required.

I can fully recommend Tink, especially when libsodium isn’t available. Although its documentation isn’t very good, it‘s build to be hard to misuse. You still need some cryptographic knowledge though, as it isn’t that opinionated as libsodium.

This is not necessarily the fault of the browser alone. I‘m also unique on a Safari on an up-to-date iOS, which in itself is not very unique.

The QR code is usually just for easier use, you can also unlock them in the apps via selecting the vehicles on the map.

Sure. As far as I‘m aware the Gedankenstrich is usually set as en-dash with spaces in German, though [1].

1: https://de.wikipedia.org/wiki/Halbgeviertstrich#Gedankenstri...

Yes, and the Gedankenstrich is usually set as en-dash with spaces around, only rarely as em-dash. See https://de.wikipedia.org/wiki/Halbgeviertstrich#Gedankenstri...

The alternative is usually en-dash with spaces.

In German that’s the way it’s done: en-dash with spaces, em-dashes (basically) don’t exist.

Yes, this is a shame. Building a low-idle-power system with desktop components is far harder than it seems, unfortunately.

There shouldn’t be much of a difference, although the rust crate is more similar to the OpenSSL part. Just make sure to properly seed your CSPRNG, e.g. via using Rust’s ThreadRng[1]. In basically all cases there is no reason to use anything from the rand crate except ThreadRng.

1: https://rust-random.github.io/rand/rand/rngs/struct.ThreadRn...

In Germany historically yes, but today most people mean the person him/herself.

You get some form of cross-platform sync. Apple, Google, and so on each have syncing, but in their ecosystem only. You can break out with the QR codes, but this might not be the preferred solution to some.

Just check your data after re-importing the passwords. LastPass sometimes has issues with the export (see elsewhere in this thread) and does not export attachments at all. You have to move attachments manually.