on master help sign in
add tldr section and new information (#516)

* add tldr section and new information * remove unnecessary words

commit6c9a6a11b222875468b34c81e8b40c0efe85532e authorJosh Lehman <jlehman@fastmail.com> dateMon 30 Nov 2020, 22:07 (6 years ago) parent6ed7550
1 file changed+24−2
content/breach.md+24−2
content/breach.md+24−2
@@ -3,9 +3,25 @@ title = "~2020.12 Network Breach"
33template = "page_indiced.html"
44+++
55
6+## TL;DR
7+
8+A network breach is coming up on ~2020.12.7.
9+
10+Unlike past breaches, this one comes with a tool to export and reimport all of your data so that you don't lose anything; we call it `flagday`.
11+
12+This tool and documentation on its usage will be made available on or before ~2020.12.4.
13+
14+This document will be kept up-to-date throughout the process, and updates will be issued via Twitter [here](https://twitter.com/tloncorporation/).
15+
16+*If you are self-hosting your ship, following these instructions is mandatory in order to communicate with the rest of the network.*
17+
618## When is the next breach?
719
8−The next breach is scheduled for early December.
20+The target date is Monday December 7th, but it may happen on Tuesday December 8th.
21+
22+## How do I get updates about what's going on throughout the process?
23+
24+We'll be adding new information to this document as soon as there's anything to share. Updates will be broadcasted via Twitter [here](https://twitter.com/tloncorporation/) as well.
925
1026## What is a “network breach”?
1127
@@ -36,7 +52,9 @@ There are no Ethereum transactions necessary for this breach.
3652
3753## I’m self-hosted—what do I need to do?
3854
39−Simply use the `flagday` tool that we will provide. It will perform all the relevant actions on your behalf, as well as exporting and reimporting your data.
55+Simply use the `flagday` tool that will be provided. It will perform all the relevant actions on your behalf, as well as exporting and reimporting your data.
56+
57+`flagday` will become available for use on or before ~2020.12.4.
4058
4159If you want to do the work manually, follow these steps:
42601. Download your [keyfile from Bridge](https://urbit.org/using/install/#keyfile).
@@ -64,3 +82,7 @@ We are optimistic that this will be our last breach, as all future updates to th
6482## What happens if I don’t breach?
6583
6684Your Urbit will fall out of communication with the rest of the Urbit network which has performed the breach. This means that updates (OTAs) will no longer process and you won’t be able to communicate with anyone else on the network.
85+
86+## How do I get help if I need it?
87+
88+If you're in a tight spot or confused, reach out to us at support@urbit.org.