Tim Watson

+1 - sounds reasonable to me too.

Looking at this, I want to understand `decoded` a bit better... If we get a fingerprint match, we have to unencode (and that's coerce in the local case, don't forget),...

That last paragraph sounds like the most pragmatic approach to me?

Since that's the case, can we close this issue? Should I add something about this to the documentation? It feels to me like I should probably compile the various issues...

Yes actually that's a good question... I think the answer is in the client's court. Calling unlink means I no logger want link exceptions. If I want to avoid having...

Looking at the code, I'm not sure some of your assertions hold @facundominguez. After sending a control message to the node controller, `unlink` waits for a message of type `DidUnlinkProcess`,...

And in actual fact, `ncEffectUnlink` in the node controller *doesn't even care* if the target (i.e. linked-to process) is alive or not. So there's not even a race, because even...

BTW - I'm quite happy to pick up the grunt work on this once we've made some decisions about how it should work.

> I'm perfectly happy to for you to take stuff out of SimpleLocalnet. It's a quick-and-dirty backend to get people going, it > should not influence design decisions. Cool, so...

We should also consider the impact that removing `say`, the built-in logger process and the start{Slave,Master} APIs from `SimpleLocalNet` will have on example code and blog posts. That should be...