Solar Bear

  • 0 Posts
  • 137 Comments
Joined 1 year ago
cake
Cake day: June 27th, 2023

help-circle
  • Criticizing people’s past and current actions relating to the subject and bringing up their direct history relavent to the subject is not a personal attack, nor is it out of line to point out he does his to advance his political agenda within the project, which is why he got banned in the first place. All of this directly relates to the subject at hand.

    You know what doesn’t relate to the subject at hand? Your random little “sjw gender terrorists” comment. But it does make it rather clear why you want to obfuscate the facts about Srid’s history with the project, subsequent ban, and continued amplification of drama and general shit-stirring ever since.




  • You should know that the guy you cited in the second link, Srid, is a well-known right-wing shit-stirrer who is banned from basically all NixOS spaces because he cannot peacefully coexist. He literally gets up day after day with the seemingly sole purpose of fueling drama and causing problems. Don’t take his opinion at face value, he wants to see the project burn down and this colors his interpretation of events.

    NixOS is going through a rocky moment for sure, but there’s no indication it will implode currently.


  • Have it just be form-fitted outside contacts, with magnetic adhesion to hold the plug in place.

    I actually really like this idea. If we’re breaking backwards compatibility anyways, let’s do something useful with it. This form factor was invented in the 1950s. I’m sure we can do something better now.

    We need to move away from everything having a battery anyways. Wireless headphones were a mistake. Now people are walking around with 4-6 batteries on them at all times. Phone, laptop, earbuds, earbud case, battery backup, smart watch. Batteries aren’t great for the environment, not to mention they typically condemn something to being tech waste in a few short years. We need to significantly rethink this model.










  • Solar Bear@slrpnk.nettoLinux@lemmy.mlThoughts on this?
    link
    fedilink
    English
    arrow-up
    26
    ·
    7 months ago

    it’s probably time to come to terms with the fact that better alternatives would have arisen had anyone thought they could truly manage it.

    This is the most important takeaway. There’s a lot of people whining about Wayland, but Wayland devs are currently the only people actually willing to put in the work. Nobody wants to work on X and nobody wants to make an alternative to Wayland, so why do we keep wasting time on this topic?






  • Solar Bear@slrpnk.nettoLinux@lemmy.mlCanonical changes the license of LXD to AGPL
    link
    fedilink
    English
    arrow-up
    17
    arrow-down
    1
    ·
    edit-2
    7 months ago

    The full details are complex but I’ll give you the basic gist. The original GPL licenses essentially say that if you give somebody the compiled binary, they are legally entitled to have the source code as well, along with the rights to modify and redistribute it so long as they too follow the same rules. It creates a system where code flows down freely like water.

    However, this doesn’t apply if you don’t give them the binary. For example, taking an open source GPL-licensed project and running it on a server instead. The GPL doesn’t apply, so you can modify it and do whatever, and you aren’t required to share the source code if other people access it because that’s not specified in the GPL.

    The AGPL was created to address this. It adds a stipulation that if you give people access to the software on a remote system, they are still entitled to the source code and all the same rights to modify and redistribute it. Code now flows freely again, and all is well.

    The only “issue” is that the GPL/AGPL are only one-way compatible with the Apache/MIT/BSD/etc licenses. These licenses put minimal requirements on code sharing, so it’s completely fine to add their code to GPL projects. But themselves, they aren’t up to GPL requirements, so GPL code can’t be added to Apache projects.


  • Most Snaps have apt or Flatpak alternatives.

    I’m simply not going to support a distro that creates a proprietary service and ships it as the default source of software. I will support and use distros that open source their code so that everyone can benefit from it. Whether workarounds or alternatives exist is unimportant, my prime issue with Ubuntu and Canonical is with their principles, not Ubuntu’s quality as a product to be consumed by me.