I think this is both insightful and funny. It's a pretty interesting little thing that I'm sure could easily get blow out of context by the same people who get upset when they learn about master and slave devices.
Re:How SSH got port number 22
by The_Egg_Man on Sunday April 23, 2017 @03:44PM
(#14180057)
SimHacker and DonHopkins are the same person. Check out SimHackers history and Don's site; he is a hacker of the SIMs
I don't know why he uses two accounts!
Re:How SSH got port number 22
by DonHopkins on Sunday April 23, 2017 @11:14PM
(#14181700)
I don't use them at the same time: I switched over to using my own name instead of an old alias.
Whenever I plagiarize myself, I try to check the links and refine the text to keep it relevant.
Just posting a link to an old article requires less effort for me, but more effort for other people to switch context, navigate and read. And a server's disk space and bandwidth aren't as precious as a reader's time and effort.
It was not my intention to trigger mdekkers into having fits about SJWs, or shocking paxcoder who is not a gay supporter.
Personally I think it's great that you reposted your comment.
I suggest however that when you do, you add a line to the bottom that says something along the line "This comment was based on an earlier comment I made X days ago using another account." when you do just to keep people from accusing you of plagiarizing others.
I'm okay with it. I hadn't seen the last time it was posted and I found it very interesting.
The act of trying to connect an even socket to another even socket, or an odd socket to another odd socket, was considered a "peculiar error" called "homosocketuality", which was strictly forbidden by internet protocols, and mandatory "heterosocketuality" was called the "Anita Bryant feature" [2].
http://www.saildart.org/IMPSER.DOC[SS,SYS]
When the error code is zero, the next 8 bit byte is the Stanford peculiar error code, followed by 72 bits of the ailing command returned. Here are the Stanford error codes. [...]
IGN 3 Illegal Gender (Anita Bryant feature--sockets must be heterosocketual, ie. odd to even and even to odd) [...]
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.NCP[S,NET]
(The PDP-10 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.)[1] https://en.wikipedia.org/wiki/Network_Control_Program
[2] https://www.youtube.com/watch?v=H-A2Ql81WTY