Ivan Yurchenko

Data streaming geek. Fight with machines at @aiven_io 🦀. Do stuff around @apachekafka. Used to run #HelsinkiJUG. All opinions are my own.

[Ivan Yurchenko @ivan0yu]

I'm hiring Apache #Kafka and Apache #Flink experts (esp. on the ops side) and engineers experienced with Python for the Kafka & Flink team in @aiven_io. Helsinki 🇫🇮, Berlin 🇩🇪 and also remote in some European 🇪🇺 countries.

RT please 😉

[Vesuvius Challenge @scrollprize]

I still can’t believe we’re reading Greek text from this piece of coal! Every month, we’ll award $20,000 to contributors who help us recover more text from other pieces of coal like this one. Join our Discord: https://t.co/hTtOORBWA1

[Cursor @cursor_ai]

We're excited to join forces with @SpaceX to advance the frontier of useful AI. Expect significant improvements to Cursor soon.

[The Witcher @thewitcher]

Medallion's humming... that can only mean one thing! It's time to announce The Witcher 3: Wild Hunt - Songs of the Past! ⚔️

This brand new expansion for The Witcher 3: Wild Hunt will take you to the Path with Geralt of Rivia once more. It’s being co-developed with @Fools_Theory and is coming to PC, Xbox Series X|S, and PlayStation 5 in 2027. Stay tuned for more information in late summer. ⏰

[Tobias Ziegler @Tobias__Ziegler]

If you're interested in SSD internals and how to use them efficiently, our paper, “How to Write to SSDs,” has been accepted to VLDB and is currently on the Hacker News front page. https://t.co/bwYAtPFTBg

[v @iavins]

UUID v4 collisions are less rare than you think 💣

[Marc Brooker @MarcJBrooker]

This is such a great example of theory vs practice. In theory, UUIDv4 collisions don't happen (generating one million per second, probability of seeing one collision in a year is ~10^-8).

But they have been observed to happen in practice, especially in distributed systems. Why?

[Obsidian @obsdmd]

https://t.co/6mKCfJLmao

[Lex Fridman @lexfridman]

Here's my conversation all about @FFmpeg, the legendary open-source software powering most video on the Internet. In the episode, I talk with Jean-Baptiste Kempf and Kieran Kunhya. JB is lead developer of VLC and Kieran is FFmpeg contributor, codec engineer, and the person behind the now-infamous @FFmpeg account on X.

VLC (@videolan), by the way, is also a legendary piece of open-source software: it's a video player that can open basically anything & has been downloaded over 6 billion times.

I think both FFmpeg and VLC are two of the most important and impactful software systems ever created, both open source, and both created & maintained by volunteers: brilliant engineers from all walks of life.

Thank you to everyone who contributed to FFmpeg and VLC, and in general to all engineers giving their heart & soul to building systems used by millions (or billions) of people, and often doing so not for money, status, or fame, but purely for the love of building great software and doing good for the world.

Thank you to the builders! 🙏❤️

Shoutouts in this chat to @ID_AA_Carmack @karpathy @elonmusk @TimSweeneyEpic and everyone who is a contributor & fan of open source!

It's here on X in full and is up everywhere else (see comment).

Timestamps:
0:00 - Episode highlight
2:17 - Introduction
5:35 - Weirdest things VLC opens
9:59 - How video playback works
19:20 - Video codecs and containers
30:07 - FFmpeg explained
51:07 - Linus Torvalds
55:46 - Turning down millions to keep VLC ad-free
1:10:04 - FFmpeg & Google drama
1:29:18 - FFmpeg developers
1:35:55 - VLC and FFmpeg
1:40:29 - History of FFmpeg
1:43:46 - Reverse engineering codecs
1:57:01 - FFmpeg testing
2:01:08 - Assembly code (handwritten)
2:25:26 - Rust programming language
2:34:42 - FFmpeg and Libav fork
2:43:04 - Open source burnout
2:50:51 - x264 and internet video
3:04:07 - Video compression basics
3:11:04 - CIA and fake VLC
3:21:39 - Ultra low latency streaming
3:39:07 - AV2 codec and video patents
3:48:59 - VLC backdoors
3:59:14 - Video archiving
4:05:51 - Future of FFmpeg and VLC

[Almog Gavra @almoggavra]

wild that changing malloc to jemalloc literaly 2x's the performance on our rust timeseries engine

[Lukasz Olejnik @lukOlejnik]

A 2005 state-designed worm designed to corrupt physics simulations sat undetected on VirusTotal for nearly a decade. Fast16, intercepted executable files at the kernel level and silently rewrote floating-point calculations to make them produce slightly wrong answers. Targets: high-precision engineering suites used for structural analysis, crash simulations, and physical process modeling, including LS-DYNA, a tool cited in reports on Iran's nuclear weapons research. The sabotage vector relied on deployment of the driver across a network via worm, corrupting calculations on every machine, and eliminating the possibility of cross-checking results against a clean system. Stuxnet got the documentary. Fast16 got twenty years of nothing. https://t.co/3qfJMziXVd

[Ivan Yurchenko @ivan0yu]

@brk0v Will add to https://t.co/tYKY9FltXi !

[DHH @dhh]

Also very impressive how quickly this came together. After @MichaelDell got the right people at Dell and Intel engaged, it was just a few weeks before we had solved everything, and could ship the final solution. Founder urgency since 1984 🤘

[DHH @dhh]

In celebration of Omarchy 3.5 being the first distro to ship with complete Linux compatibility for the new XPS Panther Lake laptops, @Dell made me a special unit with super + omarchy keys instead of Windows and Copilot. So damn cool!

[Aiven @aiven_io]

We're excited to announce the Limited Availability launch of Aiven Apps!

Unify your code and data, and deploy stateless applications inside your secure Aiven data perimeter. Stop paying the integration tax and minimize costly egress fees.

Learn more and get started today: https://t.co/Xi6QHxOzLj

#AivenApps #CloudNative #DevOps

[Georgi Gerganov @ggerganov]

llama.cpp at 100k stars

now that 90% of the code worldwide is being written by AI agents, I predict that within 3-6 months, 90% of all AI agents will be running locally with llama.cpp 😄

Jokes aside, I am going to use this small milestone as an opportunity to reflect a bit on the project and the state of AI from the perspective of local applications. There is a lot to say and discuss and yet it feels less and less important to try to make a point. Opinions about viability of local LLMs are strongly polarized, details are overlooked, the scientific approach is lacking. Arguments are predominantly based on vibes and hype waves.

One thing is clear though - local LLMs are used more and more. I expect this trend to continue and likely 2026 will end up being one of the most important years for the local AI movement.

I admit that I didn't expect the agentic era to come so quickly to the local LLM space. One year ago, the available models were too computationally expensive for doing long-context tasks. There wasn't an obvious path towards meaningful agentic applications. The memory and compute requirements were huge. Last summer, with the release of gpt-oss, things started to change. It was the first time we saw a glimpse of tool calling that actually works well within the resource constraints of our daily devices. Later in the year, even better models were released and by now, useful local agentic workflows are a reality.

Comparing local vs hosted capabilities at a given moment of time is pointless. To try put things into perspective:

- We don't need frontier intelligence to automate searches and sending emails
- We don't need trillion parameter models to be able to summarize articles or technical documents
- We don't need massive GPU data centers to control our home appliances or turn the lights off in the garage

I believe that there is a certain level of intelligence we as humans can comprehend and meaningfully utilize to improve our working process. Beyond that level, access to more intelligence becomes unnecessary at best and counterproductive at worst. I also believe that that level of useful artificial intelligence is completely within reach locally and it has always been just a matter of implementing the right software stack to bring it to the end user.

With llama.cpp, I am confident that we continue to be on the right track of building that software stack!

The llama.cpp project is going stronger than ever. With more than 1500 contributors, the project keeps growing steadily.

From technical point of view, I think that llama.cpp + ggml is the only solution that actually makes sense. That is, the software stack must run efficiently on every possible device, hardware and operating system. The technology is too important to be vendor-locked. It has to be developed in the open, by the community, together with the independent hardware vendors. This is the only right way to build something that will truly make a difference in the long run.

I won't try to convince you about what is currently and will be possible with local AI. We will just continue to build as usual. I am confident that after the smoke clears and we look objectively at what we have built together, the benefits will be obvious to everyone.

Big shoutout to all llama.cpp maintainers. I feel extremely lucky to be able to work together with so many talented contributors. Every day I learn something new and I feel there is so much more cool stuff that we are going to build. Also, I am really thankful that the project continues to have reliable partners to support it!

Cheers!

[lcamtuf @lcamtuf]

I'm dying. With this translate tool, I'm finally able to effectuate ideation synergies

[🇨🇳XuZhenqing徐祯卿 @XueJia24682]

✨🇨🇳This is the customized parking feature of XPeng Motors from China. You mark where you want to park, and it will automatically park there precisely.

[Ivan Yurchenko @ivan0yu]

7 years BTW

[Ivan Yurchenko @ivan0yu]

Now, I've joined an amazing company @aiven_io (thank you for the warm welcome!)

[Wholesome Side of 𝕏 @itsme_urstruly]

Bro pulled off the best video of his life