Date | Commit message (Collapse) |
|
Thanks to Let's Encrypt, the bogomips.org now supports
HTTPS so our homepage can be moved to:
https://bogomips.org/clogger/
While clogger.bogomips.org is part of the TLS certificate, it is
needless subjectAltName bloat that should not have been created.
This will also make it easier to have multiple homepages in
the future as a Tor hidden service.
|
|
You may (optionally) subscribe to the new mailing list at:
clogger-public+subscribe@bogomips.org
You'll need to subscribe manually since librelist subscribers cannot be
imported. Of course, you do not have to be subscribed to post, either
(please Cc: everyone as folks may not be subscribed).
If your ISP prevents you from using port 25, port 587 (submission) is
open on bogomips.org. You may use Tor if you do not wish to expose your
IP when using port 587.
Any HTML mail will be flagged as spam, so please do not send it and
waste storage and bandwidth on it. Basic, old-fashioned mailing list
conventions apply: no top-posting, trim replies, attribute your quotes,
short signatures, etc.
This existing list will operate in public-inbox "hijack mode":
the new address is subscribed to the old librelist, so any messages
sent to the librelist are automatically archived to the new
public-inbox. Of course, not much happens here, anyways, so
nobody notices :)
Background:
Over the years, I've come to disagree with the subscription-required
posting policy of librelist. Combined with disabling of rsync archives,
one of my main reasons for choosing librelist back in the day are gone.
Lately, I've also been working on public-inbox, http://public-inbox.org/
an "archives-first" approach to mailing lists using git.
ssoma (git) archives are available at:
git://bogomips.org/clogger-public/
The ssoma format is described at http://ssoma.public-inbox.org/
HTML archives are going to http://bogomips.org/clogger-public/
All archives imported from gmane, and posts to this librelist
also go there.
|
|
This is more portable across different servers than Thread.current
in case of non-blocking servers which may be serving multiple
clients at once. This is also faster than relying on $e{...} since
$e{...} uses eval and that is slow.
|
|
In case I'm hit by a bus, the lesser evil is to allow the FSF
to update our license than to be stuck as LGPLv3-only in the
future.
Some documentation/gemspec formatting updates while I'm at it.
|
|
Rubyforge is going away on May 15, 2014.
|
|
Because we do, and this is still what I end up using all of the
time (startup performance, and I understand C, not C++)
|
|
Ruby 2.0.0preview1 is out, and we happen to be compatible
(with some harmless linker/build warnings)
|
|
It never /not/ worked under 1.9.3, but we should keep the
website up-to-date.
|
|
It's easier-to-read with the concise syntax.
|
|
It's clearer that we have zero commercial intent
when using a non-profit .org domain for the mailing
list.
|
|
strftime() isn't locale-independent, so it can lead to
inconsistencies in logs.
|
|
This appeared in nginx 0.9.6
|
|
|
|
Old git URLs still work, but new ones are shorter
|
|
Remove unnecessary "DESCRIPTION" header, also added note
about Rubinius support.
|
|
This lessens confusion for people configuring Clogger in
config.ru, since "File" could be mistaken for Rack::File
and "::File" needs to be specified.
|
|
|
|
There may also be some MRI users uncomfortable running C
extensions.
|
|
|
|
|
|
A bare "File" constant may conflict with Rack::File
when run inside Rack::Builder
|
|
|
|
Hopefully it was obvious before, if not it is now.
|
|
|
|
|
|
It was too much confusion to have multiple gems in the mix
and I mainly use the C extension anyways.
If we're not on a compatible version of Ruby, the extension will
just be disabled by generating a dummy no-op Makefile to work
around it.
|
|
Several bikeshed reasons brought me to this point:
* I like the README.html layout more than any default index.html
even if it's using README content. Having links on the side
helps navigation IMHO.
* publish_docs preserves timestamps to improve cache hit rate
* git is used to maintain the manifest at packaging/release-time
so my changesets have less noise in them
* git is used to generate history files (from tag messages),
this is a more DRY approach to me.
* I don't like the ".txt" suffix being translated to "_txt.html" in
URLs. I don't like the ".txt" suffix in general.
* I don't like Manifest.txt showing up in my RDoc
|