From e5907e23495aa0fa194c13a318da71be45acb8e3 Mon Sep 17 00:00:00 2001
From: Melody Horn <melody@boringcactus.com>
Date: Sun, 13 Apr 2025 11:33:35 -0600
Subject: overhaul <details> display

---
 _posts/2023-02-12-uuid-versions.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

(limited to '_posts/2023-02-12-uuid-versions.md')

diff --git a/_posts/2023-02-12-uuid-versions.md b/_posts/2023-02-12-uuid-versions.md
index 9293056..52d5fde 100644
--- a/_posts/2023-02-12-uuid-versions.md
+++ b/_posts/2023-02-12-uuid-versions.md
@@ -17,11 +17,12 @@ in the early 90s, some UNIX people ran into this problem when drawing up their D
 the UUID format has two control fields and three data fields. the version field is pretty straightforward - it's 1 for UUIDv1, 2 for UUIDv2, etc. at this point, they only had 1 and 2, but they left room in the spec for up to 15 just in case. there's also a variant field, which says whether it's a normal UUID (`10`, hex value `8` through `b`) or some other bullshit that may or may not adhere to any of the rest of this spec.
 
 <details>
-
 <summary>other bullshit</summary>
+<aside>
 
 if the variant field is `0` then it's a UUID from Apollo Computer's Network Computing System, which had UUIDs before DCE but defined them in a slightly different way. if it's `110` then it's a UUID but the wrong endian, which Microsoft does sometimes when it makes UUIDs (it calls them GUIDs, because they're thinking too small, merely Global rather than Universal). if it's `111` then you're living in the future where they assigned a meaning to variant `111`. what's it like? how's the whole climate change thing going?
 
+</aside>
 </details>
 
 the data fields are
-- 
cgit v1.2.3