Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Moonshot AI suspends new subscriptions due to Kimi K3 demand

twitter.com

Post reply on HN
Print view View original

71–80 of 118 posts

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#71

Post by kasey_junk »

kamranjon wrote: post #52
thevinter wrote: post #15

Personal anecdote: I exhausted my Claude usage yesterday so I decided to spend 20$ to try Kimi while I was at it. Logged in, paid, downloaded Kimi Code, set it to use K3 and prompted something along the lines of: "Check this repository and find all the settings that can be passed as input related to hardware, I/O, thread control or networking. Produce a report". It thought for about 12 minutes and then told me I had…

So I am likely coming from a completely different world because I use entirely self hosted models - but is it really common in your workflows to just wait for 12 minutes without any feedback? I am constantly watching my model and following the path it’s taking and cutting it off or steering it if it’s headed down a dead path. I was just curious if this is really common to just have no feedback for 12 minutes?

I have workflows that run for 8-10 hours unattended regularly. This is on frontier models though.

But if I were to look in on them they’d be giving feedback during that time, but they wouldn’t need steering.

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#72

Post by brcmthrowaway »

kamranjon wrote: post #52
thevinter wrote: post #15

Personal anecdote: I exhausted my Claude usage yesterday so I decided to spend 20$ to try Kimi while I was at it. Logged in, paid, downloaded Kimi Code, set it to use K3 and prompted something along the lines of: "Check this repository and find all the settings that can be passed as input related to hardware, I/O, thread control or networking. Produce a report". It thought for about 12 minutes and then told me I had…

So I am likely coming from a completely different world because I use entirely self hosted models - but is it really common in your workflows to just wait for 12 minutes without any feedback? I am constantly watching my model and following the path it’s taking and cutting it off or steering it if it’s headed down a dead path. I was just curious if this is really common to just have no feedback for 12 minutes?

What local model?

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#73

Post by throw1234567891 »

thevinter wrote: post #15

Personal anecdote: I exhausted my Claude usage yesterday so I decided to spend 20$ to try Kimi while I was at it. Logged in, paid, downloaded Kimi Code, set it to use K3 and prompted something along the lines of: "Check this repository and find all the settings that can be passed as input related to hardware, I/O, thread control or networking. Produce a report". It thought for about 12 minutes and then told me I had…

What's the app? nodejs todo app with a "database back end" in a text file, or a 1m line spaghetti code COBOL app from 1971?

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#74

Post by throw1234567891 »

kasey_junk wrote: post #71
kamranjon wrote: post #52

Earlier quoted context omitted.

So I am likely coming from a completely different world because I use entirely self hosted models - but is it really common in your workflows to just wait for 12 minutes without any feedback? I am constantly watching my model and following the path it’s taking and cutting it off or steering it if it’s headed down a dead path. I was just curious if this is really common to just have no feedback for 12 minutes?

I have workflows that run for 8-10 hours unattended regularly. This is on frontier models though. But if I were to look in on them they’d be giving feedback during that time, but they wouldn’t need steering.

I have the same on local models.

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#76

Post by twobitshifter »

himata4113 wrote: post #7

I wonder if anthropic and openai will remain relevant simply due to the fact that they're the only ones that are able to handle this much demand for the forseeable future? My bet would be that companies would probably not be too happy with employee time being wasted on outages and other related issues when it already costs so much.

As an open weights model Kimi will quickly find hosts other than moonshot, so I don’t expect this to really cause any issues for open weights adoption.

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#77

Post by eru »

kasey_junk wrote: post #71
kamranjon wrote: post #52

Earlier quoted context omitted.

So I am likely coming from a completely different world because I use entirely self hosted models - but is it really common in your workflows to just wait for 12 minutes without any feedback? I am constantly watching my model and following the path it’s taking and cutting it off or steering it if it’s headed down a dead path. I was just curious if this is really common to just have no feedback for 12 minutes?

I have workflows that run for 8-10 hours unattended regularly. This is on frontier models though. But if I were to look in on them they’d be giving feedback during that time, but they wouldn’t need steering.

I assume a lot of these 8-10 hours are spend calling tools and getting feedback from that?

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#78

Post by eru »

impossiblefork wrote: post #33
michalsustr wrote: post #20

Earlier quoted context omitted.

I talked with Hochreiter about 1.5y ago they should go for it and properly scale xLSTM to LLMs, not just playing around with few B params for experiments. They felt like they are too late to the game to get investment and traction. So much for European ambitions I guess...

Yes, but how would it have been if the EU governments just piled on, subsidized whoever had reasonable qualifications who wanted to try, straight-up funded accelerator development so that the chips don't just become investment in US AI companies, straight up built the supercomputers for training, straight up offered access to groups that had previously had reasonable success in training some model. I don't think it w…

What's their track record for other state sponsored high tech work?

I remember a few high profile failures; but perhaps on average these things work out?

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#79

Post by pluralmonad »

JoshTriplett wrote: post #29
Razengan wrote: post #26

Earlier quoted context omitted.

> a company that prioritizes their current customers and focus on keeping them satisfied instead of just focusing on fast growth. I always hated how the "Login" button is smaller on every website than the "Sign Up" button.

> I always hated how the "Login" button is smaller on every website than the "Sign Up" button. I always assumed that was because it's the least common flow. Once you've signed up, you're logged in, so the only time you should ever need the "login" button is on a new computer, or after logging out to switch accounts, or if the service offers a "remember me" checkbox (don't do that) and doesn't check it by default ( de…

You sign up once and login an arbitrary number of times. Not sure how signing up is ever the more frequent path. I've signed up for things I use maybe at most twice throughout a lifetime. Logins I couldn't even begin to count.

Re: Moonshot AI suspends new subscriptions due to Kimi K3 demand

#80

Post by kasey_junk »

eru wrote: post #77
kasey_junk wrote: post #71

Earlier quoted context omitted.

I have workflows that run for 8-10 hours unattended regularly. This is on frontier models though. But if I were to look in on them they’d be giving feedback during that time, but they wouldn’t need steering.

I assume a lot of these 8-10 hours are spend calling tools and getting feedback from that?

Yeah absolutely. And from other context windows for agents.
Post reply on HN