[squid-users] RE: YouTube Resolution Locker

2014-08-28 Thread Stakres
Hi All,

New version 1.10 including YouTube, Vevo and DailyMotion videos.
https://sourceforge.net/projects/youtuberesolutionlocker/

Have fun 

Questions and/or comments are welcome...

Bye Fred



--
View this message in context: 
http://squid-web-proxy-cache.1019090.n4.nabble.com/Video-Resolution-Locker-tp4667042p4667420.html
Sent from the Squid - Users mailing list archive at Nabble.com.


[squid-users] RE: YouTube Resolution Locker

2014-07-29 Thread Stakres
Hi Eliezer,
If the URL is the same, meaning using the same locked resolution for the
same video, the deduplicated ID will be the same so it'll come from the
existing Squid cache.
I agree with you if the admin changes the resolution the ID will be
different so it'll not be taken from the cache.

Bye Fred



--
View this message in context: 
http://squid-web-proxy-cache.1019090.n4.nabble.com/YouTube-Resolution-Locker-tp4667042p4667096.html
Sent from the Squid - Users mailing list archive at Nabble.com.


Re: [squid-users] RE: YouTube Resolution Locker

2014-07-28 Thread csn233
On Sat, Jul 26, 2014 at 7:52 PM, babajaga augustus_me...@yahoo.de wrote:
 Not correct. It is possible to cache youtubes content using StoreID.

Still possible to cache after YT changed/randomized their id=...
parameter for the same videos?


[squid-users] RE: YouTube Resolution Locker

2014-07-28 Thread Stakres
Hi csn233,
If you keep the same resolution, yes it'll be cached.

Bye Fred



--
View this message in context: 
http://squid-web-proxy-cache.1019090.n4.nabble.com/YouTube-Resolution-Locker-tp4667042p4667089.html
Sent from the Squid - Users mailing list archive at Nabble.com.


Re: [squid-users] RE: YouTube Resolution Locker

2014-07-28 Thread Eliezer Croitoru

No it will not..
Since the ID is being changed from a stub id per video to using some 
hashing algorithm with some salt added into it there is no basic way to 
use the same ID for the same video.


Eliezer

On 07/28/2014 08:21 PM, Stakres wrote:

Hi csn233,
If you keep the same resolution, yes it'll be cached.

Bye Fred





[squid-users] Re: YouTube Resolution Locker

2014-07-26 Thread Stakres
Hi All,

Feel free to modify the script (client side) to do not send all requests.
As Cassiano said, only the YouTube urls need to be rewritten...

Bye Fred



--
View this message in context: 
http://squid-web-proxy-cache.1019090.n4.nabble.com/YouTube-Resolution-Locker-tp4667042p4667054.html
Sent from the Squid - Users mailing list archive at Nabble.com.


Re: [squid-users] Re: YouTube Resolution Locker

2014-07-26 Thread Amm


On 07/26/2014 12:05 PM, Stakres wrote:

Hi All,

Feel free to modify the script (client side) to do not send all requests.
As Cassiano said, only the YouTube urls need to be rewritten...


My point here is that you have not mentioned anywhere that your script 
collects information.


Script is made by Unveiltech and it sends all data to Unveiltech servers.

Your server can very easily send redirection to their own server and 
fetch username OR password of any site. (If end user is not technically 
sound)


For example your server can easily redirect http://login.google.com to 
http://storeid.unveiltech.com/login.google.com/ (which looks exactly 
same as Google login page). End user will not even know what is happening.


Not sure if you did this on purpose OR you are new to programming that 
you did not realize this huge security and privacy angle.


Additionally your script is one small function modification EXAMPLE 
redirector script. A real script would include full logic of youtube 
resolution locker (what your storeid server does currently).


No offence meant, please. I am just warning other users if they try to 
use this php script, there is huge security risk.


Regards,

PS: Sorry for being off-topic on squid mailing list.

AMM


[squid-users] Re: YouTube Resolution Locker

2014-07-26 Thread Stakres
HI Amm,

Everyone is free to modify the script (client side) by sending YouTube urls
only, no need to send all the Squid traffic.
Then, we collect nothing, the requests are reviewed by the script and it
returns modified urls to lock the YouTube resolutions.
We do not make any statistics, we do not share data with internal or
external teams.

We're not new to programming and we DO realize security and privacy
issues, you're free to use the API or not, we force nobody.
Everyone is free to spend time for developing a similar function or use ours
for a quick solution.

The one small functionis for free to all, we spent time to develop this
API and we're a commercial company. So, do you work for free ? we do not.
If you are interested by the complete API, no problem just contact us and
I'm sure we will find an arrangement 

No problem for the No offence, all comments are welcome.

PS: Sorry for being off-topic on squid mailing list, too.

Bye Fred



--
View this message in context: 
http://squid-web-proxy-cache.1019090.n4.nabble.com/YouTube-Resolution-Locker-tp4667042p4667056.html
Sent from the Squid - Users mailing list archive at Nabble.com.


Re: [squid-users] Re: YouTube Resolution Locker

2014-07-26 Thread Amos Jeffries
On 26/07/2014 8:36 p.m., Stakres wrote:
 HI Amm,
 
 Everyone is free to modify the script (client side) by sending YouTube urls
 only, no need to send all the Squid traffic.
 Then, we collect nothing, the requests are reviewed by the script and it
 returns modified urls to lock the YouTube resolutions.
 We do not make any statistics, we do not share data with internal or
 external teams.
 
 We're not new to programming and we DO realize security and privacy
 issues, you're free to use the API or not, we force nobody.
 Everyone is free to spend time for developing a similar function or use ours
 for a quick solution.
 
 The one small functionis for free to all, we spent time to develop this
 API and we're a commercial company. So, do you work for free ? we do not.
 If you are interested by the complete API, no problem just contact us and
 I'm sure we will find an arrangement 
 
 No problem for the No offence, all comments are welcome.
 
 PS: Sorry for being off-topic on squid mailing list, too.
 
 Bye Fred


It would be better practice to publish a script which is pre-restricted
to the YT URLs which your server is useful for and your initial
advertisement stated its purpose was.

That would protect your servers from excessive bandwidth from naive
administrators, help to offer better security by default, and protect
your company from this type of complaint and any future legal
accusations that may arise from naive use of the script.

Amos



[squid-users] Re: YouTube Resolution Locker

2014-07-26 Thread Stakres
Hi Amos,

You're totaly right here.
We'll prepare a version 1.01 including ACL restrictions...

Bye Fred



--
View this message in context: 
http://squid-web-proxy-cache.1019090.n4.nabble.com/YouTube-Resolution-Locker-tp4667042p4667058.html
Sent from the Squid - Users mailing list archive at Nabble.com.


Re: [squid-users] Re: YouTube Resolution Locker

2014-07-26 Thread Amm


On 07/26/2014 02:36 PM, Amos Jeffries wrote:

On 26/07/2014 8:36 p.m., Stakres wrote:

HI Amm,

Everyone is free to modify the script (client side) by sending YouTube urls
only, no need to send all the Squid traffic.
...
Bye Fred


It would be better practice to publish a script which is pre-restricted
to the YT URLs which your server is useful for and your initial
advertisement stated its purpose was.

That would protect your servers from excessive bandwidth from naive
administrators, help to offer better security by default, and protect
your company from this type of complaint and any future legal
accusations that may arise from naive use of the script.

Amos


Yes and also mention on top of script that Script sends URL data to 
your servers and giving link to privacy policy and if / how you use the 
URL data.


Otherwise you may really have legal issue for capturing data without 
permission. (Even if you directly throw it in dustbin you can still be 
sued. - just my two cents)


Amm.


[squid-users] RE: YouTube Resolution Locker

2014-07-26 Thread Stakres
Hi James,

All is in the title YouTube Resolution Locker, so...
The API is there to lock the resolution to low value, we think the API to
help in reducing bandwidth as HD videos consume a lot.

Regarding bandwidth limiter with YouTube, do you think Squid admins need a
special script ?
There are plenty of samples explaining how to use Quota with Squid... ;)

Bye Fred



--
View this message in context: 
http://squid-web-proxy-cache.1019090.n4.nabble.com/YouTube-Resolution-Locker-tp4667042p4667062.html
Sent from the Squid - Users mailing list archive at Nabble.com.


RE: [squid-users] RE: YouTube Resolution Locker

2014-07-26 Thread James Harper
 Hi James,
 
 All is in the title YouTube Resolution Locker, so...
 The API is there to lock the resolution to low value, we think the API to
 help in reducing bandwidth as HD videos consume a lot.
 
 Regarding bandwidth limiter with YouTube, do you think Squid admins need
 a special script ?
 There are plenty of samples explaining how to use Quota with Squid... ;)
 

Actually after I hit send I realised that it probably wouldn't work anyway, 
unless youtube really did use a consistent url domain name for their content 
delivery network... the tricky bit wouldn't be the quota itself, it would be 
identifying the urls/ip's to limit. A script may be required to identify the 
current list.

James


[squid-users] RE: YouTube Resolution Locker

2014-07-26 Thread babajaga
 it probably wouldn't work anyway, unless youtube really did use a
consistent url domain name for their content delivery network..
Not correct. It is possible to cache youtubes content using StoreID.
Additionally, locking the resolution is much more trivial, as the requested
youtube-URL contains the requested resolution as one of the ... pars. Just
needs modification.
I run a free youtube proxy myself, for years already, and also do the
resolution locking myself, to low res, to avoid overload of the proxy. 




--
View this message in context: 
http://squid-web-proxy-cache.1019090.n4.nabble.com/YouTube-Resolution-Locker-tp4667042p4667064.html
Sent from the Squid - Users mailing list archive at Nabble.com.