we've got a bad date (used as an initialization placeholder) that is showing up in moves where they shouldn't be. perhaps in the +scry cache? 
Show this thread
-
-
-
hmm. maybe a false alarm...https://github.com/urbit/urbit/issues/1160#issuecomment-462103013 …
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.