You can find all binaries, including the one for iOS and Android, on our website, signed by the core developers. If you trust us, it is totally up to you. GitHub is used as a mirror only as we run our own infrastructure so quite obviously we are not using the GitHub release process.
This is untrue. Apple is just publishing it in different regions at different times. I had a call with them 3 hours ago and they told me that it can take up to 12 hours (!) until all regions have it.
According to our WWDR contact, there is no way to blacklist trademarks you own on the App Store, so we need to send DMCA take-down notices for all infringements. We sent 39 against 48 apps last year and it takes apple up to 3 months to pull the apps, even for obvious violations.
This is because you downloaded our app a while ago and we did something so you can re-download it to your device now. This is in preparation of our actual release in the next days (we won't release 2.4.0 publicly but 2.4.1 because of a regression).
This is the last in a long row of copyright violations permitted by Apple to the store despite app review and multiple complaints by us in the past.
This binary is based on buggy, old pre-production code, includes ads and absolutely non-working integrations to Dropbox, etc. because the provider did not set the private keys correctly.
The official app currently awaits review and will hopefully be out soon. It will be stable, ad-free and with full support for the clouds.
This is one of the reasons why you have to use a wrapper for the VLC binary to execute it within a root environment. Said wrapper is usually in an extra package on Linux and not provided on Windows and OS X (it can be compiled manually of course).
Like 10 people per year complain about not being able to run VLC as root, but then again, why should you?
VLC is free (both as in beer and in speech) and will always be :)
However, you can donate to our non-profit organization, which e.g. paid the iPad I used for development, as well as a whole lot of other things around VLC and further VideoLAN projects.
Sorry, but we aren't responsible for 3rd apps who try to use VLC's functionality in a completely unsupported way. Stuff within an application bundle is considered private and can change anytime.
Anyway, we informed the Handbrake devs about a month prior to VLC's 2.0 release, which is why they came up with a fix in their latest version shortly after.