A husband. A father. A senior software engineer. A video gamer. A board gamer.

  • 0 Posts
  • 23 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle
  • ulkesh@beehaw.orgtoOpen Source@lemmy.ml***
    link
    fedilink
    English
    arrow-up
    7
    ·
    edit-2
    5 months ago

    It’s strange to me that if the guy has such a problem with how open source software works (such as his code being used (ideally with license being followed), bugs, pull requests, etc), why did he not just keep it closed source?

    Seems to me he either didn’t understand how open source works, or he got in way over his head.

    You’re right, though, best to ignore.





  • I don’t have an answer for you, but I have a caution…

    I once worked for AT&T and worked on AT&T Messages.

    DO NOT USE IT, if it still exists, if you’re with AT&T. At the time I worked on it, there was no encryption except in-flight (https) – which means if I had had production access (and some people who worked there at my level, definitely did), I could have read all messages, blobs, everything. I was told after I quit that they intended to add encryption, but since AT&T would still hold the keys, it’s useless.






  • You are right. They can’t for every distro.

    But fedora/rhel, Ubuntu/debian, and arch-based distros are the most commonly used. So they can provide official packages for those, and/or as the OP said, provide an official flatpak.

    And to be fair, it’s a nice-to-have to have a better sense of trust, but given the unofficial ones are open source, it’s quite likely any maliciousness would be rooted out very quickly.