user/dev discussion of public-inbox itself
 help / color / Atom feed
From: Eric Wong <>
To: Dmitry Alexandrov <>
Cc: Mateusz Loskot <>,
Subject: Re: Default theme
Date: Sat, 23 Feb 2019 02:47:12 +0000
Message-ID: <20190223024712.qcvjsnnwzfzxp3az@dcvr> (raw)
In-Reply-To: <>

Dmitry Alexandrov <> wrote:
> Eric Wong <> wrote:
> > 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.

Oops, I think "!important" in userContent.css will fix that.
The documentation and sample CSS will be updated with "!important"

> 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.

I sympathize with that, since bright things hurt my eyes.
Unlike the rest of the web, public-inbox is intended to be
fully forkable/mirror-able and will always be.

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

Choosing any theme at all for was not an easy
decision.  But I think it was necessary given the new features
(another response coming to your other message) and the overall
goal of fighting against centralized communications platforms
and services.

UI preferences/colors is not as important as fighting against
centralization.  So if my color preference puts people off and
encourages light/un-themed mirrors to spawn, then it's a win :)

  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
2019-02-23  2:47     ` Eric Wong [this message]
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 \
    --in-reply-to=20190223024712.qcvjsnnwzfzxp3az@dcvr \ \ \ \ \

* 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