Comments on: Google Blog Search https://www.lafferty.ca/2005/09/14/google-blog-search/ Rich Lafferty's OLD blog Sun, 11 Feb 2007 18:55:40 +0000 hourly 1 https://wordpress.org/?v=5.9.2 By: substitute https://www.lafferty.ca/2005/09/14/google-blog-search/comment-page-1/#comment-2057 Wed, 14 Sep 2005 23:29:55 +0000 #comment-2057 Does updates.sixapart.com also provide feeds if someone has checked the preference to block search spiders? I’ve seen some (unverified) complaints by people who found their LJs on the google blog search when they thought they’d blocked Google by denying robots. The mechanism for supplying the data is entirely different, of course, but I expect many people will have assumed that their preference carried forward to this newer setup.

]]>
By: substitute https://www.lafferty.ca/2005/09/14/google-blog-search/comment-page-1/#comment-2056 Wed, 14 Sep 2005 21:03:43 +0000 #comment-2056 …and 30 seconds later I discover that someone with a ukulele blog on MSN republished my Lysenko piece. Yao.

]]>
By: dossy https://www.lafferty.ca/2005/09/14/google-blog-search/comment-page-1/#comment-2055 Wed, 14 Sep 2005 19:30:58 +0000 #comment-2055 Now, cool would be being able to add Google (which happens to belong to someone already, pfft!) to your LJ Friends list, which would in turn allow the Googlebot to spider your Friends-locked entries for searching. Google’s search results obviously shouldn’t show an excerpt for these particular entries in the overall results, nor allow folks to view a cached version of the page … but at least provide a means of getting the entries into your search results.

]]>
By: Rich https://www.lafferty.ca/2005/09/14/google-blog-search/comment-page-1/#comment-2054 Wed, 14 Sep 2005 19:25:40 +0000 #comment-2054 Oh hey, that’s a good idea. I just stuck it on my userinfo. I suppose the ideal way would be to integrate it into the style somehow. I really should get around to picking up S2.

]]>
By: Rich https://www.lafferty.ca/2005/09/14/google-blog-search/comment-page-1/#comment-2053 Wed, 14 Sep 2005 19:22:45 +0000 #comment-2053 Ah, that makes sense. Was Google one of the ones you wrote the push feed thingy for?

A user preference to choose between publishing the domain-alias URL, paid user URL, or free user URL would be neat, though. I suppose all I’d need to do is ping weblogs.com with a domain-alias URL whenever I posted and it wouldn’t know that it wasn’t LJ, though. (If I used the domain-alias feature for something other than a livegerbil.com URL, of course.)

]]>
By: brad https://www.lafferty.ca/2005/09/14/google-blog-search/comment-page-1/#comment-2052 Wed, 14 Sep 2005 19:08:59 +0000 #comment-2052 Probably because that’s all we advertise here:

http://updates.sixapart.com/

]]>
By: sachmet https://www.lafferty.ca/2005/09/14/google-blog-search/comment-page-1/#comment-2051 Wed, 14 Sep 2005 18:59:42 +0000 #comment-2051 I stole this and made it a “backdated” post for December 31, 2037 at 23:59 (the last date/time combo LJ currently accepts), so that it’s always the first post for people looking at my journal but doesn’t show up in friends view.

Thanks for this!

]]>
By: Rich https://www.lafferty.ca/2005/09/14/google-blog-search/comment-page-1/#comment-2050 Wed, 14 Sep 2005 18:29:16 +0000 #comment-2050 Ah, no, I stand corrected — they are using feeds, not spidering. It’s too bad they can’t just integrate their existing non-bloggy index for older posts.

]]>
By: Rich https://www.lafferty.ca/2005/09/14/google-blog-search/comment-page-1/#comment-2049 Wed, 14 Sep 2005 18:27:31 +0000 #comment-2049 I can’t tell from their about page if they’re getting feeds or if they’re spidering. This certainly would mesh with what Brad mentioned in the post where he talked about the stream you’re using there, though, about companies asking for pings for all entries.

]]>
By: node https://www.lafferty.ca/2005/09/14/google-blog-search/comment-page-1/#comment-2046 Wed, 14 Sep 2005 18:15:29 +0000 #comment-2046 The funny thing is I wrote this just yesterday. It’s not obsolete…yet. Google certainly has the processing power to parse all the articles for keyword searches on their servers.

It uses a lot of bandwidth, though. I ran it from 7:35 to 9:35 Pacific this morning, and it used almost 30MB of bandwidth. It’ll go up as more North Americans wake up and start posting.

]]>