Danila Poyarkov
1.5K posts






An even better solution would be to write it in Elixir. I’m already testing something along those lines internally and will publish it once it stabilizes. Unlike LiteLLM, I have no intention of commercializing something this simple, so it will be completely free and open source.






Finally, Durov can stop pretending that TON is not affiliated with Telegram. The idea was always quite simple: put a crypto wallet on every Telegram user’s device. Overnight, that would make Telegram one of the most widely adopted crypto wallets in the world. Because of the SEC ruling, Telegram had to build the entire Mini Apps infrastructure to make Wallet (a non-custodial wallet) and Tribute (microtransactions) look like independent third-party products. But the ties between those apps and the platform have always been easy to trace. Those apps were able to obtain bot handles without the “_bot” suffix long before Fragment auctions existed. Some people who have publicly disclosed their involvement with Wallet and Tribute previously worked at Telegram or VK. But now that the SEC under the Trump administration has become, ahem, “crypto-friendly”, Telegram can finally play with its cards on the table. So congrats to the team. I think there’s a good chance we’ll see crypto assets integrated directly into Telegram within a few weeks


I’ve just updated and found out that a beautiful native macOS app turned into yet another piece of Electron crap. Dammit. You have dozens of developers on seven-figure salaries and practically unlimited access to frontier models. Why can’t you keep maintaining a native app? What the hell are you trying to save by making such a downgrade?

I’ve just updated and found out that a beautiful native macOS app turned into yet another piece of Electron crap. Dammit. You have dozens of developers on seven-figure salaries and practically unlimited access to frontier models. Why can’t you keep maintaining a native app? What the hell are you trying to save by making such a downgrade?



Now that we merged ChatGPT and Codex, what should we merge next? What's the double or nothing move.


Noticing Fable is very often writing code comments that reference details from chatting with it, but they make very little sense in the context of reading it in the codebase







