Re: Moxie on Web3
&gt; As for Signal it’s at least open source, but there’s no way to check that the client I’m using, or my friend is using, actually matches that source code.<p>This is… not true? Signal builds are reproducible. You can verify that the apk in the app store corresponds to a specific point in git history, and if you don&#x27;t trust Google you can sideload that.<p>&gt; Even if there was it’s irrelevant. Centralized infrastructure can claim to provide privacy but can never provide control: they can openly alter the deal at any time and I’d be forced to continue using it, if I couldn’t get my friends to switch to something else.<p>If you&#x27;re using Signal because of the E2E properties, and Signal unilaterally changes its behaviour, you are absolutely not forced to continue using it. If you do wish to continue communicating with people who are using Signal, you&#x27;re still able to reappraise what you feel comfortable saying now you know that the behaviour has changed.<p>The claim that &quot;Signal encryption doesn’t actually work&quot; just seems inaccurate. We can verify that Signal has the properties it claims it has. &quot;Signal encryption could stop working&quot; would be true - the client could absolutely just choose to start sending everything in plaintext, but we&#x27;re not relying on a centralised group to make that claim! Anyone can look at the commits to Signal and flag that the claimed properties no longer apply.