Just to clarify further, I don't mean to imply this use case isn't valid:

> I think it's all about the text sizing and choice of curated data by zoom. For example, a really large image of data from zoom 4 at the effective resolution of zoom 8 without the corresponding increase in text size.

But these are really visual design decisions and having users adjust tile sizes in the tilelive-vector API to achieve this is the wrong knob to have people turning.

Also this specific case can now be achieved in TM2 using a very high scale factor and very small text sizes : )