I think my actual issue was that claude code was downloading a 30GB file and choking my network.
I think my actual issue was that claude code was downloading a 30GB file and choking my network.
该用户的聊天记录定位。
I think my actual issue was that claude code was downloading a 30GB file and choking my network.
I think my actual issue was that claude code was downloading a 30GB file and choking my network.
It's been in and out for me the past five minutes. As much as 10s delayed
It's been in and out for me the past five minutes. As much as 10s delayed
Anyone seeing big market data delays for WC right now??
Anyone seeing big market data delays for WC right now??
Or i could press "unsubscribe" on their email and it would unsubscribe me?
Or i could press "unsubscribe" on their email and it would unsubscribe me?
It's not just obnoxious, but also i believe illegal for you to keep sending them after i've unsubscribed
It's not just obnoxious, but also i believe illegal for you to keep sending them after i've unsubscribed
How do i unsubscribe from these stupid emails i get every time one of my bets wins? I've clicked "unsubscribe" three times.
How do i unsubscribe from these stupid emails i get every time one of my bets wins? I've clicked "unsubscribe" three times.
Did you do any more trades?
Did you do any more trades?
No, because you don't trigger a ping to every market maker on the playform
No, because you don't trigger a ping to every market maker on the playform
What harm are the responders causing? Maybe I just don't understand
What harm are the responders causing? Maybe I just don't understand
You're not listening though. If you allow spammers (the people who create garbage RFQs, not the people who respond to them), then all the makers (a) have to waste quotes responding to the garbage, and (b) won't get filled, because the creator doesn't have a valid order. He's just trying to fish for errors
You're not listening though. If you allow spammers (the people who create garbage RFQs, not the people who respond to them), then all the makers (a) have to waste quotes responding to the garbage, and (b) won't get filled, because the creator doesn't have a valid order. He's just trying to fish for errors
But one reason they have bad quote to fill ratios is because you let people spam requests for quotes
But one reason they have bad quote to fill ratios is because you let people spam requests for quotes
<@1294044400065839177> these are the types of guys to ban. Not those other people who were responding to RFQs.
<@1294044400065839177> these are the types of guys to ban. Not those other people who were responding to RFQs.
I am all for banning RFQ spammers, but it doesn't sound like these guys are RFQ spammers. These are liquidity providers.
I am all for banning RFQ spammers, but it doesn't sound like these guys are RFQ spammers. These are liquidity providers.
It's kind of a pain for me to have different rules for the same sport.
It's kind of a pain for me to have different rules for the same sport.
Anyone know if KXWC will be the syntax of World Cup series in the knockout stages? I assume so, but also would make my life easier if it weren't
Anyone know if KXWC will be the syntax of World Cup series in the knockout stages? I assume so, but also would make my life easier if it weren't
I think evidence that contradicts this is that it would be an extremely good idea to ban/limit RFQ spammers, and implementing good ideas isn't Kalshi's style.
I think evidence that contradicts this is that it would be an extremely good idea to ban/limit RFQ spammers, and implementing good ideas isn't Kalshi's style.
I don't think understanding their API represents any meaningful edge
I don't think understanding their API represents any meaningful edge
<@1294044400065839177> you STILL have yes/no syntax on the orderbook feed? I just yelled at Claude for doing more YES/NO stuff in my code, but I guess Claude was right. You ever plan to clean this FrankenAPI up?
<@1294044400065839177> you STILL have yes/no syntax on the orderbook feed? I just yelled at Claude for doing more YES/NO stuff in my code, but I guess Claude was right. You ever plan to clean this FrankenAPI up?
Because no work good
Because no work good
15-20 min
15-20 min
Can't wait for the future dystopia where Kalshi gets the game paused when they have outages
Can't wait for the future dystopia where Kalshi gets the game paused when they have outages
Or create a "FUBAR Mode" for your algo
Or create a "FUBAR Mode" for your algo
I am just IOCing for the rest of the day
I am just IOCing for the rest of the day
Kalshi's "9:00 ET" isn't the same as ours
Kalshi's "9:00 ET" isn't the same as ours
Not what i remember at the super bowl
Not what i remember at the super bowl
This outage maybe have saved me for once, i was going to lay into a trade that would not be going well
This outage maybe have saved me for once, i was going to lay into a trade that would not be going well
It's just like the YES/NO garbage... the inconsistent API... the lack of versioning... it's just one more thing the PMs over at Kalshi decide they think they know more than 100s of years of financial markets that preceded them.
It's just like the YES/NO garbage... the inconsistent API... the lack of versioning... it's just one more thing the PMs over at Kalshi decide they think they know more than 100s of years of financial markets that preceded them.
I don't make, so i don't care for my sake.
I don't make, so i don't care for my sake.
They will maybe get into the higher tier because the election was busy, then the next month, when there is not election, you'll take it away
They will maybe get into the higher tier because the election was busy, then the next month, when there is not election, you'll take it away
But now... now you want to concoct some way that kills specialist in certain subjects. Like say elections. There will never be a time when the person who needs the higher tier actually has it
But now... now you want to concoct some way that kills specialist in certain subjects. Like say elections. There will never be a time when the person who needs the higher tier actually has it
Obviously you should incentivize whales, but that's what volume tier discounts are for
Obviously you should incentivize whales, but that's what volume tier discounts are for
Well, the fundamental problem is that you keep creating structures around volume, which doesn't really make sense. You want to incentivize the market makers to provide competitive liquidity. It's not a market maker's fault if the markets you want them to provide liquidity in doest't have customers--and thus volume isn't being driven.
Well, the fundamental problem is that you keep creating structures around volume, which doesn't really make sense. You want to incentivize the market makers to provide competitive liquidity. It's not a market maker's fault if the markets you want them to provide liquidity in doest't have customers--and thus volume isn't being driven.
Does Jump/SIG pay you to concoct these schemes to kill their competitors, or do you think of it all on your own?
Does Jump/SIG pay you to concoct these schemes to kill their competitors, or do you think of it all on your own?
You did teach me about the std::expected feature. I will now be gutting 1000s of lines of my code base where i used a much less efficient in-house version.
You did teach me about the std::expected feature. I will now be gutting 1000s of lines of my code base where i used a much less efficient in-house version.
Is this your plan? I like it if so
Is this your plan? I like it if so
This whole thing is making me think the ideal migration strategy for you all should be making the depreciated feed worse and worse to make people switch. Keep dropping from 20 QPS, to 5, to 2... eventually to 1 QPM, and every time someone comes in to complain about throttling, send them to v2
This whole thing is making me think the ideal migration strategy for you all should be making the depreciated feed worse and worse to make people switch. Keep dropping from 20 QPS, to 5, to 2... eventually to 1 QPM, and every time someone comes in to complain about throttling, send them to v2