That page is about chat while the parent comment seems to be about completions, that's the codepilot feature most of us will be looking to replace/improve on.
In general I completely agree that code name overload is dreadful. But I think in this case, where this pair is so fundamental and used so frequently in the codebase, I think I would probably permit it. Beware codename creep.
I run and pub and brewery in the east of England that was established in 1991. We have lots of breweries around here and none of them seem to be on openbrewerydb. I have joined the Discord and will see if I can contribute some info.
This is genuinely something I hadn't considered. A test tenant may have been in a more than ideal position to stage phishing attacks from. Hopefully this is the case, and not a more concerning lack of disclosure or shudder NSL situation.
This seems similar to how Eloquent (Laravel's ORM) will, by default, make separate IN queries when you ask for a collection plus its relationships (instead of using a JOIN).
I have thought about how you might return normalised data to your front-end and, with support from a front-end library, rebuild the object relationships so you can access them naturally.
One place I got stuck with JSON:API is that support for updating a row and its relationships in a single API request seems to have been kicked around for a while and is unresolved:
https://github.com/json-api/json-api/issues/795
I don’t understand. Doesn’t your balance equal the sum of your transactions on your statement? I understand there is no outgoing transaction, but unless some “money in” lines were removed then how does it add up?
Requiring approval for the first couple of posts from new users is one of the most sensible anti-spam policies. I'd much rather see more of that than the current forced AI training labor favored by most sites.