@@ -0,0 +1,50 @@
1+:- :~ date/'~2019.3.14'
2+ title/'~2019.3.4 Update'
3+ preview/'A short update from the Tlon team for the week of ~2019.3.4.'
4+ author/'~hidrel-fabtel'
5+ type/'post'
6+ ==
7+;>
8+
9+# ~2019.3.4 Update
10+
11+Here’s a short update from the team for the week of `~2019.3.4`:
12+
13+;img@"https://media.urbit.org/site/posts/updates/~2019.3.4-update-1.jpg"(width "100%");
14+
15+## Network
16+
17+We breached successfully. You can read about [what we fixed](https://github.com/urbit/arvo/pull/1101). Issues ocassionally crop up as people join the network, but it looks to be smooth sailing as we make our way toward [cc-release](https://github.com/urbit/urbit/tree/cc-release) and new %ames.
18+
19+## `@p` Bug
20+
21+The nice folks behind [@urbitlive](https://twitter.com/urbitlive) discovered a bug in `@p` leading to planet name-collisions. Due to a subtly incorrect implementation of the cryptographic algorithm we use to scramble planet names – used to dissociate them from their parent stars – a small percentage of people with different Azimuth points could end up with the same planet name. For example:
22+
23+```
24+> `@p`3.108.299.008
25+~morlyd-mogmev
26+> `@p`479.733.505
27+~morlyd-mogmev
28+```
29+
30+We [announced the bug on Twitter](https://twitter.com/urbit/status/1105850450559918082) today, and [a conversation](https://github.com/urbit/arvo/issues/1105) has been ongoing on Github. It appears we've settled on a solution, outlined in [this 3-line suggestion](https://github.com/urbit/arvo/issues/1105#issuecomment-472585937) from @max19, which elegantly corrects the implementation of the algorithm while preserving all existing planet names – a truly miraculous solution that came out of nowhere. Thank you Max!
31+
32+Stay tuned for a post with a full report.
33+
34+## Team
35+
36+*Jared* `~nidsut-tomdun` spent the week on the `@p` debacle and more than once generated all four billion planet names to check for collisions. *Ted* `~rovnys-ricfer` spent much of the week thinking about redesigning the PKI only to realize that the existing design is quite good. *Logan* `~tacryt-socryp` and *Isaac* `~novlud-padtyv` started working on the next major revision to Landscape. *Ben* `~pitmug-roptic` quietly [started working on](https://github.com/urbit/urbit/pull/1221) 64-bit Vere. `~pilfer-pandex` [brought the hammer down](https://github.com/urbit/docs/pull/399#issuecomment-472667240) on the pronunciation debate.
37+
38+Tlon is at the beginning a new batch of work for 2019, so new proposals are popping up almost daily. *Morgan* `~hidrel-fabtel` is working on revamping our proposal (“UP”) system so that the outside world can more easily participate in all of the work that’s going on. *Anthony* `~poldec-tonteg` and *Jared* `~nidsut-tomdun` are also working on standards for our repository documentation and open-source development process.
39+
40+## Community
41+
42+Our Austin meetup and San Francisco AMA were a blast. You can watch [the recording of the latter](https://www.youtube.com/watch?v=ndk2b69fA9A) on Youtube. Thank you for coming and for all of your questions!
43+
44+Out there on the Internet, people are starting to build their own platforms around Urbit and Azimuth. There are now multiple planet stores and at least one active online community. It's exciting to watch the community start to grow all by itself.
45+
46+Until next time.
47+
48+;br;
49+
50+*Morgan* `~hidrel-fabtel`