[nongnu] elpa/mastodon 5a6671dbf1 37/76: readme encrypted tokens / epa/plstore key vars

[ELPA Syncer]

branch: elpa/mastodon
commit 5a6671dbf1dfc2d522de63d383ff3c95f453cd30
Author: marty hiatt <martianhiatus@disroot.org>
Commit: marty hiatt <martianhiatus@disroot.org>

    readme encrypted tokens / epa/plstore key vars
---
 README.org | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/README.org b/README.org
index 9cfdcee94a..6c54bacfaf 100644
--- a/README.org
+++ b/README.org
@@ -127,17 +127,23 @@ follow the steps again.
 **** encrypted access tokens (from 1.2.0)
 
 By default, user access tokens are now stored in the user's auth source
-file (typically =~/.authinfo.gpg=). When you first update to 1.2.0, or if
-you encounter issues due to old credentials, call
-=(mastodon-forget-all-logins)= and then authenticate again. If you don't
-want this behaviour, set =mastodon-auth-use-auth-source= to nil. Entries
-will be stored in =mastodon-client--token-file= instead.
+file (typically =~/.authinfo.gpg=, check the value of =auth-sources=). When
+you first update to 2.0.0, or if you encounter issues due to old
+credentials, call =(mastodon-forget-all-logins)= and then authenticate
+again. If you don't want this behaviour, set =mastodon-auth-use-auth-source=
+to nil. Entries will be stored encrypted in =mastodon-client--token-file= 
instead.
 
 And if for some reason you reauthenticate, you'll need to either remove the
 entry in your auth sources file, or manually update the token in it after
 doing so, as mastodon.el is unable to reliably update (or even remove)
 entires.
 
+Finally, if you find you're asked for your key passphrase too often while
+authenticating, consider setting =epa-file-encrypt-to= (for auth-source
+encryption) and =plstore-encrypt-to= (for plstore encryption) to your
+preferred key ID.
+
+
 *** Timelines
 
 =M-x mastodon=