Re: remove twitter links

Hello

This (untested) patch removes links to Twitter at the bottom of pages,
per discussion at https://postgr.es/m/18718-19d3521550f7b12e@postgresql.org

Also remove the accompanying Git link, which is unlikely to be useful.

--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
Essentially, you're proposing Kevlar shoes as a solution for the problem
that you want to walk around carrying a loaded gun aimed at your foot.
(Tom Lane)

On 11/21/24 10:00 AM, Alvaro Herrera wrote:
> Hello
>
> This (untested) patch removes links to Twitter at the bottom of pages,
> per discussion at https://postgr.es/m/18718-19d3521550f7b12e@postgresql.org
>
> Also remove the accompanying Git link, which is unlikely to be useful.

I don't agree with the discussion on there. We still maintain a X
profile (with news coming from it), and the git link lets people more
easily find the codebase, which otherwise is challenging to find.

We can just update the logo to be more correct.

Jonathan

On 11/21/24 08:11, Jonathan S. Katz wrote:
> On 11/21/24 10:00 AM, Alvaro Herrera wrote:
>> Hello
>>
>> This (untested) patch removes links to Twitter at the bottom of pages,
>> per discussion at
>> https://postgr.es/m/18718-19d3521550f7b12e@postgresql.org
>>
>> Also remove the accompanying Git link, which is unlikely to be useful.
>
> I don't agree with the discussion on there. We still maintain a X
> profile (with news coming from it), and the git link lets people more
> easily find the codebase, which otherwise is challenging to find.
>
> We can just update the logo to be more correct.

+1

>
> Jonathan
>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

> On Nov 21, 2024, at 08:11, Jonathan S. Katz <jkatz(at)postgresql(dot)org> wrote:
> I don't agree with the discussion on there. We still maintain a X profile (with news coming from it), and the git link lets people more easily find the codebase, which otherwise is challenging to find.

I am +0 about the git link either way, but +1 to removing the Twitter/X link. At this point, I don't think it makes sense to point directly to a specific social media network. Having a single link there for the community's social media presences would be a more useful solution, rather than privileging Twitter/X.

On Thu, Nov 21, 2024 at 8:34 AM Christophe Pettus <xof(at)thebuild(dot)com> wrote:
>
> At this point, I don't think it makes sense to point directly to a specific social media network. Having a single link there for the community's social media presences would be a more useful solution, rather than privileging Twitter/X.

+1

As for the Git link, I'd be pretty surprised if it got any significant
traffic. Things like that belong up top, IMHO, unless we've somehow
trained people to habitually scroll to the bottom of web pages to find
Git logos.

--Jacob

Le jeu. 21 nov. 2024 à 17:46, Jacob Champion <
jacob(dot)champion(at)enterprisedb(dot)com> a écrit :

> On Thu, Nov 21, 2024 at 8:34 AM Christophe Pettus <xof(at)thebuild(dot)com>
> wrote:
> >
> > At this point, I don't think it makes sense to point directly to a
> specific social media network. Having a single link there for the
> community's social media presences would be a more useful solution, rather
> than privileging Twitter/X.
>
> +1
>
>
+1 too.

As for the Git link, I'd be pretty surprised if it got any significant
> traffic. Things like that belong up top, IMHO, unless we've somehow
> trained people to habitually scroll to the bottom of web pages to find
> Git logos.
>
> --Jacob
>
>
>

--
Guillaume.

On 11/21/24 12:52 PM, Guillaume Lelarge wrote:
> Le jeu. 21 nov. 2024 à 17:46, Jacob Champion
> <jacob(dot)champion(at)enterprisedb(dot)com
> <mailto:jacob(dot)champion(at)enterprisedb(dot)com>> a écrit :
>
> On Thu, Nov 21, 2024 at 8:34 AM Christophe Pettus <xof(at)thebuild(dot)com
> <mailto:xof(at)thebuild(dot)com>> wrote:
> >
> > At this point, I don't think it makes sense to point directly to
> a specific social media network.  Having a single link there for the
> community's social media presences would be a more useful solution,
> rather than privileging Twitter/X.
>
> +1
>
>
> +1 too.

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. It gives another way for folks to connect
with places we're sending information from the community (news, etc.).
I'd also say there's a high probability we continue to add more links there.

I started on a patch to update the Twitter/X logo - we have to do some
adaptations for light/dark on the logo, so I'll likely pick it up in the
morning.

Jonathan

> On Nov 21, 2024, at 20:59, Jonathan S. Katz <jkatz(at)postgresql(dot)org> 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. 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.

> On 22 Nov 2024, at 06:31, Christophe Pettus <xof(at)thebuild(dot)com> wrote:
>
>> On Nov 21, 2024, at 20:59, Jonathan S. Katz <jkatz(at)postgresql(dot)org> 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.

> 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.

--
Daniel Gustafsson

On 11/22/24 3:48 AM, Daniel Gustafsson wrote:
>> On 22 Nov 2024, at 06:31, Christophe Pettus <xof(at)thebuild(dot)com> wrote:
>>
>>> On Nov 21, 2024, at 20:59, Jonathan S. Katz <jkatz(at)postgresql(dot)org> 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

In a situation like this, data matters.

I think you would find that the two links at the bottom of that page get
about zero clicks. Who has time to scroll through the wall of text that is
the front page vs what is likely the two most clicked links (documentation,
download)?

+1 on updating because that is correct
-1 on removing as it would remove a contact point
+1 on having a subsection in the Community section that lists all social
accounts

On Sat, Nov 23, 2024 at 10:13 AM Jonathan S. Katz <jkatz(at)postgresql(dot)org>
wrote:

> On 11/22/24 3:48 AM, Daniel Gustafsson wrote:
> >> On 22 Nov 2024, at 06:31, Christophe Pettus <xof(at)thebuild(dot)com> wrote:
> >>
> >>> On Nov 21, 2024, at 20:59, Jonathan S. Katz <jkatz(at)postgresql(dot)org>
> 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
>
>
>
>
>

On Thu, Nov 21, 2024 at 11:34 AM Christophe Pettus <xof(at)thebuild(dot)com> wrote:

> I am +0 about the git link either way, but +1 to removing the Twitter/X
> link. At this point, I don't think it makes sense to point directly to a
> specific social media network. Having a single link there for the
> community's social media presences would be a more useful solution, rather
> than privileging Twitter/X.
>

+1, well said.

On 11/22/24 9:34 AM, Jonathan S. Katz wrote:
> On 11/22/24 3:48 AM, Daniel Gustafsson wrote:
>>> On 22 Nov 2024, at 06:31, Christophe Pettus <xof(at)thebuild(dot)com> wrote:
>>>
>>>> On Nov 21, 2024, at 20:59, Jonathan S. Katz <jkatz(at)postgresql(dot)org>
>>>> 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.

Here's the first patchset to update the icons in the footer.

0001 patch is primarily the boiler plate to upgrade font awesome to get
the newer icons.

0002 removes the images and swaps them out with the icons, which removes
the problem we're having with light/dark mode. This also allows us to
add in more icons, i.e. Bluesky, which we now have an account with the
@postgresql.org domain.

Later, I'll have a 3rd patch that adds to the contact page the social
links (We already have X/Twitter on that one).

Thanks,

Jonathan

Hi,

On Thu, 2024-11-21 at 21:31 -0800, Christophe Pettus wrote:
>  If we're going to link to Twitter/X, though, we should link to
> Mastodon and BlueSky at a minimum. 

+1.

Regards,
--
Devrim Gündüz
Open Source Solution Architect, PostgreSQL Major Contributor
Twitter: @DevrimGunduz , @DevrimGunduzTR

Devrim =?ISO-8859-1?Q?G=FCnd=FCz?= <devrim(at)gunduz(dot)org> writes:
> On Thu, 2024-11-21 at 21:31 -0800, Christophe Pettus wrote:
>>  If we're going to link to Twitter/X, though, we should link to
>> Mastodon and BlueSky at a minimum. 

> +1.

+1. I'm not for removing the links to X, but we should treat all
those services on an equal basis.

regards, tom lane

On 11/23/24 20:43, Tom Lane wrote:
> Devrim =?ISO-8859-1?Q?G=FCnd=FCz?= <devrim(at)gunduz(dot)org> writes:
>> On Thu, 2024-11-21 at 21:31 -0800, Christophe Pettus wrote:
>>>  If we're going to link to Twitter/X, though, we should link to
>>> Mastodon and BlueSky at a minimum.
>
>> +1.
>
> +1. I'm not for removing the links to X, but we should treat all
> those services on an equal basis.

+1 here as well.

<release-duty hat>
However if we are going to really treat them all equally, to me that
implies that we should have official community accounts on all of them,
and we should have the release announcements automatically pushed to all
of them the way the X announcements are now.

Also, is there an equivalent to "pinning the tweet" on all of those?
</release-duty hat>

--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

> On Nov 24, 2024, at 07:25, Joe Conway <mail(at)joeconway(dot)com> wrote:
>
> <release-duty hat>
> However if we are going to really treat them all equally, to me that implies that we should have official community accounts on all of them, and we should have the release announcements automatically pushed to all of them the way the X announcements are now.

+1

> Also, is there an equivalent to "pinning the tweet" on all of those?
> </release-duty hat>

BlueSky and Mastodon both have pinned posts, pretty much the same in concept as X.

On Sun, Nov 24, 2024 at 4:25 PM Joe Conway <mail(at)joeconway(dot)com> wrote:

> On 11/23/24 20:43, Tom Lane wrote:
> > Devrim =?ISO-8859-1?Q?G=FCnd=FCz?= <devrim(at)gunduz(dot)org> writes:
> >> On Thu, 2024-11-21 at 21:31 -0800, Christophe Pettus wrote:
> >>> If we're going to link to Twitter/X, though, we should link to
> >>> Mastodon and BlueSky at a minimum.
> >
> >> +1.
> >
> > +1. I'm not for removing the links to X, but we should treat all
> > those services on an equal basis.
>
> +1 here as well.
>
> <release-duty hat>
> However if we are going to really treat them all equally, to me that
> implies that we should have official community accounts on all of them,
> and we should have the release announcements automatically pushed to all
> of them the way the X announcements are now.
>
> Also, is there an equivalent to "pinning the tweet" on all of those?
> </release-duty hat>
>
>
We should absolutely not link to a service where we don't have an *active*
account. The point isn't linking to the service itself, the point is
(obviously) to link to *our* presence on the service. At this moment,
that's pretty much just X, but there is WIP on fixing that, independently
of what's linked.

--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>

On 25/11/2024 09:44, Magnus Hagander wrote:
> On Sun, Nov 24, 2024 at 4:25 PM Joe Conway <mail(at)joeconway(dot)com> wrote:
>
> On 11/23/24 20:43, Tom Lane wrote:
> > Devrim =?ISO-8859-1?Q?G=FCnd=FCz?= <devrim(at)gunduz(dot)org> writes:
> >> On Thu, 2024-11-21 at 21:31 -0800, Christophe Pettus wrote:
> >>>  If we're going to link to Twitter/X, though, we should link to
> >>> Mastodon and BlueSky at a minimum.
> >
> >> +1.
> >
> > +1.  I'm not for removing the links to X, but we should treat all
> > those services on an equal basis.
>
> +1 here as well.
>
> <release-duty hat>
> However if we are going to really treat them all equally, to me that
> implies that we should have official community accounts on all of
> them,
> and we should have the release announcements automatically pushed
> to all
> of them the way the X announcements are now.
>
> Also, is there an equivalent to "pinning the tweet" on all of those?
> </release-duty hat>
>
>
> We should absolutely not link to a service where we don't have an
> *active* account.  The point isn't linking to the service itself, the
> point is (obviously) to link to *our* presence on the service. At this
> moment, that's pretty much just X, but there is WIP on fixing that,
> independently of what's linked.

At this point there are no social media accounts anymore on the website.
People do not have a chance to follow the project on the most common
accounts.

Is there any plan to link to existing presences?
And what happened to the WIP for other platforms?

--
Andreas 'ads' Scherbaum
German PostgreSQL User Group
European PostgreSQL User Group - Board of Directors
Volunteer Regional Contact, Germany - PostgreSQL Project

> On 19 Mar 2025, at 16:02, Andreas 'ads' Scherbaum <ads(at)pgug(dot)de> wrote:

> Is there any plan to link to existing presences?
> And what happened to the WIP for other platforms?

According to the commit message there are plans on replacing the now removed
links, but I assume pgconf.dev organizing etc has consumed a lot of available
resources.

commit 403be5a3878a24793b89a988fbf4dbf48f6b194c
Author: Jonathan S. Katz <jonathan(dot)katz(at)excoventures(dot)com>
Date: Wed Feb 12 21:12:49 2025 -0800

Prepare for social link updates

The full work will be handled in a subsequent patch, but for now
prepare for the update while finalizing the design.

--
Daniel Gustafsson