Old 3rd November 2002, 12:46   #1
Jodash
Junior Member
 
Join Date: Mar 2001
Posts: 10
ripping streams

is there anyway that you can tell if there is someone ripping your streams,as i seem to have one ip jumping in every 5 mins "starting stream (UID: 4)[L: 1]{A: WinampMPEG/2.8}(P: 0)" is what im getting on my log


tia

best in oldies
Jodash is offline   Reply With Quote
Old 3rd November 2002, 15:50   #2
Jay
Moderator Alumni
 
Jay's Avatar
 
Join Date: May 2000
Location: Next Door
Posts: 8,942
if they mask their user agent then there is really not a way to tell
Jay is offline   Reply With Quote
Old 3rd November 2002, 17:07   #3
Dedicated|Moku
Member
 
Join Date: Nov 2002
Location: San Jose
Posts: 65
Send a message via ICQ to Dedicated|Moku Send a message via AIM to Dedicated|Moku
The streamripper I sometimes use is just a plugin for winamp...

If he is using that, there is no real way to tell.
Dedicated|Moku is offline   Reply With Quote
Old 3rd November 2002, 17:22   #4
Jodash
Junior Member
 
Join Date: Mar 2001
Posts: 10
thks
Jodash is offline   Reply With Quote
Old 3rd November 2002, 21:53   #5
Jay
Moderator Alumni
 
Jay's Avatar
 
Join Date: May 2000
Location: Next Door
Posts: 8,942
actually I was sitting around the other night thinking about it and there are things you can do to make it inconvenient to rip your stream. One method would require that you make a script or program update the title of the song with dynamic information such as the amount of time the track has played or ratating news. On programs like StreamRipper32 the song will be cut up by each update. Not sure about the plugin. Another thing you can do is crossfade your tracks and mix promos into the sound of the end or beginning of the track. This will limit the popularity of the track on p2p networks and possibly the person ripping the stream will find it sounding no different then a rip off of normal over the air radio. If you use SqrSoft to crossfade your tracks it actually has the added benefit of offsetting the current song meta tag 10 or so seconds depending on the size of the buffer, so that the end of the track gets cut off and the beginning of each track gets the prior track's sounds. Just some thoughts. There is nothing you can do to completely eliminate streamripping but there are things you can do to make it less convienient to do.
Jay is offline   Reply With Quote
Old 5th November 2002, 01:32   #6
DJ AmPs
Major Dude
 
DJ AmPs's Avatar
 
Join Date: Mar 2002
Location: g
Posts: 1,603
i created a php script that bans anybody with stream or freeamp in the user agent. since it's a php script, the only way i could make it run on its own is to add it to the server stats script on the home page -- so it checks every time someone pulls up the website; which is about every 5 min or so. so basically the listeners are banning themselves now


many times rippers with a "fake winamp" option show up as winamp/mpeg 2.0 (instead of the usual 2.6 or 2.7). If kicked and it connects again instantly to the same relay, it's probably a ripper. Many times they give it away by connecting simultaniously with both mpeg2.0 and mpeg2.7

For the smart people who connect once with the proper useragent, they are home free.

I also thought about the active title updating throughout a song, but failed to find any tools to do that automatically. any clues?

-amps
DJ AmPs is offline   Reply With Quote
Old 5th November 2002, 17:38   #7
Romilar_D
Member
 
Romilar_D's Avatar
 
Join Date: Sep 2000
Posts: 68
Send a message via ICQ to Romilar_D
Try a url call of the form
Quote:
http://www.host.com:portnumber/admin.cgi?pass=Password&mode=updinfo&song=SongTitle&url=http://someurl.com
to your server. This will change the meta info a listener recieves.
Romilar_D is offline   Reply With Quote
Old 5th November 2002, 20:57   #8
Jay
Moderator Alumni
 
Jay's Avatar
 
Join Date: May 2000
Location: Next Door
Posts: 8,942
Quote:
Originally posted by DJ AmPs
i created a php script that bans anybody with stream or freeamp in the user agent. since it's a php script, the only way i could make it run on its own is to add it to the server stats script on the home page -- so it checks every time someone pulls up the website; which is about every 5 min or so. so basically the listeners are banning themselves now


many times rippers with a "fake winamp" option show up as winamp/mpeg 2.0 (instead of the usual 2.6 or 2.7). If kicked and it connects again instantly to the same relay, it's probably a ripper. Many times they give it away by connecting simultaniously with both mpeg2.0 and mpeg2.7

For the smart people who connect once with the proper useragent, they are home free.

I also thought about the active title updating throughout a song, but failed to find any tools to do that automatically. any clues?

-amps
Yea I wrote a little shoutcast bot that does this in real time. You can write a rules list, if I can get all the bugs out of it it would be a very powerful app, I am trying to get it finished by RTB 1.0.
Jay is offline   Reply With Quote
Reply
Go Back   Winamp & Shoutcast Forums > Shoutcast > Shoutcast Discussions

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump