izSpK
BANNED
- Sep 5, 2010
- 1,511
- 1,688
Nevermind it, don't even bother.Can it be the same code or do i have to get a different one each time?
Nevermind it, don't even bother.Can it be the same code or do i have to get a different one each time?
so if i just use the same one over and over again it won't matter?Nevermind it, don't even bother.
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):
It's pretty easy to figure out what's going on. Each request is made at a 10 second interval.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
and then cycle through them by entering them in the browser and clicking enter?
can i add you on skype?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.
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.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.
do you think you could help me?alright, thanks, ill keep you updated.
Not nice ripping people off.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.
Finally a very good post here in BHW. Good one man!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.
I have been working on something and i think its almost ready. just need some more test and share it with you guys![]()
all they care about is the view count10k 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.
How would you tell that to every person exploiting it ? should've thought about it in the first place.
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".