Sunday, July 01, 2007
Gordon's Tech: Now serving on tech.kateva.org
The url for this blog is now tech.kateva.org, but you you shouldn't have to do anything. If you're reading this your reader has navigated the 301 redirect. If the url doesn't correct itself automatically you may want to change it manually, but then, of course, you probably can't read this.
Site change pending: the 301 redirect didn't work!
[This has been updated from the original. I was optimistic the 301 redirect would mean that feed readers would find the new feed, but neither Bloglines nor Google Reader did.]
I'm going to move this blog to a new google apps domain, but the feed will still be managed by Google/Blogger. You shouldn't won't have to do anything, because:
The main side-effect of the move will be that the last 10 posts will be treated as "new". I've written a bit about how the move is accomplished previously.
The new site, kateva.org, has its own "main page" and will eventually hold two blogs, this tech blog and my "everything else" blog. The urls for the pages will eventually be:
I've two reasons to make the move. One is to get away from the whimsical URLs I chose to play with years ago, the other is to move my pseudonymous identify (John Gordon) a few degrees away from my "true name" (John xxxxxxxx).
More after the move ...
Update 7/1/07: After 14 hours neither Google Reader nor Bloglines have updated pre-existing subscriptions. Yech. You should update manually if you can read this. Google Groups Help discussion here.
Update 7/2/07: The Blogger help group samaritans found that Blogger is returning a true 301 redirect, so the fault seems to lie with Bloglines ...
Update 7/3/07: I've not heard anything from Bloglines tech support. One clue might be that the pattern of the Blogger feed has changed:
Update 7/3/07: Bloglines may be absolved! Google uses a different syntax for RSS feeds on custom domain vs. traditional blogger. It appears the 301 redirect only changes the domain, so a subscription that references the RSS feed will break during a transition and cannot be updated.
I'm going to move this blog to a new google apps domain, but the feed will still be managed by Google/Blogger. You shouldn't won't have to do anything, because:
- Google will do a URL redirect indefinitely.
- The specific URL redirect is a "301 redirect", meaning a permanent move. Many feed readers will automatically update their feeds, even though the old feed address will continue to work. The update will take a few minutes to occur.
The main side-effect of the move will be that the last 10 posts will be treated as "new". I've written a bit about how the move is accomplished previously.
The new site, kateva.org, has its own "main page" and will eventually hold two blogs, this tech blog and my "everything else" blog. The urls for the pages will eventually be:
- Gordon's Tech: googlefaughnan.blogspot.com will become tech.kateva.org (today)
- Gordon's Notes: jfaughnan.blogspot.com will become notes.kateva.org (in a week or so)
I've two reasons to make the move. One is to get away from the whimsical URLs I chose to play with years ago, the other is to move my pseudonymous identify (John Gordon) a few degrees away from my "true name" (John xxxxxxxx).
More after the move ...
Update 7/1/07: After 14 hours neither Google Reader nor Bloglines have updated pre-existing subscriptions. Yech. You should update manually if you can read this. Google Groups Help discussion here.
Update 7/2/07: The Blogger help group samaritans found that Blogger is returning a true 301 redirect, so the fault seems to lie with Bloglines ...
Update 7/3/07: I've not heard anything from Bloglines tech support. One clue might be that the pattern of the Blogger feed has changed:
- old: http://googlefaughnan.blogspot.com/rss/googlefaughnan.xml
- new: http://tech.kateva.org/feeds/posts/default?alt=rss
7/2/2007 18:58:21 Trying http://googlefaughnan.blogspot.comI'm going to try the redirect using some tools suggested on the Blogger group and see what happens when I try to hit the old url directly.
Redirect!
Header:
HTTP/1.0 301 Moved Permanently
Location: http://tech.kateva.org/
Content-Type: text/html; charset=UTF-8
Cache-control: private
Content-Length: 205
Date: Tue, 03 Jul 2007 01:57:37 GMT
Server: GFE/1.3
Connection: Keep-Alive
Update 7/3/07: Bloglines may be absolved! Google uses a different syntax for RSS feeds on custom domain vs. traditional blogger. It appears the 301 redirect only changes the domain, so a subscription that references the RSS feed will break during a transition and cannot be updated.
Repairing and replacing an old iBook keyboard
Our dual USB white G3 iBook, somehow, lives on. The hinge s broken, so we never close it. When we move it, we carry it open. (I try to put it to sleep first, but sometimes the drive is spinning. It survives.) We replaced it with a MacBook last fall, but it lives on as the kitchen web client and family slideshow server. The location, setup, and low care requirement means it's still heavily used.
Thanks to some manuals I downloaded from the superb PowerBookMedic site I was able to replace the dislodged shift key and install the keyboard; so far it works though one top tab didn't quite fit and I had to press in the side where it had been kinked. In any case it's firmly in place.
Next time though I'll go with either PowerBookMedic or iFixit.com; I owe them for the excellent repair books they provide. I recommend downloading the one that fits your laptop and keeping it at hand.
Update 7/18/07: Mac Recycling (macrecycling.com) did not respond to the message I left on their web site. Email isn't as reliable as it once was, so there's a 10% chance they're not crooks. Unfortunately, there's a 90% chance they are crooks. Don't have anything to do with them.
Recently, the "L" key broke. Happily there are several places to buy keys and attachment mechanisms for prices ranging from $5 (refurb key, probably just fine) to $9 (key and hinge) to $20 (key and hinge, never used, Apple) to varying prices up to $100 + shipping for a new keyboard. I opted for a used keyboard for $26 (incl. shipping) from Mac Recycling (see update)...
I chose the used keyboard option since the old one is a real mess, infested with generations of dog hair and varied unmentionables. I'm sure other keys are going to break. If the replacement kb works I'll have a supply of two of each keys, excepting the "L" key of course. A wonderfully obsessive web page tells us how to disassemble and clean an iBook's keyboard, so I feel reasonably prepared. (A few days later the site disappeared! This alternate guide is excellent.)
The prices per key do explain why even broken iBooks have some value to resellers. It's a real win-win; I'm quite happy to pay $5 for a working refurbished key and that means an old but relatively clean iBook keyboard is worth something. When this machine finally dies, (lord knows when, it seems it might go on for years) I'll cast around to see if anyone wants to pay shipping fees to get the relic and its working Airport card.
Update 7/7/07: The Mac Recycling (macrecycling.com) keyboard arrived with one key off and a kink in one side. I was angry at first, figuring they'd sent me a bum keyboard. On closer inspection though I see that the FedEx shipped box is creased along one edge. I think the keyboard was probably fine when it left Mac Recycling, but they might have done a better job packing it.Thanks to some manuals I downloaded from the superb PowerBookMedic site I was able to replace the dislodged shift key and install the keyboard; so far it works though one top tab didn't quite fit and I had to press in the side where it had been kinked. In any case it's firmly in place.
Next time though I'll go with either PowerBookMedic or iFixit.com; I owe them for the excellent repair books they provide. I recommend downloading the one that fits your laptop and keeping it at hand.
Update 7/18/07: Mac Recycling (macrecycling.com) did not respond to the message I left on their web site. Email isn't as reliable as it once was, so there's a 10% chance they're not crooks. Unfortunately, there's a 90% chance they are crooks. Don't have anything to do with them.
How Bloglines or Google Reader could (does?) handle comment tracking
This idea is a freebie, anyone can use it. (It's not patentable though, since I just wrote about it here, and for one other reason described below.)
Weblog comments don't fit the current syndication model. Most blogs don't support subscribing to a specific post's comment feed, and even if they did the overhead of creating and tracking such transient feeds doesn't scale.
Email notification of new comments is occasionally supported, but I'm trying to shrink my email, not grow it. Still, email is the right approach -- if it were integrated with a blog reader. Bloglines and Google Reader could manage the integration.
Here's the simplest version of the approach, using Bloglines as an example.
Here's the funny bit. Bloglines does this now, but they don't describe its use for subscribing to comments. They provide it as a throwaway email address to use with vendors and other unsavory correspondents. I discovered they had this feature by accident as I was composing this blog post and looking up the term they use for their feed trackers ("subscription", of course).
If they provided a bit of guidance on how to use it, they'd get more use. The only problem with their current implementation is that the randomly generated addresses cannot be remembered. I've implemented a redirect from one of my domains so I have memorable transient addresses, but Bloglines needs to allow us to specify the email address of the form "jfaughnan.____@bloglines.com.
Update 7/1/07: This works pretty well. I have a few google app domains, so I created a user on one of them to support this process. I then gave that user a Gmail Nickname, a relatively new Gmail feature that allows one to create and destroy public identities as needed while somewhat shielding one's private identity. The Gmail nickname is the key. It's memorable, and disposable. The Gmail nickname redirects to the special purpose user, which keeps the notifications in the inbox (why not?) while forwarding to the disposable but not memorable bloglines notifier address.
This redirect, combined with Bloglines email service, gives me the comment notification functionality I'm seeking. Of course it only works with blog services that support email notification for comments, but if this catches on more of them will. Note that everything in this chain is disposable, but the first line of defense is the Gmail nickname. When that's discovered by spammers it's trivial to change (I used an incrementing number for now).
Of course this is way too complex for anyone but an insane geek who lives constantly with redirection, but Bloglines could implement all this by allowing users to create memorable but disposable "nicknames" for their Bloglines subscription, or simply let users specify the personalized subscription address.
Weblog comments don't fit the current syndication model. Most blogs don't support subscribing to a specific post's comment feed, and even if they did the overhead of creating and tracking such transient feeds doesn't scale.
Email notification of new comments is occasionally supported, but I'm trying to shrink my email, not grow it. Still, email is the right approach -- if it were integrated with a blog reader. Bloglines and Google Reader could manage the integration.
Here's the simplest version of the approach, using Bloglines as an example.
- My bloglines account has a new "subscription" called "Comments Subscription". It also provides me with an email address corresponding to that subscription. I can change that email address any time I want. For example: jfaughnan.gwyt8ytt@bloglines.com
- I enter that email address into blogs that support email notification of comments. Then I get notification via my feed reader. Notifications include links to the blog comments section.
- When I start getting spam, I throw away the email address and get another.
Here's the funny bit. Bloglines does this now, but they don't describe its use for subscribing to comments. They provide it as a throwaway email address to use with vendors and other unsavory correspondents. I discovered they had this feature by accident as I was composing this blog post and looking up the term they use for their feed trackers ("subscription", of course).
If they provided a bit of guidance on how to use it, they'd get more use. The only problem with their current implementation is that the randomly generated addresses cannot be remembered. I've implemented a redirect from one of my domains so I have memorable transient addresses, but Bloglines needs to allow us to specify the email address of the form "jfaughnan.____@bloglines.com.
Update 7/1/07: This works pretty well. I have a few google app domains, so I created a user on one of them to support this process. I then gave that user a Gmail Nickname, a relatively new Gmail feature that allows one to create and destroy public identities as needed while somewhat shielding one's private identity. The Gmail nickname is the key. It's memorable, and disposable. The Gmail nickname redirects to the special purpose user, which keeps the notifications in the inbox (why not?) while forwarding to the disposable but not memorable bloglines notifier address.
This redirect, combined with Bloglines email service, gives me the comment notification functionality I'm seeking. Of course it only works with blog services that support email notification for comments, but if this catches on more of them will. Note that everything in this chain is disposable, but the first line of defense is the Gmail nickname. When that's discovered by spammers it's trivial to change (I used an incrementing number for now).
Of course this is way too complex for anyone but an insane geek who lives constantly with redirection, but Bloglines could implement all this by allowing users to create memorable but disposable "nicknames" for their Bloglines subscription, or simply let users specify the personalized subscription address.
Saturday, June 30, 2007
How to move a cellphone number that doesn't want to move
Desperation is the mother of invention. The person who came up with this hack for migrating a "stuck" cellphone number from one service to another developed a mental model of the underlying database problem, and hacked a workaround: "AppleInsider | How to port 'ineligible' mobile numbers to AT&T and iPhone"
Google voice search for phones
If I didn't despise my RAZR so much, this would tempt me to restore Sprint data services to my account. As it is I'll add this to my phone list so I can play with it.
Official Google Blog: 1-800-GOOG-411: now with maps
...a few months back we launched 1-800-GOOG-411 (1-800-466-4411) in the U.S. It's a free telephone service that lets you search for businesses by voice and get connected to those businesses for free.
Today, your GOOG-411 experience just got better: during your call to GOOG-411, just say 'map it', and you'll get a text message with the details of your search plus a link to a map of your results right on your mobile phone.
Don't buy OS X software that doesn't use Apple's Installer
Adobe is the prime offender in the marketplace. We shouldn't be buying software that uses VISE and other non-compliant OS X installers. If a product doesn't use Apple's installer, don't use it. It's the mark of a vendor that doesn't care.
On Installers | Mac Geekery:
# PocketMac for Blackberry – Installer requires local admin account, AND installs essential components in ~/Library, forcing someone to log in with a local admin account, then drag the components to /Library/ then change the permissions so the actual user can utilize PocketMac.
# Adobe – Adobe’s installers and terrible enterprise support cause me an apopolectic fit. I still can’t get Reader 8 to repackage and deploy nicely....
Subscribe to:
Posts (Atom)