In that case it's just another symptom of the thing that is naturally selecting them

Auto!Automatic!!’s first album[1] has different track titles on streaming services [2] likely because of a refusal to account for these edge cases

[1] https://www.discogs.com/master/1902714-AutoAutomatic-Another... [2] https://open.spotify.com/album/0rNK6bVONDkJAdBgmemm9h

We do a similar thing at Last.fm. We bundle our most commonly used modules in a single file. The rest all pulled in at runtime.

Paul wrote about it here: http://www.paulrhayes.com/2013-09/a-light-progressive-framew...

"The domain "boxsocial.fm" doesn't appear registered with GoDaddy."

Another one to test against as I've not moved it yet.

I'd be interested to know how common credit scoring applicants is. I understand why they'd be necessary for financial institutions but as a general method of filtering candidates it seems rather intrusive.

More detailed pricing information is available here: http://code.google.com/apis/maps/faq.html#tos_pricing

Awesome, thanks. I looked all over that Premium site and didn't see it.

Was this a straight HTML list or were you using a jQueryMobile listview to pretty it up? When we've used templates to render a list (using either underscore or ejs) it was taking 10-20ms to generate the initial HTML but around 10-15x as long to call listview on it.

I was using jQuery Mobile. The listview framework is a big part of the performance problem.

Needless to say, the best advice I would give (that others have said here as well) is to avoid frameworks like jQuery Mobile. There many other reasons too...not least of which is that jQuery Mobile doesn't work on T-Mobile or O2 in the UK and parts of Europe. It appears these networks intercept all traffic and try to minify the JS and CSS before they deliver it to the phone. There is some part of jQuery Mobile that they choke on and the page doesn't render correctly. I've tested extensively using Perfecto Mobile and even the jQuery Docs & Demo pages don't work right (so I know its not just me).

Thanks for this info. I wasn't aware of potential carrier-specific issues so I'll make sure we take this in to account while testing. Have you raised this with the networks? I guess there's a chance that it could also affect non-jqm powered code.

I got the same. Just click the 'sign in' link at the top, then 'Sign in with Github' and it should take you to your account.

Yah, though that just gets me back to the sky blue screen of nothingness.

We're seeing this as well. The problems are being investigated.

I'm using node.js for a personal project: http://boxsocial.fm

The site reads and writes to last.fm in the background and pushes updates to client's browsers while doing so.

I'm sure it would have been possible to write it using some other technology but node.js just made it so easy. Also, writing the entirety of the app in just one language was an additional bonus.

I'm excited about building something bigger with it soon.

Is this alternative client for last.fm? I wonder how useful developing alternative clients can be apart from learning purposes. I have seen a lot of twitter clients coming up. Do users really care about using these?

To some extent. It copies a user's scrobbles/now playing info to one or more other users' profiles. So if a bunch of you are in the same room listening to music you can all scrobble at the same time.

That said, it was mainly written to get to grips with node. As well as to scratch a personal itch, obviously.

I can't seem to get this through npm. Has it been published?

yes, it's available with `npm install ready`