Previously: https://lemmyrs.org/post/175672

I originally had sources and data of the site public, hoping they would be interesting to study, aid in bug reporting, bring contributions, and make site’s algorithms transparent.

Instead, I got knee-jerk reactions about lines of code taken out of context. I got angry dogpiles from the Rust community, including rust-lang org members. I don’t need to endure such mudslinging. Therefore, the sources are no longer available.

As of right now bitcoin crate is not deprecated, instead libs.rs responds with error 502.

  • Anders429@lemmy.world
    link
    fedilink
    English
    arrow-up
    19
    ·
    1 year ago

    I can’t say I’m surprised. I was honestly wondering how this backlash would affect kornel; it can’t feel good to get such a negative response on an open source project like this, and I feel bad for him. While I strictly don’t agree with the actions done against crypto crates, especially not the marking of an active crate as deprecated, I thought that some of the other reactions to things like marking crates as non-semver compliant were overblown.

    Specifically, I think one of the cases definitely was an accident, as it probably was made at a point when it really looked like the author was doing the same 1.0.x format that some other notable crates are guilty of, even thought that turned out to not be the case.

    Ultimately, this is a good example of why crates.io is so hesitant to be opinionated at all about anything, which is I think a big reason why something like lib.rs came into existence anyway. If anyone has been wondering why crates.io is so hesitant to stop people from squatting crates names, it’s because they would get reactions like this. Being opinionated means things will get political and the community may divide themselves over it.