Archive for September, 2005

Wordpress.com

Tuesday, September 6th, 2005

Niall hooked me up with a Wordpress.com invite, which I converted into miker.wordpress.com. I wanted to check out how they had it setup, there seemed to be some interesting slickness in and about the admin area. It’s a nice setup, but I’m a pre-biased Wordpress fan. I didn’t want to just use up an early invite to play with stuff, so in the interest of helping out here’s how to setup Vagablog to post to a wordpress.com blog:

  • Go to the Server settings under the Options menu. The Host to enter is the domain name of your blog (in my case this was miker.wordpress.com), set the URL to “/xmlrpc.php” (don’t forget the leading slash), and set Type to Wordpress.
  • Now go to Identity, also under Options. Set your username and password.
  • Tap on the Blog List button, and then the Refresh button on the screen that pops up. Refreshing the list of blogs is the first time Vagablog actually hits the server, so if you now see the name of your blog in the list everything should be working fine. Select your blog in the list, it’s probably the only one, and tap OK.
  • Now you should be able to enter in a post title and text and post it. The category stuff should work, though I haven’t tried it. It used to be that the XMLRPC calls expected the number of the category and name didn’t work, not sure if that’s the case still or not.

There ya go! Image upload would rock. It would rock like ten times as much if someone else wrote it and gave me a patch for it. I’m kinda busy these days.

Real World Tagging

Monday, September 5th, 2005

semapedia.org is making the rounds recently. I was just fooling around with it on Friday, after having heard the folks on #mobitopia talking about it. There’s a post at the Social Software weblog asking if there isn’t a less obtrusive way to do the same thing. I was thinking about that as well. There are a couple of different aspects to make sure you have covered though. Here’s my brief rundown.

Systems somewhat like Semapedia.org, and by extension Semacode, have been around for a while. If we take the base idea as attaching some bit of information to a place, there are projects using Bluetooth to find nearby devices (which can include static beacons) and using GPS and triangulation based on Wifi access points or cell phone towers. What really stuck out about this one for me was that the information was embedded right in the tag. For most location based services you have some central server in the sky that takes the information about your location and directs you to the right resource. It centralizes control and restricts what people can do with the system. However, the semacode embeds the information for the resource right in the tag. No central control, no intermediating server, no need to get my information “put into the system” for others to look up. I just put my info online and I can print out the tags myself. Completely federated tagging. That was one of the big plusses that caught my attention when I first read about it. There’s no infrastructure that needs to be ongoing in order to support it. People need to have a reader installed on their phone, but that can’t be “broken” by a central server being down or taken out of service. Once you bootstrap this effort it stays up.

Now, of course we can have a Bluetooth device out there sending out a full URL in whatever it sends. Lets look past the problem that it isn’t meant to send URLs (you can always do things like attaching them as the homepage for a contact or something, or have a dedicated app like semacode does, so it’s not really much of a “problem”). There’s both the power and cost problems. It costs me almost nothing to create a semacode, I just went online and printed out a tag. If I already have a printer that’s a trivial cost. Totally the kinds of cost you want to see when you’re encouraging grassroots efforts. However the cost to deploy a bluetooth device to do the same thing is much higher. Plus it needs to be powered, which is problematic in both wired and battery delivered versions. And a device, even a simple one that just transmits some info, has value. I’m sure they would be stolen almost as fast as they get put out, especially if there weren’t tamperproof. People would steal them to reuse them for their own tags. And creating a tamperproof system really drives up the cost. However a printed sheet with one particular mark on it isn’t likely to be stolen. Vandalized or destroyed, sure. But no one’s goig to steal it. And replacing it is very simple. This is the deployment problem. In this respect as well Semacode really does a great job of fitting the kind of pattern that a community effort wants to follow. Semacodes turn any printer into a location markup device, and there are lots of printers out there already. Bluetooth basestations would work, but really fit the pattern of an infrastructure deployment more than a community effort.

I really hate to say it, but there is one other technology that could work well here, RFID. However, it would have to be a version of the tags that are capable of storing a full URL directly, and I’m pretty sure that passive tags aren’t nearly at that storage capacity yet. They’re meant to hold UPC style info. That doesn’t keep you from using multiple tags and some kind of encoding to spread the data across multiple tags. Hmm.. wonder if anyone is doing that. And then there are “active tags”, which are effectively little radio transmitters with batteries. The passive tags are much more appealing because they’re a lot smaller, cheaper, and specifically because they don’t have batteries. I don’t like RFID by the way. I think it’s a totally overhyped and underdelivered area of work. However, I would be somewhat interested if someone came up with a way to get low cost passive RFID tags to hold a URL of the users choosing and a system for using them to do this kind of community tagging. We could just wait for smartdust , and paint or pixiedust the tag on. Tagging pixiedust, I hope del.icio.us doesn’t have a trademark on that.

Vazu Free SMS

Friday, September 2nd, 2005

Russ turned me on to Vazu the other day, and I was just fooling around with it some. They have a little contact management and info site that you can sign up for, but I was much more interested in their developer API. They have tools (executable for Windows it looks like, I tried out the Firefox extension under Linux) that you can use to send messages using the API, and you can develop your own tools and integrate the messaging with your own site or service. The main usage pattern for me is sending myself links that I know I would like to check out when I have a few moments of spare time. Actually, I’m thinking a bookmarklet that would take the URL I’m reading, wrapper it so that I’m going through Skweezer or PHONifier, TinyURL the result, and send that to my phone. I’m also wondering how long till we see a MIDlet based on this so that I can send free messages from my phone.

I really hope they’re able to monetize this with the advertisements. I think the carrier model is broken, and their method of charging for messages in and out is just killing off what would be a tremendous amount of usage if it was just allowed to happen. Tough medium though, with lots of constraints. There are advantages however, Vazu could end up with a pretty rich profile of who the person at the end of the phone number is. That’s something that’s always a problem with online advertising, how do you build up a profile of the user so you can target to them. Vazu can track aggregate behavior because their messages are sent to a phone number. They’ll know that my number gets messages about Linux and happenings in downtown Palo Alto and cell phone reviews. There’s some potential there. And right off the bat they’re saying “Hey, we’re taking 60 characters for our own use”. No problem for me there, you can have 60 characters of the message if I get to send it for free, totally fair! I’m keeping my fingers crossed. Good luck Vazu!!