Roman Iakovlev

@ben-manes right, I've been thinking about implementing some sort of lazy loading as well. I'm not sure what's the best way to implement this, but I think it might be...

Thanks @rmathar for chiming in. Indeed the timezone designations in the oceans are somewhat confusing, and [many](https://github.com/evansiroky/timezone-boundary-builder/issues/100) [have](https://github.com/evansiroky/timezone-boundary-builder/issues/45) [tripped](https://github.com/evansiroky/timezone-boundary-builder/issues/38) [in the past](https://github.com/RomanIakovlev/timeshape/issues/4#issuecomment-406242101). Here's the authoritative quote on the topic: https://github.com/eggert/tz/blob/main/etcetera#L36-L51....

Closing due to lack of activity.

Closing as fixed, since the latest version of Timeshape (2022f.15 as of writing) uses a version of zstd without the mentioned vulnerability.

Closing due to lack of activity. I don't want to preclude any work on improving the performance of Timeshape, but I don't have a throughput to work on it (and...

This issue is quite old, and Timeshape now uses a later version of zstd-jni. I'm going to close this for now, if it still doesn't work, please open a new...

Closing due to lack of activity. If there's still interest in working on this, anyone should feel free to pick up this work, and I'll provide support with code reviews...

Closing due to lack of activity.

Closing based on lack of activity. Etc/* timezones are somewhat confusing indeed, but the Timeshape works correctly.

Closing based on lack of activity. Hopefully the instructions in readme now provide a clear path to run Timeshape on Android.