Recherche avancée

Sur d’autres sites (11795)

• 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

• Annual Release of External-Videos plugin – we’ve hit v1.0

  13 janvier 2017, par silvia

  This is the annual release of my external-videos wordpress plugin and with the help of Andrew Nimmolo I’m proud to annouce we’ve reached version 1.0 !

  So yes, my external-videos wordpress plugin is now roughly 7 years old, who would have thought ! During the year, I don’t get the luxury of spending time on maintaining this open source love child of mine, but at Christmas, my bad conscience catches up with me – every year ! I then spend some time going through bug reports, upgrading the plugin to the latest wordpress version, upgrading to the latest video site APIs, testing functionality and of course making a new release.

  This year has been quite special. The power of open source has kicked in and a new developer took an interest in external-videos. Andrew Nimmolo submitted patches over all of 2016. He decided to bring the external-videos plugin into the new decade with a huge update to the layout of the settings pages, general improvements, and an all-round update of all the video site APIs which included removing their overly complex SDKs and going straight for the REST APIs.

  Therefore, I’m very proud to be able to release version 1.0 today. Thanks, Andrew !

  Enjoy – and I look forward to many more contributions – have a Happy 2017 !

  —

  NOTE : If you’re upgrading from an older version, you might need to remove and re-add your social video sites because the API details have changed a bit. Also, we noticed that there were layout issues on WordPress 4.3.7, so try and make sure your WordPress version is up to date.

  The post Annual Release of External-Videos plugin – we’ve hit v1.0 first appeared on ginger’s thoughts.

• Creating an ffmpeg html/php form process and need ffmpeg technical feedback

  7 juin 2016, par dave

  I have decided to create an input form for ffmpeg to go with my video uploader.

  This is for my video uploader plugin for a social site software. Users have told me that they want technical options for videos so they can choose the specific options they want including thumbnail options.

  I have been reading the ffmpeg docs most of the morning as well as watching some videos and i have come up with a rough draft of my form. The videos uploaded will more than likely be non gaming, personal and hobby videos.

  The goal here is to have a form that is easy enough for the non technical user, but technical for those that want the options. So i do plan to have a checkbox which allows the non technical user to skip the technical settings. This will result in a generic ffmpeg command with default settings. If they choose to use the technical specs then it will create a more specific ffmpeg command stream.

  here is what i have so far in the draft.

  select max size options ’50MB’,’100MB’,’200MB’,’500MB’,’650MB’,’750MB’,’1GB’,’2GB’,’3GB’

  input for thumbcapture in seconds maxlength 2 size 2

  input for video in ’mpg’,’wma’,’mov’,’flv’,’mp4’,’avi’,’qt’,’wmv’,’rm’

  option for video size ’200x100’,’320x240’,’560x315’,’640x360’,’853x480’,’1280x720’ not sure if i want to offer a custom slot or not.

  my thought here is that if they do not want the tech version of the form then the codecs will be b:v copy b:a copy (if that is the smart way to do it) or just left out and let ffmpeg decide what is best.

  ===== this is the technical part of the form =======

  select for acodec options copy, mp3, mp1, mp2, dnet, 28_8, wmav2, alac, cook

  select for vcodec option copy, ffv1, ms-cram, mpeg-4, rv40, wmv, xvid, mov, qt, avchd

  select for bitrate audio 32k, 64k, 128k

  select for bitrate video 1000k, 1200k, 1500k

  select for sampling rate 22050, 44100

  input for crf(mp4 out only) size 2 maxlength 2 minval 2 maxval 49

  input for avi quantanizer (avi out only) size 2 maxlength 2 minval 2 maxval 49

  ===== end technical form =====================

  select for video out ’avi’,’mp4’,’flv’

  that is what i have so far. How does that combination on the technical side look to you ffmpeg pros ?

  Any suggestions ? :)