Signal-Desktop VS org.signal.Signal

2: https://github.com/signalapp/Signal-Desktop/issues/1862

If you only have the phone app then yes they are instantly downloaded and removed from their servers.

But if you have Desktop client(s) registered, then they need to hold onto those messages until you open your client(s).

That is why they have a 2 week (from memory) login limit on Desktop clients. If they didn't they'd potentially have to hold onto messages forever.

https://github.com/signalapp/Signal-Desktop/issues/4730

Love the product. Had a monthly recurring donation for many years. Dropped it over what I consider to be their serial mishandling of open source. See https://github.com/signalapp/Signal-Desktop/pull/6186 for the latest chapter in the, "we won't implement desktop GIPHY that we announced in 2016, and also won't merge it when someone else thoughtfully implements it for us" saga.

It does, see [0]. Fun fact: Signal desktop, which uses Electron under the hood, is running without sandbox on Linux [1][2].

[0] https://github.com/electron/electron/pull/39824

[1] https://github.com/signalapp/Signal-Desktop/issues/5195

[2] https://github.com/signalapp/Signal-Desktop/pull/4381

Issues have been ongoing for the past couple weeks. It's not clear if this is the client or backend. Dual stack works again with v6.20.2, but IPv6-only with NAT64 still doesn't. Actively being worked on, and hopefully some good learnings. Issue link thread: https://github.com/signalapp/Signal-Desktop/issues/6439

Fix1, Fix2, Fix3, Fix4

not able to do so after going through the CONTRIBUTING.md and following each and every step i am getting this error tried to search it on google and asked chatgpt too still not able to figure out

the CONTRIBUTING.md has steps using yarn tried using npm also still not able to do so

Compare https://github.com/signalapp/Signal-Desktop/commits/main with https://github.com/DrKLO/Telegram/commits/master

you can try using the flatpak version of signal

Even easier, from here: https://flathub.org/apps/details/org.signal.Signal * Open Terminal * Paste: flatpak install flathub org.signal.Signal * Given the choice for 1) system or 2) user * Choose either one (doesn't matter) * error: Nothing matches org.signal.Signal in remote flathub

It stands to reason, since the flathub build files on GitHub only provides x86_64 support. It's still coming down the pipeline and has been discussed and worked on since 2019. However, inside that thread I found there is a private flatpak repo by one called Elagost that provides aarch64/arm64 support. Be fore warned though: this is experimental and a private repo, so tread carefully. That being said, the build environment is available on GitLab. and besides lacking Wayland support it still seems promising.

you can use the flatpak version: https://flathub.org/apps/details/org.signal.Signal