371
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 06 Jul 2024
371 points (90.9% liked)
Technology
59054 readers
3182 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
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.
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.
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.