Comments on: Outreach Mission http://libertini.net/libertus Mature, refined and elegant. Almost, but not entirely unlike the geek equivalent of a good wine. Mon, 13 Apr 2009 08:18:18 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Libertus http://libertini.net/libertus/outreach/comment-page-1/#comment-460 Libertus Fri, 02 Jun 2006 19:59:08 +0000 http://www.libertini.net/libertus/outreach/#comment-460 I've been thinking for a while about how to extend the reach my Outreach search links to the websites they eventually link. At the moment, the HTTP referer is Google search, not here. <strong>Mental note:</strong> Add something like -site:www.libertini.net/libertus as a search term. That will hopefully appear in their incoming weblogs and have a beneficial effect on the search - it won't link back! <ins datetime="2006-07-08T08:18:18+00:00"><a href="/libertus/2006/07/07/developing-outreach-2/#post-304" rel="nofollow">Update</a></ins> I've settled on "-site:$post_permalink_without_scheme", which Google will hopefully NOOP internally but pass on in its referral query string, to be picked up by the link endpoint. Access log analysis programs may list the term but are unlikely to understand its meaning. It's subtle but it is also important. The link endpoint should know that the incoming search phrase was not typed into Google <i>ad hoc</i>. I’ve been thinking for a while about how to extend the reach my Outreach search links to the websites they eventually link. At the moment, the HTTP referer is Google search, not here. Mental note: Add something like -site:www.libertini.net/libertus as a search term. That will hopefully appear in their incoming weblogs and have a beneficial effect on the search – it won’t link back!

Update
I’ve settled on “-site:$post_permalink_without_scheme”, which Google will hopefully NOOP internally but pass on in its referral query string, to be picked up by the link endpoint. Access log analysis programs may list the term but are unlikely to understand its meaning. It’s subtle but it is also important. The link endpoint should know that the incoming search phrase was not typed into Google ad hoc.

]]> By: Libertus http://libertini.net/libertus/outreach/comment-page-1/#comment-459 Libertus Fri, 24 Feb 2006 18:30:23 +0000 http://www.libertini.net/libertus/outreach/#comment-459 Daniel! Welcome! You are my first, ever commenter on the Outreach Mission. I shall remember you forever! And you express yourself with <i>style</i>. How delightful. I gave a lot of thought to <code>cite</code>, knowing there was an existing use in XHTML. In fact, I studied the existing use quite extensively before deciding to adopt it. As with XHTML, my <code>cite</code> attribute expresses a citation of some kind, specific to the tag being used. With all my tags, the <code>cite</code> attribute should be omitted if the tagged text is also the citation. Citations are not URIs, except for <code><is:uri></code>. If a URI reference is needed when using the other tags, it is specified by the <code>from</code> attribute. Daniel! Welcome! You are my first, ever commenter on the Outreach Mission. I shall remember you forever! And you express yourself with style. How delightful.

I gave a lot of thought to cite, knowing there was an existing use in XHTML. In fact, I studied the existing use quite extensively before deciding to adopt it. As with XHTML, my cite attribute expresses a citation of some kind, specific to the tag being used.

With all my tags, the cite attribute should be omitted if the tagged text is also the citation. Citations are not URIs, except for <is:uri>. If a URI reference is needed when using the other tags, it is specified by the from attribute.

]]> By: Daniel Schierbeck http://libertini.net/libertus/outreach/comment-page-1/#comment-458 Daniel Schierbeck Fri, 24 Feb 2006 16:41:57 +0000 http://www.libertini.net/libertus/outreach/#comment-458 The <code>@cite</code> attribute is different from the one in <abbr title="Extensible HyperText Markup Language">XHTML</abbr> - have you considered using an <abbr title="Uniform Resource Identifier">URI</abbr> instead? The @cite attribute is different from the one in XHTML – have you considered using an URI instead?

]]>