Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tEUjy-007hDp-3p for pgsql-www@arkaria.postgresql.org; Fri, 22 Nov 2024 14:34:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tEUjw-009B0s-PJ for pgsql-www@arkaria.postgresql.org; Fri, 22 Nov 2024 14:34:32 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tEUjw-009Azj-Fl for pgsql-www@lists.postgresql.org; Fri, 22 Nov 2024 14:34:32 +0000 Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tEUjt-003EPe-Ln for pgsql-www@lists.postgresql.org; Fri, 22 Nov 2024 14:34:31 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:From:References:Cc:To:Subject:MIME-Version:Date:Message-ID:Sender :Reply-To:Content-ID:Content-Description; bh=dzbqY1AbUqX76GR2b4URbpqf4Q9slF0wjMCPPoePRbs=; b=CTlh6OfIC0uSUQ3h65ANG4Cqi9 9S7DcsF/pd6z/r3/zqi15e/UxoWeFvBWWdHiG9jxgCTFOyXM3N0fE80zQZvIp4z/sKTXEoGPyYxYK kyCuuKRuOXPmBQtjEgNLZXsJ2Me+waFKa/pvgUHbIpVMxCqYDheK7fSoJUc8uqXedZ0UaBQB4hePW vU8jTTmRdUywIGETWCUGAKK2KdLfpOTb6DB5cgQLe9JAcHTaIbTfBmX72dCTHXgdT5l4v/vIGiV9I ETMshTXkgTFq9C36rSFphcLwoFpT5e6GzK2dYrESo/6sk5Bj2KoGo/6PaDDNA/8nx4pvG6pEokhlq XD9VfDpw==; Received: from syn-108-176-026-082.biz.spectrum.com ([108.176.26.82] helo=[172.24.9.47]) by meldrar.postgresql.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tEUji-007xmw-5n; Fri, 22 Nov 2024 14:34:20 +0000 Message-ID: <8ced7424-407e-4ac7-9e8d-6b3fb7e64a34@postgresql.org> Date: Fri, 22 Nov 2024 09:34:12 -0500 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: remove twitter links To: Daniel Gustafsson , Christophe Pettus Cc: Guillaume Lelarge , Jacob Champion , Alvaro Herrera , w^3 References: <202411211500.vmk6eobdmosb@alvherre.pgsql> <2B01B195-2EBA-47DB-AED4-CBEC254DB1FF@thebuild.com> <80ff5ad7-de4e-478a-ae87-e6a4ab7e4c2c@postgresql.org> <01FAF3FB-46EC-44DD-9790-597201826DB9@yesql.se> Content-Language: en-US From: "Jonathan S. Katz" In-Reply-To: <01FAF3FB-46EC-44DD-9790-597201826DB9@yesql.se> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 11/22/24 3:48 AM, Daniel Gustafsson wrote: >> On 22 Nov 2024, at 06:31, Christophe Pettus wrote: >> >>> On Nov 21, 2024, at 20:59, Jonathan S. Katz wrote: >>> Many other community website have these kinds of links (the NPOs, conferences), and also at the bottom of their pages. I don't see why we'd remove that from .org. >> >> I don't think anyone is suggesting having no link to social media at the bottom of the page. If we're going to link to Twitter/X, though, we should link to Mastodon and BlueSky at a minimum. > > Totally agree. The 2nd sentence, that was clipped from the above said "I'd also say there's a high probability we continue to add more links there." which aligns with what was stated above, i.e. adding more socials or other links. >> I think it makes more sense to have a separate page on .org with the social media links, and link to that from the footer. > > We already have about/contact linked to in the footer which in turn links to > Twitter, reworking that page (perhaps also making the link more prominent) with > links to all the various social media presences might be more useful. I think that's fine, but we should also be careful that folks may not necessarily respond from socials on the main account. Jonathan