| Date | Commit message (Collapse) |
|---|
|
The concept of a "mailing list" infers the existence of a
centralized subscriber list, and hurts forkability. The
"public inbox" concept is a more accurate description and
mostly centralization-resistant, aside from domain names.
|
|
I've gotten cgit to work well for browsers without CSS
support (patches posted to <cgit@lists.zx2c4.com>).
For browsers with CSS support, the color scheme
is now dark and can help save electricity for users
of OLED and CRT displays.
|
|
We've had HTTPS support for several years, now.
|
|
There's no point in advertising the mlmmj subscription: Nobody's
subscribed in ~5 years and I never wanted to deal with
delivering mail over SMTP, anyways.
The subscriber list is a point-of-centralization, anyways.
Furthermore, the NNTP, Atom, and HTML interfaces all allow
reading archives anonymously without needing a throwaway email
address.
|
|
Oops :x
|
|
Might as well eat our own dogfood w.r.t. yahns TLS support
|
|
Also, give the Atom feed a little more visibility.
|
|
HTTPS provides some security against spying and MitM attacks,
so refer users to HTTPS sites, instead.
|
|
HTTPS adds some level of privacy protection and helps marketing
(because we care soooo much about good marketing! :P).
Performance-wise, this reduces subjectAltName bloat when
negotiating connections and will also speed up occasional
certificate renewals when/if we drop the old name.
Also, not occupying the document root of a domain will make it
easier to add alternative site locations in the future, because
centralization sucks and I don't like the idea of anybody paying
ICANN or similar entities for domain names.
|
|
Remove all pandoc references. We shouldn't need to clutter our
documentation with out-of-date references to pandoc, and pod2man is
probably widely-available enough that nobody should need to install
it.
Reduce HTTP redirects when linking to external sites.
It's also excessive to mention libkqueue as using the native
implementation (whether it be kqueue or epoll) is preferred
and easier.
|
|
Using the 'update-copyright' script from gnulib[1]:
git ls-files | UPDATE_COPYRIGHT_HOLDER='all contributors' \
UPDATE_COPYRIGHT_USE_INTERVALS=2 \
xargs /path/to/gnulib/build-aux/update-copyright
We're also switching to 'GPL-3.0+' as recommended by SPDX
to be consistent with our gemspec and other metadata
(as opposed to the longer but equivalent "GPLv3 or later").
[1] git://git.savannah.gnu.org/gnulib.git
|
|
It's been there long enough and kqueue itself hasn't changed. In
fact, IIRC the entire design of yahns (for another server in late
2011) probably came about because of the name "kqueue"...
|
|
This is no place to advertise weirdo projects.
|
|
The service seems stable and reliable enough to advertise in our
README.
|
|
Otherwise it may be hard for non-hackers to to find in HACKING....
|
|
Note: technically we remain unofficially 1.9.3-compatible
outside of extras/try_gzip_static.rb, but we won't try very
hard to remain 1.9.3 compatibility in the future.
We'll also stop advertising Rubinius compatibility: I am no longer
willing to deal with proprietary bug trackers.
In the future, becoming 2.0.0+ only will allow us to drop the
close_on_exec=true assignments we do all over the place.
|
|
As evidenced by the presence of :wait_readable and :wait_writable
combinations in our case/when statements, we may support TLS in the
future. So add an exception for supporting the "openssl" extension
in the C standard library.
However, GnuTLS support ought to be an option, too.
|
|
* updated kqueue support status
* noted sbrk/mmap scalability issue
* speling fiks ("optimally")
* indent "git clone" invocation
* updated copyright status
|
|
Rubyforge is going away on May 15, so update our docs for it.
|
|
This release now depends on "kgio-sendfile", a (hopefully temporary)
fork of the original sendfile gem for mainline ruby trunk
compatibility and a (probably correct) FreeBSD-related bugfix.
kqueue/FreeBSD support is considered highly experimental. Of course;
you should never rely on anything in production unless you can get bugs
fixed in every part of your stack; even the kernel. yahns (ab)uses
kqueue and epoll in uncommon ways, so you may encounter subtle kernel
bugs along the way.
Because yahns has been self-hosting its own website for months without
crashes or major problems (BORING! :P), I've decided to start hosting the
yahns website <http://yahns.YHBT.net/README> with ruby trunk (currently
r45341).
yahns - dangerous by design (and sleepy!)
|
|
This should hopefully educate users of the potential negative
consequences of using yahns without understanding it. Or scare off
some of the willfully ignorant :P
|
|
MRI 1.9.3 support was not hard to add, does not impact performance, and
there are still many sites on 1.9.3. We'll only support Rubinius as
best-effort for now since their issue tracker runs on an API shich is
non-Free Software (and filled with crap CSS/JS). Redmine (for MRI)
is easier to deal with for me.
|
|
Shorter URLs should be easier-to-type, since we already have
the project name in the path component of the URL.
|
|
Hmm... greylisting is annoying on Rubyforge.
|
|
|