聊天记录
共 73 条，显示第 51-73 条
if you want the extra niceties that come with using more than just fills ws, you need to put in effort into doing heavy reconciliation (e.g. with rest). so to answer your originally question, no, you will end up with an approximation, but are fine 99.9% of the time
if you want the extra niceties that come with using more than just fills ws, you need to put in effort into doing heavy reconciliation (e.g. with rest). so to answer your originally question, no, you will end up with an approximation, but are fine 99.9% of the time
you can derive your entire order state (apart from whether order is canceled) purely from the fills websocket. this happens to contain `post_position_fp` which is your source of truth. if you start tacking on miscellaneous streams (positions ws, user order, wtv) then yes, you can start having drift (like if positions ws emits before a fill comes in)
you can derive your entire order state (apart from whether order is canceled) purely from the fills websocket. this happens to contain `post_position_fp` which is your source of truth. if you start tacking on miscellaneous streams (positions ws, user order, wtv) then yes, you can start having drift (like if positions ws emits before a fill comes in)
but this answer is misleading
but this answer is misleading
per year
per year
it’s $10k
it’s $10k
i checked what was being queried by the website itself
i checked what was being queried by the website itself
maybe had the wrong id
maybe had the wrong id
my existing auth flow didn’t work when i tried and i gave up. i am likely doing incorrectly
my existing auth flow didn’t work when i tried and i gave up. i am likely doing incorrectly
has the desire to remove pnl fields from positions ws been purged or is that still on the chopping block?
has the desire to remove pnl fields from positions ws been purged or is that still on the chopping block?
keep the functionality 🙂
keep the functionality 🙂
and for single order batch use? why is indexing into one item not functionally equivalent to the regular endpoint server side
and for single order batch use? why is indexing into one item not functionally equivalent to the regular endpoint server side
why?
why?
idk why the “regular” endpoints even need to exist. just support 1 or multiple and internally route that whichever way
idk why the “regular” endpoints even need to exist. just support 1 or multiple and internally route that whichever way
sometimes i cancel multiple sometimes i cancel one. i can hit the same endpoint for both use cases
sometimes i cancel multiple sometimes i cancel one. i can hit the same endpoint for both use cases
i’m not in the know
i’m not in the know
lmao what i was about to pay $10k for this
lmao what i was about to pay $10k for this
seeing elevated user data timestamp lag rn
seeing elevated user data timestamp lag rn
concerning, i need to check
concerning, i need to check
more for the rest of us 🙂
more for the rest of us 🙂
apex's statement is true. maybe not for live events, but before they start, you can achieve
apex's statement is true. maybe not for live events, but before they start, you can achieve
need like a 24h warning email or something
need like a 24h warning email or something
yoooo i’m getting demoted
yoooo i’m getting demoted
perpetual futures tho!
perpetual futures tho!
Kalshi