Tobias Bieniek

Tobias Bieniek

@tobias.bieniek.cloud

✈️ glider pilot 🦀 https://crates.io team & Rust Foundation engineer 🐹 Ember CLI team emeritus

305 followers118 following191 posts

Tobias Bieniek reposted

Dirkjan Ochtman
@djc.ochtman.nl

If you’re using rustls, upgrade to rustls-webpki 0.103.16 and/or webpki-roots or webpki-root-certs 1.0.10.

Filippo Valsorda@filippo.abyssdomain.expert

Update everything that verifies certificates against public roots.

Tobias Bieniek reposted

Dion Dokter
@diondokter.nl

"We don't want to use Rust because we don't want hundreds of dependencies" Ok, then just don't add dependencies? You're in control of your own destiny here! sudo-rs has only 2 which they deemed better than 0

Tobias Bieniek
@tobias.bieniek.cloud

🦀 or you can go to github.com/sponsors/rus... and sponsor the #rustlang project directly through the @rustfoundation.org maintainers fund 😉 more info at rust-lang.org/funding/ including links to all the people you can sponsor individually 😊

github.comSponsor @rustfoundation on GitHub SponsorsThe Rust Foundation is an independent non-profit organization dedicated to a more secure, performant, and versatile future through the use of the Rust programming language. Our work supports Rust's...
This post is unavailable.

Tobias Bieniek reposted

Michael Gattozzi
@mgattozzi.dev

Unfortunately a job offer I had fell through due to head count elimination so I am currently on the market for a new job! If you need someone with 11+ years of Rust, backend, and distributed systems experience I am your guy. Contact Email: michael@ductile.systems. Boosting appreciated!

Tobias Bieniek reposted

Marco Otte-Witte
@marcoow.bsky.social

.@mainmatter.com has an all-star Rust team available immediately. After some budget hiccups at one of our clients, we happen to have a well-established team of Rust experts around that's ready to go immediately. 1/🧵

Tobias Bieniek reposted

Josh Bressers
@josh.bressers.name

I had a chat with Erik Möller from @sovereign.tech about what they're doing in the universe of funding open source Eric breaks down what they're doing, how it works, and how you can apply for funding. We even learn about some similar projects happening in the EU

opensourcesecurity.ioSovereign Tech Agency with Erik MöllerEpisode Links Erik’s LinkedIn Sovereign Tech Agency Meet the First Sovereign Tech Standards Cohort Incident Report: unsanctioned agent behaviour during cyber testing STA on Mastodon This episode is al...

Tobias Bieniek reposted

pnpm
@pnpm.io

If you are on the latest pnpm v11.10.0 (or v10.34.5), you can try out the pnpm v12 alpha via: pnpm self-update 12.0.0-alpha.5 It is fully in Rust! 🦀

Tobias Bieniek reposted

Josh Bressers
@josh.bressers.name

I had a chat with Lori Lorusso and Niko Matsakis about the Rust Foundation Maintainers Fund Funding open source is a huge topic right now, the Rust Foundation has some great ideas. It will be exciting to watch this one grow and evolve #OpenSourceSecurity #rust #RustFoundation

opensourcesecurity.ioRust Foundation Maintainers Fund with Lori and NikoJosh chats with Lori Lorusso and Niko Matsakis about the Rust Foundation Maintainers Fund. This is a new project the Rust Foundation has create to help fund Rust maintainers. It’s a great discussion w...

Tobias Bieniek reposted

EuroRust
@eurorust.eu

🦀 Are you feeling lucky? Amos (@fasterthanli.me) and Tris (from No Boilerplate) are hosting a Rust game show at #EuroRust26! Two teams of expert panelists navigate bug-filled code in a spooky game show of pedantic corrections 🎲👻 Learn more 👉 eurorust.eu/talks/game-s... #RustLangNo

Tobias Bieniek
@tobias.bieniek.cloud

🦀 first basic prototype for the diff viewer on crates.io seems to work as planned 😍 and the regular code viewer is now publicly released :) #rustlang

Tobias Bieniek@tobias.bieniek.cloud

🦀 I did another thing... what do you think? 😄 Code viewer right inside of crates.io that shows the uploaded files ✨ It's still a prototype, but once I've cleaned it up I'll open a PR. Diff viewer next? 🙀 #rustlang

Tobias Bieniek
@tobias.bieniek.cloud

🦀 It's open for "public" beta testing now! Example: crates.io/crates/base6... The code viewer is not linked anywhere yet while we test it. Just append `/code` to the crate URLs 😉 #rustlang

Tobias Bieniek@tobias.bieniek.cloud

🦀 I did another thing... what do you think? 😄 Code viewer right inside of crates.io that shows the uploaded files ✨ It's still a prototype, but once I've cleaned it up I'll open a PR. Diff viewer next? 🙀 #rustlang

Tobias Bieniek
@tobias.bieniek.cloud

🦀 I did another thing... what do you think? 😄 Code viewer right inside of crates.io that shows the uploaded files ✨ It's still a prototype, but once I've cleaned it up I'll open a PR. Diff viewer next? 🙀 #rustlang

Tobias Bieniek
@tobias.bieniek.cloud

🦀 I've now extracted the dataset to github.com/rust-lang/st... This should make it easier to other tools to make use of the data. The combined dataset is available as rust-lang.github.io/std-replacem... :) Contributions welcome! ✨ #rustlang

github.comGitHub - rust-lang/std-replacement-data: Curated dataset of standard-library replacements for crates, surfaced on crates.ioCurated dataset of standard-library replacements for crates, surfaced on crates.io - rust-lang/std-replacement-data
Tobias Bieniek@tobias.bieniek.cloud

🦀 I did a thing... what do you think? github.com/rust-lang/cr... #rustlang

Tobias Bieniek reposted

daniel:// stenberg://
@bagder.mastodon.social.ap.brid.gy

A human in control. In #curl development. https://daniel.haxx.se/blog/2026/06/10/a-human-in-control/

daniel.haxx.seA human in controlThere seems to be a fair amount of people in either extremes in the current AI landscape. At one side we see the “vibe coders” who use agents and allow them to merge code without any person even looking at the source, while on the other side of the field there are people who are against everything and anything even remotely associated with AI. My personal stance is somewhere in between, as I suppose shouldn’t be too surprising to readers of this blog. ## A work of love and pride The core team behind curl, and that is more people than just me, consists of individuals to whom code quality and source code excellence is important. We do software development because it is a craft we love and we are proud of what we have accomplished this far. We do not hand over our responsibilities to any machines. _We stand for ever bit of code we merge – as humans._ ## AIs do mistakes Blindly accepting code written by AI means that you merge a certain amount of errors, but this is certainly true for human written code as well, so this is not in itself special. Some data suggests that AI generated code might even contain more mistakes than the human versions. We invented test cases and code review a long time ago as a means to help us combat and reduce mistakes to get merged. The particular way code was written does not take away the benefits from code review and getting additional checks and eyes on pending changes. A good code review helps spotting mistakes, omissions or slip-ups. It also helps reinforce the architecture and established design choices. This is true however the code was created. This far, code reviews done by automatic AI bots and the likes have not yet managed to replace the humans. They are simply not good enough. Human reviews are much better. They catch other things and they help make sure proposed changes stay on track. Not to mention how I want to know how curl works, even if I don’t keep 100% intimate knowledge of every single angle and corner, I know most of it. I think it helps me make better decisions, debug better, help users better and keep the architecture sound. Getting the initial code written is not the big deal. For curl, maintaining and polishing the landed code _through decades_ is the real task. _Everything we merge in curl is determined fine and fitting by humans._ ## Humans do mistakes In all living software projects we get bugs reported and we fix them. We do new releases and continue to iterate. We have done this since software was invented and we still do, as humans are quite fallible and easily make mistakes. We try to reduce the error density and frequency by adding tests and by adding more human eyes on the code before we green-light it. It helps, but is not perfect. To help us do better code we invent, introduce and enforce a wide variety of different tools. With tools that look at code and identify problems in the early stages, they help avoid landing bad code in the first place. They make us do better code. They reduce the bug frequency. Some of the best tools for detecting coding mistakes today use AI. These tools might work on existing source code in a git repository or they might look at proposed changes in pull-requests. Above I mentioned that human code reviews are better; but the opposite is also true. In a somewhat complicated change request, it is now common that after the humans can’t spot any more problems, the AI PR review bots can still find an issue or two to remark on. Sure, sometimes they are wrong and then the comment is easily dismissed, but more often than not the findings they point out are actually something worth addressing before merge. _curl is developed and driven by humans, assisted by tools._ ## Communication is for humans Open Source is about sharing code and is a development model where we do things in the open. The _communication_ part of this model is key. Share your ideas, your visions, your problems or maybe just your ideas for what to do this afternoon. Express what you want or what the problem is, and the team can respond and we can work together on fixing and improving whatever needs to be done. Effective communication, a condition for good Open Source, implies _human-to-human_ interaction. Inserting a large AI generated tone-deaf large wall-of-text into such a flow _can_ still work, but only in the same way humans can learn to work with difficult individuals as well. It is not ideal and it is not a smooth way of working. It introduces sand in the machine. Don’t do that. It is rude. _Effective Open Source work means we communicate as humans, even if parts of the work and the code is made with the help of AI._ ## The combination Humans and machines excel at different things. We can complement each other in software development. Everyone is free to act to their own will, but in the curl project we don’t hand over responsibility to machines. We stand for our product. We make it as good as we possibly can; using all the tools that are available to us. I claim that in order to do this, humans need to remain in control.

Tobias Bieniek reposted

EuroRust
@eurorust.eu

The full schedule for EuroRust 2026 is here! ✨ We have great speakers and talks, fun side activities, workshops and of course the impl day. If you haven’t already, now is the time to get your ticket! 🦀 See the full schedule and get your ticket 👇 eurorust.eu/schedule/ #RustLang #EuroRust

Tobias Bieniek
@tobias.bieniek.cloud

🦀 OMG, github.com/renovatebot/... is finally merged and released! 🎉 from now on renovatebot will automatically keep your `rust-toolchain.toml` files up-to-date with support for stable and nightly versions :) #rustlang

github.comfeat(rust-toolchain): Add `rust-toolchain` manager by Turbo87 · Pull Request #38554 · renovatebot/renovateNew package manager questionnaire Did you read our documentation on adding a package manager? I've read the adding a package manager documentation. Basics What's the name of the package ...

Tobias Bieniek reposted

Corbin Crutchley
@crutchcorn.dev

We at TanStack just had a major attack against our Router packages. We have a postmortem out now explaining what happened and how we mitigated the response: tanstack.com/blog/npm-sup... No other TanStack packages outside of the Router monorepo were impacted

tanstack.comPostmortem: TanStack npm supply-chain compromise | TanStack BlogOn 2026-05-11, an attacker chained a pull_request_target Pwn Request, GitHub Actions cache poisoning across the fork↔base trust boundary, and OIDC token extraction from runner memory to publish 84 mal...

Tobias Bieniek reposted

Mark Erikson
@acemarke.dev

I wrote about everything I've felt, feared, and experienced about using AI for code over the last few years, and my opinions on where we stand. It's the most personal thing I've ever written. And I'm putting it out there to share with all of you. blog.isquaredsoftware.com/2026/05/ai-t...

blog.isquaredsoftware.comMy Thoughts on AI, Part 1: Fears, Opinions, and Mental JourneyMy own personal thoughts and opinions on AI effects and usage, and how those have evolved over time