on master help sign in
another link, old urbit-help fix
commit80fe499bd60158c5197189ee4da92297033b7e1a authorsyzygyzer <jon@tlon.io> dateMon 23 Nov 2020, 16:49 (6 years ago) parentb234cb6
1 file changed+8−2
tutorials/guide-to-breaches.md+8−2
tutorials/guide-to-breaches.md+8−2
@@ -12,12 +12,18 @@ There are two kinds of breaches: **personal breaches** and **network breaches**.
1212
1313Ships on the Ames 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 on the network has forgotten about it.
1414
15−Personal breaches often fix connectivity issues, but should only be used as a last resort. Before performing a personal breach, look at alternative fixes in the [Ship Troubleshooting](../ship-troubleshooting) guide. Also reach out for help in `~/~dopzod/urbit-help`, or, failing that, in the `#ship-starting-support` channel in our [Discord server](https://discord.gg/n9xhMdz) to see if there is another option.
15+Personal breaches often fix connectivity issues, but should only be used as a
16+last resort. Before performing a personal breach, look at alternative fixes in
17+the [Ship Troubleshooting](../ship-troubleshooting) guide. Also reach out for
18+help in the Help channel in the Urbit Community group
19+`~bitbet-bolbel/urbit-community`, or, failing that, in the
20+`#ship-starting-support` channel in our [Discord
21+server](https://discord.gg/n9xhMdz) to see if there is another option.
1622
1723There are two types of personal breaches - one where your Ethereum ownership address
1824remains the same, and one where you are switching to a new Ethereum ownership
1925address. We make the emphasis about the Ethereum _ownership_ address as
20−changing your [proxies](@/glossary/proxies.md) does not require a breach.
26+changing your [proxies](@/docs/glossary/proxies.md) does not require a breach.
2127
2228If you will be keeping the same Ethereum ownership address and would like to perform a
2329personal breach, follow the steps below.