Re: #2.
Reproducible builds, that are only reproducible on Signal's servers, seems as if it's the opposite of any useful reproducible build system and peer reviewed science that I would ever want to endorse or rely upon personally.
jwz's detraction list also seems to omit that Signal's so-called "desktop" app, last I checked used Electron (https://www.electronjs.org/), which seems to run face first into the landmine against which
@tqbf@infosec.exchangeThomas H. Ptacek has warned against rather loudly about trusting anything cryptographic to ECMAScript/JavaScript. To say nothing for how Electron "apps" tend to sour faster than the rotting milk of Docker containers with toolchains that don't get updated as frequently as healthier OS ports and package paradigms.
As an example, I saw some others recommend Session as a Signal fork/alternative?
Even if you wanted to ignore
@soatok@furry.engineerSoatok Dreamseeker's reasons against Session https://soatok.blog/2025/01/14/dont-use-session-signal-fork/ I couldn't help but notice that Session's own "desktop" app was so far behind the times that it still required Apple's CPU translation layer "rosetta" (2) on Apple Silicon hardware, even after Apple had stopped selling Intel hardware entirely. Which is to say: whatever build system that Session uses is over four years behind the curve (coming up on five if you count the Apple Silicon DTK [Developer Transition Kit release date]). Maybe they're hiding the aarch64/M1 builds somewhere? session-desktop-mac-x64-1.15.2.dmg is what they link to (note: the x64, implying AMD64/Intel) by default on their website, even now as I reply.
Reproducible builds, that are only reproducible on Signal's servers, seems as if it's the opposite of any useful reproducible build system and peer reviewed science that I would ever want to endorse or rely upon personally.
jwz's detraction list also seems to omit that Signal's so-called "desktop" app, last I checked used Electron (https://www.electronjs.org/), which seems to run face first into the landmine against which
@tqbf@infosec.exchangeThomas H. Ptacek has warned against rather loudly about trusting anything cryptographic to ECMAScript/JavaScript. To say nothing for how Electron "apps" tend to sour faster than the rotting milk of Docker containers with toolchains that don't get updated as frequently as healthier OS ports and package paradigms.As an example, I saw some others recommend Session as a Signal fork/alternative?
Even if you wanted to ignore
@soatok@furry.engineerSoatok Dreamseeker's reasons against Session https://soatok.blog/2025/01/14/dont-use-session-signal-fork/ I couldn't help but notice that Session's own "desktop" app was so far behind the times that it still required Apple's CPU translation layer "rosetta" (2) on Apple Silicon hardware, even after Apple had stopped selling Intel hardware entirely. Which is to say: whatever build system that Session uses is over four years behind the curve (coming up on five if you count the Apple Silicon DTK [Developer Transition Kit release date]). Maybe they're hiding the aarch64/M1 builds somewhere? session-desktop-mac-x64-1.15.2.dmg is what they link to (note: the x64, implying AMD64/Intel) by default on their website, even now as I reply.