• 0 Posts
  • 55 Comments
Joined 4 years ago
cake
Cake day: July 13th, 2020

help-circle


  • Exactly. I was surprised to see my unique named throw-away email being found in the leak, despite having changed it to an uniquely generated throw-away account alias in the year prior. But i don’t mind that much.

    However, bad security practices must still be pointed out regardless of it being applied to something important or large. I do still can criticize my friend decision to expose his local server at home, unsecured, even if in the grand matter of things, it is unlikely it will be exploited or impact him in any way.

    Now, the only issue having my throw-away address, is that i will have to throw it away once i start receiving spam on it. As far i know, the pirated database wasn’t shared nor necessarily conserved outside of prooving the original clowns hacktivists group involvment, outside of confirmed security analyst.



  • Not in the usual sense, because you can still fully fork it, use it, modify it and redistribute it freely like a FOSS software.

    You may use or modify the software only for non-commercial purposes such as personal use for research, experiment, and testing for the benefit of public knowledge, personal study, private entertainment, hobby projects, amateur pursuits, or religious observance, all without any anticipated commercial application. You may distribute the software or provide it to others only if you do so free of charge for non-commercial purposes.

    The only limitation which make it non-free is :

    Notwithstanding the above, you may not remove or obscure any functionality in the software related to payment to the Licensor in any copy you distribute to others.

    I don’t really understand if it “prevent you” to remove and/or prevent the modification of the donation to FUTO part of the code. Should not prevent you from adding yours on top of it (As in, adding a prompt as in "If you want to do donate to the project, you can donate to the original app owner (DONATE TO FUTO) or the maintainer of the fork you are using (DONATE TO THE MAINTAINER).) And the obvious limitation of making derivative work of it, non-free of course.

    Also, they do reserve themselves rights to abrodge the license for those who abridge it, which i don’t know how legally useful it may be, for license violations compared to protecting the GPL licenses from violations for example.

    tl;dr : Seems FOSS to me, as long as :

    • You don’t try to make it non-free
    • You don’t remove the donation to FUTO part of the app





  • What I don’t get, but maybe because of the lack of information I have on the topic

    Exactly. That’s also the issue there. It was opt-out by default AND didn’t seemed to give enough info to the end-user about what it does, and why it would be better to keep it enabled. Most people, complain about the forced default decision without any notice, and without any appropriate info to understand if it was a decent change or not. You should only enable it, IF you understand and ablige to what it does.





  • They don’t. They rely entirely on donations (and sponsorship donations). It also mean, they have less resources to maintain and develop their software, ESPECIALLY Conqueror since it’s not as much well-maintained compared to other parts of the KDE software suite. Plus, Firefox do maintain their own web-engine, while KDE just use the WebKit one, so even more reasons that Firefox can’t substain with the resources KDE currently has.






  • Speaking of doas, is there any advantage of using it when… sudo is still available to be used? I agree that most of the stuff we require to use doesn’t need all the options sudo as, but if it is for the sake of security, maintenance, and stability… is there any reason to use doas ON TOP of the already setup sudo or su? In the past, I even tried to just apply a simple alias to replace sudo with doas, but numerous scripts and programs when trying to request explicit super-user permissions, just didn’t know what to do with doas as expected, so this ain’t it.