Recherche avancée

Sur d’autres sites (4539)

• Today we celebrate Data Privacy Day 2019

  28 janvier 2019, par Jake Thornton — Privacy
  Today we celebrate Data Privacy Day 2019 !!!

  What is Data Privacy Day ?

  Wikipedia tells us that : The purpose of Data Privacy Day is to raise awareness and promote privacy and data protection best practices.

  Our personal data is our online identity. When you think what personal data means – our phone records, credit card transactions, GPS position, IP addresses, browsing history and so much more. All so valuable and personal to us as human beings.

  That’s why we cannot take our personal data online for granted. We have a right to know which websites collect our data and how it’s then used, something that’s often not visible or easily recognisable when browsing.

  What Data Privacy Day means to Matomo

  Every year the team at Matomo uses this day as a chance to reflect on how far the Matomo (formerly Piwik) project has come. But then also reflect how far we still have to go in spreading the message that our data and personal information online matters.

  2018 saw the introduction of the EU General Data Protection Regulation (GDPR) to protect people’s data online. As a team, Matomo was at the forefront of this development in the analytics space and have since built a GDPR Manager to ensure our users can be fully compliant with the GDPR.

  With every new release of Matomo, we are ensuring that security continues to be at the highest standard and we will continue to be committed to our bug bounty program. Our most recent release of Matomo 3.8.0 alone added a Two Factor Authentication (2FA) feature and a password brute force prevention.

  What next for Matomo and data privacy ?

  As always, security is a top priority for every new release of Matomo and continues to only get better and better. We have a duty to spread our message further that the protection of personal data matters and today is a vital reminder of that. We are, and forever will be, the #1 open-source (and free to use) web analytics platform in the world that fully respects user privacy and gives our users 100% data ownership.

  In 2018 we changed our name, we updated our logo and website, and advanced our platform to compete with the most powerful web analytics tools in the world, all so we can spread our message further and continue our mission.

  Come with us on this exciting journey. Now is the time to take back control of your data and let’s continue creating a safer web for everyone.

  Please help us spread this message.

• Converting WebM audio to mp3 using ffmpeg and Rails

  30 avril 2021, par Garrett Bodley

  I created an online step sequencer and want to add functionality so that users can record the audio and save it as an mp3 on their local machine. I've been able to use the WebAudioAPI to record the sound generated in the browser window and send it to my Rails backend as a WebM blob. I am attempting to incorporate ffmpeg using the Streamio gem.

  


  How do I convert that blob to mp3 ? I'm planning on making a Recording model that belongs_to :user and has_one_attached :audio. I imagine I should use a before_save callback to process the blob ? What's confusing to me is that it seems streamio creates a new copy of the file when transcoding. How do I convert the blob to mp3 in place ?

  


  I've seen some posts where people call ffmpeg using system("ffmpeg code goes here") but I don't really understand how to grab the output so that ActiveStorage can link the resulting file to my models and whatnot.

  


  To add complexity to all of this is that I ultimately want to host this publicly and store the audio in a Cloudinary folder, which I imagine would change the process quite a bit. As you can tell I'm a bit confused as to how best to approach this problem. Any help would be greatly appreciated !

  


• Best Web Video Encoding Practices for IOS (FFMpeg)

  21 juin 2012, par MagicMushroom

  I am working on an online video repository system for a client, written mostly in PHP. At the moment I am building a mobile version of our desktop website. Our desktop site allows users to watch videos in the browser, much like YouTube.

  My client uploads videos through the manager interface I have created, and my application uses FFmpeg on the server to transcode his videos into several resolutions and bitrates. I am no expert on FFmpeg, and while I do not know the ins and outs of each individual setting, I do understand how it works as a whole. Right now, we are using the mp4 container format with the h.264 codec to encode our videos. Our command looks like :

  ffmpeg -y -i "INPUT FILE.mov" -f mp4 -s 640x480 -vcodec libx264 -preset fast -maxrate 1500 -bitrate 1000 -bufsize 4096 -acodec libfaac -ab 192 -ac 2 "OUTPUT_FILE.mp4" >> "FILE.log" 2>&1 &

  I'm hoping to gain information about best practices with encoding video for web streaming on IOS and other mobile devices using FFmpeg. What resolutions and settings make for good mobile streaming video ? How can I ensure maximum compatibility across the sea of Android devices ?