From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-3.6 required=3.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from mail-qk1-x735.google.com (mail-qk1-x735.google.com [IPv6:2607:f8b0:4864:20::735]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 949B91F560 for ; Fri, 15 Sep 2023 19:17:30 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; unprotected) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=google header.b=AJv/aSLV; dkim-atps=neutral Received: by mail-qk1-x735.google.com with SMTP id af79cd13be357-76f0807acb6so160686585a.1 for ; Fri, 15 Sep 2023 12:17:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; t=1694805448; x=1695410248; darn=public-inbox.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=iW1mlhK1SAIX2yod0cjn+UnmfoJhfxXfT6WpS3XG+eY=; b=AJv/aSLVYETx3Ay0naDdlx1xrLrC0NWYGq4ZVb1ue1lZ/mqvsdfB/28bmyhBtaWxTb EWqvGsxUdV76F4EvW8bvDcvKqW/rCINt+/CDwEVrdlMjteVplZm6NxfxdmLxzq4Tq4y1 /oZFq5p9qTlWz7NHx7+lGExgH9+EwAddQ6mUc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694805448; x=1695410248; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=iW1mlhK1SAIX2yod0cjn+UnmfoJhfxXfT6WpS3XG+eY=; b=b8SHfvWSRG+1sPA+3n411qgecOIy7KecSx223khAQHtQPtS/xCbmNxxFnzGy49h6CP XUNoOBFOGeBSi0b4Ol7c/SkFvT6wAkk5u+GC8MvQqTkzC0hHkVAijiEPfMJdRCwTmi/y MHih2oaSaS8p425WZB15RZZNHuifuNtFsHp+MmBPrtIUm+J1TC5SuoLWO1mlunUCKsEO 8vEaId6BOl+kWvfNrGm/TYSbZLll3WRx64TLFhtn8FtRf7rQHLeb0UdA2uPdtBWLn42b q/f1awyfqfGtixgOzketLqPmG8Jb/wk+OU7pCY3YEddKRtakmqSFKiwabf+tGXdO5XBY 2m1A== X-Gm-Message-State: AOJu0YzMJV8JHUf0Ddxy6BVeJqaFi/KqbYwYlt3Mn1MMtu0uFvrqxs4j oJwX0zYg6n6T+iM5RyZrhniff8ETQ8Eg+fW25fU= X-Google-Smtp-Source: AGHT+IEBnmwyTf+SKV1wEYFqrabzSvTQgGL2I332DldAwF9+dwj+IBNpJqCgw4QfdmafD/zesK6hxQ== X-Received: by 2002:a05:620a:3886:b0:76c:e0c5:2f6c with SMTP id qp6-20020a05620a388600b0076ce0c52f6cmr2246951qkn.38.1694805447888; Fri, 15 Sep 2023 12:17:27 -0700 (PDT) Received: from nitro.local ([209.226.106.110]) by smtp.gmail.com with ESMTPSA id z3-20020ae9c103000000b00767e98535b7sm1426322qki.67.2023.09.15.12.17.27 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 15 Sep 2023 12:17:27 -0700 (PDT) Date: Fri, 15 Sep 2023 15:17:19 -0400 From: Konstantin Ryabitsev To: Eric Wong Cc: meta@public-inbox.org Subject: Re: [RFC] pop3: support `?limit=$NUM' parameter in mailbox name Message-ID: <20230915-skittle-huff-36d60d@meerkat> References: <20230912-impart-swinger-4c2434@meerkat> <20230912224034.M689061@dcvr> <20230913062040.M617670@dcvr> <20230913-sizzling-uncoated-629002@meerkat> <20230913220326.M198766@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20230913220326.M198766@dcvr> List-Id: On Wed, Sep 13, 2023 at 10:03:26PM +0000, Eric Wong wrote: > > What if we move the uuid into the password field -- it seems it belongs there > > anyway, as it's tied to the user cookie. > > I've thought about that, too; but it can get tricky since passwords > aren't visible in most UIs. I've also seen some UIs (not POP3) which > forbid copy+paste in password fields. > > Furthermore, if a user wants to migrate to a different POP3 client; > carrying their UUID with them is easier when it's readable in the > username. (I'm assuming users won't be bothered backup their UUID > anywhere) That makes sense. > I'm open to supporting both ways; but I'm also not inclined to > do so unless there's evidence of real-world POP3 clients being > unable to handle the user names. > > Documenting both ways can be overwhelming to users. Yes, let's keep it as-is -- I'll test the patches shortly and follow up with details. -K