this post was submitted on 13 Jun 2023
5 points (100.0% liked)
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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
A few things:
Personally, I don't have any preference. I will simply subscribe to the community which is the most active on whichever instance.
The downside to individual servers, and micro-communities, is the cost and maintenance of lemmy instance. Its more scalable, reliable and cheaper to have a bunch of relatively low-churn communities exist on one bigger instance.
The upside is that the rust community gets to own its own data. If programming.dev decides to shut down tomorrow, and posts and comments made there are gone. Lemmy doesn't mirror or cache... all that data lives solely on the server ran by somebody.
I'd vote lemmyrs at least for now until a governance and stability model is figured out to ensure these conversations don't go into /dev/null like /r/rust (sort of) did.
If say the Linux Foundation or a similarly large open source foundation (Apache, FSF, OSI, etc) decided to host a larger "open source" server, I'd consider moving there to improve discoverability and lessen the burden on the rust community itself
I think it would be really cool if the Rust Foundation had a Rust Lemmy instance!
Well, sure, if you know who the owner of lemmyrs is, and if they follow all the other stuff you talk about here.
Correct! Which is why I've already taken great pains to make sure that if something happens to me (owner of programming.dev) that the server continues to run. I already have someone else managing the domain with me, several people have access to the server. Backups occur daily. Is some sort of "legally separated backup where if I die the lawyers can hand over the db backups to someone else and they can take over" what you're looking for? I am trying very hard to make sure that the website does not depend on a single person to keep it running, but it seems like a lot of people want something to happen, but can't describe what that is.
Oh I'm not saying what your doing over at programming.dev is wrong or insufficient... Honestly I don't know what your doing to ensure the lemmy server exists long term (though its great to hear you've got some policies in place already).
I'm more thinking the rust community should evaluate options and vote, or some rust subgroup of the leadership should set criteria to ensure that another reddit-type event doesn't happen again (the home of this community must be open-source, with data backups publicly available, with a governing body and a line of succession or something, etc).
If programming.dev meets those things today, I'd say sure lets move there. I think its better to have a lemmy instance for a concept (computer science) than a specific topic (rust), but that's just me
Oh yes, I completely understood you weren't saying that. I'm asking what we can do to make it more likely for the community to want to be at !rust@programming.dev! I want to do as much as possible! The rust community would be a huge benefit to others in the instance, and we think others will be more likely to want to work on the Lemmy project if the Rust community does join. Having programmers alongside each other will be really helpful to us all I think.
Yeah I'd love to see this! The data backups being publicly available might cause a problem (then your usernames and passwords have a chance of being cracked 😬), but other than that, yeah I completely agree!
Agreed, there are advantages of having an own community. Especially until the people running e.g. programming.dev have a proven track record of being reliable.
Hi, creator of programming.dev here. What could we do to prove reliability to you? Would open graphs and metrics of the current state of the service help? Would current server costs and how much has been covered by donations help? Would knowing the names of everyone with access to the server, on the admin team, or access to the domain name help?
It seems to me like a user stood up an instance of lemmy and because it has
rsas part of the name you might be treating it like the Rust community's, but to me, it's exactly the same as programming.dev, except it has a lot less chance of staying running.