DopeLabs

yea its not really disruptive other than the fact that it throws off some of the stats like avg listener time, stream hits, etc… at most the log files are a little bit bigger.. but not by much. and at most your looking at what… maybe 320+kbps per listener from a shoutcast server… so thats no worries.. but i have it sorted out now… im just sending all the mta client requests to a dedicated server for mta tune ins. thanks for all the info (everyone)… much appreciated!

yea i could pretty much see driveby's as they happened…. 60+ clients all tuning in for about 3 seconds…"heeey cooolaiid" and honestly, with the way that shoutcast is built, im willing to bet in that short amount of time they dont even hear any music because of the buffer when connecting… which makes about 80% of the requests pointless… shoutcast servers are light, fast, and easy to spawn in an instance, all you would need to do is set the relay url and port and fire it up.. leave it connected until the last person disconnects then do the same yourself… maybe it would also be a good idea if your specifically listing stations… maybe send them a quick email letting them know you want to do so, and explain what that involves… i can bet that most are willing … im just wondering if theres someway i can contribute.. all this looks pretty cool… if people would use it i would be totally down for building some kind of central service that these radio apps could use.. can be an aggregate of all their current lists, and a submission form for new ones. they submit a station name and a url to the playlist file, script curls the pls file, puts the host ip and port at the end of a config template and saves a fresh copy.. a shoutcast server will fire and make a single connection to the radio station the first time a client requests the customlzed pls file form me. will stay connected until the last person disconnects, rinse, repeat…. its pretty easy, can even take a soundcloud or youtube or whatever audio source and offer it up. im not sure if the game supports it, but i can do all the same with streaming video, static of live content… then these guys can put custom or live video content on the tv screens they installed in the seats ha.. comical =] granted this also means that you will need to have half decent bandwidth depending on the content being streamed.

thanks hex... just wanted to get an understanding is all..it seems like its pretty much free reign for script writers and ill prob never track them all down… what will most likely end up happening is any mta client request will get redirect to dedicated mta radio servers… also.. ads are shitty, im sure everyone can agree..(except for the advertisers i guess) all my content is ad free.. and i dont think you could pay me enough to put in stream ads.

your claim of 'only the person who initiates it' is incorrect… 200 mtasa.dubstep.fm GET /listen.pls HTTP/1.1 86.176.96.217 BASS/2.4 200 mtasa.dubstep.fm GET /listen.pls HTTP/1.1 85.24.169.143 BASS/2.4 200 mtasa.dubstep.fm GET /listen.pls HTTP/1.1 81.237.199.73 BASS/2.4 200 mtasa.dubstep.fm GET /listen.pls HTTP/1.1 78.69.66.56 BASS/2.4 200 mtasa.dubstep.fm GET /listen.pls HTTP/1.1 83.109.39.185 BASS/2.4 200 mtasa.dubstep.fm GET /listen.pls HTTP/1.1 5.14.9.150 BASS/2.4 200 mtasa.dubstep.fm GET /listen.pls HTTP/1.1 78.70.121.73 BASS/2.4 200 mtasa.dubstep.fm GET /listen.pls HTTP/1.1 83.9.187.55 BASS/2.4 200 mtasa.dubstep.fm GET /listen.pls HTTP/1.1 78.69.70.114 BASS/2.4 200 mtasa.dubstep.fm GET /listen.pls HTTP/1.1 86.179.233.61 BASS/2.4 200 mtasa.dubstep.fm GET /listen.pls HTTP/1.1 90.207.200.2 BASS/2.4 200 mtasa.dubstep.fm GET /listen.pls HTTP/1.1 86.15.143.108 BASS/2.4 200 mtasa.dubstep.fm GET /listen.pls HTTP/1.1 80.216.227.68 BASS/2.4 all within about a half second…. so please tell me again its only the client that initiates it… the above is just a small example… my servers are not over stressed, and the only thing forcing radio's to play from every web page would do is cause the shoutcast to reach their max users as specified in the config file. but i would also get an alert, see the logs, and null route your ip(s).. nothing will be 'clogged'… i am just trying to understand what this whole process is about, because as i mentioned before, it effects the normal metrics and stats in a negative manor, i was asked to investigate, so i am… and after watching the behavior of these scripts for a while im just trying to figure out who i need to contact to talk about a better and more efficient method for this… im pretty curious how all this stuff works.. because if you can make other players go out to the web and download a file just by being in earshot during gameplay, i wonder what the limits are =]

yea i dont know what their called in relation to the game.. but from what i could search up.. it looks like a modification of a siren function and instead of playing a siren, it plays a stream… having all the clients go out and each make an http request for a file? your doing it wrong… and again.. is this something that the server has to support, or can any client use it on any server? the potential for abuse here is pretty silly….

i will also mention that i do not play nor run an mta server… i am a hosting provider.. mostly radio… and the way that these mta clients are designed is bad. from what i have noticed by tailing my access logs, and from playing gta/etc, it seems that someone playing a station in car can drive past a group of people, which forces all of those people to then make an http req for the pls file, thus they all hit the stream urls, counting as a stream hit, throwing off the metrics and stats… this is bad… i find it amazing that people are ok with their computers going out to the web and downloading and executing a file, which was triggered by someone driving past in a car… this is such a terrible security risk, and its just begging for someone to exploit it most of these seem like 'drive bys' as they are only tuned into the station for a few seconds…. i just took a peak at the resource list search results.. and this is, well…. had no idea there were that many…

i own a hosting company for web and shoutcsat, etc… the process for how clients/players tune in isnt very good at all… BASS/2.4, SA-MP, and MTA:SA are the http user agents im seeing grabbing the tune in files and im guessing that last one is the 'suggested' or default setting… anyways…im not sure how many stations are listed in these apps, but i seem to be hosting a number of them, and… i want to avoid redirecting all requests coming from mta to an alternate radio server with a loop of justin beiber…. so, please chime in