It's a market in the same way that poker and blackjack are "markets" on which cards are most likely to appear. You don't need to redefine what gambling is.
Yeah I keep reading comments about "semiconductor boom/bust cycles", but they ignore that Moore/Dennard Laws were in a totally different regime back then, and they ignore the external factor of AI. So I just don't understand what those comments are alluding to.
There’s a very clear anti-building conspiracy in Canada. I can only think that someone must be limiting supply to keep prices high to protect profits.
Because my friend had the craziest protectionism story.
He wanted to build a multi family home on his existing lot.
Of course all kinds of studies need to be done. One of them is a tree study. Which costs $3,000 alone per tree. He hired firm and they were doing a study (for building purposes).
Then one day a crew shows up and cuts the tree all of a sudden. Turns out that his neighbour, unknown to him, was complaining that the tree was creating too much shade. So without any study they just came and cut it down.
You can build a model accounting for all the things you like, you don't have to limit yourself to Elo (its main selling point is that it's easy enough that players can easily calculate how many rating points they stand to lose/gain) or Glicko (almost as easy).
Even in the most optimistic case, betting market accuracy will be limited by the commission (if you have a better estimate than the market, but not sufficiently better that you'll make money on it, you don't bet), and I think even a not-terribly-smart model can get you there for chess games. We don't need betting markets for the prediction's sake.
The way the problem was solved at first hand by just "recognizing the pattern of (2n) choose n" wouldn't satisfy me at all, where's the proof ? Why does it work ? This isn't maths, this is "pattern recognition".
Elastic/Opensearch uses GET requests with a body for search, which is complicated or forbidden (not exactly sure) with the HTTP spec. Not all HTTP clients are willing to submit a body with a GET.
So opensearch also allows you to POST search requests, but those are uncacheable
QUERY would fit here perfectly - it's probably trivial for opensearch to add but it will take some time for clients to catch up.
I get a lot done with something that's also approximately 6 tokens/second, if you're willing to give it a well defined set of prompts and projects to work on, leave it for an hour or two, then come back and check what it's done. And often to remember to give it something of more consequence to do for at least 3-4 hours of wall clock runtime before heading to bed.
One of our government agencies has expert panels where people from the field and in different lecels of administration get consulted in group about legislativ or procedural issues.They call it round tables and they get organised about three times a year on different fields of expertise.
After these round tables the reports go to the cabinets and eventually the refined versions will be presented before the MP. They make new legislation bases on a structural review of procedures and law and that is how a government could operate without hiring expensive experts. You already have the experts on board, let them participate.
> using HTTP GET with a request body is a bad idea, as for example users behind a corporate firewall or a different browser may be unable to use your website.
So is using QUERY requests for quite some time from now.
Good, but the number of internet stinks about this particular cultural appropriation I have encountered so far is zero. But I have encountered multiple dramas from people offended on behalf of the people who never asked them to whiteknight for them.
