GrapheneOS (@GrapheneOS@grapheneos.social)
grapheneos.social
Choosing to write the Matrix server software in Python in the first place was a huge mistake. It's now far harder to develop and maintain the software. It heavily contributes to it being buggy and fragile. It's the biggest factor in it being so incredibly slow and hard to scale.

A chat server running on powerful hardware collapsing when handling more than 100 events per second isn’t acceptable. Events scale up based on room activity from non-local users including spammers too. It’s an issue for a server with 12 users too.

https://element.io/blog/scaling-to-millions-of-users-requires-synapse-pro/

Choosing to write the Matrix server software in Python in the first place was a huge mistake. It’s now far harder to develop and maintain the software. It heavily contributes to it being buggy and fragile. It’s the biggest factor in it being so incredibly slow and hard to scale.

  • MajorHavoc@programming.devEnglish
    7·
    9 days ago

    I don’t care for the look of giving technical critique to another project from a platform account. I would encourage the GrapheneOS team to switch to personal accounts for such discussions.

    It comes off as entitled - which we need less of in open source. I’m learning to recognize what comes off as entitled, because I often come across this way myself. I’m working on it, so I notice it more in others, today.

    It also has a junior developer vibe. I’ve found junior developers the most prone to comment “how hard could this really be?” from the sidelines of an effort.

    • akc3n@lemmy.mlMEnglish
      1·
      7 days ago

      Thank you for your feedback.

      Suggesting we use personal accounts for discussions like this overlooks the accountability we have to provide accurate and transparent feedback on issues directly impacting our infrastructure. Constructively critiquing software that affects the performance of hosting critical organizational chat rooms is not entitlement—it’s responsibility. These concerns are real and measurable, with tangible effects on user experience and scalability.

      This is based on firsthand experience hosting our own Matrix homeserver instance for our community space chat rooms using their software, not on tautological reasoning.

  • MajorHavoc@programming.devEnglish
    3·
    9 days ago

    As ever, static deep links to Mastodon posts show no content without JavaScript.

    I realize I’m the last person with JavaScript disabled, but others (and the server) still occasionally suffer since rather than serving the directly requested content, a piece of JavaScript is served that then requests the content.