From b288090b886573e69b4c8d7d79126ef5af9757fb Mon Sep 17 00:00:00 2001 From: Seirdy Date: Sun, 23 Jun 2024 16:22:24 -0400 Subject: [PATCH] Syndicate --- content/notes/on-valid-xhtml5-again.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/notes/on-valid-xhtml5-again.md b/content/notes/on-valid-xhtml5-again.md index 74255ac..292ce62 100644 --- a/content/notes/on-valid-xhtml5-again.md +++ b/content/notes/on-valid-xhtml5-again.md @@ -6,9 +6,9 @@ replyTitle: "what if I put in a bunch of effort to make my website valid XHTML5" replyType: "SocialMediaPosting" replyAuthor: "LunarEclipse" replyAuthorURI: "https://lunareclipse.zone/" -#syndicatedCopies: -# - title: 'The Fediverse' -# url: '' +syndicatedCopies: + - title: 'The Fediverse' + url: 'https://pleroma.envs.net/objects/4660408b-41dc-4850-9197-9ce6585fceb7' --- Switching a site to XHTML5 is only a lot of work at first, because it may have latent bugs. For instance, you may have a stray tag that the HTML parser auto-closes but an XHTML parser won't. I find this effort worthwhile because [some of these bugs will eventually visibly manifest]({{}}).