Aloso

What’s the bad scenario you’re worried about here? What type of data you’re specifically worried about? Do you expect me to maliciously manipulate the data, or is even well-intentioned curation and use of heuristics somehow not acceptable?

I think they are worried that some crates may not show up in the search results, either because their author requested their removal, or you decreased their search ranking for political reasons.

And I agree with you that crates.io is not a viable alternative due to the poor quality of the search results. So switching from lib.rs to crates.io doesn't make sense for this reason alone, since crates.io may not display the crate you're looking for either, unless you already know its name.

You need to tell the user that this is an error, otherwise they don't know if it succeeded or not.

error: --att cannot be used at the same time as --intel

The last line is incomprehensible, just use a full sentence.

And are you sure the license is the sole reason for that? With a sample size of 2, this correlation might very well be coincidence. I'm not intimately familiar of the history of Linux or BSD, so I might be off base, but I don't think a permissive license like MIT prevents a project from being widely adopted and becoming successful.

Thanks, this link worked :)

I can't find it on LemmyRS, is it possible that LemmyRS is not federating with kbin.social?

i also saw that there’s about 200+ open tickets of variable importance

Note that it is normal that the number of open issues grows faster than issues are resolved. For example, rust-lang/rust has 8,963 open issues and 39,803 closed issues. microsoft/TypeScript has 6,001 open issues and 31,397 closed issues. A large number of open issues isn't necessarily concerning, unless high-priority issues (vulnerabilities and critical bugs) stay open for a long time.

• Custom CSS saved along with your user profile

You can use a browser extension like Stylus or Greasemonkey. Actually, I could create and publish a configurable userstyle if there's demand for it.

You mean the Rust logo? That is not a cog, it's a sprocket (a wheel that meshes with a bicycle chain).

I really like the darker colors. But I don't think it's possible to change the styles of this particular instance, it would have to be implemented in lemmy-ui (and then be available to all lemmy instances).

And note that capitalized text isn't particularly accessible. In fact, it is harder to read than regular text, because we have a lot more practice reading regular text than capitalized text.

I'd like for the r/rust community to completely migrate to lemmy, and for the r/rust moderators to become moderators of the chosen lemmy instance.

I don't care which instance it will be, although I do like the idea of the Rust community being fully self-sufficient and self-governed by hosting our own instance (but still being interoperable with others). The main downside seems to be that people who are active in multiple communities will need multiple accounts, and creating an account requires

• a unique username (too bad if the name you use on another instance is already taken here)
• a password you need to save in your password manager
• approval by the instance owners/moderators, which makes this not only tedious, but also slow

And if you use a mobile app as well as the web app, you need to login twice after the account was approved.

On another note: The lemmyrs.org instance currently has several "communities", which are more like categories. They might be a substitute for Reddit flairs, which should allow people to filter what they see on their Reddit homepage. However, Lemmy doesn't support flairs, and on r/rust they weren't actually used that much. Most people didn't set a flair when posting something, which kind of defeated the purpose. I think we should come up with a proper solution for this at some point.

Modifying the logo would likely violate the logo trademark. We could use Ferris instead (and that's what https://lemmy.ml/c/rust does)

There are executors for more specific use cases.

• For example, bastion is a "Highly-available Distributed Fault-tolerant Runtime", inspired by Erlang, and including an async executor.
• embassy includes an async executor specifically for embedded systems.
• fuchsia-async is an executor for use in the Fuchsia OS.
• wasm-bindgen-futures converts Rust Futures to JavaScript Promises and schedules them to run to completion. It could also be seen as a (very basic) executor.