This commit introduces two meta tags to strengthen the application's security posture and enhance user privacy, following best practices and OWASP recommendations. - Add Content-Security-Policy (CSP) to strictly to strictly control which resources the application is allowed, mitigating the risk of code injection attacks such as Cross-Site Scripting (XSS). - Add `referrer` meta tag to prevent the users' browser from sending the page's address, or referrer, when navigating to another site, thereby enhancing user privacy.
55 lines
2.4 KiB
Markdown
55 lines
2.4 KiB
Markdown
# Desktop vs. Web Features
|
|
|
|
This table highlights differences between the desktop and web versions of `privacy.sexy`.
|
|
|
|
| Feature | Desktop | Web |
|
|
| ------- | ------- | --- |
|
|
| [Usage without installation](#usage-without-installation) | 🔴 Not available | 🟢 Available |
|
|
| [Offline usage](#offline-usage) | 🟢 Available | 🟡 Partially available |
|
|
| [Auto-updates](#auto-updates) | 🟢 Available | 🟢 Available |
|
|
| [Logging](#logging) | 🟢 Available | 🔴 Not available |
|
|
| [Script execution](#script-execution) | 🟢 Available | 🔴 Not available |
|
|
|
|
## Feature descriptions
|
|
|
|
### Usage without installation
|
|
|
|
You can use the web version directly in a browser without installation.
|
|
The desktop version requires download and installation.
|
|
|
|
> **Note for Linux users:** On Linux, privacy.sexy is available as an `AppImage`, a portable format that doesn't need traditional installation.
|
|
> This allows Linux users to use the desktop version without full installation, akin to the web version.
|
|
|
|
### Offline usage
|
|
|
|
The web version, once loaded, supports offline use.
|
|
Desktop version inherently allows offline usage.
|
|
|
|
### Auto-updates
|
|
|
|
Both the desktop and web versions of privacy.sexy provide timely access to the latest features and security improvements. The updates are automatically deployed from source code, reflecting the latest changes for enhanced security and reliability. For more details, see [CI/CD documentation](./ci-cd.md).
|
|
|
|
The desktop version ensures secure delivery through cryptographic signatures and version checks.
|
|
|
|
[Security is a top priority](./../SECURITY.md#update-security-and-integrity) at privacy.sexy.
|
|
|
|
> **Note for macOS users:** On macOS, the desktop version's auto-update process involves manual steps due to Apple's code signing costs.
|
|
> Users get notified about updates but might need to complete the installation manually.
|
|
> Consider [donating](https://github.com/sponsors/undergroundwires) to help improve this process ❤️.
|
|
|
|
### Logging
|
|
|
|
The desktop version supports logging of activities to aid in troubleshooting.
|
|
This feature is not available in the web version.
|
|
|
|
Log file locations vary by operating system:
|
|
|
|
- macOS: `$HOME/Library/Logs/privacy.sexy`
|
|
- Linux: `$HOME/.config/privacy.sexy/logs`
|
|
- Windows: `%APPDATA%\privacy.sexy\logs`
|
|
|
|
### Script execution
|
|
|
|
Direct execution of scripts is possible in the desktop version, offering a more integrated experience.
|
|
This functionality is not present in the web version due to browser limitations.
|