Feedback-ID: ia2694551:Fastmail
Date: Mon, 4 Sep 2023 12:59:58 +0200
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Andreas 'ads' Scherbaum <ads@pgug.de>
Cc: pgsql-www@lists.postgresql.org, planet@postgresql.org
Subject: Re: New blog - who dis?
Message-ID: <20230904105958.s45oaei7x3te37e4@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CAMDzVO9mer4V8OON7KhynDwE267oZr6BiF-9=gc22dzLmsxWDw@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/20230904105958.s45oaei7x3te37e4%40alvherre.pgsql>
Precedence: bulk

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.

If your platform doesn't let you do this, I think PlanetPostgres would
mark the new posts as hidden anyway, because of the volume (but pester
everyone along the way).  That way only future new posts (actually new
posts) would be syndicated, but everything would appear duplicate in the
admin interface.

> Did someone do such a move before, what is your experience?

It's usually a pretty noisy things to do, from the moderators point of
view.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/