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=NICE_REPLY_A, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 7280 invoked from network); 18 Aug 2022 16:59:36 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 18 Aug 2022 16:59:36 -0000 Received: from dpmailmta01.doteasy.com ([65.61.218.6]) by 9front; Thu Aug 18 12:58:03 -0400 2022 X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=192.168.101.81; Received: from dpmailrp01.doteasy.com (unverified [192.168.101.81]) by dpmailmta01.doteasy.com (DEO) with ESMTP id 95829986-1394429 for <9front@9front.org>; Thu, 18 Aug 2022 09:57:52 -0700 Return-Path: Received: from dpmail01.doteasy.com (dpmail01.doteasy.com [192.168.101.1]) by dpmailrp01.doteasy.com (8.15.2/8.15.2/Debian-8+deb9u1) with ESMTP id 27IGvpKd017702 for <9front@9front.org>; Thu, 18 Aug 2022 09:57:52 -0700 X-SmarterMail-Authenticated-As: fde101@fjrhome.net Received: from [192.168.1.81] (pool-173-67-134-57.hrbgpa.fios.verizon.net [173.67.134.57]) by dpmail01.doteasy.com with SMTP (version=Tls12 cipher=Aes256 bits=256); Thu, 18 Aug 2022 09:57:32 -0700 Message-ID: <1fc39a84-d4cf-b280-7cb5-1bf7a10e1e3d@fjrhome.net> Date: Thu, 18 Aug 2022 12:57:27 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.1.2 Content-Language: en-US To: 9front@9front.org References: <9BAA91F5C6FAC6721688D0F7710FB552@eigenstate.org> <59E49EBC-5853-4BBD-A67D-EB772CE0ECAE@stanleylieber.com> From: "Frank D. Engel, Jr." In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Exim-Id: 1fc39a84-d4cf-b280-7cb5-1bf7a10e1e3d X-Bayes-Prob: 0.8612 (Score 2, tokens from: base:default, @@RPTN) X-CanIt-Geo: No geolocation information available for 192.168.101.1 X-CanItPRO-Stream: base:default X-Canit-Stats-ID: 01894VPu3 - df7f4e092bb5 - 20220818 X-Scanned-By: CanIt (www . roaringpenguin . com) on 192.168.101.81 X-Originating-IP: 192.168.101.81 List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: pipelining configuration ACPI over YAML GPU scripting frontend Subject: Re: [9front] dangerous Exit menu item in sub-rio Reply-To: 9front@9front.org Precedence: bulk Why not move the confirmation to be first - so that the user needs to confirm that they even want the option to exit before it shows up in the menu? Or else have the option there but disabled unless a modifier key is held down on the keyboard (hold down shift or whatever to enable the exit item)? On 8/18/22 12:22 PM, Kurt H Maier wrote: > On Thu, Aug 18, 2022 at 09:59:40AM -0600, Jacob Moody wrote: >> On 8/18/22 07:59, Stanley Lieber wrote: >>> what if the gray background is completely covered up? >>> >>> maybe exit could imitate delete and just require a second click (but this time, click anywhere and the current rio dies). we don’t have to call it a confirmation, we can pretend we’re a hunter targeting our prey. we could even borrow the skull and crossbones icon from mothra. maybe this would disturb the cognitive load just enough to be effective? >>> >>> sl >> This is exactly how it works now, following the latest commit made this morning. >> >> Thanks, >> >> moody > > Awful. Terrible. Clicking exit should result in a modal dialog > confirmation box, and upon confirmation should shitcan all running > processes in the subrio, black out the screen, and print "It Is Now Safe > To Turn Off Your Rio" in huge orange letters. The market has spoken. > > khm >