Recherche avancée

Médias (1)

Mot : - Tags -/intégration

Autres articles (64)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

  • Participer à sa traduction

    10 avril 2011

    Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
    Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
    Actuellement MediaSPIP n’est disponible qu’en français et (...)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

Sur d’autres sites (11021)

  • Evolution #3895 (Fermé) : Permettre d’activer sur certains sites le flag Secure du cookie de session

    31 janvier 2017, par - Equipement

    Le flag Secure permet de laisser la décision d’envoi ou non du cookie au navigateur. Il signifie “n’envoie le cookie que sur les moyens de communication que tu considères comme sécurisés”.

    En général, le protocole HTTPS est considéré comme un canal de communication sécurisé, mais pas le protocole HTTP. Aussi, un cookie de session avec le flag Secure ne sera envoyé que si les requêtes et réponses sont en HTTPS. Ceci évite le vol de session durant le transport du cookie de session en HTTP.

    Sur un site entièrement en HTTPS, il peut exister des situations dans lesquelles les cookies transitent en clair (HTTP). Par exemple, lorsqu’un utilisateur cherche à joindre le site en HTTP (après avoir cliqué sur un lien par exemple). L’utilisateur est alors immédiatement redirigé vers l’HTTPS mais la première requête aura été effectuée en HTTP, et s’il possédait un cookie à ce moment là, il sera envoyé en HTTP (lors de cette première requête), c’est ce qu’empêche le flag Secure.

    Pour en savoir plus : https://www.information-security.fr/securite-sites-web-lutilite-flags-secure-httponly/

    Le patch proposé ci-dessous n’est activé que si le fichier mes_options.php contient :

    define("_COOKIE_SECURE_FLAG", true) ;

    Le patch consiste à remplacer, dans la fonction spip_setcookie :

    $httponly = in_array($name, explode(’ ’, ’spip_session’)) ;
    

    par :

    $httponly = in_array($name, explode(’ ’, ’spip_session’)) ;
    if ($httponly AND defined(’_COOKIE_SECURE_FLAG’) AND _COOKIE_SECURE_FLAG)
        $secure = true ;
    

    Cordialement

    Equipement

  • Announcing Long Term Support in Piwik 2 – The analytics platform for your mission critical projects

    11 janvier 2016, par Matthieu Aubry — About, Development

    We are proud to announce our Long Term Support (LTS) for Piwik 2.X !

    Why Long Term Support (LTS) ?

    Part of our mission is to ready Piwik for the enterprise — and ready the enterprise for Piwik. Our fast release cycle and our ability to quickly innovate has served us well for the past seven years and has lead Piwik to being one of the most popular open source projects, used by over one million websites worldwide. But Piwik’s success today has also shown us that this fast release cycle is not suited for all users and customers. Like most large open source projects (such as Ubuntu, Firefox, Debian, Symfony, Node.js, etc.) at Piwik we now also offer a Long Term Support release which gives users the confidence that Piwik can be used for mission critical projects for months to come.

    What does LTS mean for Piwik ?

    For the duration of the LTS period, Piwik 2.X will continue to receive the following fixes :

    • Critical bugs causing data loss or data corruption.
    • Major and Critical security issues.

    Our goal is to offer you a Piwik LTS release that you can trust for all your mission critical projects.

    How long will Piwik 2.X be supported ?

    Piwik 2.X will be supported for at least 12 months after the initial release of Piwik 3.0.0.
    Piwik 3.0.0 is expected to be released in the second half of 2016.
    This means that Piwik 2.X will be supported at least until the second half of 2017.

    Which Piwik version is LTS ?

    The latest Piwik 2.16.X release is our Long Term Support version.

    How do I benefit from the LTS version ?

    To get the full benefits of Piwik LTS, please make sure you are using the latest LTS version. First, update to the latest Piwik 2.X version, then Configure Piwik to use the LTS release channel and then update to the latest LTS version.

    How do I configure Piwik to use the LTS version ?

    By default, Piwik will not use the LTS version. When you use the one-click update your Piwik instance will be updated to the very latest release : when Piwik 3.0.0 will be released, the one click update will update your instance to 3.0.0. It is however possible to configure your Piwik so that you will stay on Piwik 2.X and keep using the LTS Long Term Support version :

    • Login Piwik as the Super User,
    • Go to Settings > General > Update settings,
    • Under “Release channel” click “Latest stable 2.X Long Term Support version”, and click “Save”.

    How do I get professional Piwik Support ?

    If you need professional support for your Piwik service get in touch with the Piwik PRO experts.


    For other questions, feedback or discussion, feel free to join our forums and comment on this LTS forum post.

    We wish you all a fantastic year 2016 !

  • How to know the delay of frames between 2 videos, to sync an audio from video 1 to video 2 ?

    8 janvier 2021, par jaimepm

    world.

    


    I have many videos that I want to compare one-to-one to check if they are the same, and get from there the delay of frames, let's say. What I do now is opening both video files with virtualdub and checking manually at the beginning of video 1 that a given frame is at position, i.e., 4325. Then I check video 2 to see the position of the same frame, i.e., 5500. That would make a delay of +1175 frames. Then I check at the end of the video 1 another given frame, position let's say 183038. I check too the video 2 (imagine the position is 184213) and I calculate the difference, again +1175 : eureka, same video !
The frame I chose to compare aren't exactly random, it must be one that I know it is exactly one I can compare to (for example, a scene change, an explosion that appears from one frame to another, a dark frame after a lighten one...) and I always try to check for the first comparison frames within the first 10000 positions and for the second check I take at the end.
What I do next is to convert the audio from video 1 to video 2 calculating the number of ms needed, but I don't need help with that. I'd love to automatize the comparison so I just have to select video 1 and video 2, nothing else, that way I could forget forever virtualdub and save a lot of time.

    


    I'm tagging this post as powershell too because I'm making a script where at the moment I have to introduce the delay between frames (after comparing manually) myself. It would be perfect that I could add this at the beginning of the script.

    


    Thanks !