Matt tried to make me look good.

/via Kyle Neath on Twitter.

We’ve set up a special page on Viddler just for Magic Ruby to help let people know some of the things we’re already doing with the Ruby community. We hope to learn a little about Ruby, to let attendees know about Viddler, and to enjoy the weather.

Viddler’s offerings to developers aren’t limited to only Ruby. We’ve got a fantastic API that has been recently overhauled and wrappers for just about every language. We power some of the biggest brands online and our platform has been used to power web sites, applications, iPhone and iPad applications and much more. I personally hope to help Viddler grow in this area in 2011.

If you’re a developer and ever have any video needs – consider using Viddler for your next project.

/via the Viddler Developers Group.

His example shows an easy way to grab all of your Delicious bookmarks off of the service. Only, if you are a Terminal newb you may not have any idea what just happened after you run his suggested command.

So, my suggestion is to run the following command. First, open Terminal by opening the ~/Applications/Utilities/Terminal.app or simply type Terminal into Spotlight and hit Enter. Then, run this command.

curl https://username:password@api.del.icio.us/v1/posts/all -o "delicious.xml"

That -o flag, or option, tells curl that you’d like to save the file. The filename that you’d like to use is in the quotes. Now, you’ll have a single XML file saved in your Home directory called delicious.xml with all of your Delicious Bookmarks.

What you do with that is up to you. Just about any text editor will allow you to read the .xml file.

Oh, and like Mr. Keith I’ll be posting all of my links back onto Delicious as well. I just have to write a quick plugin for WordPress. I’m sure I’ll find time for that sometime in 2011. I’ve never thought of doing that (no idea why) but I am going to start. I don’t know what the future holds for Delicious but either way it is fun and easy to “dual post” the links.

For more information, see the Viddler developers page.

Note: If you are using Google Reader you may not be able to see this video. The Reader team is dragging their feet on supporting Viddler’s latest embed code. Come on over to my site to see it.

/via Simon Willison.

Brady Forrest for O’Reilly Radar on the possible implications of this acquisition:

“Second, does this herald Twitter’s moves into being a location provider? At Sarver’s previous company they had a location-brokering service called MyLoki that never gained ubiquity. Twitter has the opportunity to become a major location broker. Twitter currently has a very simple on/off switch for location. To become a full-fledged consumer location service (like Latitude or Fire Eagle) they will need to build in more controls.”

Forrest’s use of the term “location broker”, I believe, means that Twitter could become a standard for just about anyone to location-enable their own applications rather than simply geocoding tweets. I think Twitter should do this by keeping GeoAPI “open for business” allowing developers to continue to build products using the API, commit data to it, and improve the API over time.

Forrest asks if Twitter will charge for the use of the GeoAPI like it charges for access to Twitter’s public timeline (or firehouse as they call it) to developers. I think they should charge for the use of this API and they should use the same reasonable pricing model that GeoAPI already had in place. No one should have to pay for the data, but they should have to pay for requesting that data hundreds of thousands of times.

In essence, I believe GeoAPI should stick around. It looks like a fantastic API and I’m looking forward to it being implemented into Twitter’s own API but I think it’d be a good idea to have the service stick around separate from Twitter itself.

Update: After reading the post on the GeoAPI blog about the acquisition by Twitter I realized that they are planning, for now at least, to keep GeoAPI up and running. They said: “We will continue to give new API keys for GeoAPI.com – however there may be some delays in getting keys over the holidays.” Good.

I love that they came right out and said that they were inspired by WordPress’ move.

Hopefully this feature will be available via a plugin sometime in the near future?

/via Tony Schneider.

• Use your own API. The very best way to make sure your API is equipped with everything one would need to build something of value is to use it yourself. You will find that by using your own API to build your product you will work out a lot of kinks that would otherwise frustrate third-party developers.
• Remove as many learning curves as possible. An example of this is to provide more documentation than you really need to by writing tutorials and not just flat documents. Code examples go a long way too. Provide “wrappers” or frameworks in common languages that help third party developers to “plug and play” with your API.
• Follow standard conventions. This is related to removing learning curves, but you do not go against the grain. Try to utilize as many standards as possible. Chances are any third party developers that use your API will already be familiar with much of what you’re doing.
• Support multiple response types. Do not assume that third party developers will only use the response type that you prefer. Supporting XML, JSON, PHP, and others is not too much more work and yet has a measurable impact on your APIs adoption.
• Create and keep your own conventions. If you have one way to do things try to stick with it all the way through your API. An example of this would be how Twitter recently added a Lists API to their API and used the very same convention of interacting with that API as they do with accounts. This makes integration of new features dead simple and it will be appreciated.
• Add some brains! If there are common actions that must be taken by all third party developers to interact with your API try to build those actions into the API. A good example of this is Flickr’s support for machine tags. Although a third party developer could do all of the work on their end to work with namespaces, predicates, and ultimately the values they are looking for – Flickr makes it easy by doing all of that work on the server-side. Taking the most common actions and rolling them back into the API will slowly build tremendous value in your API.
• Open source as much code as you can. If you build any tools, frameworks, testing applications, products, or anything that uses your API – try to release that stuff as open source. This will help any new third parties to be able to see real examples of products that use your API. It would also be a good idea to promote open source projects to use your API as well so that the entire development community that you build can benefit.
• Communicate with those using your API. Give the developers a clear path to communicate with you about your API, their applications, or anything they may need to get their jobs done. You will learn a lot about what you are lacking that you may have never thought of.
• Drink a lot of caffeine.

These are just a few tips that I’ve learned in working with Viddler‘s development team to build our API. We’re currently working on the next version of our API, dubbed version 2, and we’ll be making massive improvements to the way that the API works, is documented, and how we use it internally. We’ve learned a lot over the last few years and we’re taking all of the tips above and everything we’ve learned from our development community to build what we think is a much more solid offering.

I hope that if you are building an API you can learn from our experience, our failures, and our successes (and I’ll try to share more of them here). If you have anything you’d like to add about good API design please do so in the comments.

The photo of the fire hydrant has nothing to do with this post but I liked it. It is one from my Lincolnton, North Carolina photo set.

Read more about this feature on The Viddler Blog in a tutorial on how to get the best quality out of this feature called: How to: Set an image as a video thumbnail.

You can see the results on Eat Weird Episode 5. Gorgeous.

Also, this feature is exposed via the Viddler API’s setThumbnail method.

“The Viddler team is using CodeIgniter more and more for our internal PHP projects. Obviously we need to use CodeIgniter with the Viddler API quite a bit so we figured we’d share with you how easy it is to include PHPViddler, the open source PHP API wrapper class for the Viddler API, in your CodeIgniter application.”

Read more in the blog post titled How to: Use the Viddler API with CodeIgniter.

Go forth, and hack! Oh, and its completely open source too. (More on this later.)

But I think it is time to stop complaining and start helping.  How?   What if we created a list of “well built” applications that use the Twitter API?  By that I mean applications, tools, widgets, etc. that do a good job of not pummeling Twitter’s servers with requests.

The A-list of Twitter apps

I’m not foremost expert on scalability – but I know a well-built application from a bad one.  Any application, widget, or tool that does not use even the simplest form of caching, for example, will not make this list.

I will need your help.  So please comment below with any applications or tools I have not yet linked to, I’ll vet them a little, and add them to the list if it makes the cut.  If you are a developer – please include what you do to help Twitter with your link.

• MW Latest Tweet - by Eric Meyer – A WordPress plugin that shows your latest Twitter status anywhere on your WordPress-powered site.  In order to make sure that I am also helping Twitter, I’ve installed this here on my site.  You can see it on the sidebar of my front page.
• Twitterrific – by The IconFactory – A Mac OS X application that allows you to view your friends timeline and post to Twitter.  Twitterric only requests the Twitter API on a set interval (customizable, and I have mine set to every 15 minutes now).
• Twhirl – by Marco Kaiser and now owned by Seesmic – An Adobe AIR application, which means it runs on both Macintosh and Windows platforms, that lets you follow Twitter, FriendFeed, Pownce, and others.  The highlight of how this application helps Twitter is that it has a requests-per-hour-slider.  I’ve got mine set to 10 (but I only have it check for new statuses every 15 minutes).

Do you have any applications you think should be added to this list?  Why?  Leave them in the comments.  As I update this, I’ll notify people through Twitter, FriendFeed, and Pownce.  ”Follow” me if you dare.

Miscellaneous tips

A few tips and tricks to helping Twitter out, regardless of the tools you choose to use.

 

• Decrease number of requests.  No matter what applications you use, increase the interval (or decrease the number of requests per hour) between requests to Twitter for updates.  The common “side effect” of doing this is actually being more productive.  Give it a try!
• Don’t manually refresh after update. I’ve noticed myself doing this too.  When you send in a new status, don’t manually update.  Chances are it will take a few moments for your latest status to appear in whatever application you are using.  Send in the new status, if there isn’t an error, wait for the next scheduled request. I can’t imagine how many requests this could potential get rid of.

 

If you are a developer, whether or not you are interested in building an application, web site, or service using Viddler’s APIs.  Please chime in with some of your thoughts, if you have a moment.

Thanks in advance:

Source: What do you really need? In Viddler’s Developers group.

Weighing in at over 120Mb, this podcast is over two hours long so you might not find the time to listen to it for a while. When and if you do, please come back and let me know what you thought of the show.

Our topics included: Viddler (of course), the Viddler API, being a geek, the iPhone macro lens (video demo), my background in computers, a special announcement gets thrown in, and much more. All in all I think the interview portion weighs in at nearly 50 minutes.

The interview begins at around 40:00 into the show.

Thanks to Alan Chaess, and his team at the OtakuGeneration.net podcast, for inviting me to be on the show and I hope to someday be part of another show!

This is too cool.

(Source: PownceFS — Richard Crowley’s blog)

Our topics of discussion on the show ranged from a general overview of Viddler itself, a description of what can be done with Viddler’s API, and of course we talk about SXSW Videos since this was just prior to the festivals this year.

If you have time, be sure to give it a listen. Sorry I haven’t mentioned it until now, but I had fun being on the program, and I hope Philly TIP returns stronger than ever!

Update: This plugin is now available to everyone!

I’m happy to announce that as of ten minutes ago, we’ve distributed a private-beta to a few friends that use WordPress. Having worked on this quite a bit I’m happy to get it into other’s hands, even if they come back with a ton of bugs for me to fix, at least it will allow me the feedback to make the plugin better.

If you use WordPress and are interested in allowing your audience to comment with video, and you didn’t get an email from me today, contact me and I’ll be glad to get you a beta copy of the plugin. We’re eager to get people using it, but we just want to make sure we’ve dotted our Ts and crossed our… you get the idea.

Within a few days I’ll be writing more about this plugin on The Viddler Spotlight, the company blog, and by that time the plugin will be freely downloadable from our site for you to use. I’ll then provide some development notes, how we pulled it off, and other tidbits. For now, if you’re interested in working with flash-video online, look no further than Viddler’s API.

To test the plugin click “Record a video comment?” below the comment form. This will paste the appropriate code into the comment form to include your video. See, I told you it was simple.

Update: Thanks to all that have emailed me and commented so far. This last test has truly been very fruitful. I was able to squash a bunch of bugs last night, and I’m hoping to put the hammer to a few this morning. I’m expecting to release 1.0 beta 2 early this afternoon so please update your respective blogs when it comes out. Again, if you’d like to beta test this plugin, just send me an email.

Update 2: Looking for more testers. Version 1.0 beta 5 is now in the hands of the current group of beta testers and appears to be really stable. I’d like to expand the number of blogs this is installed on by about double the number of blogs we have currently. Anyone interested should comment below or send me an email. Thanks again everyone for testing this out.

The first is “related posts”. There are countless related posts plugins out there and all of them work fairly well but since I already use the Ultimate Tag Warrior plugin for my tagging efforts, and it has a function for related posts, I’m using a slightly tweaked version of that. When WordPress 2.3 is released, and tags are included by default along with a way to import all of my UTW tags, I may need to adjust the way I handle related posts. Until then, these seem to work well enough.

The second was I’ve always wanted to utilized my Ma.gnolia bookmarks better. Bookmarks seem to come and go and rarely are they ever used as a really valueable resource. I think the way I am using them now will add a lot of value to bookmarks that I’ve stored on Ma.gnolia, even if I had saved them there a very long time ago*. What’s more is that I’m adding value to my posts too!

The way I am using my bookmarks is through “related links” which can be found just to the right of the related posts on the bottom of every post on my site. I’m using Ma.gnolia’s API to search my Ma.gnolia account for bookmarks tagged with the same tags as the current post and constructing a list of the latest five of those. I’ll be working on extending this somehow to show every applicable bookmark but I’ve found that five should provide enough of a resource in most cases.

So come to the site, take a look, and let me know what you think. I’ll be releasing this new “Ma.gnolia Related” plugin after I’ve let it run on my site for a little while and I’m able to clean up the code a little. Oh, and it uses an as yet unreleased method argument of Ma.gnolia’s API – so I may need to wait until the next version of their API is officially released. (And to those that will probably wonder, yes I’m caching requests. Expertly, I may add. )

Web applications are different then the applications you run on your computer in two very specific and obvious ways. First, they are run completely in your web browser (Firefox, Safari, Internet Explorer, etc.) and you do not need to download or install any local files for the application to function. Second, the data that the application stores or edits is not on your local machine but rather saved “on the Internet”. These may seem like very obvious differences but I’ve mentioned these two reasons because the paradigm has shifted overtime and Google Gears almost completes that shift.

One of the many mantras of “Web 2.0″ applications has been to freely allow users of these applications to have access to their data both via an API and being able to “export” their data into various formats. These APIs afforded many developers to blur the line between desktop and web applications – such as being able to geotag your photos in iPhoto using Google Maps – but these solutions still required an Internet connection for them to work properly. Something also to note is the fact that these APIs are mainly used by developers and not by the users themselves so even though the data was portable, this fact hasn’t been exploited by the average user much, yet.

Enter Google Gears – which provides developers with the needed technology to make their entire applications portable not just the data. The first example Google chose to show off Gears with is Google Reader (a really great example). Google Reader, up until a few days ago, was a way to read your favorite sites by subscribing to their feeds but its use was limited to when you were connected to the Internet. Google Gears allows you to use Google Reader, at least most of the application, offline. You connect to the Internet, download your latest feed subscription’s updates, get offline, and you’re still able to read the feeds that you’ve cached on your local system. What’s more is that you are able to flag those items and Google Reader will sync with your Google Reader account once an Internet connection is available.

In short; Google Gears brings your favorite web applications to your local computer and allows them to run almost like desktop applications.

Why am I excited? Because my main reason for not using some of the most popular web applications has been because I can not use them offline. I am a firm believer in having all of my data available to me at anytime. Unfortunately in some cases, such as my photo and music libraries becoming larger than my laptop’s hard drive, I’ve had to make sacrifices. However, when it comes to much smaller yet more important pieces of data such as email messages, bookmarks, and important documents I can not afford to make those sacrifices. As Google Gears is adopted and implemented in more web applications I’ll be able to begin using them offline.

“hey, i think twitter might have switched something up on you, on your blog your twitters are there but the time isnt”

After doing a little sniffing around I’ve found that Twitter has indeed updated their JSON output for my personal timeline on Twitter and removed the ‘relative_created_at’ values (which would show things like “3 hours ago” on a specific status). My best guess is that by ripping out this value Twitter is saving themselves an immense amount of calculations on their end. They still provide you with the date and time that a particular status was stored, so you can still do the math on your end.

I am not sure when they will make this public, or if they are still making subtle changes like this and want to make one update to cover all of the adjustments they are making but I thought I’d give everyone a heads up that might be using Twitter’s JSON output(s) to show status on their respective sites or applications.

Update April 5, 2007: Twitter has announced API updates as well as written up documentation for their API.

[tags]twitter, api, json, update[/tags]
[slug]twitter-json-update[/slug]

First, I grabbed a modified version of Cutline and made my own little tweaks (which I’m not quite finished with yet). Obviously I changed the way the headers work and brought back my featured headings in order to highlight certain posts randomly. I’ll be adding many more banners over time, since there are ton of posts that should be highlighted. I’ll be doing a little more of this by creating a “random note” area in my right-most sidebar soon.

I also edited the way that the sidebars work. I wanted a 3-column layout to allow me to pull in my flickr photos, some posts from Viddler, ChanceCube, and The uber geeks, as well as a place that I will soon be putting various other collections. However, I wanted to have only 2-columns on my single entry pages because I like having the width for things like photos. Also, some of the pages (like the new diet page), have 3-columns, while some only have 2-columns.

On the frontpage you will notice the latest posts from the other sites that I write on (mentioned above). This section is powered by BDP RSS Aggregator. Obviously I could have built this type of functionality myself but after seeing how well thought out this WordPress plugin was – it made the decision to use it very easy. BDP RSS Aggregator does far more than what I am using it for, and if you are looking to syndicate some feeds on your WordPress powered site, I highly recommend you looking into it.

My most recent Flickr photos, on the frontpage, is powered by FlickrRSS. Since BDP RSS Aggregator has so many options, I could have technically used it and ended up with the same result, but I chose to use something that was specifically built for grabbing my photos from Flickr. Obviously Flickr’s API could have been used for such a task, but all I really wanted was a cached list of my 4 most-recent photos, and using the API would seem like a little overkill. FlickrRSS does an excellent job, is easy to configure, and has just the right number of options. Another plugin that I highly recommend.

For my recent comments I’m using a highly modified version of the recent comments plugin. I’ve added support for Gravatars and a few other options that it didn’t have out of the box. Once I clean up the code I hacked to get it done I may submit the changes, but since it is reliant on someone using the Gravatar WordPress Plugin (site currently under repair as of today) too, I may not. If you want this, just give me a shout.

For my archives I’m using Justin Blanton’s Smart Archives plugin. I like my archives simple, and this plugin allows me to have just that. I see now that its been updated recently, so I may have to get me a fresh copy.

For my keyword tagging I can’t do without the Ultimate Tag Warrior plugin – which in my mind is the best keyword tagging plugin for WordPress. It allows me to use MarsEdit to write my posts and put my keywords inline – which has increased the accuracy and ease of searching quite a bit too. There are many benefits to using this plugin.

I’m using Shaun Inman’s Widon’t plugin to help clean up the straggling words on my post titles. This layout doesn’t succumb to these problems as much as the last one did, but this plugin is handy nonetheless. Plugins that work completely behind the scenes and yet make such big differences in your site should really be applauded.

My feed is being delivered through Feedburner via the Feedburner WordPress plugin by my friend Steve Smith. It is all transparent to you on your end, but to me it adds a nice little layer that allows me to pull some nice stats on how many people and who are subscribed to my site’s feed. If you are using Feedburner and WordPress, this plugin is a must have.

Obviously I’m using ChanceCube‘s Slugger plugin to help me never to see WordPress’ administrative area as well as HappyPals to take advantage of my XFN relationships in my links. I also have Mike Stickel‘s Simple Countdown plugin installed and activated, but you’ll have to wait till the weekend to see why. These three plugins have become indispensable for me in how I publish, Slugger the greatest of these. I could never stand using WordPress’ admin (or any administrative area that I’ve seen) to write my blog posts. I’m happy I don’t have to anymore.

I think I covered pretty much everything. Poke around, if you see anything outta whack just let me know. Other slight tweaks will have to wait till the weekend as I have a fairly busy week this week.

Oh! For those of you on the diet that have recently been contacted by me (which most of you have, and if you have not then it probably means you’ve been fairly active in the dieting area over the last few months) – I’ll be updating everyone today or tomorrow but suffice to say that Tuesday begins another 20-week (minimum) run of updates. More soon.

[tags]cdevroe.com, redesign, shaun inman, wordpress, plugins, chancecube, mike stickel, slugger, happypals, simple countdown, ultimate tag warrior, justin blanton, smart archives, flickrrss, gravatar, recent comments, bdp rss aggregator, viddler, theubergeeks, cutline, theme, steve smith, feedburner, flickr, api[/tags]
[slug]cdevroe-v0207[/slug]

But, instead of focusing on what has yet-to-come, I wanted to point y’all towards a few things that have already been done.

The flash player and buffering technology behind-the-scenes is constantly being refined. If I remember correctly I’ve been through well over 12 iterations of the player (thought it appears the same as the day I first saw it) in my short time using Viddler. Obviously the better your bandwidth the better the experience, but for the quality of video that Viddler is capable of serving I can not believe how responsive their player is – and it continues to get better. A little birdy has told me to watch for some updates to the player in the near future that will separate the men from the boys. I think updates like this show that Viddler is dedicated to making the best possible experience, even if you do not know they are making the changes.

Though most video bloggers rely on their own systems of content distribution, and they should, there is no reason that they can’t take advantage of Viddler’s superior player for the audience that enjoys viewing their video in their browser and interacting with the community. Having the best of both worlds is very possible and we’ve taken the time to document the process as well as provide an overview and demo video. Obviously Viddler has some improvements to make to become video blogger’s one-stop-shop but they definitely are moving in the right direction.

Listen up video bloggers. Viddler is the place that you need to invest your time and effort into if you are looking to use a really great flash player and community service in conjunction with your downloadable and distributable file formats. I foresee many video blog archives being time tagged and searchable like ever before.

Something that has been mentioned before on Viddler is the ability to switch videos inline without refreshing the page. This is going to be extremely powerful for people who have multiple episodes in a single interface (especially as people start using the yet-to-be-released API, shhhh). We’re refining this process too as you can see from the latest featured videos post. More on this soon.

I am hoping to talk less and use more Viddler on my site soon. If you are remotely interested in this stuff, I’d suggest subscribing to the Viddler Blog. That is where all the juicy announcements will be happening.

[tags]viddler, video sharing, video blogging, flash, javascript, api[/tags]
[slug]viddler-new0206[/slug]

You can look at my profile over on Viddler, subscribe to the Viddler blog, or just learn how to use the service – while you’re following me around today.

6:00am – Just showered and fired up my Macbook to get last minute directions. I’m going a different way than I did the first time because I’m dropping Eliza off at some friend’s in Slatington (the Rosarios) before heading into Bethlehem.

It snowed last night! I got all of my gear ready (camera, ipod, laptop, etc.) and I’m going to start the Jeep up early. First time I’ve had to do that all winter. Off I go, next time I blog will be from the Viddler HQ more than likely.

9:19am – Just arrived at Viddler. Man, what a hassle with the ice and snow! I didn’t account for school buses or blinding sun on icy roads.

Of all things, Rob and I are talking about how Web 2.0 Viddler is. Oh, and we’re going to start posting in the new Viddler forums!

9:59am – The forums are up and running and you can even use video to respond or post in the forums. Very slick.

10:25am – Just finished a quick video, in better quality, letting people know you can respond to forum threads with videos.

We’re on our way out to Dan’s Camera Shop to see if we can get into some trouble.

1:54pm – Had a great meeting at Dan’s Camera Shop with Mark Woodland. Great guy, great company, if you live anywhere near them, I recommend you check out their site, and their shop.

By odd coincidence we saw Eliza, Andrea, Ava, and Giana there. I couldn’t believe it. I thought for sure they were stalking us.

I got to meet Donna finally! After leaving Dan’s Camera Shop we headed to a chinese buffet and went over what we learned in our meeting. Seeing this business from all perspectives is not only important, but it is also extremely interesting. Mark was able to teach us a lot about their side of the business in a relatively short period of time. Invaluable experience.

We’re now back at “the ranch” listening to some Cold War Kids and going over the new yet-to-be-released Viddler API.

2:56pm – We’re going to head over into the conference room and I’m going to record a “ScobleShow-esque” interview with Rob so that people can get a pretty good feel for Viddler.

If you have any questions, you can send them to me via email or comments.

4:02pm – Rob and I recorded a quick interview video and we’ll be publishing that on Viddler slowly over the next week or so. It has some great insight into not only Viddler’s past, but also Viddler’s present, and future.

I’m on my way out of Viddler HQ now. Going to head back to Slatington to hang out with some friends and get a bite to eat. I had a great day here at Viddler and I hope to come back really soon.

[tags]viddler, bethlehem, pennsylvania, slatington, macbook, eliza devroe, api, andrea rosario, dans camera shop, giana rosario, ava rosario, mark woodland, chinese buffet, food, lunch[/tags]
[slug]live-viddlerhq[/slug]

Flickr provides me with a great way to share photos with friends and family, and it has some useful tools for me to tag (categorize) as well as geotag (or note where I took the photo), and it lets me connect with different sets of people by using Flickr’s groups. These are all great. However the data that I put into Flickr is not mine and without using the API I will never be able to benefit too greatly from putting in the time it takes to utilize all of Flickr’s tools.

Del.icio.us is a great way to post your favorite URLs, tag (categorize) them, and make some small notes. Obviously there is the entire community aspect too though I’ve never taken full advantage of any of them. Also I do not use del.icio.us (boy is that annoying to type everytime) as my bookmark storage solution.

So I don’t fully utilize the two major web services that I would otherwise really like to — so perhaps something else could be done to openly share data and yet reap the most benefit from the time I put into cataloging it. I think my personal site is the perfect platform for this, and I’m going to start making both dramatic and subtle changes to the site and its architecture in order to do this.

Please “stand by” while I make some adjustments (which will probably take a total of two or three weeks to make, though you should start seeing some of these changes within the next few days).

[tags]cdevroe.com, updates, flickr, delicious, bookmarks, photos, sharing, web services, api[/tags]