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 1rCHyC-00FFCT-Bi for pgsql-www@arkaria.postgresql.org; Sun, 10 Dec 2023 11:27:36 +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 1rCHyA-006aFV-O2 for pgsql-www@arkaria.postgresql.org; Sun, 10 Dec 2023 11:27:34 +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 1rCHyA-006aF0-FU for pgsql-www@lists.postgresql.org; Sun, 10 Dec 2023 11:27:34 +0000 Received: from mail-pf1-x435.google.com ([2607:f8b0:4864:20::435]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rCHy7-00BCQm-9g for pgsql-www@lists.postgresql.org; Sun, 10 Dec 2023 11:27:33 +0000 Received: by mail-pf1-x435.google.com with SMTP id d2e1a72fcca58-6ce972ac39dso2222066b3a.3 for ; Sun, 10 Dec 2023 03:27:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hagander.net; s=mail; t=1702207648; x=1702812448; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=47otIKBY0IOdNhwU2aXqkCpJSLASDSdeypdsapXNRKE=; b=er6/Kx6WHNCrH7YDGxi/HEPPBDRR4VZwPivHYxqLcDbYkOrf23iHQjXnGrOuAH5sw2 5bOEVTLO2ayK0RS3uOJ8X89ihqkSwDMXLpAd6fRFV32J6uNRPoyrWKxAwEkSX4HbOIYn rtf6LptAXGLRT1dW8nm1tmeR2oG+yrlHplNwdGVHnwXe5cify+gxZgE++wcJwfVKrtPE 1PVEm+czhMxJhCqlkLoxMTGX34YOcom+gqhjFw2f/gyrsbtKdlxG2ZnNN7pT8fkNsJuR 8UH5pS65bWuuvRpuKe+XSxm506qAFxSeBEvdnh20S0+0rPnI8hh85WRCccXRuxFC48G8 BAAA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702207648; x=1702812448; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=47otIKBY0IOdNhwU2aXqkCpJSLASDSdeypdsapXNRKE=; b=CpkMsfKhs9xMRlW9Zp9pInB3K6S6S7ydH+HVeSH0O72peroKhG+fjvCkrTj3uq8zcu 66J56fzjfnA06eizpxFrd0Ak0sBP5JTZES9tzgzbQ6TihgFyS+5BSY/pQsPrBM02sWl+ /R1BORU9QDKnnH5joVET7woLLjOvLNFPspj1xpTn86v4p3CURfenTvuKGc4PZAKqHzTb 6TTBiptu18odjAKaxMMyS/mQML/Wr30MXmKusN6dqHYw4o8h8AecjxjV1ymDFFqjf0rX 3DxYEm4XMluQY6AiON13rgNgK0Hzso8SWTOLCFzNwPq9LWkWwwrGZrkFUp484Sjxtqb4 EawQ== X-Gm-Message-State: AOJu0Yxa15FYIua2K57fsP9Pav6ZZcLZJzC4rBEJi0YGq0zSoalPrkMa wvgV4Q1NEiulKOLtBQZFwusy0KVAJWpinDEDw1TBSg== X-Google-Smtp-Source: AGHT+IGsieg7xUh6rPhpqjpU1YDCDL8XC/T6ewZ4YbpRL5EXdXou3cTcNXKHYTnzZBnE31HsLvmsGltfrjySZ+J4d24= X-Received: by 2002:a17:90a:cb92:b0:286:c54a:a1fd with SMTP id a18-20020a17090acb9200b00286c54aa1fdmr1025388pju.46.1702207647875; Sun, 10 Dec 2023 03:27:27 -0800 (PST) MIME-Version: 1.0 References: <20230904105958.s45oaei7x3te37e4@alvherre.pgsql> <7fbfadbb-58e6-4e35-83b3-37465f602d11@pgug.de> <95898a5a-db3a-4452-89bf-6d5475376fa8@pgug.de> In-Reply-To: <95898a5a-db3a-4452-89bf-6d5475376fa8@pgug.de> From: Magnus Hagander Date: Sun, 10 Dec 2023 11:31:09 +0100 Message-ID: Subject: Re: New blog - who dis? To: "Andreas 'ads' Scherbaum" Cc: Alvaro Herrera , PostgreSQL WWW , planet Content-Type: multipart/alternative; boundary="0000000000002f95dc060c261a8e" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000002f95dc060c261a8e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Dec 4, 2023, 21:44 Andreas 'ads' Scherbaum wrote: > On 23/11/2023 15:40, Magnus Hagander wrote: > > On Mon, Nov 20, 2023 at 11:44=E2=80=AFPM Andreas 'ads' Scherbaum > wrote: > >> On 11/09/2023 16:09, Magnus Hagander wrote: > >>> On Mon, Sep 11, 2023 at 8:01=E2=80=AFAM Andreas 'ads' Scherbaum > wrote: > >>>> > >>>> On Tue, Sep 5, 2023 at 2:16=E2=80=AFPM Magnus Hagander > wrote: > >>>>> On Mon, Sep 4, 2023 at 2:47=E2=80=AFPM Andreas 'ads' Scherbaum > wrote: > >>>>>> > >>>>>> On Mon, Sep 4, 2023 at 1:00=E2=80=AFPM Alvaro Herrera < > alvherre@alvh.no-ip.org> wrote: > >>>>>>> Hello, > >>>>>>> > >>>>>>> On 2023-Sep-04, Andreas 'ads' Scherbaum wrote: > >>>>>>> > >>>>>>>> I plan to migrate my blog to a new software platform, which > >>>>>>>> will also change the URLs which appear in the RSS feed. There > >>>>>>>> is no convenient way to keep the old URLs in place. > >>>>>>>> > >>>>>>>> Most importantly, this will affect Planet PostgreSQL, which > >>>>>>>> suddenly might see about 150 "new" blog postings. > >>>>>>>> > >>>>>>>> Is there a recommended way how to deal with such a move? > >>>>>>> Each post in the blog has a "guid" unique identifier, which is > usually > >>>>>>> the same as the URL, but some platforms let you set up something > >>>>>>> different. If you can "migrate" your posts to the new platform > while > >>>>>>> keeping the GUIDs, that would be best -- they would not be seen a= s > new > >>>>>>> posts. The actual URLs don't actually matter. > >>>>>> The guid in my case is the full URL of the posting, including the > domain. > >>>>>> I would need to break and fix quite a few things to port this guid > over to > >>>>>> the new system, and I can easily miss something before going live. > >>>>> You wouldn't need to keep the URL for the new posts, only the GUIDs= . > >>>>> That is, new posts could have GUIDs in a new format, old posts coul= d > >>>>> just use the old URL in the GUID and the new URL in the, well, URL. > >>>> That's a theme change which I more or less permanently need to > >>>> maintain. I'd avoid that, if possible. > >>>> > >>>> > >>>>>> I'd rather not go down this path. > >>>>> Strictly speaking, per the RSS requirements, you have to. Not doni= g > >>>>> so will cause reposts for anybody *else* who is tracking your RSS > feed > >>>>> as well, not just Planet PostgreSQL. > >>>> Correct, but I'm mostly worried about spamming Planet. > >>>> > >>>> > >>>>> * No posts older than 7 days will get posted to *twitter*. They onl= y > >>>>> go in the planet RSS feed(s). > >>>>> * The planet RSS feeds contain 30 items. The homepage as well. At > this > >>>>> point you can see this goes back to Aug 24, so not very far. That > >>>>> means that any entries older than that will be ingested into the > >>>>> system, but they won't actually be shown to anybody. > >>>>> * The feed passed through to www.postgresql.org further restricts > this > >>>>> to just the past 10 > >>>>> > >>>>> So this would indicate that if you have a period of say 2 weeks of = no > >>>>> postings, *planet* won't notice. Others might. > >>>> Basically not posting to Planet from this blog for 2-3 weeks, and > maybe > >>>> giving someone a heads-up should do the job? > >>> Yes. Note the date of your last post and keep an eye out on > >>> planet.postgresql.org and make sure that date has "scrolled off the > >>> end". Once it has, and it's >7 days, then you are safe from a planet > >>> perspective. > >> Well, can report that I made sure that the old feed url sends a 301 > >> (permanently moved) to the new feed url. > >> > >> However Planet doesn't like this: > >> > >> Feed returned redirect (http 301) > >> > >> And marks the request as "Failure". > >> > >> Looks like the new feed url must be updated (and then the blog goes in= to > >> review). > > Yeah, this is normal -- planet only autodiscovers redirects to the > > https version of the same one. If you change the contents of the URL, > > it will get sent back for moderation. (For the *RSS* that is - any > > *links* will of course be followed, because that's done by the > > browser) > > What does "the same one" mean? I had a 301 to "the same content" > - aka the feed - in place, and planet complained about the 301. > > That's when I updated the feed url, which then naturally went into > moderation. > The same url. That is if the url changes only in the http to https transition. There can be no other changes in the url, and it doesn't attempt to do any kind of content comparison, just the url. By the way: who does the moderation? > The new URL is still stuck in moderation. > I know at least one person on the (small) team has been unexpectedly unavailable recently due to to a few family emergencies. This has made the review queue even longer than normal, unfortunately. /Magnus > --0000000000002f95dc060c261a8e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Mon, Dec 4, 2023, 21:44 Andreas 'ads' Scher= baum <ads@pgug.de> wrote:
On 23/11/2023 15:40, Magnus Hagander wrote:=
> On Mon, Nov 20, 2023 at 11:44=E2=80=AFPM Andreas 'ads' Scherba= um <= ads@pgug.de> wrote:
>> On 11/09/2023 16:09, Magnus Hagander wrote:
>>> On Mon, Sep 11, 2023 at 8:01=E2=80=AFAM Andreas 'ads' = Scherbaum <ads@pgug.de> wrote:
>>>>
>>>> On Tue, Sep 5, 2023 at 2:16=E2=80=AFPM Magnus Hagander <= ;magnus@hagander.net> wrote:
>>>>> On Mon, Sep 4, 2023 at 2:47=E2=80=AFPM Andreas 'ad= s' Scherbaum <ads@pgug.de> wrote:
>>>>>>
>>>>>> On Mon, Sep 4, 2023 at 1:00=E2=80=AFPM Alvaro Herr= era <alvherre@alvh.no-ip.org> wrote:
>>>>>>> Hello,
>>>>>>>
>>>>>>> On 2023-Sep-04, Andreas 'ads' Scherbau= m wrote:
>>>>>>>
>>>>>>>> I plan to migrate my blog to a new softwar= e platform, which
>>>>>>>> will also change the URLs which appear in = the RSS feed. There
>>>>>>>> is no convenient way to keep the old URLs = in place.
>>>>>>>>
>>>>>>>> Most importantly, this will affect Planet = PostgreSQL, which
>>>>>>>> suddenly might see about 150 "new&quo= t; blog postings.
>>>>>>>>
>>>>>>>> Is there a recommended way how to deal wit= h such a move?
>>>>>>> Each post in the blog has a "guid" u= nique identifier, which is usually
>>>>>>> the same as the URL, but some platforms let yo= u set up something
>>>>>>> different.=C2=A0 If you can "migrate"= ; your posts to the new platform while
>>>>>>> keeping the GUIDs, that would be best -- they = would not be seen as new
>>>>>>> posts.=C2=A0 The actual URLs don't actuall= y matter.
>>>>>> The guid in my case is the full URL of the posting= , including the domain.
>>>>>> I would need to break and fix quite a few things t= o port this guid over to
>>>>>> the new system, and I can easily miss something be= fore going live.
>>>>> You wouldn't need to keep the URL for the new post= s, only the GUIDs.
>>>>> That is, new posts could have GUIDs in a new format, o= ld posts could
>>>>> just use the old URL in the GUID and the new URL in th= e, well, URL.
>>>> That's a theme change which I more or less permanently= need to
>>>> maintain. I'd avoid that, if possible.
>>>>
>>>>
>>>>>> I'd rather not go down this path.
>>>>> Strictly speaking, per the RSS requirements, you have = to.=C2=A0 Not donig
>>>>> so will cause reposts for anybody *else* who is tracki= ng your RSS feed
>>>>> as well, not just Planet PostgreSQL.
>>>> Correct, but I'm mostly worried about spamming Planet.=
>>>>
>>>>
>>>>> * No posts older than 7 days will get posted to *twitt= er*. They only
>>>>> go in the planet RSS feed(s).
>>>>> * The planet RSS feeds contain 30 items. The homepage = as well. At this
>>>>> point you can see this goes back to Aug 24, so not ver= y far. That
>>>>> means that any entries older than that will be ingeste= d into the
>>>>> system, but they won't actually be shown to anybod= y.
>>>>> * The feed passed through to www.postgresql= .org further restricts this
>>>>> to just the past 10
>>>>>
>>>>> So this would indicate that if you have a period of sa= y 2 weeks of no
>>>>> postings, *planet* won't notice. Others might.
>>>> Basically not posting to Planet from this blog for 2-3 wee= ks, and maybe
>>>> giving someone a heads-up should do the job?
>>> Yes. Note the date of your last post and keep an eye out on >>> planet.postgresql.org and make sure that dat= e has "scrolled off the
>>> end". Once it has, and it's >7 days, then you are = safe from a planet
>>> perspective.
>> Well, can report that I made sure that the old feed url sends a 30= 1
>> (permanently moved) to the new feed url.
>>
>> However Planet doesn't like this:
>>
>> Feed returned redirect (http 301)
>>
>> And marks the request as "Failure".
>>
>> Looks like the new feed url must be updated (and then the blog goe= s into
>> review).
> Yeah, this is normal -- planet only autodiscovers redirects to the
> https version of the same one. If you change the contents of the URL,<= br> > it will get sent back for moderation. (For the *RSS* that is - any
> *links* will of course be followed, because that's done by the
> browser)

What does "the same one" mean? I had a 301 to "the same cont= ent"
- aka the feed - in place, and planet complained about the 301.

That's when I updated the feed url, which then naturally went into
moderation.

The same url. That is if the url changes only in the http to htt= ps transition. There can be no other changes in the url, and it doesn't= attempt to do any kind of content comparison, just the url.=C2=A0



=
By the way: who does the moderation?
The new URL is still stuck in moderation.


I know= at least one person on the (small) team has been unexpectedly unavailable = recently due to to a few family emergencies. This has made the review queue= even longer than normal, unfortunately.=C2=A0

<= /div>
/Magnus=C2=A0
--0000000000002f95dc060c261a8e--