Casey Marshall

If we make the extension purely contextual and remove `target:` -- so that it applies to its parent element -- is it expressive enough to allow for including content that...

One thing we should also make clear is when to use this extension, vs. existing features in OpenAPI. In some cases, a `description:` might be enough. This should be used...

This can be a linting rule; only allow use of the extension if a non-empty description is provided.

I think this can be done in a single extension on the operation, `x-snyk-deprecated-on`, which takes a date of the form `YYYY-mm-dd`. Adding `x-snyk-deprecated-on` to an operation should cause requests...

Related: * https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#referenceObject * Discussion about it in https://github.com/OAI/OpenAPI-Specification/issues/1514

A better alternative to consider is requiring sub-typed links to be used in resources, which would then have actually-relevant examples. Then we don't need a custom extension.

Thanks for raising this, as I think it will be important to clearly communicate the impact of the changes we introduce here (whichever way we decide). AFAICT `snyk container monitor...

Currently, yes. The index stores a 256-bit digest for each piece, which in the latest release & main branch, is hard coded to 1MB. Veilid has an upper limit on...

I'd like to keep this open if you don't mind. Closing it to me means having a way to seed arbitrarily large files, and some guidance in the README. stigmerge...

With #266 comes the possibility of a configurable piece size -- the protocol will now support it.