Aaron D Goldman

Python uses a `=` for optional argument and requires the non-default arguments at the end. ```python >>> f = lambda a=1, b: a+b SyntaxError: non-default argument follows default argument ```...

I feel like this is just a special case of the scope within expressions. Whether it is a tuple, a struct, or a args what do we want the comma...

I think you are combining two distinct ideas. The handles are not the same as the DIDs. `@alice.com` is a Handle `did:plc:7iza6de2dwap2sbkpav7c6c6` is a DID When you do a search...

This may end up replaced with CBOR Object Signing and Encryption (COSE) https://datatracker.ietf.org/doc/html/rfc8152 If it looks like the IPFS ecosystem is standardizing on JOSE/COSE for object signing.

``` const documentData = z.object({ did: z.string(), signingKey: z.string(), recoveryKey: z.string(), username: z.string(), atpPds: z.string(), }) ``` One could certainly imagine adding a ``` plcKey: z.string(), ``` To the DID...

Not intended as allowing any other hash algorithm or prefix length just providing future proofing if it is needed. Adding options would still require a spec update just not ambiguity.

https://github.com/bluesky-social/atproto/blob/main/packages/common/src/tid.ts TID ``` 1 53 10 - ----------------------------------------------------- ---------- |0| μs since epoch | clock id | - ----------------------------------------------------- ---------- ``` The JavaScript run time gives milliseconds not microseconds. So...

For some reason I was expecting ``` https://${handle}/.well-known/_atproto -> did=${did} ``` To match the DNS form as closely as possible 🤷‍♂️

I agree with @pfrazee. If am coming in with an existing DID then the PDS should ask for the latest commit. The first commit at the new PDS should point...

> What exactly is context and blockNumber? I'd like to see a spec before we merge this. moving to draft PR until we merge the update to the CIP