Be (9e08cfc3) at 25 Nov 05:17

Be (4839d3dd) at 07 Sep 21:24

Be (572e1172) at 07 Sep 09:31

... and 1 more commit

Be (fbcea72d) at 07 Sep 09:30

Be (ddf7a549) at 07 Sep 09:19

Be (49656748) at 07 Sep 09:18

Be (006c5c65) at 07 Sep 09:15

Be (5b26691d) at 07 Sep 09:02

Be (afae28d6) at 28 Feb 02:42

Be (b3249f63) at 28 Feb 02:25

Be (14721f92) at 09 Feb 02:18

Does that require any changes in Signal, or can this be taken care of entirely by F-Droid?

I was surprised to see an update notification for Signal from F-Droid today despite having installed Signal from the APK on their website and no public statements about this from Signal. I have a few questions about this:

1. Has shipping Signal this way been discussed and approved by the Signal developers?
2. I notice this just puts the upstream Signal APK builds into the Guardian Project's F-Droid repository rather than building from source (this is also what the Flatpak on Flathub does for Signal Desktop FWIW). Do you intend to build from source in the future?
3. The upstream Signal APK automatically checks Signal's server for updates and makes its own notifications separate from F-Droid. Since I just updated from F-Droid, I haven't yet seen myself how these might interact with F-Droid's notifications. Have you tested how this will work out? I imagine it could create a confusing user experience, which might only be solved by disabling the built-in update checks for Signal's server... which would presumably require building from source (there is no user option to disable this).

Be (f9695a51) at 08 Jan 23:52

Might a similar fix work for the other affected devices?

Can you please provide more details? Can you link to the Gerrit change or post the Git commit hash of the fix? What was the cause of the bug? Does the fix apply to all devices that have been reported to be affected?

Be (d5fb2305) at 07 Jun 18:57

Be (7e85f96d) at 07 Jun 18:51

I think changing the default to Pipewire will be sufficient to get the bug reports. But leaving users with a buggy setup without making it easy to fallback to what was working for them before wouldn't be very nice.

FWIW, I think Fedora was the first distro to ship Pipewire for audio by default. The way they are packaged in Fedora still makes it trivial to switch between PulseAudio (dnf install pulseaudio --allowerasing) and Pipewire (dnf install pipewire-pulseaudio --allowerasing) 3 years after the default was changed. AFAIK no Fedora packagers have a problem with this situation or any plans to change it. Note that there is no option for this at install time like this proposal; this is something users can easily change after installation.