From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 8BC25158083 for ; Thu, 26 Sep 2024 05:09:10 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 033CB2BC01B; Thu, 26 Sep 2024 05:09:04 +0000 (UTC) Received: from out.packetderm.com (out.packetderm.com [173.166.91.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 990DB2BC013 for ; Thu, 26 Sep 2024 05:09:03 +0000 (UTC) Received: from localhost (out.packetderm.com[173.166.91.13]) by smtp (5.7.4/5.7.4) with ESMTPSA id 48Q591Ph099326 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Thu, 26 Sep 2024 01:09:02 -0400 (EDT) (envelope-from waltdnes@waltdnes.org) Date: Thu, 26 Sep 2024 01:08:54 -0400 From: Walter Dnes To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Wayland! Beware of! Message-ID: References: <65e5de50-e053-46ff-be61-52f472d95025@gentoo.org> <6af6d0dd-f081-4345-b574-ea6d6c9358bb@gentoo.org> <86a5fw7xv6.fsf@gentoo.org> <5563bc4b-23e0-40ee-959d-a4b527cbaded@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5563bc4b-23e0-40ee-959d-a4b527cbaded@gentoo.org> X-Archives-Salt: eda939fb-e724-4889-9990-fa972349ee68 X-Archives-Hash: cfa1afbe6ca06564c761a99063e66d37 On Wed, Sep 25, 2024 at 08:25:12PM -0400, Eli Schwartz wrote > I think the two of you are talking past each other. What did Arsen mean > by "the vague concept of IPv6"? I suspect he meant: > > You are trying to solve a concrete user issue with your browsing. Correct. > Your idea of how to solve the user issue is to blame IPv6, then get all > meta about how to solve it and decide that the vague concept of IPv6 > must be eradicated and purged from the public consciousness You're overdoing it and you seem offended. I was not "thinking deep thoughts about IPV6" or going off the deep end with QANON conspiracies. Back then I was unaware of the power of sysctl or using the kernel command line. All that I (and a lot of other people) knew was that... USE="ipv6" ==> delays and timeouts for people on IPV4-only systems USE="-ipv6" ==> problems solved for people on IPV4-only systems This was simply a pragmatic decision to solve a problem. Firefox with USE="ipv6" probably would've worked OK on a machine with a working IPV6 connection. > -- rather than disabling the specific issue that is causing problems. Looking at the output of "sysctl -a | grep net.ip | less" *ON MY SYSTEM*, I see a slew of "net.ipv4.*" entries, but no "net.ipv6.*" entries, so there's no "sysctl knob" to tweak. -- There are 2 types of people 1) Those who can extrapolate from incomplete data