Recherche avancée

Sur d’autres sites (9908)

• 11 ways Piwik Analytics helps you to protect your visitors privacy

  11 janvier 2017, par InnoCraft — Community

  At Piwik and at InnoCraft, we think Privacy matters. From the beginning, Piwik has had a strong focus on privacy and ensures the privacy of your visitors and analytics data. As a result, Piwik has been recommended as a privacy-compliant analytics tool for example by the Independent Center for Privacy Protection in Germany (ULD) and by the Center for Data Privacy Protection in France (CNIL). In France, Piwik is the only web analytics tool that does not require Cookie Consent.

  Here are some ways how you can ensure your users and visitors privacy by using Piwik.

  1. You own the data

  Whether you host Piwik on premise yourself, managed on premise by InnoCraft, or whether you use our Piwik cloud, when you use Piwik, YOU keep control of your data and nobody else. This also means you can decide where your data should be located physically.

  2. Anonymized IP addresses

  For better privacy by default, Piwik will not record the full IP address of your visitors because otherwise the browsing history could be easily tracked across several days and even across websites within the same Piwik server. Some countries even require to anonymize the IP address, considered Personally Identifiable Information (PII).

  To change the IP anonymization settings go to “Administration > Privacy”. Optionally, you can use the full IP to still get for example accurate location data.

  

  3. Delete old visitor logs

  The visitor logs contain information all the collected raw data about every visitor and every action. You can configure Piwik to automatically delete logs from the database. When you delete old logs, only the real time and visitor log reports will no longer work for this old time period, all other aggregated reports will still work.

  For privacy reasons, we highly recommend that you keep the detailed Piwik logs for only 3 to 6 months and delete older log data. This has one other nice side effect : it will free significant database space, which will, in turn, slightly increase performance !

  

  4. Support Do Not Track preference

  Do Not Track enables users to opt out of any tracking by websites they do not visit, including analytics services, advertising networks, and social platforms. By default, Piwik respects users preference and will not track visitors which have specified “I do not want to be tracked” in their web browsers. Get more information about DoNotTrack.

  To make sure Do Not Track is respected, go to “Administration => Privacy”.

  5. Include an Opt-Out Feature on your website or app

  By embedding the Opt-Out feature in your website, you give your visitors the possibility to opt-out of the tracking. When you go to “Administration > Privacy”, you will be able to copy and paste an HTML Iframe code to embed the opt-out feature for example into your privacy policy page or in your ‘Legal’ page. Your users can then click on a link to opt-out.

  On the Piwik Marketplace there are also some plugins available to customize the Opt-Out experience. For example AjaxOptOut and CustomOptOut.

  

  6. Disable Live features

  The Real-Time, Visitor Log and Visitor Profile features give you insights into the tracked raw data by showing you details about every visitor and every action they performed. To protect the privacy of your visitors you may decide to prevent access to such features by disabling the “Live” plugin in “Administration => Plugins”. This way only aggregated reports will be shown in your Piwik.

  7. Disable fingerprinting across websites

  By default, when one of your visitors visits several of your websites, Piwik will create a fingerprint for this user that will be different across the websites to increase the visitors’ privacy. You can make sure that this feature is disabled by going to “Administration => Config file” and verifying that the value of “enable_fingerprinting_across_websites” is set to zero.

  8. Disable tracking cookies

  Piwik uses cookies to store some information about visitors between visits. In some countries, the legislation requires websites to provide a way for users to opt-out of all tracking, in particular tracking cookies. You can disable cookies by adding one line in the Piwik Javascript code.

  9. Custom development

  Piwik is an open platform that lets you extend and customize the tracking, the reporting and the Piwik user interface to your needs and to protect your visitors’ privacy the way you want or need it. Learn more in the Piwik Developer Zone. You may also have a look at our Piwik Marketplace where you can find several free and premium features to extend your Piwik.

  10. Transparency

  By default, all information and all collected data in your Piwik server are protected and nobody can access it. However, Piwik allows you to optionally make your collected data public and you can export any Piwik report including the whole dashboard to embed it into your website. This way you can show your users exactly which information you track. When you decide to make reports public, we do our best to protect privacy and automatically hide any Personally Identifiable Information such as the Visitor Profile and we make sure to not show any Visitor IP address and the Visitor ID.

  11. Privacy policy

  When you use Piwik to track your visitors, we recommend to update your Privacy Policy to explain how Piwik is used and what data it gathers. We provide a Privacy Policy template for Piwik users that you can copy on your site.

  Continuous privacy improvements

  We are always interested in improving the privacy. If you miss any feature or have an idea on how to improve the privacy, please let us know.

  More information about all the Piwik features

  If you want to learn more about all the features in Piwik, have a look at our User Guides and FAQ entries.

• ffmpeg drops the moov atom when coverting mp4 to ogg, flv, or webm

  31 janvier 2014, par user1370897

  I'm using processor qtfaststart and the gem paperclip-ffmpeg in Rails to convert an mp4 file to either ogg, webm, or flv. However, I haven't had any success converting the mp4 file to these formats for streaming purposes because the moov atom gets dropped (converting mp4 to mp4 keeps its moov atom though*).

  I did a $ qtfaststart -l on the original mp4 file and I get this :

  ftyp (24 bytes)
  
  moov (5691 bytes)
  
  free (399309 bytes)
  
  mdat (12312760 bytes)

  Which shows me that the mp4 file has an moov atom in there. The command that paperclip-ffmpeg is executing is something like this :

  $ ffmpeg -i ~/Movies/VID_20140119_134445.mp4 -acodec libvorbis -ac 2 -ab 96k -ar 44100 -s 640x360 -y ~/tmp/iguana.webm

  However, doing a qtfaststart on the new file (iguana.webm) I get the following :

  $ qtfaststart -l ~/tmp/iguana.webm 
  
  moov atom not found, is this a valid MOV/MP4 file?
  
  Traceback (most recent call last):
  
  File "/usr/local/bin/qtfaststart", line 5, in <module>
  
  pkg_resources.run_script(&#39;qtfaststart==1.8&#39;, &#39;qtfaststart&#39;)
  
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources.py", line 489, in run_script
  
  self.require(requires)[0].run_script(script_name, ns)
  
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources.py", line 1214, in run_script
  
  exec script_code in namespace, namespace
  
  File "/Library/Python/2.7/site-packages/qtfaststart-1.8-py2.7.egg/EGG-INFO/scripts/qtfaststart", line 17, in <module>
  
  
  
  File "build/bdist.macosx-10.9-intel/egg/qtfaststart/command.py", line 44, in run
  
  File "build/bdist.macosx-10.9-intel/egg/qtfaststart/processor.py", line 65, in get_index
  
  File "build/bdist.macosx-10.9-intel/egg/qtfaststart/processor.py", line 106, in _ensure_valid_index
  
  qtfaststart.exceptions.FastStartException
  
  </module></module>

  I've also tried adding the option -movflags faststart to the command ffmpeg but ffmpeg still keeps dropping the moov atom to the output file.

  I'm using Rails 4, paperclip-ffmpeg 1.0.1, ffmpeg 2.1.3 Built on Jan 28 2014. Any help would be greatly appreciated.

• FFMPEG - Stream discovered after head already parsed [on hold]

  7 février 2014, par John Doe

  I am trying to live transcode an RTMP stream to another RTMP HLS stream using the following command :

  ffmpeg -re -i rtmp://localhost/videochat/testing -c:v libx264 -c:a:0 libfaac -b:a:0 480k -f flv rtmp://localhost:12345/hls/mystream;

  However I receive the following error and the transcoding never begins :

  ffmpeg version git-2014-02-06-474db7a Copyright (c) 2000-2014 the FFmpeg developers
  
  built on Feb  6 2014 22:20:14 with gcc 4.6 (Ubuntu/Linaro 4.6.3-1ubuntu5)
  
  configuration: --enable-gpl --enable-libass --enable-libfaac --enable-libfdk-aac --               enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-librtmp --enable-libtheora --enable-libvorbis --enable-libvpx --enable-x11grab --enable-libx264 --enable-nonfree --enable-version3
  
  libavutil      52. 63.100 / 52. 63.100
  
  libavcodec     55. 49.101 / 55. 49.101
  
  libavformat    55. 30.100 / 55. 30.100
  
  libavdevice    55.  7.100 / 55.  7.100
  
  libavfilter     4.  1.102 /  4.  1.102
  
  libswscale      2.  5.101 /  2.  5.101
  
  libswresample   0. 17.104 /  0. 17.104
  
  libpostproc    52.  3.100 / 52.  3.100
  
  Metadata:
  
  description           Chat using VideoChat example.
  
  [flv @ 0x1ec89e0] Stream discovered after head already parsed
  
  ^C[flv @ 0x1ec89e0] Could not find codec parameters for stream 0 (Video: none):    unspecified size
  
  Consider increasing the value for the 'analyzeduration' and 'probesize' options
  
  Input #0, flv, from 'rtmp://localhost/videochat/testing':
  
  Metadata:
  
  description     : Chat using VideoChat ex   ?5P
  
  Duration: N/A, start: 0.000000, bitrate: N/A
  
  Stream #0:0: Video: none, 1k tbr, 1k tbn, 1k tbc
  
  Stream #0:1: Data: none
  
  Codec AVOption b (set bitrate (in bits/s)) specified for output file #0 (rtmp://localhost:12345/hls/mystream) has not been used for any stream. The most likely reason is either wrong type (e.g. a video option with no video streams) or that it is a private option of some encoder which was not actually used for any stream.
  
  Output #0, flv, to 'rtmp://localhost:12345/hls/mystream':

  If anyone has ever dealt/solved this problem before, can you please share as I have been trying to solve this for 2 days but to no avail !