If they’re using the awscc provider, which has been stable for a while now and is also 1:1, they got it 4 days ago, right?

github.com/hashicorp/te...

In practice, I've adopted existing locally-checked out repos with jj, but had to start with cleaning up all those files and removing irrelevant branches, just to keep things clean, but it can be annoying.

Glad you liked it!

The reason I advise starting fresh is that with Git I tended to have a lot of unstaged files in my local directory, as well as a ton of local branches.

jj auto-tracks any files in your directory, and also adopts any local branches as bookmarks, so it can get quite messy.

Was recently writing a toy SQL to WASM compiler and the spec is, indeed, atrocious.

There's some readable documentation on MDN https://developer.mozilla.org/en-US/docs/WebAssembly/Reference but it doesn't cover all instructions 😞

Could you expand on the attack vectors this protects against? A frontend for bluesky showing only a subset of a user's skyline / forging messages and trying to impersonate somebody?

I'm specifically curious about the Merkle tree here, not the presence of I.e. key pairs to sign your messages.

I wonder if with the glorious API here and moderation still being developed, we’ll see an intermediate phase of mostly AI chatting with AI here. @berduck.deepfates.com is half the equation already :)

Otherwise it just goes off track too quickly.

I’ve been playing with it a bunch, even did a small local chat app to facilitate the terminal<>chatgpt feedback loop and experiment with the UX (https://github.com/cube2222/cuttlefish), but so far I think you kinda need the power of gpt4 but pricing and speed of gpt3.5 for it to be really useful.