From: Eric Wong <e@80x24.org>
To: Dmitry Alexandrov <321942@gmail.com>
Cc: Mateusz Loskot <mateusz@loskot.net>, meta@public-inbox.org
Subject: Re: Default theme
Date: Sat, 23 Feb 2019 02:47:12 +0000 [thread overview]
Message-ID: <20190223024712.qcvjsnnwzfzxp3az@dcvr> (raw)
In-Reply-To: <87mumn4kx8.fsf@gmail.com>
Dmitry Alexandrov <321942@gmail.com> wrote:
> Eric Wong <e@80x24.org> 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
> public-inbox.org now joined them.
Choosing any theme at all for public-inbox.org 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 :)
next prev parent reply other threads:[~2019-02-23 2:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 13:36 Default theme 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] usercontent.pm: 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190223024712.qcvjsnnwzfzxp3az@dcvr \
--to=e@80x24.org \
--cc=321942@gmail.com \
--cc=mateusz@loskot.net \
--cc=meta@public-inbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).