Recherche avancée

Sur d’autres sites (8375)

• 12 ways Matomo Analytics helps you to protect your visitor’s privacy

  5 mai 2020, par InnoCraft — Analytics Tips, Privacy, Security

  This post was originally published on January 11, 2017, and updated on May, 2020.

  At Matomo we think privacy matters. From the beginning, Matomo has had a strong focus on privacy and ensuring the privacy of your visitors and analytics data. 

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

  1. Owning the data gives you power to protect user privacy

  Whether you host Matomo on-premises yourself, or whether you use Matomo’s cloud, YOU keep control of your data and nobody else. By knowing exactly where your data is stored and having full control over what happens to it, you have the power to protect your user’s privacy. No-one else can claim ownership. 

  2. GDPR compliance

  GDPR is one of the most important privacy laws to have come out in the last few years. As such, Matomo takes GDPR compliance very seriously. There’s even a 12-step checklist for you to follow to ensure your Matomo is GDPR compliant. Not only that Matomo is HIPAA, CCPA, LGPD, and PECR compliant.

  3. Data anonymization

  For better privacy by default, Matomo implements a range of data anonymization techniques. One of the main techniques is not recording the full IP address of your visitors. Some countries even require you to anonymize additional info considered Personally Identifiable Information (PII).

  To change the IP anonymization settings go to “Administration > Privacy”. 

  

  4. Configuring Matomo to not process personal data or personally identifiable information (PII)

  To further protect the privacy of your visitors, you can learn how to not process any personal information or PII. 

  5. Deleting old visitor logs

  The is important because visitor logs contain information all the collected raw data about every visitor and every action. You can configure Matomo 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 Matomo 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 !

  

  6. Supporting the 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, Matomo 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”.

  7. Including 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 Matomo Marketplace there are also some plugins available to customize the Opt-Out experience. For example AjaxOptOut and CustomOptOut.

  

  8. Disabling 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 Matomo.

  9. Disabling fingerprinting across websites

  By default, when one of your visitors visits several of your websites, Matomo 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.

  10. Disabling tracking cookies

  Matomo uses first-party 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 Matomo Javascript code.

  11. Creating the tool of your dreams by developing your own plugins and getting access to the API

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

  12. Transparency

  By default, all information and all collected data in your Matomo server are protected and nobody can access it. However, Matomo allows you to optionally make your collected data public and you can export any Matomo 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.

  Bonus tip – A privacy policy template for you

  When you use Matomo to track your visitors, we recommend you update your Privacy Policy to explain how Matomo is used and what data it gathers. Here’s a Privacy Policy template for you to 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 Matomo features

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

• Generate video with ffmpeg to play using JavaFX

  25 mai 2015, par taskman

  People always say to post a new question so I am posting a new question that relates to Generate video with ffmpeg for JavaFX MediaPlayer

  The images I use can be downloaded from here https://www.dropbox.com/s/mt8yblhfif113sy/temp.zip?dl=0. It is a 2.2GB zip file with 18k images, still uploading, might take some time. The images are slices of a 3D object. I need to display images every 10ms to 20ms. I tried it with Java, but just couldn’t get faster than 30ms+ so now I am trying to generate a video that will display images as fast as I want without worrying about memory or CPU power.

  People will be using my software to slice the objects and then generate the videos to be played later one. The player might run on a cheap laptop or might run on a Raspberry Pi. I need to make sure the slicer will work on any OS and that people don’t need to install too much extra stuff to make it work. It would be best if I can just include everything that is needed in the download of the app.

  I also posted here
  https://ffmpeg.zeranoe.com/forum/viewtopic.php?f=15&t=2474&sid=4f7a752f909202fbec19afc9edaf418c

  I am using Windows 7 and I have VLC installed. The ffmpeg version is

  ffmpeg version N-72276-gf99fed7 Copyright (c) 2000-2015 the FFmpeg developers
  
    built with gcc 4.9.2 (GCC)

  I also tried the command lines posted on the linked question

  This line produced the video and JavaFX didn’t have any errors

  ffmpeg -f image2 -r 50 -i "Mandibular hollow 1 micron.gizmofill%d.gizmoslice.jpg" -s 1638x1004 -vcodec mpeg4 -qscale 1 -f mp4 Timelapse.mp4

  

  This line also produced the video, but JavaFX had an error : "Caused by : MediaException : MEDIA_UNSUPPORTED : Unrecognized file signature !"

  ffmpeg -f image2 -r 50 -i "Mandibular hollow 1 micron.gizmofill%d.gizmoslice.jpg" -s 1920x1080 -vcodec mpeg4 -qscale 1 Timelapse.avi

  

  I also tried this two pass encoding I believe. It produced the video, but didn’t play

  ffmpeg -r 50 -i "Mandibular hollow 1 micron.gizmofill%d.gizmoslice.jpg" -s 1638x1004 -r 50 -b:v 1550k -bt 1792k -vcodec libx264 -pass 1 -an combined50.flv && ffmpeg -y -r 50 -i "Mandibular hollow 1 micron.gizmofill%d.gizmoslice.jpg" -s 1638x1004 -r 50 -b:v 1550k -bt 1792k -vcodec libx264 -pass 2 -vpre hq -acodec libfaac -ab 128k combined50.flv

  This is my JavaFX code. As you can see I tried the Oracle video and that worked fine.

  public class FXMLDocumentController implements Initializable {
  
  
  
      @FXML
  
      private Label label;
  
  
  
      @FXML
  
      private MediaView mediaView;
  
  
  
      @FXML
  
      private void handleButtonAction(ActionEvent event) {
  
          System.out.println("You clicked me!");
  
  
  
  //        final File f = new File("http://download.oracle.com/otndocs/products/javafx/oow2010-2.flv");
  
          final File f = new File("C:/Users/kobus/Dropbox/JavaProjects/Gizmetor/temp/Timelapse.avi");
  
  
  
  //        "C:/Users/kobus/Dropbox/JavaProjects/Gizmetor/temp/combined50.avi.flv"
  
  //        http://download.oracle.com/otndocs/products/javafx/oow2010-2.flv
  
  
  
          Media media = new Media(f.toURI().toString());
  
  //        Media media = new Media("http://download.oracle.com/otndocs/products/javafx/oow2010-2.flv");
  
          MediaPlayer mediaPlayer = new MediaPlayer(media);
  
          mediaPlayer.setAutoPlay(true);
  
  
  
          mediaPlayer.play();
  
          mediaView.setMediaPlayer(mediaPlayer);
  
          label.setText("Hello World!");
  
          System.out.println(mediaPlayer.isAutoPlay());
  
  
  
  //        mediaView
  
      }
  
  
  
      @Override
  
      public void initialize(URL url, ResourceBundle rb) {
  
          // TODO
  
      }
  
  
  
  }

• Recording usb cam on raspberry pi with ffmpeg - usb troubleshooting

  18 septembre 2017, par Hwy2Hell

  I want to save video from an external usb cam on the raspberry pi 3. In order to avoid voltage drop issues, I use the offical raspberry power supply (2.5 Amp) and connected all usb devices by a separetely powered usb hub :

  pi@raspi:~/appdev/ffmpeg $ lsusb
  
  Bus 001 Device 037: ID 046d:09a1 Logitech, Inc. QuickCam Communicate MP/S5500
  
  Bus 001 Device 036: ID 046d:c03f Logitech, Inc. M-BT85 [UltraX Optical Mouse]
  
  Bus 001 Device 035: ID 04d9:1503 Holtek Semiconductor, Inc. Shortboard Lefty
  
  Bus 001 Device 012: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
  
  Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
  
  Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. 
  
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  When I try to test the functionality by running the following bash script (snippet) :

  function capture
  
  {
  
      capfile=$(date +%F_%Hh%Mm%Ss)
  
      echo saving to $wdir/$capfile.mp4
  
      echo $PATH
  
      ffmpeg -video_size 320x240 -i /dev/video0 \
  
      -vf drawtext="fontsize=18:x=10:y=220:fontcolor=red:\
  
      fontfile=/usr/share/fonts/truetype/dejavu/DejaVuSans.ttf:\
  
      text=%{localtime}" -t 10 $wdir/$capfile.mp4
  
      # change -t to 3600 = 1h
  
  }
  
  
  
  for i in $(seq 1 10)
  
  do
  
      echo
  
      echo Pass $i ...
  
      capture
  
  done

  After a few loop-runs I always see device errors :

  Pass 5 ...
  
  saving to /home/pi/appdev/ffmpeg/2017-09-16_13h31m00s.mp4
  
  /usr/local/bin:/usr/bin/ffmpeg:/usr/bin:/bin:/sbin
  
  ffmpeg version 3.3.3 Copyright (c) 2000-2017 the FFmpeg developers
  
    built with gcc 4.9.2 (Raspbian 4.9.2-10)
  
    configuration: --arch=armhf --target-os=linux --enable-gpl --enable-libfreetype --enable-mmal --enable-nonfree --enable-omx --enable-omx-rpi
  
    libavutil      55. 58.100 / 55. 58.100
  
    libavcodec     57. 89.100 / 57. 89.100
  
    libavformat    57. 71.100 / 57. 71.100
  
    libavdevice    57.  6.100 / 57.  6.100
  
    libavfilter     6. 82.100 /  6. 82.100
  
    libswscale      4.  6.100 /  4.  6.100
  
    libswresample   2.  7.100 /  2.  7.100
  
    libpostproc    54.  5.100 / 54.  5.100
  
  /dev/video0: Input/output error

  The kernel message log shows that the usb cam has been resetted :

  pi@raspi:~/appdev/ffmpeg $ dmesg | grep usb
  
  [ 4497.358195] usb 1-1.2.4: new high-speed USB device number 37 using dwc_otg
  
  [ 4497.573440] usb 1-1.2.4: New USB device found, idVendor=046d, idProduct=09a1
  
  [ 4497.573466] usb 1-1.2.4: New USB device strings: Mfr=0, Product=0, SerialNumber=2
  
  [ 4497.573481] usb 1-1.2.4: SerialNumber: A032D310
  
  [ 4497.605698] input: UVC Camera (046d:09a1) as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2.4/1-1.2.4:1.0/input/input15
  
  [ 4497.625582] usb 1-1.2.4: Warning! Unlikely big volume range (=3072), cval->res is probably wrong.
  
  [ 4497.625606] usb 1-1.2.4: [5] FU [Mic Capture Volume] ch = 1, val = 4608/7680/1
  
  [ 5268.123764] usb 1-1.2.4: reset high-speed USB device number 37 using dwc_otg

  Next time I start the script, the usb cam gets disconnected and /dev/viedo0 disappears :

  pi@raspi:~/appdev/ffmpeg $ dmesg | grep usb
  
  [ 5621.216896] usb 1-1.2.4: USB disconnect, device number 37
  
  [ 5621.586804] usb 1-1.2.4: new full-speed USB device number 38 using dwc_otg
  
  [ 5621.686694] usb 1-1.2.4: device descriptor read/64, error -32
  
  [ 5621.896583] usb 1-1.2.4: device descriptor read/64, error -32
  
  [ 5622.106572] usb 1-1.2.4: new full-speed USB device number 39 using dwc_otg
  
  [ 5622.206574] usb 1-1.2.4: device descriptor read/64, error -32
  
  [ 5622.416577] usb 1-1.2.4: device descriptor read/64, error -32
  
  [ 5622.626586] usb 1-1.2.4: new full-speed USB device number 40 using dwc_otg
  
  [ 5623.046583] usb 1-1.2.4: device not accepting address 40, error -32
  
  [ 5623.146583] usb 1-1.2.4: new full-speed USB device number 41 using dwc_otg
  
  [ 5623.566603] usb 1-1.2.4: device not accepting address 41, error -32
  
  [ 5623.566670] usb 1-1.2-port4: unable to enumerate USB device

  Has anybody experienced similar problems and can provide a fix for it ?

  What tools can I use to troubleshoot the usb communication on the pi ?