Rust Lang

7 readers

1 users here now

Rules [Developing]

Observe our code of conduct

Strive to treat others with respect, patience, kindness, and empathy.
We observe the Rust Project Code of Conduct.
Submissions must be on-topic
Posts must reference Rust or relate to things using Rust. For content that does not, use a text post to explain its relevance.
Post titles should include useful context.
For Rust questions, use the stickied Q&A thread. [TBD]
Arts-and-crafts posts are permitted on weekends.
No meta posts; message the mods instead.

Constructive criticism only

Criticism is encouraged, though it must be constructive, useful and actionable.
If criticizing a project on GitHub, you may not link directly to the project’s issue tracker. Please create a read-only mirror and link that instead.
Keep things in perspective
A programming language is rarely worth getting worked up over.
No zealotry or fanaticism.
Be charitable in intent. Err on the side of giving others the benefit of the doubt.

No endless relitigation

Avoid re-treading topics that have been long-settled or utterly exhausted.
Avoid bikeshedding.
This is not an official Rust forum, and cannot fulfill feature requests. Use the official venues for that.

No low-effort content

Showing off your new projects is fine

No memes or image macros

Please find other communities to post memes

No NSFW Content

There are many other NSFW communities, let’s keep this related to the language

founded 1 year ago

MODERATORS

admin@lemmyrs.org

erlend_sh@lemmyrs.org

Libs.rs is now closed source (gitlab.com)

submitted 1 year ago by manpacket@lemmyrs.org to c/rustlang@lemmyrs.org

31 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] Kerfuffle@sh.itjust.works 6 points 1 year ago (1 children)

Do you have suggestions what the future of lib.rs should be?

Not the same person, but my suggestions would be:

Reverse the decision to go closed source. Making stuff less transparent isn't really going to help, and the primary controversy is coming from philosophical differences not the code itself. You can't practically (and really shouldn't) hide your policies. So going closed source is just another thing for people to complain about.
Allow opting out of the opinionated parts in a relatively easy way. You can't force other adults to align with your philosophy here, and trying is just going to cause problems.
Personally, I think a better approach to the opinionated part isn't directly changing data or obscuring/deprioritizing results. What you could do instead is add a section that has some context about why you think certain categories/crates are harmful. This makes the information available but doesn't force people to do any particular thing.

I think by taking that approach you'll avoid a lot of the backlash because you are allowing people a choice.

I'm not a lawyer and this isn't legal advice, but personally I'd be pretty careful about editorializing/moderating content in this kind of situation. Suppose someone publishes as crate that actively causes harm. Users download it and get their data stolen/wiped/whatever. Can they reasonably have an expectation that you should have protected them from that sort of thing? After all, you are editorializing the content and going so far as to moderate content that doesn't cause direct immediate harm to an individual but even content that potentially is harmful to society.

Possibly I should disclose that I avoid lib.rs currently because I don't agree with the philosophy of editorializing crates and personally I hate opinionated stuff that doesn't give me choice/control. I use open source software/resources specifically because I care about having a choice. We don't disagree philosophically on points like the harm of crypto such as bitcoin, I just don't like this approach to dealing with it. Also, painting all crypto stuff with the same brush can potentially delay less (or maybe even non-?) harmful alternatives that don't involve wasting massive amounts of computation to no end.

[–] Zeitufah@lemmyrs.org 3 points 1 year ago (1 children)

Allow opting out of the opinionated parts in a relatively easy way. You can’t force other adults to align with your philosophy here, and trying is just going to cause problems.

Would a link to crates.io be enough here? When I want objective data, I go to crates.io; when I want curated info about crates or want to find a new crate for some topic I go to lib.rs; when I want hand-written info about crates I go to blessed.rs/crates.

I personally agree with your point 1. and slightly agree with your point 3.

[–] Kerfuffle@sh.itjust.works 1 points 1 year ago

Would a link to crates.io be enough here?

I'd tend to say: probably not. It's not that people don't know that crates.io exists, right? So that's not changing anything.

or want to find a new crate for some topic I go to lib.rs

And lib.rs will suppress the visibility of crates it thinks are "bad" and you'd never even know the crate existed to go look at the objective data on crates.io. Or let's say a result comes up but it's just an empty page with a link to crates.io: you won't have enough information to know whether it's worth going through the trouble of following a link to another site and a lot of people wouldn't bother.

So I don't think that change really solves anything.