Follow rename of DAVdroid to DAVx⁵

diff --git a/content/new-address-book.md b/content/new-address-book.md
index 38c25178d8202c1ca82b11b5877d08cdc807f6c7..05d553b3601a6885f092155914077bc93c88694f 100644 (file)
--- a/content/new-address-book.md
+++ b/content/new-address-book.md
@@ -139,25 +139,27 @@ Encrypt](https://letsencrypt.org/), reloaded again, and off we go.
 
 ### Android integration
 
-I installed [DAVdroid](https://davdroid.bitfire.at/) from the Play Store: it
-cost a few pounds, but I was OK with that since it's GPLv3 and I'm happy to
-help fund free software.  I created two accounts, one for my existing Google
+I installed [DAVx⁵](https://www.davx5.com/) from the Play Store: it cost a
+few pounds, but I was OK with that since it's GPLv3 and I'm happy to help
+fund free software.  I created two accounts, one for my existing Google
 Contacts database (and in fact calendaring as well, although I don't intend
 to switch over to self-hosting that just yet), and one for the new Xandikos
-instance.  The [Google
-setup](https://davdroid.bitfire.at/configuration/google/) was a bit fiddly
-because I have two-step verification turned on so I had to create an
-app-specific password.  The Xandikos setup was straightforward: base URL,
-username, password, and done.
+instance.  The Google setup was a bit fiddly because I have two-step
+verification turned on so I had to create an app-specific password.  The
+Xandikos setup was straightforward: base URL, username, password, and done.
 
 Since I didn't completely trust the new setup yet, I followed what seemed
-like the most robust option from the [DAVdroid contacts syncing
-documentation](https://davdroid.bitfire.at/faq/entry/existing-contacts-are-not-synced/),
+like the most robust option from the [DAVx⁵ contacts syncing
+documentation](https://www.davx5.com/faq/existing-contacts-are-not-synced),
 and used the stock contacts app to export my Google Contacts account to a
-`.vcf` file and then import that into the appropriate DAVdroid account
-(which showed up automatically).  This seemed straightforward and everything
-got pushed to Xandikos.  There are some weird delays in syncing contacts
-that I don't entirely understand, but it all seems to get there in the end.
+`.vcf` file and then import that into the appropriate DAVx⁵ account (which
+showed up automatically).  This seemed straightforward and everything got
+pushed to Xandikos.  There are some weird delays in syncing contacts that I
+don't entirely understand, but it all seems to get there in the end.
+
+*2019-06-13: Followed rename of DAVdroid to DAVx⁵.  At the moment Google
+Contacts support seems to be flaky at best; see the [DAVx⁵
+forums](https://forums.bitfire.at/tags/google) for tips.*
 
 ### mutt integration