> I've created a public S3 bucket called org.schemers.files, and I'll pay
> the storage costs.  Note that if there is to be an index.html page it
> will have to be maintained by hand: there is no fallback to just listing
> all the files with links, as web servers typically provide.  The URL
> would be <https://s3.amazonaws.com/org.schemers.files/index.html> we can
> make files.schemers.org <http://files.schemers.org> point to this.
>
> Note the S in fileS.
>
> Hmm, there seems to be a problem with public access.  I'll look into it
> when I have a chance.

Thanks for the initiative on this.

However, should we simply go with a traditional Linux server? We have at
least two servers ready with nginx set up in any case.

Disk usage for the entire file archive will probably be no more than a
few gigs.

Note: we are free to use scheme.org for the domain at this point. We
should really make the schemeorg mailing list at this point. It's good
that discussion of the domain is picking up the point.