Regarding the 'mobile method'

Nevermind it, don't even bother.
so if i just use the same one over and over again it won't matter?

and am i even doing it it right? I am entering my link over and over again into the browser and clicking enter is that all i have to do?

Thanks for the help izSpK cause i have no clue what i am doing
 
You have to change the et, st, and rt values.

I made this not long ago (for normal views, not mobile, but it's still the same):

Code:
1st request
rt        1.489
et        0.058
st        0.058
bt        0.629
lact    714

2nd request
rt        11.582
et        10.036
st        0
bt        10.013
lact    10807

3rd request
rt        21.572
et        20.038
st        10.036
bt        8.603
lact    20796

4th request
rt        31.574
et        30.038
st        20.038
bt        10.900
lact    30797
It's pretty easy to figure out what's going on. Each request is made at a 10 second interval.

and then cycle through them by entering them in the browser and clicking enter?
 
and then cycle through them by entering them in the browser and clicking enter?

Doing that will not generate a new RDM and PLID value. You may also need to visit the /watch page to get new cookies but I'm not too sure. You need to make a legit bot, not just visit the url over and over.
 
Doing that will not generate a new RDM and PLkID value. You may also need to visit the /watch page to get new cookies but I'm not too sure. You need to make a legit bot, not just visit the url over and over.
can i add you on skype?
I just have some questions ( thanks for the help)
mines : Jaredsskypeaccount
 
i've got it working but where are you scraping the plid from? as of now i'm just scraping plids from the nonmobile page and using them for the requests.

it hasn't been long enough for me to see if it works but if i'm supposed to be scraping it from somewhere else it would help to know now. thanks.
That should work, although I haven't done it before. I don't know how strict they are with verifying playback ID tokens. Let me know how it goes via PM.
 
i've got it working but where are you scraping the plid from? as of now i'm just scraping plids from the nonmobile page and using them for the requests.

it hasn't been long enough for me to see if it works but if i'm supposed to be scraping it from somewhere else it would help to know now. thanks.
Yeah i was confused about this also. There is no way to scrape it from the mobile watch page. I have figured out how both RDM and PLID are generated though. For plid, it's made up of two parts. The first part is the current date/time in milliseconds and encoded using base36. The second part is a very large randomly generated number. It is also encoded in base36. The two parts are merely appended to together.

RDM is also made up of two parts. The first is the build_id (can be scraped) that has been encoded in base36. The second is a smaller randomly generated number that is also encoded in base36.
 
Last edited:
Haha yeah magic views sure does work and I'm naming some pretty side income from selling the views all the buyers cAre about are the views i doubt they even know seo ranking etc :evil:
 
Haha yeah magic views sure does work and I'm naming some pretty side income from selling the views all the buyers cAre about are the views i doubt they even know seo ranking etc :evil:
Not nice ripping people off.
 
10k? you have a program for free, that will probably not work next week 10k for $5 isn't decent at all.
Maybe if you had put some time into the method of providing the views yourself..Give it 24hours there will be people selling 1Mil views for $5 on there to get as many sales in before it stops working again
 
Yeah i was confused about this also. There is no way to scrape it from the mobile watch page. I have figured out how both RDM and PLID are generated though. For plid, it's made up of two parts. The first part is the current date/time in milliseconds and encoded using base36. The second part is a very large randomly generated number. It is also encoded in base36. The two parts are merely appended to together.

RDM is also made up of two parts. The first is the build_id (can be scraped) that has been encoded in base36. The second is a smaller randomly generated number that is also encoded in base36.
Finally a very good post here in BHW. Good one man!
 
all they care about is the view count :) 10k on fiverr.com 10k for $5 is decent :)

I hope you realize that rtsp flooding can now get your youtube accounts banned in a few days. Not to mention that if you deliver more than 1 million views, your network provider is going to get a nice shiny formal email about you and your funny network activity.

Magicviews wasn't intended for video flooding, it was intended to be a proof-of-concept, to demonstrate the bug in action, and that's why I only released a limited version.
 
I hope you realize that rtsp flooding can now get your youtube accounts banned in a few days. Not to mention that if you deliver more than 1 million views, your network provider is going to get a nice shiny formal email about you and your funny network activity.

Magicviews wasn't intended for video flooding, it was intended to be a proof-of-concept, to demonstrate the bug in action, and that's why I only released a limited version.

Lol, damn. Imagine trying to explain this to your ISP.
 
How would you tell that to every person exploiting it ? should've thought about it in the first place :).

This is very recent, and it only happens with the cracked version, not the version I released (since it's been weakened on purpose)
 
Ha, most don't care, they will blast their videos till the sun don't shine (or receive a cease and desist). This power was never meant to be in the hands of the general public that does not respect and know how to properly utilize such power.

Then there are even less intelligent folks under the assumption that if they release such information to the general public, it will boost their "perceived ego" along with alternative motives, such as trying to kill off a method in an attempt to stiffle competition and remain in control. The latter rarely works though and in most cases backfires, as killing one method simply increases efforts to discover another. Reign over a kingdom rarely lasts.

Finally, there are a very rare few who truly believe in the spirit of open knowledge and for all the right reasons. But even some of them do not realize that where exploits are concerned, longevity will best be served by keeping such knowledge to ones self.
 
Last edited:
Ha, most don't care, they will blast their videos till the sun don't shine (or receive a cease and desist). This power was never meant to be in the hands of the general public that does not respect and know how to properly utilize such power.

It's not a C&D, it falls under "denial-of-service".
 
Back
Top