From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 31490 invoked from network); 15 Jul 2021 03:22:34 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 15 Jul 2021 03:22:34 -0000 Received: from mimir.eigenstate.org ([206.124.132.107]) by 1ess; Wed Jul 14 23:13:31 -0400 2021 Received: from abbatoir.myfiosgateway.com (pool-74-108-56-225.nycmny.fios.verizon.net [74.108.56.225]) by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id ff7d35b2 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO) for <9front@9front.org>; Wed, 14 Jul 2021 20:13:17 -0700 (PDT) Message-ID: <962979BA9BD1BAD282CBD98AA1DE556E@eigenstate.org> To: 9front@9front.org Date: Wed, 14 Jul 2021 23:13:15 -0400 From: ori@eigenstate.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: NoSQL CSS-scale locator Subject: Re: [9front] Mouse clipping patch Reply-To: 9front@9front.org Precedence: bulk Quoth hiro <23hiro@gmail.com>: > > yes i like the idea and all that, but the reality is that rio is > already *not* transparent. and this is the case in multiple ways, both > architectural and in the user interface. Yes. How do we simplify that situation, instead of making it worse?