on master help sign in
be more explicit about beta-quality flagday
commit2a29a174966338ec780177d031ceab9e25e67cd3 authorJosh Lehman <josh@urbit.org> dateMon 7 Dec 2020, 16:29 (6 years ago) parent4c9d1c2
1 file changed+5−4
content/breach.md+5−4
content/breach.md+5−4
@@ -5,11 +5,11 @@ template = "page_indiced.html"
55
66## TL;DR
77
8−*Last updated ~2020.12.6*
8+*Last updated ~2020.12.7*
99
1010A network breach is coming up on Tuesday, ~2020.12.8.
1111
12−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` (details below).
12+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`. Currently a test version of `flagday` and details about its usage can be found below.
1313
1414This document will be kept up-to-date throughout the process, and updates will be issued via Twitter [here](https://twitter.com/tloncorporation/).
1515
@@ -52,9 +52,10 @@ There are no Ethereum transactions necessary for this breach.
5252
5353## I’m self-hosted—what do I need to do?
5454
55−**Simply use the `flagday` tool that we have provided**. It will perform all the
55+**Simply use the `flagday` tool that we will provide**. It will perform all the
5656relevant actions on your behalf, as well as exporting and reimporting your data.
57−You can find the `flagday` script
57+
58+You can find a test version of the `flagday` script
5859[here](https://gist.github.com/philipcmonk/8e3d095b9545069237c759cd9aad32c2).
5960Usage instructions are provided in the comments at the top of the file. **It's
6061not necessary to run `flagday` until after the breach**. Furthermore, your ship