on master help sign in
docs: add software dist FAQ
6b89714James Acklin
content/using/os/dist-faq.mdnew file+81
@@ -0,0 +1,81 @@
1++++
2+title = "Software Distribution FAQ"
3+template = "doc.html"
4+weight = 9
5++++
6+
7+This document concerns the September 2021 release of the software distribution OTA, codenamed "Grid." It is current as of 2021-09-29 at 7:45 AM PST.
8+
9+## Changes
10+
11+**How do I get back to Landscape to see my DMs?**
12+
13+What was formerly called "Landscape" is now the Groups app. You can access DMs and groups via the "Groups" tile.
14+
15+**Where did my app tiles in Landscape go?**
16+
17+For apps ported to software distribution, tiles will be shown in the home screen.
18+
19+If you're already running non-Tlon apps, those apps will stop running, but the state will be preserved.
20+
21+If the developer provides a version of the app over software distribution and you install it, the new app will migrate the old state.
22+
23+**What's the base hash?**
24+
25+After this OTA there is a base hash _per app desk_:
26+
27+| Software | Desk | Base Hash |
28+| ------------ | ---------- | --------- |
29+| Arvo/OS | %base | TK |
30+| Home Screen | %garden | TK |
31+| Groups | %landscape | TK |
32+| BTC Wallet | %bitcoin | TK |
33+| Web Terminal | %webterm | TK |
34+
35+**How do I see the base hashes for my ship?**
36+
37+The `+trouble` generator is now an alias for `+vats`.
38+Running either one will show the base hashes for every installed app desk.
39+
40+Clicking the settings icon on the top left of the home screen provides an 'About' choice.
41+Selecting this will bring up an app info widget for the system app, which will show the base hash of the `%garden` desk.
42+
43+Selecting the menu icon in the top right of an application tile provides an 'App Info' choice.
44+Selecting this will bring up an app info widget for the selected application, which will show its desk name and the base hash of its desk.
45+
46+Groups (formerly Landscape) will no longer show a base hash within the app.
47+
48+## Troubleshooting
49+
50+**The OTA is taking a long time.**
51+
52+This is expected and unfortunately unavoidable.
53+Your ship will be unresponsive for several minutes, possibly up to half an hour.
54+This is normal.
55+
56+Technical note: this is because OTAs are run as a single Arvo event which must compile the OTA and run migrations.
57+
58+**I saw crashes and stack traces during the OTA.**
59+
60+Some stack traces are expected. The `%goad` and `%publish` apps will not be present in the OTA,
61+and Clay will complain about not being able to build them. You will also see some Clay `read-at-aeon-fail` errors.
62+
63+If the OTA succeeds it will not end on a stack trace and you will have a working dojo prompt.
64+
65+**I haven't gotten the OTA yet and I can't post in some groups or DM some people.**
66+
67+This OTA includes breaking changes to `%graph-store` which stores and shares messages, notebooks, and collections.
68+Ships with the OTA will not be able to communicate over graph store with ships without the OTA.
69+
70+**I have gotten the OTA and I can't post in some groups or DM some people.**
71+
72+See above. Once your peers receive the OTA, you will be able to communicate again.
73+
74+**Can I still `|hi` between pre and post OTA ships?**
75+
76+`|hi` will continue to work between pre and post OTA ships.
77+
78+**Can I still use `|ota` to select my OTA provider?**
79+
80+`|ota` will continue to work on ships without the OTA, even if their OTA provider is running the OTA.
81+After the OTA, the `|ota` command is removed and is replaced by the `|install` command.