doesn't work with direct link from Vimeo Pro

Yes , The Algorithm was change since version 3.0 to have better seeking and light resources

However , Google Drive , Vimeo and Youtube also other hosting that doesn’t give direct access to file are not guaranteed compatible anymore.

There might be a way to make it works but the video will not able to seek video and stuff.

and It will make the experienced worst.

In my opinion , If you just buy a Vimeo Pro because of this. You should get a refund

and Buy a shared hosting on Hostgator , Godaddy or any web hosting

and Host your file there

Using .htaccess to block all access except your server ip address

It should look like this

Deny From ALL
allow from (your server ip)

I think we should consult about buying a Vimeo Pro before taking action.

Thanks .

Hope this help

Juthawong Naisanguansee

and Thanks For Opening This Topic .

I try to announcement that Defa Protector is not compatible with Vimeo Pro anymore

It’s actually pretty easy to make it work with Vimeo. I looked at your code and it does a few things wrongly. Right now your code fetches then passes the wrong headers (it also makes 3 request per seek, which is overkill but can also break the flow between the servers). Use GET (not HEAD) and serve with 206 status not 200. Anyway, I’ve written my own code for this and it works just fine with Vimeo, including seeking, tested with both Firefox and Chrome. I may make a proper plugin when I have more time.

I noticed that you intentionally introduced the “headers already sent” error by putting session_start() in wp_head instead of wp_loaded, and now offer a 2nd plugin for which you ask money …

[rude comment moderated]

p.s. This kind of protection is pretty much useless. The .mp4 file can be found in the cache folder. For Firefox in Windows, that is %appdata%\local\temp\mozilla-temp-files\<some-big-file>. Just rename it to movie.mp4. This is even easier than installing DownloadHelper …

Your Act is against the law.

I warn you this time or I will report an international police to put you in jail

You disdain me with something I don’t intention to do.

The reason I use 200 because it can protect from the request that create by accessing the cache file. You use 206 , It was too easy to let the cache out of the program file.

I didn’t intentionally to create header already sent error. It was my mistake 3 month ago when I try to includetop.php which my old includetop.php have a header file to that add with the compatible guideline for Internet Explorer.

I don’t take an introduce the fix, I create the wordpress header already sent fix plugin to fix other wordpress plugin error and It was Free or Donation.

It is a Donationware and I didn’t make profit from them.

and This is my first reason why I don’t want you to have a demo because you will hack it anyway and other than just hacking it and send me a private email to fix .

You ruined other people business by showing everyone how to . I don’t know that it is real or not but It consider a violation against law.

You should reconsider yourself and have a little more think like an Adult.

Thanks

I just told you how to fix a bug in your own open source code, i.e. Vimeo does not send the same headers for HEAD as it does for GET (doesn’t respect the HTTP standard) and you need 206 for Firefox. It’s easy to fix your code with this information … you should be happy, not upset.

Your Act is against the law. I warn you this time or I will report an international police to put you in jail

The definition of open source is that anyone can download and modify the code. If you think that’s illegal then you either have serious issues, or you are too young to contribute with code on public forums. In any case, you should refrain from making public threats about putting people in jail. Nobody takes you seriously but you may get banned from these forums if someone reports you.

Lastly, yes, you did intentionally hide a flaw in your code and claim it’s all free but you are in fact turning a profit. Here’s what you say in the other thread about the error, which you clearly aware of:

If you have a Header Already Sent Error You can use our free and paid plugin to fix this . It cover all the universe. Download now at : https://www.juthawong.com/downloads/wordpress-header-already-sent-fix-plugin-for-free-and-paid/
Please don’t hating on me that I don’t give this for free on WordPress Repository and also please don’t burn my house.

Instead of fixing the error in the main code, you chose to write a separate plugin and to upload the so called “free” version of it to a website that requires one to register for cash prizes in order to download (link) while the other version you are selling for a price (screenshot). It’s your code, sure, but pretending and claiming it’s free and that you don’t get financial gains is defined as “a dick move“. It violates the principle of free and open source software. But good luck to you …

Regards.

p.s. The browser will always leave the file in the cache. That’s a widely known issue. I have my own code to hide Vimeo links using a similar technique and I suffer from the same issue (encrypted HLS would make it harder) but I believe in free software and free methods of access to information. You seem to believe in what’s called “security through obscurity”, which is unhealthy. Don’t be upset.

p.p.s. Stop editing my posts!

p.p.s. Stop editing my posts!

@normadize The plugin author can’t edit user’s posts but moderators can and did.

It’s really simple: do not make personal attacks and you won’t have to worry about it.

@juthawong I have issues with this statement.

Your Act is against the law.

I warn you this time or I will report an international police to put you in jail

That’s nonsense. Seriously, do not do that again.

If you really feel that way then you can remove your plugin from the repo. Or if you make more “I will report you” threats then your plugin can easily be removed from the WordPress repo for you.

This part is good.

In my opinion , If you just buy a Vimeo Pro because of this. You should get a refund

and Buy a shared hosting on Hostgator , Godaddy or any web hosting

and Host your file there

Because it explains that Vimeo Pro and similar services are designed to prevent that sort of sharing.

But these are support forums for your open source plugin and your plguin description is “Protect your html5 video from being downloaded or stolen automatically with the latest technology.”

The idea behind this plugin is flawed and how your plugin works is 100% completely open. If you do not want users to talk about how your plugin works then remove your plugin from this repository.

@jan, thanks for the comments. I thought it was the plugin author who was moderating. I had zero intentions of being rude, but wanted to point a dick move from the plugin author in order to prevent others (innocent and less savvy users) from wasting their money and time on the so called “free” fix he provides. I made it more clear in the above post.

Anyway , Let me talk to my lawyer office first

I’m already print it as my evidence.

Anyway , Let me talk to my lawyer office first

@juthawong You were warned.