• davel@lemmy.ml
    link
    fedilink
    English
    arrow-up
    59
    arrow-down
    2
    ·
    6 months ago

    Seriously, don’t sign a CLA

    A contributor license agreement, or CLA, usually (but not always) includes an important clause: a copyright assignment.

    This is a strategy employed by commercial companies with one purpose only: to place a rug under the project, so that they can pull at the first sign of a bad quarter. This strategy exists to subvert the open source social contract. These companies wish to enjoy the market appeal of open source and the free labor of their community to improve their product, but do not want to secure these contributors any rights over their work.

    List of some companies that use CLAs: https://en.wikipedia.org/wiki/Contributor_License_Agreement#Users

        • lemmyreader@lemmy.ml
          link
          fedilink
          English
          arrow-up
          4
          ·
          6 months ago

          No issues here whatsoever with other sites, including those that use L.E. certs. Weird. I guess it is a Tor circuit related issue. On another browser without Tor it loads fine.

          • Norah - She/They@lemmy.blahaj.zone
            link
            fedilink
            English
            arrow-up
            2
            ·
            6 months ago

            I clicked it now and it’s fine. I think sometimes LE certs haven’t renewed yet in their time zone of origin, even tho in the viewers time zone it is expired. As far as I can tell, ssl certs don’t have time zone fields for their dates, which seems kinds weird.

            • lemmyreader@lemmy.ml
              link
              fedilink
              English
              arrow-up
              2
              ·
              6 months ago

              Right. Thanks for sharing that thought. The weird thing was that the warning was about the domain name not being listed except for two other domains including one wildcard. Maybe it has to do with the fact the Drew had to deal with severe DDOS attacks some time ago, and had to move and rebuild services which may have included their blog. I had this with Tor browser, and then tested with LibreWolf configured for Tor and got the same error (I didn’t check the details of the two Tor circuits) I made a screenshot of the warning.