该用户的聊天记录定位。
I dont bother using it but idrc about latency
I dont bother using it but idrc about latency
im not measuring anything
im not measuring anything
not sure if I even can measure that accurately
not sure if I even can measure that accurately
I havnt measured but probably somewhere between 20-30 ms
I havnt measured but probably somewhere between 20-30 ms
I specificially whitelisted it last night before these changes
I specificially whitelisted it last night before these changes
if u want
if u want
you can ignore it
you can ignore it
the error is non fatal
the error is non fatal
the url path is /markets/<series>/<event>
the url path is /markets/<series>/<event>
KXMLBGAME-26JUN161840MIAPHI-MIA → https://kalshi.com/markets/kxmlbgame/kxmlbgame-26jun161840miaphi
KXMLBGAME-26JUN161840MIAPHI-MIA → https://kalshi.com/markets/kxmlbgame/kxmlbgame-26jun161840miaphi
yes
yes
<@1511133985940705370> scam <@1413713829883543613>
<@1511133985940705370> scam <@1413713829883543613>
I think you should be able to rely on the actual exchange's UI as a source of truth
I think you should be able to rely on the actual exchange's UI as a source of truth
The argument that you should be expected to build your own UI is dumb
The argument that you should be expected to build your own UI is dumb
You can't take a day off in these markets
You can't take a day off in these markets
should I be concerned
should I be concerned
u cant search for them
u cant search for them
I think you can see top of book or something if its resting
I think you can see top of book or something if its resting
this does not look accurate afaik
this does not look accurate afaik
your skill issues are not their problem
your skill issues are not their problem
We dont need frivolous endpoints and fields
We dont need frivolous endpoints and fields
Kalshi needs to keep the api minimal so its as maintainable and performant as possible imo
Kalshi needs to keep the api minimal so its as maintainable and performant as possible imo
or field
or field
there doesn't need to be a seperate api call for your use case as I read it
there doesn't need to be a seperate api call for your use case as I read it
I am not sure what exactly are you asking for that you can't implement on your own side
I am not sure what exactly are you asking for that you can't implement on your own side
wdym you can just implement this yourself
wdym you can just implement this yourself
Please dont reply to copy pasted ai slop
Please dont reply to copy pasted ai slop
but maybe idk
but maybe idk
macro crypto is a psuedo science
macro crypto is a psuedo science
save time
save time
I would just test in prod with small amounts
I would just test in prod with small amounts
it has a lot of bugs and isnt maintained well
it has a lot of bugs and isnt maintained well
I wouldnt use their SDK
I wouldnt use their SDK
Looks like my work the past days is paying off my stuff running smooth
Looks like my work the past days is paying off my stuff running smooth
just insane how those things resolve
just insane how those things resolve
nah its prob fine
nah its prob fine
weather not even worth the rate limit
weather not even worth the rate limit
<@378727998121181184> nba game 5 going live get ready to take another quick vacation
<@378727998121181184> nba game 5 going live get ready to take another quick vacation
endpoint
endpoint
get portfolio
get portfolio
after 5 minutes
after 5 minutes
but it self resolved
but it self resolved
I am doing a lot of dev work today
I am doing a lot of dev work today
maybe I just broke something
maybe I just broke something
anybody see that
anybody see that
a second ago
a second ago
I got infinite 500 errors
I got infinite 500 errors
but idrc if its removed tbh
but idrc if its removed tbh
I also use the batch orders in ways I cant replicate with single orders
I also use the batch orders in ways I cant replicate with single orders
why is the socket closing
why is the socket closing