Winer and Co are talking about building a true podcast device: no DRM, wifi, podcast subscriptions. It’s indeed incredibly that neither Apple, Sony nor M$ have taken this opportunity yet, and I think the community can totally spec and build a device. Open source hardware, it’s the next step.

Speed is still a very big deal in UX. This yahoo research says that one of the easiest improvements you can make is having less objects (images, js files, …) per page, which reduces the amount of requests the browser has to make. There you go, Yahoo said so. Drop those images.

If only I was a good programmer, I would have known to expect the weirdest stuff with data coming from outside the system. At mefeedia, we aggregate RSS feeds, and anything you can imagine is out there. Loads of invalid feeds (but we take them anyway), invalid data, missing elements, and so on. What a mess :)

Here’s a thought: a scalable memcached service. So what you provide is a memcached pool. Charge by memory – it doesn’t matter how many servers this runs on. x4/MB of memcached. Then, I, as a user, just have to buy some, and call it in my code. And I can easily get more. Nice & sweet, especially because shared hosts and such often can’t easily install memcached.

I know, probably a bad idea.