You are going to revolutionize my life. I was trying to think of cool things to build for my tablet as well as now aiming for specific quirks of certain models is no longer an obstacle and their older custom android forks.

I'll be sending architecture diagrams to my agent, I draw those much faster than I talk. I hope there's a good way to get alerted for agent waiting for your turn. Hmm I wonder if the Claude Code app will install on my Boox. I've been finding it fun to run Claude on weird things, if it runs linux there's a good chance. My favorite install was into my Steamdeck to debug some button sensitivity issues.

Yes that is exactly what's happening.

Claude keeps track of memory if you've turned that on so all conversations are somehow tracked over time Claude randomly will mention that I'm a developer while I'm asking unrelated questions and say oh because you're a developer you might like this or because of my background and infrastructure you might find this interesting and I always get creeped out by it.

They have the concept of incognito chats, but I can see those being worse without context from other conversations happening.

They don't even let you really run those yourself now either, We moved off a big GHE footprint because the support for it was getting abysmal and features were slowly become GH.com. Ive been dreading the move to GitHub.com and it was worse than I expected.

So how's forgejo been going for you?

Coder uses terraform providers to do the provisioning. I think that's the correct layer of abstraction, all major providers will be there and can be customized with the modifications needed via various other terraform features.

I've written three different solutions for platforms that solve this standard protocol layer. What has worked for us was deciding to standardize on the Kubernetes API for our services back in 2017, and then from then on, all our providers have provided either a k8s API to interact with resources, or provide a Cluster API for provisioning. For example we have two datacenter VM providers that implement the k8s API and we've been able to swap the providers with no user refactoring, it's a good solution in hindsight with how many people have k8s in their stack.

For the second big feature you're thinking of, we never really go a good solution to this problem, a lot of our workloads are long lived and not necessarily spot instance-able, but it's a very fun routing problem. Most of our need to be in multiple clouds is that we want to heavily separate our customer facing services, and keeping it away from internal workloads that support those customer APIs.

Is this public work? I'd love to take a look. This is my bread and butter.

Yeah using terraform providers is a great idea and something I have considered and aim to support. The thing I'm building also aims to handle things like payments and identity, not directly but with a plug/play facilitator model - so different providers/users can support/use different payment methods, crypto, decentralized identity, etc. That part kind of sits outside the resource provisioning part, and the resource provisioning part could in theory be terraform providers (after identity/payments is established). Resource discovery and search including - specs, pricing, region, capabilities, etc. I envision this protocol being used to build both centralized and decentralized compute/cloud resource marketplaces. In the decentralized view - regular users sharing/renting their hardware/resources with each other... lots of security/abuse risks/questions there.

I will be publicly releasing everything ~soon (I hope), it's in a pretty early stage at this point, many open questions.

I've noticed a few self identify and other random occupations, cool to see those fields checking out this tech at a deeper surface level.

I'm just a dev, but I appreciate the insights from other professionals.

You should have seen some of the Flash sites people made in the mid 90s early aughts. They all seemed to be straight up screenshots of the desired website and then buttons stapled on random portions.

They were an accessibility nightmare, but you use what you got. I tried so hard as a kid to understand flash, but had to settle on MS Frontpage to publish my first RPG page.

What's old is new again.

That they should be able to find distillation 'attacks' if they had enough observability.

That's not @throwa356262's argument.

@throwa356262 argument is that it is infeasible to distill and release a new frontier model in two weeks.

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.

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.