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.
Hold a vote, which server we use. Within all the community, with everyone who has push access on GitHub, within the Leadership Council, on URLO, whatever. It doesn’t matter that much and, honestly, it’s bikeshedding.
Advertise it on the website and TWIR, and make the mods part of the Rust Moderation hierarchy.
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.
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.
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. [email protected].
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.