on master help sign in
update guide to breaches (#746)

Adds warning about personal breaches

commit9a9f49610ab367f7186b49bcedf7188ca63abc6f authorrmariani <robert@tlon.io> dateTue 3 Dec 2019, 16:24 (7 years ago) parent3944727
1 file changed+3−1
tutorials/guide-to-breaches.md+3−1
tutorials/guide-to-breaches.md+3−1
@@ -12,7 +12,9 @@ There are two kinds of breaches: **personal breaches** and **network breaches**.
1212
1313Ships on the Arvo network sometimes need to reset their continuity. A personal breach is when an individual ship announces to the network: "I forgot who I am, let's start over from scratch." That is, it clears its own event log and sends an announcement to the network, asking all ships that have communicated with it to reset its networking information in their state. This makes it as though the ship was just started for the first time again, since everyone has network has forgotten about it.
1414
15−Personal breaches often fix connectivity issues, but should only be used as a last resort. To perform a personal breach, follow the steps below.
15+Personal breaches often fix connectivity issues, but should only be used as a last resort. Before performing a personal breach, reach out for help in the #ship-starting-support channel in our [Discord server](https://discord.gg/n9xhMdz) to see if there is another option, or look at alternative fixes in the [Ship Troubleshooting](../ship-troubleshooting) guide.
16+
17+To perform a personal breach, follow the steps below.
1618
1719- Go to [bridge.urbit.org](https://bridge.urbit.org) and log into your identity.
1820- Go to the `Admin` section. Then go to `Edit Permisions`, then `Networking Keys`.