aboutsummaryrefslogtreecommitdiff
path: root/blog/content/notes/tech
diff options
context:
space:
mode:
authoralex <alex@pdp7.net>2026-08-30 17:59:34 +0200
committeralex <alex@pdp7.net>2026-08-30 17:59:34 +0200
commit90d622507bf577ca7b8bbe7e0381b97375c30fac (patch)
tree972a7d53ee91d3e3d4fcda135e4049a0c417e04e /blog/content/notes/tech
parentd7fb62db6e1e4c357cf108114610e815670bf425 (diff)
Add even more Internet basics
Diffstat (limited to 'blog/content/notes/tech')
-rw-r--r--blog/content/notes/tech/internet-basics.gmi8
1 files changed, 8 insertions, 0 deletions
diff --git a/blog/content/notes/tech/internet-basics.gmi b/blog/content/notes/tech/internet-basics.gmi
index 6b3816d8..651f480b 100644
--- a/blog/content/notes/tech/internet-basics.gmi
+++ b/blog/content/notes/tech/internet-basics.gmi
@@ -35,3 +35,11 @@ Keeping data with sufficient resiliency is complex, because making proper backup
Many storage providers do not give you enough control over your data if you want to move to a different provider. You should always keep a full copy of your data that you can access without the Internet. (You can achieve this by using systems that keep your data synchronized to at least a device you control, or by keeping your own backups.)
(A way to provide this would be for NAS devices to support easy interoperable mutual encrypted backups, so that you can easily back up your data to someone you know in a way that they cannot read your data unless you want them to.)
+
+## Everyone must have a good password manager or trustable federated identities
+
+For good security, online accounts should have strong, unique passwords or no password at all.
+
+Strong unique passwords are still the best option, despite passkeys and federated identities, because they are lowest-common denominator and simple.
+
+Federated identities are useful, as long as the entity providing them is of enough trust for you. The providing entity can fail, deny you access, or die at any time, taking your federated identity with you.