294 karma · joined November 30, 2019
From https://openai.com/our-structure
- First, the for-profit subsidiary is fully controlled by the OpenAI Nonprofit. We enacted this by having the Nonprofit wholly own and control a manager entity (OpenAI GP LLC) that has the power to control and govern the for-profit subsidiary.
-Second, because the board is still the board of a Nonprofit, each director must perform their fiduciary duties in furtherance of its mission—safe AGI that is broadly beneficial. While the for-profit subsidiary is permitted to make and distribute profit, it is subject to this mission. The Nonprofit’s principal beneficiary is humanity, not OpenAI investors.
-Third, the board remains majority independent. Independent directors do not hold equity in OpenAI. Even OpenAI’s CEO, Sam Altman, does not hold equity directly. His only interest is indirectly through a Y Combinator investment fund that made a small investment in OpenAI before he was full-time.
-Fourth, profit allocated to investors and employees, including Microsoft, is capped. All residual value created above and beyond the cap will be returned to the Nonprofit for the benefit of humanity.
-Fifth, the board determines when we've attained AGI. Again, by AGI we mean a highly autonomous system that outperforms humans at most economically valuable work. Such a system is excluded from IP licenses and other commercial terms with Microsoft, which only apply to pre-AGI technology.
Edit on initial reply: “Keto gets its benefit from avoiding low simple carbs , not from avoiding complex carbs or consuming high saturated fats.“
hmmm...
Package managers have been arguably the single biggest reason that I've gravitated back toward Linux and have exclusively used it for developing that past 10 years. Rolling your own installation script doesn't on its face look like a good strategy for adoption.
Hello, Q. What is happening? A. We are ending support for Node.js 10 in AWS Lambda on July 30, 2021. This follows the Node.js language governing body declaring Node.js 10 end of life as of April 30, 2021 [1].
Q. What does end of support for Node.js 10 in Lambda mean? A: As described in the Lambda runtime support policy [2], end of support for language runtimes in Lambda happens in two stages. Starting July 30, 2021, Lambda will no longer apply security patches and other updates to the Node.js 10 runtime used by Lambda functions, and functions using Node.js 10 will no longer be eligible for technical support. In addition, you will no longer be able to create new Lambda functions using the Node.js 10 runtime. Starting Aug 30, 2021, you will no longer be able to update existing functions using the Node.js 10 runtime.
End of support does not impact function execution. Your functions will continue to run. However, they will be running on an unsupported runtime which is no longer maintained or patched by the AWS Lambda team.
... Q. How do I know if I have any functions using Node.js 10? aws lambda list-functions --function-version ALL --output text --query "Functions[?Runtime=='nodejs10.x'].FunctionArn"
Q. What do I need to do? A. You should migrate your existing Node.js 10 Lambda functions to Node.js 14, which is the latest supported Node.js version in Lambda [4]. Node.js 14 is not yet supported by Lambda@Edge, so Lambda@Edge functions should be upgraded to Node.js 12. By moving to a supported runtime version you will continue to benefit from important ... enhancements offered by more recent releases.
Q. What if I need additional help? A. Please contact us through AWS Support [5], the AWS Lambda Developer Forum [6], or your AWS account team should you have any questions or concerns.
Sincerely, Amazon Web Services
Is this really a problem with capitalism or with human nature?