public inbox for [email protected]
help / color / mirror / Atom feedFrom: Magnus Hagander <[email protected]>
To: Andreas 'ads' Scherbaum <[email protected]>
Cc: Alvaro Herrera <[email protected]>
Cc: [email protected]
Cc: [email protected]
Subject: Re: New blog - who dis?
Date: Mon, 11 Sep 2023 16:09:07 +0200
Message-ID: <CABUevEy1HN523TEs8Ts-E21Uzux3pGf=qv0VwceomdyrYcEEZQ@mail.gmail.com> (raw)
In-Reply-To: <CAMDzVO9+GpT=Ebdj4s1TJWcxehJsWb7ev2nhqBgL1f9=_kTy8Q@mail.gmail.com>
References: <CAMDzVO9mer4V8OON7KhynDwE267oZr6BiF-9=gc22dzLmsxWDw@mail.gmail.com>
<[email protected]>
<CAMDzVO9do0WroHM-Mto3gmYbHUVE6LncpRONZc=1-m0=uVQbtg@mail.gmail.com>
<CABUevEwWY4jnvOrbKyVQ4g8gwLExdPaiG3Z69EYbrEsOje_wTw@mail.gmail.com>
<CAMDzVO9+GpT=Ebdj4s1TJWcxehJsWb7ev2nhqBgL1f9=_kTy8Q@mail.gmail.com>
On Mon, Sep 11, 2023 at 8:01 AM Andreas 'ads' Scherbaum <[email protected]> wrote:
>
>
>
> On Tue, Sep 5, 2023 at 2:16 PM Magnus Hagander <[email protected]> wrote:
>>
>> On Mon, Sep 4, 2023 at 2:47 PM Andreas 'ads' Scherbaum <[email protected]> wrote:
>> >
>> >
>> >
>> > On Mon, Sep 4, 2023 at 1:00 PM Alvaro Herrera <[email protected]> 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 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 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?
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.
//Magnus
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: New blog - who dis?
In-Reply-To: <CABUevEy1HN523TEs8Ts-E21Uzux3pGf=qv0VwceomdyrYcEEZQ@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox