In any case, the restriction makes it incompatible with pretty much all password generators, including the built-in ones in modern browsers. To improve matters, I would suggest dropping all restrictions on what cannot be included altogether.
I tried adding https://github.com/torvalds/linux and asking it to write a simple kernel module for me, but it gave me this error:
"Something went wrong, please try again later. If the problem persists, please contact us."
Edit: looks like it is, I see it's making a POST request to https://gptduck-production.up.railway.app/query which responds with a 500 Internal Server Error when I use a URL that looks like a GitHub repository (whether it actually exists or not), and "invalid repo" otherwise.
I thought ChatGPT could only process a very limited context (a few thousand words or so) and this claims to work for repositories <100 MB, which is gigantic in comparison.
The site says: "we will download [the repo] to the server and create embeddings against the code". What kind of embeddings are these?
Logging with GitHub is still lowish but like 1k per hour or so. (IIRC)
What makes this even worse, is that Yellen would have lost nothing had she said they would back every bank and not just large banks - small bank failures are just not that common, and the risk is low, (and can be walked back in two years when the tension lowers).
Even worse, well over half of the SVB bailout went to <20 accounts.
IMO, they should have raised the amount that FDIC is insuring, which is unquestionably too low. [They still should do that.] They then should have insured everyone equally up to that point. And if Circle and Roku would lose 90% of their value from such a move, that beats the whole banking system consolidating into one or two massive players that can act with impunity.
OK, I am not an economist, and admit that I probably don't know what I am talking about, but HN is full of smart people with domain knowledge. Please (gently) broaden my perspective.
Do you have a source for this?