• Björn Tantau@swg-empire.de
    link
    fedilink
    English
    arrow-up
    0
    ·
    4 months ago

    It takes up half a GB of RAM and constantly keeps the CPU active. It’s still on X11 and thus integrates poorly with the rest of my Wayland apps. It seems to report itself to Pipewire as something else every other week and is thus impossible to control reliably.

    It works well and I haven’t encountered any crashes or other bugs in months. But I genuinely think it could have been much better as a QT app or so. Plus, thanks to Electron there isn’t an ARM version either making it impossible to run on my Raspberry Pi or my Pinephone.

    • MeanEYE@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 months ago

      I don’t know why they didn’t just make it a web application. It’s the same damn thing. Just like there’s web.whatsapp.com, make Signal the same way. At least that way I get to use my own browser and in a single instance.

    • mrvictory1@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      4 months ago

      Use these to enable Wayland support: –enable-features=UseOzonePlatform --ozone-platform=wayland

      To launch the app on ARM, install electron from package manager, copy paste signal’s application directory and launch like this: /path/to/electron /path/to/app.asar

      I don’t use Signal, these are generic instructions for electron apps so YMMV.