Skip to content

Commit

Permalink
Deemphasize 'Cloud' usage in the Sync page (#255)
Browse files Browse the repository at this point in the history
I'm trying to deemphasize the term 'cloud' here because I think it
implies that it's going somewhere unknown. It should be clear that it's
going to a users installed server, and nowhere else. Pikapods and
fly.io, I think would be classic examples where where the term 'cloud'
makes sense but wouldn't make sense if someone had it installed on a
local PC, NAS or Raspberry Pi.

I left a lot of the document alone further down because it seems like
there may be error messages within the app that use the term 'cloud'.

Maybe add an additional explainer in the section that explains the cloud
file?

**Came up in a discord support issue.
  • Loading branch information
shall0pass authored Oct 9, 2023
1 parent 5ccd7a7 commit 46092de
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions docs/getting-started/sync.md
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# Syncing Across Devices

Actual is a different kind of app. Instead of storing all of your data on the internet by default, it stores all of your data locally. That means it works regardless of your network connection, and you always have direct access to your data.
Actual is a different kind of app. It stores all of your data on your installed Actual server by default AND it stores all of your data on your local device. That means it works regardless of your network connection, and you always have direct access to your data. Your data never goes to any external servers that you don't choose. It's your data, and you're in control.

We don't want to throw away the internet though. It's too useful. When your data is stored in the cloud, you can access it from any device easily, and you never have to worry about losing your data in case you drop your laptop or phone into a lake.
We don't want to throw away the internet though. It's too useful. You can set up your server to access it through a VPN or through the wider internet. The choice is yours. You can access it from any device easily, and you never have to worry about losing your data in case you drop your laptop or phone into a lake.

That's why we automatically sync all of your data to your selected server in the background. You get the best of both worlds: all data is local by default, but if internet is available, your data is seamlessly backed up and synced to all other devices. This is the opposite of most apps which heavily rely on the internet to be available.

Expand All @@ -20,7 +20,7 @@ In addition to the requirement to enter your password before the Actual server w

End-to-end encryption offers the ability for you to generate a key based on a password and encrypt it so that hosted services can't read the data. Before your data leaves your device, it is encrypted using keys only you have.

This guarantees that only you will ever have access to your data. This is optional and using it requires you to enter a password whenever downloading cloud files (this only needs to be done once per device). The password you enter can be different from the main server password.
This guarantees that only you will ever have access to your data. This is optional and using it requires you to enter a password whenever downloading [cloud files](#this-file-is-not-a-cloud-file) (this only needs to be done once per device). The password you enter can be different from the main server password.

Data on your local device is still unencrypted. We recommend full disk encryption if you are interested in local encryption.

Expand Down

1 comment on commit 46092de

@github-actions
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@check-spelling-bot Report

🔴 Please review

See the 📜action log or 📝 job summary for details.

❌ Errors Count
❌ dictionary-not-found 4

See ❌ Event descriptions for more information.

Available 📚 dictionaries could cover words (expected and unrecognized) not in the 📘 dictionary

This includes both expected items (37) from .github/actions/spelling/expect.txt and unrecognized words (0)

Dictionary Entries Covers Uniquely
cspell:typescript/dict/typescript.txt 1098 6 3
cspell:npm/dict/npm.txt 302 5 3
cspell:fullstack/dict/fullstack.txt 419 4 3
cspell:html/dict/html.txt 2060 7
cspell:css/dict/css.txt 263 6 1

Consider adding them (in .github/workflows/spelling.yml) for uses: check-spelling/check-spelling@main in its with:

      with:
        extra_dictionaries:
          cspell:typescript/dict/typescript.txt
          cspell:npm/dict/npm.txt
          cspell:fullstack/dict/fullstack.txt
          cspell:html/dict/html.txt
          cspell:css/dict/css.txt

To stop checking additional dictionaries, add (in .github/workflows/spelling.yml) for uses: check-spelling/check-spelling@main in its with:

check_extra_dictionaries: ''

Please sign in to comment.