MIME-Version: 1.0
References: <718B8706-A775-449A-9996-2288DF4F51D4@yesql.se>
 <1acf4e56-6669-6f18-b71c-b977641e07eb@postgresql.org>
In-Reply-To: <1acf4e56-6669-6f18-b71c-b977641e07eb@postgresql.org>
From: Magnus Hagander <magnus@hagander.net>
Date: Fri, 8 Oct 2021 10:51:55 +0200
Message-ID: 
 <CABUevEy5XGc-0wwq_ie0Lt6vLHRq3KoFPWTxVfhrVM9Dg8a8NA@mail.gmail.com>
Subject: Re: Blogspot links in the Planet policy
To: "Jonathan S. Katz" <jkatz@postgresql.org>
Cc: Daniel Gustafsson <daniel@yesql.se>,
 PostgreSQL WWW <pgsql-www@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000006d176d05cdd37ecb"
Archived-At: 
 <https://www.postgresql.org/message-id/CABUevEy5XGc-0wwq_ie0Lt6vLHRq3KoFPWTxVfhrVM9Dg8a8NA%40mail.gmail.com>
Precedence: bulk

--0000000000006d176d05cdd37ecb
Content-Type: text/plain; charset="UTF-8"

On Thu, Oct 7, 2021 at 11:56 PM Jonathan S. Katz <jkatz@postgresql.org>
wrote:

> On 10/7/21 5:08 PM, Daniel Gustafsson wrote:
> > I noticed today that the example URLs for blogspot content in the Planet
> > PostgreSQL policy are actual <a> tagged links (without nofollow), which
> doesn't
> > seem right.  I propose to apply the attached.  Since it only change the
> > rendering of the policy and not the content, that should be
> uncontroversial I
> > assume?
>
> +1
>

+1.

I think the only other thing to consider would be to drop the blogpost
section completely. Surely this is not a "frequently asked question" about
planet postgresql. It was at one time, but it 's been a very long time
since we saw anything like that. Blogspot is kind of a... thing of the past?

And if we want to keep it it should probably go somewhere else than in the
poblicy. Everything else in the FAQ is about the actual policy, except for
this one which is a technical question about one particular provider.

So a +1 for fixing it, but a +5 for moving it somewhere else or just plain
removing it.

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

--0000000000006d176d05cdd37ecb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Thu, Oct 7, 2021 at 11:56 PM Jonat=
han S. Katz &lt;<a href=3D"mailto:jkatz@postgresql.org">jkatz@postgresql.or=
g</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
>On 10/7/21 5:08 PM, Daniel Gustafsson wrote:<br>
&gt; I noticed today that the example URLs for blogspot content in the Plan=
et<br>
&gt; PostgreSQL policy are actual &lt;a&gt; tagged links (without nofollow)=
, which doesn&#39;t<br>
&gt; seem right.=C2=A0 I propose to apply the attached.=C2=A0 Since it only=
 change the<br>
&gt; rendering of the policy and not the content, that should be uncontrove=
rsial I<br>
&gt; assume?<br>
<br>
+1<br></blockquote><div><br></div><div>+1.</div><div><br></div><div>I think=
 the only other thing to consider would be to drop the blogpost section com=
pletely. Surely this is not a &quot;frequently asked question&quot; about p=
lanet postgresql. It was at one time, but it &#39;s been a very long time s=
ince we saw anything like that. Blogspot is kind of a... thing of the past?=
</div><div><br>And if we want to keep it it should probably go somewhere el=
se than in the poblicy. Everything else in the FAQ is about the actual poli=
cy, except for this one which is a technical question about one particular =
provider.</div><div><br></div><div>So a=C2=A0+1 for fixing it, but a=C2=A0+=
5 for moving it somewhere else or just plain removing it.</div></div><div><=
br></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr"=
><div>=C2=A0Magnus Hagander<br>=C2=A0Me: <a href=3D"http://www.hagander.net=
/" target=3D"_blank">https://www.hagander.net/</a><br>=C2=A0Work: <a href=
=3D"http://www.redpill-linpro.com/" target=3D"_blank">https://www.redpill-l=
inpro.com/</a></div></div></div></div>

--0000000000006d176d05cdd37ecb--