Except the Pharaoh would still be alive(!?) in this case.

The source code will be Blizzard IP for a long time after the coders are dead.

Neither Chris Metzen or James Phinney even works at Blizzard anymore. The same is likely true for many of the coders.

And, importantly, never tell anyone about #2 (at least until you can be completely certain Blizzard won't take action against you).

No. They're using the same gameplay code as the original Starcraft:

    Q: How did you go about replicating all the unexpected “bugs” that made BW micro
    so special? Did you simply reuse code from the original game, or did you find a
    solution to replicate the nuances of BW’s gameplay?

    A: StarCraft: Remastered is able to achieve this effect as it uses all the same
    gameplay code as Brood War. This means that Dragoons and Goliaths are still a
    bit derpy in how they react to movement commands. The Reaver’s shot doesn’t
    always find a target. Mutas stack.

    The fact is that the gameplay is identical enough that old replays from 1.16
    will play and work just fine under StarCraft: Remastered.

from http://www.teamliquid.net/forum/brood-war/520464-an-intervie...

The story, for anyone else wondering what was referred to: https://hackernoon.com/paypal-is-still-one-of-the-worst-onli...

On IPv4, the server accepts the connection but closes it right after.

On IPv6, it works (as mentioned by others already).

If you want to do this only for a single invocation, this will work:

  ssh -o IdentitiesOnly=yes -i /dev/null host

Specifying just IdentitiesOnly is not enough.

> Specifying just IdentitiesOnly is not enough.

In what manner?

With IdentitiesOnly, any explicitly configured via IdentityFile, or the default identity file if none are configured explicitly, is/are still sent. Using "-i /dev/null" in combination with IdentitiesOnly prevents that.

Interesting. If you're right, the manual leaves out the rather critical "or the default identity file" bit:

> Specifies that ssh(1) should only use the authentication identity and certificate files explicitly configured in the ssh_config files or passed on the ssh(1) command-line, even if ssh-agent(1) or a PKCS11Provider offers more identities.

I verified the behavior with ssh -vv (macOS Sierra).

Or just never install an identity in the default location (.ssh/id_*)

There's instructions for installing from their repos elsewhere on the site: https://www.microsoft.com/net/core#linuxubuntu

So it's like Slack, period.

And here are the actually interesting parts:

https://docs.datproject.org/how-dat-works

https://github.com/datproject/docs/blob/master/docs/hyperdri...

Seems very similar to BitTorrent, but without trackers, with Content Defined Chunking (instead of Fixed Size Chunking) and utilizing Merkle trees + public key cryptography to enable append-only operations on shared data sets (rather than 'read-only once published').

Thanks for the links, here are a few more you may find interesting:

In progress paper - https://github.com/datproject/docs/blob/master/papers/dat-pa...

Dat protocol site - https://www.datprotocol.com/

The parent is correct, the given command redirects stdout to stderr, it's not copied (so stdout will be empty).

Again, have you tried it?

    # echo "foo" 1>&2 | sed 's/foo/bar/'
    foo
    bar

Edit: I've done some more testing, and discovered that the above works on zsh, but not in bash

2nd Edit: Ahha! http://www.cs.elte.hu/zsh-manual/zsh_7.html . So this is because zsh w/ the stock config (MULTIOS option enabled) will open as many outputs as you give it. So it can both copy FD 1's contents to FD 2 and to the pipe'd command.