Hacker News new | ask | show | jobs
by SimHacker 4688 days ago
Good thing TCP/IP legalized same-sex connections. NCP was not so open minded.

The old NCP networking protocol required that connect and listen sockets must have different parity gender (one even, the other odd -- I can't remember which was which, or if it mattered -- they just had to be different). The act of trying to connect an even socket to another even socket, or an odd socket to another odd socket, was called "homosocketuality", and it was strictly forbidden by internet protocols, and was called the "Anita Bryant feature".

http://www.saildart.org/IMPSER.DOC[SS,SYS][1]

Illegal gender in RFC, host hhh/iii, link 0

The host is trying to engage us in homosocketuality. Since this is against the laws of God and ARPA, we naturally refuse to consent to it.

http://www.saildart.org/FTP.OLD[S,NET]1[2]

    ; Try to initiate connection

    loginj:
            init log,17
            sixbit /IMP/
            0
            jrst noinit
            setzm conecb
            setom conecb+lsloc
            move ac3,hostno
            movem ac3,conecb+hloc
            setom conecb+wfloc
            movei ac3,40
            movem ac3,conecb+bsloc
            move ac3,consck
            trnn ac3,1
                jrst gayskt            ; only heterosocketuals can win!
             movem ac3,conecb+fsloc
             mtape log,[
                   =15
                    byte (6) 2,24,0,7,7
                         ]          ; Time out CLS, RFNM, RFC, and INPut

    [...]

    gayskt:    outstr [asciz/Homosocketuality is prohibited (the Anita Bryant feature)

    /]

        ife rsexec,<jrst rstart;>exit       1,
(The code above adds the connect and listen socket numbers together, which results in bit 0 being 0 if they are the same gender, then TRNN is "test bits right, no change, skip if non zero", which skips the next instruction (jrst gayskt) if they different sex.)