Recherche avancée

Sur d’autres sites (11604)

• Use Google Analytics and risk fines, after CJEU ruling on Privacy Shield

  27 août 2020, par Joselyn Khor — Privacy
  EU websites using Google Analytics and Facebook are being targeted by European privacy group noyb after the invalidation of the Privacy Shield. They filed a complaint against 101 websites for continuing to send data to the US. 

  “A quick analysis of the HTML source code of major EU webpages shows that many companies still use Google Analytics or Facebook Connect one month after a major judgment by the Court of Justice of the European Union (CJEU) - despite both companies clearly falling under US surveillance laws, such as FISA 702. Neither Facebook nor Google seem to have a legal basis for the data transfers.”

  

  The Privacy Shield previously allowed for EU data to be transferred to the US. However, this was invalidated by the Court of Justice of the European Union (CJEU) on July 16, 2020. The CJEU deemed it illegal for any websites to transfer the personal data of European citizens to the US. 

  They also made it clear in a press release that “data subjects can claim compensation for inadmissible data exports (marginal no. 143 of the judgment). This should in particular include non-material damage (“compensation for pain and suffering”) and must be of a deterrent amount under European law.” Which puts extra financial pressure on websites to take the new ruling seriously.

  Immediate action is required after Google Privacy Shield invalidation

  The Berlin Commissioner for Data Protection and Freedom of Information therefore calls on all those responsible under its supervision to observe the decision of the ECJ [CJEU]. Those responsible who transfer personal data to the USA - especially when using cloud services - are now required to immediately switch to service providers in the European Union or in a country with an adequate level of data protection.

  As the ruling is effective immediately, there’s a pressing need for websites using Google Analytics to act, or face getting fined.

  What does this mean for you ?

  If you’re using Google Analytics the safest bet is to stop using it immediately. 

  "Neither Google Analytics nor Facebook Connect are necessary for the operation of these websites and could therefore have been replaced or at least deactivated in the meantime."

  If you still need to use it, then you’ll need to inform your visitors via a clear consent screen. This banner needs to make clear their personal data will be sent to the US, and to educate them about any potential risk related to this. They will then need to explicitly agree to this. 

  Another downside of cookie consent screens is that you may also suffer a damaging loss of visitors. After implementing cookie consent best practices, the UK’s data regulator the Information Commissioner’s Office (ICO) found a 90% drop in traffic, “implying a ninety percent drop in opt-in rates.”

  With an acceptance rate for such consent screens being lower than 10% your analytics becomes guesswork rather than science. 

  Looking for a privacy-respecting alternative to Google Analytics ?

  Privacy compliant Matomo Analytics is one of the best Google Analytics alternatives availalble. 

  With Matomo you’re able to continue using analytics without facing the wrath of both the GDPR and the CJEU. Matomo On-Premise lets you choose where your data is stored, so you can ensure no data is processed in the US. 

  Matomo is privacy-friendly and can be tweaked to comply with all privacy laws. Including the GDPR, HIPAA, CCPA and PECR. The benefits of this include : not needing to use tracking or cookie consent screens (like with GA) ; and avoiding fines because no personal data is collected. You also get 100% accurate data and the ability to protect your user’s privacy.

  Download Matomo

  

  Is your EU business at risk of being fined for using Google Analytics ?

  Email

  Get our assessment guide

• Run PHP exec() asynchronously, but check for completion ?

  1er septembre 2015, par PeregrineStudios

  I’m coding up a website back-end that will include user-uploaded video. In order to ensure maximum accessibility, I’m compressing the uploaded videos and re-saving them as .mp4 and .webm format to cover all browsers (or as many as possible anyway). To do this, I’m running an avconv command in the PHP exec() function.

  I don’t want to make the user wait for the script to finish before the page loads, so I’m running the code asynchronously. My code so far is below.

  exec('bash -c "exec nohup setsid avconv -i ' . $tempPath . ' -c:v libx264 ' . $transpose . ' ' . $newPath . 'mp4 > /dev/null 2>/dev/null &"');
  
  exec('bash -c "exec nohup setsid avconv -i ' . $tempPath . ' -c:v libvpx ' . $transpose . ' ' . $newPath . 'webm > /dev/null 2>/dev/null &"');

  In addition to running the exec functions, I also save the video to a database and send the user an email thanking them for uploading their video.

  Here’s the rub : I want the server to WAIT until the video conversion is finished, and THEN add it to the database and send the user an email. Basically, the program flow would be :

  User uploads video.
  Video is placed in a temp folder.
  User is taken to a thank you page indicating their video will be up shortly.
  The server executes two avconv commands to convert and compress the video for web use.
  Once BOTH conversions are finished, the video info is added to a MySQL database, an email is sent to the user, and the original uploaded video is deleted.

  It may just be my ignorance of the command line (in fact it almost definitely is), but how could I ’queue up’ these commands ? First do both conversions, then call a PHP script to add to the database, then delete the original video, all while being asynchronous with the original PHP script ?

  EDIT : I’ve tried queuing them up with an ’&&’ operator, like below :

  exec('bash -c "exec nohup setsid avconv -i ' . $tempPath . ' -c:v libx264 ' . $transpose . ' ' . $newPath . 'mp4 && avconv -i ' . $tempPath . ' -c:v libvpx ' . $transpose . ' ' . $newPath . 'webm > /dev/null 2>/dev/null &"');

  However, that seems to cancel out the fact that I’m running it asynchronously, since the page now seems to wait for the command to finish.

• avcodec/vc1dec : Re-order init to avoid initting hwaccel too early

  8 août 2015, par Philip Langdale

  avcodec/vc1dec : Re-order init to avoid initting hwaccel too early
  At least for vdpau, the hwaccel init code tries to check the video
  
  profile and ensure that there is a matching vdpau profile available.
  If it can’t find a match, it will fail to initialise.
  In the case of wmv3/vc1, I observed initialisation to fail all the
  
  time. It turns out that this is due to the hwaccel being initialised
  
  very early in the codec init, before the profile has been extracted
  
  and set.
  Conceptually, it’s a simple fix to reorder the init code, but it gets
  
  messy really fast because ff_get_format(), which is what implicitly
  
  trigger hwaccel init, is called multiple times through various shared
  
  init calls from h263, etc. It’s incredibly hard to prove to my own
  
  satisfaction that it’s safe to move the vc1 specific init code
  
  ahead of this generic code, but all the vc1 fate tests pass, and I’ve
  
  visually inspected a couple of samples and things seem correct.
  Signed-off-by : Philip Langdale <philipl@overt.org>
  

  • [DH] libavcodec/vc1dec.c