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

help-circle

  • 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



  • Oh no.

    Anyway, glad that Mastodon isn’t down due to it’s decentralized nature. That’s something bad actors (such as those who are doing that DDOS) and most users (which make the mstdn.social instance and a few other ones, the main ~80% of all Mastodon) fail to to understand, the beauty of it.

    (Still feeling bad for the instance and it’s users, despite the sarcastic tone)




  • 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.









  • Well, i believe in all showcased cases from people here, they are NOT replacing sudo entirely (Except if some are from BSD or if I’m incorrect with this assumption). They are just replacing their user habit with doas and use that command instead. In the end, all unix scripts or apps expect using sudo (If not, su) so… ### What’s even the need to ?

    • Size : Installed on top of the already system present sudo.
    • Security : Only perhaps if you made a sudo alias to doas (But since it isn’t entirely 1:1 identical, if anyone have a cleaner way of implementing that, I’m all hear)
    • Simplicity : You now have two tools. A easy to use keycard, and a key. The second is more complicated to use, so you use it rarely but it’s still two tools instead of one.
    • Less dependencies : Again, unless you can actually replace it ENTIRELY, it’s just an added tool (Still almost dependency free)

    Really looking to corrections if i do some