3 Matching Annotations
  1. Last 7 days
    1. When thinking about your relationship with AI in general, it helps to consider a spectrum. On one end, you reject the technology completely: you don’t want it anywhere near your notes. On the other end, the AI completely replaces you. Neither extreme is desirable, so most approaches fall somewhere on the spectrum.

      This is akin to [[Monstertheorie 20030725114320]] spectrum (kiil the monster, adapt the monster, adapt cultural categories, embrace the monster) It is sort of logical that most of us will fall in the middle 2 groups, adapting both the tech and ourselves.

  2. Jun 2024
  3. Apr 2024
    1. This is not the first time an open source package has been hijacked after a maintainer was added – it actually happens all the time in Python repositories and such, and has been one of the leading causes of infostealers and coin miners in development pipelines. It is absolutely not a surprise that somebody is targeting open source compression libraries that systemd loads.. and it is also sadly not a surprise that people online bully the creators of these libraries, either.

      Wrt [[XZ open source kwetsbaar door psyops 20240331083508]] and examples referred to here, the author focuses on technology fixes to reduce risks. Whereas most of the problems highlighted are social aspects, for which no other solution is suggested than paying OSS devs who maintain stuff. That may well alleviate some of the social aspects that became an attack surface, but does nothing to look at Q of connections between devs and knitting those into relationships that are more resistant to social engineering and psyops. That and more transparency both on the social side of things and the chains. OSS is open source wrt the piece of software in front of you only.