“People are arseholes. They’re just always gonna be that way.”

  • 3 Posts
  • 21 Comments
Joined 15 days ago
cake
Cake day: July 23rd, 2026

help-circle
  • The article does not mention mountains. Mountains are often more suited to trains than planes, cf. Switzerland.

    The article does quote Anna Hughes of Flight Free UK, who echoes my sentiments: “The reality of decarbonising travel will inevitably be travelling a lot less, investing heavily in rail, and only then electrifying the flights that remain.”

    France’s short-haul flight ban is excellent and more countries should adopt it.

    As for “counterpoint”, no-one here disagrees with decarbonising island routes rail can’t serve. Still, I’d favour sail or electric fast ferries over aircraft where possible.

















  • Yes. Here are some common self-hosting scenarios:

    • Home server containing family files: scans, photos, device backups, …
    • Office server containing business files: sensitive documents, device backups, …
    • Web or email server containing websites, Fediverse instances, emails, etc

    In all those cases, full disk encryption (FDE) is a sensible precaution to protect the data in case the server is physically stolen.

    Linux is probably the most common OS kernel for self-hosting. On Linux, LUKS (Linux Unified Key Setup) is probably the best FDE system. It’s mature and reliable. But anyone self-hosting a Linux server with LUKS FDE is faced with the question of where to store the keys.

    Hardware security tokens (HSTs) are widely considered a safer place for keys than SSDs, HDDs, or USB storage. They follow the smartcard principle: a private key can be written to an HST but not read from it (security vulnerabilities excepted). Instead, they implement cryptographic algorithms to prove possession of the private key. So, anyone self-hosting a Linux server with LUKS FDE should strongly consider storing their private key(s) on an HST.

    However, there is more than one way to do that. Hence the question in my OP.