• 0 Posts
  • 7 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle
  • I get that, and I agree with it in general, but there’s literally no company on earth that would approach open source developers with the intent to pay them to work on a closed source product, or to buy out their open source work without having an NDA in place. Hell, even if Meta just wants to pay them to do open source work to support the community, there will still likely be an NDA covering what they can say to the public about the arrangement or anything they learn from having access to internal systems.

    It’s like saying “Meta has security guards at the doors to their datacenters! They must be doing something illegal in there!”

    Meta is evil and is very likely doing something bad with these developers, but the NDA isn’t the smoking gun evidence of evil… It’s Meta’s history in general


  • I don’t know why everyone is so upset about the NDA thing… It’s such a standard business practice. Whenever I (a mid tier infra engineer at a mid sized software company) needed to talk to a vendor, get a product demo/consultation, get support on a licensed application, etc… We either sent an NDA to that company or bad one on file already with them. Nobody discusses internal processes, policies or roadmaps with an outside contact without an NDA first. It’s literally just a standard business practice.

    It could be nefarious, since it’s meta afterall, but I wouldn’t be shocked if there’s thousands of people/companies who have standing NDAs with meta just so they could come on campus and demo their product to some team



  • 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


  • It’s not the tech here. Postgres can scale both vertically and horizontally (yes there are others that can scale easier or in different factors of CAP).

    The problem is how the data is being stored and accessed. Lemmy is doing some really inefficient data access and it’s causing bottlenecks under load.

    Lemmy (unfortunately) just wasn’t ready for this level of primetime yet… It has a number of issues that are going to be quite tricky to fix now that it’s seen such wide adoption (database migrations are tricky on their own, doing so on a production site even harder, doing so on 8k+ independent production sites… Sounds like a nightmare)



  • 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