this post was submitted on 27 Aug 2023
85 points (95.7% liked)
Rust Lang
3 readers
9 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
So, the main blocking problem for transitioning to the Threadiverse is that there are too many alternatives?
I know that the Rust project doesn't often make things "official", but in this case this would be a very easy way to solve a very real problem.
Later, when we have some way to collect communities together, we can diversify again to have a bit more resiliency against one server going down.
I know the Leadership Council is probably busy, but I would really love if they would do this (though I'm not very deep in the Rust Project myself, so I can't kick this off).
Agreed. Why overcomplicate things? I can understand the desire not to pick favourites in a rapidly-evolving space which was clearly the approach of /r/rust mods early on, but enough time has now passed that the project could save everyone some headaches by just picking one Lemmy community that they're confident will be held to the Rust community standards. Nobody's expecting a permanent decision with young software. We can change the way we operate again in a year or two if we have to.
Agreed, why throwing more programming, delays and complexity to it while the main goal is just to first find a new official home, P0 is to pick an instance, move to it and announce it. Then P1 if you want to federate better subcommunities: sure! do it! and the larger lemmy community will benefit from it.
I already commented this on programming.dev, but I would like to be able to use rust's domain in the fediverse. ex. user@fediverse.rust-lang.org.
It could provide as a method for better identity verification across the fediverse. I also think it just makes sense for rust's governance to control a fediverse instance, as they're more knowledgeable to the content that is posted. As an example, it doesn't make sense for a movies forum to host a community for surgeons. While programming.dev is relevant to programmers, it might be beneficial for rust's governance to be able expand communities on the instance for rust in the future.