On 11/30/2016 04:52 PM, Peter Eisentraut wrote:
On 11/27/16 8:37 AM, Magnus Hagander wrote:
Ok, we now have it. https://postgr.es/m/messageid will redirect to that
messageid in the main archives.

I like the idea of recording the location of the discussion, but I'm not
fond of the URL shortener.  Besides the general problem that URL
shortening looks ugly and fake, it fragments the way we address things.
Ideally, message IDs should tie together our main development tools:
email, commit fest app, web site, and commits.  If we use different
addresses in each of them, it will be confusing and harder to tie things
together.  For example, I would ideally like to just paste the thread
URL from the commit fest app into the commit message.  If I have to
manually shorten the URL, then that is error prone and less interesting
to do.  Also, the commit fest app links to a thread, not a message.
Another concern is how search engines will process this.

Agreed. I just did my first commit with the shortened URL, and I didn't like it. If we want to use URLs, let's use the canonical https://www.postgresql.org/message-id/<message-id> format.

Do we know of an actual length limit that is useful to aim for?  If we
just make it just a bit shorter but it's still too long for a large
class of email readers, depending on the message ID format, then it's
not that useful.

Right, we can't control the length of the URL, because it contains the message-id, which can be arbitrarily long.

- Heikki

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to