Padraic Shafer

All good :) A project this size is bound to have some corners to tidy up. On balance, `tiled` is a fantastic achievement that simplifies finding and accessing datasets.

I started trying to implement this with `--include` and `--exclude` options, similar to how they are used in [`rsync`](https://superuser.com/questions/1637887/how-to-use-rsync-include-and-exclude-to-capture-distributed-set-of-files). However, `typer` does not seem to support preserving the order of...

> Another workaround might use `@typer.Typer().callback()` to hijack the command line context and manually extract `--include` and `--exclude` options in the order they were specified. This seems pretty hacky though,...

For simplicity we could start with implementing only an "exclude" option. I imagine that most use cases involve exposing all files / objects in the container while hiding only a...

> One possible name for this proposed new structure family is `unstructured`. I think I like that better than my original suggestion, `opaque_bytes`. I'll add a few more into the...

> I think the current proposal to beat is … Agreed. I don’t have strong feelings re: `unknown` vs. `unspecified`. Maybe @prjemian and @dylanmcreynolds have a preference?

> [octet stream](https://www.iana.org/assignments/media-types/application/octet-stream#:~:text=The%20%22octet%2Dstream%22%20subtype,than%20for%20any%20automatic%20processing) ? > > > is used to indicate that a body contains arbitrary binary data That makes sense. Stream has its own baggage of expectations, but "application/octet-stream"...

> it's hard to argue against. OK, I stand corrected. 😆

It seems like we have a winner. Should we proceed with using `bytes`?

I'd be interested in drafting a PR for this, along with some follow up discussions. It would be great to have a companion for this. @jmaruland are you interested in...