A learning thermostat would apply, say one that uses historical records to predict changes in temperature and preemptively adjusts. And it would be low risk and unregulated in most cases. But attach to a self-heating crib or premature baby incubator and that would jump to high risk and you might have to prove it is safe.
Maybe you are right and it is still risky for sleeping adults. In any case, even high risk the standard that needs to be followed might be as simple as 'must have a physical cutoff at 30C'.
> strongly suggestive that they have been trained on copyrighted materials
Given that everything -- including this comment -- is copyrighted unless it is (1) old or (2) deliberately put into the public domain, this is almost certainly true.
Isn’t this comment in the public domain? I presume that’s what I’m doing when I’m posting on a forum. If somebody copied and pasted something I wrote on here could I in theory use copyright law to restrict distribution? I think the law would say I published it on a public forum and thus it is in the public domain.
Why would it be in the public domain? Anything you create, under US copyright law, is the opposite of being in the public domain, it's yours. According to the legalese of YC, you are granting YC and YC alone a license to use the UGC you submitted to their website, but if anything, the YC agreement DEMANDS that you own the copyright to the comment you are posting.
> User Content Transmitted Through the Site: With respect to the content or other materials you upload through the Site or share with other users or recipients (collectively, “User Content”), you represent and warrant that you own all right, title and interest in and to such User Content, including, without limitation, all copyrights and rights of publicity contained therein. By uploading any User Content you hereby grant and will grant Y Combinator and its affiliated companies a nonexclusive, worldwide, royalty free, fully paid up, transferable, sublicensable, perpetual, irrevocable license to copy, display, upload, perform, distribute, store, modify and otherwise use your User Content for any Y Combinator-related purpose in any form, medium or technology now known or later developed. However, please review the Privacy Policy located here for more information on how we treat information included in applications submitted to us.
> You acknowledge and agree that any questions, comments, suggestions, ideas, feedback or other information about the Site (“Submissions”) provided by you to Y Combinator are non-confidential and Y Combinator will be entitled to the unrestricted use and dissemination of these Submissions for any purpose, without acknowledgment or compensation to you.
Another example of this is people putting code, intended to be shared, up on e.g. Github without a licence.
Many people seem to think that no licence = public domain, but it's still under strong copyright protection. This is the point of things like the Unlicense license.
This is angels-on-pins level stuff, though. In normal English lax enforcement of a rule doesn't mean you're not required to obey it. It just means you're gambling that you won't be put under sufficient pressure to crack your resolve.
All EU countries have to publicly commit to joining the Euro and doing the work to do so. They are therefore required to join it, under any reasonable interpretation of the treaty language. The fact that some countries realized they could just not do what they agreed to and/or hack their economy to avoid the entry criteria, without any consequences, is good evidence that the treaties are indeed meaningless. But lax enforcement isn't the same as no requirement. The EU Commission could change their stance at any time.
It has been a while since I last looked at this, but from memory a pre-condition for Euro adoption is spending a certain amount of time within some formal "convergence mechanism", however there is no obligation to join that convergence mechanism.
I think you are required to join it, but proceeding to actual Euro rollout requires a currency to be within a certain range for a period of time, and that requires active intervention in currency markets. Governments can just either not do it or claim they can't intervene enough to stay on target.
The problem is most people think their app is super complex and requires some mad thing that's actually complicated when actually its a glorified crud.
The iPhone is 100x more complex and does 10x more than like 10 separate gadgets from the 90s, and yet is also easier to use and more efficient than them all, broadly.
Your CRUD app could be terrible in pure HTML and amazing in Svelte. Or vice versa. But a competent engineer will make a better version with the more modern tech.
Your OS GUI is an abstraction on an abstraction, it's UI kit is on top of that, the browser is on top of that, React on top of that...
People always draw the ideal line exactly at where they learned things / stopped learning things.
1 BC should be renamed year 0. Then the years 0-99 are the 0th century, the years 1900-1999 are the 19th century, etc.
To avoid confusion between new style and old style centuries, create a new word, "centan", meaning "100 years" and use cardinal instead of ordinal numbers, for conciseness. Then the years 1900-1999 are the 19-centan.
