Tech Support

In terms of EU enforcement of GDPR regulation: https://en.wikipedia.org/wiki/General_Data_Protection_Regulation we would like to make a statement on which personal data is stored and processed in KVS. Cookies KVS is using some impersonalized cookies to facilitate traffic stats calculation. These cookies store the following info: Which URL user first came from. Which URL user first came to. Which IPs user had when navigating through site. Whether user has already visited this site during last 24 hours. Whether user is a registered member or not. This info is not stored anywhere in KVS or server-side; it is stored in user's browser and can be deleted using browser functionality any time. KVS database KVS database stores the following information for every user: Personal data that was specified by users during registration or when filling their profiles, e.g. username, display name, email, other text data users opted to specify. This information may be visible to public depending on theme design. IP address and country users had during registration. This information is stored for security reasons. List of all logins during last 365 days, including IP address, country and browser type. This information is stored for security reasons. When using online payments, KVS will store information provided by payment system for each transaction. This information is stored for accounting reasons and doesn't contain any personal data (4.0.2 fix). KVS is not using the information described here for any decision making, deep learning, exporting or anything else that may result in commercial benefits. You can configure KVS to delete all IP / country data automatically. In order to this you should edit /admin/include/setup.php file and search for this option: $config['safe_mode']="false"; Change this option to true, which will force KVS to delete all IPs / countries / logs stored in database: $config['safe_mode']="true"; Deleting personal info from KVS Users can choose to request their profiles to be removed from KVS powered site. This functionality is provided by member_profile_delete block and may or may not be supported by some themes. In any way if such functionality is missing users should be able to contact support for their profiles to be deleted. Profiles can be deleted from admin panel only. When profile is deleted, all data connected to this profile gets fully deleted, including IPs, logs, profile data (4.0.2 fix will delete logs). Admins should decide manually how to handle content uploaded by user: it can be either deleted as well, or kept available on the site by changing this content's ownership.

4.0.2 update is ready in beta mode: https://www.kernel-video-sharing.com/forum/forum/general-discussion/announcements/758-kvs-4-0-2-update

Update status 4.0.2 update status is FINAL. You can download update in KVS client zone for all your licenses: Update procedure Any project starting from 3.0.0 can be updated to 4.0.2 with one only procedure. Depending on your current KVS version, update procedure may contain additional steps for older versions. You must use KVS update plugin in order to update your project. For update you will need: - KVS update ZIP archive for your project and its hash code for update plugin (contact support in beta phase to get these). - FTP connection to your project so that you can upload files. If your project's version is 3.9.0+, the update procedure is standard and nothing special is expected: Create backup using Backup plugin. Upload update ZIP into KVS update plugin and specify hash code. KVS update plugin will notify you if there are any custom changes in KVS system files, which will be overridden by update (player skins are not checked here, so they will be silently updated if have custom changes). KVS update plugin will update database automatically. You will need to copy files from the archive on top of your project using FTP or filesystem copy. Please make sure you are NOT USING sync functionality in your FTP client, which will delete many files on your server, because obviously update archive contains only part of all files. What you need is just to drag and drop files from update archive on top of your project root folder and confirm their re-writing (excluding _INSTALL folder, it doen't need to be copied). KVS update plugin will verify the updated files and finalize update procedure. You can use System audit plugin to verify everything looks good. If your project's version is before 3.9.0, the update procedure will be difficult and will include cache reset for the whole site (if you have much traffic it can make your project to be unavailable for some time). Also 3.9.0 update can have issues with displaying the new player if conflicting with your design styles, please check this post listing all issues: https://www.kernel-video-sharing.com.../28-kvs-v3-9-0 Specific to 4.0.2 4.0.2 update contains set of player VAST bugfixes. If your project is already 4.0.1 and you want to simply get player bugfixes from 4.0.2, you can replace this file on your installation with the new version from kvs-demo.com: https://kvs-demo.com/player/kt_player.js If you are not interested in other fixes in this update, you won't need to update your project, taking player JS file is enough to get all player bugfixes. If your project accepts payments and uses KVS payment processors, it is recommended that you update it to 4.0.2 to get the new way of logging. What's new in 4.0.2 1) Added Google ReCAPTCHA integration, which allows replacing all KVS captcha. In order for it to work correctly, massive theme template changes are required. They will be described on forum. 2) KVS will now support dynamic pricing from CCBill added as a separate payment processor (CCBill Dynamic Pricing). 3) In paid access package settings you can now enable filtering by countries, so that certain access packages are only available for certain countries. This will let you configure access packages in different currencies; also you can use this feature to make special offers for different market segments. 4) It will now be allowed to change conversion server libraries configuration directly from admin panel. Previously if you needed to change this, you could do only via conversion server filesystem. 5) In models death date field was added. 6) In grabbers we changed the way how the time part of post date is populated. Previously you could configure to take post date from the source site, but its time part was always randomized between 00:00 and 23:59. Now we added additional option to enable time randomization, and if the option is not enabled, grabber will set time to the current server time as the new default behavior. 7) Video quick preview in admin panel will not open a separate window anymore, it will show a modal layer on top of existing window. 8) When displaying list of site pages and if your page components have a lot of global blocks used in them (e.g. header, footer), these global blocks will be listed for all site pages and make page list display too cluttered. We fixed that by grouping such global blocks under the single row with ability to expand it. 9) We started a long-running task to refactor block parameters and documentation. Block parameters will be logically grouped and displayed in similar grouped way, so that they are easier to understand and navigate. Block documentation will be updated with the latest scenarios and practices. Block default templates will also be updated to render all possible data fields (all possible input field for form blocks). This will let you easily render the needed data by simply copy-pasting the needed code from default template of a block. This is a multiple-version task: since we have almost 60 blocks it will take some time for us to silently update them all. 10) In response to GDPR enforcement we reviewed data sets stored by KVS for registered members and made some fixes to reduce data storage in certain cases. Starting from 4.0.2 KVS will not keep login and transaction logs anymore when a member is deleted from KVS. We will also provide a statement on our forum to describe information that is being used and stored by KVS for registered members. 11) Models (list_models) and categories (list_categories) list blocks were extended with ability to display list of related models (categories) by videos and albums they are used together with the current model (category). 12) In signup block you can now configure that access code field is required; so that only users who have access code can register. 13) In logon block it is now possible to restrict only users with webmaster status to log in. This option may be useful if you want to separate memberzone into members and webmasters, which all have different functionality. 14) In logon block it will also be possible to set up 3rd-party callback for logging all login events. If you are using NATS, it provides such callback script to record all logins for additional analysis. 15) In internal messages list block (list_messages) it is now possible to batch approve or reject all pending friendship invitations. 16) Added several display modes in mixed content list block (list_content) to align this block with standalone video / album lists. 17) Bugs that have been fixed: Exoclick should now correctly consider all VAST stats from KVS player. When start screen advertising was enabled together with VAST, start screen advertising was not clickable. The option to skip N videos before showing the next pre-roll ad was distorting VAST advertiser stats, as player requested VAST tag even if advertising was not displayed. Now it was fixed to only load VAST tag when pre-roll is going to be displayed. Vertical videos were handled incorrectly with the new ffmpeg versions. Fixed memory leak in mass editing and content stats plugin when processing huge amount of videos. When videos half-processing was enabled, secondary tasks had default priority; should have had the same priory as primary task's priority was. In some rare cases uploading new photos to existing albums would result in background task error without no reason. In category groups list block (list_categories_groups) there was incorrect avatar URL rendered. Tag directory was not always re-generated correctly. Model auto-selection plugin didn't consider models with numbers in their titles. No error message was shown when uploading ZIP archives that are password protected. Grabbers will not be using GoogleBot user agent anymore. This allowed some sites to block such requests. Category avatar generation plugin and videos sub-selection for each category in category list block did not consider category CTR stats correctly when using CTR sorting. They were using global CTR stats instead of category-specific CTR stats. When upload was configured via subdomain, it would stop working if enable uploader access restriction that we've added in 4.0.1.

4.1.0 is not yet started. 4.0.2 bugfixing and small feature release will be available this week.

Please check the original post and its (3) HLS format investigation. We will add support for this or other adaptive format finally, but not sure which version. We do not agree that it should be on high priority list, because: - This doesn't affect your monetization in much way - Most KVS clients use short videos, there is no much visible performance difference between MP4 and HLS for short videos - You can save bandwidth cost with KVS even without using HLS format, check this guide: https://www.kernel-video-sharing.com/forum/forum/educational-support/educational-series/34-how-to-save-bandwidth-with-kvs-tube-script However using HLS brings disk space issue, conversion speed issue and video protection issue. If you want to allow download, you will have to keep MP4s, this doubles your space and conversion time. Also it looks like MPEG-DASH is going to be a standard, so maybe not much sense to encode all videos into HLS, so that later you have to re-encode them in MPEG-DASH. During the investigation planned for 4.1 we will look at all possible options and will see what we are able to implement, so that old customers can convert into adaptive formats if needed.

It was added to 4.0.2:

Yes, we can probably do that.

That's right, but the only way to detect this is to do it manually, there is no way to automatically detect intro or ending advertising. Yes, if ffmpeg delogo function can detect such watermarks automatically, we will add this to KVS.

We will consider adding this feature if easily implemented. This is already possible with KVS. Please go to Settings -> Video formats and in video format settings you configure skip from start and from end. Also in 4.0 there is a way to configure this programmatically with your own logic. Please check here: https://www.kernel-video-sharing.com/forum/forum/general-discussion/announcements/273-kvs-4-0-implementation-previously-was-3-9-2?p=544#post544 For example if you are using content sources, you can customize this PHP code to cut different fragments from start / end for videos from different content sources. You can use $video_data['content_source_id'] to check for content source ID and return different options for content sources with different IDs. Other possible scenario would be to use content source custom text fields to specify offsets and query content source data in this customization script to check for values to skip.

Album source files are not changed in any way, because these are source files and should be stored in original uploaded format. If you want to have logo on them, put the logo before you upload them to KVS. Otherwise you MUST create a new album format and configure logo there. We fully understand that this may be a waste of disk space, but in modern servers disk space is not an issue anymore. However you will be able to change your logo / other options at any time by simply re-creating album format. Which will never be possible if you configure them on source files. Imagine that you have 100k albums uploaded to KVS. And you decided to configure logo today, but you accidentally uploaded the wrong file and updated ALL source files with the wrong logo image. This will mean that your 100k albums are broken forever. But this won't be a problem if logo is applied not to source files, but to format instead. You will be able to fix this issue very soon and restore all your albums.

KVS supports VR videos, e.g. you can upload and convert them. But in order to show them you will need to use special VR video player.

We don't think such option is needed. You can configure this message in block template directly. Go to Website UI -> Pages and search for video_edit block. Enter this block settings and backup its template locally to some text file. Then change template with your error message. As a result -> everyone who opens upload page will see your message. When finished, restore template back from your backup file.

We updated test code in the original post for this issue. The new grabber API has things coded differently. Content URLs on the page should be detected automatically based on what you provide in this function: public function get_supported_url_patterns() { return array("/regexp here/i"); }

Yes, we have this item in our wishlist already.

There is Other browsers choice, which actually covers all other (minor) browsers. I cannot imagine a situation when you need to show a very specific adveritising for Android Webview browser, which will be different for all other Android browsers.

This was implemented in 4.0: https://www.kernel-video-sharing.com/forum/forum/general-discussion/announcements/273-kvs-4-0-implementation-previously-was-3-9-2?p=522#post522

How do we validate these? We are not google.

Email notifications are planned for future updates, but not for 4.1. Probably 4.2. Please check the original post: Low priority features for 4.1 -> 2) Comments and rating enhancements -> Ability to reply to other comments (hierarchy).

Yes, we are planning to add support for crypto payment processing soon.

Sorry, we cannot comment on inability of your hoster team to modify default Apache configuration. Configuring upload via subdomain requires the exact configuration described in FAQ. If your hoster is not able to configure that, you will not be able to upload files via subdomain.

Integrated Google Recaptcha as a plugin into KVS: The main problem for old customers will be to update templates, because otherwise it will not work. There is no way to render it without updating templates. We will provide instructions later for all themes, but the updates will be huge... Here is example how it will look with default theme:

Please create a support ticket for that, you are probably using the old template and we don't have this anymore, so need to update your template code.

If you delete open_basedir option from php.ini it will mean that this limitation is fully disabled and PHP should be able to access any directories based on filesystem permissions. We are not sure for OS windows though, KVS does not support this OS based on its requirements.

Yes we have this feature in our wishlist already, but probably not for 4.1.

After discussing this with CCBill support, they said that there is no difference from KVS perspective whether you want to use FlexForm or old JPost approach. They confirmed that both Background Post and Datalink features work in the same way for FlexForms. So looks like there is nothing we should do here in general. Perhaps it will be required to update postback processor if some variables it expects to be available are not present in FlexForm postback, but we can only do this on the live site having live postbacks, since there is no doc describing that. If you want to configure this on your site, just try that and let us know if something is wrong.