• 6 Posts
  • 135 Comments
Joined 6 months ago
cake
Cake day: March 12th, 2024

help-circle



  • I felt strong aversion and irritation throughout, thinking they were unnecessarily making enemies.

    They certainly have an extreme view and goal. And are personally invested to the point of seeing fellow collaborators on FOSS as enemies(?) now.

    Putting up barriers through segmentation and alternative tech creates silos. To reach new people I don’t think we can get around meeting users where they are and what they are familiar with.

    Bring value through FOSS, and hint and nudge them. If you meet them where they are and bring them to your software it’s already one more than none. You don’t need to get them to make a huge leap into a whole ecosystem of alternative software at once.

    Their categorical dismissal of other’s opinions or priorities certainly felt irritating to me. Maybe they care more about FOSS license than UX or features, but why is that the only correct view in their eyes? Blind users may not even be able to use FOSS alternatives when they lack accessibility features or quality.

    Even as a contributor to a project I don’t want to use a supportive side platform only for that when it’s annoying or cumbersome. I very well may just skip it, or leave as a contributor.

    I would have been interested in the premise; why they think advocating and exclusively FOSS is the only correct view and thing to do. The lack of a strong basis also made all that followed more irritating.














  • Its still the same extension, same source code, same logic, just less capable

    the same… but not the same… ??

    I think the technologies are quite different.

    uBOL is entirely declarative, meaning there is no need for a permanent uBOL process for the filtering to occur, and CSS/JS injection-based content filtering is performed reliably by the browser itself rather than by the extension. This means that uBOL itself does not consume CPU/memory resources while content blocking is ongoing – uBOL’s service worker process is required only when you interact with the popup panel or the option pages.

    Are you claiming non-lite does the same, plus more?

    You say it’s the same source code, but it’s a different source code repository. non-lite, lite.




  • the most relevant:

    To take advantage of the vulnerability, a hacker has to already possess access to a computer’s kernel, the core of its operating system.

    For systems with certain faulty configurations in how a computer maker implemented AMD’s security feature known as Platform Secure Boot—which the researchers warn encompasses the large majority of the systems they tested—a malware infection installed via Sinkclose could be harder yet to detect or remediate, they say, surviving even a reinstallation of the operating system.

    For users seeking to protect themselves, Nissim and Okupski say that for Windows machines—likely the vast majority of affected systems—they expect patches for Sinkclose to be integrated into updates shared by computer makers with Microsoft, who will roll them into future operating system updates.