Thanks anyways :)

The problem is with the “no-store” keyword in the value for the Cache-Control HTTP header (you can get headers information using the Web Developer toolbar for Firefox, for instance). It shouldn’t be that hard to fix. You will need to activate mod_header (I think) if it’s not on, then in a .htaccess file at the root of your blog folder you could have:

Header set Cache-Control “no-cache, must-revalidate, post-check=0, pre-check=0″

(Well, that’s if you only want to remove the no-store value. On my own blog and sites I either don’t use Cache-Control or use “Cache-Control: max-age=some_value”, with a value of 600 — i.e. 10 minutes — for HTML pages, ten days for CSS or JS, and one month for images.)

I may comment again on the topic (Spotify) when I have some free time. :)

Wrote a long comment (on why I like Spotify). Submitted it but I forgot to fill in my name and email (it’s placed on the right, didn’t see it). So I got an error, and when I hit Back my message was gone, thanks to this HTTP header:
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0

Way to loose twenty minutes. :(

I tried the dpi trick and OK, it made the menu look ok but destroyed all the other texts of Spotify. I’m now installing msttfcorefonts to see if it helps.

@Paul: Sorry, don’t have any.

@Jonas: I agree, it’d be nice to get Spotify ‘open up’ to have it integrated in existing players people use, like last.fm is available in amarok etc. But I’m not sure the developers are interested in including commercial partners in the default configuration but of course Spotify could pay someone to write an amarok plugin or somethin. Don’t know, we’ll see where it goes. As @jmc pointed out, there’s already despotify available – one could guess that other clients will rise soon.

@daoo: Thanks for the link!