• elucubra@sopuli.xyz
    link
    fedilink
    arrow-up
    38
    arrow-down
    4
    ·
    6 days ago

    Why didn’t they pour money on Jitsi?

    European, mature, FOSS…

    I fear grift is there somewhere.

    Also, French engineering has a habit of turning sound concepts into messy overengineerd but underbuilt results.

    • e8d79@discuss.tchncs.de
      link
      fedilink
      arrow-up
      30
      arrow-down
      1
      ·
      edit-2
      6 days ago

      My guess would be that its because La Suite tries to replace all of Microsoft Office and having all the moving parts under your organisations control makes it easier to create a fully integrated office suite that offers the same UX throughout. Also Jitsi is owned by 8x8, a US company, which might have factored into the decision to create something new.

    • matlag@sh.itjust.works
      link
      fedilink
      arrow-up
      10
      ·
      6 days ago

      The development is quite transparent. The team is looking at reduced development and more integration, so instead of “pouring money on a project”, they tried various solutions, and picked the “best one”.

      One criteria was an integration with their internal communication system: Tchap, essentially a Matrix server. The Matrix video call group didn’t cut it because it requires ElementX, and apparently there are unresolved issue there (no idea if it’s the app itself or due to customization of their Matrix server). They ended up with Visio, that is not a “new” solution: it’s based on LiveKit.

      https://github.com/tchapgouv/tchap-product/issues/259

    • gdaofb27584@lemmy.ml
      link
      fedilink
      arrow-up
      8
      ·
      edit-2
      5 days ago

      Also, French engineering has a habit of turning sound concepts into messy overengineerd but underbuilt results

      Any example ?

      • elucubra@sopuli.xyz
        link
        fedilink
        arrow-up
        1
        ·
        4 days ago

        I’ve had several French cars, starting with an R4. That one was good, did exactly what it was designed to do. Next I had Talbot Horizon, an american (Chrysler) car with a very good diesel engine. Then I had a Peugeot 505, that had a good engine that was over complicated to the extreme, to the point that the oli overflow pipe litrelly crossed over from one side of the engine to the other, a truly brain dead design. Also the electrics in the back were literally routed under the rear light seals, so a seal failure meant that the electrical system shorted when it rained, the central locking and windows actuators had similar design flaws.

        I also had a Xara, which had several secondary ecus, which had to be progressively eliminated , until I sent the thing to the scrap yard, out of despair, despite having a sound body and engine.

        I’m in Europe, and I sometimes play the game of observing how many old cars (15+ years) I spot by nationality. Plenty of German, Spanish, Czech, Japanese and Korean. Very few Italian or French.

        My daily driver now is a 26 year old Skoda. I do all maintenance. In nearly 500.000 km, it has had zero major failures. A few minor things, starter (Bosch), two window regulators, a CV joint, and the usual, belts, clutch, brake pads… Consumables. I love how logical the engine bay is.

    • matlag@sh.itjust.works
      link
      fedilink
      arrow-up
      3
      ·
      5 days ago

      Look, no offense, but had you check the github Readme, or the previous comments, as it is mentioned several times, and you would have found that it is just an integration of LiveKit in their internal communication system, called Tchap, and Tchap is just a customized non-federated Matrix server.

      No wheel reinvented.

    • stormdelay@sh.itjust.works
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      4 days ago

      I couldn’t find any particular justification going through their website and other communication, it’s not perfect but it’s probably not that big a deal for an open source project to host their code there? If I remember I’ll try to send them a message asking about it

  • ooterness@lemmy.world
    link
    fedilink
    English
    arrow-up
    12
    arrow-down
    1
    ·
    6 days ago

    Why would they name it “Visio”? That is already the name of a different Microsoft product.

  • Hemingways_Shotgun@lemmy.ca
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    4
    ·
    5 days ago

    I get that government use needs to be stringently tested for security, and so things take a little longer. But really, there are PLENTY of good FOSS products in existence that can be used as a base framework and a head-start to things like this.

    You don’t have to re-invent the wheel when you could easily fork Jitsi-meet and harden it/secure it to your needs in the government.

    Jitsi is one of my top 5 FOSS projects that are basically already mature enough to be used in a professional setting

  • idriss@lemmy.ml
    link
    fedilink
    arrow-up
    7
    ·
    6 days ago

    That’s one good place I want to see tax payer money going. Would be nice if a more governments join in and make big corpo irrelevant.

  • idriss@lemmy.ml
    link
    fedilink
    arrow-up
    5
    ·
    6 days ago

    That’s one good place I want to see tax payer money going. Would be nice if a more governments join in and make big corpo irrelevant.

  • blobjim [he/him]@hexbear.net
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    5 days ago

    Seems pretty neat. Hopefully it’s somewhat simple to compile and set up. It’s kind of weird that livekit is VC funded though. Not necessarily the best, since they might have to relicense it to make investors happy at some point.

    Look at their list of investors: https://livekit.io/about

    The programmability aspect of LiveKit is cool, not that it matters much since this “meet” app is just something built on top of livekit.