i3-gnome VS Signal-Server

I have not tried it since > Gnome 41 as I was mainly at home the last months, but I used this package in the past https://github.com/i3-gnome/i3-gnome

Install i3 on PopOS

Running F35 with i3wm + i3-gnome (https://github.com/i3-gnome/i3-gnome) -

I would also highly recommend i3 + i3-gnome combination [1]. It adds a lot of gnome features out of box to i3, like sound control, notifications, etc.

1: https://github.com/i3-gnome/i3-gnome

Remove/change all the gnome hotkeys/shortcuts using dconf-editor so I can use Gnome environment like i3. I do enjoy the ease of plug and play-ablity of gnome against i3. But I just...don't like the environment. I have checked i3-gnome. It makes the HDMI output stop working.

https://github.com/i3-gnome/i3-gnome You need to do this but with dwm

Hmm, sounds a bit like you'd want i3-gnome, which states it has support for gnome 40, though my guess is that this will give you Gnome DE with i3 instead of Mutter being the only difference, so no polybar.

> They could at least BSL the server code and allow others to verify the server code and host but not compete.

This is exactly what they do (except they use AGPL): https://github.com/signalapp/Signal-Server

https://github.com/signalapp/Signal-Server/blob/main/service/src/main/java/org/whispersystems/textsecuregcm/push/APNSender.java for APNs push notification payloads

git clone https://github.com/signalapp/Signal-Server.git

yes it is available here https://github.com/signalapp/Signal-Server/blob/main/service/pom.xml

You could also start your own signal server, but with blackjack, and hookers

The fact that it locks you into using their servers, does not distribute on F-Droid (only Google Play OR an APK with an insecure update mechanism), and has a completely closed-source "abusive message filter" module server side, that could functionally be used for censorship, storing messages for future decryption, or any other number of nefarious purposes - we have no idea since it's not open source (https://github.com/signalapp/Signal-Server/blob/main/.gitmod...).

Additionally, you cannot distribute branded forks or Signal, and if you do fork it, your fork is not allowed to connect to Signal's "official" OWS (open whisper systems) servers - hostility to federation should be viewed with prejudice and suspicion at the very least, it suggests a vested interest in a single point of failure (or control), which goes against user interests.

Further reading: https://drewdevault.com/2018/08/08/Signal.html

It’s actually the signal server that isn’t reproducible because of the abusive message filter that’s in a private repository. It’s clear as day here: https://github.com/signalapp/Signal-Server