
Recherche avancée
Autres articles (81)
-
Use, discuss, criticize
13 avril 2011, parTalk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
A discussion list is available for all exchanges between users. -
Keeping control of your media in your hands
13 avril 2011, parThe 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 (...) -
Support audio et vidéo HTML5
10 avril 2011MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)
Sur d’autres sites (4534)
-
How to Track Website Visitors : Benefits, Tools and FAQs
31 août 2023, par Erin — Analytics Tips, Marketing -
It’s January 28th : Let’s celebrate Data Privacy !
29 janvier 2018, par Matomo Core TeamIt is a special Sunday here for us at Matomo, as today is international Data Privacy Day. The day was created in 2007 to raise awareness of the importance of data privacy for people and businesses worldwide.
What is data privacy about ?
Personal data refers to any data which is collected and can be linked to an individual human being such as phone records, credit card transactions, GPS position, IP addresses, browsing history… So basically, personal data refers to your identity online. That is why you should be highly concerned about sending your personal data (or your customers’ personal data) away. It is important to be aware of who is collecting the information and how it is being used.
What big changes are happening in 2018 ?
New privacy regulations GDPR comes into play next May 2018 : GDPR will bring about some changes (in the right direction) by making people and businesses aware of what data privacy means, and what they should be doing to protect their customers’ privacy. With these new regulations, data privacy awareness is reaching a critical milestone this year.
How can I protect my privacy ?
Here are a few tips to protect your privacy :
- Educate yourself on the importance of privacy : the more informed you are the better.
- Use open source solutions where you can keep full control of your own data (such as NextCloud instead of Dropbox and of course Matomo instead of Google Analytics),
- Experiment with different online services to protect your data privacy, for example using an alternative search engine (such as DuckDuckGo instead of Google) or an alternative email provider (such as ProtonMail).
What’s coming next for Matomo and Privacy ?
Here at Matomo, we are building the leading decentralised open web analytics platform. We’re currently working on new sets of privacy features to make compliance with GDPR a breeze. Stay tuned here to be notified when we launch the new privacy compliance tools !
And in case you’ve missed this important info, you may be interested in :
- Configure Privacy Settings in Matomo
- 11 ways Matomo Analytics helps you to protect your visitors privacy
The post It’s January 28th : Let’s celebrate Data Privacy ! appeared first on Analytics Platform - Matomo.
-
Anomalie #4057 (Nouveau) : Charset des feuilles CSS compilées
8 décembre 2017Le commit r5618 de 2006 indiquait que Firefox sans déclaration spécifique de charset appliquait un charset iso par défaut avec un type text/html.
Du coup, il a été mis explicitement cet envoi de charset dans tous les CSS envoyés avec cette ligne :#HTTP_HEADERContent-Type : text/css ; charset=iso-8859-15
De nos jours, cela pose différents soucis :
- le charset conseillé est utf-8 : https://www.w3.org/International/questions/qa-css-charset
- des propriétés "content : xxx" avec un caractère UTF-8 peut être mal interprété selon le caractère.
- Firefox ne réagit plus du tout comme ça maintenant :) Il garde bien le type CSS et prend par défaut un charset UTF-8.
- accessoirement certaines librairies ajoutent la directivecharset "UTF-8";
en tête de fichier, et du coup, ça ne colle pas du tout.Les fichiers de SPIP et particulièrement donc ceux en questions sont normalement déjà tous enregistrés en utf-8.
Je propose de remplacer donc la directive (et le commentaire associé) par :[(#REM)