Message ID Disclaimer

[Roy Schestowitz]

To add context to this message (for the sake of others who will skimp it),
message-id.net is a little tool that Toby set up in order for people to
refer to UseNet threads rather easily. For example, I have just referred
someone to http://message-id.net/[email protected] , which
conveniently enough, has a simple and clean structure.

However, doesn't that 'scrape' Google content in the sense that it
encapsulates it in a frame? I do not want to 'spread' many such addresses
all over UseNet if it will draw the wrath of Google (my name is bound to
these posts). Can you please comment or add a site disclaimer?

Ta,

Roy

 

[Toby Inkster]

However, doesn't that 'scrape' Google content in the sense that it
encapsulates it in a frame?

http://images.google.com/imgres?img...=25&hl=en&hs=U6Z&lr=&client=opera&rls=en&sa=N

 

[Roy Schestowitz]

__/ [Toby Inkster] on Thursday 01 September 2005 21:14 \__

http://images.google.com/imgres?imgurl...URL

Yes, I know. I even mentioned this before, remember? *smile*

Either way, I am happy to have discovered your stance on the issue. As far
as I can recall, you only acted unaware with a wise answer like "PageRank
propagation? Really?".

It will not prevent me from spreading yet more message-id's around the Net.
I hope you can enhance some of the features though, e.g.

o allow a tinyurl/snipurl/makeaurlshort type-of-service to be used at the
front page. It would be nice to construct even smaller aliases without
departing from message-id.net, e.g. message-id.net/&000001 (not secure, but
just an example) pointing to
http://message-id.net/[email protected] .

Roy

 

[Toby Inkster]

allow a tinyurl/snipurl/makeaurlshort type-of-service to be used at the
front page.

I have actually been thinking along those lines.

Though not using random numbers like:

http://message-id.net/3463456345

but more like:

http://message-id.net/*alt_www_webmaster_faq

Not sure about the asterisk there. Needs to be some character which is
invalid as part of a Message-ID header, but valid in URLs.

 

[Els]

http://message-id.net/*alt_www_webmaster_faq

Not sure about the asterisk there. Needs to be some character which is
invalid as part of a Message-ID header, but valid in URLs.

Question- or exclamation mark?
Plus?

 

[Roy Schestowitz]

__/ [Toby Inkster] on Friday 02 September 2005 08:47 \__

I have actually been thinking along those lines.

Though not using random numbers like:

http://message-id.net/3463456345

but more like:

http://message-id.net/*alt_www_webmaster_faq

Not sure about the asterisk there. Needs to be some character which is
invalid as part of a Message-ID header, but valid in URLs.

Does "alt_www_webmaster_faq" correspond to a subject line, as in a slug? If
so, you need to make sure duplicates are prevented (re-use from WordPress
slug assignment). Perhaps starting with something more shallow and
fundamental would be good. _However_, make sure you do not break older
links if/when the conventions change. Maybe just retain a flexible table
(not worrying about lookup efficiency for the time being) and accommodate
it with aliases.

One thing you could also do, for example, is rely on query speed in mySQL
and just toss aliases at it, e.g. ADD to $table VALUES $slug $address $date

You then just write a few scripts (or script) that can simply pull out the
physical (well, not truly /physical/) address and redirect to it. It should
all be transparent to the user.

Roy

 

[Toby Inkster]

_However_, make sure you do not break older links if/when the
conventions change.

Hence the asterisk (or some other character that will do the job). It's
not valid in a real Message-ID, so any URLs that start with
"http://message-id.net/*" will be assumed to be aliases.

One thing you could also do, for example, is rely on query speed in
mySQL and just toss aliases at it, e.g. ADD to $table VALUES $slug
$address $date

MySQL? No, ta. PostgreSQL with suitable indexing.