• 23 Posts
  • 22 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle













  • 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.










  • Ask yourself, in three years from now will you be thinking “it’s so nice how Meta lets me follow and interact with their enormous userbase for free, without advertising, using my own open source server and frontend”?

    Remember that’s the basic expectation today for a participant in the fediverse. If this feels implausible, doing anything else is very incompatible with the fediverse’s existing values.

    The problem isn’t just that it’s Meta, it’s any situation where a much larger actor comes in with different motivations. Today we have a small number of users whose servers are almost exclusively run on a “community service” model. Meta is an advertising business. They are much bigger and will define the fediverse if allowed in. If we allow them to connect, it should be much later after organic growth which means we can assimilate them properly and deflect any bad behaviour.

    What might happen if Meta throws their weight around? I can predict at least three outcomes

    • Proprietary variations to ActivityPub, probably starting with something that seems “understandable” like moderation reasons.
    • Certain new features get centralised on Meta’s servers only (e.g. search) claiming that it’s for efficiency in the distributed environment.
    • Claiming spam problems, require individual instance operators or their users to verify themselves with Meta to enable federation.

    The question in my mind is whether their intention is to destroy the competition, or keep the fediverse alive as a way to claim that they are not a technical monopoly that needs to be broken up by regulators, in the same way that Google provides most of the funding for Firefox.









  • I get a different video, which is from one of the submitted links further down the page. My best guess is a Lemmy bug is shifting the clickable video element into a tiny box in the top right of the page.

    I’ve been having some other issues on and off with the thumbnail rendering since we updated to the RC so maybe it’s related. (Oddly the images are loading fine according to the network requests, it’s just the CSS isn’t being set right to display them.)







  • Yes. The interaction with the Rust Foundation is described in the linked RFC.

    The Council is responsible for establishing the process for selecting Project directors. The Project directors are the mechanism by which the Rust Project’s interests are reflected on the Rust Foundation board.

    The Council delegates a purview to the Project directors to represent the Project’s interests on the Foundation Board and to make certain decisions on Foundation-related matters. The exact boundaries of that purview are out of scope for this RFC.