From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.6 required=5.0 tests=BAYES_00,DATE_IN_PAST_24_48
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: a07f3367d7,59c3b3f9911c9191
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.66.89.161 with SMTP id bp1mr1636608pab.33.1343315774963;
        Thu, 26 Jul 2012 08:16:14 -0700 (PDT)
Path: 
 b9ni65033298pbl.0!nntp.google.com!border1.nntp.dca.giganews.com!border4.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!nx02.iad01.newshosting.com!newshosting.com!newspump.sol.net!94.232.116.11.MISMATCH!feed.xsnews.nl!border-1.ams.xsnews.nl!newsfeed.straub-nv.de!nuzba.szn.dk!pnx.dk!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail
From: Simon Wright <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Re: Ada.Calendar and NTP (and Unix Epoch)
Date: Tue, 24 Jul 2012 20:25:50 +0100
Organization: A noiseless patient Spider
Message-ID: <m2fw8hq7up.fsf@nidhoggr.home>
References: <500dc548$0$2936$f40e02c5@shockwave.dk.telia.net>
	<m2wr1tqtnq.fsf@nidhoggr.home> <jum2mm$4vi$1@speranza.aioe.org>
	<m2obn5qjrf.fsf@nidhoggr.home>
	<500ed475$0$9508$9b4e6d93@newsspool1.arcor-online.net>
Mime-Version: 1.0
Injection-Info: mx04.eternal-september.org;
 posting-host="edf2659fbb8cb6d4b5f62db4b36ac1e6";
	logging-data="26478"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX18adWt0QOAJECMvMU29aNpgpAT/Gckev2s="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1 (darwin)
Cancel-Lock: sha1:mOgSu29q1gTwbKXTXpaTMcAB2xg=
	sha1:8P2vsJta3cyTQEAFsCPZIei9bPA=
Content-Type: text/plain
Date: 2012-07-24T20:25:50+01:00
List-Id: <comp.lang.ada>

Georg Bauhaus <rm.dash-bauhaus@futureapps.de> writes:

> In the end, the world frame operators will succeed in convincing
> computer users that they always need to ask the operator do anything
> with their computers. It is very well possible to adjust CSS settings
> to personal preferences using what is called a user style sheet.

I couldn't see a way to do this with Safari. I followed the recipe I
found on the Web for Firefox: no effect.

On Chrome I found Stylish which does the trick; I had to include both
.parity0 and .parity1 settings to eliminate all trace.

However, I will now disable it, since I quite like the effect complained
of!