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 1qfZzM-00C8um-JG for pgsql-www@arkaria.postgresql.org; Mon, 11 Sep 2023 06:01:37 +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 1qfZzK-00Deu0-Mr for pgsql-www@arkaria.postgresql.org; Mon, 11 Sep 2023 06:01:34 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qfZzK-00Detc-8A for pgsql-www@lists.postgresql.org; Mon, 11 Sep 2023 06:01:34 +0000 Received: from mail-pf1-x436.google.com ([2607:f8b0:4864:20::436]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qfZzF-003ua7-4N for pgsql-www@lists.postgresql.org; Mon, 11 Sep 2023 06:01:32 +0000 Received: by mail-pf1-x436.google.com with SMTP id d2e1a72fcca58-68a440a8a20so3899526b3a.3 for ; Sun, 10 Sep 2023 23:01:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgug.de; s=google; t=1694412088; x=1695016888; 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=gJx310JMGdxJFE/pSiaJVxIe06HFKaAvWuNn/OvgDew=; b=ZzYMqIM+8+QGZfapAbjNq7BAsPb5YHt+0ywoX99juEaOzvQ4H3wmh8Epkt5c0wYexy UQKPLz53Utb3c8ag14QCBZgfi8G/y7TrcwiyxSpX5i/OBGL6XbO4gk29/VhE+vbC048R 7wNhLLxzWNA6U9OsPV5XiWtObuxNwsn5r9/Z+7d2QQDAW6ntsbd/xEDXJdfTipyCRcqm qTTZHb/QMAV07hwkZfEKkEq2NO35WKdAigKhzZyFVtO8v4fU933MgCnDCS53S+I4gMtf oSC6OIhVyr35yV5RAfcDp4pHueTVcvaEKb8RIh3LcuoJGS4j+6dCMYKUQSlD/Rqiqd62 Bsag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694412088; x=1695016888; 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=gJx310JMGdxJFE/pSiaJVxIe06HFKaAvWuNn/OvgDew=; b=Z8mBpOBOJyyXC4iGDEkQ1Yd6WmYW8KCYbLdSGwBf4YV8Ob7fLA/rVCzHo5gltHdgho ZyjSf5rf1MVlYxay6BDm3UegDI31gT3MwdpAPhU9nGhJ8Mi9ktTvNCyvyP/BeJZcWtq7 j+U7f7LBw/OvFCnY03Hq3hih3GSy1Xib5HHIXY4wUPPYx9BvOL5fFibTyywRjh8NGYto xOcnDu3+vIwcMz6rgLq7kDV0NJr4qXovHo6jWhAIU+XAvOc2ZpAJ3SEgXoCcWWCwjKfd Ww6aMTsC2kmDPbzC2ppJ7lwB42OmfK7kaUEHYvOt+GazQE0IB93PNXurzFNz4YUEhDnH GP+Q== X-Gm-Message-State: AOJu0Yys01htn/E4e5KHQ6TpJERpfJTstCh2040BtgFq52cum1krPFjN XUlnGrgYSpEFMlRucOO56wVxTN7gsT35U9CJiDeg8w== X-Google-Smtp-Source: AGHT+IFBezJDbEQMgyRzo9EuMf7T50mQux+EiKyX1xfdEjPsm4Lrp520ilcmRIibUMUSCgZ3OZmk/avKq7otDhT151Y= X-Received: by 2002:a05:6a20:9383:b0:12c:2dc7:74bc with SMTP id x3-20020a056a20938300b0012c2dc774bcmr12029741pzh.46.1694412087615; Sun, 10 Sep 2023 23:01:27 -0700 (PDT) MIME-Version: 1.0 References: <20230904105958.s45oaei7x3te37e4@alvherre.pgsql> In-Reply-To: From: "Andreas 'ads' Scherbaum" Date: Mon, 11 Sep 2023 08:00:00 +0200 Message-ID: Subject: Re: New blog - who dis? To: Magnus Hagander Cc: Alvaro Herrera , pgsql-www@lists.postgresql.org, planet@postgresql.org Content-Type: multipart/alternative; boundary="00000000000096688a06050f0e33" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000096688a06050f0e33 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 > 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 as new > >> posts. The actual URLs don't actually matter. > > > > > > The guid in my case is the full URL of the posting, including the domai= n. > > 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 could > 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 donig > 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 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 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? Regards, --=20 Andreas 'ads' Scherbaum German PostgreSQL User Group European PostgreSQL User Group - Board of Directors Volunteer Regional Contact, Germany - PostgreSQL Project --00000000000096688a06050f0e33 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Tue, Sep 5, 2023 at 2:16=E2=80=AFP= M Magnus Hagander <magnus@hagande= r.net> wrote:
On Mon, Sep 4, 2023 at 2:47=E2=80=AFPM Andreas 'ads' Scherbaum= <ads@pgug.de> w= rote:
>
>
>
> 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, wh= ich is usually
>> the same as the URL, but some platforms let you 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 actually matter.
>
>
> The guid in my case is the full URL of the posting, including the doma= in.
> I would need to break and fix quite a few things to port this guid ove= r 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 could
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.

=C2=A0
> 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 tracking your RSS feed
as well, not just Planet PostgreSQL.

Co= rrect, but I'm mostly worried about spamming Planet.

=

* No posts older than 7 days will get posted to *twitter*. 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 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<= br> 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, a= nd maybe
giving someone a heads-up should do the job?


Regards,

--
Andreas 'ads' Scherbaum
German PostgreSQL User Group=
European PostgreSQL User Group - Board of Directors
Volunteer Region= al Contact, Germany - PostgreSQL Project
--00000000000096688a06050f0e33--