all 10 comments

sorted by: hot top controversial new old
[–] 19 points 1 year ago*

AGPLv3 is the only way to go. If you want to make open source software, you need a license that protects your project and your users from corporate abuse.

  • source
  • [–] 25 points 1 year ago (2 children)

    How can sole maintainers work with multi-billion corporations without being taken advantage of?

    They can't, thats why GPL is noncommercial. Capitalism is an exploitative system that relies on power imbalance. As soon as MS reached out, he should have made it clear they can't even look at his code for ideas without a contract and payment. He shouldn't have told them anything else without a contract. Papers with legal claims on them are the only language business speaks.

  • source
  • hideshow 2 child comments
  • [–] 19 points 1 year ago (3 children)

    I'm almost sure they steal ideas that people write in teams chat too..

  • source
  • hideshow 3 child comments
  • [–] 2 points 1 year ago (1 child)

    Hey maybe i can get microsoft steal my idea for a service that combines local radio news with spotify/podcasts

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 1 year ago

    I would also try to let them steal the current idea of European countries to stop using HW and SW solutions made in US, and switch to locally provided services. We'd avoid having around the globe those strange billionaires semi-tech bots

  • source
  • parent
  • [–] 12 points 1 year ago

    This came out a while ago. The developer used a license that said, "Steal this software, I don't care." Then he was shocked Pikachu when it was stolen.

    His problem is the exact reason GPL was created.

  • source
  • [–] 1 point 1 year ago

    Hoping that embrace extend extinguish Microsoft would be helping is quite naive I think.

  • source
  • 20 comments in c/linux@lemmy.ml view that post
    [–] 29 points 1 year ago (3 children)

    Active Directory and Exchange were both based on open source projects. Embrace, extend, extinguish is Microsoft’s whole jam.

  • source
  • hideshow 3 child comments
  • [–] 4 points 1 year ago (1 child)
  • [–] 5 points 1 year ago

    As with a lot of 90s software, it’s a bit more complicated than which source code did they download (or, rather, mail order on floppy… because it was the 90s). Not the least of which is due to the fact that many of the projects don’t exist anymore and there weren’t that many copies to begin with.

    However, they both embrace and extend LDAP and Kerberos among other open and not open projects of the time. Both choices were related to the results of the Protocol Wars and Microsoft’s attempts, in the 90s, to do to the Internet what Google is doing today.

  • source
  • parent
  • [–] 36 points 1 year ago (1 child)

    Poor license choice. If you really want to enforce it, don't rely on MIT.

  • source
  • hideshow 1 child comment
  • [–] 15 points 1 year ago

    Same old (50 years and more) M$ bullshit lies.

  • source
  • [–] 15 points 1 year ago (1 child)

    They stole a lot others already. Winget was prior Appget, before they duped the inventor. And what was the case two months ago?

  • source
  • hideshow 1 child comment
  • [–] 60 points 1 year ago (2 children)

    This came out a while ago. The developer used a license that said, "Steal this software, I don't care." Then he was shocked Pikachu when it was stolen.

    His problem is the exact reason GPL was created.

  • source
  • hideshow 2 child comments
  • [–] 21 points 1 year ago

    Stolen? It was forked as is allowed by the MIT license. With GPL as well there is no „you cannot fork” rule, you can do exactly the same thing. The author misunderstood that „you have to push the changes to upstream”, which is not in any of those licenses.

  • source
  • parent
  • [–] 4 points 1 year ago*

    While I'm usually all for Free software (as opposed to open-source software),

    His problem is the exact reason GPL was created.

    Nah, his problem is that Microsoft has much billions of dollars and so doesn't give a fuck about any licenses on projects by small developers. They simply ignored even the terms of the MIT license (which required MS to keep the original copyright notice, which they didn't). GPL would've done squat here since it also allows for forking (by design), but also because the US legal system is cooked, and people don't have many rights left when it comes to a dispute with a corpo.

  • source
  • parent
  • [–] 48 points 1 year ago (4 children)

    This is clickbait. tl;dr a guy released MIT-licensed software, Microsoft forked and renamed it as they're legally allowed to do. Hell they could even close the source and sell it if they wanted to.

  • source
  • hideshow 4 child comments
  • [–] 16 points 1 year ago (1 child)

    Forked it, renamed it, and changed nothing but the license on it.

    What's stopping it from becoming the defacto version putting the original into the point where it's no longer worth maintaining, then Microsoft pulls it and sells it as a subscription service?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 40 points 1 year ago

    Nothing, because the author explicitly chose to allow this kind of behavior. Paraphrasing one of the Youtube comments on the video: the author picked a cuck license and then got cucked, what a shock!

    It's funny how apropos cuck really is here. We all recognize that a woman (Microsoft) cheating on her husband (the guy in question) is a bad thing, but we no longer view it that way when we learn that the man consented, video taped, and gets off to it. If you really want to stop this kind of thing, simply choose a better license like the GPL that forbids this behavior.

  • source
  • parent
  • [–] 13 points 1 year ago (1 child)

    I mean they should have given him credit. That's what they owe him (all they owe him) under the MIT license.

  • source
  • hideshow 1 child comment
  • [–] 13 points 1 year ago

    no license is safe, they have fuck you money and will win every time, but especially don't use MIT

  • source
  • 2 comments in c/freesoftware@lemmy.zip view that post
    [–] 5 points 1 year ago* (1 child)

    Wouldn't a stronger license than MIT prevent this?

    I understand that MIT doesn't allow for misattribution of work, but I feel like its inherent permissiveness makes that step not feel like much of a reach.

    Also, maybe I'm too petty, but I would have absolutely named and shamed the specific MS engineers involved with this mess, and I'd be looking to get in touch with their immediate manager. Can't help but imagine that it would be a career limiting move for the engineer that pretended to be all buddy buddy. Good luck passing off my work for your own promotion, asshole. Especially when you failed to cover your tracks this dramatically.

  • source
  • hideshow 1 child comment
  • 2 comments in c/technologie@jlai.lu view that post
    [–] 2 points 1 year ago

    Microsoft quoi

  • source
  • [–] 2 points 1 year ago

    C'est pas la première et ce sera pas la dernière fois non plus

  • source
  • 1 comment in c/linux@sopuli.xyz view that post
    [–] 3 points 1 year ago

    Uses MIT license, complains that it does not offer the GPL protections...

    Well...

  • source
  • 1 comment in c/linux@sh.itjust.works view that post
    [–] 4 points 1 year ago

    Microsoft can't be trusted

  • source