diff --git a/content/notes/JS-enabled-engines.md b/content/notes/JS-enabled-engines.md
index 9b330fe..7a0a0bd 100644
--- a/content/notes/JS-enabled-engines.md
+++ b/content/notes/JS-enabled-engines.md
@@ -1,7 +1,7 @@
 ---
 title: "JS-enabled engines"
 date: 2022-06-02T18:30:30-07:00
-replyURI: "https://mk.nixnet.social/notes/911asmc9rn"
+replyURI: "http://archive.today/2022.09.10-195228/https://mk.nixnet.social/notes/911asmc9rn"
 replyTitle: "if search engine crawlers didn't run JavaScript the Web would be better"
 replyType: "SocialMediaPosting"
 replyAuthor: "Alexandra"
diff --git a/content/posts/website-best-practices.md b/content/posts/website-best-practices.md
index d7ee211..10eae3e 100644
--- a/content/posts/website-best-practices.md
+++ b/content/posts/website-best-practices.md
@@ -1612,7 +1612,7 @@ Imagine your typical "modern" website's deployment pipeline. It requires thousan
 
 Ten years from now, how much of this will still work?
 
-Try to ensure that your website can be archived, and/or easily re-built and served on an ordinary server. This way, your work can still be made accessible after you're gone. For example: all my site requires to build is a tarball of statically-linked binaries, a POSIX shell, and a decent Make implementation (bmake and GNU make work) to build; see [my build manifest](https://git.sr.ht/~seirdy/seirdy.one/tree/master/item/.build.yml). To serve, it just needs a static web server.
+Try to ensure that your website can be archived, and/or easily re-built and served on an ordinary server. This way, your work can still be made accessible after you're gone. For example: all my site requires to build is a tarball of statically-linked binaries, a POSIX shell, and a decent Make implementation (bmake and GNU make work) to build; see [my build manifest](https://git.sr.ht/~seirdy/seirdy.one/tree/e591c9d1ee54c16c40f4b8f2c1eab9e830577681/item/.build.yml). To serve, it just needs a static web server.
 
 Testing
 -------