Recherche avancée

Sur d’autres sites (9636)

• GDPR compliance for Matomo’s Premium Features like Heatmaps & Session Recording, Form Analytics, Media Analytics & co

  27 avril 2018, par InnoCraft

  The General Data Protection Regulation (EU) 2016/679, also referred to as RGPD in French, Datenschutz-Grundverordnung, DS-GVO in German, is fast-approaching. It is now less than 30 days until GDPR applies to most businesses around the world on 25th May 2018. If you haven’t heard of this new regulation yet, I recommend you check out our GDPR guide which we continue to expand regularly to get you up to speed with it.

  GDPR compliance in Matomo

  We are currently adding several new features to Matomo to get you GDPR ready. You will have for example the possibility to delete and export data for data subjects, delete and anonymize previously tracked data, anonymize the IP address and location, ask for consent, and more. A beta version with these features is already available. We will release more blog posts and user guides about these features soon and just recently published a post on how to avoid collecting personal information in the first place soon.

  If you are still using Piwik, we highly recommend you update to a recent version of Matomo as all versions of Piwik will NOT be GDPR compliant.

  GDPR compliance for premium features

  InnoCraft, the company of the makers of Matomo, are offering various premium features for your self-hosted Matomo so you can be sure to make the right decisions and continuously grow your business. These features are also available on the cloud-hosted version of Matomo.

  If you are now wondering how GDPR applies to these features, you will be happy to hear that none of them collect any personal information except for possibly Heatmaps & Session Recording and the WooCommerce integration. All of them also support all the new upcoming GDPR features like the possibility to export and delete data. It is important that you update your Matomo Premium Features to the latest version to use these features.

  Making Heatmaps & Session Recording GDPR compliant

  We have added several new features to make it easy for you to be GDPR compliant and in many cases you might not even have to do anything. Some of the changes include :

  • Keystrokes (text entered into form fields) are no longer captured by default.
  • You may enable the capturing of keystrokes, and all keystrokes will be anonymized by default.
  • You may whitelist certain form fields to be recorded in plain text. However, fields that likely contain personal or sensitive information like passwords, phone numbers, addresses, credit card details, names, email addresses, and more will be always anonymized to protect user privacy. (this has always been the case but we have now included many more fields).

  How personal information may still be recorded

  Nevertheless, Heatmaps and Session Recordings may still record personal or sensitive information if you show them as part of the regular website as plain text (and not as part of a form field). The below example shows an email address for a paypal account as well as a name and VAT information as a regular content.

  

  To anonymize such information, simply add a data-matomo-mask attribute to your website :

  <span data-matomo-mask>example@example.com</span>

  You can read more about this in the developer guide “Masking content on your website”.

  WooCommerce Integration

  The WooCommerce integration may record an Order ID when a customer purchases something on your shop. As the Order ID is an identifier which could be linked with your shop to identify an individual, it may be considered as personal information. Matomo now offers an option to automatically anonymize this Order ID so it is no longer considered as personal information. To enable this feature, log in to your Matomo and go to “Administration => Anonymize Data”.

  GDPR compliance for third party plugins on the Matomo Marketplace

  The Matomo Marketplace currently features over 80 free plugins. Over 50 of them are compatible with the latest Matomo 3.X version and most of them should support Matomo’s new GDPR features out of the box. If you are concerned by GDPR and are not sure if a third party plugin stores any personal information, we highly recommend you ask the developer of this plugin about the compliance.

  You can find a link to the plugin’s issue tracker by going to a plugin page and then clicking on “Github” on the bottom right.

  

  If you are a plugin developer, please read our developer guide “GDPR & How do I make my Matomo plugin compliant”.

  The post GDPR compliance for Matomo’s Premium Features like Heatmaps & Session Recording, Form Analytics, Media Analytics & co appeared first on Analytics Platform - Matomo.

• WebRTC predictions for 2016

  17 février 2016, par silvia

  I wrote these predictions in the first week of January and meant to publish them as encouragement to think about where WebRTC still needs some work. I’d like to be able to compare the state of WebRTC in the browser a year from now. Therefore, without further ado, here are my thoughts.

  WebRTC Browser support

  I’m quite optimistic when it comes to browser support for WebRTC. We have seen Edge bring in initial support last year and Apple looking to hire engineers to implement WebRTC. My prediction is that we will see the following developments in 2016 :

  • Edge will become interoperable with Chrome and Firefox, i.e. it will publish VP8/VP9 and H.264/H.265 support
  • Firefox of course continues to support both VP8/VP9 and H.264/H.265
  • Chrome will follow the spec and implement H.264/H.265 support (to add to their already existing VP8/VP9 support)
  • Safari will enter the WebRTC space but only with H.264/H.265 support

  Codec Observations

  With Edge and Safari entering the WebRTC space, there will be a larger focus on H.264/H.265. It will help with creating interoperability between the browsers.

  However, since there are so many flavours of H.264/H.265, I expect that when different browsers are used at different endpoints, we will get poor quality video calls because of having to negotiate a common denominator. Certainly, baseline will work interoperably, but better encoding quality and lower bandwidth will only be achieved if all endpoints use the same browser.

  Thus, we will get to the funny situation where we buy ourselves interoperability at the cost of video quality and bandwidth. I’d call that a “degree of interoperability” and not the best possible outcome.

  I’m going to go out on a limb and say that at this stage, Google is going to consider strongly to improve the case of VP8/VP9 by improving its bandwidth adaptability : I think they will buy themselves some SVC capability and make VP9 the best quality codec for live video conferencing. Thus, when Safari eventually follows the standard and also implements VP8/VP9 support, the interoperability win of H.264/H.265 will become only temporary overshadowed by a vastly better video quality when using VP9.

  The Enterprise Boundary

  Like all video conferencing technology, WebRTC is having a hard time dealing with the corporate boundary : firewalls and proxies get in the way of setting up video connections from within an enterprise to people outside.

  The telco world has come up with the concept of SBCs (session border controller). SBCs come packed with functionality to deal with security, signalling protocol translation, Quality of Service policing, regulatory requirements, statistics, billing, and even media service like transcoding.

  SBCs are a total overkill for a world where a large number of Web applications simply want to add a WebRTC feature – probably mostly to provide a video or audio customer support service, but it could be a live training session with call-in, or an interest group conference all.

  We cannot install a custom SBC solution for every WebRTC service provider in every enterprise. That’s like saying we need a custom Web proxy for every Web server. It doesn’t scale.

  Cloud services thrive on their ability to sell directly to an individual in an organisation on their credit card without that individual having to ask their IT department to put special rules in place. WebRTC will not make progress in the corporate environment unless this is fixed.

  We need a solution that allows all WebRTC services to get through an enterprise firewall and enterprise proxy. I think the WebRTC standards have done pretty well with firewalls and connecting to a TURN server on port 443 will do the trick most of the time. But enterprise proxies are the next frontier.

  What it takes is some kind of media packet forwarding service that sits on the firewall or in a proxy and allows WebRTC media packets through – maybe with some configuration that is necessary in the browsers or the Web app to add this service as another type of TURN server.

  I don’t have a full understanding of the problems involved, but I think such a solution is vital before WebRTC can go mainstream. I expect that this year we will see some clever people coming up with a solution for this and a new type of product will be born and rolled out to enterprises around the world.

  Summary

  So these are my predictions. In summary, they address the key areas where I think WebRTC still has to make progress : interoperability between browsers, video quality at low bitrates, and the enterprise boundary. I’m really curious to see where we stand with these a year from now.

  —

  It’s worth mentioning Philipp Hancke’s tweet reply to my post :

  https://datatracker.ietf.org/doc/draft-ietf-rtcweb-return/ … — we saw some clever people come up with a solution already. Now it needs to be implemented

  The post WebRTC predictions for 2016 first appeared on ginger’s thoughts.

• Android FFmpeg sometimes works and sometimes crashes

  20 novembre 2013, par Pawel Cala

  I compiled FFmpeg for Android ( https://gitorious.org/android-ffmpeg ) but when I'm trying to do some operations ( f.e filters cropping, transpose, trim etc ) it crashes in 5 on 10 cases.
  Error logs are not the same so I assume that it might be caused by memory issues.
  I'm using OSX, NDK android-ndk-r9b : darwing x86_64.
  Native ffmpeg method is passing args to ffmpeg.c main method. It's executed in AsyncTask in Activity.
  Thanks in advance

  EDIT :
  I forgot to mention that programs algorithm runs like that :
  Press Button - > Open Camera Intent - > Start recording - > After recording copy file to project folder ( on SD card ) - > Open edit activity + Start asynctask

  EDIT2 :
  Tested on HTC ONE with different video resolutions

  Version and config of ffmpeg

  11-20 12:15:23.001: I/ff-log(19091): ffmpeg version 0.10.2.git
  
  11-20 12:15:23.001: I/ff-log(19091):  Copyright (c) 2000-2012 the FFmpeg developers
  
  11-20 12:15:23.001: I/ff-log(19091):   built on Nov 20 2013 12:12:46 with gcc 4.6 20120106 (prerelease)
  
  11-20 12:15:23.001: I/ff-log(19091):   configuration: --target-os=linux --cross-prefix=arm-linux-androideabi- --arch=arm --cpu=armv7-a --disable-ffplay --disable-ffserver --disable-network --disable-avdevice --enable-protocol=file --enable-hwaccel=mpeg4_vaapi --enable-hwaccel=h264_vaapi --sysroot=/Users/dpc/Developer/android-ndk-r9b/platforms/android-9/arch-arm --disable-decoder=h264_vdpau --prefix=build/armv7-a --disable-asm --enable-small --disable-everything --enable-decoder=mjpeg --enable-parser=mjpeg --enable-muxer=mp4 --enable-muxer=h264 --enable-muxer=h263 --enable-muxer=yuv4mpegpipe --enable-muxer=mov --enable-demuxer=mpegvideo --enable-demuxer=mjpeg --enable-demuxer=image2 --enable-demuxer=mp4 --enable-demuxer=aac --enable-demuxer=ac3 --enable-demuxer=mp3 --enable-demuxer=yuv4mpegpipe --enable-demuxer=mov --enable-decoder=mpegvideo --enable-decoder=mpeg4 --enable-decoder=mp3 --enable-decoder=ac3 --enable-decoder=aac --enable-decoder=h264 --enable-decoder=h263 --enable-decoder=rawvideo --enable-decoder=yuv4 --enable-decoder=png --enable

  Sample comand :

  1-20 12:15:22.991: I/FFMPEG(19091): CMD:-i file:/storage/emulated/0/.project/videos/mac_video_tmp.mp4 -vf crop=1079:1079:0:420 -vcodec mpeg4 -sameq -acodec copy file:/storage/emulated/0/.project/videos/croppedVid.mp4

  Some output errors :

  1st type :

     11-20 12:15:23.011: I/ff-log(19091):   libavutil      51. 46.100 / 51. 46.100
  
  11-20 12:15:23.011: I/ff-log(19091):   libavcodec     54. 14.101 / 54. 14.101
  
  11-20 12:15:23.011: I/ff-log(19091):   libavformat    54.  3.100 / 54.  3.100
  
  11-20 12:15:23.011: I/ff-log(19091):   libavfilter     2. 70.100 /  2. 70.100
  
  11-20 12:15:23.011: I/ff-log(19091):   libswscale      2.  1.100 /  2.  1.100
  
  11-20 12:15:23.011: I/ff-log(19091):   libswresample   0. 11.100 /  0. 11.100
  
  11-20 12:15:23.011: I/ff-log(19091): before parsing options
  
  11-20 12:15:23.011: I/ff-log(19091): before parsing options
  
  11-20 12:15:23.011: I/ff-log(19091): parse options
  
  11-20 12:15:23.011: I/ff-log(19091): prepare app arguments !!! NOT defined(_WIN32) && !defined(__MINGW32CE__) !
  
  11-20 12:15:23.011: I/ff-log(19091): after prepare app arguments
  
  11-20 12:15:23.011: I/ff-log(19091): ffurl_open: file:/storage/emulated/0/.project/videos/mac_video_tmp.mp4, 1
  
  11-20 12:15:23.011: I/ff-log(19091): ffurl_alloc: file:/storage/emulated/0/.project/videos/mac_video_tmp.mp4, 1
  
  11-20 12:15:23.011: I/ff-log(19091): ffurl_alloc: file
  
  11-20 12:15:23.011: I/ff-log(19091): ffurl_open alloc: 0
  
  11-20 12:15:23.011: I/ff-log(19091): ffurl_connect
  
  11-20 12:15:23.011: I/ff-log(19091): ffurl_open connect: 0
  
  11-20 12:15:23.011: I/ff-log(19091): Format mov,mp4,m4a,3gp,3g2,mj2 probed with size=2048 and score=100
  
  11-20 12:15:23.011: I/ff-log(19091): ISO: File Type Major Brand: isom
  
  11-20 12:15:23.021: I/ff-log(19091): File position before avformat_find_stream_info() is 8458240
  
  11-20 12:15:23.041: A/libc(19091): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 19091 (t.android.utils)

  Second type :

  11-20 12:17:04.800: I/ff-log(19632):   libavutil      51. 46.100 / 51. 46.100
  
  11-20 12:17:04.800: I/ff-log(19632):   libavcodec     54. 14.101 / 54. 14.101
  
  11-20 12:17:04.800: I/ff-log(19632):   libavformat    54.  3.100 / 54.  3.100
  
  11-20 12:17:04.800: I/ff-log(19632):   libavfilter     2. 70.100 /  2. 70.100
  
  11-20 12:17:04.800: I/ff-log(19632):   libswscale      2.  1.100 /  2.  1.100
  
  11-20 12:17:04.800: I/ff-log(19632):   libswresample   0. 11.100 /  0. 11.100
  
  11-20 12:17:04.800: I/ff-log(19632): before parsing options
  
  11-20 12:17:04.800: I/ff-log(19632): before parsing options
  
  11-20 12:17:04.800: I/ff-log(19632): parse options
  
  11-20 12:17:04.800: I/ff-log(19632): prepare app arguments !!! NOT defined(_WIN32) && !defined(__MINGW32CE__) !
  
  11-20 12:17:04.800: I/ff-log(19632): after prepare app arguments
  
  11-20 12:17:04.800: I/ff-log(19632): opt_output_file ܞ�f��f��f��f���flated/0/.project/videos/mac_video_tmp.mp4
  
  11-20 12:17:04.800: I/ff-log(19632): ffurl_alloc: ܞ�f��f��f��f���flated/0/.project/videos/mac_video_tmp.mp4, 0
  
  11-20 12:17:04.800: I/ff-log(19632): ffurl_alloc: file
  
  11-20 12:17:04.800: I/ff-log(19632): ffurl_open: ܞ�f��f��f��f���flated/0/.project/videos/mac_video_tmp.mp4, 2
  
  11-20 12:17:04.800: I/ff-log(19632): ffurl_alloc: ܞ�f��f��f��f���flated/0/.project/videos/mac_video_tmp.mp4, 2
  
  11-20 12:17:04.800: I/ff-log(19632): ffurl_alloc: file
  
  11-20 12:17:04.800: I/ff-log(19632): ffurl_open alloc: 0
  
  11-20 12:17:04.800: I/ff-log(19632): ffurl_connect
  
  11-20 12:17:04.800: I/ff-log(19632): ffurl_open connect: -2
  
  11-20 12:17:04.800: I/ff-log(19632): ffurl_open FAIL
  
  11-20 12:17:04.800: I/ff-log(19632): ܞ�f��f��f��f���flated/0/.project/videos/mac_video_tmp.mp4: No such file or directory

  ( CHARSER IS AS IT'S IN OUTPUT LOGCAT )

  3rd type :

  11-20 12:18:23.243: I/ff-log(19867):   libavutil      51. 46.100 / 51. 46.100
  
  11-20 12:18:23.243: I/ff-log(19867):   libavcodec     54. 14.101 / 54. 14.101
  
  11-20 12:18:23.243: I/ff-log(19867):   libavformat    54.  3.100 / 54.  3.100
  
  11-20 12:18:23.243: I/ff-log(19867):   libavfilter     2. 70.100 /  2. 70.100
  
  11-20 12:18:23.243: I/ff-log(19867):   libswscale      2.  1.100 /  2.  1.100
  
  11-20 12:18:23.243: I/ff-log(19867):   libswresample   0. 11.100 /  0. 11.100
  
  11-20 12:18:23.243: I/ff-log(19867): before parsing options
  
  11-20 12:18:23.243: I/ff-log(19867): before parsing options
  
  11-20 12:18:23.243: I/ff-log(19867): parse options
  
  11-20 12:18:23.243: I/ff-log(19867): prepare app arguments !!! NOT defined(_WIN32) && !defined(__MINGW32CE__) !
  
  11-20 12:18:23.243: I/ff-log(19867): after prepare app arguments
  
  11-20 12:18:23.243: I/ff-log(19867): Unknown decoder '��f('
  
  11-20 12:18:23.243: I/ff-log(19867): exit_program 1
  
  11-20 12:18:23.243: I/ff-log(19867): exit_program 1
  
  11-20 12:18:23.243: I/ff-log(19867): exit_program 2
  
  11-20 12:18:23.253: A/libc(19867): @@@ ABORTING: invalid address or address of corrupt block 0x1d3422d passed to dlfree
  
  11-20 12:18:23.253: A/libc(19867): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 20393 (AsyncTask #2)

  4th type :

  11-20 12:20:07.214: I/ff-log(20660):   libavutil      51. 46.100 / 51. 46.100
  
  11-20 12:20:07.214: I/ff-log(20660):   libavcodec     54. 14.101 / 54. 14.101
  
  11-20 12:20:07.214: I/ff-log(20660):   libavformat    54.  3.100 / 54.  3.100
  
  11-20 12:20:07.214: I/ff-log(20660):   libavfilter     2. 70.100 /  2. 70.100
  
  11-20 12:20:07.214: I/ff-log(20660):   libswscale      2.  1.100 /  2.  1.100
  
  11-20 12:20:07.214: I/ff-log(20660):   libswresample   0. 11.100 /  0. 11.100
  
  11-20 12:20:07.214: I/ff-log(20660): before parsing options
  
  11-20 12:20:07.214: I/ff-log(20660): before parsing options
  
  11-20 12:20:07.214: I/ff-log(20660): parse options
  
  11-20 12:20:07.214: I/ff-log(20660): prepare app arguments !!! NOT defined(_WIN32) && !defined(__MINGW32CE__) !
  
  11-20 12:20:07.214: I/ff-log(20660): after prepare app arguments
  
  11-20 12:20:07.214: I/ff-log(20660): Unknown decoder ''
  
  11-20 12:20:07.214: I/ff-log(20660): exit_program 1
  
  11-20 12:20:07.214: A/libc(20660): Fatal signal 11 (SIGSEGV) at 0x2d007165 (code=1), thread 21017 (AsyncTask #2)