Skip to content

Latest commit

 

History

History
111 lines (70 loc) · 3.91 KB

File metadata and controls

111 lines (70 loc) · 3.91 KB

Comment Draft for Medium Article

Option 1: Technical & Enthusiastic

Hey Alexey! 🚀

This is BRILLIANT! We've been working on similar token-efficient formats for our narrative/game projects, and TOON hits all the right notes.

We just open-sourced our TOON parser/converter implementation: https://github.com/FutureVision-Labs/toon-parser

Real-world results we're seeing:

  • The Imaginatorium (narrative format): 45% token reduction
  • VIBE CHAT (chat logs): 38% token reduction
  • CML Quest (game content): 42% token reduction
  • Mini-Cursy (telemetry): 50% token reduction

The human readability is a game-changer - our content creators can edit TOON files directly without JSON syntax headaches. Plus the parsing speed boost is real!

Would love to collaborate on expanding the ecosystem. This format has serious potential! 💪


Option 2: Short & Punchy

Amazing work! 🎯

We built a TOON parser/converter and are seeing 30-60% token reduction across our projects. The readability improvement alone makes it worth it.

Open-sourced here: https://github.com/FutureVision-Labs/toon-parser

Real-world use cases:

  • Narrative/event storage (45% reduction)
  • Chat logs (38% reduction)
  • Game content (42% reduction)
  • Telemetry (50% reduction)

The format is perfect for AI workflows where token efficiency = cost savings. Excited to see where this goes! 🚀


Option 3: Detailed & Collaborative

Hi Alexey!

This is exactly what we needed! We've been experimenting with token-efficient formats for our AI-driven projects, and TOON solves so many problems we've been hitting.

We've open-sourced our implementation: https://github.com/FutureVision-Labs/toon-parser

Our real-world results:

  1. The Imaginatorium (narrative/event format) - 45% token reduction

    • Storing conversations, recipes, actions, discoveries
    • Much easier for content creators to edit manually
  2. VIBE CHAT (chat logs) - 38% token reduction

    • More efficient conversation storage
    • Faster chat log processing
  3. CML Quest (game content) - 42% token reduction

    • Episodes, rooms, NPCs, dialogs, scripts
    • Better authoring experience for game designers
  4. Mini-Cursy (telemetry) - 50% token reduction

    • Drive logs, incidents, songs, moods
    • Massive storage savings for high-frequency data

Key benefits we're seeing:

  • ✅ Human readability is incredible - non-programmers can edit TOON files directly
  • ✅ Parsing performance is noticeably faster
  • ✅ File sizes are significantly smaller
  • ✅ Perfect for AI/LLM workflows where token efficiency = cost savings

The indentation-based syntax is so much cleaner than JSON for nested structures. We're using it for everything from narrative storage to telemetry logging.

Would love to collaborate on expanding the TOON ecosystem! This format has serious potential. 🚀


Option 4: Casual & Friendly

Hey! 👋

This is SO cool! We've been building something similar for our projects and TOON is hitting all the right notes.

Just open-sourced our parser: https://github.com/FutureVision-Labs/toon-parser

We're seeing 30-60% token reduction across our projects:

  • Narrative storage: 45% reduction
  • Chat logs: 38% reduction
  • Game content: 42% reduction
  • Telemetry: 50% reduction

The human readability is a game-changer - our content creators love being able to edit TOON files directly without wrestling with JSON syntax.

Plus the parsing speed boost is real! Perfect for AI workflows where token efficiency = cost savings.

Excited to see where this goes! Would love to collaborate! 🚀💪


Recommendation

I'd go with Option 3 (Detailed & Collaborative) because:

  • Shows real-world usage and results
  • Demonstrates you've actually implemented and tested it
  • Provides specific metrics
  • Shows enthusiasm and willingness to collaborate
  • Professional but friendly tone

You can always shorten it if needed, but having the details shows you're serious about this!