As I mentioned recently, due to a change at my hosting provider, I ended up switching my self-hosted WordPress.org blog over to a WordPress.com blog. The transfer itself was very smooth and easy using the great built-in function in WordPress.com, which copied over all my posts and custom CSS (although it did not do as well with some images, but that’s a separate story).
Realistically, I completely understand why Automattic places such limitations on users: just like Steve Jobs and his stance on the stability of Flash, they want to control the environment and ensure that everything functions smoothly across a shared platform.
So, as I get used to my new home on WordPress.com, I still need to test out a few things: one of them is embedding Vimeo videos, so that’s today’s post. I don’t produce that many videos (I’m obviously much more focussed on DSLRs than video cameras), but I am still on the fence between YouTube and Vimeo: I like the interface of the latter, but, obviously, the former is much more widely used and, therefore, means more people are likely to see a video and there is better compatibility with other services (iPhone/smart phones being one: you have to sign up for Vimeo’s paying service in order to be able to switch on mobile versions of your videos).
Anyway, today’s test of a Vimeo embed – this is 15 minutes of cloud movement after a typhoon condensed into 2 minutes. It was shot last year with a Canon iVis HF21 HD video camera on a tripod (from my balcony):
(turn off the sound if you don’t like techno…) 😉
Embedding the video is really easy – WordPress.com’s instructions are here. However, oddly enough, they neglect to mention that the URL/Video ID can be pasted into either the “visual” WYSIWYG post-writing window or the HTML post-writing window.