user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: Philip Oakley <philipoakley@iee.org>
Cc: meta@public-inbox.org
Subject: Re: Favicon for (each) public-inbox
Date: Sun, 28 Aug 2016 09:46:30 +0000	[thread overview]
Message-ID: <20160828094630.GA6395@dcvr.yhbt.net> (raw)
In-Reply-To: <2F13E0B57ABA45B69F2C0EEC92E89F1B@PhilipOakley>

Philip Oakley <philipoakley@iee.org> wrote:
> Eric,
> 
> Would it be possible for the Public-Inbox to provide a simple
> Favicon(*), either for the whole site, or in someway for each
> in-box?

For people running the PSGI themselves, yes, it should 404 so
Plack::App::Cascade (or similar) may be used to fallback to
serving as a static file.

On my server, I have an empty file in favicon.ico so it is
served as a 200 (using Plack::App::File or similar).  This
reduces HTTP requests since favicon-requesting clients tend to
try repeatedly on 404s but not 200s.

> I've added the git public-inbox to my firefox bookmarks as "GitPI"
> (neat eh.), but all I get for the Icon part is a dull grey world. A
> bit of colour would be nice.

I'm afraid having any sort of icon for public-inbox itself would
be a bad representation of the project itself which strives to
be graphics-free and discourage the use of graphics (especially
for branding/marketing).

It seems every image rendering library has been affected by
nasty security bugs in recent years and I'm trying to get users
to reduce their attack surface (and save bandwidth!) by using
non-graphical browsers.

Fwiw, my slow response has been the result of having poor
connectivity the past few days.

> --
> Philip
> 
> (*) I didn't even know what they were called until I searched to see
> if I could customise the Icon. The Mozilla help pages tells me 'no',
> it comes from the source...
> https://support.mozilla.org/en-US/questions/1097942

Ideally, you could patch/hack your browser easily.  I will do my
best to make the public-inbox code easy-to-hack/customize/run,
at least.  I'm extremely picky about UI; mainly, it's _user_
interface, and should be decided for and by a particular user,
not some UI developer.

I've managed without icons for years.  As somebody with bad
eyesight and hearing, I find touch + muscle memory (keystrokes)
the best UI.

      reply	other threads:[~2016-08-28  9:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-18  9:51 [PATCH 0/2] begin online help for each public-inbox Eric Wong
2016-08-18  9:51 ` [PATCH 1/2] www: implement generic help text Eric Wong
2016-08-18  9:51 ` [PATCH 2/2] searchview: link to internal " Eric Wong
2016-08-18 19:29 ` [PATCH 0/2] begin online help for each public-inbox Philip Oakley
2016-08-18 19:33   ` Eric Wong
2016-08-26 19:30 ` Favicon for (each) public-inbox Philip Oakley
2016-08-28  9:46   ` Eric Wong [this message]

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=20160828094630.GA6395@dcvr.yhbt.net \
    --to=e@80x24.org \
    --cc=meta@public-inbox.org \
    --cc=philipoakley@iee.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).