mirror of
https://github.com/privacyguides/privacyguides.org.git
synced 2024-07-01 17:11:32 +00:00
Open-source hyphens fix (#2295)
Signed-off-by: Daniel Gray <dngray@privacyguides.org> Signed-off-by: Jonah Aragon <jonah@triplebit.net>
This commit is contained in:
ticklemyIP
Daniel Gray
parent
add980a655
commit
de216b9cde
|
|
@ -17,7 +17,7 @@ We do not make money from recommending certain products, we do not use affiliate
|
|||
We apply these priorities when considering new recommendations:
|
||||
|
||||
- **Secure**: Tools should follow security best-practices wherever applicable.
|
||||
- **Source Availability**: Open source projects are generally preferred over equivalent proprietary alternatives.
|
||||
- **Source Availability**: Open-source projects are generally preferred over equivalent proprietary alternatives.
|
||||
- **Cross-Platform**: We typically prefer recommendations to be cross-platform, to avoid vendor lock-in.
|
||||
- **Active Development**: The tools that we recommend should be actively developed, unmaintained projects will be removed in most cases.
|
||||
- **Usability**: Tools should be accessible to most computer users, an overly technical background should not be required.
|
||||
|
|
|
|||
|
|
@ -80,7 +80,7 @@ So far in 2023 we've launched international translations of our website in [Fren
|
|||
- [:simple-github: GitHub](https://github.com/hook9 "@hook9")
|
||||
- [:simple-mastodon: Mastodon](https://mastodon.neat.computer/@oliviablob "@oliviablob@neat.computer"){rel=me}
|
||||
|
||||
Additionally, [many people](https://github.com/privacyguides/privacyguides.org/graphs/contributors) have made contributions to the project. You can too, we're open sourced on GitHub, and accepting translation suggestions on [Crowdin](https://crowdin.com/project/privacyguides).
|
||||
Additionally, [many people](https://github.com/privacyguides/privacyguides.org/graphs/contributors) have made contributions to the project. You can too, we're open source on GitHub, and accepting translation suggestions on [Crowdin](https://crowdin.com/project/privacyguides).
|
||||
|
||||
Our team members review all changes made to the website and handle administrative duties such as web hosting and financials, however they do not personally profit from any contributions made to this site. Our financials are transparently hosted by the Open Collective Foundation 501(c)(3) at [opencollective.com/privacyguides](https://opencollective.com/privacyguides). Donations to Privacy Guides are generally tax-deductible in the United States.
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ Privacy Guides is not a law firm. As such, the Privacy Guides website and contri
|
|||
|
||||
Running this website, like any human endeavor, involves uncertainty and trade-offs. We hope this website helps, but it may include mistakes and can’t address every situation. If you have any questions about your situation, we encourage you to do your own research, seek out other experts, and engage in discussions with the Privacy Guides community. If you have any legal questions, you should consult with your own legal counsel before moving forward.
|
||||
|
||||
Privacy Guides is an open source project contributed to under licenses that include terms that, for the protection of the website and its contributors, make clear that the Privacy Guides project and website is offered "as-is", without warranty, and disclaiming liability for damages resulting from using the website or any recommendations contained within. Privacy Guides does not warrant or make any representations concerning the accuracy, likely results, or reliability of the use of the materials on the website or otherwise relating to such materials on the website or on any third-party sites linked on this site.
|
||||
Privacy Guides is an open-source project contributed to under licenses that include terms that, for the protection of the website and its contributors, make clear that the Privacy Guides project and website is offered "as-is", without warranty, and disclaiming liability for damages resulting from using the website or any recommendations contained within. Privacy Guides does not warrant or make any representations concerning the accuracy, likely results, or reliability of the use of the materials on the website or otherwise relating to such materials on the website or on any third-party sites linked on this site.
|
||||
|
||||
Privacy Guides additionally does not warrant that this website will be constantly available, or available at all.
|
||||
|
||||
|
|
|
|||
|
|
@ -76,7 +76,7 @@ BurungHantu also made a [twitter post](https://twitter.com/privacytoolsIO/status
|
|||
|
||||
As of September 25th 2022 we are seeing BurungHantu's overall plans come to fruition on privacytools.io, and this is the very reason we decided to create this explainer page today. The website he is operating appears to be a heavily SEO-optimized version of the site which recommends tools in exchange for financial compensation. Very recently, IVPN and Mullvad, two VPN providers near-universally [recommended](../vpn.md) by the privacy community and notable for their stance against affiliate programs were removed from PrivacyTools. In their place? NordVPN, Surfshark, ExpressVPN, and hide.me; Giant VPN corporations with untrustworthy platforms and business practices, notorious for their aggressive marketing and affiliate programs.
|
||||
|
||||
==**PrivacyTools has become exactly the type of site we [warned against](https://web.archive.org/web/20210729205249/https://blog.privacytools.io/the-trouble-with-vpn-and-privacy-reviews/) on the PrivacyTools blog in 2019.**== We've tried to keep our distance from PrivacyTools since the transition, but their continued harassment towards our project and now their absurd abuse of the credibility their brand gained over 6 years of open source contributions is extremely troubling to us. Those of us actually fighting for privacy are not fighting against each other, and are not getting our advice from the highest bidder.
|
||||
==**PrivacyTools has become exactly the type of site we [warned against](https://web.archive.org/web/20210729205249/https://blog.privacytools.io/the-trouble-with-vpn-and-privacy-reviews/) on the PrivacyTools blog in 2019.**== We've tried to keep our distance from PrivacyTools since the transition, but their continued harassment towards our project and now their absurd abuse of the credibility their brand gained over 6 years of open-source contributions is extremely troubling to us. Those of us actually fighting for privacy are not fighting against each other, and are not getting our advice from the highest bidder.
|
||||
|
||||
## r/privacytoolsIO Now
|
||||
|
||||
|
|
|
|||
|
|
@ -181,7 +181,7 @@ Google Pixel phones are the **only** devices we recommend for purchase. Pixel ph
|
|||
|
||||
Secure Elements like the Titan M2 are more limited than the processor's Trusted Execution Environment used by most other phones as they are only used for secrets storage, hardware attestation, and rate limiting, not for running "trusted" programs. Phones without a Secure Element have to use the TEE for *all* of those functions, resulting in a larger attack surface.
|
||||
|
||||
Google Pixel phones use a TEE OS called Trusty which is [open-source](https://source.android.com/security/trusty#whyTrusty), unlike many other phones.
|
||||
Google Pixel phones use a TEE OS called Trusty which is [open source](https://source.android.com/security/trusty#whyTrusty), unlike many other phones.
|
||||
|
||||
The installation of GrapheneOS on a Pixel phone is easy with their [web installer](https://grapheneos.org/install/web). If you don't feel comfortable doing it yourself and are willing to spend a bit of extra money, check out the [NitroPhone](https://shop.nitrokey.com/shop) as they come preloaded with GrapheneOS from the reputable [Nitrokey](https://www.nitrokey.com/about) company.
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ schema:
|
|||
mainEntity:
|
||||
-
|
||||
"@type": Question
|
||||
name: Is open source software inherently secure?
|
||||
name: Is open-source software inherently secure?
|
||||
acceptedAnswer:
|
||||
"@type": Answer
|
||||
text: |
|
||||
|
|
|
|||
|
|
@ -93,7 +93,7 @@ They have also received the Digital Trust Label, a certification from the [Swiss
|
|||
|
||||
Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page.
|
||||
|
||||
- Clients should be open-source.
|
||||
- Clients should be open source.
|
||||
- Clients should be audited in their entirety by an independent third-party.
|
||||
- Should offer native clients for Linux, Android, Windows, macOS, and iOS.
|
||||
- These clients should integrate with native OS tools for cloud storage providers, such as Files app integration on iOS, or DocumentsProvider functionality on Android.
|
||||
|
|
|
|||
|
|
@ -54,19 +54,19 @@ When sharing files, be sure to remove associated metadata. Image files commonly
|
|||
|
||||
The metadata that is erased depends on the image's file type:
|
||||
|
||||
* **JPEG**: ICC Profile, Exif, Photoshop Image Resources and XMP/ExtendedXMP metadata will be erased if it exists.
|
||||
* **PNG**: ICC Profile, Exif and XMP metadata will be erased if it exists.
|
||||
* **WebP**: ICC Profile, Exif and XMP metadata will be erased if it exists.
|
||||
- **JPEG**: ICC Profile, Exif, Photoshop Image Resources and XMP/ExtendedXMP metadata will be erased if it exists.
|
||||
- **PNG**: ICC Profile, Exif and XMP metadata will be erased if it exists.
|
||||
- **WebP**: ICC Profile, Exif and XMP metadata will be erased if it exists.
|
||||
|
||||
After processing the images, ExifEraser provides you with a full report about what exactly was removed from each image.
|
||||
|
||||
The app offers multiple ways to erase metadata from images. Namely:
|
||||
|
||||
* You can share an image from another application with ExifEraser.
|
||||
* Through the app itself, you can select a single image, multiple images at once, or even an entire directory.
|
||||
* It features a "Camera" option, which uses your operating system's camera app to take a photo, and then it removes the metadata from it.
|
||||
* It allows you to drag photos from another app into ExifEraser when they are both open in split-screen mode.
|
||||
* Lastly, it allows you to paste an image from your clipboard.
|
||||
- You can share an image from another application with ExifEraser.
|
||||
- Through the app itself, you can select a single image, multiple images at once, or even an entire directory.
|
||||
- It features a "Camera" option, which uses your operating system's camera app to take a photo, and then it removes the metadata from it.
|
||||
- It allows you to drag photos from another app into ExifEraser when they are both open in split-screen mode.
|
||||
- Lastly, it allows you to paste an image from your clipboard.
|
||||
|
||||
### Metapho (iOS)
|
||||
|
||||
|
|
@ -142,5 +142,5 @@ The app offers multiple ways to erase metadata from images. Namely:
|
|||
|
||||
We are working on establishing defined criteria for every section of our site, and this may be subject to change. If you have any questions about our criteria, please [ask on our forum](https://discuss.privacyguides.net/latest) and don't assume we didn't consider something when making our recommendations if it is not listed here. There are many factors considered and discussed when we recommend a project, and documenting every single one is a work-in-progress.
|
||||
|
||||
- Apps developed for open-source operating systems must be open-source.
|
||||
- Apps developed for open-source operating systems must be open source.
|
||||
- Apps must be free and should not include ads or other limitations.
|
||||
|
|
|
|||
|
|
@ -184,7 +184,7 @@ While we [recommend against](os/linux-overview.md#release-cycle) "perpetually ou
|
|||
|
||||
Choosing a Linux distro that is right for you will come down to a huge variety of personal preferences, and this page is **not** meant to be an exhaustive list of every viable distribution. Our Linux overview page has some advice on [choosing a distro](os/linux-overview.md#choosing-your-distribution) in more detail. The distros on *this* page do all generally follow the guidelines we covered there, and all meet these standards:
|
||||
|
||||
- Free and open-source.
|
||||
- Free and open source.
|
||||
- Receives regular software and kernel updates.
|
||||
- [Avoids X11](os/linux-overview.md#wayland).
|
||||
- The notable exception here is Qubes, but the isolation issues which X11 typically has are avoided by virtualization. This isolation only applies to apps *running in different qubes* (virtual machines), apps running in the *same* qube are not protected from each other.
|
||||
|
|
|
|||
|
|
@ -225,7 +225,7 @@ Canary Mail is closed-source. We recommend it due to the few choices there are f
|
|||
|
||||
### Minimum Qualifications
|
||||
|
||||
- Apps developed for open-source operating systems must be open-source.
|
||||
- Apps developed for open-source operating systems must be open source.
|
||||
- Must not collect telemetry, or have an easy way to disable all telemetry.
|
||||
- Must support OpenPGP message encryption.
|
||||
|
||||
|
|
@ -233,7 +233,7 @@ Canary Mail is closed-source. We recommend it due to the few choices there are f
|
|||
|
||||
Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page.
|
||||
|
||||
- Should be open-source.
|
||||
- Should be open source.
|
||||
- Should be cross-platform.
|
||||
- Should not collect any telemetry by default.
|
||||
- Should support OpenPGP natively, i.e. without extensions.
|
||||
|
|
|
|||
|
|
@ -343,7 +343,7 @@ When encrypting with PGP, you have the option to configure different options in
|
|||
|
||||
### Minimum Qualifications
|
||||
|
||||
- Cross-platform encryption apps must be open-source.
|
||||
- Cross-platform encryption apps must be open source.
|
||||
- File encryption apps must support decryption on Linux, macOS, and Windows.
|
||||
- External disk encryption apps must support decryption on Linux, macOS, and Windows.
|
||||
- Internal (OS) disk encryption apps must be cross-platform or built in to the operating system natively.
|
||||
|
|
|
|||
|
|
@ -41,7 +41,7 @@ When you are using an instance run by someone else, make sure to read the privac
|
|||
|
||||
{ align=right }
|
||||
|
||||
**ProxiTok** is an open source frontend to the [TikTok](https://www.tiktok.com) website that is also self-hostable.
|
||||
**ProxiTok** is an open-source frontend to the [TikTok](https://www.tiktok.com) website that is also self-hostable.
|
||||
|
||||
There are a number of public instances, with some instances having [Tor](https://www.torproject.org) onion services support.
|
||||
|
||||
|
|
|
|||
|
|
@ -22,12 +22,12 @@ cover: multi-factor-authentication.webp
|
|||
|
||||
The [comparison table](https://www.yubico.com/store/compare/) shows the features and how the YubiKeys compare. We highly recommend that you select keys from the YubiKey 5 Series.
|
||||
|
||||
YubiKeys can be programmed using the [YubiKey Manager](https://www.yubico.com/support/download/yubikey-manager/) or [YubiKey Personalization Tools](https://www.yubico.com/support/download/yubikey-personalization-tools/). For managing TOTP codes, you can use the [Yubico Authenticator](https://www.yubico.com/products/yubico-authenticator/). All of Yubico's clients are open-source.
|
||||
YubiKeys can be programmed using the [YubiKey Manager](https://www.yubico.com/support/download/yubikey-manager/) or [YubiKey Personalization Tools](https://www.yubico.com/support/download/yubikey-personalization-tools/). For managing TOTP codes, you can use the [Yubico Authenticator](https://www.yubico.com/products/yubico-authenticator/). All of Yubico's clients are open source.
|
||||
|
||||
For models which support HOTP and TOTP, there are 2 slots in the OTP interface which could be used for HOTP and 32 slots to store TOTP secrets. These secrets are stored encrypted on the key and never expose them to the devices they are plugged into. Once a seed (shared secret) is given to the Yubico Authenticator, it will only give out the six-digit codes, but never the seed. This security model helps limit what an attacker can do if they compromise one of the devices running the Yubico Authenticator and make the YubiKey resistant to a physical attacker.
|
||||
|
||||
!!! warning
|
||||
The firmware of YubiKey is not open-source and is not updatable. If you want features in newer firmware versions, or if there is a vulnerability in the firmware version you are using, you would need to purchase a new key.
|
||||
The firmware of YubiKey is not open source and is not updatable. If you want features in newer firmware versions, or if there is a vulnerability in the firmware version you are using, you would need to purchase a new key.
|
||||
|
||||
### Nitrokey
|
||||
|
||||
|
|
@ -57,7 +57,7 @@ For the models which support HOTP and TOTP, there are 3 slots for HOTP and 15 fo
|
|||
|
||||
The Nitrokey Pro 2, Nitrokey Storage 2, and the upcoming Nitrokey 3 supports system integrity verification for laptops with the [Coreboot](https://www.coreboot.org/) + [Heads](https://osresearch.net/) firmware.
|
||||
|
||||
Nitrokey's firmware is open-source, unlike the YubiKey. The firmware on modern NitroKey models (except the **NitroKey Pro 2**) is updatable.
|
||||
Nitrokey's firmware is open source, unlike the YubiKey. The firmware on modern NitroKey models (except the **NitroKey Pro 2**) is updatable.
|
||||
|
||||
### Criteria
|
||||
|
||||
|
|
|
|||
|
|
@ -133,7 +133,7 @@ Cryptee offers 100MB of storage for free, with paid options if you need more. Si
|
|||
|
||||
We are working on establishing defined criteria for every section of our site, and this may be subject to change. If you have any questions about our criteria, please [ask on our forum](https://discuss.privacyguides.net/latest) and don't assume we didn't consider something when making our recommendations if it is not listed here. There are many factors considered and discussed when we recommend a project, and documenting every single one is a work-in-progress.
|
||||
|
||||
- Clients must be open-source.
|
||||
- Clients must be open source.
|
||||
- Any cloud sync functionality must be E2EE.
|
||||
- Must support exporting documents into a standard format.
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ The **Android Open Source Project** is a secure mobile operating system featurin
|
|||
|
||||
### Choosing an Android Distribution
|
||||
|
||||
When you buy an Android phone, the device's default operating system often comes with invasive integration with apps and services that are not part of the [Android Open-Source Project](https://source.android.com/). An example of such is Google Play Services, which has irrevocable privileges to access your files, contacts storage, call logs, SMS messages, location, camera, microphone, hardware identifiers, and so on. These apps and services increase the attack surface of your device and are the source of various privacy concerns with Android.
|
||||
When you buy an Android phone, the device's default operating system often comes with invasive integration with apps and services that are not part of the [Android Open Source Project](https://source.android.com/). An example of such is Google Play Services, which has irrevocable privileges to access your files, contacts storage, call logs, SMS messages, location, camera, microphone, hardware identifiers, and so on. These apps and services increase the attack surface of your device and are the source of various privacy concerns with Android.
|
||||
|
||||
This problem could be solved by using a custom Android distribution that does not come with such invasive integration. Unfortunately, many custom Android distributions often violate the Android security model by not supporting critical security features such as AVB, rollback protection, firmware updates, and so on. Some distributions also ship [`userdebug`](https://source.android.com/setup/build/building#choose-a-target) builds which expose root via [ADB](https://developer.android.com/studio/command-line/adb) and require [more permissive](https://github.com/LineageOS/android_system_sepolicy/search?q=userdebug&type=code) SELinux policies to accommodate debugging features, resulting in a further increased attack surface and weakened security model.
|
||||
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ There are some notable privacy concerns with Linux which you should be aware of.
|
|||
- Maintain [software freedom](https://www.gnu.org/philosophy/free-sw.en.html#four-freedoms)
|
||||
- Use privacy focused systems such as [Whonix](https://www.whonix.org) or [Tails](https://tails.boum.org/)
|
||||
|
||||
### Open Source Security
|
||||
### Open-Source Security
|
||||
|
||||
It is a [common misconception](../basics/common-misconceptions.md#open-source-software-is-always-secure-or-proprietary-software-is-more-secure) that Linux and other open-source software is inherently secure simply because the source code is available. There is an expectation that community verification occurs regularly, but this isn’t always [the case](https://seirdy.one/posts/2022/02/02/floss-security/).
|
||||
|
||||
|
|
|
|||
|
|
@ -160,7 +160,7 @@ Bitwarden also features [Bitwarden Send](https://bitwarden.com/products/send/),
|
|||
|
||||
You need the [Premium Plan](https://bitwarden.com/help/about-bitwarden-plans/#compare-personal-plans) to be able to share files. The free plan only allows text sharing.
|
||||
|
||||
Bitwarden's server-side code is [open-source](https://github.com/bitwarden/server), so if you don't want to use the Bitwarden cloud, you can easily host your own Bitwarden sync server.
|
||||
Bitwarden's server-side code is [open source](https://github.com/bitwarden/server), so if you don't want to use the Bitwarden cloud, you can easily host your own Bitwarden sync server.
|
||||
|
||||
**Vaultwarden** is an alternative implementation of Bitwarden's sync server written in Rust and compatible with official Bitwarden clients, perfect for self-hosted deployment where running the official resource-heavy service might not be ideal. If you are looking to self-host Bitwarden on your own server, you almost certainly want to use Vaultwarden over Bitwarden's official server code.
|
||||
|
||||
|
|
@ -239,7 +239,7 @@ Psono provides extensive documentation for their product. The web-client for Pso
|
|||
Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page.
|
||||
|
||||
- Telemetry should be opt-in (disabled by default) or not collected at all.
|
||||
- Should be open-source and reasonably self-hostable.
|
||||
- Should be open source and reasonably self-hostable.
|
||||
|
||||
## Local Storage
|
||||
|
||||
|
|
|
|||
|
|
@ -59,7 +59,7 @@ Most online office suites do not support E2EE, meaning the cloud provider has ac
|
|||
|
||||
In general, we define collaboration platforms as full-fledged suites which could reasonably act as a replacement to collaboration platforms like Google Drive.
|
||||
|
||||
- Open-source.
|
||||
- Open source.
|
||||
- Makes files accessible via WebDAV unless it is impossible due to E2EE.
|
||||
- Has sync clients for Linux, macOS, and Windows.
|
||||
- Supports document and spreadsheet editing.
|
||||
|
|
@ -161,11 +161,10 @@ In general, we define office suites as applications which could reasonably act a
|
|||
|
||||
#### Minimum Requirements
|
||||
|
||||
- Must be open-source.
|
||||
- Must be open source.
|
||||
- Must implement "zero-trust" end-to-end encryption.
|
||||
- Must support password-protected files.
|
||||
|
||||
|
||||
#### Best-Case
|
||||
|
||||
Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page.
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ You can consult OpenWrt's [table of hardware](https://openwrt.org/toh/start) to
|
|||
|
||||
{ align=right }
|
||||
|
||||
**OPNsense** is an open source, FreeBSD-based firewall and routing platform which incorporates many advanced features such as traffic shaping, load balancing, and VPN capabilities, with many more features available in the form of plugins. OPNsense is commonly deployed as a perimeter firewall, router, wireless access point, DHCP server, DNS server, and VPN endpoint.
|
||||
**OPNsense** is an open-source, FreeBSD-based firewall and routing platform which incorporates many advanced features such as traffic shaping, load balancing, and VPN capabilities, with many more features available in the form of plugins. OPNsense is commonly deployed as a perimeter firewall, router, wireless access point, DHCP server, DNS server, and VPN endpoint.
|
||||
|
||||
[:octicons-home-16: Homepage](https://opnsense.org/){ .md-button .md-button--primary }
|
||||
[:octicons-info-16:](https://docs.opnsense.org/index.html){ .card-link title=Documentation}
|
||||
|
|
|
|||
|
|
@ -133,7 +133,7 @@ IVPN has undergone a [no-logging audit from Cure53](https://cure53.de/audit-repo
|
|||
|
||||
#### :material-check:{ .pg-green } Open-Source Clients
|
||||
|
||||
As of February 2020 [IVPN applications are now open-source](https://www.ivpn.net/blog/ivpn-applications-are-now-open-source). Source code can be obtained from their [GitHub organization](https://github.com/ivpn).
|
||||
As of February 2020 [IVPN applications are now open source](https://www.ivpn.net/blog/ivpn-applications-are-now-open-source). Source code can be obtained from their [GitHub organization](https://github.com/ivpn).
|
||||
|
||||
#### :material-check:{ .pg-green } Accepts Cash and Monero
|
||||
|
||||
|
|
@ -248,7 +248,7 @@ We require all our recommended VPN providers to provide OpenVPN configuration fi
|
|||
- Support for strong protocols such as WireGuard & OpenVPN.
|
||||
- Killswitch built in to clients.
|
||||
- Multihop support. Multihopping is important to keep data private in case of a single node compromise.
|
||||
- If VPN clients are provided, they should be [open-source](https://en.wikipedia.org/wiki/Open_source), like the VPN software they generally have built into them. We believe that [source code](https://en.wikipedia.org/wiki/Source_code) availability provides greater transparency about what your device is actually doing.
|
||||
- If VPN clients are provided, they should be [open source](https://en.wikipedia.org/wiki/Open_source), like the VPN software they generally have built into them. We believe that [source code](https://en.wikipedia.org/wiki/Source_code) availability provides greater transparency about what your device is actually doing.
|
||||
|
||||
**Best Case:**
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user