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 1tE8Ft-005MeM-2s for pgsql-bugs@arkaria.postgresql.org; Thu, 21 Nov 2024 14:34:01 +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 1tE8Fr-00GQ9z-MF for pgsql-bugs@arkaria.postgresql.org; Thu, 21 Nov 2024 14:33:59 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tE8Fr-00GQ9r-Bd for pgsql-bugs@lists.postgresql.org; Thu, 21 Nov 2024 14:33:59 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tE8Fn-0037Mm-Fl for pgsql-bugs@lists.postgresql.org; Thu, 21 Nov 2024 14:33:56 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id 8BEF1140635 for ; Thu, 21 Nov 2024 15:33:54 +0100 (CET) Received: from s981.loopia.se (unknown [172.22.191.5]) by s807.loopia.se (Postfix) with ESMTP id 72D7A1400DE; Thu, 21 Nov 2024 15:33:54 +0100 (CET) Received: from s473.loopia.se (unknown [172.22.191.6]) by s981.loopia.se (Postfix) with ESMTP id 70E8322B1712; Thu, 21 Nov 2024 15:33:54 +0100 (CET) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1.2 X-Spam-Level: X-Spam-Status: No, score=-1.2 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1] autolearn=disabled Authentication-Results: s473.loopia.se (amavisd-new); dkim=pass (2048-bit key) header.d=yesql.se Received: from s934.loopia.se ([172.22.191.6]) by s473.loopia.se (s473.loopia.se [172.22.190.13]) (amavisd-new, port 10024) with LMTP id 3pg1diONixA0; Thu, 21 Nov 2024 15:33:54 +0100 (CET) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.193 Received: from smtpclient.apple (customer-89-255-232-193.stosn.net [89.255.232.193]) (Authenticated sender: daniel@yesql.se) by s934.loopia.se (Postfix) with ESMTPSA id D78AB7CEA4E; Thu, 21 Nov 2024 15:33:53 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yesql.se; s=loopiadkim1707475645; t=1732199634; bh=sjGuWD00KLgCxMXFfl3q+43waeG5oKbCOgfTakScAiY=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=cARLQjwv2en4t14pxZjsO/mbn1Ptz3c+3nTLbjM010Ah8TypRmUpYRzQKk0LprCjw JwZRJZ4yBk6UdJ1PKhaN66pAtGFVfXv4YdbrEH4Tr5Pj/04LkC9ZLn1T7a/Hi4BFv+ orGiBwwVGn2fOlKXoAF+PenZiCArDiz82oCImQMX2ks0BR5+6FUA4ClTiZKBPefLNo QBLCpS7MExkFqeuzlZvCRzy6yHrBcpo7Ulxe92EbgLvA7qi0oOAjm7fb/yIGb6R2T8 65GNyeUQLXH/tC/oG8cyUaHeXtNUwSVKdWHKltdV08jX5g08yw082bAKQq6dxhgL9l gk1zqfS0AgBOg== Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.1\)) Subject: Re: BUG #18718: Incorrect Twitter/X Logo Displayed on PostgreSQL Documentation Page From: Daniel Gustafsson In-Reply-To: Date: Thu, 21 Nov 2024 15:33:43 +0100 Cc: Alvaro Herrera , guidoakiu@gmail.com, pgsql-bugs@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <202411211232.uwdaj7kmrlbv@alvherre.pgsql> <2977716D-834B-4463-BF1A-183E9F2BEC71@yesql.se> To: Magnus Hagander X-Mailer: Apple Mail (2.3776.700.51.11.1) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 21 Nov 2024, at 13:44, Magnus Hagander wrote: >=20 > On Thu, Nov 21, 2024 at 1:41=E2=80=AFPM Daniel Gustafsson = wrote: > > On 21 Nov 2024, at 13:32, Alvaro Herrera = wrote: > >=20 > > On 2024-Nov-21, PG Bug reporting form wrote: > >=20 > >> I would like to bring to your attention a small issue on the = PostgreSQL > >> documentation page. While browsing, I noticed that the Twitter logo > >> displayed still features the old bird icon instead of the updated = "X" > >> logo following Twitter's recent rebranding. =20 > >=20 > > I propose we simply remove any links to Twitter from the website. >=20 > I'm inclined to agree. Without placing any value judgment on either = platform, > the fact that the social media landscape is highly fragmented these = days (as > opposed to when the site redesign was launched) makes removing the = logo more > appealing than fixing it (since fixing it IMHO opens up for listing = multiple > networks). It might be more relevant to list postgres presence on = social media > under Community or Support and reclaim some vertical space (the Git = link can > also be removed, few if any will likely be helped by that). >=20 > +1. >=20 > And yes, I think removing the git link as well. To keep it from being missed by interested parties this should be raised = on -www of course. -- Daniel Gustafsson