fix bad URLs

content/notes/flatpak-and-web-browsers.md

@@ -5,7 +5,7 @@ replyURI: "https://floss.social/@alcinnz/108466919900074368"
 replyTitle: "The outer layer will be via FlatPak"
 replyType: "SocialMediaPosting"
 replyAuthor: "Adrian Cochrane"
-replyAuthorURI: "https://rhapsode.adrian.geek.nz/"
+replyAuthorURI: "https://adrian.geek.nz/"
 ---
 You might want to provision namespace-based isolation for your browsers. But that could throw a wrench into Flatpak-based distribution.
 

content/notes/new-search-box.md

@@ -3,6 +3,6 @@ title: "New search box"
 date: 2022-05-26T17:42:09-07:00
 ---
 
-I decided my site had enough content to warrant a search form, so I added one to the footer. I kanged the CSS from [gov.uk](https://www.gov.uk/); I liked how their search box was adaptive yet compatible with legacy browsers. This is a static site so I made it point to [Search My Site](https://searchmysite.net), which regularly crawls my whole website.
+I decided my site had enough content to warrant a search form, so I added one to the footer. I kanged the CSS from [gov.uk](https://www.gov.uk/); I liked how their search box was adaptive yet compatible with legacy browsers. This is a static site so I made it point to [Search My Site](https://searchmysite.net/), which regularly crawls my whole website.
 
-Eventually I'll add a dynamic page for search results (probably using the Search My Site API), and add an ATOM feed for posts and notes (I currently have an RSS feed for posts, and that's not going anywhere). If I get those two, I'll be ready for the next step of setting up [WebSub](https://w3c.github.io/websub/) and starting on [IndieMark 4](https://indieweb.org/IndieMark) (I've decided not to <abbr title="Publish on Own Site, Syndicate Elsewhere">POSSE</abbr> *all* my microblog posts, to maintain some separation between my "Rohan" and "Seirdy" identities).
+Eventually I'll add a dynamic page for search results (probably using the Search My Site API), and add an ATOM feed for posts and notes (I currently have an RSS feed for posts, and that's not going anywhere). If I get those two, I'll be ready for the next step of setting up [WebSub](https://www.w3.org/TR/websub/) and starting on [IndieMark 4](https://indieweb.org/IndieMark) (I've decided not to <abbr title="Publish on Own Site, Syndicate Elsewhere">POSSE</abbr> *all* my microblog posts, to maintain some separation between my "Rohan" and "Seirdy" identities).

content/notes/resize-and-reflow.md

@@ -10,6 +10,6 @@ replyAuthorURI: "https://yatil.net"
 
 This is a good article on the difference between SC 1.4.4 and 1.4.10. However, I don't think these criteria go far enough:
 
-Even narrower viewports exist. KaiOS devices tend to have 240&nbsp;px viewports; smartwatches tend to have half the width of a phone while emulating a phone width (Apple Watches can be instructed not to do this with a proprietary `meta` tag). Of course, making sites watch-compatible is a stretch, but support for feature phones running KaiOS should be reasonable. I wrote about this more in <cite>[Best practices for inclusive textual websites](https://seirdy.one/posts/2020/11/23/website-best-practices/)</cite>.
+Even narrower viewports exist. KaiOS devices tend to have 240&nbsp;px viewports; smartwatches tend to have half the width of a phone while emulating a phone width (Apple Watches can be instructed not to do this with a proprietary `meta` tag). Of course, making sites watch-compatible is a stretch, but support for feature phones running KaiOS should be reasonable. I wrote about this more in <cite>[Best practices for inclusive textual websites]({{<relref "/posts/website-best-practices">}})</cite>.
 
 Another thing worth remembering is that users can change default fonts or override sire-set fonts. Don't just test with default default fonts; test with something wider. These criteria should specify some font metrics or (royalty free) representative wide fonts to use for testing.

content/notes/signal-security.md

@@ -2,7 +2,7 @@
 title: "Signal security"
 date: 2022-05-26T12:18:24-07:00
 lastMod: 2022-05-26T12:18:24-07:00
-replyURI: "https://disqordia.space/notice/AJqmgRLFlyVENIXcDA"
+replyURI: "https://web.archive.org/web/20220620162305/https://disqordia.space/notice/AJqmgRLFlyVENIXcDA"
 replyTitle: "europe wants to ban signal"
 replyType: "SocialMediaPosting"
 replyAuthor: "chjara"

content/posts/floss-security.gmi

@@ -123,7 +123,7 @@ It enumerates plenty of information about Zoom without access to its source code
 
 To try this out yourself, use a sandbox designed for dynamic analysis. Cuckoo is a common and easy-to-use solution, while DRAKVUF is more advanced.
 
-=> https://cuckoosandbox.org/ Cuckoo Sandbox: automated malware analysis
+=> https://github.com/cuckoosandbox Cuckoo Sandbox: automated malware analysis
 => https://drakvuf.com/ DRAKVUF® Black-box Binary Analysis System
 
 ### Extreme example: the truth about Intel ME and AMT

content/posts/floss-security.md

@@ -132,7 +132,7 @@ Decompilers are seldom used alone in this context. Instead, they're typically a
 
 These reverse-engineering techniques---a combination of tracing, packet sniffing, binary analysis, and memory dumps---make up the workings of most modern malware analysis. See [this example](https://www.hybrid-analysis.com/sample/1ef3b7e9ba5f486afe53fcbd71f69c3f9a01813f35732222f64c0981a0906429/5e428f69c88e9e64c33afe64) of a fully-automated analysis of the Zoom Windows installer. It enumerates plenty of information about Zoom without access to its source code: reading unique machine information, anti-VM and anti-reverse-engineering tricks, reading config files, various types of network access, scanning mounted volumes, and more.
 
-To try this out yourself, use a sandbox designed for dynamic analysis. [Cuckoo](https://cuckoosandbox.org/) is a common and easy-to-use solution, while [DRAKVUF](https://drakvuf.com/) is more advanced.
+To try this out yourself, use a sandbox designed for dynamic analysis. [Cuckoo](https://github.com/cuckoosandbox) is a common and easy-to-use solution, while [DRAKVUF](https://drakvuf.com/) is more advanced.
 
 ### Extreme example: the truth about Intel ME and AMT