Also did a little cleanup and removed some obsolete import/export options:
-AOL Pictures: Site no longer exists
-Faces.com: Site (the one I built support for) no longer exists, and has been replaced with a social network.
-“Phanfare 2”: There were previously two versions of Phanfare set up for migration from within Migratr. This is because Phanfare went through some pretty drastic changes, and for a time was really two different services- The old one and the new one (designated as “Phanfare” and “Phanfare 2”). They were kind enough to leave the old version of the site up for several months in order to give users time to debate whether to convert over to an account on the new Phanfare (managed internally by them) or to determine that the new vision for the site wasn’t for them and migrate elsewhere (which is where Migratr came into play). The transition is complete, and there’s no longer a reason to keep the API for the “Old” Phanfare in Migratr. So it’s been removed, and to clear things up, “Phanfare 2” (the New Phanfare) has been renamed simply to “Phanfare”, as there’s only one version up anymore.

As mentioned in a previous post, I’ll be digging into Gallery 2.3 issues as time permits. My earlier statement that “It’s stopped working completely” turns out to be wrong- It works for me, which is really frustrating- I can’t duplicate the issues others are experiencing. Those of you who have emailed me about Gallery support- I might be hitting you up for beta testing in the coming weeks:)

For the time being… Enjoy the download, and happy Migrating!
-Alex

[download#1#image]

Also, for those of who you are having issues with Gallery- I have to admit Gallery support has always been a little sketchy with Migratr. Different hosting setups have meant that one person’s 2.2 installation could work with Migratr, wheras someone else’s would tank out while it was still pulling album data (before photos were even downloaded)- On top of that the “API” is meant to be used with PHP, which Migratr isn’t even written in. Support basically started out by ripping code out of some open source .NET Gallery remote and tweaking it to work with Migratr. With 2.3 this seems to have stopped working completely, so in the coming weeks I’ll be hunting around for a suitable replacement.

Also, if any experienced .NET developers can recommend good plugin frameworks, I’m planning on modifying the core Migratr code so that someone can write a service support DLL, drop it in the migratr directory, and have it show up as an option. This would help enormously with Migratr’s ability to support closing services, since it doesn’t always happen at a time where it’s possible for me to ninja something together (especially since they’re often places where I don’t have an account, and have closed account creations).

Thanks for the patience. Happy migrating!

-Alex

Observe!

Details later. For now, sleep.

If you go to the website, you’ll notice that in the pictures of the product, this monstrous beast of a pillow-chair-thing has straps on the corners which snap together, allowing you to make it form into a chair. This is why I’d chosen this product. The versatility of having a crash pillow that turns into a chair, that can be picked up and chucked in a closet when not in use (so as to free up room), so that you can optimize for space or seating in the living room on the fly depending on how many people are over. This is what made the Sumo Omni Plus a theoretical masterpeice- All the reviews I read touted those straps as the killer feature, the thing that really set it apart from the regular omni. But what I received in the mail wasn’t that masterpeice. Instead, I got what amounts to a giant freakin’ pillow. Not that it isn’t an AWESOME pillow. It’s still comfortable (even though the foam inside hasn’t finished expanding/settling- it’s been less than 24 hours), and you can flip it on it’s side and sit on it in a comfortable, slightly goofy fashion.

After going over all the packaging twice to make sure that it wasn’t simply an external set of straps that I’d tossed aside accidentally, I called customer support this morning, and was pretty surprised to hear their explanation.

“The new model doesn’t come with straps.”

Excuse me? So I basically just paid 50 bucks more for a regular Omni, only a little smaller and with a microsuade cover instead of rip-proof nylon? The pictures on the website were still the model with straps. This is where I honestly started to feel gipped, as we were pretty much matching the definition of “not as advertised”. The next words out of my mouth were, as a software developer, words I never thought I’d ask. “Can I exchange it for the older version, then?” She said that the old version was sold out, but that she’d check with shipping to see if they had any left, and call me back. I specified that I didn’t actually need them to send me a full new Omni Plus- I only wanted a new cover, the one that came with straps.

I suppose, worst-case scenario, I can just exchange it for a Gamer instead. Since the primary role is going to be as a chair and not a pillow, this seems like the logical substitute (also since it’s the exact same price). However, I’m a little worried about the return policy, which states that returns must be pre-approved by the Customer Service Department (is “I was expecting your older model, not the new one where you took away the feature I most cared about”), not to mention instructions, which state that all returns must be made in original packaging. This is a problem because the original packaging was vacuum-sealed, and the exposure to air has ballooned the end product into something much larger than one could ever hope to fit back into the box without the proper machinery. To give you an idea, here’s a picture of the Omni, standing next to the box it was shipped in.

At the very least, I think they need to update the pictures on the website, and throw an article into their “news” section that specifies the change to the omni. I have no idea what else is different in the “new version” of the omni plus- God knows why they removed those straps, but having done so they at least have a responsibility to not advertise something with more features than what they’re actually providing. As for sumo customers out there- I’d ignore the omni plus until this gets addressed. If what you want is primarily a crash mat, rock the straight Omni and save yourself 50 bucks. If you want something that’ll primarily be used as a chair, you should probably lean toward the “gamer” model.

Still waiting on a response from customer service as to whether I can get the old cover, straps attached, that actually makes it worthy of the “Plus” moniker, or not. I’ll let you know how that turns out.

-Alex

We all know the internet is full of dumbasses. Newsflash, you’re one of them. Being smart isn’t enough to set you apart around here. Welcome to the party.

You type “M$” when referring to Microsoft.

Congratulations, you’re against the establishment! Way to be a rebel, just like everyone else. Showing contempt for a company that charges you for use of their hard work is kind of ridiculous, so if you’re a consumer, you’re being lame. If you’re a linux hacker, you’ve got a leg to stand on, but you’ve also got a day job where they pay your salary by charging other people money. And if you’re an Apple user, then, let’s face it, you’re being an epic hypocrite. Before you go off on another rant about how bloated a Microsoft OS is, check out your mac’s price tag.

You make constant references to anything someone with “geek cred” would know, in parantheses, ending in “anyone?” (slashdot/reddit commentors, anyone?)

Often the committer of this particular sin is masking it as an on-topic reference. This is not impressive. But it is annoying. It is especially egregious if you do this during one-on-one conversation.

BTW, I consider this to be Jeff Atwood’s only serious blogging sin. I love that blog, but every time he does that I wince a little, just because I think he’s better than that.

You Namedrop e-famous bloggers like Yegge, Atwood or Spolsky

I just got called out on this one, by a friend who saw point #3. Look, none of us are perfect. That’s why it’s a cliche :D

You’ve actually answered a “How do I do (this) in (this environment)?” question with “switch to (my environment of choice)”.

This one is pretty generic. So, examples!

Q: How do I do (x) in PHP?
A: Switch to Rails (In the history of the internet, the person who asked this one has never once gone “I talked to my boss, and convinced him you were right! We’re scrapping 3 years of development to switch to a language/framework none of us know, on your say-so! Everyone’s cool with it! Hooray!”)

Q: How do I do (x) in Windows?
A: Switch to *nix (Because there’s no way the learning curve is going to become a bigger issue than the original problem, right?)
Alternate A: Switch to Mac (Often, in this case, the real answer in windows is to right click on something. HA! I’m mostly kidding, though I’ve witnessed it in the wild)
Non-existent A: Worth mentioning, I’ve never seen anyone say “switch to windows” when asked the question in linux or apple forums. You can interpret that any way you want, but I think it’s at least partially because the reaction of a windows user is something along the lines of “I don’t know. I’m a windows user.”

Q: How do I make my ford truck stop making this noise?
A: Switch to Chevy
I’m not a car guy, but from I understand, in certain parts of the country, saying this out loud is a really bad idea. Ah, the anonymizing power of the interwebs.

We’re all guilty of something. Be it namedropping, inappropriate evangalizing, self-important rambling (Yeah, I’m talking to you!), none of us are perfect. But I think a goal we can all agree on, an ideal we should continue to strive for, is this.

Don’t be that guy

-Alex

I can only speak to Photo-related web services, as that would be the area where I have the most experience. But I think most web services “get it” with regards to an API- By publishing an API, and enabling and encouraging developers to interact with your webservice, you’ve effectively given yourself a dev team larger than you could ever hope to afford. Users passionate about your services, with ideas on how to extend and improve it, and the know-how to implement those great ideas. More applications related to your website means more ways for users to interact with it, which means more chance of a “killer feature” written by a user of your service that ends up driving thousands of new users to you, any one of which can be a developer that continues the cycle. It’s an upward spiral.

But it takes more than just publishing an API. You have to make your developers WANT to write stuff for your service. Make it easy and enjoyable for them, and remove as many roadblocks and speedbumps as you possibly can so that they can complete their brilliant idea before throwing up their hands in frustration, or slowly, quietly losing motivation amidst a sea of vicious bugs, counter-intuitive behavior and documentation that either looks like it was written by Hemingway or run through babelfish.

Given my relative experience in dealing with API’s en masse, I decided to compile a checklist for being developer-friendly. Some of it is necessary. Some of it is more along the lines of “helpful”. Some of it is just wishful thinking. But these steps will help you tenfold.

Let developers know your API exists

Publish a listing for your API on best online blackjack game android, effectively giving the internet a cheat-sheet for your API- Protocols (soap, json, etc), documentation links, fee information (free non-commercial, pay commercial?), 1st and 3rd party libraries. You’ll get legions of volunteer devs through this site, who might not have even known your service existed. Also, a “developers” link in the footer of your website is like gold. It should link to a page providing the basic information: API Sign-up process, documentation, etc. I don’t want to go trolling through support documentation or chat live with a customer service rep. Just let me hit the ground running.

The developer section of your site should be more than a couple pages. It should be a microsite.

In no particular order, this should include most (if not all) of:

• developer forums
• some of your own developers monitoring and answering questions in the forums
• API documentation
• links to working third-party applications that use your API, or third-party libraries that access it
• API news and updates, blog-style
• a “My Profile” section showing me my own API keys, stored app descriptions and (unusual, but I consider this a bonus) usage statistics.

Don’t half-ass your API

AOL Pictures API was little more than “Look at us, we have an API!” lipservice. There’s no way to programmatically log-in and access private pictures, there’s no way to upload via the API, and the system for returning information about those pictures was unintuitive bordering on useless. The API should be a programmatic reflection of what your web service is capable of. On the complete opposite end of the spectrum from AOL, Flickr has an AMAZINGLY comprehensive API. You can fine-tune not only what data, but how much of it you want returned. You could practically create a flickr clone using the flickr API as a backend. (Disclaimer: Morally and legally, that’s a really bad idea.) Another bonus-points case: Kristopher Tate (of http://www.callingshotgun.net/casinos-in-southeast-florida-beaches-close/ fame) once told me that the Zooomr website was a display layer built on top of the API. I’m not asking you to do that, it’s a decision you have to make. But we know for a fact that, in this case, it’s well-tested:D It’s also based off the Flickr API, which means it’s super-easy to modify a Flickr app to make it Zooomr-compatible.

Another point, try to provide a few different options in terms of protocol. At least two of SOAP, JSON, or straight-up REST. Recently I came across an API that’s accessed via SOAP, but doesn’t provide a WSDL file. That’s cruel. I mean it, it gives me the distinct impression they dislike me personally:P Seriously, though, different languages a way of making different protocols easier/harder. Giving the option of parsing XML vs JSON, or providing a WSDL file and letting a code generator handle all that for you (a serious perk of client development in .NET) makes your API more language-agnostic and universally accessible. To summarize, the API should be stable, complete, flexible, and not counter-intuitive.

API Documentation: People actually read it.

Again, Flickr comes to mind as a shining example. Every method you call via their API has documented behavior on whether it needs the user to be authenticated, parameters, example of the response sent from the server, and possible error codes. There should be a TOC of methods split up by category (for example: photos, albums, user groups, friend list, authentication) so I can quickly and easily hone in on exactly what I’m looking for. Provide links to every third-party library that someone has written for accessing your service in a particular language.

Provide tutorials and walkthroughs, and if a third-party dev writes one too, link to that. Throw in some sample code in a few popular languages (Java, c#, python, ruby, perl) so people know what the code should look like. You don’t have to do this for every method. I’d recommend doing this for the authentication step, as developers will be able to test this without getting anything else right first. The net idea is that I should be able to get rocking with your API as soon as possible in the language of my choice, provided it’s a relatively common language (I don’t expect there to be a “Flickr Haskell Library”, for instance. But I do expect a Java one). Good documentation means your dev forums will be manageable.

Dev Accounts

I’m a little biased on this one, given that I interact with so many different webservices. But of all the services I use, most have “pro” accounts that I need to be able to test against. Some sites (major props to http://www.callingshotgun.net/borderlands-2-slot-machine-differences-between/and Zenfolio) comp pro accounts to developers who have written software that interacts with their services, as a matter of practice. Others will give the developer a one-year coupon upon request, while others don’t give us anything at all. Software is going to need testing, and if I run into a free-account limit for uploading data to your webservice while testing my software, I’m either going to have to cough up money for the right to add value to your service, go through the lengthy process of clogging your database with test accounts, or wait a month until I can do more testing. These are all roadblocks. I’m trying to write something your users will appreciate. Please don’t leave me hanging like this!

One thing that I would *like* to see, that I haven’t yet, is a special developer account- Not just a comped pro account, but a user account specific to developers. This account could have behavior specific to testing my software, like

• API-Accessible switch between account types, like “free”,”standard”,”pro”,”super-mega-expensive-awesome-pro-account-of-extreme-justice”, in terms of toggling things like upload/download limitation that vary from account to account, to reproduce errors my users are seeing and test for different errors that might come up
• None of the things I do via the API show up in “Latest activity” bar on front of site. If I’m running tests, it would be good etiquette for me to be able to avoid what could be considered spamming
• 24-hour deletes or auto-rollbacks: If it’s a test account, It’d be nice for me to be able to keep the account empty when I’m done testing, without writing housekeeping code on my end that just deletes everything. This means I’m trying to take up less space on your servers. I’m not saying this should be automatic, just we’d both be happier if I had the option.

Sites that don’t hand out free pro accounts to developers could offer these up instead, and just cripple the accounts in ways that would only matter to an active user: the 24 hour deletes could be mandatory, all data posted on a social site could be kept private and not visible to the community, etc. The main point here is that while I totally dig on the incentives provided by the services whose API’s I interact with, it’s more important that I be able to test my software against theirs, fully and comprehensively.

All this really matters, and so do your developer-users

I know it sounds pretentious and self-important when I say that as a third-party developer, I’m adding value to your service just by coding something against your API, and thus you should make things as easy for me as possible. Like I’m the kind of guy who always types “M$” when I mean Microsoft, or leaves obscure, nerdy references in parentheses followed by “anyone?” (Slashdot/Reddit commenters, anyone?). But I swear I’m not being that guy. I’m basing the idea that I’m adding value (or, in the case that I suck, the idea that someone else is adding value) off of the services I’ve seen flourish, and the ones I’ve seen wither and die.

Yahoo Photos and AOL Pictures: Half-assed API (Yahoo’s was even web-only, so you couldn’t write a desktop application for it). Both deadpooled.

Imagestation and Epson Photos: No API. Both Deadpooled.

Flickr, SmugMug, Zenfolio, Phanfare, PicassaWeb: Comprehensive, well-documented API’s with active developer communities, responsive staff and a wealth of resources for helping you get stuff done. Thriving.

In summation, in the words of Jerry McGuire, “Help me help you.”

Come on. I had to say it. You know I did.

-Alex

Oh snap! What’s that? Yeah, you read correctly. Migratr [finally] has Photobucket support! So for those of you itching to give Photobucket a shot, or for those of you with a few hundred photos wrapped up in photobucket and wanting to give another service a shot, now’s your chance. Go! Play! You’re free now. It’s all okay.

Also, I outsourced some logo development for Migratr. The picture you see at the top of this post is what you’ll see from now on as the application icon in the start-menu and/or desktop shortcuts.

Anyway, as always, rock the big download button to download the new, swanky version.

[download#1#image]

Sorry for the lack of updates lately. I’ve been plugging away, but sometimes it’s hard to get to a stopping point where I can say “this is ready for release”. Will prob. have something up before the end of the year. And, as a sidenote / friendly reminder, AOL Pictures closes on Dec. 31, so all you who use that service have just under a month to get your pictures and get out:)

-Alex

return reduce(lambda l, r: l + seperator + r, (str(s) for s in values))

While I’m not going to claim to be some sort of industry expert on the subject, and there are probably wikipedia entries and blog posts and Knuthian essays I haven’t read on the subject, this is pretty easily the most simple, elegant fencepost solution I’ve ever seen in my life. There are no special cases, boundary case handling, seeding (ie, initialize the final string to the first element, then start the loop at the second). It’s flexible, straightforward, relatively easy to understand to someone with a sufficient familiarity of lambdas. It just does its thing and disappears.

And then it occurred to me, since lambdas had been brought to c#, that this was suddenly within my power to accomplish as well.

I had certain goals in mind, as the snippet provided to me had set a serious benchmark. I wanted it to be as general and flexible as possible- It shouldn’t take only arrays, or only lists. You should be able to throw any sort of collection at it that you want. You also shouldn’t be restricted to only sending it Strings- Might as well make it possible to send it a collection of numbers, or people, or pretty much anything you want. This was more of a “hey, while we’re at it.” Feature creep, I know, I know. But it’s my exercise, and I’ll rock it as I see fit:D

Next, I wanted it to be as simple, elegant, and straightforward as possible. To me, the most significant thing about the snippet was, as stated above, that there was no special case code, and no seeding. You can develop an inferiority complex trying to make c# code as elegant as python code, because c# is a more verbose language. It just requires you to be much more explicit about everything than python does- Especially when it comes to LINQ and collections. Brackets, parentheses and curly braces everywhere. Still, I felt a degree of elegance was possible, and I was determined to find it. What can I say, I was bored, have had minimal exposure to functional programming, and the idea intrigued me…

Here’s what I came up with.

public static String fencepost(IEnumerable values, String seperator)
{
    IEnumerable strings = values.Cast