Fix broken links

Got consent from some more fedi users :3

content/notes/motivations-for-dropping-jpeg-xl.md

@@ -1,7 +1,8 @@
 ---
 title: "Motivations for dropping JPEG-XL"
 date: 2023-01-12T15:40:35-08:00
-replyURI: "https://vulpine.club/@eevee/109674417561084417"
+date: 2023-01-12T15:51:10-08:00
+replyURI: "https://web.archive.org/web/20230131193442/https://vulpine.club/@eevee/109674417561084417"
 replyTitle: "with the jpeg xl thing…pushing their own formats is convenient for their other products"
 replyType: "SocialMediaPosting"
 replyAuthor: "Eevee"

content/posts/website-best-practices.gmi

@@ -573,7 +573,7 @@ Browser support for displaying alt-text in place of broken images seems good. Mo
 => https://adrianroselli.com/2020/10/alternative-text-for-css-generated-content.html Alternative Text for CSS Generated Content
 
 That post seems to indicate that Firefox 81 on macOS 10.15 didn't display alt-text, but users report correct alt-text display in more recent Firefox versions:
-=> https://cybre.space/@nleigh/108688070682694730 Fediverse thread soliciting screenshots of alt-text display in Firefox on macOS.
+=> https://web.archive.org/web/20231210072526/https://cybre.space/@nleigh/108688070682694730 Fediverse thread soliciting screenshots of alt-text display in Firefox on macOS.
 
 On Gemini, much of this section applies to varying degrees. I typically employ this approach when linking to e.g. images. Sometimes, I even do this when linking to gemtext or HTML documents.
 

content/posts/website-best-practices.md

@@ -1910,7 +1910,7 @@ A special thanks goes out to GothAlice for the questions she answered in <samp>#
 
 [^21]: [WebAIM](https://wave.webaim.org/api/docs?format=html) and the [University of Illinois](https://fae.disability.illinois.edu/rulesets/IMAGE_4_EN/) recommend 100 characters; [Tangaru](https://www.tanaguru.com/en/) recommends an even smaller limit of 80 characters. I sometimes exceed 100 characters for detailed images but usually stay below 80.
 
-[^22]: Browser support for displaying alt-text in place of broken images seems good. More information about support for alt-text exposure can be found on {{<mention-work itemtype="BlogPosting">}}{{<cited-work name="Alternative Text for CSS Generated Content" extraName="headline" url="https://adrianroselli.com/2020/10/alternative-text-for-css-generated-content.html">}}{{</mention-work>}}. That post seems to indicate that Firefox 81 on macOS 10.15 didn't display alt-text, but [users report correct alt-text display](https://cybre.space/@nleigh/108688070682694730) in more recent Firefox versions.
+[^22]: Browser support for displaying alt-text in place of broken images seems good. More information about support for alt-text exposure can be found on {{<mention-work itemtype="BlogPosting">}}{{<cited-work name="Alternative Text for CSS Generated Content" extraName="headline" url="https://adrianroselli.com/2020/10/alternative-text-for-css-generated-content.html">}}{{</mention-work>}}. That post seems to indicate that Firefox 81 on macOS 10.15 didn't display alt-text, but [users report correct alt-text display](https://web.archive.org/web/20231210072526/https://cybre.space/@nleigh/108688070682694730) in more recent Firefox versions.
 
 [^23]: Once it gains basic support across all browsers and screen readers, I might recommend using `aria-details` instead of <code>aria-<wbr />describedby</code> for more complex descriptions. At the time of writing, [`aria-details` is only supported by JAWS](https://a11ysupport.io/tech/aria/aria-details_attribute). {{<mention-work itemtype="TechArticle">}}{{<cited-work name="WAI-ARIA 1.2" url="https://www.w3.org/TR/wai-aria-1.2/#aria-details">}}{{</mention-work>}} describes `aria-details` with an example similar to the one I gave in [code snippet 5](#xkcd-html).
 

csv/rewrites.csv

@@ -44,3 +44,4 @@ https://sparkly.uni.horse/@emily/109350421306301429,https://web.archive.org/web/
 https://sparkly.uni.horse/@emily/109224061809444742,https://web.archive.org/web/20221125010627/https://sparkly.uni.horse/@emily/109224061809444742
 https://polarhive.ml/blog/messengers/,https://polarhive.net/blog/messengers/
 https://itnan.ru/post.php?c=1&p=552844,https://web.archive.org/web/20221219060315/https://itnan.ru/post.php?c=1&p=552844#22936344
+https://news.elias.sh/posts/05-2021/,https://web.archive.org/web/20221219060306/https://news.elias.sh/posts/05-2021/

linter-configs/htmltest.yml

@@ -46,13 +46,13 @@ IgnoreURLs:
   - "https://seirdy.one/.well-known/webfinger" # inexplicable false positive
   - "https://strugee.net/" # refuses connection
   - "https://www.moonshot.forbiddenl0ve.net/index.php" # cert mismatch false positive
-  - "https://fediring.net/(previous|next)" # redir
   # - "https://forum.palemoon.org/viewtopic.php?f=1&t=25473" # manual check: blocks crawlers
   - "https://forum.palemoon.org/viewtopic.php"
   - "https://queue.acm.org/detail" # manual check: blocks crawlers
   - "https://plausible.io/blog/google-floc#" # manual check: I block this domain
   # - "https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830173" # manual check: 400 for some reason, using curl works fine.
   - "https://bugs.debian.org/cgi-bin/bugreport.cgi"
+  - "https://www.science.org/content/blog-post/deliberately-optimizing-harm" # http 413, browser works fine.
   # - "https://forum.kuketz-blog.de/viewtopic.php?p=78202" # manual check: blocks crawlers
   - "https://forum.kuketz-blog.de/viewtopic.php"
   - "https://web.archive.org/" # the wayback machine itself.