• 0 Posts
  • 60 Comments
Joined 2 years ago
cake
Cake day: June 24th, 2024

help-circle
  • No it would not, because as soon as they implement such a blocklists feature and provide official blocklists they take over responsibility (morally and in some countries even legally) to ensure that they provide updated filter lists in a timely manner.

    Oh and then they have to implement something that vets and checks incoming scam alerts, to ensure that only valid claims are blocked. This will put unneeded strain on the personal and financial resources of KDE.


  • I don’t think that it is the responsibility of KDE or Discover to perform blacklisting or cleanup here.

    It is a upstream fuck Up by Canonical, again! The solution for this can’t be that developers of a frontend, like Discover, now reserve and use time and resources to add and maintain blocklists to clean up that mess that they didn’t created.

    We should get our torches and pitchforks and put all the blame where it belongs, at Canonical!




  • You can add your own signing keys to the UEFI and boot an modified bootloader and Kernel that you have signed yourself. So yes, it is possible to “lie”

    For such a locked down system, akin to game consoles or smartphones, would be needed. And even those get jail broken and manipulated, so “total security” on there is not complete but easier to check and ensure. Another way to make sure that the code is not manipulated would be to put all those games into the cloud and have every player only play via streaming. All the code would then run on secured, locked down and verified machines.