Web Developer by day, and aspiring Swift developer at night.

  • 0 Posts
  • 38 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle



  • These sources report to Proton any time they find leaked information or data stolen in a hack from a third-party online service that’s tied to a Proton Mail email address or a Proton Pass alias.

    I’m inclined to think that they look for known data breaches using your email address or alias, and if found they will tell you what kind of data is associated with the breach; e.g., social security, physical address, etc. So they don’t need to actually know that information, because they’re not searching using that information.


  • GPLv3 is virally open source (copyleft), BSD 2-Clause is not.

    Your first statement is patently false and misleading.

    Two variants of the license, the New BSD License/Modified BSD License (3-clause), and the Simplified BSD License/FreeBSD License (2-clause) have been verified as GPL-compatible free software licenses by the Free Software Foundation, and have been vetted as open source licenses by the Open Source Initiative. (Wikipedia)

    Being “copyleft” is not a requirement for being open source. Maybe you’re thinking of free software. There are differences, but as the FSF is quoted, they are also very similar.

    GPLv3 ensures free software remains free and contributions cannot be exploited and withheld from the community. BSD2C does not.

    To my understanding, and if I’m wrong I’d love to know why, both GPLv3 and BSD2 both ensure the openness of software. They just go about it differently. GPL (I’m not super versed at v3) basically means any modifications to GPL’d code must also be GPL’d, and source made available; also, if you statically link against other GPL’d code, your code must be GPL’d. Dynamic linking (or linking against LGPL code, like glibc) does not have this requirement.

    With BSD code, your only requirement is that the code (or binaries) must remain BSD2. Sure, someone can make modifications and keep them to themselves for fun and profit. But that doesn’t mean the rest of the community has to follow suit. The original code remains open and available with no license modifications. If a company owns BSD2 code, and goes under, the community can simply fork the code and take ownership as they please.

    Neither license is perfect, and I’m sure we could find plenty of examples of people/companies that have abused both licenses.









  • If only there was an article that described the monetization of such a model… oh, wait…

    We want people to make money off of their software, but we recognize that the community benefits from a project’s economic success. Within fair-code, creators have the exclusive right of commercializing their work, ensuring long-term profitability. Companies that wish to commercialize the software can contact the author and form a business relationship that benefits both parties!