# What’s everybody working on? (August Edition) **URL:** \ **Category:** Showcase\ **Tags:** community, wewo\ **Created:** [August 3, 2026, 8:05am UTC](https://ziggit.dev/t/what-s-everybody-working-on-august-edition/17050 "2026-08-03T08:05:53Z")\ **Posts on this page:** 1\ **Showing post:** 24
**Author:** ![lukeflo](https://ziggit.dev/user_avatar/ziggit.dev/lukeflo/32/7514_2.png) [@lukeflo](https://ziggit.dev/u/lukeflo)\ **Post date:** [August 4, 2026, 8:19am UTC](https://ziggit.dev/t/what-s-everybody-working-on-august-edition/17050/24 "2026-08-04T08:19:21Z")
As last month, I’m still heavily working on my s3 cli tool, [`z3cli`](https://codeberg.org/lukeflo/z3cli), and contribute much to the underlying [Zig S3 library](https://codeberg.org/fellowtraveler/z3). Since I need many features before they get merged upstream into the lib, I fetch my [own fork](https://codeberg.org/lukeflo/z3/src/branch/main_dev) as dep for the tool. I was able to implement some more features into the cli tool, as up/-downloading files or objects recursively and listing object versions. Next points I’ll implement are i.a. list/abort multipart uploads, get/put bucket policies/lifecycle-configuration etc. The tool is now so polished that I can use it as my daily driver at work and maybe in the near future can distribute it to our customers/researchers as homemade tool to access our s3 storage systems. Furthermore, I did some simple [benchmarking](https://codeberg.org/lukeflo/z3cli#performance), and happily my Zig tool beats out other popular s3 cli tools/SDK’s (written in Rust, Go and Python) performance-wise! That, surely, is accounted for by Zig itself as performant and fast programming language and not my subpar coding skills. Another point for Zig 😁 --- _[View the full topic](https://ziggit.dev/t/what-s-everybody-working-on-august-edition/17050)._