1
00:00:00,320 --> 00:00:03,000
Speaker 1: Brought to you by the reinvented two thousand twelve Camray.

2
00:00:03,240 --> 00:00:08,959
Speaker 1: It's ready. Are you get in touch with technology? With

3
00:00:09,039 --> 00:00:18,440
Speaker 1: tech Stuff from how stuff works dot com. Hello again, everyone,

4
00:00:18,560 --> 00:00:21,239
Speaker 1: and welcome to tech stuff. My name is Chris Poulette

5
00:00:21,280 --> 00:00:23,319
Speaker 1: and I am an editor here at how stuff works

6
00:00:23,320 --> 00:00:26,639
Speaker 1: dot com. Sitting across from me as he always does

7
00:00:26,840 --> 00:00:29,400
Speaker 1: on Friday afternoons when we talk about tech things, is

8
00:00:29,480 --> 00:00:33,280
Speaker 1: senior writer Jonathan Strickland. Remember, no matter where you go,

9
00:00:34,080 --> 00:00:39,159
Speaker 1: there you are dre pithy. Thank you. So today we

10
00:00:39,200 --> 00:00:42,440
Speaker 1: wanted to uh have a little chat. Yes, actually we

11
00:00:42,479 --> 00:00:46,000
Speaker 1: want to have a little chat about a chat protocol

12
00:00:46,600 --> 00:00:50,560
Speaker 1: or a chat system that predates the World Wide Web.

13
00:00:50,920 --> 00:00:54,200
Speaker 1: And this, uh, this is a request from Charles and

14
00:00:54,400 --> 00:00:58,760
Speaker 1: also from Christopher. These are two independent requests. Both Charles

15
00:00:58,800 --> 00:01:01,480
Speaker 1: and Christopher wanted to hear a little more about I

16
00:01:01,840 --> 00:01:06,720
Speaker 1: r C or Internet Relay Chat. Yeah. Um, actually it

17
00:01:07,040 --> 00:01:11,200
Speaker 1: dates back to so this is a pretty pretty uh

18
00:01:11,400 --> 00:01:14,200
Speaker 1: robust protocol to have made it, uh you know, good,

19
00:01:14,560 --> 00:01:18,840
Speaker 1: almost twenty two years now. It's August of is when

20
00:01:18,880 --> 00:01:21,960
Speaker 1: it started to make its appearance. And um, as a

21
00:01:22,000 --> 00:01:24,080
Speaker 1: matter of fact, that's that was sort of my introduction

22
00:01:24,120 --> 00:01:25,800
Speaker 1: to the Internet. And I say sort of because it

23
00:01:25,840 --> 00:01:29,720
Speaker 1: wasn't exactly I r C UM. I became acquainted with

24
00:01:30,160 --> 00:01:34,880
Speaker 1: using online services through a similar system uh called bitnet

25
00:01:34,959 --> 00:01:38,759
Speaker 1: Relay chat um. And as a matter of fact, one

26
00:01:38,800 --> 00:01:41,960
Speaker 1: of the founders of of I r C and I'm

27
00:01:41,959 --> 00:01:46,640
Speaker 1: probably totally mispronouncing this, um Yarko arkin In, who has

28
00:01:46,680 --> 00:01:50,280
Speaker 1: a fin Uh. He apparently took some of his direction

29
00:01:50,400 --> 00:01:54,160
Speaker 1: from using bitnet chat um. And the two systems really

30
00:01:54,160 --> 00:01:58,400
Speaker 1: aren't all that different, but uh, it is a has

31
00:01:58,440 --> 00:02:02,960
Speaker 1: a much different system, uh, or at least it's a

32
00:02:02,960 --> 00:02:05,200
Speaker 1: different protocol from what you would see for so many

33
00:02:05,280 --> 00:02:10,760
Speaker 1: the other different Internet uses, right. Uh. And leading up

34
00:02:10,800 --> 00:02:15,000
Speaker 1: to I r C, before that, there was a program

35
00:02:15,040 --> 00:02:20,120
Speaker 1: called Talk, and Talk was really it's like what would

36
00:02:20,120 --> 00:02:24,000
Speaker 1: happen if you were to phone someone and uh, it's

37
00:02:24,040 --> 00:02:26,760
Speaker 1: just a regular phone line and so it's two people,

38
00:02:27,520 --> 00:02:30,160
Speaker 1: one person on either end. And that's the extent of

39
00:02:30,200 --> 00:02:34,720
Speaker 1: that conversation. That was the limitation of Talk and uh

40
00:02:34,800 --> 00:02:39,000
Speaker 1: and really the I'm not even gonna try and say

41
00:02:39,040 --> 00:02:41,800
Speaker 1: his name because my finish is terrible. I'd be finished

42
00:02:41,840 --> 00:02:47,959
Speaker 1: myself at any rate. Our our intrepid inventor thought, well,

43
00:02:48,080 --> 00:02:51,760
Speaker 1: why should we be limited to having two people in

44
00:02:51,800 --> 00:02:55,080
Speaker 1: a single discussion. When the Internet really gives you the

45
00:02:55,120 --> 00:02:58,280
Speaker 1: opportunity to connect with people all over the world, why

46
00:02:58,320 --> 00:03:00,639
Speaker 1: doesn't need to be a direct connection to two We

47
00:03:00,639 --> 00:03:04,520
Speaker 1: we could have a centralized connection where a connecting point

48
00:03:04,560 --> 00:03:08,440
Speaker 1: where where thousands of people potentially could join in and

49
00:03:08,480 --> 00:03:12,880
Speaker 1: have a conversation. Yeah, systems like talk and other early

50
00:03:13,480 --> 00:03:17,400
Speaker 1: different communication protocols like y talk and x y z

51
00:03:17,480 --> 00:03:22,040
Speaker 1: z Y. Remember that one, Um, we're we're seriously talking

52
00:03:22,080 --> 00:03:26,080
Speaker 1: like your Your whole screen would essentially look like uh,

53
00:03:26,280 --> 00:03:30,040
Speaker 1: a divided window uh and and two chats you would

54
00:03:30,040 --> 00:03:32,440
Speaker 1: see what the other person was typing in. Uh. They weren't.

55
00:03:32,440 --> 00:03:35,840
Speaker 1: It wasn't even integrated like AIM or h I c

56
00:03:36,000 --> 00:03:37,840
Speaker 1: Q or any of the other chat services that are

57
00:03:37,840 --> 00:03:40,600
Speaker 1: in use today. You know, it's like this is everything

58
00:03:40,680 --> 00:03:43,200
Speaker 1: your friend has said, and this is everything you have

59
00:03:43,320 --> 00:03:45,480
Speaker 1: said in reply. So you could go back and forth

60
00:03:45,520 --> 00:03:48,920
Speaker 1: between the other and UM and gradually. Yeah, that the

61
00:03:48,960 --> 00:03:52,200
Speaker 1: idea of of Internet relay chat actually would divide it

62
00:03:52,280 --> 00:03:56,200
Speaker 1: up and divide up the service into different channels, and

63
00:03:56,520 --> 00:03:59,720
Speaker 1: you know, theoretically you could be talking about you know,

64
00:04:00,240 --> 00:04:03,560
Speaker 1: a whole different conversation on one channel where from the

65
00:04:03,800 --> 00:04:06,480
Speaker 1: people who are talking in other channels. So it's it's

66
00:04:06,480 --> 00:04:09,440
Speaker 1: basically one service where everybody goes and you can go

67
00:04:09,480 --> 00:04:12,040
Speaker 1: from channel to channel and talk about whatever is the

68
00:04:12,080 --> 00:04:14,000
Speaker 1: topic of the day or topics of the day are.

69
00:04:14,360 --> 00:04:17,560
Speaker 1: And depending on on when you used I r C,

70
00:04:17,760 --> 00:04:21,080
Speaker 1: because it did evolve over time, that's certificantly. In fact,

71
00:04:21,279 --> 00:04:25,000
Speaker 1: you could occupy multiple channels at one time, depending on

72
00:04:25,040 --> 00:04:27,960
Speaker 1: their client. Uh. Client is an important thing that we

73
00:04:27,960 --> 00:04:30,960
Speaker 1: should talk about very quickly. UH. So you've got a

74
00:04:31,000 --> 00:04:35,080
Speaker 1: server that's hosting this program, the I r C program,

75
00:04:35,160 --> 00:04:37,479
Speaker 1: in order to access that information. In order to be

76
00:04:37,520 --> 00:04:40,760
Speaker 1: able to participate in these conversations, you as a user

77
00:04:40,839 --> 00:04:44,360
Speaker 1: would need to have a client. And there are different

78
00:04:44,360 --> 00:04:48,039
Speaker 1: ways of getting clients. Uh. You could compile a client,

79
00:04:48,120 --> 00:04:50,360
Speaker 1: get a sort, get source code, and compile your own

80
00:04:50,360 --> 00:04:53,080
Speaker 1: client if you were using a Unix based system, um,

81
00:04:53,240 --> 00:04:57,120
Speaker 1: which would require a level of of tech savvy that

82
00:04:57,279 --> 00:04:59,520
Speaker 1: is beyond my own means. But just because I've never

83
00:04:59,600 --> 00:05:02,719
Speaker 1: used a NEX system, if you never used Unix, well,

84
00:05:03,160 --> 00:05:06,920
Speaker 1: I mean that's being that's not entirely true. But I've

85
00:05:06,920 --> 00:05:09,480
Speaker 1: never got to say I thought you had. I've never

86
00:05:09,839 --> 00:05:12,200
Speaker 1: I've never owned a you know any sort of machine

87
00:05:12,279 --> 00:05:15,039
Speaker 1: or worked exclusively on a Unix based machine. I've worked.

88
00:05:15,920 --> 00:05:19,920
Speaker 1: My time with Unix has been very limited, I understand. So,

89
00:05:19,640 --> 00:05:21,360
Speaker 1: uh so I would not be able to do this.

90
00:05:21,600 --> 00:05:23,400
Speaker 1: I just don't have that knowledge. I mean it's not

91
00:05:23,440 --> 00:05:25,480
Speaker 1: that I couldn't learn. I just if you sat me

92
00:05:25,520 --> 00:05:28,440
Speaker 1: down in front of a computer right now, I'd be like, uh,

93
00:05:28,800 --> 00:05:34,520
Speaker 1: help or maybe slash help. So but once you had

94
00:05:34,560 --> 00:05:38,000
Speaker 1: a client to access this, then you could go and

95
00:05:38,120 --> 00:05:41,800
Speaker 1: uh and start having a conversation with other people. Now,

96
00:05:42,480 --> 00:05:45,000
Speaker 1: some people have have a little difficulty grasping the whole

97
00:05:45,040 --> 00:05:48,960
Speaker 1: client concept, but I'll give you a very simple analog

98
00:05:49,040 --> 00:05:51,920
Speaker 1: to that. Your web browser is essentially a client. It's

99
00:05:51,920 --> 00:05:54,960
Speaker 1: a client that lets you access the world Wide Web. Yeah.

100
00:05:54,960 --> 00:05:56,960
Speaker 1: I think this is a good time to remind people

101
00:05:56,960 --> 00:06:02,080
Speaker 1: to that, UMU, the Web is only part of the Internet.

102
00:06:02,160 --> 00:06:05,120
Speaker 1: The Internet itself is is a network of networks, is

103
00:06:05,720 --> 00:06:09,760
Speaker 1: more or less the Yeah, it hundreds of them. Actually, Yeah,

104
00:06:09,760 --> 00:06:12,400
Speaker 1: you've got you've got your mail protocols, you have the

105
00:06:12,400 --> 00:06:15,000
Speaker 1: world Wide Web. Um you can still do things like

106
00:06:15,160 --> 00:06:19,359
Speaker 1: use Gopher or waste or I r C or you

107
00:06:19,360 --> 00:06:22,440
Speaker 1: know all these different other things. Yeah, use net and

108
00:06:22,680 --> 00:06:24,159
Speaker 1: you know we should do a podcast on that, Yeah

109
00:06:24,160 --> 00:06:28,000
Speaker 1: we should. Um, but uh but yeah, I mean there

110
00:06:27,839 --> 00:06:31,000
Speaker 1: are there are a number of things that that travel

111
00:06:31,160 --> 00:06:33,599
Speaker 1: over the Internet and I r C is just one

112
00:06:33,640 --> 00:06:36,800
Speaker 1: of those protocols um that can be used that way.

113
00:06:36,800 --> 00:06:39,280
Speaker 1: So yeah, you need in order to do to actually

114
00:06:39,320 --> 00:06:44,039
Speaker 1: access that service though, you need a program that can

115
00:06:44,320 --> 00:06:48,360
Speaker 1: understand that traffic and make it into something useful for you.

116
00:06:48,480 --> 00:06:51,400
Speaker 1: Otherwise it's just a bunch of ones and zeros. So

117
00:06:51,839 --> 00:06:58,680
Speaker 1: back when I r C was was really pretty young, um,

118
00:06:58,720 --> 00:07:01,599
Speaker 1: you would be using one of these client and that

119
00:07:01,680 --> 00:07:03,320
Speaker 1: you would have to have installed on your computer. You

120
00:07:03,320 --> 00:07:06,000
Speaker 1: would have to have either built it or had someone

121
00:07:06,000 --> 00:07:10,000
Speaker 1: else build it for you. Uh. Today it's a little different.

122
00:07:10,080 --> 00:07:13,240
Speaker 1: You can actually find clients that are built into web

123
00:07:13,280 --> 00:07:16,080
Speaker 1: pages so that you could go to a web page

124
00:07:16,120 --> 00:07:20,520
Speaker 1: and log into an I r C chat area, um,

125
00:07:20,560 --> 00:07:22,520
Speaker 1: and you never have to worry. You know, it does

126
00:07:22,560 --> 00:07:24,920
Speaker 1: all the work for you, all the all the coding

127
00:07:24,960 --> 00:07:27,960
Speaker 1: and everything is is essentially hidden away from you and

128
00:07:28,000 --> 00:07:30,720
Speaker 1: you can just log in. Now, that doesn't necessarily mean

129
00:07:30,760 --> 00:07:33,320
Speaker 1: that the commands are all going to be intuitive to you,

130
00:07:33,360 --> 00:07:36,040
Speaker 1: because it turns out there are lots and lots of

131
00:07:36,040 --> 00:07:38,640
Speaker 1: different commands that you can use within I r C

132
00:07:39,320 --> 00:07:42,400
Speaker 1: while you are having conversations, And some of them are

133
00:07:43,320 --> 00:07:46,480
Speaker 1: very basic, things like being able to create a channel

134
00:07:46,680 --> 00:07:48,640
Speaker 1: so that you have a separate channel that you can

135
00:07:48,840 --> 00:07:51,400
Speaker 1: you can go into and have other people go into

136
00:07:51,440 --> 00:07:55,360
Speaker 1: if you want to take part of a conversation away

137
00:07:55,440 --> 00:07:59,560
Speaker 1: from the main room that you're in. The idea here

138
00:07:59,560 --> 00:08:01,880
Speaker 1: being that perhaps maybe you and three other people you

139
00:08:01,920 --> 00:08:06,000
Speaker 1: find out are all huge fans of a particular book series,

140
00:08:06,080 --> 00:08:08,440
Speaker 1: let's say yes, so that the room in general doesn't

141
00:08:08,480 --> 00:08:11,080
Speaker 1: have that interest. Well, the polite thing to do would

142
00:08:11,080 --> 00:08:13,840
Speaker 1: be to create a room specifically for you and your

143
00:08:14,080 --> 00:08:17,680
Speaker 1: three new book friends to go to and have a

144
00:08:17,680 --> 00:08:22,880
Speaker 1: conversation that doesn't doesn't interrupt the flow of the general conversation. Yeah,

145
00:08:22,880 --> 00:08:25,960
Speaker 1: and I r C. It's considered pretty rude to have

146
00:08:26,240 --> 00:08:29,080
Speaker 1: off topic conversations. Now, there are some channels that are

147
00:08:29,520 --> 00:08:33,240
Speaker 1: are generic, kind of free for all. Yeah and UM

148
00:08:33,600 --> 00:08:36,800
Speaker 1: usually on what I was going to get into some

149
00:08:36,800 --> 00:08:39,319
Speaker 1: more depth on this, let's let's just say usually there

150
00:08:39,440 --> 00:08:43,280
Speaker 1: is something called a channel called talk or chat. These

151
00:08:43,280 --> 00:08:47,520
Speaker 1: are very very generic, but if you were um and

152
00:08:47,520 --> 00:08:50,760
Speaker 1: and they also often have a description that goes along

153
00:08:50,800 --> 00:08:52,920
Speaker 1: with it. So you might have a channel for say

154
00:08:53,040 --> 00:08:56,439
Speaker 1: Terry Pratchett. Let's go with an author, your channel would

155
00:08:56,440 --> 00:08:59,360
Speaker 1: want to you'd want to do something descriptive and uh,

156
00:09:00,320 --> 00:09:03,160
Speaker 1: you know, generally in the title of the h of

157
00:09:03,240 --> 00:09:08,679
Speaker 1: the channel, the channel name, you would often see the

158
00:09:08,679 --> 00:09:11,720
Speaker 1: topic or a topic with a little descriptive material like,

159
00:09:11,800 --> 00:09:15,000
Speaker 1: you know, Terry Pratchett the greatest author ever or something like.

160
00:09:15,040 --> 00:09:17,080
Speaker 1: It might just be as something as simple as hashtag

161
00:09:17,160 --> 00:09:21,240
Speaker 1: Pratchett fans, Yes, exactly, um and yeah. That that's something

162
00:09:21,240 --> 00:09:24,160
Speaker 1: else to remember too, is the hashtag is generally what

163
00:09:24,280 --> 00:09:27,800
Speaker 1: shows you the uh that it's a channel name, which

164
00:09:27,840 --> 00:09:31,880
Speaker 1: is important both for their command and to identify where

165
00:09:31,880 --> 00:09:34,280
Speaker 1: you are in I r C. Yeah, because they can

166
00:09:34,320 --> 00:09:37,880
Speaker 1: get kind of confusing. I mean, you also create a

167
00:09:38,000 --> 00:09:40,880
Speaker 1: nickname when you go to an I r C chat rooms.

168
00:09:40,960 --> 00:09:42,880
Speaker 1: You know, you might have one assigned to you, or

169
00:09:43,360 --> 00:09:45,800
Speaker 1: you can always choose your own. Some of them even

170
00:09:45,840 --> 00:09:48,679
Speaker 1: allow you to register your nickname. Uses a thing called

171
00:09:48,800 --> 00:09:51,599
Speaker 1: nick Serf, which disappeared for a while off of I

172
00:09:51,800 --> 00:09:53,800
Speaker 1: r C. It was hosted in Germany for a while,

173
00:09:53,880 --> 00:09:56,959
Speaker 1: then disappeared and then came back. Um. Which it's really

174
00:09:57,000 --> 00:10:01,680
Speaker 1: just an administrative system that keeps nicknames and passwords together

175
00:10:01,720 --> 00:10:04,440
Speaker 1: so that you can reserve a nickname because of course,

176
00:10:04,480 --> 00:10:07,000
Speaker 1: otherwise what will happen is if you log off, then

177
00:10:07,040 --> 00:10:09,800
Speaker 1: anyone else could log on choose the same nickname you use,

178
00:10:09,920 --> 00:10:14,760
Speaker 1: and then that can cause confusion, whether it's intentional or not. Right, right,

179
00:10:14,880 --> 00:10:16,640
Speaker 1: Like if you have a like you want your nickname

180
00:10:16,679 --> 00:10:20,000
Speaker 1: to be optimist, prime or something okay where it's you know, well,

181
00:10:20,120 --> 00:10:22,800
Speaker 1: something where it's really identifiable, and presumably more than one

182
00:10:22,840 --> 00:10:25,920
Speaker 1: person could choose it, just you know, just by chance,

183
00:10:26,040 --> 00:10:29,800
Speaker 1: not necessarily by design. Um. Yeah, as a matter of

184
00:10:29,840 --> 00:10:32,040
Speaker 1: fact that I've had that happen to me on different channels,

185
00:10:32,080 --> 00:10:35,040
Speaker 1: and um again in the now is a good time

186
00:10:35,080 --> 00:10:37,839
Speaker 1: to point that out. Um, there are actually a number

187
00:10:37,880 --> 00:10:43,040
Speaker 1: of different UH servers that that take uh different I

188
00:10:43,240 --> 00:10:47,480
Speaker 1: r C protocols. So um, there is not one standard

189
00:10:47,520 --> 00:10:49,760
Speaker 1: I r C that is roaming around the world. And

190
00:10:49,800 --> 00:10:54,040
Speaker 1: apparently in the past um twenty two years or so,

191
00:10:54,440 --> 00:10:57,360
Speaker 1: there have been disputes between people who are running I

192
00:10:57,600 --> 00:11:00,199
Speaker 1: r C. So you have uh, you know, the r

193
00:11:00,280 --> 00:11:04,320
Speaker 1: C net, which is which is part of the original group,

194
00:11:04,320 --> 00:11:07,240
Speaker 1: and then you have e F net. I remember under

195
00:11:07,240 --> 00:11:11,200
Speaker 1: net also being a very very large UH group of

196
00:11:11,480 --> 00:11:14,880
Speaker 1: I r C folks, and they have they also maintained

197
00:11:14,920 --> 00:11:18,760
Speaker 1: multiple servers in those groups, and from what I can tell, UH,

198
00:11:18,800 --> 00:11:21,800
Speaker 1: it appears that from time to time the people behind

199
00:11:21,840 --> 00:11:26,640
Speaker 1: those UH services have maybe butted heads with one another,

200
00:11:26,640 --> 00:11:29,160
Speaker 1: because when I started looking up commands, I noticed they

201
00:11:29,160 --> 00:11:31,400
Speaker 1: were different. Some of the commands were different than what

202
00:11:31,480 --> 00:11:33,800
Speaker 1: I had remembered. I imagine that's probably because they have

203
00:11:33,880 --> 00:11:37,200
Speaker 1: updated that. But I understand that UM having multiple nicknames

204
00:11:37,200 --> 00:11:39,679
Speaker 1: and the way to deal with those has also been

205
00:11:40,000 --> 00:11:43,880
Speaker 1: an issue between the different UH server organization groups and

206
00:11:43,920 --> 00:11:47,400
Speaker 1: networks of I r C servers, so they may be

207
00:11:47,480 --> 00:11:50,240
Speaker 1: running slightly different versions of you know, the I r

208
00:11:50,320 --> 00:11:54,600
Speaker 1: C protocol. And when you have these issues, like let's

209
00:11:54,600 --> 00:11:56,880
Speaker 1: say that I logged into I r C and realized

210
00:11:56,920 --> 00:11:59,920
Speaker 1: that the handle I wanted has been taken by another user,

211
00:12:00,200 --> 00:12:02,320
Speaker 1: and let's say even that I've used that handle of

212
00:12:02,320 --> 00:12:04,560
Speaker 1: the past on I r C, UM, there's not a

213
00:12:04,559 --> 00:12:06,120
Speaker 1: whole lot you can do about it. I mean, you

214
00:12:06,120 --> 00:12:08,760
Speaker 1: can message the person and say, hey, dude, that's UH,

215
00:12:08,760 --> 00:12:11,200
Speaker 1: that's kind of my nickname. I'm kind of known for

216
00:12:11,280 --> 00:12:14,240
Speaker 1: that nickname. Do you mind logging off so I can

217
00:12:14,280 --> 00:12:17,560
Speaker 1: have it because you can't take someone's name. You can't

218
00:12:17,559 --> 00:12:19,600
Speaker 1: take someone else's name if they are currently logged into

219
00:12:19,640 --> 00:12:22,360
Speaker 1: the system. You could add a number at the end,

220
00:12:22,480 --> 00:12:25,319
Speaker 1: so you know, I could become John Strickland one or

221
00:12:25,400 --> 00:12:27,560
Speaker 1: John Strickland two or something like that, but I wouldn't

222
00:12:27,600 --> 00:12:30,040
Speaker 1: be able to be John Strickland, um if someone had

223
00:12:30,080 --> 00:12:32,120
Speaker 1: already taken that name on I r C, if I

224
00:12:32,120 --> 00:12:34,360
Speaker 1: if I had not been able to register it. Uh.

225
00:12:34,640 --> 00:12:39,640
Speaker 1: So that the same thing goes for channels. Let's say

226
00:12:39,640 --> 00:12:41,800
Speaker 1: you want to create a channel and someone's already taking

227
00:12:41,840 --> 00:12:44,760
Speaker 1: the channel name that you wanted. It's like the exact

228
00:12:44,840 --> 00:12:47,240
Speaker 1: same sort of situation. You'd have to message that person,

229
00:12:47,400 --> 00:12:50,520
Speaker 1: ask them nicely if they would relinquish that channel name

230
00:12:50,600 --> 00:12:52,760
Speaker 1: for you to be able to use it. Uh, And

231
00:12:52,800 --> 00:12:55,480
Speaker 1: if they say no, then you know, that's kind of

232
00:12:56,120 --> 00:12:59,439
Speaker 1: tough luck for you. It's not like someone taking a

233
00:12:59,520 --> 00:13:02,559
Speaker 1: nickname or taking a channel name is a bootable offense.

234
00:13:02,600 --> 00:13:04,640
Speaker 1: You know someone They're not gonna get an administrator to

235
00:13:04,640 --> 00:13:08,600
Speaker 1: boot that person. So there's certain basic commands that everyone

236
00:13:08,640 --> 00:13:12,720
Speaker 1: has access to, more or less depending on the version

237
00:13:12,720 --> 00:13:15,080
Speaker 1: of I r C or in the things like slash

238
00:13:15,200 --> 00:13:19,280
Speaker 1: nick would they all have slashes that precede the command. Yeah,

239
00:13:19,280 --> 00:13:21,040
Speaker 1: if you just type, if you just start typing when

240
00:13:21,040 --> 00:13:23,000
Speaker 1: you're in a channel, everyone in the room is going

241
00:13:23,040 --> 00:13:25,520
Speaker 1: to see the message that the words that you are

242
00:13:25,520 --> 00:13:28,640
Speaker 1: typing as soon as you hit return. Yeah, it's not

243
00:13:28,720 --> 00:13:30,559
Speaker 1: real time like, so if you leave that slash out

244
00:13:30,600 --> 00:13:33,240
Speaker 1: instead of the command that you were hoping to execute,

245
00:13:33,280 --> 00:13:36,160
Speaker 1: you're gonna it'll be as if you said, quote unquote

246
00:13:36,200 --> 00:13:38,600
Speaker 1: said that in the room. Yeah, So a forward slash

247
00:13:38,679 --> 00:13:42,560
Speaker 1: proceeds the command, and then any strings that you need

248
00:13:42,600 --> 00:13:45,400
Speaker 1: to include after that. Of course, you would want to

249
00:13:45,440 --> 00:13:47,880
Speaker 1: leave a space in between. So right, So if I

250
00:13:47,920 --> 00:13:50,839
Speaker 1: wanted to create my nickname, I would do slash in

251
00:13:51,040 --> 00:13:54,760
Speaker 1: I C K space John Strickland, Yes, and that would

252
00:13:54,960 --> 00:13:59,440
Speaker 1: change my whatever my generic login name was to John Strickland.

253
00:14:00,280 --> 00:14:04,600
Speaker 1: And then um, if you wanted to join uh the

254
00:14:04,640 --> 00:14:09,319
Speaker 1: text stuff channel, you would do slash join and then

255
00:14:09,320 --> 00:14:13,640
Speaker 1: a space hashtag tech stuff. Right. And there are other

256
00:14:14,000 --> 00:14:16,920
Speaker 1: basic commands like quit clearly that would make you quit

257
00:14:16,960 --> 00:14:19,680
Speaker 1: out of the I r C client help, which would

258
00:14:19,680 --> 00:14:21,720
Speaker 1: get you more information who is, which would give you

259
00:14:21,760 --> 00:14:25,840
Speaker 1: information about a particular person logged in under a handle

260
00:14:25,880 --> 00:14:28,040
Speaker 1: You would do you know, the slash who is all

261
00:14:28,080 --> 00:14:31,000
Speaker 1: one word w H O I S and put in

262
00:14:31,040 --> 00:14:34,080
Speaker 1: the name, which may or may not give you a

263
00:14:34,120 --> 00:14:36,360
Speaker 1: good amount of information. All depends on how the person's

264
00:14:36,520 --> 00:14:41,360
Speaker 1: set his or her account, or who was even work

265
00:14:41,800 --> 00:14:46,000
Speaker 1: if the person has recently changed the nickname or disappeared. UM,

266
00:14:46,000 --> 00:14:50,040
Speaker 1: slash away lets people know that you are not paying

267
00:14:50,240 --> 00:14:52,560
Speaker 1: attention to what's going on in the chat room at

268
00:14:52,560 --> 00:14:54,560
Speaker 1: that time. So maybe you know, have to get up

269
00:14:54,600 --> 00:14:57,120
Speaker 1: and go to the restroom, or make a cup of coffee,

270
00:14:57,360 --> 00:15:00,760
Speaker 1: or put out a fire, or walk a dog, or

271
00:15:00,960 --> 00:15:03,880
Speaker 1: apologize profusely to a spouse. Then that would be a

272
00:15:03,880 --> 00:15:05,760
Speaker 1: good thing to put so that people know that you're

273
00:15:05,800 --> 00:15:09,840
Speaker 1: not paying attention to the screen. I'm sorry what that

274
00:15:09,920 --> 00:15:12,880
Speaker 1: last one happens a lot to me. Um. But then

275
00:15:12,920 --> 00:15:15,440
Speaker 1: there and and I shall say, there's also a way

276
00:15:15,440 --> 00:15:18,400
Speaker 1: of sending private messages to people. You can do slash

277
00:15:18,560 --> 00:15:21,280
Speaker 1: msg and then a message and that sends it instead

278
00:15:21,320 --> 00:15:23,760
Speaker 1: of going to the room in general, it'll send it

279
00:15:23,800 --> 00:15:27,720
Speaker 1: straight to another person. Yeah, that's embarrassing because I thought

280
00:15:27,760 --> 00:15:33,240
Speaker 1: that that was the way to put monet. Yeah, so

281
00:15:33,280 --> 00:15:35,960
Speaker 1: you were like you were like frantically trying to poison

282
00:15:36,000 --> 00:15:37,560
Speaker 1: people and it turns out you were just saying hi,

283
00:15:37,880 --> 00:15:41,960
Speaker 1: yeah exactly, um um, then there and if they were

284
00:15:42,000 --> 00:15:45,840
Speaker 1: rebuffing my attempts to poison them with MSG, they could

285
00:15:45,840 --> 00:15:51,040
Speaker 1: be slash ignoring me. Yes, that's a very useful uh command.

286
00:15:51,080 --> 00:15:53,560
Speaker 1: If you ever run into trolls them and you know

287
00:15:53,680 --> 00:15:57,520
Speaker 1: you don't maybe the the administrator of that channel, the

288
00:15:57,520 --> 00:16:00,120
Speaker 1: the operator that channel doesn't necessarily care if there is

289
00:16:00,120 --> 00:16:04,520
Speaker 1: a trollish person in there. Ignore is your friend. And

290
00:16:04,680 --> 00:16:06,960
Speaker 1: if you are a channel operator, if you're the person

291
00:16:07,000 --> 00:16:10,760
Speaker 1: who owns the administrative power of that channel, you have

292
00:16:10,840 --> 00:16:13,760
Speaker 1: other commands that are at your disposal, including things like

293
00:16:13,960 --> 00:16:16,720
Speaker 1: you know, usually there's a kick command where you can

294
00:16:16,800 --> 00:16:21,000
Speaker 1: kick people from the room if they're being really obnoxious um,

295
00:16:21,120 --> 00:16:23,080
Speaker 1: and I'm along with other ones. You can even ban

296
00:16:23,560 --> 00:16:27,240
Speaker 1: people from a room. And sometimes there's different settings like

297
00:16:27,280 --> 00:16:30,560
Speaker 1: you can ban uh that one user or you can

298
00:16:30,600 --> 00:16:34,600
Speaker 1: ban anyone from that particular users domain. You can get

299
00:16:34,640 --> 00:16:38,960
Speaker 1: pretty nasty um, depending on the the the rights that

300
00:16:39,080 --> 00:16:43,400
Speaker 1: the channel opp has. And also you can accidentally or well,

301
00:16:43,440 --> 00:16:47,080
Speaker 1: you can give other people operator rights as well. Can

302
00:16:47,560 --> 00:16:50,160
Speaker 1: and if you're not careful, you can give other people

303
00:16:50,200 --> 00:16:53,520
Speaker 1: operator rights and relinquish your own rights, and the next

304
00:16:53,520 --> 00:16:55,680
Speaker 1: thing you know, you're at the whim of somebody else.

305
00:16:56,720 --> 00:16:59,200
Speaker 1: And they're even ways where I mean, if if people

306
00:16:59,400 --> 00:17:02,800
Speaker 1: trick you into typing a certain kind of string, that's

307
00:17:02,880 --> 00:17:05,479
Speaker 1: essentially what happens. You give over the right of not

308
00:17:05,520 --> 00:17:08,760
Speaker 1: only of the channel, you could actually give over the

309
00:17:08,800 --> 00:17:12,440
Speaker 1: ability to control the client, and the person could control

310
00:17:12,520 --> 00:17:15,040
Speaker 1: your I r C client. You could you could accidentally

311
00:17:15,040 --> 00:17:18,280
Speaker 1: relinquished control if you if you posted the right command

312
00:17:18,320 --> 00:17:21,320
Speaker 1: in there. You know, honestly, I've never heard of that happening. Yeah,

313
00:17:21,359 --> 00:17:23,600
Speaker 1: it's um, it's actually if you look at there's a

314
00:17:23,640 --> 00:17:26,280
Speaker 1: couple of really good I r C Frequently asked question

315
00:17:26,320 --> 00:17:28,679
Speaker 1: files out there on the on the web, and a

316
00:17:28,720 --> 00:17:30,520
Speaker 1: few of them will tell you. They don't tell you

317
00:17:30,560 --> 00:17:32,800
Speaker 1: specifically what the string is, but they will say, you know,

318
00:17:32,880 --> 00:17:36,120
Speaker 1: do not if someone gives you a string of seemingly

319
00:17:36,240 --> 00:17:38,879
Speaker 1: random commands and says you need to type this in

320
00:17:38,960 --> 00:17:42,000
Speaker 1: because it'll, you know, solve your problem or whatever. You

321
00:17:42,000 --> 00:17:45,120
Speaker 1: should not just automatically do that, because there are commands

322
00:17:45,160 --> 00:17:47,840
Speaker 1: that can end up coming back to haunt you when

323
00:17:47,880 --> 00:17:50,600
Speaker 1: you hand over. Essentially you hand the steering wheel over

324
00:17:50,640 --> 00:17:53,400
Speaker 1: to a maniac and then they laugh at you and say,

325
00:17:53,440 --> 00:17:56,040
Speaker 1: ha ha, we tricked you, and now you know all

326
00:17:56,119 --> 00:17:59,240
Speaker 1: your base belong to us. Someone set us up the bomb.

327
00:17:59,600 --> 00:18:04,200
Speaker 1: Speaking of which, should we mentioned bots? Bots? Yeah, alright,

328
00:18:04,200 --> 00:18:09,359
Speaker 1: so bots are and that's an automated program and automated essentially,

329
00:18:09,400 --> 00:18:12,280
Speaker 1: it's like like a script script. Yeah, and it's a

330
00:18:12,280 --> 00:18:15,000
Speaker 1: script that often takes the form of what looks to

331
00:18:15,080 --> 00:18:18,680
Speaker 1: be a normal I R C. Chatter. Yeah, I mean,

332
00:18:18,760 --> 00:18:21,320
Speaker 1: and basically they can they can stay in the channel.

333
00:18:21,359 --> 00:18:24,639
Speaker 1: Say if if you own a very popular channel, um,

334
00:18:24,840 --> 00:18:26,560
Speaker 1: and you don't want to lose control of it, but

335
00:18:26,640 --> 00:18:29,919
Speaker 1: everyone's going to bed, your bought could be sitting in

336
00:18:29,960 --> 00:18:32,400
Speaker 1: there for you. And uh. As a matter of fact,

337
00:18:32,400 --> 00:18:36,159
Speaker 1: a bot can can automatically be configured to give people

338
00:18:37,359 --> 00:18:40,080
Speaker 1: operator privileges. Yeah, you can, especially you know, like certain

339
00:18:40,080 --> 00:18:44,040
Speaker 1: people can you know, your buddies, your most trusted buddies

340
00:18:44,080 --> 00:18:46,480
Speaker 1: when they pop in and it will automatically give them ops.

341
00:18:47,040 --> 00:18:48,800
Speaker 1: And then as soon as they do that, you know

342
00:18:49,119 --> 00:18:51,880
Speaker 1: they're running a channel even when you're not there. Yeah,

343
00:18:51,960 --> 00:18:54,680
Speaker 1: you can script a bot to do lots of different things.

344
00:18:54,720 --> 00:18:57,359
Speaker 1: It doesn't have to just uh, you know, it doesn't

345
00:18:57,359 --> 00:18:59,920
Speaker 1: have to just sit there. In other words, like the reason,

346
00:19:00,200 --> 00:19:01,840
Speaker 1: as Plett was pointing out, the reason why you would

347
00:19:01,880 --> 00:19:04,359
Speaker 1: want to have a bot sit there would be so

348
00:19:04,440 --> 00:19:07,440
Speaker 1: that you could hold on to a certain channel name

349
00:19:07,480 --> 00:19:09,159
Speaker 1: and you wouldn't have to worry about someone stealing it

350
00:19:09,200 --> 00:19:12,200
Speaker 1: once you logged off. You would have a squatter essentially,

351
00:19:12,640 --> 00:19:14,879
Speaker 1: But you could also give a bot like I've seen.

352
00:19:15,000 --> 00:19:17,760
Speaker 1: Um there's one I R C. Each chat room I

353
00:19:17,800 --> 00:19:21,280
Speaker 1: occasionally go into that has a bot that what its

354
00:19:21,359 --> 00:19:26,879
Speaker 1: main purpose is to scan for for any instance of

355
00:19:27,000 --> 00:19:32,199
Speaker 1: foul language. So it essentially is is uh scanning everyone's

356
00:19:32,600 --> 00:19:36,040
Speaker 1: lines and if words that match up to its database

357
00:19:36,160 --> 00:19:39,760
Speaker 1: of naughty words pop up, it automatically boots you from

358
00:19:39,800 --> 00:19:43,040
Speaker 1: the room. So if you were to say something that

359
00:19:43,160 --> 00:19:44,920
Speaker 1: was you know, like if you were to to to

360
00:19:45,400 --> 00:19:48,440
Speaker 1: say an obscenity, type in an obscenity and and into

361
00:19:48,480 --> 00:19:51,920
Speaker 1: the main room, UH, it would notice it and kick

362
00:19:51,960 --> 00:19:54,280
Speaker 1: you from the room. Um. Other things that it would

363
00:19:54,400 --> 00:19:56,159
Speaker 1: kick you for are things like if you typed in

364
00:19:56,240 --> 00:20:01,000
Speaker 1: all caps, because that's the equivalent of counting online I

365
00:20:01,000 --> 00:20:05,320
Speaker 1: mean in text based chat rooms, all upper case is

366
00:20:05,400 --> 00:20:09,080
Speaker 1: like you're yelling, and just like any other party, no

367
00:20:09,080 --> 00:20:11,960
Speaker 1: one wants to be around the guy or or girl

368
00:20:12,359 --> 00:20:14,440
Speaker 1: who is screaming at the top of his or her

369
00:20:14,520 --> 00:20:19,200
Speaker 1: lungs uh and thinks it's funny. Yes, that is correct.

370
00:20:19,200 --> 00:20:23,440
Speaker 1: I can say that specifically after working for now as

371
00:20:23,600 --> 00:20:26,240
Speaker 1: the time of recording this podcast five weekends at the

372
00:20:26,280 --> 00:20:29,119
Speaker 1: Renaissance Festival. The loud ones are the ones that always

373
00:20:29,160 --> 00:20:32,040
Speaker 1: think they are the funniest people, and they are always

374
00:20:32,040 --> 00:20:37,040
Speaker 1: wrong unless it's me right. There is that exception to

375
00:20:37,080 --> 00:20:40,600
Speaker 1: the rule. So if you wanted to join I r C,

376
00:20:41,080 --> 00:20:43,720
Speaker 1: you don't have to really do all that much. As

377
00:20:43,720 --> 00:20:45,880
Speaker 1: long as you're on the internet, you should be able

378
00:20:45,920 --> 00:20:49,400
Speaker 1: to uh, you know, choose a client. There are many

379
00:20:49,440 --> 00:20:53,040
Speaker 1: many pre I r C clients or as Jonathan pointed

380
00:20:53,040 --> 00:20:55,320
Speaker 1: out earlier, you can go on the web to certain

381
00:20:55,359 --> 00:20:59,239
Speaker 1: sites and access from there, um you know, they are

382
00:20:59,400 --> 00:21:02,560
Speaker 1: their clients. Also that you can pay for shareware clients

383
00:21:02,600 --> 00:21:05,399
Speaker 1: if if you're really, uh really getting into the I

384
00:21:05,520 --> 00:21:08,840
Speaker 1: r C thing, they might have special you know, especially

385
00:21:08,840 --> 00:21:13,520
Speaker 1: configured windows that you can use that just make life easier. Um.

386
00:21:14,119 --> 00:21:16,359
Speaker 1: And they're you know, they're pretty you can even you

387
00:21:16,359 --> 00:21:20,399
Speaker 1: can even find them for smartphones now. Um. Although I

388
00:21:20,400 --> 00:21:24,640
Speaker 1: wouldn't recommend I r C and driving at the same time.

389
00:21:24,680 --> 00:21:27,359
Speaker 1: Actually I wouldn't recommend being on I r C on

390
00:21:27,400 --> 00:21:31,000
Speaker 1: a mobile phone anyway, because teeny tiny it's so hard

391
00:21:31,040 --> 00:21:33,320
Speaker 1: to keep up with, especially if you if you tend

392
00:21:33,359 --> 00:21:36,400
Speaker 1: to frequent rooms that have a lot of people in them.

393
00:21:36,840 --> 00:21:39,800
Speaker 1: But the one I was talking about earlier, it it

394
00:21:39,960 --> 00:21:42,640
Speaker 1: often has more than a hundred and sometimes more than

395
00:21:42,680 --> 00:21:45,520
Speaker 1: four hundred, and it peaked times nearly a thousand people

396
00:21:45,520 --> 00:21:49,520
Speaker 1: in it on a significant for an IRC chat room. Yeah,

397
00:21:49,560 --> 00:21:52,200
Speaker 1: this is a specific chat room that's a fan chat

398
00:21:52,320 --> 00:21:56,680
Speaker 1: room for a technology podcast that I listened to while

399
00:21:56,680 --> 00:22:00,600
Speaker 1: they're doing it live. Unlike unlike our technique where we

400
00:22:00,720 --> 00:22:02,760
Speaker 1: pre record everything and no one gets to hear it

401
00:22:02,760 --> 00:22:05,720
Speaker 1: while we're doing it, this other podcast they stream it

402
00:22:05,800 --> 00:22:10,080
Speaker 1: live and then upload the the actual podcast. Right, I

403
00:22:10,119 --> 00:22:12,320
Speaker 1: think I know the one that you're talking about, the

404
00:22:12,359 --> 00:22:14,399
Speaker 1: one I got to be a guest host on. It

405
00:22:14,440 --> 00:22:16,639
Speaker 1: should be a buzz out loud for seen. It might

406
00:22:16,680 --> 00:22:19,280
Speaker 1: as well go ahead and say it. So anyway, occasionally

407
00:22:19,280 --> 00:22:20,960
Speaker 1: I'll be in the that I r C chat room

408
00:22:21,080 --> 00:22:23,680
Speaker 1: and uh, I've tried to log in through my phone before,

409
00:22:23,760 --> 00:22:25,760
Speaker 1: and the problem, of course is there's two problems. One,

410
00:22:25,800 --> 00:22:28,440
Speaker 1: it's really tiny, so it's hard to read. But also

411
00:22:29,240 --> 00:22:32,280
Speaker 1: because the chat room is scrolling so quickly, and because

412
00:22:32,320 --> 00:22:35,160
Speaker 1: my phone is just occasionally getting updates through the cell

413
00:22:35,200 --> 00:22:37,720
Speaker 1: tower because I'm not I don't have the WiFi turned

414
00:22:37,720 --> 00:22:42,800
Speaker 1: on necessarily. Um, you know, the the updates come in little,

415
00:22:42,960 --> 00:22:45,879
Speaker 1: uh in little bursts. So not only are lots and

416
00:22:45,920 --> 00:22:48,399
Speaker 1: lots of people talking, but I'm getting them, you know,

417
00:22:48,480 --> 00:22:51,639
Speaker 1: all at once, and so everything scrolls off the screen

418
00:22:52,119 --> 00:22:53,760
Speaker 1: and there might be something that I was trying to

419
00:22:53,800 --> 00:22:56,480
Speaker 1: read that was reference to me, and then you know,

420
00:22:56,680 --> 00:22:59,800
Speaker 1: I have maybe a couple of seconds to read it

421
00:23:00,040 --> 00:23:03,240
Speaker 1: and process it before it's gone. And so it's kind

422
00:23:03,240 --> 00:23:06,320
Speaker 1: of a frustrating experience. Another frustrating experience with I r C.

423
00:23:06,480 --> 00:23:10,480
Speaker 1: Something else that can happen is net splitting. Oh yes,

424
00:23:10,680 --> 00:23:12,760
Speaker 1: you know you're familiar with the net splits. Net splits

425
00:23:12,760 --> 00:23:15,240
Speaker 1: are terrible. Yeah. That that that actually used to happen

426
00:23:15,240 --> 00:23:18,160
Speaker 1: to me on bitnet as well. Where part of the uh, well,

427
00:23:18,400 --> 00:23:21,560
Speaker 1: if you remember our podcast a little while ago on

428
00:23:21,600 --> 00:23:25,200
Speaker 1: how the Internet works, essentially we went through the infornet,

429
00:23:25,280 --> 00:23:29,239
Speaker 1: the internet infrastructure. Uh, you know, everything is connected to

430
00:23:29,400 --> 00:23:33,040
Speaker 1: everything else and multiple redundant connections and then every once

431
00:23:33,080 --> 00:23:36,480
Speaker 1: in a while, part of the net gets separated from

432
00:23:36,480 --> 00:23:38,280
Speaker 1: the other part of the net, and they have to

433
00:23:38,280 --> 00:23:41,600
Speaker 1: find an alternate route to move that data through. And

434
00:23:41,720 --> 00:23:44,400
Speaker 1: but in the meantime, there's an interruption in service. Yes,

435
00:23:44,440 --> 00:23:47,879
Speaker 1: and you're going, what happened, Yeah, net splits from the

436
00:23:48,000 --> 00:23:49,960
Speaker 1: From your perspective, if you're in an I r C

437
00:23:50,160 --> 00:23:52,960
Speaker 1: chat room and and a net split happens, it seems

438
00:23:52,960 --> 00:23:55,760
Speaker 1: really weird. It seems like tons of people just left

439
00:23:55,800 --> 00:23:59,520
Speaker 1: the room for no apparent reason. Not everybody, because the

440
00:23:59,560 --> 00:24:01,920
Speaker 1: way I r C works is that there's it's actually

441
00:24:01,960 --> 00:24:04,719
Speaker 1: a network each I r C. There's there're like multiple

442
00:24:04,720 --> 00:24:08,199
Speaker 1: I RC networks on multiple servers. Yes, and you're not

443
00:24:08,320 --> 00:24:10,159
Speaker 1: all on the same server, even if you're on the

444
00:24:10,200 --> 00:24:12,080
Speaker 1: same network. So you could all be on the same

445
00:24:12,200 --> 00:24:14,840
Speaker 1: channel chatting, but you're not necessarily all logged into the

446
00:24:14,840 --> 00:24:17,880
Speaker 1: same server. You're logged into the same network. So there

447
00:24:17,920 --> 00:24:19,680
Speaker 1: might be some people that are logged onto one server

448
00:24:19,760 --> 00:24:21,840
Speaker 1: on the West coast, you're logged into another server on

449
00:24:21,880 --> 00:24:25,080
Speaker 1: the East coast of I'm talking about the United States,

450
00:24:25,080 --> 00:24:29,000
Speaker 1: but really this applies anywhere. And let's say that the

451
00:24:29,040 --> 00:24:32,000
Speaker 1: connections between those two servers get severed for some reason.

452
00:24:32,119 --> 00:24:37,120
Speaker 1: Something somewhere along the pathway fails. Uh. You would each

453
00:24:37,160 --> 00:24:41,120
Speaker 1: be in your own instance of that network, that channel,

454
00:24:41,320 --> 00:24:44,760
Speaker 1: and to you, it looks like half the room just disappeared.

455
00:24:44,800 --> 00:24:46,920
Speaker 1: The other half still they're chatting, but you're like, where

456
00:24:46,960 --> 00:24:49,760
Speaker 1: did everyone else goes? They're the same way, except they're

457
00:24:49,760 --> 00:24:52,200
Speaker 1: on the other side. They're like, where did everybody? Where

458
00:24:52,240 --> 00:24:56,840
Speaker 1: did all those guys go? Once the connections get um corrected,

459
00:24:57,240 --> 00:24:59,719
Speaker 1: you know, once the data finds a new path to follow,

460
00:25:00,240 --> 00:25:03,480
Speaker 1: everything gets reabsorbed, and suddenly the room is is what

461
00:25:03,720 --> 00:25:07,840
Speaker 1: it's normal size again, there's you know, everyone's together. Uh.

462
00:25:07,920 --> 00:25:10,600
Speaker 1: It can be very frustrating, particularly like I was saying,

463
00:25:10,640 --> 00:25:12,240
Speaker 1: you know that that's seen that one that I go

464
00:25:12,359 --> 00:25:17,000
Speaker 1: to when that splits happen. I'm always on the server

465
00:25:17,240 --> 00:25:20,040
Speaker 1: that is not with the main room, but not with

466
00:25:20,119 --> 00:25:22,720
Speaker 1: like the all the hosts and all the most of

467
00:25:22,760 --> 00:25:26,240
Speaker 1: the people who with whom I chat. They are fine.

468
00:25:26,720 --> 00:25:31,159
Speaker 1: They're all together. Me and like five other folks you know,

469
00:25:31,400 --> 00:25:33,600
Speaker 1: are sitting there twiddling our thumbs and thinking, I bet

470
00:25:33,680 --> 00:25:36,000
Speaker 1: there's lots of funny stuff being talked about right now,

471
00:25:36,080 --> 00:25:39,040
Speaker 1: but I can't see it. Do you think they're trying

472
00:25:39,080 --> 00:25:41,720
Speaker 1: to tell you something? I have no idea, but at

473
00:25:41,720 --> 00:25:43,679
Speaker 1: any rate, there's no way for you to correct it

474
00:25:43,720 --> 00:25:45,879
Speaker 1: on your end waiting for the Yeah, you have to

475
00:25:45,920 --> 00:25:49,920
Speaker 1: wait till the data can find a new path um.

476
00:25:49,960 --> 00:25:52,800
Speaker 1: And I really did not have a lot of experience

477
00:25:52,800 --> 00:25:55,800
Speaker 1: with I r C until fairly recently, because as it

478
00:25:55,800 --> 00:25:57,320
Speaker 1: turns out, you know, you said that I r C

479
00:25:57,440 --> 00:25:59,800
Speaker 1: it was kind of your introduction to the Internet. My

480
00:26:00,040 --> 00:26:02,920
Speaker 1: production was tell neet. I was using tell neet protocol

481
00:26:03,080 --> 00:26:07,159
Speaker 1: tellnet into chat rooms, so you you would log in

482
00:26:07,240 --> 00:26:11,520
Speaker 1: remotely to some computer that's running a chat room program.

483
00:26:12,160 --> 00:26:16,280
Speaker 1: So it's different from the I r C network model.

484
00:26:17,119 --> 00:26:20,680
Speaker 1: And so, uh it's a totally different set of commands

485
00:26:20,720 --> 00:26:23,679
Speaker 1: as well, which was made it very confusing for me

486
00:26:23,720 --> 00:26:25,560
Speaker 1: when I first started using I r C because I

487
00:26:25,600 --> 00:26:29,320
Speaker 1: was thinking about the old tell net commands and uh, yeah,

488
00:26:29,359 --> 00:26:30,920
Speaker 1: you can always tell a tell neet or on an

489
00:26:30,920 --> 00:26:32,520
Speaker 1: I r C, or at least you used to. It

490
00:26:32,560 --> 00:26:35,000
Speaker 1: doesn't happen as much now, but you can always see

491
00:26:35,040 --> 00:26:39,000
Speaker 1: because they would say things like say hi there, you know,

492
00:26:39,119 --> 00:26:41,080
Speaker 1: like they would actually they're typing in the command that

493
00:26:41,119 --> 00:26:43,160
Speaker 1: you would normally have to tighten type and tell neet

494
00:26:43,240 --> 00:26:45,720
Speaker 1: in order to say something. And all the I r

495
00:26:45,760 --> 00:26:48,159
Speaker 1: crs are like, look at this bozo doesn't know he

496
00:26:48,200 --> 00:26:50,520
Speaker 1: doesn't have to type say or you know, doing a

497
00:26:50,920 --> 00:26:54,080
Speaker 1: quotation mark at the front of his sentence. And so yes,

498
00:26:54,119 --> 00:26:56,960
Speaker 1: I was that bozo. I still am that bozo. It's

499
00:26:57,000 --> 00:26:59,720
Speaker 1: just that now I know better. What does never mind

500
00:26:59,800 --> 00:27:02,879
Speaker 1: the UM that's the big red nose. Yes, and the

501
00:27:02,920 --> 00:27:04,840
Speaker 1: fact that every day I played the grand Prize game

502
00:27:04,880 --> 00:27:10,440
Speaker 1: at my cubicle. Yes, anyhow, Yeah, it's it's uh, it's

503
00:27:10,440 --> 00:27:12,280
Speaker 1: actually quite impressive. I think in a lot of ways

504
00:27:12,320 --> 00:27:15,360
Speaker 1: that this, uh, this chat protocol is still as popular

505
00:27:15,400 --> 00:27:18,120
Speaker 1: as it is UM. But it doesn't show any time

506
00:27:18,160 --> 00:27:21,840
Speaker 1: any signs of of falling by the wayside anytime. Seene

507
00:27:21,880 --> 00:27:23,800
Speaker 1: As a matter of fact, all the just about all

508
00:27:23,800 --> 00:27:28,239
Speaker 1: of the major UM multi protocol chat clients offer an

509
00:27:28,280 --> 00:27:31,320
Speaker 1: I r C option. And we didn't even go into

510
00:27:31,320 --> 00:27:32,960
Speaker 1: the fact that you can you can use I r

511
00:27:33,040 --> 00:27:37,679
Speaker 1: C to send files even if you were. We were

512
00:27:37,720 --> 00:27:40,240
Speaker 1: mainly talking about the chat aspect, but there there's a

513
00:27:40,280 --> 00:27:42,320
Speaker 1: lot more to it than what we're going into. We're

514
00:27:42,320 --> 00:27:45,520
Speaker 1: just talking about the main use that or I think

515
00:27:45,960 --> 00:27:48,119
Speaker 1: the most popular use for I r C, which is

516
00:27:48,160 --> 00:27:53,680
Speaker 1: to have conversation. Uh, well, that's a good conversation right there,

517
00:27:53,840 --> 00:27:55,560
Speaker 1: and we're gonna wrap it up. I do not have

518
00:27:55,600 --> 00:27:57,640
Speaker 1: any listener mail to follow it up with. I've got

519
00:27:57,680 --> 00:27:59,840
Speaker 1: tons of listener mail, don't get me wrong, but they're

520
00:27:59,840 --> 00:28:03,840
Speaker 1: all all asking for for a podcast on a specific topic.

521
00:28:04,000 --> 00:28:06,439
Speaker 1: So it's it's nothing that we could address very quickly, right,

522
00:28:06,600 --> 00:28:08,600
Speaker 1: So we're just gonna wrap this up. Thanks a lot

523
00:28:08,720 --> 00:28:11,160
Speaker 1: for that request. It was a fun thing to talk about.

524
00:28:11,200 --> 00:28:13,679
Speaker 1: We like looking at the history of the Internet and

525
00:28:13,760 --> 00:28:17,199
Speaker 1: the the early protocols that are still around um and

526
00:28:17,240 --> 00:28:20,520
Speaker 1: the early uses. So keep those requests coming in and uh,

527
00:28:21,000 --> 00:28:23,399
Speaker 1: Chris and I will talk to you again really soon.

528
00:28:25,600 --> 00:28:28,120
Speaker 1: For more on this and thousands of other topics, visit

529
00:28:28,160 --> 00:28:31,600
Speaker 1: how stuff Works dot com and be sure to check

530
00:28:31,640 --> 00:28:33,680
Speaker 1: out the new tech stuff blogs now on the house

531
00:28:33,680 --> 00:28:40,800
Speaker 1: Stuff Works homepage. Brought to you by the reinvented two

532
00:28:40,800 --> 00:28:43,360
Speaker 1: thousand twelve camera. It's ready, are you