Hello,

Noticed a stale link in the "Fossil vs. Git" document and decided to check them all. Out of more than 500 links, a few really did expire. I fixed the syntax and linked to current documentation where possible, but a few historic links now lead to Wayback Machine. The "Ardoise" link changes the skin cookie; unless I'm missing a link to a skin preview mode, it might be better to remove the link altogether.

Here is the patch:

Index: www/changes.wiki
==================================================================
--- www/changes.wiki
+++ www/changes.wiki
@@ -1184,12 +1184,11 @@
      of rows in a timeline) are held in a cookie and thus persist
      across multiple pages.
   *  Rework the skin editing process so that changes are implemented
      on one of nine /draft pages, evaluated, then merged back to the
      default.
-  *  Added the [https://fossil-scm.org/skins/ardoise/timeline|Ardoise]
-     skin.
+  *  Added the [/timeline?skin=ardoise|Ardoise] skin.
   *  Fix the "fossil server" command on Unix to be much more responsive
      to multiple simultaneous web requests.
   *  Use the IPv6 stack for the "fossil ui" and "fossil server"
      commands on Windows.
   *  Support for [https://sqlite.org/sqlar|SQL Archives] as a download

Index: www/containers.md
==================================================================
--- www/containers.md
+++ www/containers.md
@@ -670,11 +670,11 @@
 




-[whatis]: https://podman.io/whatis.html
+[whatis]: https://docs.podman.io/en/latest/index.html
 
 
 ### 6.3 <a id="nspawn"></a>`systemd-container`
 
 If even the Podman stack is too big for you, the next-best option I’m

Index: www/fossil-v-git.wiki
==================================================================
--- www/fossil-v-git.wiki
+++ www/fossil-v-git.wiki
@@ -274,12 +274,12 @@
 Git lets you see "what came before".  Fossil makes it just as
 easy to also see "what came after".
 
 Leaf check-ins in Git that lack a "ref" become "detached," making them
 difficult to locate and subject to garbage collection. This
-[http://gitfaq.org/1/01/what-is-a-detached-head/|detached head
-state] problem has caused grief for
+[https://web.archive.org/web/20240725023459/https://gitfaq.org/1/01/what-is-a-detached-head/|detached
+head state] problem has caused grief for
 [https://www.google.com/search?q=git+detached+head+state | many
 Git users]. With
 Fossil, detached heads are simply impossible because we can always find
 our way back into the Merkle tree using one or more of the relations
 in the SQL database.
@@ -341,14 +341,13 @@
 
 Fossil isn't entirely C and SQL code. Its web UI [./javascript.md |
 uses JavaScript where
 necessary]. The server-side
 UI scripting uses a custom minimal
-[https://en.wikipedia.org/wiki/Tcl|Tcl] dialect called
-[https://fossil-scm.org/xfer/doc/trunk/www/th1.md|TH1], which is
-embedded into Fossil itself. Fossil's build system and test suite are
-largely based on Tcl.⁵ All of this is quite portable.
+[https://en.wikipedia.org/wiki/Tcl|Tcl] dialect called [./th1.md|TH1],
+which is embedded into Fossil itself. Fossil's build system and test
+suite are largely based on Tcl.⁵ All of this is quite portable.
 
 About half of Git's code is POSIX C, and about a third is POSIX shell
 code. This is largely why the so-called "Git for Windows" distributions
 (both [https://git-scm.com/download/win|first-party] and
 [https://gitforwindows.org/|third-party]) are actually an

Index: www/gsoc-ideas.md
==================================================================
--- www/gsoc-ideas.md
+++ www/gsoc-ideas.md
@@ -24,11 +24,11 @@
 # UI, Look and Feel
 
 Tasks for those interested in graphic/web design:
 
 * Add a quote button to the Forum, such as [discussed in this thread](https://fossil-scm.org/forum/forumpost/7ad03cd73d)
-* Improve the documentation history-browsing page to enable selection of 2 arbitrary versions to diff, similar to the [Mediawiki history feature enabled on Wikipedia](https://en.wikipedia.org/w/index.php?title=Fossil_(software)&action=history)
+* Improve the documentation history-browsing page to enable selection of 2 arbitrary versions to diff, similar to the [Mediawiki history feature enabled on Wikipedia](https://en.wikipedia.org/w/index.php?title=Fossil_\(software\)&action=history)
 * Allow diffing of Forum posts
 * General touch-ups in the existing skins. This may, depending on how deep one
   cares to dig, require digging into C code to find, and potentially modify, how
   the HTML is generated.
 * Creation of one or more new skins. This does not specifically require any C

Index: www/reviews.wiki
==================================================================
--- www/reviews.wiki
+++ www/reviews.wiki
@@ -42,18 +42,18 @@
 was a good thing I bookmarked it, because I was never able to find the
 link again (it might have been in a bug report or something). The
 reasons I first took a close look at it were (A) it stemmed from the
 sqlite project, which I've held in high regards for years (e.g. I
 wrote JavaScript bindings for it:
-<a href="http://spiderape.sourceforge.net/plugins/sqlite/">
-http://spiderape.sourceforge.net/plugins/sqlite/</a>), and (B) it could
-run as a CGI. That second point might seem a bit archaic, but in
-practice CGI is the only way most hosted sites can set up a shared
-source repository with multiple user IDs. (i'm not about to give out
-my only account password or SSH key for my hosted sites, no matter how
-much I trust the other developers, and none of my hosters allow me to
-run standalone servers or add Apache modules.)
+<a href="https://web.archive.org/web/20161107215421/http://spiderape.sourceforge.net/plugins/sqlite/">
+https://web.archive.org/web/20161107215421/http://spiderape.sourceforge.net/plugins/sqlite/</a>),
+and (B) it could run as a CGI. That second point might seem a bit
+archaic, but in practice CGI is the only way most hosted sites can set
+up a shared source repository with multiple user IDs. (i'm not about to
+give out my only account password or SSH key for my hosted sites, no
+matter how much I trust the other developers, and none of my hosters
+allow me to run standalone servers or add Apache modules.)
 
 So I tried it out. The thing which bugged me most about it was having
 to type "commit" or "com" instead of "ci" for checking in (as is
 custom in all other systems I've used), despite the fact that fossil
 uses "ci" as a filter in things like the timeline view. Looking back

Noticed a stale link in the "Fossil vs. Git" document and decided to check them all

These, with one exception, should be resolved now. Thank you for chasing these down.

The one exception is the "git detached head" bit - the Internet Archive link for that is not working for me (it finds a link but won't show me any content).