logoalt Hacker News

kami23yesterday at 11:36 PM1 replyview on HN

Ah I interpreted it as 'of course they can't stop distillation if they couldn't stop a model from escaping its sandbox'

I can see how there's a big leap there, but I agree somewhat. If they are aware these are happening and can detect it as it is happening why are they not stopping them? What do you do there? It'll be cat and mouse for a while. Thinking of reasons they wouldn't try and stop it is just a lot of speculation in my brain.

It's probably a way harder problem than I think it is, but they are aware of them now, so I assume they are going to get more aggressive about it.

Let's say then that they can't detect them near real time or even a bit after, maybe they do have a big observabilty gap that no one has solved adequately.

The speed which they add features I've needed for governance is pretty close to the speed I 'manually' write those for my company. To me personally we are all just going fast and breaking everything and not having enough time to set up safe environments. I'm sure it's in the backlog.


Replies

moralestapiatoday at 12:08 AM

Hmm ... so the gist of the issue is this.

Training and releasing a model like Kimi K3 takes months-to-a-year (and that's if you're really good at it).

'months-to-a-year' ago there was no Fable, so there was no way for them to distill them.