From 2206176a2c84fd8ce2bc6767d2a0a551f43fddee Mon Sep 17 00:00:00 2001 From: Hattie <82660400+HattieTavares@users.noreply.github.com> Date: Thu, 29 Sep 2022 12:39:38 -0400 Subject: [PATCH 01/12] Update onboarding.md Small grammar changes for better readability. --- content/docs/sdk/flutter/onboarding.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/sdk/flutter/onboarding.md b/content/docs/sdk/flutter/onboarding.md index 4fc17df0b..6a38bde5a 100644 --- a/content/docs/sdk/flutter/onboarding.md +++ b/content/docs/sdk/flutter/onboarding.md @@ -11,7 +11,7 @@ order: 4 # Ordering of the steps ### Overview -The atPlatform uses secret keys for authenticating an atSign as cryptographically secure replacement for usernames and passwords.To make developers life easier atPlatform offers [at_onboarding_flutter](https://pub.dev/packages/at_onboarding_flutter) package which handles secure management of secret keys.If you are developing a new atPlatform app, we recommend that you use [at_app](https://pub.dev/packages/at_app) which can create atPlatform app template that already contains onboarding in it. +The atPlatform uses secret keys for authenticating an atSign as a cryptographically secure replacement for usernames and passwords. To make developers' lives easier, atPlatform offers the [at_onboarding_flutter](https://pub.dev/packages/at_onboarding_flutter) package, which handles secure management of secret keys. If you are developing a new atPlatform app, we recommend that you use [at_app](https://pub.dev/packages/at_app), which can create an atPlatform app template that already contains onboarding in it. ## Usage From 6873aad5b8d9aa06d74718e957cba118792852a4 Mon Sep 17 00:00:00 2001 From: Arindam Nath Date: Sat, 1 Oct 2022 03:01:23 +0530 Subject: [PATCH 02/12] some changes to docs --- content/docs/start/flutter.md | 2 +- content/docs/start/java.md | 6 +++--- content/docs/tutorials/at-dude/_5_dude_service.md | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/content/docs/start/flutter.md b/content/docs/start/flutter.md index e84f4e884..49c9bf9a2 100644 --- a/content/docs/start/flutter.md +++ b/content/docs/start/flutter.md @@ -36,7 +36,7 @@ See Flutter's instructions on getting the Flutter environment setup: #### 4. Create an atPlatform app -Create an atPlatform app by using [at_app](https://github.com/atsign-foundation/at_app) +Create an atPlatform app by using [at_app](https://github.com/atsign-foundation/at_app): 1. `at_app create ` 2. `cd ` 3. `flutter run` diff --git a/content/docs/start/java.md b/content/docs/start/java.md index c319c2495..657cb54a6 100644 --- a/content/docs/start/java.md +++ b/content/docs/start/java.md @@ -3,11 +3,11 @@ layout: list title: "Java" # The title (ON THE PAGE) lead: | # The lead below the title (ON THE PAGE) - Get Started with Java Development on the atPlatform + Get Started with Java Development on the atPlatform. description: | # SEO Description of the page (Shows in google and atsign.dev search) - Get started with Java Development on the atPlatform + Get started with Java Development on the atPlatform. draft: false # Change this to "true" to hide the page toc: true # Change this to "false" to hide the table of contents @@ -31,7 +31,7 @@ Next step is to install [maven](https://maven.apache.org/install.html) and add i Fork our `at_java` repository Create a new directory on your local machine where you want the java client source code to live. Change directory (cd) into this directory and git clone your fork. -Git clone: `git clone .` so that the source code is on your local machine. +Git clone: `git clone ` so that the source code is on your local machine. ### 4. Build `at_java/at_client` diff --git a/content/docs/tutorials/at-dude/_5_dude_service.md b/content/docs/tutorials/at-dude/_5_dude_service.md index 1b6ccec14..5e93954bd 100644 --- a/content/docs/tutorials/at-dude/_5_dude_service.md +++ b/content/docs/tutorials/at-dude/_5_dude_service.md @@ -19,7 +19,7 @@ order: # Ordering of the steps | [Local Notification imports](#imports-1) | | [Properties of LocalNotificationService](#properties-of-localnotificationservice) | -They are three service classes in the dude app, they are `NavigationServices()`, `DudeServices()` and `LocalNotificationServices()`. In this code lab we will explore the properties of these classes. +There are three service classes in the dude app, they are `NavigationServices()`, `DudeServices()` and `LocalNotificationServices()`. In this code lab we will explore the properties of these classes. #### DudeService From 0427302b686bb9358fdc968b7d780c4a4f8277ae Mon Sep 17 00:00:00 2001 From: Arindam Nath Date: Sat, 1 Oct 2022 03:09:09 +0530 Subject: [PATCH 03/12] some changes to docs 2 --- content/docs/sdk/flutter/at_client_manager.md | 4 ++-- content/docs/tutorials/at-dude/_3_navigation_service.md | 2 +- .../docs/tutorials/at-dude/_4_local_notification_services.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/content/docs/sdk/flutter/at_client_manager.md b/content/docs/sdk/flutter/at_client_manager.md index 7c516949a..d47ec155f 100644 --- a/content/docs/sdk/flutter/at_client_manager.md +++ b/content/docs/sdk/flutter/at_client_manager.md @@ -27,7 +27,7 @@ After Initializing you are ready to make calls of client methods and services. T ### Usage -To access CRUD methods, +To access CRUD methods : ``` AtClient atClient = atClientManager.atClient; ``` @@ -36,7 +36,7 @@ AtClient atClient = atClientManager.atClient; Notification service gives back a stream of notifications from the server to the subscribing client. -To access NotificationService methods +To access NotificationService methods : ``` NotificationService notificationService = atClientManager.notificationService; diff --git a/content/docs/tutorials/at-dude/_3_navigation_service.md b/content/docs/tutorials/at-dude/_3_navigation_service.md index 2a9505607..3cc963f2d 100644 --- a/content/docs/tutorials/at-dude/_3_navigation_service.md +++ b/content/docs/tutorials/at-dude/_3_navigation_service.md @@ -19,7 +19,7 @@ order: # Ordering of the steps | [Properties of LocalNotificationService](#properties-of-localnotificationservice) | -They are three service classes in the dude app, they are `NavigationServices()`, `DudeServices()` and `LocalNotificationServices()`. In this code lab we will explore the properties of these classes. +There are three service classes in the dude app, they are `NavigationServices()`, `DudeServices()` and `LocalNotificationServices()`. In this code lab we will explore the properties of these classes. #### NavigationService diff --git a/content/docs/tutorials/at-dude/_4_local_notification_services.md b/content/docs/tutorials/at-dude/_4_local_notification_services.md index 7a077b733..645632df9 100644 --- a/content/docs/tutorials/at-dude/_4_local_notification_services.md +++ b/content/docs/tutorials/at-dude/_4_local_notification_services.md @@ -19,7 +19,7 @@ order: # Ordering of the steps | [Properties of LocalNotificationService](#properties-of-localnotificationservice) | -They are three service classes in the dude app, they are `NavigationServices()`, `DudeServices()` and `LocalNotificationServices()`. In this code lab we will explore the properties of these classes. +There are three service classes in the dude app, they are `NavigationServices()`, `DudeServices()` and `LocalNotificationServices()`. In this code lab we will explore the properties of these classes. #### LocalNotificationService From 9160f479835088c641bb3bfa9449bc622a2406fb Mon Sep 17 00:00:00 2001 From: Roanna Victorio Date: Sat, 1 Oct 2022 23:41:40 -0700 Subject: [PATCH 04/12] improve grammar in sdk/flutter/introduction/ For consistent style with the rest of the document, changed "an object" to "object". Replaced "for developing app developers", with clearer phrase "for atPlatform developers". For issue: Docs Grammar and Typos #158 --- content/docs/sdk/flutter/introduction.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/docs/sdk/flutter/introduction.md b/content/docs/sdk/flutter/introduction.md index c917e47c8..c16b9ff5b 100644 --- a/content/docs/sdk/flutter/introduction.md +++ b/content/docs/sdk/flutter/introduction.md @@ -19,7 +19,7 @@ If you haven't already, we recommend you head to [Get Started Flutter Developmen The following is covered in this codelab: -- **AtClientManager** - an object with various services such as Client, NotificationService, and SyncService. +- **AtClientManager** - object with various services such as Client, NotificationService, and SyncService. - **AtClientPreference** - object used to configure preferences in your atPlatform application such as the namespace, storage path for the hive database, or maximum data size. - **Onboarding** - process of activating an atSign and/or authenticating the atsign into its secondary server. - **Key Basics** - learn how keys are stored in the secondary server and what key metadata is. @@ -30,7 +30,7 @@ Our atPlatform has a lot to offer for Dart/Flutter developers. - [at_widgets](https://github.com/atsign-foundation/at_widgets) - Flutter widgets for using various aspects of the atPlatform - [at_demos](https://github.com/atsign-foundation/at_demos) - collection of demo applications to help you on your atPlatform journey -- [at_app](https://github.com/atsign-foundation/at_app) - command-line utility for developing app developers +- [at_app](https://github.com/atsign-foundation/at_app) - command-line utility for atPlatform developers - [at_tools](https://github.com/atsign-foundation/at_tools) - other atPlatform tools (at_cli, at_cram, at_pkam,...) Explore our GitHub page [atsign-foundation](https://github.com/atsign-foundation) to see more of our amazing projects and tools. From d9fb396b35b1452cf7ab72ff4572c7d0005de5b3 Mon Sep 17 00:00:00 2001 From: Roanna Victorio Date: Sun, 2 Oct 2022 01:16:27 -0700 Subject: [PATCH 05/12] docs: improve grammar in sdk/flutter/at_client_preference/ **- What I did** For consistent style, replace "Default" with "Defaults". Capitalize Regex. For consistent style, replace "The number" with "Number" For issue: Docs Grammar and Typos #158 **- How I did it** Edited the markdown file **- How to verify it** Changes will appear at https://docs.atsign.com/sdk/flutter/at_client_preference/ **- Description for the changelog** docs: improve grammar in sdk/flutter/at_client_preference/ --- content/docs/sdk/flutter/at_client_preference.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/docs/sdk/flutter/at_client_preference.md b/content/docs/sdk/flutter/at_client_preference.md index 2092fe9de..83a65a494 100644 --- a/content/docs/sdk/flutter/at_client_preference.md +++ b/content/docs/sdk/flutter/at_client_preference.md @@ -25,12 +25,12 @@ AtClientPreference is used to configure the preferences of an atPlatform applica | rootDomain | Domain of the root server. Defaults to root.atsign.com | | rootPort | Port of the root server. Defaults to 64 | | syncIntervalMins | Frequency of sync tasks to run in minutes. Defaults to 10 minutes. | -| outboundConnectionTimeout | Idle time in milliseconds of connection to secondary server. Default to 10 minutes. | +| outboundConnectionTimeout | Idle time in milliseconds of connection to secondary server. Defaults to 10 minutes. | | maxDataSize | Maximum data size a secondary can store. Temporary solution. Have to fetch this from the server using stats verb. | | downloadPath | Default path to download stream files | -| syncRegex | regex to perform sync | +| syncRegex | Regex to perform sync | | syncBatchSize | Number of keys to batch for sync to secondary server | -| syncPageLimit | The number of keys to pull from cloud secondary to local secondary in a single call. | +| syncPageLimit | Number of keys to pull from cloud secondary to local secondary in a single call. | For Local device paths we recommend the path_provider package. From 73e22443dd9e1530462f018b6778323b679458b9 Mon Sep 17 00:00:00 2001 From: Harshavardhan Bajoria <62978274+HVbajoria@users.noreply.github.com> Date: Sun, 2 Oct 2022 23:16:15 +0530 Subject: [PATCH 06/12] Update notification.md --- content/docs/reference/notification.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/content/docs/reference/notification.md b/content/docs/reference/notification.md index 43dd3c6d4..23afe3a00 100644 --- a/content/docs/reference/notification.md +++ b/content/docs/reference/notification.md @@ -7,7 +7,7 @@ lead: | # The lead below the title (ON THE PAGE) description: | # SEO Description of the page (Shows in google and atsign.dev search) - Definition of Notificaton in the atPlatform, the notify verb in the atProtocol, and Definition of Monitor in the atPlatform + Definition of Notification in the atPlatform, the notify verb in the atProtocol, and Definition of Monitor in the atPlatform draft: false # Change this to "true" to hide the page toc: true # Change this to "true" to show the table of contents @@ -18,16 +18,16 @@ weight: 211 # For single pages, lower is first. ### Notification -Notification enables developers to **notify** another atSign of some data event. It is used to **notify** another atSign that data from your secondary server was modified (updated or deleted). Some example notifications include: the key's value updated, the key was deleted, the key's metadata changed, and more. +Notification enables developers to **notify** another atSign of some data event. It is used to **notify** another atSign that data from your secondary server was modified (updated or deleted). Some example notifications include: the key's value is updated, the key is deleted, the key's metadata changed, and more. -The atPlatform takes care of all of the heavy lifting with encryption, verb building, transmission, etc,. +The atPlatform takes care of all of the heavy lifting with encryption, verb building, transmission, etc. Read more [here](https://blog.atsign.dev/part-1-the-notify-verb-cko97bv8f00l5gws13umb0nvz). ### Monitor Monitor uses notifications. -Monitor is used to receive notifications from the other secondary server. +The monitor is used to receive notifications from the other secondary server. Read more {{< a href="https://github.com/atsign-foundation/at_client_sdk/blob/trunk/at_client/lib/src/manager/monitor.dart" target="_blank" rel="canonical" >}}here{{}}. @@ -134,4 +134,4 @@ Read more ## Related Resources -{{< card/breadcrumb link="/atplatform/specification/" first="Protocol Specification" >}} \ No newline at end of file +{{< card/breadcrumb link="/atplatform/specification/" first="Protocol Specification" >}} From 3539b00e5dac7f065bcc82832db04848abdbc6c4 Mon Sep 17 00:00:00 2001 From: Harshavardhan Bajoria <62978274+HVbajoria@users.noreply.github.com> Date: Sun, 2 Oct 2022 23:17:49 +0530 Subject: [PATCH 07/12] Update polymorphism.md --- content/docs/reference/polymorphism.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/docs/reference/polymorphism.md b/content/docs/reference/polymorphism.md index 29640ad46..3c796cf33 100644 --- a/content/docs/reference/polymorphism.md +++ b/content/docs/reference/polymorphism.md @@ -16,17 +16,17 @@ weight: 204 # For single pages, lower is first. ## Definition -The condition of occuring in several different forms. +The condition of occurring in several different forms. -Polymorphism on the atPlatform is the ability to share different data depending on the context of who’s asking. atPlatform applications enable you to setup multiple personas for different areas of your life. When you share data with someone else, the value of that data may be different depending on the person receiving that data. This is true for both sides, you may ask for data from different sources and get a different answer for each one. +Polymorphism on the atPlatform is the ability to share different data depending on the context of who’s asking. atPlatform applications enable you to set up multiple personas for different areas of your life. When you share data with someone else, the value of that data may be different depending on the person receiving that data. This is true for both sides, you may ask for data from different sources and get a different answer for each one. ## Polymorphic Data -The [@buzz app](https://atsign.com/apps/buzz/) is a stellar example of polymorphic data on the atPlatform. @buzz is like your contacts application, but with a twist. Rather than manually entering details for all of your contacts, and having to deal with duplicate contact entries from trying to sync all of your contacts over the cloud, you simply connect with someone through their atSign. In @buzz, they can create and share a specific persona with you. For example, I might want to share my work phone and email with colleagues, but my personal phone and a different email with friends. I can set up separate “work” and “friends” personas with each set of information, so when I connect with someone new, all I have to do is share the correct persona with that person. Better yet, if I want to share multiple personas, I can do that too! If I move or change my email address, I can update my information in the app, and my contacts have access to the new information and don’t have to make any edits themselves. +The [@buzz app](https://atsign.com/apps/buzz/) is a stellar example of polymorphic data on the atPlatform. @buzz is like your contacts application, but with a twist. Rather than manually entering details for all of your contacts, and having to deal with duplicate contact entries from trying to sync all of your contacts over the cloud, you simply connect with someone through their atSign. In @buzz, they can create and share a specific persona with you. For example, I might want to share my work phone and email with colleagues, but my phone and a different email with friends. I can set up separate “work” and “friends” personas with each set of information, so when I connect with someone new, all I have to do is share the correct persona with that person. Better yet, if I want to share multiple personas, I can do that too! If I move or change my email address, I can update my information in the app, and my contacts have access to the new information and don’t have to make any edits themselves. ## Example -@alice’s work persona may have a different value for email than her personal persona. When she shares her email to her colleagues, they will receive her work email, however when she shares it to her friends and family, they will see her personal email. As she updates the data in each of her personas, the changes will be reflected to each person that she has shared the data with. +@alice’s work persona may have a different value for email than her persona. When she shares her email with her colleagues, they will receive her work email, however, when she shares it with her friends and family, they will see her personal email. As she updates the data in each of her personas, the changes will be reflected in each person that she has shared the data with. To learn more about polymorphism see [this article post](https://medium.com/flutter-community/building-flutter-apps-with-no-backend-9715b764a81e#67d3) From 26279495b7d414eca5ed34f05b5d38ec97d7a768 Mon Sep 17 00:00:00 2001 From: Harshavardhan Bajoria <62978274+HVbajoria@users.noreply.github.com> Date: Sun, 2 Oct 2022 23:19:23 +0530 Subject: [PATCH 08/12] Update synchronization.md --- content/docs/reference/synchronization.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/content/docs/reference/synchronization.md b/content/docs/reference/synchronization.md index 5dcb5bfff..c1ce82303 100644 --- a/content/docs/reference/synchronization.md +++ b/content/docs/reference/synchronization.md @@ -16,18 +16,18 @@ weight: 210 # For single pages, lower is first. ## Definition -On at the atProtocol, your data is encrypted with your self [encryption](/reference/encryption) key and stored on your device. Periodically, this data is copied securely over to a dedicated cloud server which only you can decrypt and read since you are the only one who owns the private key. No one else, including **Atsign** can read your data. This process is known as synchronization. +At the atProtocol, your data is encrypted with your self [encryption](/reference/encryption) key and stored on your device. Periodically, this data is copied securely over to a dedicated cloud server which only you can decrypt and read since you are the only one who owns the private key. No one else, including **Atsign** can read your data. This process is known as synchronization. ## atPlatform -First we need to touch up on what local & remote secondaries are: +First, we need to touch up on what local & remote secondaries are: -1. **Remote Secondary**: A microservice with a DNS address which makes it addressable, provides a backup of your data in case of loss on the phone, provides a joining place to synchronize data if you have more than one device. -2. **Local Secondary**: A copy of data that allows for fast interactivity and offline support. Every activated atSign gets their own remote secondary which runs on Atsign's servers. All of your data is signed and encrypted, so Atsign cannot see it. +1. **Remote Secondary**: A microservice with a DNS address that makes it addressable, provides a backup of your data in case of loss on the phone, and provides a joining place to synchronize data if you have more than one device. +2. **Local Secondary**: A copy of data that allows for fast interactivity and offline support. Every activated atSign gets its remote secondary which runs on Atsign's servers. All of your data is signed and encrypted, so Atsign cannot see it. Synchronization aims to keep both local and remote secondaries with the same data. If by any chance the device is lost, then the data can be retrieved from the remote secondary: -There are two main scenarios that require synchronization. The first occurs when your device is offline. Updates are saved to your device but not synced to the server. Once the device goes online, those saved updates get synced to the server. The second scenario is when you have multiple devices: one device is offline while the other is online. Updates from the online device will get synced to the server periodically. However the offline device will not be able to pull the changes until it is back online. +Two main scenarios require synchronization. The first occurs when your device is offline. Updates are saved to your device but not synced to the server. Once the device goes online, those saved updates get synced to the server. The second scenario is when you have multiple devices: one device is offline while the other is online. Updates from the online device will get synced to the server periodically. However, the offline device will not be able to pull the changes until it is back online. _To read more about synchronization and how it works check out this [Medium Article](https://Atsigncompany.medium.com/the-protocol-synchronization-77b00ca5341b) we made._ From 8f407c9426d43864967ddcedb8d9132bef069d18 Mon Sep 17 00:00:00 2001 From: Harshavardhan Bajoria <62978274+HVbajoria@users.noreply.github.com> Date: Sun, 2 Oct 2022 23:21:02 +0530 Subject: [PATCH 09/12] Update pricing-and-costs.md --- content/docs/reference/pricing-and-costs.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/docs/reference/pricing-and-costs.md b/content/docs/reference/pricing-and-costs.md index 2568679fe..4500862e1 100644 --- a/content/docs/reference/pricing-and-costs.md +++ b/content/docs/reference/pricing-and-costs.md @@ -16,7 +16,7 @@ weight: 201 # For single pages, lower is first. ## Introduction -Since the atPlatform is fully open sourced and everyone can contribute, there is no cost for developers! When you make an app on the atPlatform, people that use your apps will not have to pay any fees for infrastructure or storage! The way that **Atsign** generates revenue is by using our special identifier which is known as an atSign. An atSign can come in many flavors with corresponding prices ranging from free, $10, $100, $1000, $5000. If you opt-in for the vanity atSign the prices increase as the atSign of your liking decreases in length and complexity. For each paid atSign you own, there is a $10 annual renewal fee. This fee does not apply to the free atSigns. What makes atSigns so awesome is that if your app is the first one someone pairs an atSign with, after buying their atSign, we pay you commission on that. Yep, you don't pay us, we pay you. +Since the atPlatform is fully open-sourced and everyone can contribute, there is no cost for developers! When you make an app on the atPlatform, people that use your apps will not have to pay any fees for infrastructure or storage! The way that **Atsign** generates revenue is by using our special identifier which is known as an atSign. An atSign can come in many flavors with corresponding prices ranging from free, $10, $100, $1000, $5000. If you opt-in for the vanity atSign the prices increase as the atSign of your liking decreases in length and complexity. For each paid atSign you own, there is a $10 annual renewal fee. This fee does not apply to the free atSigns. What makes atSigns so awesome is that if your app is the first one someone pairs an atSign with, after buying their atSign, we pay you to commission on that. Yep, you don't pay us, we pay you. ## Video @@ -49,7 +49,7 @@ For paid atSigns the options are listed below: ## Free atSigns -For a FREE atSign there exists an atSign generator which creates a new set of atSigns at random for you to choose from! You are given two options: the first option requires you to add some pre-generated atSigns while the second option lets you generate an atSign based on your interests using _super-secret_ mode. Let's say you like music and sports, the atSign generator would perform its magic and dish out: +For a FREE atSign there exists an atSign generator that creates a new set of atSigns at random for you to choose from! You are given two options: the first option requires you to add some pre-generated atSigns while the second option lets you generate an atSign based on your interests using _super-secret_ mode. Let's say you like music and sports, the atSign generator would perform its magic and dish out: * melodic74 * canopy22wild From 4f8493aac0f183a9f04a814555d6aaec832ee6ac Mon Sep 17 00:00:00 2001 From: Harshavardhan Bajoria <62978274+HVbajoria@users.noreply.github.com> Date: Mon, 3 Oct 2022 16:27:40 +0530 Subject: [PATCH 10/12] Update pricing-and-costs.md --- content/docs/reference/pricing-and-costs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/reference/pricing-and-costs.md b/content/docs/reference/pricing-and-costs.md index 4500862e1..2968eea02 100644 --- a/content/docs/reference/pricing-and-costs.md +++ b/content/docs/reference/pricing-and-costs.md @@ -16,7 +16,7 @@ weight: 201 # For single pages, lower is first. ## Introduction -Since the atPlatform is fully open-sourced and everyone can contribute, there is no cost for developers! When you make an app on the atPlatform, people that use your apps will not have to pay any fees for infrastructure or storage! The way that **Atsign** generates revenue is by using our special identifier which is known as an atSign. An atSign can come in many flavors with corresponding prices ranging from free, $10, $100, $1000, $5000. If you opt-in for the vanity atSign the prices increase as the atSign of your liking decreases in length and complexity. For each paid atSign you own, there is a $10 annual renewal fee. This fee does not apply to the free atSigns. What makes atSigns so awesome is that if your app is the first one someone pairs an atSign with, after buying their atSign, we pay you to commission on that. Yep, you don't pay us, we pay you. +Since the atPlatform is fully open-sourced and everyone can contribute, there is no cost for developers! When you make an app on the atPlatform, people that use your apps will not have to pay any fees for infrastructure or storage! The way that **Atsign** generates revenue is by using our special identifier which is known as an atSign. An atSign can come in many flavors with corresponding prices ranging from free, $10, $100, $1000, $5000. If you opt-in for the vanity atSign the prices increase as the atSign of your liking decreases in length and complexity. For each paid atSign you own, there is a $10 annual renewal fee. This fee does not apply to the free atSigns. What makes atSigns so awesome is that if your app is the first one someone pairs an atSign with, after buying their atSign, we pay you commission on that. Yep, you don't pay us, we pay you. ## Video From 3af16b2026be5a6506d933061902f894c974bb83 Mon Sep 17 00:00:00 2001 From: Harshavardhan Bajoria <62978274+HVbajoria@users.noreply.github.com> Date: Mon, 3 Oct 2022 16:29:51 +0530 Subject: [PATCH 11/12] Update synchronization.md --- content/docs/reference/synchronization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/reference/synchronization.md b/content/docs/reference/synchronization.md index c1ce82303..a4602c9a7 100644 --- a/content/docs/reference/synchronization.md +++ b/content/docs/reference/synchronization.md @@ -16,7 +16,7 @@ weight: 210 # For single pages, lower is first. ## Definition -At the atProtocol, your data is encrypted with your self [encryption](/reference/encryption) key and stored on your device. Periodically, this data is copied securely over to a dedicated cloud server which only you can decrypt and read since you are the only one who owns the private key. No one else, including **Atsign** can read your data. This process is known as synchronization. +At atProtocol, your data is encrypted with your self [encryption](/reference/encryption) key and stored on your device. Periodically, this data is copied securely over to a dedicated cloud server which only you can decrypt and read since you are the only one who owns the private key. No one else, including **Atsign** can read your data. This process is known as synchronization. ## atPlatform From c164392ccde5685c190713d7d6cc901e694455c2 Mon Sep 17 00:00:00 2001 From: Harshavardhan Bajoria <62978274+HVbajoria@users.noreply.github.com> Date: Mon, 3 Oct 2022 18:19:11 +0530 Subject: [PATCH 12/12] Update synchronization.md --- content/docs/reference/synchronization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/reference/synchronization.md b/content/docs/reference/synchronization.md index a4602c9a7..75c046bc2 100644 --- a/content/docs/reference/synchronization.md +++ b/content/docs/reference/synchronization.md @@ -16,7 +16,7 @@ weight: 210 # For single pages, lower is first. ## Definition -At atProtocol, your data is encrypted with your self [encryption](/reference/encryption) key and stored on your device. Periodically, this data is copied securely over to a dedicated cloud server which only you can decrypt and read since you are the only one who owns the private key. No one else, including **Atsign** can read your data. This process is known as synchronization. +With atProtocol, your data is encrypted with your self [encryption](/reference/encryption) key and stored on your device. Periodically, this data is copied securely over to a dedicated cloud server which only you can decrypt and read since you are the only one who owns the private key. No one else, including **Atsign** can read your data. This process is known as synchronization. ## atPlatform