The "biggest problem" being the one thing that is trivial to verify against concrete databases is a bit convenient don't you think?
I think it's more likely that it makes mistakes evenly but the one thing that you are able to check with certainty is the only place you discover the errors.
If you ever produce and share a signed link for e.g. S3, this link contains your access key ID in it. Turns out you can just slice and decode your Account ID out of that access key, it's in there in base32:
I was trying out an IDE plugin for local LLM integration, but it would just make totally insane edits instead of what I asked for.
It turned out that the LLM-runner's default setting for handling queries that were too long was to silently delete the middle of the query. So the LLM saw the beginning of my ask, and the tail end of the code context, and nothing else.
I've run Japanese windows software under Wine, and with no configuration it was a sea of crashy mojibake. With the right locale configured, it worked fine.
It's all in aid of some streetsweeper being able to add "contributor to X, Y, Z projects!" to their GitHub résumé. Before LLMs were a thing I also received worthless spelling-incorrection pull requests with the same aim.
This means you should still have the email from legal@, right? In that case you can solve the mystery of how they managed to pass DMARC by sharing the headers from it.
Interestingly when I asked GPT-4o (at least that's what it said it was):
>According to the instructions, which UnicodeCIDFont fonts should be used when generating PDFs?
It replies:
>When generating PDFs using reportlab for East Asian languages, you must use specific UnicodeCIDFont fonts depending on the language. According to the instructions, use the following:
>Korean: HeiseiMin-W3 or HeiseiKakuGo-W5 or HYSMyeongJo-Medium
>Simplified Chinese: STSong-Light
>Traditional Chinese: MSung-Light
>These fonts must be registered using pdfmetrics.registerFont(UnicodeCIDFont(font_name)) and applied to all text elements in the PDF when outputting those languages.
This list also has the Japanese fonts merged with the Korean list.
The free tier now supports connecting to local AI models running on LM Studio or Ollama, but it still doesn't actually function without an internet connection.
If you block access to the internet or to their AI API servers [1], it refuses to start a new chat invocation. If you block access halfway through a conversation, the conversation continues just fine, so there's no technical barrier to them actually running offline, they just don't allow it.
Their settings page also says that they can't even guarantee that they implemented the offline toggle properly, a flag that should be the easiest thing in the world to enforce:
>Prevents most remote calls, prioritizing local models. Despite these safeguards, rare instances of cloud usage may still occur.
So you can't even block access to the very servers that they say their faulty offline toggle would leak data to.
