mirror of
https://github.com/simplex-chat/simplex-chat.git
synced 2025-06-28 12:19:54 +00:00
ui, site: v6.2 whats new, business (#5309)
* ui, site: v6.2 whats new, business * icon Co-authored-by: spaced4ndy <8711996+spaced4ndy@users.noreply.github.com> * business Co-authored-by: spaced4ndy <8711996+spaced4ndy@users.noreply.github.com> * typo Co-authored-by: spaced4ndy <8711996+spaced4ndy@users.noreply.github.com> * typo Co-authored-by: spaced4ndy <8711996+spaced4ndy@users.noreply.github.com> --------- Co-authored-by: spaced4ndy <8711996+spaced4ndy@users.noreply.github.com>
This commit is contained in:
Evgeny
GitHub
parent
247d12fa40
commit
a182cf5730
9 changed files with 150 additions and 12 deletions
|
|
@ -520,14 +520,19 @@ private let versionDescriptions: [VersionDescription] = [
|
|||
]
|
||||
),
|
||||
VersionDescription(
|
||||
version: "v6.2 (beta.1)",
|
||||
post: URL(string: "https://simplex.chat/blog/20241125-servers-operated-by-flux-true-privacy-and-decentralization-for-all-users.html"),
|
||||
version: "v6.2",
|
||||
post: URL(string: "https://simplex.chat/blog/20241210-simplex-network-v6-2-servers-by-flux-business-chats.html"),
|
||||
features: [
|
||||
.view(FeatureView(
|
||||
icon: nil,
|
||||
title: "Network decentralization",
|
||||
view: { NewOperatorsView() }
|
||||
)),
|
||||
.feature(Description(
|
||||
icon: "briefcase",
|
||||
title: "Business chats",
|
||||
description: "Privacy for your customers."
|
||||
)),
|
||||
.feature(Description(
|
||||
icon: "bolt",
|
||||
title: "More reliable notifications",
|
||||
|
|
|
|||
|
|
@ -724,8 +724,8 @@ private val versionDescriptions: List<VersionDescription> = listOf(
|
|||
),
|
||||
),
|
||||
VersionDescription(
|
||||
version = "v6.2-beta.1",
|
||||
post = "https://simplex.chat/blog/20241125-servers-operated-by-flux-true-privacy-and-decentralization-for-all-users.html",
|
||||
version = "v6.2",
|
||||
post = "https://simplex.chat/blog/20241210-simplex-network-v6-2-servers-by-flux-business-chats.html",
|
||||
features = listOf(
|
||||
VersionFeature.FeatureView(
|
||||
icon = null,
|
||||
|
|
@ -749,6 +749,11 @@ private val versionDescriptions: List<VersionDescription> = listOf(
|
|||
}
|
||||
}
|
||||
),
|
||||
VersionFeature.FeatureDescription(
|
||||
icon = MR.images.ic_work,
|
||||
titleId = MR.strings.v6_2_business_chats,
|
||||
descrId = MR.strings.v6_2_business_chats_descr
|
||||
),
|
||||
VersionFeature.FeatureDescription(
|
||||
icon = MR.images.ic_chat,
|
||||
titleId = MR.strings.v6_2_improved_chat_navigation,
|
||||
|
|
|
|||
|
|
@ -2175,6 +2175,8 @@
|
|||
<string name="v6_2_network_decentralization_enable_flux_reason">for better metadata privacy.</string>
|
||||
<string name="v6_2_improved_chat_navigation">Improved chat navigation</string>
|
||||
<string name="v6_2_improved_chat_navigation_descr">- Open chat on the first unread message.\n- Jump to quoted messages.</string>
|
||||
<string name="v6_2_business_chats">Business chats</string>
|
||||
<string name="v6_2_business_chats_descr">Privacy for your customers.</string>
|
||||
<string name="view_updated_conditions">View updated conditions</string>
|
||||
|
||||
<!-- CustomTimePicker -->
|
||||
|
|
|
|||
|
|
@ -0,0 +1,60 @@
|
|||
---
|
||||
layout: layouts/article.html
|
||||
title: "Servers operated by Flux - true privacy and decentralization for all users"
|
||||
date: 2024-12-10
|
||||
# previewBody: blog_previews/20241210.html
|
||||
# image: images/simplexonflux.png
|
||||
# imageWide: true
|
||||
draft: true
|
||||
permalink: "/blog/20241210-simplex-network-v6-2-servers-by-flux-business-chats.html"
|
||||
---
|
||||
|
||||
# SimpleX network: preset servers operated by Flux, business chats and more with v6.2 of the apps
|
||||
|
||||
**Will be published:** Dec 10, 2024
|
||||
|
||||
This is a placeholder page for the upcoming v6.2 release announcement!
|
||||
|
||||
- Preset servers are now operated by two companies - SimpleX Chat and Flux. Read [this post](./20241125-servers-operated-by-flux-true-privacy-and-decentralization-for-all-users.md).
|
||||
- Business chats to provide support from your business to users of SimpleX network. Read [this page](../docs/BUSINESS.md).
|
||||
- and more!
|
||||
|
||||
## SimpleX network
|
||||
|
||||
Some links to answer the most common questions:
|
||||
|
||||
[How can SimpleX deliver messages without user identifiers](./20220511-simplex-chat-v2-images-files.md#the-first-messaging-platform-without-user-identifiers).
|
||||
|
||||
[What are the risks to have identifiers assigned to the users](./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).
|
||||
|
||||
[Technical details and limitations](https://github.com/simplex-chat/simplex-chat#privacy-and-security-technical-details-and-limitations).
|
||||
|
||||
[Frequently asked questions](../docs/FAQ.md).
|
||||
|
||||
Please also see our [website](https://simplex.chat).
|
||||
|
||||
## Please support us with your donations
|
||||
|
||||
Huge *thank you* to everybody who donated to SimpleX Chat!
|
||||
|
||||
Prioritizing users privacy and security, and also raising the investment, would have been impossible without your support and donations.
|
||||
|
||||
Also, funding the work to transition the protocols to non-profit governance model would not have been possible without the donations we received from the users.
|
||||
|
||||
Our pledge to our users is that SimpleX protocols are and will remain open, and in public domain, so anybody can build the future implementations of the clients and the servers. We are building SimpleX platform based on the same principles as email and web, but much more private and secure.
|
||||
|
||||
Your donations help us raise more funds — any amount, even the price of the cup of coffee, makes a big difference for us.
|
||||
|
||||
See [this section](https://github.com/simplex-chat/simplex-chat/#please-support-us-with-your-donations) for the ways to donate.
|
||||
|
||||
Thank you,
|
||||
|
||||
Evgeny
|
||||
|
||||
SimpleX Chat founder
|
||||
|
||||
[1] You can also to self-host your own SimpleX servers on [Flux decentralized cloud](https://home.runonflux.io/apps/marketplace?q=simplex).
|
||||
|
||||
[2] The probability of connection being de-anonymized and the number of random server choices follow this equation: `(1 - s ^ 2) ^ n = 1 - p`, where `s` is the share of attacker-controlled servers in the network, `n` is the number of random choices of entry and exit nodes for the circuit, and `p` is the probability of both entry and exit nodes, and the connection privacy being compromised. Substituting `0.02` (2%) for `s`, `0.5` (50%) for `p`, and solving this equation for `n` we obtain that `1733` random circuits have 50% probability of privacy being compromised.
|
||||
|
||||
Also see [this presentation about Tor](https://ritter.vg/p/tor-v1.6.pdf), specifically the approximate calculations on page 76, and also [Tor project post](https://blog.torproject.org/announcing-vanguards-add-onion-services/) about the changes that made attack on hidden service anonymity harder, but still viable in case the it is used for a long time.
|
||||
60
docs/BUSINESS.md
Executable file
60
docs/BUSINESS.md
Executable file
|
|
@ -0,0 +1,60 @@
|
|||
---
|
||||
title: SimpleX for business
|
||||
revision: 03.12.2024
|
||||
---
|
||||
|
||||
# Using SimpleX Chat in business
|
||||
|
||||
SimpleX Chat (aka SimpleX) is a decentralized communication network that provides private and secure messaging. Its users are rapidly growing, and providing customer services via SimpleX can offer you a unique opportunity to engage people who are the most enthusiastic about trying out early stage technology products and services.
|
||||
|
||||
This document aims to help you make the best use of SimpleX Chat if you choose to engage with its users.
|
||||
|
||||
## Communcate with customers via business address
|
||||
|
||||
In the same way you can connect to our "SimpleX Chat team" profile via the app, you can provide the address for your existing and prospective customers:
|
||||
- to buy your product and services via chat,
|
||||
- to ask any questions, make suggestions and provide feedback,
|
||||
- to discover more information about your business.
|
||||
|
||||
Customers who value privacy and security, and want to engage with you without sharing any personal data and minimizing any metadata that is shared with you, will be really happy to use this communication channel.
|
||||
|
||||
From v6.2 SimpleX Chat supports business addresses. Their design allows you to accept requests from multiple customers, with the app creating a new business chat with each of them.
|
||||
|
||||
Business chats operate in a way similar to dedicated customer support systems by combining features of direct conversations and groups, and the only widely used messenger that provides such functionality is WeChat with Chinese business accounts.
|
||||
|
||||
When a customer connects to your business via the business contact address, a new conversation is created. Similarly to how direct chats work, the customer will see the name and logo of your business, and you will see the name and avatar of your customer.
|
||||
|
||||
But the business conversation works as a group - once the customer is connected, other people from the business can be added to the conversation, and the customers will see who are they talking with. This can be used to transfer business conversation to another person, or for escalation - in the same way as with the dedicated support systems.
|
||||
|
||||
SimpleX Chat profile with the business address can be used in one of these ways:
|
||||
- for small teams it can be managed by one person running the app on their desktop computer, who would respond to customer questions and manually add to the conversation other people in the business, as required.
|
||||
- if you have multiple support agents, you can run business profile in CLI client running in cloud VM or on any machine with high speed Internet (see Technical advice below), and they can connect to this client from desktop client, in turns. This is how we use our business profile ourselves, even though it requires some configuration. You can manage 100s of thousands of connected customers in this way.
|
||||
- For larger teams, it would be appropriate to have this profile managed by chat bot that can reply to some simple questions, and to add support agents, based on their availability and the questions asked. These scenarios would require programming a chat bot, and we are currently working to simplify it.
|
||||
|
||||
In any case, it is important that the client application remains running and connected to the Internet for you to receive support requests.
|
||||
|
||||
## Customer broadcasts
|
||||
|
||||
While currently supported only via CLI clients (or via chat console in desktop and mobile clients), it can be used to broadcast important announcements to all connected customers. We will be adding this feature to desktop clients soon. We use it to broadcast release updates to a very large number of users who are connected to our own support profile.
|
||||
|
||||
## Community groups and promotion in group directory
|
||||
|
||||
In addition to providing support to clients individually, you can create a community group, and promote it via our experimental and growing [directory of public groups](./DIRECTORY.md). Community groups require ongoing moderation.
|
||||
|
||||
## Limitations
|
||||
|
||||
With all advantages in privacy and security of e2e encryption in SimpleX Chat, there are some important limitations:
|
||||
- **protecting your data from loss is your responsibility**. This is the price of privacy - if you lose your device, or database passphrase, there is absolutely no way we would be able to support you to recover access. There are ways to work around these limitations.
|
||||
- **you cannot access the same profile from multiple devices**. For all communication products it's a basic expectation, and yet there is not a single one that delivered it without some very serious privacy and security compromises. Better solutions are possible, and we will be implementing it, but reasonably secure approach is much more complex to implement than what is affordable at the current stage. You can access mobile or CLI profile from desktop, and the latter allows to use one profile by multiple people in turns, as we explain below.
|
||||
- **your owner role in the groups cannot be restored if you lose the device**. The solution is to create owner profiles on multiple devices for all your important groups. This way if you lose device or data for one of profiles, you won't lose control of the group, and you can add a new one. Think about it as about keys to your cryptowallet.
|
||||
- **current groups are highly experimental**. Message delivery can be delayed or fail in some cases, lists of members can be out of sync. There are approaches to make them more stable we use for our groups.
|
||||
|
||||
## Technical advice
|
||||
|
||||
### Running SimpleX Chat in the cloud
|
||||
|
||||
### Using remote profiles via Desktop app
|
||||
|
||||
## Organizations using SimpleX Chat for customer service, support and sales
|
||||
|
||||
Please let us know if you use SimpleX Chat to communicate with your customers and want to be included in this list.
|
||||
|
|
@ -238,6 +238,7 @@
|
|||
"docs-dropdown-10": "Transparency",
|
||||
"docs-dropdown-11": "FAQ",
|
||||
"docs-dropdown-12": "Security",
|
||||
"docs-dropdown-14": "SimpleX for business",
|
||||
"newer-version-of-eng-msg": "There is a newer version of this page in English.",
|
||||
"click-to-see": "Click to see",
|
||||
"menu": "Menu",
|
||||
|
|
|
|||
|
|
@ -5,12 +5,12 @@
|
|||
"url": "/docs/simplex.html"
|
||||
},
|
||||
{
|
||||
"title": "docs-dropdown-8",
|
||||
"url": "/docs/directory.html"
|
||||
"title": "docs-dropdown-14",
|
||||
"url": "/docs/business.html"
|
||||
},
|
||||
{
|
||||
"title": "docs-dropdown-2",
|
||||
"url": "/docs/android.html"
|
||||
"title": "docs-dropdown-8",
|
||||
"url": "/docs/directory.html"
|
||||
},
|
||||
{
|
||||
"title": "docs-dropdown-3",
|
||||
|
|
@ -28,10 +28,6 @@
|
|||
"title": "docs-dropdown-6",
|
||||
"url": "/docs/webrtc.html"
|
||||
},
|
||||
{
|
||||
"title": "docs-dropdown-7",
|
||||
"url": "/docs/translations.html"
|
||||
},
|
||||
{
|
||||
"title": "docs-dropdown-9",
|
||||
"url": "/downloads/"
|
||||
|
|
|
|||
|
|
@ -18,6 +18,7 @@
|
|||
"menu": "Reference",
|
||||
"data": [
|
||||
"SIMPLEX.md",
|
||||
"BUSINESS.md",
|
||||
"DIRECTORY.md",
|
||||
"ANDROID.md",
|
||||
"CLI.md",
|
||||
|
|
|
|||
|
|
@ -80,6 +80,14 @@
|
|||
|
||||
<hr class=" h-[1px] w-full dark:opacity-[0.1]">
|
||||
|
||||
<li><a href="/docs/translations.html"
|
||||
class="lg:px-[20px] flex items-center gap-1"
|
||||
>{{ "docs-dropdown-7" | i18n({}, lang ) | safe }}
|
||||
</a></li>
|
||||
<li><a href="/docs/android.html"
|
||||
class="lg:px-[20px] flex items-center gap-1"
|
||||
>{{ "docs-dropdown-2" | i18n({}, lang ) | safe }}
|
||||
</a></li>
|
||||
<li><a href="https://github.com/simplex-chat/simplex-chat/blob/stable/apps/simplex-bot-advanced/Main.hs"
|
||||
target="_blank" class="lg:px-[20px] flex items-center gap-1"
|
||||
>{{ "chat-bot-example" | i18n({}, lang ) | safe }}
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue