huevo5050
Is inaccessible but you dig into it, is obscure but are pieces of code written in C.
"Urbit's internal opacity persists for two reasons, one good and one bad. The bad reason is just laziness. The good reason is justified fear of premature explanation, which like premature optimization ruins the annealing process.
When you don't know exactly what you're doing, preserve as much ambiguity as possible. For example, a name that means something is a commitment to one specific explanation; a name that means nothing is no commitment at all. A cryptic name is productive procrastination; it lets the hard problem of naming get solved later, and hence better."
Comets are 128 bits and have no parents. They can be launched by anyone. They are temporary, disposable identities. Being disposable and essentially unlimited, they will likely not be trusted by default by others on the Urbit OS network, though you shouldn't have any problem until the network grows much larger. They have long, hard-to-memorize names, like ~racmus-mollen-fallyt-linpex-watres-sibbur-modlux-rinmex.
rasky:
https://www.nexlab.net/product/rasky/
I have contributed to it but a lot of time without news. Maybe contribute to rasky was risky.