syndicate

content/notes/choosing-an-encrypted-dns-proto.md

@@ -0,0 +1,18 @@
+---
+title: "Choosing an encrypted DNS protocol"
+date: 2023-11-18T19:30:46-07:00
+syndicatedCopies:
+    - title: 'The Fediverse'
+      url: 'https://pleroma.envs.net/notice/Abx4oDbeirFSCS0c2i'
+---
+The three most popular DNS protocols with transit encryption are DNS-over-HTTPS (<abbr>DoH</abbr>), DNS-over-TLS (<abbr>DoT</abbr>), and DNS-over-QUIC (<abbr>DoQ</abbr>). This should help you choose what to use:
+
+1. Do you actually need to override OS DNS support? If not, or if you're unsure, go to 6.
+2. Are you ready to implement DNS protocols correctly, or add a dependency that does so? If you're not, go to 5.
+3. Does the network filter DNS traffic? If it does, go to 5.
+4. Do you already have QUIC support? If not, **use DoT.** If you do, **use DoQ.**
+5. Do you have an HTTPS stack? If you do, **use DoH**.
+6. Give up and **delegate to the OS**.
+
+Let your HTTPS stack handle HTTP/1.1 vs. HTTP/2 vs. HTTP/3 support; don't treat DNS-over-HTTP/3 as a separate protocol. I don't know enough about DNSCrypt to make an informed recommendation about it, but DoQ and DoH meet my needs well enough.
+

content/posts/spoiler-element.md

@@ -1,6 +1,6 @@
 ---
 title: "Proposal: an HTML element for spoilers"
-description: "An informal proposal for dedicated elements for spoiler tags in HTML: use-cases, syntax, semantics, recommended UA behavior, and comparisions with <details>."
+description: "An informal proposal for dedicated elements for spoiler tags in HTML: use-cases, syntax, semantics, recommended UA behavior, and comparisons with <details>."
 date: 2023-11-12T13:48:00-08:00
 outputs:
     - html

static/webfinger.json

@@ -181,6 +181,11 @@
 			"href": "https://linuxreviews.org/User:Seirdy",
 			"type": "text/html"
 		},
+		{
+			"rel": "http://webfinger.net/rel/profile-page",
+			"href": "https://ln.ht/~Seirdy",
+			"type": "text/html"
+		},
 		{
 			"rel": "http://webfinger.net/rel/profile-page",
 			"href": "https://tinygem.org/Seirdy/",