Beta
×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Comments

top

Another ATM Maker Pwned by Googling

typical Re:pwned haha (252 comments)

Listen up kids

Listen up, kids

"owned", "pwned", "h4x0red", "l33t",

"owned", "pwned", "h4x0red", and "l33t" [no comma]

was interesting for about 5 minutes 5 years ago,

were interesting for about five minutes five years ago;

Stop using them, it's pathetically annoying.

Stop using them; it's pathetically annoying.

Try using some proper English for once.

Yes.

more than 7 years ago

Submissions

typical hasn't submitted any stories.

Journals

top

Legal Audio Streaming

typical typical writes  |  more than 9 years ago

Currently, many employers are very negative on the idea of music being played at work, due to concerns about copyright infringement. While we may not be able to legally get popular music for free at work, we *can* enjoy it at a very reduced cost.

It seems that it would be a worthwhile idea to modify one of the many streaming audio servers out there, such as Shoutcast, to support a "library mode". A user would be able to stick a CD in the CD drive of a running server and have the thing automatically looked up on CDDB, ripped, and cover art downloaded. Users would be able to log in to the server and create playlists of the available albums. They could click on a "play" link in their webbrowser, and the server would begin streaming audio data from their playlist to their audio player.

The main difference from any other audio server is that this one would act as a "library", where each album is "checked out" by a user for as long as it is in use. Whoever starts playing an album first "locks" it. Any other users who have the album in their playlist will simply have that album skipped over. When the locking user has finished hearing the audio from the album, the server unlocks the album and acquires a new album from the server.

This is significant, because this is legal, even though it allows everyone to enjoy the music. Have a nice big box next to the server, and every time you rip a CD to the server, toss the CD in the box, and you have proof of legality.

The main fact that this takes advantage of is that most people don't care about strict inter-album ordering when playing music (as a matter of fact, some people play individual tracks on shuffle mode). In return, it provides a large music library very inexpensively. If each person at a 50 person company brought in a handful of CDs that they like listening to at work, a large and varied audio library is created.

Other ideas:

* It might be desirable to label each ripped album with the contributor's name. That way, if the contributor ever wants their CD back, it could be handed back and the ripped audio easily purged en-masse ("delete all albums from user bob7").

* This could easily become a self-funding open-source project if it was a decent piece of software that included "buy this CD" links to a vendor that was willing to provide a cut of money for referral links. (If one really wanted to get fancy, one could provide direct "buy and download to server" links for iTunes and similar services.)

* This is a good example of a system where "phone-home" capability would allow a TiVo-like suggestion system.

Slashdot Login

Need an Account?

Forgot your password?

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>