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

help-circle




  • It’s true you will never get rid of all of it but, just like crime, basic enforcement is a deterrence. They know who’s buying, they know where they’re shipped, they have a fair idea if they’re returned. Just requiring reviews to be from purchasers after they’ve received the product, removing positive reviews for returns without replacement (or flagging them as returned), and a few other steps would make fake reviews either very expensive or very expensive for the results.

    The fact is, Amazon makes most of their money on AWS, and I don’t think they care to put in the real effort to make their marketplace trustworthy again. Without that, it will continue its downward spiral.






  • It really depends. If the contract gives ownership of the work created to the purchaser, he has no rights to it whatsoever. Moreover, trying to do a clean room implementation of your own code is almost impossible without help. A permissive license would give the purchaser unlimited use of the product, including resale while still allowing the producer unlimited use, as well. If the contract is written correctly, the producer might even retain ownership, with the right to use different licenses, while the purchaser would have few or no restrictions.


  • I’ll throw my opinions in here.

    If you’re publishing a standard or a reference application, a permissive license makes sense. What better way to guarantee compatibility than being able to use the reference code in your product. This is what happened with the TCP/IP stack, and it was used in its original form in Windows for years.

    If you’re making something that you want to build a community around, something more akin to the GPL may be more aligned with your goals. The nice part is, you can include MIT licensed projects as part of your GPL project. This means there is nothing stopping you from building your standard with a MIT license while building your community-driven application using GPL, maximizing the reach of your standard while reducing the risk to your community.

    Note that either option opens you to EEE (Embrace, Extend, Extinguish), the GPL option just takes an extra step (clean room implementation of a published standard).