user/dev discussion of public-inbox itself
 help / color / Atom feed
From: Dmitry Alexandrov <>
To: Eric Wong <>
Cc: Mateusz Loskot <>,
Subject: Re: Default theme
Date: Fri, 22 Feb 2019 23:39:47 +0300
Message-ID: <> (raw)
In-Reply-To: <20190222085014.mwvkf2mwrb6yeyrh@dcvr> (Eric Wong's message of "Fri, 22 Feb 2019 08:50:14 +0000")

[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]

Eric Wong <> wrote:
> Mateusz Loskot <> wrote:
>> I've noticed the theme has changed, from light to dark,
>> while browsing archives.
> There was no theme before, just browser defaults.

Pardon my unasked advice, but IMHO, that was a very wise choice.

> The way I see it is:  whatever color scheme I choose will make
> some people unhappy.

Why to choose any then?

> That's why I make sure it's customizable
> via user CSS and the CSS class names remain stable.

Via overriding *author* CSS, you mean.  A user stylesheet is supposed to serve as a defaults with a lower preference.

Indeed, designers of the today’s Web completely reject an idea that you know better, which typefaces, sizes, colours, line height and width, etc make it easier for you to read text on your display, as something ridiculous; so if you to disagree with them, you have to write and test numerous overrides for every single website, instead of specifying it once and for all.

And I was quite disappointed to discover that even owners of now joined them.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply index

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-21 13:36 Mateusz Loskot
2019-02-22  8:50 ` Eric Wong
2019-02-22 20:39   ` Dmitry Alexandrov [this message]
2019-02-23  2:47     ` Eric Wong
2019-02-23 10:56       ` [PATCH 0/2] ensure user CSS always overrides BOFH CSS Eric Wong
2019-02-23 10:56         ` [PATCH 1/2] set "!important" to override BOFH prefs Eric Wong
2019-02-23 10:56         ` [PATCH 2/2] www: prevent '!important' in BOFH-specified CSS Eric Wong
2019-02-23 19:55       ` Default theme Mateusz Loskot
2019-02-22 20:53   ` Mateusz Loskot
2019-02-23  1:19     ` Dmitry Alexandrov
2019-02-23  2:50       ` Eric Wong
2019-02-23 10:49         ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

user/dev discussion of public-inbox itself

Archives are clonable:
	git clone --mirror
	git clone --mirror http://czquwvybam4bgbro.onion/meta
	git clone --mirror http://hjrcffqmbrq6wope.onion/meta
	git clone --mirror http://ou63pmih66umazou.onion/meta

Example config snippet for mirrors

Newsgroups are available over NNTP:

 note: .onion URLs require Tor:

AGPL code for this site: git clone