# Zigtoberfest 2025 **URL:** \ **Category:** Meet\ **Tags:** events, event\ **Created:** [April 13, 2025, 9:02am UTC](https://ziggit.dev/t/zigtoberfest-2025/9598 "2025-04-13T09:02:25Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![r4gus](https://ziggit.dev/user_avatar/ziggit.dev/r4gus/32/5114_2.png) [@r4gus](https://ziggit.dev/u/r4gus)\ **Post date:** [April 13, 2025, 9:02am UTC](https://ziggit.dev/t/zigtoberfest-2025/9598/1 "2025-04-13T09:02:26Z")
For those who might be interested, Zigtoberfest is returning to Munich on the 25th of October 2025. For more info: [https://zigtoberfest.de](https://zigtoberfest.de) You can find the talks of Zigtoberfest 2024 on youtube: [https://m.youtube.com/@zigtoberfest/videos](https://m.youtube.com/@zigtoberfest/videos). The audio quality isn’t that good but I’ve already invested in better microphones. ---
**Author:** ![r4gus](https://ziggit.dev/user_avatar/ziggit.dev/r4gus/32/5114_2.png) [@r4gus](https://ziggit.dev/u/r4gus)\ **Post date:** [May 2, 2025, 11:13am UTC](https://ziggit.dev/t/zigtoberfest-2025/9598/2 "2025-05-02T11:13:58Z")
I’ve just published the agenda for this year: [Zigtoberfest](https://zigtoberfest.de/agenda2025/). ---
**Author:** ![tensorush](https://ziggit.dev/letter_avatar_proxy/v4/letter/t/6a8cbe/32.png) [@tensorush](https://ziggit.dev/u/tensorush)\ **Post date:** [October 25, 2025, 7:26am UTC](https://ziggit.dev/t/zigtoberfest-2025/9598/3 "2025-10-25T07:26:38Z")
Live in half an hour: [![](https://ziggit.dev/uploads/default/original/2X/3/3f4b851fd6d34f6ded7b7c67bc865281f835cde4.jpeg "Zigtoberfest 2025") ](https://www.youtube.com/watch?v=2PgjgTT27Os) ---
**Author:** ![yamafaktory](https://ziggit.dev/user_avatar/ziggit.dev/yamafaktory/32/7689_2.png) [@yamafaktory](https://ziggit.dev/u/yamafaktory)\ **Post date:** [October 26, 2025, 4:11pm UTC](https://ziggit.dev/t/zigtoberfest-2025/9598/4 "2025-10-26T16:11:16Z")
Are the examples from Andrew available somewhere? The talks were awesome and it’s a pleasure to see how fast Zig is evolving and bringing so much on the table. ---
**Author:** ![r4gus](https://ziggit.dev/user_avatar/ziggit.dev/r4gus/32/5114_2.png) [@r4gus](https://ziggit.dev/u/r4gus)\ **Post date:** [October 26, 2025, 5:30pm UTC](https://ziggit.dev/t/zigtoberfest-2025/9598/5 "2025-10-26T17:30:39Z")
I’m not sure but I think you’ll be able to try it out with the next release. ---
**Author:** ![r4gus](https://ziggit.dev/user_avatar/ziggit.dev/r4gus/32/5114_2.png) [@r4gus](https://ziggit.dev/u/r4gus)\ **Post date:** [October 26, 2025, 5:34pm UTC](https://ziggit.dev/t/zigtoberfest-2025/9598/6 "2025-10-26T17:34:52Z")
The talk [“Send all your private data to ChatGPT”](https://youtu.be/FUpEAMUQkCA) by Frank Denis has been published on YouTube. ## Abstract A couple of weeks ago, my cloud provider bill suddenly and unexpectedly went through the roof. To react quickly and figure out what was going on, I did what anyone would do in 2025: I sent the server logs to ChatGPT and asked it to analyze them and tell me what to do. Of course, these logs contained a ton of private information that should never be shared with third parties, but whatever. Just before that, I had already used an MCP server to get insights about another service, using private data as well. So I was probably already on my way to hell. Or maybe not. In this talk, I’ll introduce techniques for using untrusted third-party services to analyze private information without ending up burning in hell. ## About Frank I maintain a few things in Zig as [@jedisct1](https://github.com/jedisct1) on GitHub and in the [std.crypto namespace](https://github.com/ziglang/zig/tree/master/lib/std/crypto) of the Zig standard library. ---
**Author:** ![andrewrk](https://ziggit.dev/user_avatar/ziggit.dev/andrewrk/32/7011_2.png) [@andrewrk](https://ziggit.dev/u/andrewrk)\ **Post date:** [October 29, 2025, 8:10pm UTC](https://ziggit.dev/t/zigtoberfest-2025/9598/7 "2025-10-29T20:10:46Z")
> **[Zig's New Async I/O (Text Version) - Andrew Kelley](https://andrewkelley.me/post/zig-new-async-io-text-version.html)** ---
**Author:** ![gyozo](https://ziggit.dev/letter_avatar_proxy/v4/letter/g/97f17d/32.png) [@gyozo](https://ziggit.dev/u/gyozo)\ **Post date:** [October 29, 2025, 9:31pm UTC](https://ziggit.dev/t/zigtoberfest-2025/9598/8 "2025-10-29T21:31:57Z")
Nice article! I think example 7 is slightly misleading. It is only correct because the `io.sleep(.fromSeconds(1), .awake) catch {};` line does a lot of heavy-lifting by ensuring that the error and success code paths are the same. If there was a `try` after the allocation (for example if someone wrote `try io.sleep()`, which is very natural to do) then we would need to also add an `errdefer gpa.free(copied_string)` or something like that. This particular example is fine (canceling `sleep()` is just a shorter sleep) but usually functions creating resources do not return the resource if an error happened inside – they return an error. I think example 7 would be less _magical_ if it handled the `io.sleep()` errors explicitly. ---
**Author:** ![andrewrk](https://ziggit.dev/user_avatar/ziggit.dev/andrewrk/32/7011_2.png) [@andrewrk](https://ziggit.dev/u/andrewrk)\ **Post date:** [October 29, 2025, 10:06pm UTC](https://ziggit.dev/t/zigtoberfest-2025/9598/9 "2025-10-29T22:06:21Z")
Yes that’s a great point. I noticed that just after publishing the article. It’s always a challenge to balance making the examples realistic vs making them minimal and thus helpful for demonstration. ---
**Author:** ![r4gus](https://ziggit.dev/user_avatar/ziggit.dev/r4gus/32/5114_2.png) [@r4gus](https://ziggit.dev/u/r4gus)\ **Post date:** [November 30, 2025, 9:00pm UTC](https://ziggit.dev/t/zigtoberfest-2025/9598/10 "2025-11-30T21:00:07Z")
I’ve published a small blog post about Zigtoberfest. There are two versions available: - [German]([Zigtoberfest](https://zigtoberfest.de/news/20251130/de/)) - [English]( [Zigtoberfest](https://zigtoberfest.de/news/20251130/en/) )