There isn't one.

Like I said, it's a standoff.

The editors don't want to cause a schism in the userbase, because if we online a fork while the old domain is live, not everyone will move.

RIght now, the status quo is this:

Root refuses to remove the robot block. The editors have copies of the site ready to go, updated to an S3 bucket daily.

If Root pulls the domain down, the editors will pick a new domain, stand up the latest backup and all that Root accomplishes is that he loses control, he doesn't manage to kill the site.

As long as Root doesn't go nuclear by pulling down 1d4chan.org, the editors won't go nuclear by using their backups to fork the site.

Hence: Standoff.

There isn't one.

Like I said, it's a standoff.

The editors don't want to cause a schism in the userbase, because if we online a fork while the old domain is live, not everyone will move.

RIght now, the status quo is this:

Root refuses to remove the robot block. The editors have copies of the site ready to go, updated to an S3 bucket daily.

If Root pulls the domain down, the editors will pick a new domain, stand up the latest backup and all that Root accomplishes is that he loses control, he doesn't manage to kill the site.

As long as root doesn't go nuclear by pulling down 1d4chan.org, the editors won't go nuclear by using their backups to fork the site.

Hence: Standoff.

There isn't one.

Like I said, it's a standoff.

The editors don't want to cause a schism in the userbase, because if we online a fork while the old domain is live, not everyone will move.

RIght now, the status quo is this:

Root refuses to remove the robot block. The editors have copies of the site ready to go, updated to an S3 bucket daily.

If Root pulls the domain down, the editors will pick a new domain, stand up the latest backup and all that Root accomplishes is that he loses control, he doesn't manage to kill the site.