Audio Galaxy kicks ass!

by Brian Enigma on September 18, 2001 4:42am

in Code,Dear Diary

Did I ever men­tion how cool Audio Galaxy is?  I have music before it has been released.  HOW COOL IS THAT?!?!  Unfor­tu­nately, I see two prob­lems with Audio Galaxy at the present time.  One is a design deci­sion and the other is a polit­i­cal decision. 

Design-wise, AG uti­lized a cen­tral­ized server.  Unlike Gnutella, IRC, and sev­eral other pro­grams, it is NOT decen­tral­ized.  This means there is a sin­gle point of fail­ure.  A sin­gle Jugu­lar vein for lawyers and record execs to slice.  When “audiogalaxy.com” is killed, the sys­tem no longer works.  The client you run talks to a cen­tral server.  Your web browser user inter­face talks to a cen­tral server.  Take away the server and you have nothing–except for a bunch of bro­ken client pro­grams.  And don’t even men­tion the band­width that the server must be suck­ing up.  Every­one talks to it, so there must be enough con­nec­tiv­ity for every­one to talk.  That costs mucho bucks. 

Political-wise, AG is closed source.  This means that if-and-when it gets taken down, nobody can grab a copy and set up their own server.  Hell, you can’t even make your own clients.  You HAVE to use their clients.  Blah.  This puts them into a lit­tle bit of a power posi­tion, in that you get to see THEIR ads and installing the Win­dows soft­ware (at least used to–I didn’t see it when I just now installed) installs some spy­ware that tracks your brows­ing habits and such.  Sure, they need the income from their ads to pay for the band­width of the cen­tral server, but it means that nobody out­side of their orga­ni­za­tion can cre­ate a client, run their own server, fix bugs, or add features. 

What would be cool would be to write a clone of some sort.  The eas­i­est clone (which is not easy, by any stretch) would involve writ­ing an Open Source dupli­cate of their cen­tral­ized server soft­ware.  This, I am sure, would mean some PHP, some MySQL, and some C++ for the clients and prob­a­bly a server dae­mon.  Not too dif­fi­cult, but very time con­sum­ing.  Mak­ing it open source means peo­ple could run their own servers (although this means that splin­ter groups would sit in iso­lated pools and share only amongst them­selves, not the rest of the world).  The next log­i­cal step would be to have the servers talk to one another.  This is what Nap­ster servers ended up doing after it had taken off.  Of course, this adds even more complexity.

Anyway–food for thought.  Some­one should prob­a­bly do some­thing like this before AG gets shut down.  If I get more moti­vated, I might make a start at this.  Prob­a­bly not.

Share and Enjoy:
  • Digg
  • Reddit
  • del.icio.us
  • StumbleUpon
  • Yahoo! Buzz
  • Facebook
  • Google Bookmarks
  • Technorati

If you liked this post, you may also enjoy:

  1. LJProxy: From friend-locked Live­Jour­nal posts to Google Reader
  2. Azureus replace­ment?
  3. Warn­ing: work­fil­ter / Warn­ing: technobabble
  4. Java Woes
  5. Bet­ter liv­ing through xgrid

Leave a Comment

Previous post:

Next post: