mirror of
https://github.com/simplex-chat/simplex-chat.git
synced 2026-05-25 04:15:31 +00:00
improve the links of blogs
This commit is contained in:
M Sarmad Qadeer
@@ -16,8 +16,8 @@ The only way to do it before this version was by deleting the contact, now you c
|
||||
|
||||
<img src="./images/20220524-clear-chat1.png" width="240"> <img src="./images/20220524-clear-chat2.png" width="240">
|
||||
|
||||
See [v1 announcement](./20220112-simplex-chat-v1-released.md) for information on how SimpleX protects the security of the messages.
|
||||
See [v1 announcement](https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220112-simplex-chat-v1-released.md) for information on how SimpleX protects the security of the messages.
|
||||
|
||||
See [v2 announcement](./20220511-simplex-chat-v2-images-files.md) for more information about SimpleX platform and how it works.
|
||||
See [v2 announcement](https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220511-simplex-chat-v2-images-files.md) for more information about SimpleX platform and how it works.
|
||||
|
||||
Read about SimpleX design in [whitepaper](https://github.com/simplex-chat/simplexmq/blob/master/protocol/overview-tjr.md).
|
||||
|
||||
@@ -8,7 +8,7 @@ date: 2022-06-04
|
||||
|
||||
**Published:** June 4, 2022
|
||||
|
||||
See [v2 announcement](./20220511-simplex-chat-v2-images-files.md) for more information about SimpleX platform and how it protects your privacy by avoiding user identities of any kind in its design - SimpleX, unlike any other messaging platfom, has no identity keys or any numbers that identify its users.
|
||||
See [v2 announcement](https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220511-simplex-chat-v2-images-files.md) for more information about SimpleX platform and how it protects your privacy by avoiding user identities of any kind in its design - SimpleX, unlike any other messaging platfom, has no identity keys or any numbers that identify its users.
|
||||
|
||||
## New Privacy and Security settings in version 2.2
|
||||
|
||||
@@ -47,6 +47,6 @@ You can discover additional features we are currently testing in Experimental Fe
|
||||
|
||||
## More information
|
||||
|
||||
See [v1 announcement](./20220112-simplex-chat-v1-released.md) for information on how SimpleX protects the security of the messages.
|
||||
See [v1 announcement](https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220112-simplex-chat-v1-released.md) for information on how SimpleX protects the security of the messages.
|
||||
|
||||
Read about SimpleX design in [whitepaper](https://github.com/simplex-chat/simplexmq/blob/master/protocol/overview-tjr.md).
|
||||
|
||||
+6
-6
@@ -9,13 +9,13 @@ date: 2022-07-11
|
||||
|
||||
## New in version 3
|
||||
|
||||
- [instant notifications for iOS](#instant-notifications-for-ios)
|
||||
- [database export and import](#database-export-and-import)
|
||||
- [protocol privacy and performance improvements](#protocol-privacy-and-performance-improvements)
|
||||
- [instant notifications for iOS](https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.md#instant-notifications-for-ios)
|
||||
- [database export and import](https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.md#database-export-and-import)
|
||||
- [protocol privacy and performance improvements](https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.md#protocol-privacy-and-performance-improvements)
|
||||
|
||||
### Instant notifications for iOS
|
||||
|
||||
I wrote previously about [our design for iOS notifications](./20220404-simplex-chat-instant-notifications.md#problem---users-expect-to-be-instantly-notified-when-messages-arrive) - this is now released. The app will offer to migrate the database when updated, and then you need to choose notifications mode – instant or periodic push notifications, or previously available periodic background refresh that does not use push notifications.
|
||||
I wrote previously about [our design for iOS notifications](https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220404-simplex-chat-instant-notifications.md#problem---users-expect-to-be-instantly-notified-when-messages-arrive) - this is now released. The app will offer to migrate the database when updated, and then you need to choose notifications mode – instant or periodic push notifications, or previously available periodic background refresh that does not use push notifications.
|
||||
|
||||
To deliver the notifications to iOS devices we use our notification server, as there is a single private key that Apple issues for the app. This server has minimal amount of information about your chat activity:
|
||||
|
||||
@@ -58,7 +58,7 @@ Adding push notifications for iOS required SimpleX Messaging Protocol changes. W
|
||||
|
||||
We also improved the protocol flow for establishing bidirectional connection between two users - it is substantially faster now, consuming much less network traffic and battery. It improves the time it takes to connect to your contacts and to start delivering images and files.
|
||||
|
||||
All these changes did not affect backward compatibility - if your contact has the previous version of the client, or you are connecting to a previous version of the server, the previous version of the protocol will be used - SimpleX has independent version negotiation in 4 protocol layers [since v1](./20220112-simplex-chat-v1-released.md#stable-protocol-implementation), allowing us to evolve the protocols without any disruption to the users.
|
||||
All these changes did not affect backward compatibility - if your contact has the previous version of the client, or you are connecting to a previous version of the server, the previous version of the protocol will be used - SimpleX has independent version negotiation in 4 protocol layers [since v1](https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220112-simplex-chat-v1-released.md#stable-protocol-implementation), allowing us to evolve the protocols without any disruption to the users.
|
||||
|
||||
## SimpleX platform
|
||||
|
||||
@@ -78,7 +78,7 @@ SimpleX platform avoids these risks by not having any user identity in its desig
|
||||
|
||||
Many people asked: _if SimpleX has no user identifiers, how can it deliver messages?_
|
||||
|
||||
I wrote about it in [v2 release announcement](./20220511-simplex-chat-v2-images-files.md) and you can get more information about SimpleX platform objectives and technical design in [the whitepaper](https://github.com/simplex-chat/simplexmq/blob/master/protocol/overview-tjr.md).
|
||||
I wrote about it in [v2 release announcement](https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220511-simplex-chat-v2-images-files.md) and you can get more information about SimpleX platform objectives and technical design in [the whitepaper](https://github.com/simplex-chat/simplexmq/blob/master/protocol/overview-tjr.md).
|
||||
|
||||
## We ask you to help us pay for 3rd party security audit
|
||||
|
||||
|
||||
@@ -9,10 +9,10 @@ date: 2022-07-23
|
||||
|
||||
## What's new
|
||||
|
||||
- terminal app: [access to messaging servers via SOCKS5 proxy](#terminall-app-access-to-messaging-servers-via-socks5-proxy--tor) (e.g., Tor).
|
||||
- mobile apps: [join and leave chat groups](#mobile-apps-join-and-leave-chat-groups).
|
||||
- [optimized battery and traffic usage - up to 90x reduction!](#optimized-battery-and-traffic-usage---up-to-90x-reduction).
|
||||
- [two docker configurations for self-hosted SMP servers](#docker-configuration-for-self-hosted-smp-servers).
|
||||
- terminal app: [access to messaging servers via SOCKS5 proxy](https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.md#terminall-app-access-to-messaging-servers-via-socks5-proxy--tor) (e.g., Tor).
|
||||
- mobile apps: [join and leave chat groups](https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.md#mobile-apps-join-and-leave-chat-groups).
|
||||
- [optimized battery and traffic usage - up to 90x reduction!](https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.md#optimized-battery-and-traffic-usage---up-to-90x-reduction).
|
||||
- [two docker configurations for self-hosted SMP servers](https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.md#docker-configuration-for-self-hosted-smp-servers).
|
||||
|
||||
### Terminall app: access to messaging servers via SOCKS5 proxy / Tor
|
||||
|
||||
@@ -22,7 +22,7 @@ While SMP protocol is focussed on protecting application-level meta-data by usin
|
||||
|
||||
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.
|
||||
|
||||
To access SimpleX servers via Tor you need to install Tor proxy and run simplex-chat with `-x` option. See [terminal app docs](../docs/CLI.md#access-messaging-servers-via-tor-beta) for more information.
|
||||
To access SimpleX servers via Tor you need to install Tor proxy and run simplex-chat with `-x` option. See [terminal app docs](https://github.com/simplex-chat/simplex-chat/blob/stable/docs/CLI.md#access-messaging-servers-via-tor-beta) for more information.
|
||||
|
||||
As this is a beta release, to install it you need to use this command:
|
||||
|
||||
@@ -69,11 +69,11 @@ We are building a new platform for distributed Internet applications where priva
|
||||
|
||||
### The first (and the only?) messaging platform without user identifiers of any kind - 100% private by design!
|
||||
|
||||
To protect identities of users and their connections, instead of user identifiers visible to the servers and/or the network (that are used by all other messaging platforms), SimpleX Chat uses [pairwise identifiers](https://csrc.nist.gov/glossary/term/Pairwise_Pseudonymous_Identifier) of connections between the users – there are two queues in each connection, each queue having 2 different identifiers to send and to receive the messages. It increases the number of used identifiers to the square of the number of users, making it more difficult (or impossible) to determine who is talking to whom. I [wrote previously](./20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.md#why-having-users-identifiers-is-bad-for-the-users) why it is bad for the users' privacy to have any identifiers, even random numbers, associated with their profiles.
|
||||
To protect identities of users and their connections, instead of user identifiers visible to the servers and/or the network (that are used by all other messaging platforms), SimpleX Chat uses [pairwise identifiers](https://csrc.nist.gov/glossary/term/Pairwise_Pseudonymous_Identifier) of connections between the users – there are two queues in each connection, each queue having 2 different identifiers to send and to receive the messages. It increases the number of used identifiers to the square of the number of users, making it more difficult (or impossible) to determine who is talking to whom. I [wrote previously](https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.md#why-having-users-identifiers-is-bad-for-the-users) why it is bad for the users' privacy to have any identifiers, even random numbers, associated with their profiles.
|
||||
|
||||
### If SimpleX has no user identifiers, how can it deliver messages?
|
||||
|
||||
I wrote about it in [v2 release announcement](./20220511-simplex-chat-v2-images-files.md) and you can get more information about SimpleX platform objectives and technical design in [the whitepaper](https://github.com/simplex-chat/simplexmq/blob/master/protocol/overview-tjr.md).
|
||||
I wrote about it in [v2 release announcement](https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220511-simplex-chat-v2-images-files.md) and you can get more information about SimpleX platform objectives and technical design in [the whitepaper](https://github.com/simplex-chat/simplexmq/blob/master/protocol/overview-tjr.md).
|
||||
|
||||
### Privacy: technical details and limitations
|
||||
|
||||
@@ -94,7 +94,7 @@ What we plan to add soon to further improve privacy and security:
|
||||
- using Tor v3 hidden service addresses for messaging servers.
|
||||
- passphrase-based local database encryption.
|
||||
|
||||
SimpleX Chat [README page](../README.md#privacy-technical-details-and-limitations) has more details about it.
|
||||
SimpleX Chat [README page](https://github.com/simplex-chat/simplex-chat/blob/stable/README.md#privacy-technical-details-and-limitations) has more details about it.
|
||||
|
||||
## We ask you to help us pay for 3rd party security audit
|
||||
|
||||
|
||||
Reference in New Issue
Block a user