pbreit

HTTP client libraries on the various languages still seems so lousy with excessive boilerplate and all sorts of complexity to handle cases that are beyond rare.

What would be a good tool to train on a "knowledge base" (a set of URLs) to be used to field customer support inquiries?

Is there by chance a CRUD boilerplate/starter (_NOT_ a to-do app)?

Or perhaps writing pro rata checks doesn't require that many people?

Most of the regional bank stocks have been halted: https://twitter.com/BrianRoemmele/status/1635279537885052928

What would be some examples of features that your service could add to my app?

The "new" web UI is positively awful. The messages list is unreadable.

Slower than JSON?

Arrow looks super complicated.

Are data types useful for data to/fro web/mobile clients? Encode type into the column header?

But in this case there is almost no difference. Basically same payloads with a slightly different "command" format.

Is it though? Or is the difference mostly semantics? At then end of the day it's just barely different ways for issuing a "command".

What is the difference between RPC and API besides the URL & payload structure?

I was just thinking how lousy a data format JSON is for tabular data. Would sending it down in CSV improve things at all?

It's interesting that JSON is still the format of choice for transmitting tabular data to SPAs and mobile apps. Granted, it's likely compressed. But still seems something more efficient like CSV would be better.

Besides XML, JSON is about the worst way to format tabular data, right?

Does it mostly just mean that, for non-JWT-style tokens, the same string essentially serves as both a "username" and a "password"?

Was there anything inherently bad about the SPAC approach or did it mostly just attract lousy users?

I can't even think of another provider. And Gmail is otherwise quite amazing.

That doesn't seem very compelling. And these aren't even JWT-style tokens which would make it a bit more understandable.

API keys have been around for a long time without needing the prefix. I could understand the Bearer prefix when using JWT-style tokens. I could also see using it if there were indeed an Oauth flow involved. But in this case just seems like a nuisance.

FIXED: needs to be a POST. Doh!

Can anyone get it to work? I get this error on everything I've tried:

  GET /v1/completions HTTP/1.1
  Host: api.openai.com
  Authorization: Bearer sk-xxx
  Content-Type: application/json
  Content-Length: 115

   {
    "temperature" : 0.5,
    "model" : "text-davinci-003",
    "prompt" : "just a test",
    "max_tokens" : 7
   }


  {
    "error": {
        "message": "you must provide a model parameter",
        "type": "invalid_request_error",
        "param": null,
        "code": null
    }
  }

Could explain what the point of "Bearer" is in this authorization header?

"Authorization: Bearer $OPENAI_API_KEY"

Are there any modern open source NNTP/USENET servers?

If not django, what on python? Anything else besides flask?

I'm confused. Rockefeller now gets credit for Carngeie, Mellon and Ford? Spacex, the by far most prolific private space company ever is a "tiny space company"? The by far most consequential EV company is a "shoddy carriage company"? And not even mentioning Zip2, PayPal, OpenAI, Boring or Neuralink? Wow.

Why are the email providers so bad about this? When I check my "spam" filder in Gmail, around half the email is not spam. Is it because humans are so bad at classifying spam?

Or much easier if codebases start looking 90% more familiar.

Care to name one or 2?

How so? I consider multiple creations substantially more impressive than one.

One oil company?