From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, guidoakiu(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #18718: Incorrect Twitter/X Logo Displayed on PostgreSQL Documentation Page |
Date: | 2024-11-21 14:33:43 |
Message-ID: | C28D5823-6CF1-4595-B3CD-309C79FFD9F7@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
> On 21 Nov 2024, at 13:44, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>
> On Thu, Nov 21, 2024 at 1:41 PM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> > On 21 Nov 2024, at 13:32, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> >
> > On 2024-Nov-21, PG Bug reporting form wrote:
> >
> >> 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.
> >
> > I propose we simply remove any links to Twitter from the website.
>
> 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).
>
> +1.
>
> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Bertrand Drouvot | 2024-11-21 14:35:50 | Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails |
Previous Message | Bruce Momjian | 2024-11-21 14:21:16 | Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails |