Skip to main content

Bad eMusic Expiriences?

Has anyone has had a bad expirience with eMusic? Lured by promises of DRM-free MP3 files, like so many others, I signed up for a trial of their service. I was unimpressed with the selection, although I understand the problem they face trying to convince the labels that their methods are financially safe for the music industry. Still, my wife and I were unable to find even a handful of songs we were interested in, and I found it impossible to actually download anything. Their download manager gave me an error about some non-existant cache directory within my Firefox installation, and their support offered no help that actually solved the problem, just a standard "Reinstall the program and try it again." Realizing the service would not be worth the $9.99 per month, I cancelled my account and didn't look back.

Until they charged my bank account two weeks later and caused me a series of cascading overdraft fees that I've had to lodge a complaint with my bank to clear up. I contacted eMusic about this issue, and they will not respond, so my bank is looking into this matter for me. Thank god for fraudulent charge protection on my Visa, because the month of eMusic I didn't even want almost cost me $73.99 plus a massive headache.

Comments

Anonymous said…
Just had a similar experience. eMusic suks! Horrible site - bad browsing and web site layout. They are missing LOTS of popular, common tunes. Their movie soundtrack selection is horrible. I can't say enough bad things about eMusic - don't ever sign up for it - its really bad.

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this.


CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer. 
One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC?

It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on. The only re…

Interrupting Coders Isn’t So Bad

Here’s a hot take: disrupting coders isn’t all that bad.

Some disruptions are certainly bad but they usually aren’t. The coder community has overblown the impact. A disruption can be a good thing. How harmful disruption might be a symptom of other problems.

There are different kinds of disruptions. They are caused by other coders on your team, managers and other non-coders, or meetings throughout the day.

The easiest example to debunk is a question from a fellow developer. Imagine someone walks over to your desk or they ping you on Slack, because they have “one quick question.” Do you get annoyed at the interruption when you were in the middle of something important? You help out your teammate quickly and get back to work, trying to pick up where you left off. That’s a kind of interruption we complain about frequently, but I’m not convinced this is all that bad.

You are being disrupted but your team, of which you are only one member of the whole unit, is working smoothly. You unstuck …

How To Care If BSD, MIT, or GPL Licenses Are Used

The two recent posts about some individuals' choice of GPL versus others' preference for BSD and MIT style licensing has caused a lot of debate and response. I've seen everything as an interesting combination of very important topics being taken far too seriously and far too personally. All involved need to take a few steps back.

For the uninitiated and as a clarifier for the initiated, we're dealing with (basically) three categories of licensing when someone releases software (and/or its code):
Closed Source. Easiest to explain, because you just get nothing.GPL. If you get the software, you get the source code, you get to change it, and anything you combine it with must be under the same terms.MIT and BSD. If you get the software, you might get the source code, you get to change it, and you have no obligations about anything else you combine it with.The situation gets stickier when we look at those combinations and the transitions between them.

Use GPL code with Closed S…