Developer who cares about aesthetics. @finanzfluss

Joined September 2020
46 Photos and videos
To celebrate @nitrojsdev v3 beta, nitro-test-utils v1 is here. Testing your server routes should be just as fast as building them. 🧪 Vitest 4 full config control 🍪 Shared cookies across requests 🔁 Source changes auto-rerun your tests 📦 Zero config
3
9
111
7,240
Johann Schopplich retweeted
AI eliminated the natural barrier to entry that let OSS projects trust by default. People told me to do something rather than just complain. So I did. Introducing Vouch: explicit trust management for open source. Trusted people vouch for others. github.com/mitchellh/vouch The idea is simple: Unvouched users can't contribute to your projects. Very bad users can be explicitly "denounced", effectively blocked. Users are vouched or denounced by contributors via GitHub issue or discussion comments or via the CLI. Integration into GitHub is as simple as adopting the published GitHub actions. Done. Additionally, the system itself is generic to forges and not tied to GitHub in any way. Who and how someone is vouched or denounced is up to the project. I'm not the value police for the world. Decide for yourself what works for your project and your community. All of the data is stored in a single flat text file in your own repository that can be easily parsed by standard POSIX tools or mainstream languages with zero dependencies. My hope is that eventually projects can form a web of trust so that projects with shared values can share their vouch lists with each other (automatically) so vouching or denouncing a person in one project has ripple effects through to other projects. The idea is based on the already successful system used by @badlogicgames in Pi. Thank you Mario. Ghostty will be integrating this imminently.
223
355
3,934
592,945
Johann Schopplich retweeted
30 Dec 2025
I built an iOS shortcut inspired by @waitbutwhy’s life calendar: your entire life as a finite grid of weeks on your lock screen. Since apps can’t update the lock screen, a shortcut runs weekly, fetches the next image from an endpoint, and updates the lock screen automatically.
157
123
3,972
397,999
🧮 New docs page: “TOON vs JSON: Byte-Level Efficiency Model” A simple byte math framework for why TOON is smaller in some structures – and why compact JSON can win in others. Huge thanks to @lafalcemateo for contributing it! toonformat.dev/reference/eff…
3
4
14
832
Loved doing this interview – thanks for having me!
3 Dec 2025
Longer queries means incurring higher token costs. But there’s more to building good AI applications than pinching pennies on tokens. TOON (Token-Oriented Object Notation) creator @jschopplich explains: heavybit.com/library/article…
2
5
689
It's wild to see how much debate and controversy a text format can spark. I learn by building, and TOON is just an experiment. If it turns out to be useful, people will adopt it. If not, it'll quietly fade away. That's the power of open source.
5
25
2,001
Commissioned artwork by @szkx_art 💛
3
329
Johann Schopplich retweeted
18 Nov 2025
Crazy how much more informed you can be by just reading the README file on the repo. Armin is wrong here, the training data doesn't matter. TOON makes most models more accurate for lookup.
AI discourse on Twitter is frustrating. Take this tweet with thousands of views. It claims you should use TOON instead of JSON. But if you actually count tokens, the savings are … barely existing, it's not in the training data, and tabular JSON beats it. x.com/DataChaz/status/198905…
76
19
647
145,509
This is exactly the type of use case TOON was designed for – thx for sharing, Jake! Interesting to hear about the drops in token usage and latency with Nova Micro, especially since the model struggled with CSV/XML for your payloads.
15 Nov 2025
Yes I did. I’m using it in production w/ Amazon Nova Micro and it is performing better. We serve a ridiculous amount of ecomm traffic daily and have observed a clear drop in token usage and a decrease in ttfb from bedrock. The model did not perform well with CSVs or XML and did not even handle large compressed JSON well. For this model it is a win across the board
13
1,179
Instead of posting another TOON rant that doesn’t even cover the full JSON data model, why not help improve the spec? 🙂 github.com/toon-format/spec
BREAKTHROUGH: I have invented a novel object notation format that provides an additional 71% token savings over JSON and 59% over TOON. I have named it VSC (Values Separated by Comma), patent pending.
18
4
85
36,402
Just improved the TOON docs based on community feedback: 💡 "When not to use TOON” section 🍎 Two benchmarks tracks for apples-to-apples comparison: mixed (vs JSON/YAML/XML) and flat (incl. CSV) TOON is an idea in progress. Contributions and feedback always welcome!
3
2
30
2,072

1
422
JSON isn't dead, and TOON isn't trying to kill it! Context matters. Just updated the README with a clearer picture (literally – new ASCII art). → TOON: ~1/2 smaller, great for uniform tables → JSON: better for varied fields/complex trees Use the right tool for the job. 🤾
3
2
41
2,127
Also, new logo by @szkx_art – thanks a ton!
2
3
424
🪂 TOON just got its own home under the "toon-format" GitHub organization! 🛠️ The new @​toon-format/spec repo ships with language-agnostic test fixtures for encode/decode conformance. Validate your implementation with the official test suite: github.com/toon-format/spec
3
5
36
2,183
Next up: Assembling the team for the first official TOON implementation (Python). Rust and Go will follow!
1
1
352
⌨️ @​toon-format/cli just dropped! JSON ↔ TOON conversion from your terminal. 🦛 Auto-detects encode/decode 💸 Shows token savings PS: @​byjohann/toon is deprecated → use @​toon-format/toon (library) & @​toon-format/cli Docs: github.com/johannschopplich/…
6
10
180
9,411
TOON now has a proper `decode()` method! 🏈 Auto-detects delimiters (comma/tab/pipe) 🌵 Validates input strictly by default (array length mismatches, delimiter inconsistencies, etc.) Strict parsing can be turned off at any time. Docs: github.com/johannschopplich/…
12
7
160
8,069