> I'm thinking of a policy of curating such things in one or more
> files organizing and indexing "generally useful stuff", with pointers
> to repos, tarballs, etc. of the code itself, and behind the scenes
> also making backups of them, so if the site rots or the user is banned
> the code it contained can be resurrected.

That reminds, I've been thinking it could be useful to have a
"file.scheme.org" server storing an archive of Scheme-related files such
as tarballs and PDFs. We could serve all the RnRS reports from there, as
well as past releases of Scheme implementations.

Having them in a central location would be nice for archival, as you say
it guards against losing the files (though web.archive.org is wonderful,
it is not always simple to navigate) in case the original sites go
missing and the authors are no longer reachable. We could also provide
an index of all the files from api.scheme.org. In case there are
copyright or security problems with some files, there would be a central
place to clear them out.

Finally, it would give us simple and stable URLs to refer to popular
files. Something like this:

https://file.scheme.org/r5rs.pdf
https://file.scheme.org/r6rs-app.pdf
https://file.scheme.org/gambit-v4_9_3.tgz
https://file.scheme.org/kali-0.52.2.tar.gz
https://file.scheme.org/ypsilon-0.9.6.update3.tar.gz