Ganther
August 24, 2024, 11:25am
22
Signal for desktop was originally a browser extension. It had the huge advantage that it was available literally everywhere a Chromium browser could be run.
Is take a potential auto update attack any day over Signal having the sandbox intentionally disabled for a decade.
jonah
August 24, 2024, 2:58pm
23
This change is being made here:
privacyguides:main ← privacyguides:foreground-molly
opened 06:12PM - 22 Aug 24 UTC
Changes proposed in this PR:
- Move the Molly listing and other relevant part… s from the Signal Configuration and Hardening blog post to a listing under the Signal recommendation
- Relevant discussion: https://discuss.privacyguides.net/t/recommend-molly-instead-of-signal/17597/8
- Signal Config and Hardening post
- Remove parts about Molly in the Signal blog post that were ported to the RTC recommendation page
- Remove the Endpoint Security section
- Reason: IMO, the advice given here is somewhat redundant with the advice given elsewhere on the website regarding mobile OSes.
- Remove the Caveats section in the Molly section and move the relevant parts of it to the listing on the main site
- Reword Molly description to emphasize that it still uses the Signal network (credit goes to dngray's [comment](https://discuss.privacyguides.net/t/recommend-molly-instead-of-signal/17597/6) in the above forum thread)
- Sharpen some parts of both pages by including threat model labels and relevant links to the Common Threats page
- Lowercase "Forward Secrecy" on the RTC page where appropriate
## To Do
- [x] Restructure and add introduction to Molly section in blog post
---
<!-- SCROLL TO BOTTOM TO AGREE!:
Please use a descriptive title for your PR, it will be included in our changelog!
If you are making changes that you have a conflict of interest with, please
disclose this as well (this does not disqualify your PR by any means):
Conflict of interest contributions involve contributing about yourself,
family, friends, clients, employers, or your financial and other relationships.
Any external relationship can trigger a conflict of interest.
-->
<summary>
- [x] I agree to the terms listed below:
<details><summary>Contribution terms (click to expand)</summary>
1) I am the sole author of this work.
2) I agree to grant Privacy Guides a perpetual, worldwide, non-exclusive, transferable, royalty-free, irrevocable license with the right to sublicense such rights through multiple tiers of sublicensees, to reproduce, modify, display, perform, relicense, and distribute my contribution as part of this project.
3) I have disclosed any relevant conflicts of interest in my post.
4) I agree to the Community Code of Conduct.
</details>
<!-- What's this? When you submit a PR, you keep the Copyright for the work you
are contributing. We need you to agree to the above terms in order for us to
publish this contribution to our website. -->
1 Like
It seems a bit like Librewolf for Firefox.
Closing this thread as the PR marked as solution has been merged