Sur d’autres sites (7722)

• Open letter to the European Parliament’s LIBE committee

  28 novembre 2019, par Joselyn Khor — Uncategorized

  An open letter to the European Parliament’s LIBE committee

  

  In an effort to stem the tide of external control over user privacy, Matomo has rallied with other like-minded companies like Protonmail, NextCloud, Tutanota and Mailfence, to advocate for pro-privacy changes to the European Commission’s “e-evidence” proposal.

  Excerpt from the letter : 

  “The Commission’s e-evidence proposal threatens the competitive advantage European tech businesses have over their American counterparts by undermining the protections we can provide to our customers. It breaks with the long-standing rule that only trusted national judicial authorities can order companies to hand over customer data for criminal investigations. Instead, the Commission’s e-evidence proposal would allow any foreign law enforcement agency from across the EU to force us to hand out customer data without our own authorities doublechecking the foreign order.

  “Different from American Big Tech firms, European privacy tech companies lack the resources to verify the legality of each foreign order. Because of the way the e-evidence proposal is phrased, we would not even be able to properly authenticate foreign authorities to ensure that we are not replying to a malicious actor – let alone object to an order if we found it to be unwarranted.”

  Matomo Founder, Matthieu Aubry emphasises, “It is time that privacy-minded tech companies work together to defend their users, their businesses, and the values they are founded on. This is why we are supporting Privacy Tech Europe.”

  Read our open letter to members of the LIBE Committee in full.

• Revision 113005 : Je suis encore tombé sur un bug dans l’évaluation côté php d’un ...

  21 décembre 2018, par root — Log

  Je suis encore tombé sur un bug dans l’évaluation côté php d’un
  afficher_si, lié à un champ sérializé avec des checkbox cumulatifs.
  Du coup, plutôt que d’essayer de debugger un code "pas terrible", et
  pour tout dire illisible, je reprend tout ou presque à zero.
  Ca permet notamment d’éviter d’avoir trop de chose en eval().
  L’idée est de procéder ainsi
  1. reperer toutes les @champs@ (==|IN| !IN| !=) "quelquechose"
  2. Evaluer chacune de ces expressions, en tenant compte du fait que IN signifie en réalit
  in_array, et du fait qu’on peut avoir des champs dont la valeur est un
  array sérializé, ou un array tout court.
  3. Puis évaluer les relations booléens entre chacune de ces
  expressions.
  Première étape : construire la fonction pour le 2 + les tests unitaires qui vont avec.

• Anomalie #4799 (Fermé) : Validité du RSS

  7 juillet 2021, par b b

  C’est intégré, je ferme car amha le point sur les multiples enclosures est négligeable, cf :

  According to the RSS Advisory Board’s Best Practices Profile, support for the enclosure element in RSS software varies significantly because of disagreement over whether the specification permits more than one enclosure per item. Although the author intended to permit no more than one enclosure in each item, this limit is not explicit in the specification.

  For best support in the widest number of aggregators, an item should not contain more than one enclosure.
  Meanwhile, be aware that multiple-enclosure support varies widely from tool tool to tool, and therefore should be avoided if at all possible.