@@ -21,9 +21,9 @@ We breached successfully. You can read about [what we fixed](https://github.com/
2121The 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:
2222
2323```
24−> `@p`3.108.299.008
24+> `````@p```````3.108.299.008
2525~morlyd-mogmev
26−> `@p`479.733.505
26+> `````@p`````479.733.505
2727~morlyd-mogmev
2828```
2929
@@ -39,8 +39,6 @@ Stay tuned for a post with a full report.
3939
4040Tlon is at the beginning a new batch of work for 2019, so new proposals are popping up almost daily. *I* `~hidrel-fabtel` am 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.
4141
42−The Interface team is brewing a new onboarding process and new tools on Urbit. We can’t wait to share, but it will be awhile.
43−
4442## Community
4543
4644Our 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!