aboutsummaryrefslogtreecommitdiff
path: root/blog/content/notes
diff options
context:
space:
mode:
Diffstat (limited to 'blog/content/notes')
-rw-r--r--blog/content/notes/interesting-articles.gmi3
-rw-r--r--blog/content/notes/tech/internet-basics.gmi26
2 files changed, 29 insertions, 0 deletions
diff --git a/blog/content/notes/interesting-articles.gmi b/blog/content/notes/interesting-articles.gmi
index d7d1cfc2..7966f6dd 100644
--- a/blog/content/notes/interesting-articles.gmi
+++ b/blog/content/notes/interesting-articles.gmi
@@ -10,6 +10,9 @@ Simplicity is sacrifice. See also:
=> https://www.geoffreylitt.com/2025/03/03/the-nightmare-bicycle.html Avoid the nightmare bicycle
Good designs expose systematic structure; they lean on their users’ ability to understand this structure and apply it to new situations.
+=> https://earthly.dev/blog/thought-leaders/ Don't Feed the Thought Leaders
+Contingent advice (that depends on the situation) is in general better than generic advice. In my experience, one of the most difficult parts is knowning when you have to deviate from common practices.
+
## Programming
=> https://mikehadlow.blogspot.com/2012/05/configuration-complexity-clock.html The Configuration Complexity Clock
diff --git a/blog/content/notes/tech/internet-basics.gmi b/blog/content/notes/tech/internet-basics.gmi
index f83082c7..651f480b 100644
--- a/blog/content/notes/tech/internet-basics.gmi
+++ b/blog/content/notes/tech/internet-basics.gmi
@@ -17,3 +17,29 @@ The ISP must control use of the email addresses with the domain to prevent spam.
Delivery targets decouple the email domain from the email service that stores the email. Users can choose to store email in whatever service they prefer, including an ISP service or other services.
Email services must support transferring stored email.
+
+## Everyone must have a feed reader. All website updates should work with feed readers
+
+Getting updates from websites is tedious.
+
+Many use social networks to centralize updates. However, social networks are mostly controlled by entities not aligned with you. Also, social networks are rarely used to centralize updates, so they tend to be suboptimal for this purpose.
+
+RSS, ATOM and others are standards for sites to provide feeds of updates. There are plenty of feed readers.
+
+When you use multiple devices to follow updates, having device synchronization of subscribed feeds and read items is nearly a necessity.
+
+## Everyone must have sufficient data storage with sufficient resilience and control
+
+Keeping data with sufficient resiliency is complex, because making proper backups is difficult and tedious.
+
+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.