blog, docs: typo fixes

This commit is contained in:
Matthías Ragnarsson 2024-08-26 21:37:08 +00:00
parent 8a6bf05773
commit 6a6fc486e1
5 changed files with 6 additions and 6 deletions

View file

@ -23,7 +23,7 @@ permalink: "/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.html"
<img src="./images/20220723-tor.jpg" width="480">
While SMP protocol is focussed on protecting application-level meta-data by using pairwise connection identifiers instead of user identifiers (that are used by all other messaging platforms), there are scenarios when it is important for the users to protect their IP addresses from the servers - quite a few users have been somewhat disappointed that we didn't add it earlier.
While SMP protocol is focused on protecting application-level meta-data by using pairwise connection identifiers instead of user identifiers (that are used by all other messaging platforms), there are scenarios when it is important for the users to protect their IP addresses from the servers - quite a few users have been somewhat disappointed that we didn't add it earlier.
This release of terminal app supports accessing the servers via Tor, but the servers themselves are still available on their usual addresses. We are planning to add .onion addresses (v3 hidden service) to all messaging servers we provide, and the users who self-host the servers will also be able to have dual servers addresses - so that one party in the conversation can access the servers via .onion address without necessarily requiring that the other party uses Tor as well.

View file

@ -46,7 +46,7 @@ Other group improvements we will add soon:
<img src="./images/20220808-tor1.png" width="330"> &nbsp; <img src="./images/20220808-tor2.png" width="330">
SimpleX protocols are focussed on protecting application-level meta-data they don't have any user identifiers used by all other messaging platforms, instead relying on pairwise connection identifiers.
SimpleX protocols are focused on protecting application-level meta-data they don't have any user identifiers used by all other messaging platforms, instead relying on pairwise connection identifiers.
But there are scenarios when users need to protect their IP addresses from the servers and any network observers this is best done by using Tor to access any network services.

View file

@ -28,7 +28,7 @@ Also, we added Persian interface language to the Android and desktop apps, thank
<img src="./images/simplex-explained.svg" width="37%" class="float-right">
SimpleX network design has always been focussed on protecting user identity on the messaging protocol level - there is no user profile identifiers of any kind in the protocol design, not even random numbers or cryptographic keys.
SimpleX network design has always been focused on protecting user identity on the messaging protocol level - there is no user profile identifiers of any kind in the protocol design, not even random numbers or cryptographic keys.
Until this release though, SimpleX network had no built-in protection of user transport identities - IP addresses. As previously the users could only choose which messaging relays to use to receive messages, these relays could observe the IP addresses of the senders, and if these relays were controlled by the recipients, the recipients themselves could observe them too - either by modifying server code or simply by tracking all connecting IP addresses.
@ -49,7 +49,7 @@ Many SimpleX network design ideas are borrowed from Tor network design:
So why didn't we just embed Tor into the messaging clients to provide IP address protection?
We believe that Tor may be the wrong solution for some users for one of the reasons:
We believe that Tor may be the wrong solution for some users for one of these reasons:
- much higher latency, error rate and resource usage.
- people who want to use Tor are better served by specialized apps, such as [Orbot](https://guardianproject.info/apps/org.torproject.android/).
- Tor usage is restricted in some networks, so it would require complex configuration in the app UI.

View file

@ -49,7 +49,7 @@ You are an expert in language models, databases and Haskell:
- passionate about privacy, security and communications.
- interested to make contributions to SimpleX Chat open-source project in your free time before we hire you, as an extended test.
- **Exceptionally pragmatic, very fast and customer-focussed**:
- **Exceptionally pragmatic, very fast and customer-focused**:
- care about the customers (aka users) and about the product we build much more than about the code quality, technology stack, etc.
- believe that the simplest solution is the best.
- 2-3x faster than the most competent people you worked with.

View file

@ -6,7 +6,7 @@ revision: 31.07.2023
## Overview
XFTP is a new file transfer protocol focussed on meta-data protection - it is based on the same principles as SimpleX Messaging Protocol used in SimpleX Chat messenger:
XFTP is a new file transfer protocol focused on meta-data protection - it is based on the same principles as SimpleX Messaging Protocol used in SimpleX Chat messenger:
- asynchronous file delivery - the sender does not need to be online for file to be received, it is stored on XFTP relays for a limited time (currently, it is 48 hours) or until deleted by the sender.
- padded e2e encryption of file content.