News for hackers. Stuff that matters.
Re:Urbit user guide, hosted on Urbit by e12e on Thursday October 22, 2015 @10:02PM (#10436406)
From[1]: "Anyone can run the Urbit VM, of course. But the %ames network is officially invitation-only. Not that we're antisocial -- just that we're under construction."

So, is there support for running a separate p2p network? Or is the only option to wait for urbit to stabilize?

[ed: Never mind, it's covered under "Launch Instructions": If you don't have an invitation, pick a nickname for your comet, like mycomet. Urbit will randomly generate a 128-bit plot]

[ed2: Hm, looks like the ability to spawn an alternate universe would make playing with urbit more interesting, as I understand it - without an invite, most of the best parts are inaccessible: "The fanciest way to control your urbit is through Urbit itself: a moon, or satellite urbit. Sadly, only planets can have moons."]

[1] http://urbit.org/docs/user/intro

Re:Urbit user guide, hosted on Urbit by chc4 on Thursday October 22, 2015 @11:27PM (#10436629)
It's entirely possible to spawn an alternate universe. In fact, it's recommended to spin up an offline version of ~zod to develop on so you don't end up crashing you actual planet. The `-F` flag makes it so your ships only connect over localhost instead of looking up the top-level galaxies from *.urbit.org

It's also possible to hard-fork the network. The galaxies' public key hash is hard-coded in the source, so if you change it your ship will accept that the new key is the actual galaxy. Of course, there is no guarentee that any OTHER ship you talk to will agree with you...

Re:Urbit user guide, hosted on Urbit by e12e on Friday October 23, 2015 @01:17AM (#10436924)
Oh, thanks for the update. But this doesn't appear to be documented anywhere? So far I've only been reading the documentation, not the source code -- perhaps it's more obvious from the source code that such functionality already exists (eg: the -F flag)?
Re:Urbit user guide, hosted on Urbit by state on Friday October 23, 2015 @01:31AM (#10436973)
Our documentation is still very young, but it is mentioned in our contributing guide:

http://urbit.org/docs/dev/contributing

There's much more to cover in terms of how the network works. It's coming! For the time being some things are just folk knowledge. We're always happy to answer questions though.

Re:Urbit user guide, hosted on Urbit by state on Thursday October 22, 2015 @11:56PM (#10436714)
Just to clarify: you can substitute 'planet' for 'ship' in the above. We changed the naming scheme.
Re:Urbit user guide, hosted on Urbit by e12e on Thursday October 22, 2015 @10:27PM (#10436477)
Another interesting tidbit, that maybe someone can shed some light on: "Reactive auto-updates are a particular speciality of %clay. We use them to drive auto-updates of code at every layer. A normal Urbit user never has to think about software update."

Is this another way to say that you can never know what version of urbit you're running? So when someone compromises the upstream keys/ids urbit becomes one big botnet?

Re:Urbit user guide, hosted on Urbit by yarvin9 on Thursday October 22, 2015 @10:50PM (#10436534)
Yes. And the same is probably true of the browser you used to post this. Also, the OS it's running on. It's the price of being "evergreen."

It's worth thinking about why we've accepted this tradeoff. The cost of evergreen software is that we put all our eggs in one basket, and watch the heck out of that basket. The benefit is that we solve a huge set of system administration problems that would otherwise be ridiculously impractical.

One metaphor I like to use is the difference between the Soviet and American design styles in aerospace. The Soviet way was to build systems with loose tolerances that worked okay even when parts were a little out of spec. The American way is to build systems with precise tolerances that work perfectly when everything is right, and fail catastrophically when it isn't.

There's much to be said for the Soviet style, and indeed it might be summed up well in Postel's law. But as the problems you're trying to solve get harder (like keeping all the world's browsers updated), it doesn't scale very well. If we compare the problems we can solve with manual upgrades and Postel's law, to the problems we can solve with automatic upgrades and rigorous protocol validation, there's no contest.

Re:Urbit user guide, hosted on Urbit by e12e on Friday October 23, 2015 @01:28AM (#10436963)
Thank you for taking the time to respond.

> Yes. And the same is probably true of the browser you used to post this. Also, the OS it's running on. It's the price of being "evergreen."

The OS, yes, to a certain extent. I don't think I've set up apt/cron-apt to automatically pull in stuff on (any of) my desktop(s) yet -- they tend to have a couple of bleeding edge repos enabled, and I often do not want even security updates at surprising times. Nothing like firing up your laptop on an airplane just to discover 3d acceleration no longer works because of a kernel security update (frequently for a local-only crash/exploit).

As for browsers, I'm mostly familiar with FF, and that usually prompts before update? I think you can set it to automatically update, though?

I do accept that trusting a single group of people to maintain the OS can be a good trade-off -- I trust Debian's Security team to do that. Sure, if they are compromised (or more likely, make a mistake) I'll suffer. But I'm not interested in having the small chance of key compromise be multiplied with all the (complex) software packages I use.

Also, for context, the same documentation clearly states "Urbit is not (currently) secure in any way" (or something to that effect), and in passing "if urbit runs as root". Well, apt-get does run as root, but a) it only runs automatically if I tell it to, and b) it's built on rather well-tested primitives (GnuPG etc).

So, having Urbit be notified of changes, and optionally automatically update sounds great, I'm not sure if I think "always automatically update" sounds quite as great. Especially if the stuff on which trust is built (encryption etc) is still considered unstable.

[ed: To be clear, the last bit, I like: "A normal Urbit user never has to think about software update." Key word being "normal". As Urbit is unstable, and everyone are developers and/or testers - there aren't (yet) any such "normal" users? ]

Re:Urbit user guide, hosted on Urbit by pcmonk on Friday October 23, 2015 @02:31AM (#10437116)
In the general case, we think evergreen updates are an excellent idea. It's important to note, though, that it's easy to stop syncing from the upstream repository. Notification plus manual update is totally possible. Most people won't want to do that, but some will.

With SaaS web apps, it is of course impossible to turn off updates, which annoys the heck out of me.