Recherche avancée

Sur d’autres sites (9192)

• Meta Receives a Record GDPR Fine from The Irish Data Protection Commission

  29 mai 2023, par Erin — GDPR

  The Irish Data Protection Commission (the DPC) issued a €1.2 billion fine to Meta on May, 22nd 2023 for violating the General Data Protection Regulation (GDPR). 

  The regulator ruled that Meta was unlawfully transferring European users’ data to its US-based servers and taking no sufficient measures for ensuring users’ privacy. 

  Meta must now suspend data transfer within five months and delete EU/EEA users’ personal data that was illegally transferred across the border. Or they risk facing another round of repercussions. 

  Meta continued to transfer personal user data to the USA following an earlier ruling of The Court of Justice of the European Union (CJEU), which already address problematic EU-U.S. data flows. Meta continued those transfers on the basis of the updated Standard Contractual Clauses (“SCCs”), adopted by the European Commission in 2021. 

  The Irish regulator successfully proved that these arrangements had not sufficiently addressed the “fundamental rights and freedoms” of the European data subjects, outlined in the CJEU ruling. Meta was not doing enough to protect EU users’ data against possible surveillance and unconsented usage by US authorities or other authorised entities.

  Why European Regulators Are After The US Big Tech Firms ? 

  GDPR regulations have been a sore area of compliance for US-based big tech companies. 

  Effectively, they had to adopt a host of new measures for collecting user consent, ensuring compliant data storage and the right to request data removal for a substantial part of their user bases. 

  The wrinkle, however, is that companies like Google and Meta among others, don’t have separate data processing infrastructure for different markets. Instead, all the user data gets commingled on the companies’ servers, which are located in the US. 

  Data storage facilities’ location is an issue. In 2020, the CJEU made a historical ruling, called the invalidation of the Privacy Shield. Originally, international companies were allowed to transfer data between the EU and the US if they adhered to seven data protection principles. This arrangement was called the Privacy Shield. 

  However, the continuous investigation found that the Privacy Shield scheme was not GDPR compliant and therefore companies could no longer use it to justify cross-border data transfers.

  The invalidation of the Privacy Shield gave ground for further investigations of the big tech companies’ compliance statuses. 

  In March 2022, the Irish DPC issued the first €17 million fine to Meta for “insufficient technical and organisational measures to ensure information security of European users”. In September 2022, Meta was again hit with a €405 million fine for Instagram breaching GDPR principles. 

  2023 began with another series of rulings, with the DPC concluding that Meta had breaches of the GDPR relating to its Facebook service (€210 million fine) and breaches related to Instagram (€180 million fine). 

  Clearly, Meta already knew they weren’t doing enough for GDPR compliance and yet they refused to take privacy-focused action. 

  Is Google GDPR Compliant ?

  Google has a similar “track record” as Meta when it comes to ensuring full compliance with the GDPR. Although Google has said to provide users with more controls for managing their data privacy, the proposed solutions are just scratching the surface. 

  In the background, Google continues to leverage its ample reserves of user browsing, behavioural and device data in product development and advertising. 

  In 2022, the Irish Council for Civil Liberties (ICCL) found that Google used web users’ information in its real-time bidding ad system without their knowledge or consent. The French data regulator (CNIL), in turn, fined Google for €150 million because of poor cookie consent banners the same year. 

  Google Analytics GDPR compliance status is, however, the bigger concern.

  Neither Google Univeral Analytics (UA) nor Google Analytics 4 are GDPR compliant, following the Privacy Shield framework invalidation in 2020. 

  Fines from individual regulators in Sweden, France, Austria, Italy, Denmark, Finland and Norway ruled that Google Analytics is non-GDPR compliant and is therefore illegal to use. 

  The regulatory rulings not just affect Google, but also GA users. Because the product is in breach of European privacy laws, people using it are complacent. Privacy groups like noyb, for example, are exercising their right to sue individual websites, using Google Analytics.

  How to Stay GDPR Compliant With Website Analytics 

  To avoid any potential risk exposure, selectively investigate each website analytics provider’s data storage and management practices. 

  Inquire about the company’s data storage locations among the first things. For example, Matomo Cloud keeps all the data in the EU, while Matomo On-Premise edition gives you the option to store data in any country of your choice. 

  Secondly, ask about their process for consent tracking and subsequent data analysis. Our website analytics product is fully GDPR compliant as we have first-party cookies enabled by default, offer a convenient option of tracking out-outs, provide a data removal mechanism and practice safe data storage. In fact, Matomo was approved by the French Data Protection Authority (CNIL) as one of the few web analytics apps that can be used to collect data without tracking consent. 

  Using an in-built GDPR Manager, Matomo users can implement the right set of controls for their market and their industry. For example, you can implement extra data or IP anonymization ; disable visitor logs and profiles. 

  Thanks to our privacy-by-design architecture and native controls, users can make their Matomo analytics compliant even with the strictest privacy laws like HIPAA, CCPA, LGPD and PECR. 

  Learn more about GDPR-friendly website analytics.

  Final Thoughts

  Since the GDPR came into effect in 2018, over 1,400 fines have been given to various companies in breach of the regulations. Meta and Google have been initially lax in response to European regulatory demands. But as new fines follow and the consumer pressure mounts, Big Tech companies are forced to take more proactive measures : add opt-outs for personalised ads and introduce an alternative mechanism to third-party cookies. 

  Companies, using non-GDPR-compliant tools risk finding themselves in the crossfire of consumer angst and regulatory criticism. To operate an ethical, compliant business consider privacy-focused alternatives to Google products, especially in the area of website analytics. 

• Revision 8c1f071f1e : Allocate buffers based on correct chroma format The encoder currently allocates

  17 juin 2014, par Adrian Grange

  Changed Paths :
   Modify /vp9/common/vp9_alloccommon.c

  
   Modify /vp9/common/vp9_alloccommon.h

  
   Modify /vp9/common/vp9_scale.h

  
   Modify /vp9/encoder/vp9_encoder.c

  
   Modify /vp9/encoder/vp9_firstpass.c

  
  
  Allocate buffers based on correct chroma format

  The encoder currently allocates frame buffers before
  it establishes what the chroma sub-sampling factor is,
  always allocating based on the 4:4:4 format.

  This patch detects the chroma format as early as
  possible allowing the encoder to allocate buffers of
  the correct size.

  Future patches will change the encoder to allocate
  frame buffers on demand to further reduce the memory
  profile of the encoder and rationalize the buffer
  management in the encoder and decoder.

  Change-Id : Ifd41dd96e67d0011719ba40fada0bae74f3a0d57

• Thread in Thread

  28 mai 2014, par user3679963

  My company is working for visual effects and we set up an internal shot playback via a browser for our clients. For that we need to upload the video file to a FTP server.

  I want to convert a image sequence to mp4 and upload this file directly after the rendering will finish.

  For that I use :

  • one command prompt to convert
  • one command prompt to get an `md5hash
  • one for uploading the file

  I already achieved that on my local computer, where I just chained os.system('command').

  After recognizing that the program freezes very long with longer image sequences I changed the script to spawn a thread using the os.system chain.
  But on the Render Farm Server this script does not actually work.

  The RenderFarm Server runs Python 2.5

  There are some code examples :

  class CopraUpload(threading.Thread):
  
  
  
      # initializing Thread
  
      # via super constructor
  
      def __init__(self):
  
          threading.Thread.__init__(self)
  
  
  
  
  
      # return the size of the
  
      # created mp4 file
  
      #
  
      # @return: the file size in byte
  
      def _getFileSize(self):
  
  
  
  
  
      # creates a random id for organising
  
      # the server upload used as flag
  
      #
  
      # @return: a hash
  
      def _getHash(self):
  
              self.fileLoc = str(self.outputfileName + '.mp4')
  
              self.fileLoc = os.path.normpath(self.fileLoc)
  
              return str(os.path.getsize(self.fileLoc))
  
  
  
      # integrates the "missing" data for the xml file
  
      # generated post render from the mp4 file
  
      def _setPreviewDataToXML(self):
  
          self.xmlFile = str(self.outputfileName + '_copraUpload.xml')
  
          self.xmlFile = os.path.normpath(self.xmlFile)
  
  
  
          ett = ET.parse(self.xmlFile)
  
          root = ett.getroot()
  
          for child in root.getiterator('preview_size'):
  
              child.text = self._getFileSize()
  
          for child in root.getiterator('preview_md5hash'):
  
              child.text = self._getHash()
  
          ett.write(self.xmlFile)
  
  
  
  
  
      # create a connection to a ftp server
  
      # and copies the mp4 file and the xml file
  
      # on the server
  
      def _uploadToCopra(self):
  
  
  
          os.system(self.uploadCommand)
  
          #process = Popen(self.uploadCommand)
  
  
  
  
  
      # the main function of the program
  
      # called via start from a Thread Object
  
      def run(self):
  
  
  
          # the command which will be send to the commando shell
  
          # for further adjustments see ffmpeg help with ffmpeg.exe -h
  
          FinalCommand = self.ffmpegLocation + " -r "+ self.framerate + " -i " + self.inputPath + " -an -strict experimental -s hd720 -vcodec libx264 -preset slow -profile:v baseline -level 31 -refs 1 -maxrate 6M -bufsize 10M -vb 6M -threads 0 -g 8 -r " + self.framerate + " " + self.outputfileName + ".mp4 -y"
  
          FinalCommandList = FinalCommand.split(" ")
  
  
  
  
  
          # calling the program
  
          print "Start ffmpeg convertion"
  
  
  
          outInfo = os.path.normpath("C:\\Users\\sarender\\Desktop\\stdoutFFMPEG.txt")
  
          outError = os.path.normpath("C:\\Users\\sarender\\Desktop\\stderrFFMPEG.txt")
  
          stdoutFile = open(outInfo,"w")
  
          stderrFile = open(outError,"w")
  
  
  
          handle = subp.check_all(FinalCommandList,stdout = stdoutFile,stderr = stderrFile)
  
          handle.communicate()
  
          stdoutFile.close()
  
          stderrFile.close()
  
          print "Convertion from ffmpeg done"
  
  
  
          # fill the xml file with the missing data
  
          # - preview file size
  
          # - preview md5hash
  
          self._setPreviewDataToXML()
  
          self._uploadToCopra()
  
          print "---------------------------------->FINISHED------------------------------------------------------>"
  
  
  
  
  
      # Creates a callable Thread for the Copra Upload.
  
      # start is calling the run method which will start the Uploading

  and the main start :

      if "$(RenderSet.writenode)" == "PREVIEW":
  
          print "---------------------------------->Initializing Script------------------------------------------------------>"
  
          process = CopraUpload()
  
          process.start()

  What happens :

  The script starts after the rendering and ffmpeg converts the image sequence and creates an mp4. But it stops after that. It does not print "Conversion from ffmpeg complet". Just stops the script.

  It actually should create the Thread converting with ffmpeg and wait until it finishes. After it should write some stuff in an xml file and upload both to the server.

  Do I miss something ? Is subprocess within a thread not the way to go ? But I need a Thread because I can not deadlock the render management server.