SpK's View Methods - Part 1 - The 'mobile method' (and disguising as Facebook/Twitter)

Status
Not open for further replies.
Is one request to the stat server enough to get a single view on a video?
Also, how important is the correctness value for "rt", which is the playbacktime - the current request to stat server time?
 
Ok, so I followed IzSpk advice and connecting my HTC to the laptop I was able to finally see the correct mobile HTTP requests.

After confronting the parameters and re-reading several times the most important posts in this thread, it seems to me that if I'm going to send say 10k views to the same video, I can just replicate 10k times every one of the twelve HTTP requests that Fiddler collects while viewing that video, changing only the PLID parameter (if I understood correctly the 3 characters in base36 at the end of RDM value don't need to be changed every time).

Am I on the right track saying this or are there other dynamic parameters to be changed every time I send a view?
 
Ok, so I followed IzSpk advice and connecting my HTC to the laptop I was able to finally see the correct mobile HTTP requests.

After confronting the parameters and re-reading several times the most important posts in this thread, it seems to me that if I'm going to send say 10k views to the same video, I can just replicate 10k times every one of the twelve HTTP requests that Fiddler collects while viewing that video, changing only the PLID parameter (if I understood correctly the 3 characters in base36 at the end of RDM value don't need to be changed every time).

Am I on the right track saying this or are there other dynamic parameters to be changed every time I send a view?

It's the other way around: PLID will remain the same for each request and rdm will change the last 3 characters for each request. The other params that change are: rt, et, st
 
It's the other way around: PLID will remain the same for each request and rdm will change the last 3 characters for each request. The other params that change are: rt, et, st

That's not exactly what I meant, it seems to me that PLID will change for every view but will remain the same for every one of the 12 requests for the same view.
While I noticed that other parameters like the 3 ending characters of RDM change on every request, from what I understood reading other posts it seems that if you replicate them in order of succession as in Fiddler, the view get counted anyway (as long as you place in the request a new PLID).

Again, correct me if I'm wrong, I'm just guessing here.
 
yes, the PLID remains the same for all requests for a single view while the final three characters of the rdm change for each request.
That's not exactly what I meant, it seems to me that PLID will change for every view but will remain the same for every one of the 12 requests for the same view.
While I noticed that other parameters like the 3 ending characters of RDM change on every request, from what I understood reading other posts it seems that if you replicate them in order of succession as in Fiddler, the view get counted anyway (as long as you place in the request a new PLID).

Again, correct me if I'm wrong, I'm just guessing here.
 
yes, the PLID remains the same for all requests for a single view while the final three characters of the rdm change for each request.

But if I mantain the exact same 12 requests changing only the PLID will the view be counted or do I have to change also the final 3 characters of RDM in every request?
 
maybe it can work, but it is better to rebuild every time a new rdm, it is not difficult...
Code:
var chars = "abcdefghijklmnopqrstuvwxyz0123456789";
                var random = new Random();
                var result = new string(
                    Enumerable.Repeat(chars, 3)
                              .Select(s => s[random.Next(s.Length)])
                              .ToArray());

rdmpart = "m5zadq";
rdm = rdmpart + result;

But if I mantain the exact same 12 requests changing only the PLID will the view be counted or do I have to change also the final 3 characters of RDM in every request?
 
Pretty sure I have just figured this out as 'fiddler' tells me I'm getting s.youtube.com requests, unless the cheeky bastards lying to me ;)

If I have... Shit is gonna hit the Fan.. ;)

Fingers crossed I have as I'm one of the minority here that doesn't do this to make any money!

Just pure promotion.... For Myself :)
 
I may be wrong, but the bot I have created looks like it could be working.. could it not?

Here is a screenshot...
http://oi45.tinypic.com/280p21j.jpg

I'm generating new PLID's everytime and the s.youtube.com is being requested..

Would like to hear someones views on this..

Cheers guys
 
Yeah, I've done that, just seeing if you guys who know what they are talking about can see anything that wouldn't make it work. Roll on tomorrow I guess :)
 
I may be wrong, but the bot I have created looks like it could be working.. could it not?

Here is a screenshot...
http://oi45.tinypic.com/280p21j.jpg

I'm generating new PLID's everytime and the s.youtube.com is being requested..

Would like to hear someones views on this..

Cheers guys
$10 it won't count more than MAX 50 views ;)
 
After observing hundreds of real requests, I noticed that most PLIDS are 17 characters long (like the ones kindly generated by tb303 codes) but sometimes it gives 16 and even 15 characters PLIDS. Does it matter?

Does it make any difference if I use a real twitter (for ex) url on the &referrer=http%3A%2F%2Ft.co.... and also on the requestX.referer = "http://t.co........" ? Or a generic "http://www.twitter.com" would suffice on both cases?

The requestX.referer = "http://......" always comes from m.youtube.com according to Fiddler, so should I even bother trying a "twitter" ulr there?

I'm testing all possible variations until I get a solid result. Just don't want to waste time going in the wrong direction lol
 
Status
Not open for further replies.
Back
Top