@hipsterelectron@circumstances.run
2025-12-16 00:19 UTC
@epage@hachyderm.io @vavakado@mas.to @KFears@mstdn.games the only response i've seen from tolnay was not an apology and was a deleted github gist. i've contributed to his crates before in order to allow libsignal to depend on him. i am now taking whatever means are necessary to avoid introducing a dependency on a racist into my dependency graph, since they believe absurdities and are therefore quite dangerous in a supply chain.
Replies (1)
-
@hipsterelectron@circumstances.run 2025-12-16 00:20
@epage@hachyderm.io @vavakado@mas.to @KFears@mstdn.games perhaps steve klabnik would prefer to go on the oxide podcast again to describe tolnay's most objectionable episode as the time he worked around cargo's lack of a precompiled binary distribution mechanism, caching system straight from the 1900s, and complete failure to represent generalized build products generated by scripts in an auditable and overridable way by precompiling a macro in serde on x86. i believe the term "untrustworthy" was used to describe tolnay—not for fucking up rust's image indefinitely in a very public way, but for veering even slightly outside the chain of command.