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=1.0 required=5.0 tests=DATE_IN_PAST_06_12,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM autolearn=no autolearn_force=no
	version=3.4.4
Received: (qmail 29600 invoked from network); 14 Jul 2021 23:31:13 -0000
Received: from 1ess.inri.net (216.126.196.35)
  by inbox.vuxu.org with ESMTPUTF8; 14 Jul 2021 23:31:13 -0000
Received: from mail-lf1-f54.google.com ([209.85.167.54]) by 1ess; Wed Jul 14 14:42:16 -0400 2021
Received: by mail-lf1-f54.google.com with SMTP id q16so5296079lfa.5
        for <9front@9front.org>; Wed, 14 Jul 2021 11:42:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-transfer-encoding;
        bh=SoB7xcZjS/vw23nIeQU7VwDMeq5sl1jEQldsOeeJLtI=;
        b=XZRemJnoLkpfMeJBV+6VVjd4bv/HowDcCK64xdDx+MKLJBJJV11SNvsLDmOKXdClSl
         CP9VVJSfRNyXuTZFYxojUf43Zh8xggh2IMTLp/NZURR1EUobbuOevCSy3HcL5HhpFJ8q
         X8QqKh8P6jg6UGlNtOx19oMfny+J2z+WkokWCMDZiezXiOSGVFErA0xEoS0cC9B/mlgs
         5tP6E9SoMETPZSAEpa2VuivGLHOv5Moh3ZASM93Z4Kf/uRFr9NlUxMLb7rjYMApSlXnM
         9oSsLR5enFmZ6xATjKw5Lr9CwA0F6CIFVowMDYKdMzTkBI6iV/ymr+NaaF3qIU4UZSbC
         UwVw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:in-reply-to:references:from:date
         :message-id:subject:to:content-transfer-encoding;
        bh=SoB7xcZjS/vw23nIeQU7VwDMeq5sl1jEQldsOeeJLtI=;
        b=gXf5CI49rX20lt7Je9iN6UmTjxDuRWVnUerb0PAO73vTPwDOqdbEO9htSPsxEaVBCv
         zg3w/2XHBTPXt/OEYbW0PAVFaq+yZnprmwX5dSfQhTJO/nGTphle0EYhV9CMiI0okNrl
         QT05z5vPGiZ52GrhPwKJ2KrmTNjUdH9YElm/ZsJXdiIKakkzzplhz0V7fMWkFjc5fWW6
         p5w5CY5PrC9ZW88d8z/zl+988ZQ96nIHBi5XAU+4Op88WYLx1D3ldK/cGYfjJ78qTOGy
         nZeF3eR9BFnAxCNWdCO/86GtZScjbowZlhin4P26baDTrEkIz0HfHn4cFxh/0ZiIv8x6
         eZvA==
X-Gm-Message-State: AOAM530uQ6oAQj1pjXR8HKcxVlUU/cISxNjpKTBZ04ramLRzrDAO6ssa
	1WrSUoqL9YGt/MsDRDuaaD30xukNU7ToRXypP+uNsu0XzTQ=
X-Google-Smtp-Source: ABdhPJxUgB0QAIseb98RuXj9VIqraRqbTX63ADL9IAOHFtOW7BUXrhjobbmtUnGGMW2WkWPsL8yWWlUoCVui9amBBT4=
X-Received: by 2002:a17:906:86ce:: with SMTP id j14mr11818671ejy.152.1626264274022;
 Wed, 14 Jul 2021 05:04:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a17:906:76c8:b029:4d9:7711:78cc with HTTP; Wed, 14 Jul 2021
 05:04:32 -0700 (PDT)
In-Reply-To: <CAA85C84kc46zYNxTJdzfu4V9aU+8ipyKdD8u_Bgo4UDcUzgaUg@mail.gmail.com>
References: <CAA85C879ggSM=fPu+CcgToakbhMh2Rk=A5gn3AWsPUqUYGFckQ@mail.gmail.com>
 <8CE29EA89CBA8F74C1D4D8EEF2528473@eigenstate.org> <CAA85C87qdQe6Bj6E4XvGwgOd7_cgQOJ4Yiv8tRhL4pEzzMTqQQ@mail.gmail.com>
 <CAFSF3XPsOK5f2-5s1ZG=nSEP+ejng+vLfZZ+J_iX=RuTTpoYjg@mail.gmail.com>
 <CAA85C84DWyYoo-y4-errRfwvgFyktO+faRGhA6JdMunwOfvWCw@mail.gmail.com>
 <CABB-WO9KD40paOd-hnHsqGoq_0=6s4uoW_xmXJNwd15Zx5Yhvg@mail.gmail.com>
 <CAFSF3XPhDeKiKXdsL0Abnderm45Uc2GCPYsi6ygSaBkf7gDBmA@mail.gmail.com>
 <CAA85C84BsFY97VYJZjMufRZmPcBmEVvVZ+EsMxyDkGfPJELbpw@mail.gmail.com> <CAA85C84kc46zYNxTJdzfu4V9aU+8ipyKdD8u_Bgo4UDcUzgaUg@mail.gmail.com>
From: Stuart Morrow <morrow.stuart@gmail.com>
Date: Wed, 14 Jul 2021 13:04:32 +0100
Message-ID: <CABB-WO8u9QVLuUWeNNO+wyBY4axHG4k1QgE3SFAmYy_8-iSdMA@mail.gmail.com>
To: 9front@9front.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: social browser WEB2.0 STM method reduce/map solution 
Subject: Re: [9front] Mouse clipping patch
Reply-To: 9front@9front.org
Precedence: bulk

On 13/07/2021, Jos=C3=A9 Miguel S=C3=A1nchez Garc=C3=ADa <soy.jmi2k@gmail.c=
om> wrote:
> Thinking about it, seems like screenlock is the odd one here: I can't
> think about other use case which would require that level of control
> over the mouse. Ideally, a system which could "navigate up" the stack
> of rio (unfocusing them from their container) would be a good idea to
> both escape the clip prison and also to open the door to future
> keyboard-based interactions in an elegant way. If that didn't get in
> the way of screenlock, I would undoubtely implement that.

There's no reason screenlock *has* to start using the clip prison
instead of to keep doing what it's doing. If I were you I'd just do
what you wanna do and ignore screenlock.