WEBVTT

00:00.000 --> 00:09.440
This is dedicated to all the hackers and the crackers, to the hackers and the crackers.

00:09.760 --> 00:15.520
I see in binary, I speak source code, step on my toes, I'll post a million jpegs of you

00:15.520 --> 00:20.800
in a fag pose, in your digital stance, getting firewalls hoes, cause I'm riding the net in

00:20.800 --> 00:26.440
my six foes, I was a dick with my 56, now with my cable I'm able to get that stable,

00:26.440 --> 00:31.740
on the out, my name is Ace and I'm a Leo, on the digital highway, my name is Neo and

00:31.740 --> 00:37.240
I'm a hero, in a flash I'll screw you on burning dreamcast, you need some ISO, let me through

00:37.240 --> 00:42.680
my hard drive rifle, our exchange you could never stifle, in a digital hug, you just caught

00:42.680 --> 00:48.940
the love bug, I bootlegged your CD, I caused the fight between Un and Jay-Z, cause CG, it's

00:48.940 --> 00:53.380
all gonna be free, whether we take it by force or we take it nicely, you feel that rattle

00:53.380 --> 00:58.140
in your bones, when I tell you we just hacked out Jones, and NASDAQ leaves you flat on your

00:58.140 --> 01:03.560
back, cause I am he who loves to hack and crack, cause I am he who loves to hack and crack.

01:04.000 --> 01:11.180
This is dedicated to the hackers and the crackers, serial phones, source codes, ISO, RAM, SIS,

01:11.180 --> 01:14.200
this is dedicated to the hackers and the crackers.

01:15.060 --> 01:22.000
Hello and welcome to Binary Revolution Radio, episode 109, with today's date, August 16th,

01:22.000 --> 01:27.760
2005. I'm Black Ratchet, and there's no Strom this week, he sort of went missing, he's been

01:27.760 --> 01:33.280
arrested by feds, and currently down in Guantanamo Bay or something. So, you know, not theory was

01:33.280 --> 01:35.460
very kind, and decided to help us out tonight.

01:36.540 --> 01:41.980
Yeah, and I'm through with all my Verizon problems, so now this can finally be a show about computers.

01:42.260 --> 01:43.940
We don't need to talk anything about phones tonight.

01:43.940 --> 01:46.540
But I thought this was a freaking show.

01:48.060 --> 01:48.260
Oh.

01:48.680 --> 01:49.060
It is?

01:49.320 --> 01:50.680
Oh, I don't know.

01:50.680 --> 01:51.420
Oh, well, I don't know.

01:52.260 --> 01:55.540
No, no, no. Tonight is an all-computer episode.

01:56.200 --> 01:56.760
Apparently, Strom and I are...

01:56.760 --> 01:59.560
Why don't you want to talk about fishing? We can talk about fishing or something.

01:59.560 --> 02:00.280
Fishing would be fun.

02:00.680 --> 02:02.920
Oh, time of fishing, the P-H or the F.

02:04.120 --> 02:06.520
Oh. Yeah, maybe we should not talk about that.

02:07.040 --> 02:09.920
I don't know. How to own Korea or something.

02:11.260 --> 02:13.400
Actually, no. How to own the United States from Korea.

02:14.340 --> 02:15.220
Yeah, that's more like it.

02:15.220 --> 02:18.720
No. Anyway, this is an all-computer episode tonight.

02:18.880 --> 02:21.340
We're going to try to steer away from it.

02:21.860 --> 02:25.440
Pick a nice, juicy, meaty computer subject for all you people out there

02:25.440 --> 02:28.480
complaining that Strom and I are a little too phone-friendly

02:28.480 --> 02:30.920
or we're turning this into Freak Factor

02:30.920 --> 02:33.900
or all your other complaints, so sit down and step away.

02:33.900 --> 02:36.080
Oh, I really hope you're not turning it into Freak Factor, dude.

02:37.080 --> 02:39.820
No. Actually, you know, we actually have an all-section

02:39.820 --> 02:42.560
where we're just going to call up Walmart and try to get on their PA system.

02:43.480 --> 02:44.780
Oh, that would be so neat.

02:44.960 --> 02:48.260
Oh, man. I hear if you hit, like, pound nine, you'll get there.

02:48.460 --> 02:49.000
Want to try it?

02:50.860 --> 02:56.040
Actually, Freak Factor may make a resurgence.

02:56.040 --> 02:58.960
I might have some time freeing up

02:58.960 --> 03:01.880
as I move Freak Factor to a new mystery day.

03:02.340 --> 03:06.120
Yeah, actually, it seems to be dying out.

03:06.120 --> 03:09.860
Yeah, you know, because nobody's ever around to host it

03:09.860 --> 03:13.240
and that's mostly my fault because the show was, like, my idea

03:13.240 --> 03:15.860
and Snag's off doing his own thing.

03:16.380 --> 03:20.480
So if I'm not there to run it, you know, it kind of goes nowhere very quickly,

03:20.540 --> 03:22.280
as you can tell if you've listened to any of them.

03:22.480 --> 03:27.640
Yeah, I got an IM from Cypher X on about 11.30 last Saturday.

03:27.840 --> 03:29.100
He's like, where are you?

03:29.160 --> 03:30.720
And I was, you know, driving home.

03:30.840 --> 03:32.740
And I said, oh, I'm in the car. I'm on my sidekick.

03:33.080 --> 03:35.560
Oh, my God, no one's there to run Freak Factor.

03:35.560 --> 03:36.280
We're not streaming.

03:36.480 --> 03:37.820
And I was like, oh, okay.

03:38.280 --> 03:40.200
So I had to run home and bridge the conferences

03:40.200 --> 03:42.040
because someone forgot to do it.

03:42.100 --> 03:42.980
I wonder who that could be.

03:44.680 --> 03:46.220
Oh, no, that's me.

03:46.420 --> 03:47.740
I didn't forget to do it.

03:47.820 --> 03:49.800
I just didn't want to.

03:50.520 --> 03:52.760
So, you know, what can I say about that?

03:52.800 --> 03:54.980
The amount of love that non-theory has for Freak Factor.

03:55.680 --> 03:57.600
No, no, that's not true.

03:57.800 --> 04:00.100
The thing about it was I was at a wedding

04:00.100 --> 04:01.960
and I was very drunk by that point.

04:01.960 --> 04:05.300
So there was no way I could possibly get onto my phone

04:05.300 --> 04:08.840
and use Putty to get in there and bridge the conferences.

04:09.260 --> 04:10.300
I've got to say that would be pretty elite.

04:10.560 --> 04:11.800
You got Putty running on your phone?

04:13.080 --> 04:13.560
Oh, yeah.

04:13.700 --> 04:15.860
The phones that are not pieces of crap like the sidekick,

04:15.940 --> 04:16.520
they run Putty.

04:17.060 --> 04:18.440
What kind of episode would this be

04:18.440 --> 04:20.400
without not theory talking about the sidekick?

04:21.520 --> 04:22.180
Oh, yeah.

04:22.540 --> 04:23.680
We're going toward phones.

04:23.740 --> 04:24.480
We're going toward phones.

04:24.640 --> 04:27.260
So let's go segue to the next topic.

04:27.260 --> 04:28.820
I have a bit of an announcement.

04:29.880 --> 04:32.800
Rant Radio is going to start pulling our feed from our podcast,

04:33.100 --> 04:35.540
and that's how it's going to grab our episodes.

04:36.380 --> 04:38.580
So I think this is fine and dandy.

04:38.760 --> 04:40.480
I only have to upload one episode now.

04:40.600 --> 04:42.020
I used to have to make two.

04:42.140 --> 04:44.340
I'd send one over to DDP Hack Radio.

04:44.840 --> 04:46.340
Then I'd have to log into Rant Radio

04:46.340 --> 04:47.560
and upload the second episode.

04:47.740 --> 04:49.480
It'd be two settings,

04:49.840 --> 04:52.640
two bits and pieces I have to set,

04:52.700 --> 04:54.120
and two MP3s I have to export.

04:54.620 --> 04:55.700
So now it's easy.

04:55.700 --> 04:57.800
You only have to do one episode, pull it off BINREV.

04:58.600 --> 05:02.520
However, I realized that we update our podcast

05:02.520 --> 05:04.260
after the episode airs.

05:05.140 --> 05:07.040
Actually, Stank actually pointed this out to me,

05:07.080 --> 05:07.660
so it wasn't me.

05:08.580 --> 05:10.580
So this is a bit of a dilemma.

05:11.000 --> 05:13.220
Either I need to update the podcast early,

05:13.480 --> 05:15.320
or Rant Radio is going to be a week behind

05:15.320 --> 05:16.760
of the current episode.

05:18.820 --> 05:20.360
So after much debate,

05:20.460 --> 05:23.580
I decided to let Rant Radio be a week behind.

05:23.580 --> 05:27.460
And we update our podcast early.

05:27.680 --> 05:30.580
No one's going to listen to the live streaming broadcast

05:30.580 --> 05:33.160
we do at 9.30 every Tuesday night.

05:34.000 --> 05:36.560
So no one will want to listen to it.

05:36.700 --> 05:37.860
What's the point of doing it?

05:38.060 --> 05:39.680
So basically what's going to happen is

05:39.680 --> 05:41.420
Rant Radio is now going to be a week behind

05:41.420 --> 05:44.220
the actual live episode.

05:44.220 --> 05:48.360
And right now the only place to get your piping hot,

05:48.560 --> 05:50.920
steaming, fresh out of the oven BINREV radio

05:50.920 --> 05:53.700
is going to be on the DDP hack radio stream

05:53.700 --> 05:55.640
at radio.BINREV.com.

05:55.900 --> 05:57.280
9.30 every Tuesday night.

05:57.440 --> 05:58.140
Be there, be square.

05:58.840 --> 05:59.640
All that other jazz.

06:00.500 --> 06:01.200
Isn't it exciting?

06:01.880 --> 06:04.280
Yeah, I think that is true or right.

06:04.740 --> 06:07.980
Well, you know, Rant Radio does have a large user base,

06:08.020 --> 06:08.760
and it's good over there.

06:09.120 --> 06:10.820
And it'd be cool to give them the live episode also.

06:11.700 --> 06:12.280
I still haven't.

06:12.360 --> 06:13.860
I might contact them and say,

06:14.020 --> 06:16.920
oh, geez, we don't do this until after our episode's aired,

06:17.000 --> 06:18.020
so you're going to be a week behind

06:18.020 --> 06:19.520
and see what they say.

06:19.720 --> 06:22.560
But, you know, hey, DDP hack radio,

06:22.640 --> 06:23.200
that's where it's at.

06:23.360 --> 06:23.940
BINREV.com.

06:24.420 --> 06:24.740
Yeah.

06:25.000 --> 06:28.260
Yeah, I'm not saying anything bad about Rant Radio.

06:28.260 --> 06:29.280
I think Rant Radio is awesome.

06:29.580 --> 06:31.960
But, you know, it's our show,

06:32.180 --> 06:33.160
and it's our station,

06:33.340 --> 06:34.480
so it should be there first.

06:34.900 --> 06:35.000
Yeah.

06:35.320 --> 06:36.040
And plus, you know,

06:36.080 --> 06:37.260
if we start flooding it with listeners,

06:37.260 --> 06:38.220
listeners, you know,

06:38.260 --> 06:39.760
Nick84 will just start freaking out.

06:39.880 --> 06:40.860
That'll be fun to watch.

06:41.840 --> 06:42.600
Oh, yeah.

06:42.740 --> 06:44.480
Oh, my God, the stream has 50 people.

06:45.760 --> 06:47.300
Yeah, is the limit beyond 50 now?

06:47.380 --> 06:49.580
Because I'm not really sure that it is.

06:50.260 --> 06:50.860
I forget.

06:50.960 --> 06:51.840
I think it's only at 50.

06:51.920 --> 06:52.320
I'm not sure.

06:53.060 --> 06:53.680
I don't know.

06:53.680 --> 06:56.680
I don't understand telling me that he thought he changed it, but...

06:56.680 --> 06:58.340
I thought he bumped it up to 50.

06:58.520 --> 06:59.500
I don't know.

06:59.880 --> 07:00.820
We'll find out.

07:01.720 --> 07:02.780
Everyone will be, you know,

07:02.860 --> 07:05.180
clamoring for their live DDP hack radio.

07:05.180 --> 07:06.700
Actually, this is a good thing,

07:06.860 --> 07:08.800
because hopefully now,

07:09.160 --> 07:10.980
the big thing in my eyes

07:10.980 --> 07:12.580
to get us from doing live episodes

07:12.580 --> 07:14.220
is trying to reconfigure ourselves

07:14.220 --> 07:15.900
to work with Radio's live stream.

07:16.660 --> 07:17.400
So hopefully now,

07:17.440 --> 07:18.640
it should be rather simple

07:18.640 --> 07:19.780
to flip the switch

07:19.780 --> 07:21.100
and instantly do a live episode

07:21.100 --> 07:24.020
for Binary Revolution Radio.

07:24.520 --> 07:25.900
Has Tank ever done a live episode?

07:27.100 --> 07:28.120
No, I don't think so.

07:28.360 --> 07:29.360
I don't think we've had, like,

07:29.400 --> 07:31.200
the technical prowess

07:31.200 --> 07:33.420
to get that pulled off with...

07:33.420 --> 07:35.600
Well, we don't have technical prowess either,

07:35.680 --> 07:36.640
but we're going to try it anyway.

07:37.560 --> 07:37.880
Good luck.

07:38.080 --> 07:38.960
Yeah, and apparently,

07:39.140 --> 07:40.580
I mean, if you listen to Freak Radio,

07:40.680 --> 07:42.080
you know nobody knew technical prowess

07:42.080 --> 07:42.900
and that kind of crap.

07:42.960 --> 07:43.740
Well, if I did it,

07:43.920 --> 07:44.480
there you go.

07:45.200 --> 07:45.440
Yeah.

07:45.940 --> 07:47.240
What magazine inscription

07:47.240 --> 07:48.080
did you get that phone from?

07:48.820 --> 07:50.200
You're getting all GSM-y on me.

07:50.920 --> 07:52.800
Oh, you know,

07:53.720 --> 07:55.800
it's just the area that I live.

07:56.040 --> 07:57.420
People here are super rich,

07:57.420 --> 07:59.700
and I don't like having cell sites

07:59.700 --> 08:00.700
anywhere near their house.

08:00.700 --> 08:03.200
They don't want their babies

08:03.200 --> 08:05.120
to have five arms and three legs.

08:05.340 --> 08:05.580
Yeah.

08:06.080 --> 08:07.400
Yeah, my town's not so bad,

08:07.520 --> 08:08.820
but a couple of towns over,

08:08.940 --> 08:09.420
they have, like,

08:09.440 --> 08:10.060
a town ordinance

08:10.060 --> 08:11.440
against having cell sites

08:11.440 --> 08:12.080
in the town.

08:12.300 --> 08:12.660
Oh, yeah,

08:12.660 --> 08:13.400
we have a couple of those

08:13.400 --> 08:14.000
in Massachusetts.

08:14.260 --> 08:14.720
Oh, I mean,

08:14.760 --> 08:15.800
how pompous can you get?

08:16.420 --> 08:17.860
Yeah, give me a phone break.

08:18.500 --> 08:20.180
And if you ever drive near them,

08:20.260 --> 08:21.840
your cell phone drops to nothing.

08:22.180 --> 08:22.960
It's disgusting.

08:23.600 --> 08:24.720
I actually know people

08:24.720 --> 08:25.820
who drive routinely

08:25.820 --> 08:26.900
through this same town,

08:27.520 --> 08:28.720
and they have to have

08:28.720 --> 08:29.720
two cell phones,

08:30.100 --> 08:30.800
because one works

08:30.800 --> 08:31.700
in the middle of the town,

08:31.800 --> 08:32.600
one works in the edge

08:32.600 --> 08:33.080
of the town.

08:33.580 --> 08:34.080
That's it.

08:35.160 --> 08:35.360
So,

08:35.460 --> 08:36.060
we're back talking

08:36.060 --> 08:36.660
about phones again.

08:36.820 --> 08:36.940
So,

08:37.020 --> 08:37.700
how do we talk about that?

08:37.700 --> 08:38.120
Well, you know,

08:38.160 --> 08:38.640
cell phone,

08:38.700 --> 08:39.900
that's up to radio engineering.

08:40.060 --> 08:40.460
That's, you know,

08:40.520 --> 08:40.800
whatever.

08:41.800 --> 08:43.140
We can pass that off.

08:43.660 --> 08:44.100
I'm going to send

08:44.100 --> 08:45.240
a shout-out to Chris.

08:46.100 --> 08:46.740
He sent me

08:46.740 --> 08:48.040
the proper pronouncement

08:48.040 --> 08:49.840
of Ubuntu Linux.

08:49.960 --> 08:50.320
That would be

08:50.320 --> 08:51.440
Ubuntu.

08:52.660 --> 08:53.020
So,

08:53.120 --> 08:53.600
thanks, Chris.

08:53.680 --> 08:54.180
Thanks a lot.

08:54.900 --> 08:56.180
And last week,

08:56.220 --> 08:57.900
I mentioned a free IDE

08:57.900 --> 08:59.160
that was for C++

08:59.160 --> 09:00.020
and on Windows.

09:00.200 --> 09:00.860
It's called

09:00.860 --> 09:01.900
Dev C++.

09:02.320 --> 09:04.020
It's a free speech,

09:04.360 --> 09:04.860
as in, you know,

09:04.920 --> 09:05.380
GPL,

09:06.040 --> 09:06.820
a new public license.

09:06.920 --> 09:07.720
You can download the source

09:07.720 --> 09:08.640
and re-contract it

09:08.640 --> 09:09.700
for your own nefarious needs.

09:10.380 --> 09:11.540
It's a free IDE

09:11.540 --> 09:12.240
for C++.

09:13.100 --> 09:13.940
And sadly,

09:14.100 --> 09:14.480
right now,

09:14.520 --> 09:15.420
it's not fully compatible

09:15.420 --> 09:16.240
with Visual Studio.

09:17.240 --> 09:18.480
But I remember playing it

09:18.480 --> 09:19.860
before I got a copy

09:19.860 --> 09:21.000
of Visual Studio for work.

09:21.160 --> 09:21.480
And, you know,

09:21.960 --> 09:22.780
most of the stuff

09:22.780 --> 09:23.920
that you come across,

09:24.180 --> 09:25.380
a couple of quick fixes

09:25.380 --> 09:26.100
and maybe change

09:26.100 --> 09:26.920
some library names

09:26.920 --> 09:27.800
and some function calls.

09:28.920 --> 09:30.340
It's pretty easy.

09:30.460 --> 09:31.840
You can get it down to it.

09:31.960 --> 09:32.820
It's not that hard.

09:33.620 --> 09:34.080
It's available

09:34.080 --> 09:37.440
at www.bloodshed.net.

09:37.740 --> 09:40.400
B-L-O-O-D-S-H-E-D.

09:40.740 --> 09:41.180
Bloodshed.

09:41.860 --> 09:43.220
It's not very violent.

09:43.380 --> 09:43.740
It's a nice,

09:43.840 --> 09:45.580
easy-to-use C++ IDE.

09:45.980 --> 09:46.080
So,

09:46.420 --> 09:47.560
don't let the domain name

09:47.560 --> 09:48.020
freak you out.

09:48.740 --> 09:48.920
Yeah,

09:48.980 --> 09:49.900
it doesn't sound very friendly.

09:50.660 --> 09:51.180
Yes, yes.

09:51.480 --> 09:52.520
Shall we go into the email?

09:53.480 --> 09:53.920
Sure.

09:53.920 --> 09:54.040
Sure.

10:09.920 --> 10:16.520
Okay, for our first email tonight.

10:17.480 --> 10:18.760
Dear Black Ratchet and Strom,

10:19.260 --> 10:20.760
or Dear Black Ratchet and Not Theory,

10:20.880 --> 10:21.360
I guess, you know.

10:21.360 --> 10:22.180
All right.

10:22.520 --> 10:24.060
I've just listened to your intro

10:24.060 --> 10:24.900
into hacking episode

10:24.900 --> 10:26.380
and would like to say a few things.

10:26.820 --> 10:27.740
First things first,

10:28.060 --> 10:29.380
silenceisdefeat.org

10:29.380 --> 10:30.760
is not a Linux shell account.

10:31.220 --> 10:33.580
It is an open BSD account,

10:33.820 --> 10:34.760
which,

10:34.980 --> 10:36.720
while BSD is similar to Linux,

10:36.820 --> 10:37.820
it is not the same thing.

10:38.500 --> 10:39.460
Speaking of BSD,

10:39.620 --> 10:40.980
it's another great open-source

10:40.980 --> 10:42.280
Unix-like operating system

10:42.280 --> 10:43.380
that, in my opinion,

10:43.460 --> 10:44.120
is just as good

10:44.120 --> 10:45.500
to start hacking on as Linux.

10:46.500 --> 10:48.480
Though net and open BSD

10:48.480 --> 10:49.720
are a bit more advanced

10:49.720 --> 10:50.960
for a Unix novice

10:50.960 --> 10:51.760
and get up and running,

10:52.180 --> 10:53.240
free BSD is great

10:53.240 --> 10:54.400
for those who are new to Unix.

10:55.640 --> 10:57.460
You also did not really

10:57.460 --> 10:58.260
touch on programming.

10:58.360 --> 10:59.280
You touched a tiny bit

10:59.280 --> 11:00.940
on how to be a script kitty,

11:01.060 --> 11:02.280
but not really explain

11:02.280 --> 11:04.260
just using other people's exploits

11:04.260 --> 11:05.720
as kind of anti-hackerish.

11:06.460 --> 11:07.660
And as breaking into computers

11:07.660 --> 11:08.160
is your thing,

11:08.220 --> 11:10.140
it's more about figuring out

11:10.140 --> 11:11.160
what's wrong with the system

11:11.160 --> 11:12.200
and how to exploit it

11:12.200 --> 11:13.400
than using others

11:13.400 --> 11:14.300
to gain access.

11:15.120 --> 11:16.180
And that's from Steve-O.

11:18.280 --> 11:18.720
Oops.

11:19.200 --> 11:19.680
My bad.

11:19.920 --> 11:20.120
You know,

11:20.300 --> 11:21.740
I'm sure there's more

11:21.740 --> 11:22.600
than a few people out there

11:22.600 --> 11:23.680
that kind of got ticked off

11:23.680 --> 11:24.560
that didn't mention BSD.

11:25.560 --> 11:26.340
And plus,

11:26.420 --> 11:27.620
nothing really pisses off

11:27.620 --> 11:28.380
a BSD person

11:28.380 --> 11:29.540
to associate them with Linux.

11:30.140 --> 11:30.780
I'm kidding.

11:30.880 --> 11:31.200
I'm kidding.

11:31.520 --> 11:32.160
Well, sort of.

11:33.080 --> 11:34.560
I didn't touch on BSDs,

11:34.560 --> 11:35.200
so I'll quickly talk

11:35.200 --> 11:35.680
about them here.

11:36.140 --> 11:37.400
BSDs are much more

11:37.400 --> 11:38.760
Unix-y than Linux.

11:38.920 --> 11:39.680
They are real,

11:39.740 --> 11:40.640
honest-to-goodness Unix.

11:40.640 --> 11:41.920
They were forked

11:41.920 --> 11:44.540
from the AT&T BSD distribution.

11:44.980 --> 11:45.420
Are you, like,

11:45.440 --> 11:45.940
cleaning your room

11:45.940 --> 11:46.280
or something?

11:47.160 --> 11:47.760
No, I'm just

11:47.760 --> 11:48.520
shuffling around

11:48.520 --> 11:49.140
so it gets better.

11:50.100 --> 11:50.720
Oh, look at that.

11:50.760 --> 11:51.660
He's just shuffling around.

11:51.780 --> 11:51.920
He's, like,

11:51.940 --> 11:52.820
climbing on the roof.

11:53.960 --> 11:54.320
Goodness,

11:54.460 --> 11:54.740
he's, like,

11:54.780 --> 11:55.540
tearing his house down

11:55.540 --> 11:55.960
or installing

11:55.960 --> 11:56.700
an antenna or something.

11:57.040 --> 11:57.540
Yeah, I've got to

11:57.540 --> 11:58.360
rip out this wall

11:58.360 --> 11:58.900
to be able to

11:58.900 --> 11:59.820
get a good reception here.

12:00.120 --> 12:00.420
Yes.

12:01.120 --> 12:01.740
This old house

12:01.740 --> 12:02.300
was not dairy.

12:04.740 --> 12:05.520
School of time.

12:06.140 --> 12:07.140
BSDs are all forked

12:07.140 --> 12:07.820
from the original

12:07.820 --> 12:09.640
AT&T BSD Unix code.

12:10.640 --> 12:11.620
When I first

12:11.620 --> 12:11.920
cut my,

12:12.040 --> 12:13.580
I find that

12:13.580 --> 12:14.560
they're a lot

12:14.560 --> 12:15.600
less newbie-friendly.

12:15.980 --> 12:17.040
I cut my teeth

12:17.040 --> 12:17.540
after,

12:17.760 --> 12:18.520
on FreeBSD

12:18.520 --> 12:19.600
after, you know,

12:19.660 --> 12:20.400
about two years,

12:20.500 --> 12:21.000
two, three years

12:21.000 --> 12:21.420
with Linux,

12:21.540 --> 12:23.720
and it was a very

12:23.720 --> 12:24.660
interesting experience.

12:24.800 --> 12:26.040
It's not what I was used to.

12:26.300 --> 12:26.600
It's,

12:26.860 --> 12:27.160
there's a,

12:27.260 --> 12:28.340
they're a lot more powerful

12:28.340 --> 12:28.980
and,

12:29.160 --> 12:29.800
but they have a lot

12:29.800 --> 12:30.600
less hand-holding.

12:30.980 --> 12:31.820
I still kind of feel

12:31.820 --> 12:32.180
that way.

12:32.240 --> 12:33.560
I haven't used FreeBSD

12:33.560 --> 12:34.040
in a while.

12:34.220 --> 12:34.940
I've moved over

12:34.940 --> 12:35.660
to OpenBSD.

12:36.360 --> 12:36.640
And,

12:36.880 --> 12:38.880
I guess you could say

12:38.880 --> 12:40.580
that I,

12:40.580 --> 12:40.660
I,

12:40.740 --> 12:41.480
I'm a bit more

12:41.480 --> 12:42.000
versed with them,

12:42.100 --> 12:42.780
so I can't really say

12:42.780 --> 12:43.480
how newbie-friendly

12:43.480 --> 12:44.100
they are anymore.

12:44.980 --> 12:45.340
Anyway,

12:45.440 --> 12:45.980
I'm talking about

12:45.980 --> 12:46.580
FreeBSD,

12:46.720 --> 12:47.320
OpenBSD,

12:47.400 --> 12:47.960
and FBSD,

12:48.040 --> 12:48.780
and you're all going,

12:48.980 --> 12:49.180
what?

12:49.560 --> 12:49.880
So,

12:49.960 --> 12:50.600
let's go over that.

12:51.000 --> 12:52.000
There's three major

12:52.000 --> 12:53.220
BSD forks out there.

12:53.560 --> 12:54.040
OpenBSD,

12:54.240 --> 12:54.460
who's,

12:54.600 --> 12:54.980
basically,

12:55.240 --> 12:56.140
its main purpose

12:56.140 --> 12:57.060
is to be a very,

12:57.200 --> 12:58.240
very secure distribution.

12:58.420 --> 12:59.260
I believe they've

12:59.260 --> 13:01.980
gone five years

13:01.980 --> 13:02.620
and they've only had

13:02.620 --> 13:03.920
one root compromised

13:03.920 --> 13:04.560
in the default

13:04.560 --> 13:04.940
themselves.

13:05.320 --> 13:05.660
Not there,

13:05.740 --> 13:07.200
do you use OpenBSD

13:07.200 --> 13:07.460
at all?

13:08.340 --> 13:08.880
You know,

13:09.020 --> 13:09.680
I don't.

13:10.040 --> 13:11.300
I actually started

13:11.300 --> 13:12.760
on FreeBSD

13:12.760 --> 13:13.560
a long time ago,

13:13.780 --> 13:14.420
but then

13:14.420 --> 13:16.280
just switched to Linux

13:16.280 --> 13:16.840
for the hell of it

13:16.840 --> 13:18.060
and haven't looked back,

13:18.120 --> 13:18.880
not because BSD

13:18.880 --> 13:19.480
was bad,

13:19.480 --> 13:19.760
but,

13:20.280 --> 13:20.640
I don't know.

13:20.980 --> 13:21.440
For Linux,

13:21.560 --> 13:21.860
for me,

13:21.960 --> 13:23.200
for some reason,

13:23.260 --> 13:24.000
it was just more fun,

13:24.480 --> 13:25.420
but I haven't touched it

13:25.420 --> 13:25.980
in a long time,

13:26.060 --> 13:27.000
so I can't really attest

13:27.000 --> 13:28.900
to very much.

13:28.960 --> 13:29.520
Other than that,

13:29.560 --> 13:30.160
I think you're right.

13:30.260 --> 13:30.840
In five years,

13:30.900 --> 13:31.680
they've had one

13:31.680 --> 13:35.080
local root compromised.

13:36.340 --> 13:37.020
I thought it was

13:37.020 --> 13:37.300
remote.

13:37.400 --> 13:37.780
I thought it was

13:37.780 --> 13:38.740
the SSH problem.

13:39.800 --> 13:40.140
I don't know.

13:40.140 --> 13:40.420
Was it?

13:40.940 --> 13:42.320
They proudly display it.

13:42.340 --> 13:43.260
Go to their website.

13:43.400 --> 13:44.620
It's openbsd.org.

13:45.860 --> 13:46.340
Let's see.

13:46.400 --> 13:46.880
What else do we have?

13:46.880 --> 13:47.380
OpenBSD.

13:47.380 --> 13:48.340
There's NetBSD,

13:48.500 --> 13:49.680
whose purpose is,

13:49.740 --> 13:50.060
basically,

13:50.240 --> 13:51.020
they want to port

13:51.020 --> 13:51.600
to everything

13:51.600 --> 13:52.520
under the sun.

13:52.860 --> 13:53.580
Your toaster,

13:53.760 --> 13:54.820
your washing machine,

13:55.660 --> 13:56.860
your Mac,

13:56.860 --> 13:57.260
SE.

13:58.060 --> 13:59.380
They are really

13:59.380 --> 14:00.420
like porting nuts

14:00.420 --> 14:00.860
over there.

14:02.240 --> 14:02.860
I've seen,

14:03.220 --> 14:03.660
basically,

14:04.100 --> 14:04.880
with NetBSD,

14:05.300 --> 14:06.220
all the palm tops

14:06.220 --> 14:06.900
you see that are

14:06.900 --> 14:07.460
just coming out,

14:07.540 --> 14:08.400
NetBSD people

14:08.400 --> 14:09.540
are instantaneously

14:09.540 --> 14:10.160
working on them,

14:10.180 --> 14:10.840
and you usually see

14:10.840 --> 14:11.760
NetBSD on them

14:11.760 --> 14:12.940
before Linux,

14:13.160 --> 14:14.160
because these are

14:14.160 --> 14:14.940
what these people do.

14:15.940 --> 14:16.380
Finally,

14:16.540 --> 14:17.540
there's FreeBSD,

14:17.700 --> 14:18.260
and basically,

14:18.580 --> 14:19.440
their main purpose

14:19.440 --> 14:20.760
is to design

14:20.760 --> 14:21.240
a nice,

14:21.480 --> 14:23.020
stable Intel

14:23.020 --> 14:24.120
x86 Unix,

14:24.920 --> 14:25.700
and that's what

14:25.700 --> 14:26.080
they do,

14:26.260 --> 14:26.800
and they're

14:26.800 --> 14:27.460
pretty good at it.

14:28.980 --> 14:29.600
They always

14:29.600 --> 14:30.200
pride themselves

14:30.200 --> 14:30.660
with being,

14:30.700 --> 14:30.860
you know,

14:30.900 --> 14:31.560
very stable,

14:31.680 --> 14:32.560
very slow-moving,

14:32.700 --> 14:32.920
you know,

14:33.000 --> 14:33.820
don't want to have

14:33.820 --> 14:34.300
the cutting-edge

14:34.300 --> 14:34.660
hardware,

14:34.820 --> 14:35.420
because,

14:35.560 --> 14:35.760
you know,

14:36.860 --> 14:37.500
they don't want

14:37.500 --> 14:38.380
to make 15 revisions

14:38.380 --> 14:38.780
to a kernel

14:38.780 --> 14:39.240
in a week.

14:39.420 --> 14:40.120
They want to do

14:40.120 --> 14:40.480
nice,

14:40.560 --> 14:40.820
slow,

14:40.940 --> 14:41.520
deliberate stuff.

14:41.640 --> 14:42.240
There's patches

14:42.240 --> 14:42.860
out there to bring

14:42.860 --> 14:43.260
it up to date

14:43.260 --> 14:43.900
with more hardware,

14:44.080 --> 14:45.120
but they're more

14:45.120 --> 14:45.740
geared toward,

14:46.100 --> 14:46.380
you know,

14:46.420 --> 14:47.040
running a server,

14:47.640 --> 14:48.620
not having a change,

14:48.820 --> 14:49.540
basically setting up

14:49.540 --> 14:49.860
a kernel,

14:49.860 --> 14:50.600
and only updating

14:50.600 --> 14:51.020
it if there's

14:51.020 --> 14:51.780
something majorly

14:51.780 --> 14:52.460
bad with it.

14:54.840 --> 14:55.660
BSD is fun.

14:56.160 --> 14:57.320
I like OpenBSD

14:57.320 --> 14:58.100
for my internet-facing

14:58.100 --> 14:58.560
systems.

14:59.100 --> 14:59.940
I use it at work

14:59.940 --> 15:00.620
a few times.

15:00.960 --> 15:01.260
However,

15:01.740 --> 15:03.360
I still follow

15:03.360 --> 15:04.000
by the thing,

15:04.140 --> 15:04.600
if you want

15:04.600 --> 15:05.240
to take the plunge,

15:05.660 --> 15:06.160
don't expect

15:06.160 --> 15:06.800
to have your handheld.

15:07.600 --> 15:08.320
It's scary

15:08.320 --> 15:09.160
for the first time.

15:09.340 --> 15:10.120
I did it.

15:11.360 --> 15:11.580
You know,

15:11.640 --> 15:11.980
Steve-O,

15:12.080 --> 15:13.240
as you're for the programming,

15:13.380 --> 15:14.400
I did touch on programming,

15:14.680 --> 15:15.800
just not a lot,

15:15.860 --> 15:16.440
and I don't believe

15:16.440 --> 15:17.180
running exploits

15:17.180 --> 15:18.140
coded by other people

15:18.140 --> 15:18.920
instantly turns you

15:18.920 --> 15:19.600
into a script kid,

15:19.600 --> 15:19.880
either.

15:20.580 --> 15:21.780
When I run an exploit,

15:22.240 --> 15:23.420
I understand how it works,

15:23.600 --> 15:24.700
I know what it's doing,

15:25.320 --> 15:25.700
however,

15:25.820 --> 15:26.520
I fully admit

15:26.520 --> 15:27.940
that I can't code

15:27.940 --> 15:28.460
one for shit.

15:28.700 --> 15:30.340
I do not know shellcode.

15:31.040 --> 15:32.160
I have a copy

15:32.160 --> 15:32.900
of the shellcoders

15:32.900 --> 15:33.360
handbook,

15:33.620 --> 15:33.980
and running,

15:34.160 --> 15:34.740
what is it,

15:34.780 --> 15:35.560
running shellcode

15:35.560 --> 15:36.540
for fun and profit,

15:36.660 --> 15:36.900
it was something

15:36.900 --> 15:37.720
like a frack or something,

15:38.340 --> 15:39.680
and basically,

15:39.900 --> 15:40.180
they're shitting

15:40.180 --> 15:40.760
on my shelf

15:40.760 --> 15:43.200
just collecting dust,

15:43.260 --> 15:43.920
because I haven't had

15:43.920 --> 15:44.660
time to read them yet.

15:45.420 --> 15:45.600
Yeah,

15:45.660 --> 15:46.380
I was actually going

15:46.380 --> 15:46.760
to recommend

15:46.760 --> 15:47.720
the shellcoders handbook

15:47.720 --> 15:48.240
if you want to learn

15:48.240 --> 15:49.040
how to write shellcode,

15:49.040 --> 15:50.300
and beyond that,

15:50.360 --> 15:50.980
if you want to learn

15:50.980 --> 15:52.480
how a lot of this stuff

15:52.480 --> 15:53.320
hangs together

15:53.320 --> 15:54.480
and why exploits work

15:54.480 --> 15:55.180
and stuff like that,

15:55.440 --> 15:56.260
it's a pretty good book.

15:56.340 --> 15:56.820
I have it,

15:56.920 --> 15:58.000
I've only read some of it

15:58.000 --> 15:58.920
because I've been really busy,

15:59.060 --> 15:59.980
but the parts of it

15:59.980 --> 16:00.440
that I read

16:00.440 --> 16:01.840
were just outstanding.

16:01.840 --> 16:02.420
Yeah,

16:02.440 --> 16:03.740
and essentially,

16:03.960 --> 16:06.980
if you want to write shellcode,

16:07.420 --> 16:10.320
be an expert at assembly.

16:10.820 --> 16:12.820
Assembly is what shellcode

16:12.820 --> 16:13.700
is all based out on.

16:16.620 --> 16:17.660
It's as simple as that,

16:17.740 --> 16:18.360
and I mean,

16:18.520 --> 16:20.200
I'm not as well-versed assembly

16:20.200 --> 16:20.900
as I thought I did

16:20.900 --> 16:21.660
after I started reading

16:21.660 --> 16:22.200
shellcoders.

16:22.660 --> 16:23.500
I just basically,

16:23.600 --> 16:24.140
I picked it up,

16:24.180 --> 16:24.920
I started reading it,

16:24.920 --> 16:28.600
and that's where it went.

16:28.800 --> 16:29.100
I mean,

16:29.140 --> 16:29.440
I was like,

16:29.500 --> 16:29.980
oh God,

16:30.040 --> 16:30.980
this is really complex.

16:31.160 --> 16:31.840
I don't know all this stuff.

16:31.900 --> 16:32.300
I have to read

16:32.300 --> 16:33.400
my assembly handbook again,

16:33.400 --> 16:35.580
and that's where I stopped.

16:40.280 --> 16:40.920
So anyway,

16:41.400 --> 16:42.460
I can look at a box.

16:42.600 --> 16:43.160
I can figure out

16:43.160 --> 16:44.000
if holes exist in it.

16:44.480 --> 16:45.420
I can exploit them

16:45.420 --> 16:45.960
to my advantage.

16:46.060 --> 16:46.220
However,

16:46.320 --> 16:47.700
I can't code up bugs

16:47.700 --> 16:48.320
that I might find

16:48.320 --> 16:48.860
in people's code.

16:48.960 --> 16:49.900
I think it's partially that,

16:50.020 --> 16:50.220
you know,

16:50.280 --> 16:51.100
I never had really someone

16:51.100 --> 16:51.740
I can learn from,

16:51.820 --> 16:52.360
and partially that

16:52.360 --> 16:53.000
I've never had someone,

16:53.620 --> 16:54.880
I never really had a reason

16:54.880 --> 16:55.300
to learn it.

16:56.100 --> 16:57.040
I don't,

16:57.160 --> 16:58.320
I'm not into security auditing.

16:58.600 --> 16:59.640
I don't have that much

16:59.640 --> 17:00.420
experience with it,

17:00.540 --> 17:01.740
and I've never really had

17:01.740 --> 17:02.620
a reason to learn to it.

17:03.400 --> 17:04.080
You know,

17:04.140 --> 17:04.400
however,

17:04.520 --> 17:05.640
I can use exploits

17:05.640 --> 17:06.400
and get successfully

17:06.400 --> 17:06.780
in a machine.

17:06.900 --> 17:07.420
I can use what

17:07.420 --> 17:08.560
the misconfigured stuff is.

17:08.680 --> 17:09.020
I know,

17:09.600 --> 17:10.860
I used to be a virtual

17:10.860 --> 17:12.160
encyclopedia on exploits

17:12.160 --> 17:13.240
with certain problems

17:13.240 --> 17:13.960
and programs.

17:14.780 --> 17:15.960
My university used to run

17:15.960 --> 17:17.120
a capture-to-fly contest.

17:17.520 --> 17:18.240
All four times

17:18.240 --> 17:18.640
they ran it

17:18.640 --> 17:19.500
that I participated in,

17:19.580 --> 17:21.200
my team either placed

17:21.200 --> 17:21.920
or won.

17:22.420 --> 17:23.100
I think we won

17:23.100 --> 17:23.960
the last two times.

17:24.920 --> 17:25.160
Yeah,

17:25.180 --> 17:25.820
that sounds about right.

17:26.000 --> 17:26.360
Nice.

17:26.740 --> 17:26.960
Yeah,

17:27.060 --> 17:27.240
yeah,

17:27.280 --> 17:28.140
I was pretty elite.

17:28.380 --> 17:28.980
What can I say?

17:28.980 --> 17:30.020
We always got our,

17:30.540 --> 17:32.400
we had our winnings

17:32.400 --> 17:33.280
in beer as always.

17:33.680 --> 17:34.380
They gave us a nice

17:34.380 --> 17:35.160
gift certificate

17:35.160 --> 17:36.360
over to UNO's,

17:36.400 --> 17:37.220
which was down the street.

17:38.220 --> 17:39.020
Headed on over

17:39.020 --> 17:39.800
and generally

17:39.800 --> 17:41.000
just got completely tanked.

17:42.000 --> 17:42.320
Hmm,

17:42.540 --> 17:42.960
not bad.

17:43.920 --> 17:45.020
And they didn't arrest you

17:45.020 --> 17:45.880
or anything for this?

17:45.980 --> 17:46.820
It was like a really

17:46.820 --> 17:49.040
fully sanctioned contest?

17:50.080 --> 17:50.420
Oh yeah,

17:50.460 --> 17:51.520
it was a fully sanctioned contest.

17:51.640 --> 17:52.340
Basically what they did

17:52.340 --> 17:53.080
is they gave us

17:53.080 --> 17:54.060
this little sandbox

17:54.060 --> 17:56.160
on 192.168,

17:56.160 --> 17:56.720
and you gave us,

17:56.780 --> 17:57.380
you got an account

17:57.380 --> 17:59.780
on a outward-facing machine

17:59.780 --> 18:01.140
that basically connected you

18:01.140 --> 18:01.980
to your own box

18:01.980 --> 18:03.120
and you had 24 hours

18:03.120 --> 18:03.580
to cure it

18:03.580 --> 18:04.280
and 48 hours

18:04.280 --> 18:05.300
to break into everyone else.

18:07.160 --> 18:07.520
Hmm.

18:08.360 --> 18:09.100
Sounds pretty cool.

18:10.380 --> 18:10.580
Yeah,

18:10.640 --> 18:11.420
it was lots of fun.

18:11.480 --> 18:12.640
I really do miss it

18:12.640 --> 18:15.000
and as much as I want

18:15.000 --> 18:15.920
to try to CTF

18:15.920 --> 18:16.380
at, you know,

18:16.440 --> 18:16.820
DEF CON

18:16.820 --> 18:17.520
and all that stuff,

18:17.580 --> 18:18.320
I know that I'm going

18:18.320 --> 18:19.140
to get blown out of the water.

18:19.260 --> 18:20.100
So I just enjoy

18:20.100 --> 18:21.280
sitting there

18:21.280 --> 18:21.860
and looking out

18:21.860 --> 18:22.120
and saying,

18:22.200 --> 18:22.340
yeah,

18:22.420 --> 18:23.700
I could do that maybe

18:23.700 --> 18:25.580
and realize back in my mind,

18:25.680 --> 18:26.220
no you can't.

18:26.240 --> 18:26.440
What are you,

18:26.500 --> 18:26.680
nuts?

18:27.840 --> 18:28.160
Yeah,

18:28.180 --> 18:28.820
I was actually just going

18:28.820 --> 18:29.200
to ask you about

18:29.200 --> 18:29.920
the capture of the flag

18:29.920 --> 18:30.680
if you had checked out.

18:31.100 --> 18:31.340
No,

18:31.420 --> 18:32.220
I mean,

18:32.260 --> 18:32.720
I know you said

18:32.720 --> 18:33.600
you didn't get involved

18:33.600 --> 18:33.820
in it,

18:33.880 --> 18:34.500
but I didn't even

18:34.500 --> 18:34.940
get a chance

18:34.940 --> 18:35.480
to look at it.

18:35.520 --> 18:35.940
As a matter of fact,

18:36.000 --> 18:36.480
I didn't even see

18:36.480 --> 18:37.580
the vendor area

18:37.580 --> 18:38.140
at DEF CON

18:38.140 --> 18:39.220
the entire time

18:39.220 --> 18:39.620
I was there.

18:39.780 --> 18:40.040
Really?

18:40.140 --> 18:40.360
You didn't hit

18:40.360 --> 18:40.860
the vendor area?

18:40.980 --> 18:42.040
I stopped by once

18:42.040 --> 18:43.720
and then I saw

18:43.720 --> 18:44.380
that they didn't have

18:44.380 --> 18:45.400
any shirts in my size

18:45.400 --> 18:46.520
because I went there

18:46.520 --> 18:47.180
far too late

18:47.180 --> 18:48.140
and at which point

18:48.140 --> 18:48.540
I just said,

18:48.640 --> 18:49.200
screw this.

18:50.560 --> 18:51.680
I went to the

18:51.680 --> 18:52.860
Unix Air Plus guys

18:52.860 --> 18:53.460
and they had a couple

18:53.460 --> 18:54.020
of fun things

18:54.020 --> 18:54.360
that I wanted

18:54.360 --> 18:55.060
to get my hands on

18:55.060 --> 18:56.160
but I decided

18:56.160 --> 18:56.940
that carrying

18:56.940 --> 18:58.540
a bunch of switches

18:58.540 --> 18:59.100
in my bag

18:59.100 --> 18:59.700
would probably

18:59.700 --> 19:00.320
not do well

19:00.320 --> 19:00.960
with TSA.

19:02.360 --> 19:02.720
Yeah,

19:03.000 --> 19:03.240
you know,

19:03.340 --> 19:03.860
I actually did

19:03.860 --> 19:04.600
the same thing

19:04.600 --> 19:06.080
with my backpack.

19:06.300 --> 19:07.020
I had my laptop

19:07.020 --> 19:08.420
and I had phones

19:08.420 --> 19:09.220
and cables

19:09.220 --> 19:10.040
and all kinds of stuff

19:10.040 --> 19:11.340
and I can't imagine

19:11.340 --> 19:12.120
that it looked like

19:12.120 --> 19:13.160
anything other than

19:13.160 --> 19:14.020
a bomb,

19:14.340 --> 19:14.620
you know,

19:14.980 --> 19:15.780
but every time

19:15.780 --> 19:16.220
I went through

19:16.220 --> 19:17.040
they never asked

19:17.040 --> 19:17.540
me to open up

19:17.540 --> 19:17.860
the bag.

19:17.940 --> 19:18.520
The only time

19:18.520 --> 19:19.080
I've ever been

19:19.080 --> 19:20.040
searched is when

19:20.040 --> 19:20.520
I had nothing

19:20.520 --> 19:21.020
in my bag.

19:21.460 --> 19:21.680
Wow,

19:21.800 --> 19:22.380
that's weird.

19:24.080 --> 19:24.440
Actually,

19:24.620 --> 19:25.340
I was at

19:25.340 --> 19:27.820
McCarron International

19:27.820 --> 19:28.140
Airport,

19:28.300 --> 19:28.640
which is the main

19:28.640 --> 19:29.460
airport in Las Vegas

19:29.460 --> 19:30.880
and I was sitting

19:30.880 --> 19:31.860
there and my

19:31.860 --> 19:32.160
friend,

19:32.460 --> 19:33.660
he picked up

19:33.660 --> 19:34.520
a souvenir mug

19:34.520 --> 19:35.000
from one of his

19:35.000 --> 19:35.860
friends and he

19:35.860 --> 19:36.680
got flagged and I'm

19:36.680 --> 19:37.140
sitting there in

19:37.140 --> 19:37.560
the little waiting

19:37.560 --> 19:38.120
area for,

19:38.240 --> 19:38.380
you know,

19:38.780 --> 19:39.600
wait for your

19:39.600 --> 19:39.880
friend.

19:40.000 --> 19:40.240
It's like I'm

19:40.240 --> 19:40.720
out of the security

19:40.720 --> 19:41.440
checkpoint and I look

19:41.440 --> 19:42.120
over my shoulder

19:42.120 --> 19:44.020
and over there

19:44.020 --> 19:45.380
is a DEFCON goon

19:45.380 --> 19:46.060
being inspected

19:46.060 --> 19:46.380
and he had

19:46.380 --> 19:46.560
like,

19:46.600 --> 19:46.760
you know,

19:47.460 --> 19:48.800
three laptops all

19:48.800 --> 19:50.040
in his carry-on bag

19:50.040 --> 19:50.780
and they had them

19:50.780 --> 19:51.440
all open there

19:51.440 --> 19:52.040
looking at him

19:52.040 --> 19:52.880
and swabbing it

19:52.880 --> 19:53.980
and I was just

19:53.980 --> 19:54.160
going,

19:54.640 --> 19:54.900
oops,

19:55.180 --> 19:55.760
I really wanted

19:55.760 --> 19:56.260
to take a photo

19:56.260 --> 19:57.680
of it but I

19:57.680 --> 19:58.440
decided against that.

19:58.520 --> 19:59.140
TSA might not

19:59.140 --> 19:59.560
like that.

20:01.480 --> 20:01.880
So,

20:01.980 --> 20:02.360
let's see,

20:02.420 --> 20:02.900
next email.

20:02.900 --> 20:04.340
Hey Black Ratchet

20:04.340 --> 20:05.160
and Strom Carlson

20:05.160 --> 20:05.480
and Random

20:05.480 --> 20:05.940
Co-host,

20:06.380 --> 20:07.360
I found that

20:07.360 --> 20:08.020
very amusing

20:08.020 --> 20:08.540
that you started

20:08.540 --> 20:09.100
talking about

20:09.100 --> 20:09.720
running caseless

20:09.720 --> 20:10.180
computers.

20:10.480 --> 20:11.100
My roommate and

20:11.100 --> 20:11.580
I scrapped

20:11.580 --> 20:12.580
enough spare parts

20:12.580 --> 20:13.020
to our two

20:13.020 --> 20:13.680
machines to make

20:13.680 --> 20:14.300
another computer

20:14.300 --> 20:15.540
and he suggested

20:15.540 --> 20:16.040
we mount it

20:16.040 --> 20:16.500
on the wall.

20:17.200 --> 20:17.840
This was about

20:17.840 --> 20:18.680
15 weeks ago.

20:18.920 --> 20:19.360
He bought some

20:19.360 --> 20:19.860
little mounting

20:19.860 --> 20:20.320
hooks at a

20:20.320 --> 20:21.020
supply store and

20:21.020 --> 20:21.580
stuck the computer

20:21.580 --> 20:21.980
on the wall

20:21.980 --> 20:22.560
at our apartment.

20:23.280 --> 20:23.700
I installed

20:23.700 --> 20:24.600
Fedora Code 3

20:24.600 --> 20:24.920
on it,

20:25.040 --> 20:25.380
I'm sorry,

20:25.520 --> 20:26.580
Fedora Core 3

20:26.580 --> 20:28.440
and we used it

20:28.440 --> 20:28.820
for internet

20:28.820 --> 20:29.280
browsing and

20:29.280 --> 20:29.720
multimedia.

20:30.580 --> 20:30.980
In the last

20:30.980 --> 20:31.520
month he found

20:31.520 --> 20:32.500
an iMac G3

20:32.500 --> 20:33.020
and bought it

20:33.020 --> 20:33.700
home and he

20:33.700 --> 20:34.200
stole the hard

20:34.200 --> 20:34.640
drive out of

20:34.640 --> 20:35.340
our living room

20:35.340 --> 20:36.360
wall box to

20:36.360 --> 20:36.740
try to get

20:36.740 --> 20:37.480
the iMac working.

20:37.940 --> 20:38.540
But once we

20:38.540 --> 20:39.140
found the iMac

20:39.140 --> 20:39.580
was broken,

20:39.720 --> 20:40.200
we gutted it

20:40.200 --> 20:40.960
but saved its

20:40.960 --> 20:41.460
pretty shell.

20:42.000 --> 20:42.560
Our apartment

20:42.560 --> 20:43.380
manager came to

20:43.380 --> 20:45.140
inspect the place

20:45.140 --> 20:45.700
so we had to

20:45.700 --> 20:46.140
take the wall

20:46.140 --> 20:46.920
computer completely

20:46.920 --> 20:47.260
down.

20:48.200 --> 20:48.520
Unfortunately,

20:50.140 --> 20:50.360
hmm,

20:50.500 --> 20:51.040
that was a bad

20:51.040 --> 20:51.300
period.

20:52.180 --> 20:52.680
But I had to

20:52.680 --> 20:53.140
do it again.

20:53.560 --> 20:54.780
I hoped to do

20:54.780 --> 20:55.140
it again.

20:55.300 --> 20:55.840
It was a lot of

20:55.840 --> 20:56.040
fun.

20:56.300 --> 20:56.860
Thanks for reading.

20:56.940 --> 20:57.380
Hopefully this

20:57.380 --> 20:58.160
story was interesting.

20:58.580 --> 20:59.080
I've listened to

20:59.080 --> 20:59.620
BinRev Radio

20:59.620 --> 21:00.200
for several months

21:00.200 --> 21:00.600
now and I've

21:00.600 --> 21:00.880
gone through

21:00.880 --> 21:01.380
all the episodes

21:01.380 --> 21:02.020
I really enjoy

21:02.020 --> 21:03.340
you guys keep

21:03.340 --> 21:03.560
it up.

21:03.660 --> 21:04.080
Thanks again.

21:04.160 --> 21:04.740
Control shift.

21:05.460 --> 21:06.100
Great story,

21:06.200 --> 21:06.660
control shift.

21:07.020 --> 21:07.800
I love wall

21:07.800 --> 21:08.500
mounted computers.

21:09.040 --> 21:09.300
Although I'm

21:09.300 --> 21:10.020
really curious how

21:10.020 --> 21:11.140
you interfaced with

21:11.140 --> 21:11.740
the computer when

21:11.740 --> 21:12.180
it was on the

21:12.180 --> 21:12.400
wall.

21:12.540 --> 21:12.680
I mean,

21:12.720 --> 21:12.960
you can't

21:12.960 --> 21:13.940
really mount

21:13.940 --> 21:14.520
a monitor to

21:14.520 --> 21:14.840
your wall,

21:14.900 --> 21:15.260
can you?

21:16.220 --> 21:16.540
Anyway,

21:17.720 --> 21:18.180
one of my

21:18.180 --> 21:18.680
friends did it.

21:18.900 --> 21:19.540
They did all

21:19.540 --> 21:20.040
stuff over the

21:20.040 --> 21:20.620
network so they

21:20.620 --> 21:21.040
didn't have to

21:21.040 --> 21:21.700
worry about that.

21:22.360 --> 21:22.660
However,

21:22.900 --> 21:23.880
you really have

21:23.880 --> 21:24.440
it configured in

21:24.440 --> 21:24.900
some way that

21:24.900 --> 21:26.080
lets you use the

21:26.080 --> 21:26.960
computer to some

21:26.960 --> 21:27.200
part.

21:27.320 --> 21:28.040
I'm curious as

21:28.040 --> 21:28.440
to whether or not

21:28.440 --> 21:28.900
you just mounted

21:28.900 --> 21:29.360
it on a table

21:29.360 --> 21:29.920
or did something

21:29.920 --> 21:30.920
a little more

21:30.920 --> 21:31.340
interesting.

21:32.720 --> 21:33.420
This actually

21:33.420 --> 21:34.000
reminded me of a

21:34.000 --> 21:34.580
story of a guy who

21:34.580 --> 21:35.080
built a computer

21:35.080 --> 21:36.240
into his wall.

21:37.020 --> 21:37.460
You can read this

21:37.460 --> 21:38.280
really neat hack at

21:38.280 --> 21:39.700
tinyurl.com

21:39.700 --> 21:40.800
slash 84

21:40.800 --> 21:42.920
echo x-ray

21:42.920 --> 21:43.420
oscar.

21:43.420 --> 21:44.160
Wow, I had

21:44.160 --> 21:44.700
trouble remembering

21:44.700 --> 21:45.300
what he was.

21:46.440 --> 21:47.320
Very nice hack.

21:47.520 --> 21:48.160
Looks amazingly

21:48.160 --> 21:48.700
well done.

21:51.000 --> 21:51.560
It's just,

21:51.680 --> 21:52.380
it's really cool.

21:52.960 --> 21:53.380
Have you ever

21:53.380 --> 21:53.760
seen that?

21:53.760 --> 21:53.860
Yeah, a lot of

21:53.860 --> 21:54.460
these pictures are

21:54.460 --> 21:55.420
actually very nice.

21:55.560 --> 21:56.860
I didn't, I haven't

21:56.860 --> 21:57.760
seen this before but

21:57.760 --> 22:01.280
it looks pretty cool.

22:01.440 --> 22:02.260
Is it all touch

22:02.260 --> 22:02.940
screen or what's

22:02.940 --> 22:03.540
Yeah, it's all

22:03.540 --> 22:04.020
touch screen.

22:04.120 --> 22:04.760
It's really cool.

22:06.140 --> 22:06.320
Huh.

22:07.800 --> 22:08.200
Interesting.

22:08.620 --> 22:08.820
Yeah.

22:09.480 --> 22:10.260
So go check that

22:10.260 --> 22:10.400
out.

22:10.460 --> 22:10.720
He has the

22:10.720 --> 22:11.700
Trudus pictures and

22:11.700 --> 22:12.180
he has it all

22:12.180 --> 22:12.800
well designed.

22:13.400 --> 22:14.120
Essentially it's a

22:14.120 --> 22:16.320
dumb terminal that

22:16.320 --> 22:18.280
runs X and he

22:18.280 --> 22:18.900
just used it for

22:18.900 --> 22:19.480
home automation.

22:20.500 --> 22:21.100
Guy's pretty

22:21.100 --> 22:21.360
elite.

22:23.420 --> 22:24.160
Let's see, our

22:24.160 --> 22:25.200
next email is from

22:25.200 --> 22:25.800
VoltageX.

22:26.240 --> 22:27.440
Hey guys, just

22:27.440 --> 22:28.240
listening to 107.

22:28.520 --> 22:28.940
Friends and

22:28.940 --> 22:29.520
teachers have sent

22:29.520 --> 22:30.620
multiple iPods back

22:30.620 --> 22:31.560
after they've died.

22:32.260 --> 22:33.320
Come into the pack

22:33.320 --> 22:34.120
missing and parts

22:34.120 --> 22:34.460
miss it.

22:34.520 --> 22:35.100
They come back but

22:35.100 --> 22:35.820
the parts missing,

22:36.080 --> 22:36.360
et cetera.

22:37.140 --> 22:38.120
Are the number of

22:38.120 --> 22:39.260
faulty iPods around

22:39.260 --> 22:39.880
due to the sheer

22:39.880 --> 22:40.660
number of them or

22:40.660 --> 22:41.280
is this the Apple

22:41.280 --> 22:41.820
hard mark?

22:41.820 --> 22:42.600
At school, we've

22:42.600 --> 22:43.720
had multiple faulty

22:43.720 --> 22:44.780
Apple laptops and

22:44.780 --> 22:45.620
computers sent back.

22:45.840 --> 22:46.480
Because of this, I

22:46.480 --> 22:47.280
started using such

22:47.280 --> 22:48.160
terms as crap and

22:48.160 --> 22:49.340
tosh, Mac and

22:49.340 --> 22:50.840
trash, laptop on a

22:50.840 --> 22:52.040
stick, laptop school.

22:53.320 --> 22:54.180
He puts in

22:54.180 --> 22:54.800
parentheses the

22:54.800 --> 22:56.520
iMac G5, which is

22:56.520 --> 22:57.500
I find an amusing

22:57.500 --> 22:57.740
term.

22:57.880 --> 22:58.540
Anyway, the show's

22:58.540 --> 22:58.780
improving.

22:58.920 --> 22:59.260
Keep it up.

22:59.360 --> 22:59.860
VoltageX.

23:00.800 --> 23:02.120
Well, now that I

23:02.120 --> 23:02.720
hear this and I

23:02.720 --> 23:04.120
actually talked

23:04.120 --> 23:04.660
around to a couple

23:04.660 --> 23:05.120
of my friends,

23:05.380 --> 23:06.100
I'm possibly

23:06.100 --> 23:06.860
Strom was right.

23:06.860 --> 23:09.040
Besides my

23:09.040 --> 23:09.720
recently discovered

23:09.720 --> 23:10.700
battery trouble, I've

23:10.700 --> 23:11.320
yet to have my

23:11.320 --> 23:12.020
iPod break.

23:12.200 --> 23:13.040
However, Strom

23:13.040 --> 23:13.820
went out and got

23:13.820 --> 23:14.380
two of them and

23:14.380 --> 23:14.920
I called a couple

23:14.920 --> 23:15.500
of friends who've

23:15.500 --> 23:16.100
had one break.

23:17.960 --> 23:18.740
All of them within

23:18.740 --> 23:19.460
the past couple of

23:19.460 --> 23:19.680
months.

23:19.780 --> 23:20.520
It's very interesting.

23:21.580 --> 23:22.020
Yeah, I actually

23:22.020 --> 23:22.940
have a friend even

23:22.940 --> 23:23.560
who has an older

23:23.560 --> 23:23.880
one.

23:25.500 --> 23:27.760
Somehow, every single

23:27.760 --> 23:29.300
Apple thing he has

23:29.300 --> 23:30.100
just keeps breaking

23:30.100 --> 23:30.560
and breaking.

23:30.680 --> 23:31.040
I don't know what

23:31.040 --> 23:31.320
it is.

23:31.320 --> 23:33.240
Yeah, I don't

23:33.240 --> 23:33.400
know.

23:33.680 --> 23:34.360
I have a nice

23:34.360 --> 23:37.300
iMac G3 that has

23:37.300 --> 23:37.960
been working fine

23:37.960 --> 23:38.320
forever.

23:40.140 --> 23:40.540
Whatever.

23:40.860 --> 23:41.240
I don't know.

23:41.700 --> 23:42.420
It's not an iMac.

23:42.520 --> 23:42.940
It's a blue and

23:42.940 --> 23:43.440
white G3.

23:43.580 --> 23:43.940
Pardon me.

23:44.180 --> 23:45.060
At least iMacs.

23:46.660 --> 23:47.320
VoltageX, as for

23:47.320 --> 23:48.040
your terms, I've been

23:48.040 --> 23:48.940
using those since I

23:48.940 --> 23:50.160
was about 13 and

23:50.160 --> 23:51.040
that's been quite a

23:51.040 --> 23:52.340
while for most of

23:52.340 --> 23:52.840
you out there.

23:54.260 --> 23:55.420
However, like I

23:55.420 --> 23:55.960
said, I do like

23:55.960 --> 23:56.440
laptops.

23:56.580 --> 23:56.700
Cool.

23:56.940 --> 23:58.360
That's pretty

23:58.360 --> 23:58.680
amusing.

23:59.660 --> 24:00.600
I have a couple of

24:00.600 --> 24:01.220
people who are

24:01.220 --> 24:01.900
doing interesting

24:01.900 --> 24:02.560
mods with their

24:02.560 --> 24:05.320
iBooks and it

24:05.320 --> 24:06.420
really does start

24:06.420 --> 24:07.020
to look like a

24:07.020 --> 24:08.600
laptop icicle.

24:09.200 --> 24:09.420
Whatever.

24:10.440 --> 24:11.100
The reason why I

24:11.100 --> 24:11.900
posted this is we're

24:11.900 --> 24:12.280
going to have a

24:12.280 --> 24:13.000
homework assignment.

24:13.840 --> 24:14.360
How many of you

24:14.360 --> 24:15.560
have Apple products

24:15.560 --> 24:16.040
that have failed

24:16.040 --> 24:16.480
miserably?

24:16.700 --> 24:17.340
And to counterpoint,

24:17.420 --> 24:17.840
how many of you

24:17.840 --> 24:18.960
had rock solid

24:18.960 --> 24:20.720
Apple products?

24:21.320 --> 24:22.100
Email us at

24:22.100 --> 24:22.500
radio at

24:22.500 --> 24:23.380
binrev.com.

24:25.220 --> 24:25.700
Let's see.

24:25.720 --> 24:26.180
We have one more

24:26.180 --> 24:26.700
email tonight.

24:28.120 --> 24:28.800
I found your

24:28.800 --> 24:29.460
radio service to

24:29.460 --> 24:30.360
this website, which

24:30.360 --> 24:31.080
is a podcast

24:31.080 --> 24:32.000
directory.com.

24:32.100 --> 24:32.880
He attached the

24:32.880 --> 24:33.140
email.

24:33.960 --> 24:34.720
You guys rock.

24:34.840 --> 24:35.780
Basically, I'm a

24:35.780 --> 24:36.420
noob without a

24:36.420 --> 24:36.920
pseudoname.

24:38.060 --> 24:38.640
I thought it would

24:38.640 --> 24:39.360
be very cool if I

24:39.360 --> 24:39.980
could get named by

24:39.980 --> 24:40.420
you guys.

24:40.660 --> 24:41.520
I realize this might

24:41.520 --> 24:41.980
be a strange

24:41.980 --> 24:42.540
request, but I'm

24:42.540 --> 24:42.940
going on the

24:42.940 --> 24:43.540
premise of only

24:43.540 --> 24:44.580
stupid questions is

24:44.580 --> 24:45.280
one that I'd ask.

24:45.920 --> 24:46.880
Keep us great work.

24:47.220 --> 24:47.560
P.S.

24:47.560 --> 24:48.420
I also subscribe to

24:48.420 --> 24:49.420
Boston, sorry,

24:49.560 --> 24:50.300
2600.

24:50.460 --> 24:51.080
Wow, I'm kind of

24:51.080 --> 24:51.760
used to constantly

24:51.760 --> 24:52.400
saying Boston

24:52.400 --> 24:53.300
penny 2600.

24:55.700 --> 24:56.100
Wow.

24:56.100 --> 24:56.620
Do you think he

24:56.620 --> 24:57.180
trusts us?

24:58.560 --> 25:00.200
Well, I see

25:00.200 --> 25:01.160
written down here

25:01.160 --> 25:01.900
what you think you

25:01.900 --> 25:02.580
should name him.

25:04.080 --> 25:05.400
Yeah, you know, I

25:05.400 --> 25:06.500
was actually kind of

25:06.500 --> 25:07.140
rattling this around

25:07.140 --> 25:07.680
in my head, you

25:07.680 --> 25:08.380
know, Thrax,

25:08.860 --> 25:09.180
Wraith.

25:09.860 --> 25:10.640
I'm personally

25:10.640 --> 25:12.100
partial to Black

25:12.100 --> 25:12.620
Ratchet Jr.

25:12.620 --> 25:14.780
Oh, yeah, that is

25:14.780 --> 25:15.700
just precious.

25:16.000 --> 25:16.400
Yeah, yeah.

25:16.420 --> 25:16.640
Do you want to

25:16.640 --> 25:17.420
have a not-theory

25:17.420 --> 25:18.100
Jr. over there?

25:19.520 --> 25:20.620
No, I don't think.

25:20.680 --> 25:21.260
Maybe we could just

25:21.260 --> 25:22.060
call him Thury, and

25:22.060 --> 25:23.000
like, he and I

25:23.000 --> 25:24.140
could be like some

25:24.140 --> 25:25.500
type of arch-nemesis

25:25.500 --> 25:26.480
thing going on.

25:28.060 --> 25:28.880
You never know.

25:31.280 --> 25:32.040
Picking a handle

25:32.040 --> 25:33.580
is something, it's

25:33.580 --> 25:34.600
not pseudoname, it's

25:34.600 --> 25:35.580
a, I guess you could

25:35.580 --> 25:36.280
call it a pseudonym,

25:36.420 --> 25:36.760
I guess.

25:36.940 --> 25:37.580
You know, I always

25:37.580 --> 25:38.460
called it my online

25:38.460 --> 25:39.720
alter ego for people

25:39.720 --> 25:40.460
who know me in real

25:40.460 --> 25:40.720
life.

25:40.720 --> 25:42.440
So, picking a

25:42.440 --> 25:43.760
handle is something

25:43.760 --> 25:44.820
you should really do

25:44.820 --> 25:45.260
on your own.

25:45.480 --> 25:46.820
I think that Strom

25:46.820 --> 25:47.500
has a very cool

25:47.500 --> 25:48.040
handle, because you

25:48.040 --> 25:48.580
can give it out as a

25:48.580 --> 25:48.960
real name.

25:49.080 --> 25:49.800
Lots of people think

25:49.800 --> 25:50.640
that Strom Carlson

25:50.640 --> 25:51.260
is a real name.

25:51.540 --> 25:52.000
It isn't.

25:54.420 --> 25:55.660
The way I picked

25:55.660 --> 25:56.860
my name is basically

25:56.860 --> 25:58.760
it was blackratchet.org,

25:59.080 --> 26:00.520
it was, or org, or

26:00.520 --> 26:01.080
whatever you want to

26:01.080 --> 26:01.380
call it.

26:02.060 --> 26:02.920
It was the only

26:02.920 --> 26:03.820
domain name available

26:03.820 --> 26:04.720
that did not sound

26:04.720 --> 26:05.380
lame and sounded

26:05.380 --> 26:05.700
cool.

26:07.220 --> 26:08.240
So, how did you pick

26:08.240 --> 26:08.720
your name, not

26:08.720 --> 26:08.920
Thury?

26:10.720 --> 26:11.920
It is a really,

26:12.260 --> 26:13.100
really long story.

26:13.960 --> 26:14.980
But basically, the

26:14.980 --> 26:16.960
short version of the

26:16.960 --> 26:18.320
story is, when I was

26:18.320 --> 26:19.020
in college, a lot of

26:19.020 --> 26:19.880
professors, I would

26:19.880 --> 26:20.840
talk to them about

26:20.840 --> 26:21.560
different things I

26:21.560 --> 26:22.800
wanted to do, and I

26:22.800 --> 26:23.400
always ask them what

26:23.400 --> 26:23.980
they thought about it,

26:24.000 --> 26:24.560
because I looked up to

26:24.560 --> 26:25.040
them, obviously.

26:25.460 --> 26:26.100
And they'd always say,

26:26.160 --> 26:27.160
well, in theory you

26:27.160 --> 26:28.080
could do it, but this,

26:28.140 --> 26:28.900
this, this, this, this.

26:28.980 --> 26:29.800
In theory, and all

26:29.800 --> 26:30.800
these guys, all they

26:30.800 --> 26:31.460
would ever talk about

26:31.460 --> 26:32.340
is theoretically you

26:32.340 --> 26:33.060
could do something.

26:33.500 --> 26:34.520
But it seemed like,

26:35.040 --> 26:35.660
aside from writing

26:35.660 --> 26:36.500
papers about what they

26:36.500 --> 26:37.200
could do theoretically,

26:37.360 --> 26:38.500
these guys actually did

26:38.500 --> 26:38.620
it.

26:38.620 --> 26:40.120
So, I essentially

26:40.120 --> 26:41.000
just told everybody,

26:41.160 --> 26:41.900
like, I want to do

26:41.900 --> 26:43.640
things in practice, not

26:43.640 --> 26:43.920
theory.

26:44.160 --> 26:45.500
So, that's where it

26:45.500 --> 26:45.900
came from.

26:47.040 --> 26:47.620
That's pretty

26:47.620 --> 26:48.020
interesting.

26:48.360 --> 26:49.360
Stank always thought

26:49.360 --> 26:49.840
that, like, I picked

26:49.840 --> 26:51.060
my name by getting

26:51.060 --> 26:51.900
beaten by a black

26:51.900 --> 26:52.660
ratchet one day or

26:52.660 --> 26:53.880
something, or something

26:53.880 --> 26:55.620
amusing or something.

26:55.740 --> 26:56.800
But no, no, very

26:56.800 --> 26:57.080
lame.

26:57.180 --> 26:58.000
I originally was just

26:58.000 --> 26:58.480
going to have something

26:58.480 --> 26:59.240
called Black Ratchet

26:59.240 --> 27:00.360
Labs to pack all my,

27:01.160 --> 27:02.160
you know, more gray

27:02.160 --> 27:03.040
stuff in real life.

27:03.040 --> 27:03.820
And it's just sort of

27:03.820 --> 27:05.460
descended into a giant

27:05.460 --> 27:06.600
pseudonym for me, or

27:06.600 --> 27:07.300
handle, or whatever you

27:07.300 --> 27:07.820
want to say it.

27:09.060 --> 27:09.920
Well, it works.

27:12.460 --> 27:14.200
Oh, so, that's it for

27:14.200 --> 27:14.740
the emails tonight.

27:14.820 --> 27:15.320
We're going to go into

27:15.320 --> 27:15.920
show and tell.

27:16.300 --> 27:17.400
Do you have any fun

27:17.400 --> 27:18.520
hacking, personal hacking

27:18.520 --> 27:18.900
stories?

27:20.780 --> 27:23.720
Um, let me think.

27:23.920 --> 27:24.880
I really thought that I

27:24.880 --> 27:25.120
did.

27:25.360 --> 27:26.020
I don't know why I'm

27:26.020 --> 27:26.900
choking at the last

27:26.900 --> 27:27.460
second, though.

27:27.460 --> 27:31.820
Um, I don't know, I

27:31.820 --> 27:32.380
can't really think of

27:32.380 --> 27:32.920
anything exciting.

27:33.040 --> 27:33.840
I had something that I

27:33.840 --> 27:34.500
was going to release

27:34.500 --> 27:35.860
before DEF CON, and

27:35.860 --> 27:36.320
then I was going to

27:36.320 --> 27:37.580
release at DEF CON, and

27:37.580 --> 27:37.980
now I'm going to

27:37.980 --> 27:39.060
release, obviously, after

27:39.060 --> 27:39.800
DEF CON, because it

27:39.800 --> 27:40.440
still hasn't come out

27:40.440 --> 27:40.640
yet.

27:41.060 --> 27:43.240
But, um, I'm not going

27:43.240 --> 27:43.940
to spill the beans on

27:43.940 --> 27:44.380
it just yet.

27:44.400 --> 27:46.560
Can you, you know, give

27:46.560 --> 27:47.100
us a hint here?

27:48.680 --> 27:50.620
Um, it has something

27:50.620 --> 27:51.720
to do with making the

27:51.720 --> 27:53.360
Bell's Mind information

27:53.360 --> 27:55.280
much more detailed.

27:55.580 --> 27:56.160
Ooh, sounds

27:56.160 --> 27:56.520
interesting.

27:56.540 --> 27:56.820
That's about it.

27:56.820 --> 27:59.860
Um, but, I, uh, I

27:59.860 --> 28:00.500
can say that I

28:00.500 --> 28:01.340
definitely am going to

28:01.340 --> 28:03.160
redo the interface to

28:03.160 --> 28:03.720
Bell's Mind.

28:03.780 --> 28:04.340
I've been planning to

28:04.340 --> 28:05.260
do it for a while, but,

28:05.780 --> 28:07.020
um, I guess,

28:07.100 --> 28:07.940
unfortunately in one

28:07.940 --> 28:08.740
sense, but fortunately

28:08.740 --> 28:09.800
in, like, a real-life

28:09.800 --> 28:10.660
sense, I have a lot of

28:10.660 --> 28:11.440
work that keeps getting

28:11.440 --> 28:12.280
thrown at me, so I

28:12.280 --> 28:12.840
don't have time to do

28:12.840 --> 28:13.400
anything anymore.

28:13.880 --> 28:15.780
Um, normally I have a

28:15.780 --> 28:16.840
lot of work, but, uh,

28:16.840 --> 28:17.700
now it's, like, really,

28:17.820 --> 28:18.780
really piling up, so.

28:20.040 --> 28:22.220
Well, I, I, I do

28:22.220 --> 28:23.760
enjoy the very raw HTML

28:23.760 --> 28:24.640
look of Bell's Mind

28:24.640 --> 28:25.140
as of now.

28:25.140 --> 28:26.940
So, it looks pretty

28:26.940 --> 28:27.080
weird.

28:27.080 --> 28:28.000
Well, I don't, it's not

28:28.000 --> 28:28.820
going to, it's not going to

28:28.820 --> 28:29.440
change too much.

28:29.500 --> 28:30.120
I'm not going to have,

28:30.180 --> 28:31.260
like, you know, punch the

28:31.260 --> 28:32.840
monkey, or, or slap the

28:32.840 --> 28:33.620
ferret, or whatever the

28:33.620 --> 28:34.900
whole, like, flash ads are

28:34.900 --> 28:36.740
called, but it'll still look

28:36.740 --> 28:38.080
somewhat the same, but it'll

28:38.080 --> 28:39.180
just be, you know, kind of

28:39.180 --> 28:39.860
more functional.

28:39.980 --> 28:40.760
There'll be a lot of search

28:40.760 --> 28:41.660
functions that people have

28:41.660 --> 28:44.380
been asking me for, um, and

28:44.380 --> 28:45.280
if you've been asking me for

28:45.280 --> 28:45.920
it, I've been listening.

28:46.140 --> 28:46.660
Maybe I haven't been

28:46.660 --> 28:48.020
replying to, uh, email, but

28:48.020 --> 28:49.660
I've definitely been taking

28:49.660 --> 28:51.140
notes on what people really

28:51.140 --> 28:52.920
want, and, um, I'm

28:52.920 --> 28:53.980
implementing a bunch of

28:53.980 --> 28:55.220
them.

28:55.220 --> 28:56.100
Oh, we are very excited.

28:57.040 --> 28:58.720
Because I, because I am a

28:58.720 --> 28:59.740
Bell's Mind chunky, I will

28:59.740 --> 29:00.020
admit.

29:00.240 --> 29:01.340
I, I constantly come there.

29:02.840 --> 29:03.240
Nice.

29:03.540 --> 29:04.860
Uh, yeah, let's, let's hope

29:04.860 --> 29:05.680
it actually comes together,

29:05.760 --> 29:05.920
though.

29:05.920 --> 29:06.020
Oh.

29:06.700 --> 29:07.340
Well, we'll, we'll, we'll,

29:07.340 --> 29:08.080
we'll be waiting with

29:08.080 --> 29:08.560
bated breath.

29:08.620 --> 29:09.140
We'll probably get it

29:09.140 --> 29:10.140
sometime around 2007.

29:13.620 --> 29:14.700
You're supposed to say no,

29:14.780 --> 29:15.760
but I, I guess not.

29:15.760 --> 29:17.620
I, I said ouch.

29:17.820 --> 29:18.540
That's about it.

29:18.660 --> 29:20.020
I, I can't, I can't really

29:20.020 --> 29:21.000
say no.

29:21.460 --> 29:22.800
I could just say ouch.

29:23.080 --> 29:24.440
It'll, it'll come out when

29:24.440 --> 29:25.000
it comes out.

29:25.060 --> 29:26.320
It'll, it'll come out before

29:26.320 --> 29:28.460
Windows, whatever it is.

29:29.960 --> 29:30.740
Or something.

29:31.260 --> 29:32.280
Um, as for me.

29:33.620 --> 29:34.020
Hopefully.

29:34.260 --> 29:35.200
Gotta, gotta love that.

29:36.800 --> 29:38.140
As for me, I, I really

29:38.140 --> 29:38.900
haven't had any, many, much

29:38.900 --> 29:39.440
projects either.

29:39.560 --> 29:40.180
I've been doing a lot of

29:40.180 --> 29:41.220
work-related stuff lately.

29:41.220 --> 29:43.700
Uh, I, I did a massive

29:43.700 --> 29:46.300
ticking apart my room one

29:46.300 --> 29:47.400
weekend, and I was getting

29:47.400 --> 29:48.740
ready for the MIT flea

29:48.740 --> 29:49.980
just coming up.

29:50.000 --> 29:50.740
I'm going to sell some of

29:50.740 --> 29:51.560
my worldly possessions

29:51.560 --> 29:52.980
because they, I no longer

29:52.980 --> 29:54.000
use them, and they're just

29:54.000 --> 29:54.740
taking up space.

29:55.020 --> 29:57.040
So, that, that's about it

29:57.040 --> 29:57.320
for me.

29:57.380 --> 29:59.320
I haven't been doing much

29:59.320 --> 29:59.660
else.

29:59.900 --> 30:01.000
I'm doing work stuff, but

30:01.000 --> 30:01.780
I'm not going to really talk

30:01.780 --> 30:02.740
about that on air because

30:02.740 --> 30:03.980
I don't think work would

30:03.980 --> 30:04.320
like that.

30:06.120 --> 30:07.060
So, okay.

30:07.200 --> 30:07.980
We're, we're going to move

30:07.980 --> 30:09.860
into our juicy, meaty, you

30:09.860 --> 30:11.000
know, fresh out of the oven

30:11.000 --> 30:12.300
computer subject tonight,

30:12.420 --> 30:14.580
and it's all about Pearl.

30:15.380 --> 30:16.220
Gotta love Pearl.

30:17.180 --> 30:18.540
Ah, I definitely love

30:18.540 --> 30:18.780
Pearl.

30:18.960 --> 30:21.440
Pearl is just the ultimate.

30:21.600 --> 30:22.680
It does everything.

30:23.020 --> 30:23.200
Yeah.

30:23.500 --> 30:24.320
Even when you're not sure

30:24.320 --> 30:25.400
how, how to do it, it just

30:25.400 --> 30:26.120
kind of works somehow.

30:26.420 --> 30:27.200
Yeah, it's, it's all

30:27.200 --> 30:27.500
mystical.

30:27.680 --> 30:28.540
It's like, you know, you,

30:28.660 --> 30:29.460
if you pull apart the

30:29.460 --> 30:30.380
binary, you'll start seeing

30:30.380 --> 30:31.160
like, you know, goat's

30:31.160 --> 30:33.740
guts in the inside and evil

30:33.740 --> 30:34.200
stuff.

30:35.800 --> 30:37.740
You know, okay, so, it's,

30:37.740 --> 30:38.040
it's Pearl.

30:38.200 --> 30:39.760
Pearl stands for practical

30:39.760 --> 30:41.120
extraction and report

30:41.120 --> 30:41.620
language.

30:41.940 --> 30:43.560
It's, so it's, what's the

30:43.560 --> 30:44.240
other term for it?

30:44.380 --> 30:46.360
Practical eclectic rubbish

30:46.360 --> 30:46.940
something?

30:47.940 --> 30:48.940
No, I don't know.

30:49.060 --> 30:49.780
Something like that.

30:49.880 --> 30:50.180
Whatever.

30:50.380 --> 30:50.600
Yeah.

30:50.800 --> 30:51.560
I love Pearl.

30:51.760 --> 30:52.260
Apparently not.

30:52.320 --> 30:53.120
Theory loves Pearl as much

30:53.120 --> 30:53.460
as I do.

30:53.640 --> 30:54.960
Pearl is the Swiss Army

30:54.960 --> 30:57.020
chainsaw of data processing.

30:58.280 --> 30:59.340
You know, given enough time,

30:59.480 --> 31:00.480
effort, and skill, you can,

31:00.540 --> 31:01.360
you can really do anything

31:01.360 --> 31:01.700
with it.

31:01.800 --> 31:03.660
I've made Pearl do things

31:03.660 --> 31:05.060
that no programming languages

31:05.060 --> 31:06.120
should be able to do.

31:06.120 --> 31:07.780
It's, it's, it's scary.

31:07.920 --> 31:08.560
It really is.

31:09.000 --> 31:09.740
You can start building

31:09.740 --> 31:11.640
interfaces to take, you

31:11.640 --> 31:12.540
know, data out of one

31:12.540 --> 31:14.000
portion and pop it into

31:14.000 --> 31:14.740
a completely different

31:14.740 --> 31:16.760
format for Lord knows

31:16.760 --> 31:17.020
what.

31:18.480 --> 31:18.880
Okay.

31:19.000 --> 31:20.940
Well, rather than like,

31:20.980 --> 31:21.500
you know, I can start

31:21.500 --> 31:22.240
babbling with the wonders

31:22.240 --> 31:23.300
of Pearl, but let's start

31:23.300 --> 31:23.960
with the basics, you

31:23.960 --> 31:24.060
know.

31:24.660 --> 31:25.700
Pearl was developed by

31:25.700 --> 31:26.460
Larry Wall.

31:26.640 --> 31:27.680
He developed Pearl

31:27.680 --> 31:28.820
originally as a data

31:28.820 --> 31:29.640
reduction language,

31:29.840 --> 31:31.700
which would something be a

31:31.700 --> 31:32.860
language that is capable of

31:32.860 --> 31:34.040
consuming a lot of data

31:34.040 --> 31:35.480
in a quick and efficient

31:35.480 --> 31:36.780
manner and, you know,

31:36.820 --> 31:38.860
do some various mumbo

31:38.860 --> 31:39.640
jumbo on it and then

31:39.640 --> 31:40.420
spitting out some other

31:40.420 --> 31:40.720
place.

31:41.880 --> 31:43.020
Like I said, Pearl is for

31:43.020 --> 31:44.000
practical extraction

31:44.000 --> 31:44.700
report language.

31:44.960 --> 31:46.540
Pearl is the perfect tool

31:46.540 --> 31:47.520
for system administrators,

31:47.780 --> 31:49.120
and that really isn't

31:49.120 --> 31:49.420
a lie.

31:49.620 --> 31:50.420
It's wonderful.

31:50.700 --> 31:51.560
You can do all kinds of

31:51.560 --> 31:52.320
crazy stuff with it.

31:52.660 --> 31:53.640
It's essentially, it's

31:53.640 --> 31:54.980
shell scripting on steroids.

31:56.380 --> 31:57.500
It, you know, easy

31:57.500 --> 31:58.900
manipulation of files.

31:59.020 --> 31:59.840
You want to go, new,

31:59.920 --> 32:01.500
report about your, your

32:01.500 --> 32:02.500
syslog, just, you know,

32:02.520 --> 32:03.440
make a nice little Pearl

32:03.440 --> 32:05.180
script for it, pop it

32:05.180 --> 32:06.320
in, pull it, and you'll

32:06.320 --> 32:07.060
get this wonderful

32:07.060 --> 32:08.100
properly formatted

32:08.100 --> 32:08.900
report out, basically

32:08.900 --> 32:09.840
into any format you

32:09.840 --> 32:10.140
want.

32:10.860 --> 32:14.780
HTML, XML, SGML, you

32:14.780 --> 32:16.180
know, pretty fine, raw

32:16.180 --> 32:17.120
text, whatever you want

32:17.120 --> 32:17.680
to put it in.

32:18.120 --> 32:18.840
Pearl will do that.

32:18.840 --> 32:19.640
Like a document format?

32:20.680 --> 32:21.680
Can you really do that?

32:21.760 --> 32:21.840
Yeah.

32:22.240 --> 32:23.180
Maybe if they move to

32:23.180 --> 32:23.980
XML, but I don't think

32:23.980 --> 32:24.760
you can actually create a

32:24.760 --> 32:25.700
doc with Pearl, can you?

32:27.680 --> 32:29.220
You know, honestly, I

32:29.220 --> 32:30.080
wouldn't be surprised.

32:30.820 --> 32:31.880
You can, there are some

32:31.880 --> 32:33.420
tricks to get to get

32:33.420 --> 32:34.420
things formatted so

32:34.420 --> 32:35.560
that they kind of look

32:35.560 --> 32:37.520
all right in, in

32:37.520 --> 32:38.200
Microsoft Word.

32:38.280 --> 32:39.200
I had to do it at one

32:39.200 --> 32:39.860
point for somebody.

32:39.980 --> 32:40.720
It's very basic.

32:40.840 --> 32:41.400
You can't really do

32:41.400 --> 32:42.580
crazy things like create

32:42.580 --> 32:43.600
animated three-dimensional

32:43.600 --> 32:45.020
graphs that have sound

32:45.020 --> 32:46.080
and stuff like that, but

32:46.080 --> 32:48.120
you can write it down.

32:48.620 --> 32:49.560
Put, put the Star Wars

32:49.560 --> 32:50.300
theme in your Excel

32:50.300 --> 32:50.700
report.

32:51.580 --> 32:52.580
Yeah, you can't, you

32:52.580 --> 32:53.240
can't really do that.

32:53.360 --> 32:54.500
Due to copyright reasons

32:54.500 --> 32:54.900
as well.

32:55.160 --> 32:55.280
Yeah.

32:55.280 --> 33:00.340
But, yeah, you can, you

33:00.340 --> 33:01.380
can do crazy stuff with it.

33:01.380 --> 33:01.560
Yeah.

33:01.840 --> 33:03.580
Well, I mean, even with

33:03.580 --> 33:05.760
it is, you can put it in

33:05.760 --> 33:06.100
RTF.

33:06.300 --> 33:07.680
RTF is a standard supported

33:07.680 --> 33:08.140
by Word.

33:08.700 --> 33:09.800
And you can also put it

33:09.800 --> 33:10.480
into a lot of other

33:10.480 --> 33:11.600
standards that Word

33:11.600 --> 33:12.620
understands or Excel

33:12.620 --> 33:13.740
understands, but aren't

33:13.740 --> 33:15.160
really Excel files, like

33:15.160 --> 33:16.460
stuff like, you know,

33:16.540 --> 33:17.480
comma-separated value

33:17.480 --> 33:18.620
files or tab-separated

33:18.620 --> 33:19.280
value files.

33:19.420 --> 33:20.440
You know, Pearl loves

33:20.440 --> 33:20.940
that stuff.

33:21.060 --> 33:22.340
It's insanely simple to

33:22.340 --> 33:23.740
have stuff inputted or

33:23.740 --> 33:24.520
outputted via that.

33:27.020 --> 33:28.480
Pearl is another thing

33:28.480 --> 33:29.420
that's, it's really cool

33:29.420 --> 33:30.220
for people who write

33:30.220 --> 33:31.520
CGI bin scripts or

33:31.520 --> 33:32.340
common gateway interface,

33:32.440 --> 33:33.200
basically, uh, web

33:33.200 --> 33:34.700
scripts, and you can

33:34.700 --> 33:35.780
process web forms with

33:35.780 --> 33:35.920
it.

33:36.280 --> 33:38.160
It has a nice, uh, plug-in

33:38.160 --> 33:39.220
for Apache called Mod

33:39.220 --> 33:39.540
Pearl.

33:40.140 --> 33:41.180
It's, it's very fast.

33:41.260 --> 33:41.880
It's very efficient.

33:43.040 --> 33:44.420
I'm starting kind of

33:44.420 --> 33:45.320
shying away from that

33:45.320 --> 33:46.400
because I'm, I'm, I've,

33:46.400 --> 33:47.280
I've fallen in love with

33:47.280 --> 33:49.980
PHP, but it's, I, I cut

33:49.980 --> 33:51.000
my teeth on that for web

33:51.000 --> 33:51.440
programming.

33:51.820 --> 33:52.780
It, it works like a

33:52.780 --> 33:53.000
charm.

33:53.380 --> 33:54.280
A lot of people call it,

33:54.280 --> 33:55.300
uh, something, let's see,

33:55.340 --> 33:55.940
I have it in my notes

33:55.940 --> 33:57.640
here, the glue that holds

33:57.640 --> 33:58.960
the web together, and

33:58.960 --> 33:59.880
I'm, I'm sure some

33:59.880 --> 34:00.680
market droid came up

34:00.680 --> 34:01.280
with that someplace.

34:02.660 --> 34:03.600
It's, it, the good

34:03.600 --> 34:04.400
thing about, for CGI

34:04.400 --> 34:05.460
programming, it's, it's

34:05.460 --> 34:07.200
really useful for string

34:07.200 --> 34:08.720
manipulation, and, like,

34:08.860 --> 34:09.920
it, it comes in handy,

34:10.040 --> 34:10.800
Pearl comes in handy for

34:10.800 --> 34:11.780
that all across the

34:11.780 --> 34:11.940
board.

34:12.020 --> 34:12.980
It's not just, it's not

34:12.980 --> 34:14.080
just for web programming

34:14.080 --> 34:14.780
anymore.

34:16.420 --> 34:17.520
Um, like I said, you

34:17.520 --> 34:18.920
know, Pearl syntax, it,

34:18.920 --> 34:19.920
it's essentially, it's,

34:19.920 --> 34:20.840
it's shell scripting on

34:20.840 --> 34:21.260
steroids.

34:21.420 --> 34:22.000
It's an interpretive

34:22.000 --> 34:22.360
language.

34:22.440 --> 34:22.840
You don't have to

34:22.840 --> 34:23.380
compile it.

34:23.540 --> 34:25.000
It, it resembles shell

34:25.000 --> 34:25.540
programs.

34:25.760 --> 34:26.820
It also has a bit of C.

34:26.820 --> 34:28.820
Uh, it has a lot of

34:28.820 --> 34:30.300
functions that are built

34:30.300 --> 34:31.540
into, uh, aux, set, and

34:31.540 --> 34:32.360
grep, which are Unix

34:32.360 --> 34:33.700
command line utilities for

34:33.700 --> 34:34.420
data processing.

34:35.700 --> 34:37.040
It, it, it's, it's very

34:37.040 --> 34:37.980
easy to learn.

34:38.980 --> 34:40.540
Uh, one of the things to

34:40.540 --> 34:41.180
always remember about

34:41.180 --> 34:42.000
Pearl, there's, there's

34:42.000 --> 34:43.480
always one more way, one

34:43.480 --> 34:44.720
way, more than one way to

34:44.720 --> 34:45.060
do it.

34:45.160 --> 34:46.180
You know, put five people

34:46.180 --> 34:46.800
in, probably Pearl

34:46.800 --> 34:47.520
programmers in the same

34:47.520 --> 34:48.640
room, tell them to write

34:48.640 --> 34:49.900
a certain piece of code

34:49.900 --> 34:50.740
that does a certain thing,

34:50.740 --> 34:52.700
and you'll see, like, you

34:52.700 --> 34:53.580
know, five different ways

34:53.580 --> 34:54.060
of doing it.

34:54.060 --> 34:54.800
It's, it's kind of

34:54.800 --> 34:55.100
creepy.

34:55.980 --> 34:56.940
Yeah, one will be an

34:56.940 --> 34:58.280
obfuscated piece of code

34:58.280 --> 34:59.960
that looks like a cat, and

34:59.960 --> 35:00.640
the other one will be

35:00.640 --> 35:02.220
nice, straightforward, you

35:02.220 --> 35:02.980
know, commented and

35:02.980 --> 35:04.460
everything, and people can

35:04.460 --> 35:05.440
do insane stuff.

35:06.080 --> 35:07.060
Yeah, it's, it's nice.

35:07.820 --> 35:09.100
Uh, I, I took a Pearl

35:09.100 --> 35:12.300
class one, and they, they

35:12.300 --> 35:13.760
had, like, an assignment,

35:13.980 --> 35:15.360
and I, I compared it to my

35:15.360 --> 35:16.940
neighbors sometimes, and

35:16.940 --> 35:18.300
mine looked completely

35:18.300 --> 35:19.300
different from his, and

35:19.300 --> 35:20.440
we both got, like, A's on

35:20.440 --> 35:21.260
it, or check pluses,

35:21.260 --> 35:21.860
whatever, I thought they

35:21.860 --> 35:24.500
created it that week, but

35:24.500 --> 35:26.800
it's, it's, it's creepy.

35:26.920 --> 35:27.540
It really is.

35:28.760 --> 35:31.000
Uh, I, I learned Pearl

35:31.000 --> 35:32.500
immediately after I started

35:32.500 --> 35:33.120
learning Linux.

35:33.320 --> 35:35.280
I, I looked for, I, I did a

35:35.280 --> 35:36.460
lot of data program, data

35:36.460 --> 35:36.940
processing.

35:37.100 --> 35:37.860
Well, technically, I still

35:37.860 --> 35:38.080
do.

35:38.640 --> 35:40.340
So, when I, I was

35:40.340 --> 35:41.420
basically asked to, you

35:41.420 --> 35:42.240
know, convert some stuff

35:42.240 --> 35:43.060
and start looking into

35:43.060 --> 35:44.580
ways of moving some of our

35:44.580 --> 35:45.640
applications over to Linux,

35:45.740 --> 35:47.020
because I was the pimply-faced

35:47.020 --> 35:48.380
youth, and I had tons of

35:48.380 --> 35:48.800
free time.

35:48.800 --> 35:50.200
So, I was looking for a

35:50.200 --> 35:52.460
simple, easy-to-learn, you

35:52.460 --> 35:53.740
know, succinct data

35:53.740 --> 35:55.040
processing language, and

35:55.040 --> 35:56.220
lo and behold, I was

35:56.220 --> 35:56.880
introduced to Pearl.

35:57.880 --> 35:59.100
I, I fell in love with

35:59.100 --> 35:59.600
Pearl quickly.

35:59.760 --> 36:00.660
It's, it's a breeze to

36:00.660 --> 36:02.300
learn, and it's infinitely

36:02.300 --> 36:04.220
easy to mince data and

36:04.220 --> 36:05.180
munch it about and change

36:05.180 --> 36:06.600
it around and do whatever

36:06.600 --> 36:07.180
you want to it.

36:07.960 --> 36:09.180
Uh, I, I use it regularly

36:09.180 --> 36:10.500
to change formats of, you

36:10.500 --> 36:11.460
know, some of, we have,

36:11.600 --> 36:13.460
like, five or six different

36:13.460 --> 36:14.760
data standards of work, at

36:14.760 --> 36:15.660
work, depending on where

36:15.660 --> 36:16.620
we're getting our data from

36:16.620 --> 36:17.460
or where we're sending it

36:17.460 --> 36:20.300
to, and I, I have about,

36:20.380 --> 36:21.380
you know, ten Pearl scripts

36:21.380 --> 36:22.700
that, you know, convert it

36:22.700 --> 36:23.740
from one format to another,

36:23.740 --> 36:25.220
and I actually, you know,

36:25.320 --> 36:26.040
pasted them all together

36:26.040 --> 36:27.020
one day, and I wrote this

36:27.020 --> 36:28.100
little command line utility

36:28.100 --> 36:28.840
that says, you give it

36:28.840 --> 36:30.380
two files, it determines

36:30.380 --> 36:31.820
which one, which format

36:31.820 --> 36:33.500
each file is in, and it

36:33.500 --> 36:34.260
converts them immediately.

36:34.640 --> 36:36.960
It's, it's amazing,

36:37.240 --> 36:38.160
considering that no one's

36:38.160 --> 36:39.000
able to ever do that

36:39.000 --> 36:40.120
before I came there, but

36:40.120 --> 36:41.520
we won't get into that.

36:41.520 --> 36:45.260
Um, you know, more than,

36:45.320 --> 36:45.880
like I said, more than

36:45.880 --> 36:46.940
once someone complains

36:46.940 --> 36:48.280
about, you know, someone

36:48.280 --> 36:49.520
upstairs says, oh, we have

36:49.520 --> 36:50.700
data in this format, and

36:50.700 --> 36:51.780
someone wants it downstairs

36:51.780 --> 36:52.940
with, you know, format two,

36:53.600 --> 36:55.280
and it could be two things

36:55.280 --> 36:55.980
that I've never heard from

36:55.980 --> 36:57.220
before, but I can usually

36:57.220 --> 36:58.040
have a Pearl solution

36:58.040 --> 36:58.940
coded up in about a half

36:58.940 --> 36:59.200
hour.

36:59.440 --> 37:00.860
It's, it's, it's amazing

37:00.860 --> 37:01.400
what it can do.

37:01.780 --> 37:02.680
As long as you write it in

37:02.680 --> 37:03.720
some type of standard format

37:03.720 --> 37:04.420
and you want it to some

37:04.420 --> 37:05.280
other standard format,

37:06.120 --> 37:06.700
Pearl is there.

37:06.840 --> 37:07.540
Pearl can handle it.

37:07.640 --> 37:09.040
Pearl can, you know, do

37:09.040 --> 37:09.480
whatever you want.

37:09.560 --> 37:10.260
Pearl, Pearl, Pearl.

37:10.260 --> 37:11.840
So, developers, developers,

37:12.080 --> 37:12.440
developers.

37:13.200 --> 37:14.160
Oh, man.

37:14.600 --> 37:15.520
Were you there for any of

37:15.520 --> 37:16.760
that fiasco at DefCon?

37:17.420 --> 37:17.820
No.

37:17.920 --> 37:18.620
What, what fiasco?

37:19.980 --> 37:22.860
Well, me and, uh, Slipmode

37:22.860 --> 37:23.820
and some other guys, we

37:23.820 --> 37:24.680
kind of, like, bounced

37:24.680 --> 37:25.800
around from party to party

37:25.800 --> 37:28.580
at DefCon, and, um, I

37:28.580 --> 37:29.200
don't remember if it was

37:29.200 --> 37:31.200
his idea or mine, but we

37:31.200 --> 37:32.240
just started chanting

37:32.240 --> 37:33.460
developers, developers,

37:33.680 --> 37:34.580
developers, developers,

37:34.680 --> 37:36.020
over and over and over

37:36.020 --> 37:37.260
again in all of these

37:37.260 --> 37:38.360
different places just to

37:38.360 --> 37:39.060
see if we could get

37:39.060 --> 37:39.860
these different, like,

37:39.860 --> 37:41.780
completely separate

37:41.780 --> 37:43.020
crowds to start chanting

37:43.020 --> 37:43.700
at different times.

37:43.760 --> 37:45.120
It works rather well

37:45.120 --> 37:46.240
at a place like DefCon.

37:46.820 --> 37:48.720
Um, but yeah.

37:48.780 --> 37:49.080
Because everyone

37:49.080 --> 37:49.760
understands it.

37:50.660 --> 37:51.620
I mean, I could run

37:51.620 --> 37:52.960
downstairs and, you

37:52.960 --> 37:54.360
know, go outside and

37:54.360 --> 37:55.020
start running up to a

37:55.020 --> 37:55.600
random group of people

37:55.600 --> 37:56.420
and saying, developers,

37:56.660 --> 37:57.540
developers, developers,

37:57.720 --> 37:58.440
and I'll get huddled

37:58.440 --> 37:59.160
away by the police

37:59.160 --> 37:59.720
because they'll think

37:59.720 --> 38:00.440
I'm an insane person.

38:01.580 --> 38:02.400
Yeah, but not at

38:02.400 --> 38:02.800
DefCon.

38:02.960 --> 38:03.560
Not at DefCon.

38:03.580 --> 38:03.840
Anyway.

38:04.080 --> 38:04.760
Or at Microsoft

38:04.760 --> 38:05.720
references, apparently.

38:06.820 --> 38:08.000
Oh, where were they?

38:08.220 --> 38:09.200
Did I cover where we

38:09.200 --> 38:09.680
can get Perl?

38:09.820 --> 38:10.380
No, I don't think

38:10.380 --> 38:10.860
I discovered where

38:10.860 --> 38:11.380
we can get Perl.

38:12.500 --> 38:13.500
Perl is cool because

38:13.500 --> 38:14.120
for those of you

38:14.120 --> 38:14.940
with access to a Linux

38:14.940 --> 38:15.940
system, chances are

38:15.940 --> 38:16.720
you probably already

38:16.720 --> 38:17.080
have it.

38:17.820 --> 38:18.400
You know, a simple way

38:18.400 --> 38:19.220
of doing this, for

38:19.220 --> 38:19.700
those of you who

38:19.700 --> 38:20.240
don't know, is

38:20.240 --> 38:21.120
basically you type in

38:21.120 --> 38:22.660
which, which as in

38:22.660 --> 38:24.580
W-H-I-C-H, then

38:24.580 --> 38:25.620
space Perl, and, you

38:25.620 --> 38:26.100
know, see if it

38:26.100 --> 38:27.680
returns a command.

38:27.800 --> 38:28.320
Like, it should say,

38:28.440 --> 38:29.800
you know, user Perl

38:29.800 --> 38:31.100
or bin Perl or user

38:31.100 --> 38:31.920
bin Perl, user

38:31.920 --> 38:32.620
little bin Perl.

38:32.700 --> 38:33.260
So just, you know,

38:33.260 --> 38:33.980
some type of command

38:33.980 --> 38:35.220
where it's a file

38:35.220 --> 38:35.760
somewhere in the

38:35.760 --> 38:36.400
directory structure.

38:38.000 --> 38:39.320
If you haven't, you're

38:39.320 --> 38:39.800
good to go.

38:39.920 --> 38:41.060
You are ready to take

38:41.060 --> 38:42.080
a plunge into the

38:42.080 --> 38:45.260
Perl pool something.

38:45.540 --> 38:46.480
I could think of a

38:46.480 --> 38:47.940
good way of coming

38:47.940 --> 38:48.360
out with that.

38:49.640 --> 38:50.620
Basically, if you

38:50.620 --> 38:51.420
don't have it, tough

38:51.420 --> 38:51.680
luck.

38:52.320 --> 38:53.140
What you need to do

38:53.140 --> 38:54.340
is see if your

38:54.340 --> 38:54.860
package management

38:54.860 --> 38:55.720
system has it and

38:55.720 --> 38:56.860
install it, or if you

38:56.860 --> 38:57.480
want, you can go to

38:57.480 --> 38:59.640
www.perl.org.

38:59.880 --> 39:00.820
By the way, Perl is

39:00.820 --> 39:01.360
actually spelled

39:01.360 --> 39:02.600
P-E-R-L for those

39:02.600 --> 39:03.160
of you who can't,

39:03.180 --> 39:04.360
you know, convert the

39:04.360 --> 39:06.120
name back to the

39:06.120 --> 39:06.420
acronym.

39:07.300 --> 39:07.700
It would be

39:07.700 --> 39:08.960
Perl.org, you have

39:08.960 --> 39:09.600
it available for

39:09.600 --> 39:10.080
download and

39:10.080 --> 39:10.420
compiling.

39:10.580 --> 39:11.240
I've never actually

39:11.240 --> 39:11.760
compiled it.

39:13.140 --> 39:13.860
It's one of those

39:13.860 --> 39:14.540
things that I don't

39:14.540 --> 39:15.020
like to compile

39:15.020 --> 39:15.800
programming languages

39:15.800 --> 39:16.280
because it can be

39:16.280 --> 39:16.860
very messy.

39:18.180 --> 39:18.940
So I just use

39:18.940 --> 39:19.700
the package manager.

39:20.600 --> 39:21.420
And it takes a

39:21.420 --> 39:21.880
while, too.

39:21.960 --> 39:23.400
I've done it on

39:23.400 --> 39:24.140
Gentoo, and it

39:24.140 --> 39:24.560
doesn't take a

39:24.560 --> 39:25.300
ridiculous amount of

39:25.300 --> 39:26.460
time, but you

39:26.460 --> 39:27.420
don't have a fast

39:27.420 --> 39:27.940
machine, you can

39:27.940 --> 39:28.520
wait for a while.

39:29.220 --> 39:29.880
Do you know how

39:29.880 --> 39:30.360
big the source

39:30.360 --> 39:30.940
distribution is?

39:32.380 --> 39:33.680
I actually have

39:33.680 --> 39:34.540
no idea.

39:36.040 --> 39:37.020
I am also

39:37.020 --> 39:37.260
unaware.

39:38.280 --> 39:39.000
Oh, by the way,

39:39.060 --> 39:39.440
you asked me to

39:39.440 --> 39:40.380
check before, Open

39:40.380 --> 39:42.420
BSD has had only

39:42.420 --> 39:43.720
one, you are

39:43.720 --> 39:44.520
correct, remote

39:44.520 --> 39:46.440
root exploit in

39:46.440 --> 39:48.220
eight years.

39:48.360 --> 39:48.980
Eight years?

39:49.160 --> 39:49.400
Wow.

39:49.660 --> 39:50.120
Eight years.

39:50.960 --> 39:52.040
Good for Theo.

39:52.160 --> 39:52.520
I'm sorry.

39:52.700 --> 39:53.120
A lot of people,

39:53.200 --> 39:53.800
he gets a lot of

39:53.800 --> 39:54.460
flack as a prima

39:54.460 --> 39:55.840
donna, but he's

39:55.840 --> 39:56.680
got the skills to

39:56.680 --> 39:57.920
back that up.

39:58.040 --> 39:58.660
I don't care what

39:58.660 --> 39:58.880
you say.

39:59.020 --> 39:59.740
If you have enough,

39:59.740 --> 40:00.500
if you can talk

40:00.500 --> 40:00.960
the talk and

40:00.960 --> 40:01.500
walk the walk,

40:01.600 --> 40:02.280
go right ahead.

40:03.060 --> 40:03.460
It's just all

40:03.460 --> 40:04.020
these people who

40:04.020 --> 40:04.780
constantly complain

40:04.780 --> 40:05.200
and they can't

40:05.200 --> 40:05.740
do anything about

40:05.740 --> 40:05.880
it.

40:07.940 --> 40:08.700
Also, one of the

40:08.700 --> 40:09.480
fun things, for

40:09.480 --> 40:09.880
those of you with

40:09.880 --> 40:10.920
Windows, you can

40:10.920 --> 40:11.400
run Perl.

40:12.260 --> 40:12.960
It's a little bit

40:12.960 --> 40:13.420
more tricky.

40:14.000 --> 40:14.840
However, there's a

40:14.840 --> 40:15.940
distribution for

40:15.940 --> 40:16.560
Perl for Windows.

40:16.680 --> 40:17.520
It's done by a

40:17.520 --> 40:18.000
company called

40:18.000 --> 40:18.680
ActiveState.

40:18.680 --> 40:21.100
It's ActiveState.com.

40:22.280 --> 40:23.400
Basically, the links

40:23.400 --> 40:24.380
there are horrible

40:24.380 --> 40:25.280
and I really didn't

40:25.280 --> 40:26.340
feel like tiny URL-ing

40:26.340 --> 40:27.600
it, so click away.

40:27.680 --> 40:28.200
You'll see it right

40:28.200 --> 40:28.440
there.

40:28.540 --> 40:29.680
It's ActivePerl

40:29.680 --> 40:31.000
5.8 something or

40:31.000 --> 40:31.120
other.

40:31.780 --> 40:32.460
Basically, what they

40:32.460 --> 40:33.700
do is they take the

40:33.700 --> 40:35.140
Perl source distribution

40:35.140 --> 40:36.240
and port it over to

40:36.240 --> 40:36.560
Windows.

40:37.000 --> 40:38.260
It runs fine.

40:38.480 --> 40:39.480
It's a simple way to

40:39.480 --> 40:39.900
install it.

40:39.940 --> 40:40.840
It's an MSI file,

40:40.940 --> 40:41.620
download it, double

40:41.620 --> 40:42.260
click it, and you're

40:42.260 --> 40:42.900
set to go.

40:43.840 --> 40:44.740
It works fairly

40:44.740 --> 40:45.580
consistently as the

40:45.580 --> 40:46.540
Linux version or the

40:46.540 --> 40:47.360
other Unix version.

40:47.360 --> 40:47.960
It doesn't have to

40:47.960 --> 40:48.840
necessarily be Linux,

40:48.900 --> 40:49.260
by the way.

40:49.320 --> 40:49.880
It's any Unix.

40:50.300 --> 40:51.500
FreeBSD, OpenBSD,

40:51.580 --> 40:52.400
NetBSD, probably

40:52.400 --> 40:52.900
all have it.

40:53.820 --> 40:54.940
I think it even

40:54.940 --> 40:56.100
works on VMS, which

40:56.100 --> 40:58.180
two people run still,

40:58.260 --> 40:58.680
but anyway.

41:00.800 --> 41:01.460
The problem with the

41:01.460 --> 41:02.560
Linux version is,

41:02.620 --> 41:03.020
I'm sorry, the

41:03.020 --> 41:03.420
problem with the

41:03.420 --> 41:04.280
Windows version is

41:04.280 --> 41:05.780
that there's some

41:05.780 --> 41:07.160
idiosyncrasies between

41:07.160 --> 41:08.380
Windows and Perl.

41:09.900 --> 41:10.660
I'm sorry, with

41:10.660 --> 41:11.360
Windows and Linux.

41:12.080 --> 41:13.140
They're not always the

41:13.140 --> 41:14.640
same, and I'll go

41:14.640 --> 41:15.120
into some of the

41:15.120 --> 41:15.720
differences later,

41:15.720 --> 41:16.280
one of the major

41:16.280 --> 41:16.980
ones that I hate.

41:17.360 --> 41:20.180
So, okay, you have

41:20.180 --> 41:21.320
it installed, you're

41:21.320 --> 41:22.380
ready to go, let's go

41:22.380 --> 41:23.060
find a tutorial.

41:23.920 --> 41:24.840
An excellent tutorial

41:24.840 --> 41:26.160
that I like, that I

41:26.160 --> 41:27.240
learned on, but it's

41:27.240 --> 41:28.800
still very, it still

41:28.800 --> 41:29.700
all works, it's called

41:29.700 --> 41:30.440
Robert's Pearl

41:30.440 --> 41:31.460
Tutorial, and it's

41:31.460 --> 41:34.920
tinyurl.com slash

41:34.920 --> 41:36.760
6 Sierra November

41:36.760 --> 41:37.840
5 Lima.

41:38.960 --> 41:39.840
This is what I

41:39.840 --> 41:41.600
learned on, however,

41:41.780 --> 41:42.380
it hasn't been

41:42.380 --> 41:43.840
updated, I think, by

41:43.840 --> 41:44.680
the time I saw it,

41:44.680 --> 41:45.640
it's been updated the

41:45.640 --> 41:46.300
last time it was

41:46.300 --> 41:46.660
updated.

41:47.360 --> 41:48.980
As in, you know, I

41:48.980 --> 41:49.460
think it was updated

41:49.460 --> 41:51.440
April 21st, 2005.

41:52.340 --> 41:53.500
So, I'm sorry, April

41:53.500 --> 41:55.540
21st, 1999, and here

41:55.540 --> 41:56.920
it is 2005, about six

41:56.920 --> 41:57.380
years later.

41:59.060 --> 41:59.500
Yeah.

42:00.400 --> 42:02.440
So, but anyway, it

42:02.440 --> 42:03.200
hasn't changed that

42:03.200 --> 42:06.640
much, so it's not

42:06.640 --> 42:07.300
going to be a major

42:07.300 --> 42:07.620
thing.

42:08.500 --> 42:09.320
Yeah, the basics are

42:09.320 --> 42:09.680
all the same.

42:09.680 --> 42:10.780
Yeah, the basics are all

42:10.780 --> 42:11.160
the same.

42:11.840 --> 42:12.800
You might, I think it

42:12.800 --> 42:14.180
was probably, it's still

42:14.180 --> 42:14.980
the major distribution,

42:15.160 --> 42:15.840
everything right now is

42:15.840 --> 42:17.000
running on Perl 5, they're

42:17.000 --> 42:17.960
coming up with Perl 6,

42:18.700 --> 42:20.100
quote, real soon now,

42:20.160 --> 42:21.100
unquote, but we won't

42:21.100 --> 42:21.620
get into that.

42:23.780 --> 42:24.880
And, you know, it's still

42:24.880 --> 42:25.760
the major division, all the

42:25.760 --> 42:26.580
syntax still there,

42:26.740 --> 42:27.820
everything works, all the

42:27.820 --> 42:28.960
basics are, you know,

42:28.960 --> 42:29.940
haven't changed at all.

42:29.940 --> 42:33.900
But, it, it, everything

42:33.900 --> 42:34.500
works fine.

42:36.320 --> 42:37.880
Another book that I

42:37.880 --> 42:39.460
found was Pick Up Perl,

42:39.540 --> 42:42.540
Pick Up Perl, and it's

42:42.540 --> 42:44.740
very, it's an e-book, it's

42:44.740 --> 42:46.420
all in a tar-gz format, but

42:46.420 --> 42:47.300
it's pretty good.

42:47.360 --> 42:48.100
I was sort of thumbing

42:48.100 --> 42:48.940
through it at work because

42:48.940 --> 42:50.520
our internet decided to

42:50.520 --> 42:51.300
crash today, and it's

42:51.300 --> 42:54.500
tinyurl.com slash 99hon.

42:56.680 --> 42:57.720
They're both, like I said,

42:57.780 --> 42:58.580
both very straightforward

42:58.580 --> 43:01.360
on Perl, it's, and they're

43:01.360 --> 43:02.760
really easy to follow, and

43:02.760 --> 43:03.720
once you get the basics

43:03.720 --> 43:05.040
down, it's, it all built on

43:05.040 --> 43:07.100
top of itself, so, I mean,

43:07.480 --> 43:09.080
like I said, Perl is a

43:09.080 --> 43:09.680
breeze to learn.

43:09.900 --> 43:11.240
All of the limits you see

43:11.240 --> 43:13.180
in C, you see in C++, Perl

43:13.180 --> 43:13.960
just sort of throws them

43:13.960 --> 43:16.720
out the window, and it's,

43:16.720 --> 43:17.180
it's fine.

43:18.820 --> 43:20.080
So, one of the best

43:20.080 --> 43:21.180
features I found about Perl

43:21.180 --> 43:21.860
is that it has something

43:21.860 --> 43:23.820
called modules, and modules

43:23.820 --> 43:25.240
are libraries and bits of

43:25.240 --> 43:26.860
code that people make that

43:26.860 --> 43:27.720
you can include in your

43:27.720 --> 43:28.560
program that automatically

43:28.580 --> 43:29.740
made it certain methods

43:29.740 --> 43:30.640
and certain functions.

43:31.980 --> 43:32.980
You know, for example,

43:33.600 --> 43:34.980
the one that I really

43:34.980 --> 43:36.760
found in handy was back

43:36.760 --> 43:37.500
about a month ago, I

43:37.500 --> 43:38.600
needed to have a bot for

43:38.600 --> 43:40.500
binrev, for those of you

43:40.500 --> 43:42.220
who, I'm sorry, a bot for

43:42.220 --> 43:43.400
the pound binrev, which is

43:43.400 --> 43:44.420
our IRC channel on

43:44.420 --> 43:45.840
irc.dal.net.

43:47.580 --> 43:49.260
So, after looking at a

43:49.260 --> 43:50.080
bunch of bots, like, you

43:50.080 --> 43:51.760
know, what is it, emec and

43:51.760 --> 43:52.840
eggdrop and all the other

43:52.840 --> 43:54.820
ones, I found that none of

43:54.820 --> 43:55.960
them really fit my needs, so

43:55.960 --> 43:57.760
I, basically, I sat down and

43:57.760 --> 43:58.640
started figuring out, okay,

43:58.680 --> 44:00.520
I need to code a bot, and

44:00.520 --> 44:01.300
of course, what did I pick

44:01.300 --> 44:02.960
but Perl, because Perl can

44:02.960 --> 44:03.540
do everything.

44:05.100 --> 44:06.740
Now, you know, normally

44:06.740 --> 44:08.000
with a programming language,

44:08.080 --> 44:08.900
you have to write a way to

44:08.900 --> 44:09.740
sometime to connect with a

44:09.740 --> 44:11.200
socket, a way to write data

44:11.200 --> 44:13.740
to the socket, read data

44:13.740 --> 44:14.640
from the socket, control

44:14.640 --> 44:15.680
idle checks, watch for

44:15.680 --> 44:16.700
disconnections, watch for

44:16.700 --> 44:17.840
joins, do all the stuff in

44:17.840 --> 44:18.940
the channel, send to a

44:18.940 --> 44:20.340
channel, and basically, I'd

44:20.340 --> 44:21.160
have to start reading the

44:21.160 --> 44:24.020
protocol RFC and handling it

44:24.020 --> 44:25.440
that way, however, you know,

44:25.480 --> 44:27.220
Which, I'll tell you, for

44:27.220 --> 44:29.720
IRC is, IRC is basically a

44:29.720 --> 44:31.060
telnet session, but still, it

44:31.060 --> 44:32.540
is annoying to write a

44:32.540 --> 44:33.560
client from scratch, I had

44:33.560 --> 44:34.340
to do it for a programming

44:34.340 --> 44:35.520
class once, and it sucked.

44:35.800 --> 44:36.820
You had to write an IRC

44:36.820 --> 44:38.780
channel for, ooh, I mean,

44:38.840 --> 44:38.900
that was...

44:38.900 --> 44:39.620
Yeah, I had to write a

44:39.620 --> 44:40.940
telnet client, and one of the

44:40.940 --> 44:44.100
tests was to make a couple

44:44.100 --> 44:45.500
of modifications and use it

44:45.500 --> 44:47.120
as an IRC client.

44:47.240 --> 44:48.880
It was terrible.

44:49.540 --> 44:49.700
Yeah.

44:52.020 --> 44:54.100
Some of us, I mean, I have

44:54.100 --> 44:55.000
one of us, I was actually

44:55.000 --> 44:55.920
trying to do something with

44:55.920 --> 44:57.640
C++ and sockets, and it was

44:57.640 --> 44:58.600
just, it was painful.

44:59.080 --> 44:59.780
It really was.

44:59.880 --> 45:00.620
I couldn't even imagine

45:00.620 --> 45:01.860
trying to implement the IRC

45:01.860 --> 45:04.080
protocol, because even though

45:04.080 --> 45:05.540
it's telnet, it handles all

45:05.540 --> 45:06.480
of its messages in a certain

45:06.480 --> 45:08.140
format, there's an RFC for it,

45:08.200 --> 45:10.320
I think it's 43, 35, I don't

45:10.320 --> 45:11.220
know, I'm not even going to

45:11.220 --> 45:11.920
throw a number out there.

45:12.440 --> 45:13.700
There's some RFC out there,

45:13.760 --> 45:16.000
and there's about, I think

45:16.000 --> 45:17.260
there's like 400 different

45:17.260 --> 45:19.560
types of messages you have

45:19.560 --> 45:21.880
to handle that, you know,

45:21.940 --> 45:23.600
to be perfectly functioning

45:23.600 --> 45:24.520
as an IRC client.

45:25.400 --> 45:27.300
So, I mean, I was just ready

45:27.300 --> 45:28.460
to cry, and I was figuring

45:28.460 --> 45:29.280
that I'd have to do this

45:29.280 --> 45:30.220
over a telnet session.

45:30.800 --> 45:31.560
However, there's something

45:31.560 --> 45:33.020
called, thanks to the

45:33.020 --> 45:34.020
wonders of modules, there's

45:34.020 --> 45:35.120
something called PoE

45:35.120 --> 45:38.320
Component IRC, and I tossed

45:38.320 --> 45:40.740
it into my thing, and I started

45:40.740 --> 45:41.660
writing code around it, and

45:41.660 --> 45:43.020
what it is, basically, every

45:43.020 --> 45:44.100
time something happens, it

45:44.100 --> 45:44.980
calls a certain function.

45:45.140 --> 45:46.660
You say, okay, when X

45:46.660 --> 45:47.760
happens, do this.

45:47.840 --> 45:49.360
When Y happens, do this.

45:49.620 --> 45:50.800
When Z happens, do this

45:50.800 --> 45:51.200
other thing.

45:52.240 --> 45:54.020
And quite literally, this

45:54.020 --> 45:55.840
model saved, this module

45:55.840 --> 45:57.980
saved me weeks upon weeks

45:57.980 --> 45:59.500
of coding, because I, and

45:59.500 --> 46:00.780
quite frankly, this module

46:00.780 --> 46:01.680
saved me, because I don't

46:01.680 --> 46:02.540
think I'd be able to write a

46:02.540 --> 46:04.220
bot in Perl or any other

46:04.220 --> 46:05.900
language that handles the

46:05.900 --> 46:06.640
IRC protocol.

46:07.640 --> 46:08.320
It's nuts.

46:09.900 --> 46:11.980
So, and, you know, we have

46:11.980 --> 46:12.900
all these modules, and that's

46:12.900 --> 46:13.740
a really cool idea.

46:13.740 --> 46:15.760
Yeah, so it's cool by

46:15.760 --> 46:16.660
itself, but what all the

46:16.660 --> 46:17.960
maintainers did a few years

46:17.960 --> 46:19.260
back, actually, I have no

46:19.260 --> 46:21.140
idea when they did it, they

46:21.140 --> 46:22.240
said, no, oh, geez, we have

46:22.240 --> 46:23.620
all these modules, we should

46:23.620 --> 46:24.260
make them easy to get.

46:24.800 --> 46:26.120
So they made a project called

46:26.120 --> 46:27.540
the Comprehensive Perl

46:27.540 --> 46:29.140
Archive Network, or CPAN.

46:30.500 --> 46:31.480
I'm assuming I'm pronouncing

46:31.480 --> 46:31.820
that right.

46:31.860 --> 46:32.700
I've never actually heard it

46:32.700 --> 46:33.640
pronounced by somebody.

46:34.480 --> 46:36.000
Actually, every person that I

46:36.000 --> 46:37.060
know that uses it calls it

46:37.060 --> 46:37.520
CPAN.

46:37.780 --> 46:38.200
Oh, okay.

46:38.200 --> 46:40.760
And they worship it, because

46:40.760 --> 46:42.540
it is one of the greatest

46:42.540 --> 46:43.080
things ever.

46:43.420 --> 46:45.620
Yeah, well, let's explain

46:45.620 --> 46:46.000
what it is.

46:46.060 --> 46:46.640
We'll just spell it the

46:46.640 --> 46:47.460
best thing ever, and we'll

46:47.460 --> 46:48.160
just leave it at that.

46:49.100 --> 46:49.900
Yeah, that's cool.

46:50.020 --> 46:50.540
Just forget it.

46:50.680 --> 46:51.400
Yeah, it's a CPAN.

46:51.520 --> 46:52.100
That's what it is.

46:52.140 --> 46:53.580
CPAN is the shizzle.

46:54.020 --> 46:54.800
Just use it.

46:54.920 --> 46:55.640
We won't tell you how to

46:55.640 --> 46:56.640
use it, but you should be

46:56.640 --> 46:57.780
using it if you use Perl.

46:59.780 --> 47:02.660
No, anyway, but what CPAN

47:02.660 --> 47:04.260
is, it's basically a giant

47:04.260 --> 47:05.220
laundry list of all the

47:05.220 --> 47:06.900
modules that, you know,

47:06.960 --> 47:07.780
basically they do

47:07.780 --> 47:09.120
everything from, you

47:09.120 --> 47:10.100
know, connecting to IRC

47:10.100 --> 47:12.520
to making sure a, you

47:12.520 --> 47:13.380
know, a phone number is

47:13.380 --> 47:14.520
theoretically valid for the

47:14.520 --> 47:14.920
Ukraine.

47:15.300 --> 47:16.700
They have modules that do

47:16.700 --> 47:17.140
everything.

47:17.820 --> 47:18.720
Stuff that automates

47:18.720 --> 47:20.080
Telnet clients, stuff that

47:20.080 --> 47:21.220
automates Telnet servers.

47:21.760 --> 47:23.700
You can open up raw TCP

47:23.700 --> 47:24.300
sockets.

47:24.520 --> 47:25.740
It's just, it's simply

47:25.740 --> 47:26.720
amazing all the crap that

47:26.720 --> 47:27.360
people do with this

47:27.360 --> 47:28.020
programming language.

47:28.180 --> 47:29.800
It's kind of scary.

47:30.980 --> 47:32.180
But, you know, what the

47:32.180 --> 47:33.700
cool thing is about it is

47:33.700 --> 47:36.600
the way to access the

47:36.600 --> 47:37.400
archive, you can do it

47:37.400 --> 47:37.980
through the web and

47:37.980 --> 47:38.540
there's like, you know,

47:38.580 --> 47:39.600
15 bazillion ways to

47:39.600 --> 47:40.480
actually access it.

47:40.820 --> 47:41.840
But they have included

47:41.840 --> 47:43.120
modules in the Perl

47:43.120 --> 47:44.340
distribution itself that

47:44.340 --> 47:46.080
you can run through the

47:46.080 --> 47:46.860
Perl client on the

47:46.860 --> 47:47.880
command line that will

47:47.880 --> 47:48.860
allow you to interface

47:48.860 --> 47:50.240
with the database,

47:50.600 --> 47:51.600
download all your crap,

47:51.800 --> 47:52.700
you know, interface with

47:52.700 --> 47:52.880
it.

47:55.100 --> 47:56.160
I mean, it's all just

47:56.160 --> 47:56.960
there in the basic Perl

47:56.960 --> 47:57.800
distribution, so all you

47:57.800 --> 47:58.660
need to do is, you know,

47:58.820 --> 47:59.700
pull it up and you're all

47:59.700 --> 47:59.940
set.

48:00.620 --> 48:01.420
Once you do that, you

48:01.420 --> 48:02.460
can have full access to

48:02.460 --> 48:03.480
all the archives and you

48:03.480 --> 48:05.220
say install net component

48:05.220 --> 48:07.080
IRC, or I'm sorry, POE

48:07.080 --> 48:08.880
component IRC, and it

48:08.880 --> 48:09.600
automatically pulls it

48:09.600 --> 48:10.640
down, it tests it for you,

48:10.680 --> 48:12.040
it installs it, and you're

48:12.040 --> 48:12.560
all set to go.

48:12.620 --> 48:13.300
You can use it in your

48:13.300 --> 48:13.580
system.

48:16.380 --> 48:17.980
It's, besides like a quick

48:17.980 --> 48:19.100
configuration that you have

48:19.100 --> 48:19.900
to do the first time you do

48:19.900 --> 48:21.560
it, it's instantaneous.

48:21.920 --> 48:22.440
It's amazing.

48:23.080 --> 48:25.380
This is the best feature of

48:25.380 --> 48:26.040
Perl, in my opinion.

48:26.140 --> 48:26.960
All the modules and

48:26.960 --> 48:27.960
everyone can be treating to

48:27.960 --> 48:29.260
it and just them making it

48:29.260 --> 48:30.100
so easy to get to.

48:30.100 --> 48:32.860
I mean, there's tons of C++

48:32.860 --> 48:33.840
and there's tons of C

48:33.840 --> 48:34.700
libraries out there that

48:34.700 --> 48:35.620
people access it, but

48:35.620 --> 48:36.520
they're just all distributed

48:36.520 --> 48:37.400
and you have to, like, you

48:37.400 --> 48:38.980
know, pour through Google

48:38.980 --> 48:42.640
to find them and it's really

48:42.640 --> 48:42.980
difficult.

48:43.160 --> 48:43.560
It's not fun.

48:43.780 --> 48:44.520
No, it's not fun.

48:44.680 --> 48:46.120
And Perl has just, you know,

48:46.120 --> 48:47.600
set it up and made it

48:47.600 --> 48:48.700
incredibly easy to access.

48:51.100 --> 48:51.780
It's cool.

48:51.780 --> 48:54.620
And really, there's a

48:54.620 --> 48:55.520
million things you can do

48:55.520 --> 48:55.940
with Perl.

48:57.260 --> 48:59.500
Perl has ability to, you

48:59.500 --> 49:00.540
know, if you want to create

49:00.540 --> 49:01.660
a GUI tool, if you want to

49:01.660 --> 49:02.960
create a GUI for your

49:02.960 --> 49:04.300
program, like graphical user

49:04.300 --> 49:06.440
interface, Perl can do that.

49:06.560 --> 49:08.540
They interface with, I

49:08.540 --> 49:09.700
believe the interface is with

49:09.700 --> 49:10.280
GTK.

49:10.420 --> 49:12.660
I believe there's a QT binding

49:12.660 --> 49:13.800
for it that you can, you

49:13.800 --> 49:15.100
know, in your Perl program,

49:15.220 --> 49:16.040
you can control it and

49:16.040 --> 49:17.040
actually have a window pop

49:17.040 --> 49:18.800
up on your, whether you'll be

49:18.800 --> 49:20.320
KDE or GNOME or whatever

49:20.320 --> 49:21.140
your X windowing

49:21.140 --> 49:21.780
environment is.

49:22.240 --> 49:23.140
Do they have stuff for

49:23.140 --> 49:25.240
just raw X, you know, or

49:25.240 --> 49:25.800
like motif?

49:27.180 --> 49:28.240
You know, I believe there

49:28.240 --> 49:29.660
is some raw X stuff and I

49:29.660 --> 49:31.020
think there's open, I know

49:31.020 --> 49:32.100
there's OpenGL stuff too.

49:32.160 --> 49:33.460
I've just never really

49:33.460 --> 49:34.280
gotten it to work.

49:34.620 --> 49:35.560
I've never actually heard

49:35.560 --> 49:36.140
of the OpenGL.

49:36.420 --> 49:37.340
That's something I have to

49:37.340 --> 49:39.000
check it in.

49:40.120 --> 49:41.500
You can do anything with

49:41.500 --> 49:41.640
it.

49:41.840 --> 49:42.460
You know, Perl can grab

49:42.460 --> 49:43.960
data off the web, you

49:43.960 --> 49:45.240
know, pop it off the, you

49:45.240 --> 49:46.040
know, pop it out via the

49:46.040 --> 49:46.960
phone with asterisk, which

49:46.960 --> 49:48.820
is the module I've just

49:48.820 --> 49:50.000
recently, I wouldn't say

49:50.000 --> 49:50.520
just recently.

49:51.000 --> 49:52.380
I settled upon right

49:52.380 --> 49:52.940
after I started

49:52.940 --> 49:53.940
programming with asterisk

49:53.940 --> 49:56.300
and it is just, it used

49:56.300 --> 49:57.200
to be cool, you used to

49:57.200 --> 49:58.100
be able to take stuff off

49:58.100 --> 49:59.060
the web and put it into a

49:59.060 --> 49:59.740
format you want.

49:59.840 --> 50:00.640
Now you can, you know,

50:00.700 --> 50:01.600
take stuff off of the web

50:01.600 --> 50:02.520
and have it read it back to

50:02.520 --> 50:03.160
you over the phone.

50:03.320 --> 50:05.080
It's amazing.

50:05.200 --> 50:05.720
It's the shizzle.

50:06.900 --> 50:08.400
Have you done fun things

50:08.400 --> 50:08.780
with Perl?

50:10.280 --> 50:12.640
Actually, my title in the

50:12.640 --> 50:13.480
forums, the data

50:13.480 --> 50:14.500
pillager, I got that

50:14.500 --> 50:15.600
pretty much because Perl

50:15.600 --> 50:16.900
enabled me to write a

50:16.900 --> 50:17.680
bunch of scripts and

50:17.680 --> 50:20.880
just pull mountains and

50:20.880 --> 50:21.600
mountains and mountains

50:21.600 --> 50:22.780
data off the internet

50:22.780 --> 50:24.380
and stuff them in

50:24.380 --> 50:25.960
databases and then using

50:25.960 --> 50:27.040
PHP, I can make a user

50:27.040 --> 50:27.740
interface to it.

50:27.820 --> 50:28.560
And essentially, that's

50:28.560 --> 50:29.140
really how Bell's

50:29.140 --> 50:29.660
Mine started.

50:30.020 --> 50:33.520
So I've done a lot of

50:33.520 --> 50:34.600
data pillaging with Perl

50:34.600 --> 50:36.180
and I'm totally in love

50:36.180 --> 50:36.700
with it for that.

50:36.960 --> 50:38.460
Yeah, it's simply amazing.

50:38.580 --> 50:39.220
Where did you pull your

50:39.220 --> 50:40.460
data from, if I may ask?

50:40.640 --> 50:42.080
Or do you want to admit to

50:42.080 --> 50:42.200
it?

50:42.200 --> 50:42.680
How about that?

50:42.680 --> 50:44.320
Oh, no, no, no, no, no.

50:44.460 --> 50:46.400
I fully admit to it.

50:46.540 --> 50:48.700
I pulled data from NAMPA,

50:48.900 --> 50:50.720
the North American Numbering

50:50.720 --> 50:51.520
Client Association.

50:52.240 --> 50:54.800
I pulled data from CNAC,

50:54.940 --> 50:56.880
the Canadian numbering

50:56.880 --> 50:58.780
something.

50:59.880 --> 51:01.300
The damn connects with

51:01.300 --> 51:01.640
phones.

51:01.760 --> 51:02.480
I pulled it from those

51:02.480 --> 51:02.760
guys.

51:05.280 --> 51:08.200
And, well, DSLreports.com

51:08.200 --> 51:09.480
was particularly interesting

51:09.480 --> 51:10.720
because every few hours,

51:10.720 --> 51:12.260
they would block whatever

51:12.260 --> 51:13.740
I was doing.

51:14.100 --> 51:14.800
But they were blocking

51:14.800 --> 51:15.640
by user agents.

51:15.780 --> 51:16.760
So I just told Perl,

51:16.840 --> 51:18.300
hey, change your user

51:18.300 --> 51:19.380
agent to something else.

51:20.780 --> 51:21.700
And the funny story about

51:21.700 --> 51:23.140
that is that I initially

51:23.140 --> 51:24.400
sent my user agent to

51:24.400 --> 51:26.280
Bob Dole and they

51:26.280 --> 51:27.640
blocked the user agent

51:27.640 --> 51:28.620
of Bob Dole.

51:28.960 --> 51:30.200
So I changed the user

51:30.200 --> 51:31.300
agent from Bob Dole to

51:31.300 --> 51:31.980
Bob Dole 2.

51:32.420 --> 51:33.120
And then they blocked

51:33.120 --> 51:33.440
that.

51:33.540 --> 51:34.260
And then I changed it to

51:34.260 --> 51:34.940
Bob Dole 3.

51:35.060 --> 51:36.100
And this went on about

51:36.100 --> 51:37.260
15 or 20 times.

51:37.760 --> 51:38.720
I guess they didn't kind

51:38.720 --> 51:39.720
of pick up on the hint

51:39.720 --> 51:41.100
like maybe he's going

51:41.100 --> 51:42.160
to up it by one and

51:42.160 --> 51:43.180
call Bob Dole again.

51:43.740 --> 51:45.260
But, you know, in

51:45.260 --> 51:46.040
three or four days,

51:46.180 --> 51:48.900
I had all of DSLreports.com.

51:49.120 --> 51:50.600
I'm sure it was

51:50.600 --> 51:50.960
automated.

51:51.180 --> 51:51.860
I'm actually probably

51:51.860 --> 51:52.520
someone like poured

51:52.520 --> 51:53.140
through the logs

51:53.140 --> 51:54.020
afterwards and someone

51:54.020 --> 51:54.840
said, what the hell is

51:54.840 --> 51:55.380
this guy doing?

51:56.060 --> 51:56.780
Of course, by then you

51:56.780 --> 51:58.560
were like a thief in

51:58.560 --> 51:59.700
the night and going

51:59.700 --> 52:00.000
away.

52:00.180 --> 52:01.200
So basically what you're

52:01.200 --> 52:02.140
saying is you pulled

52:02.140 --> 52:03.240
data down from three

52:03.240 --> 52:04.300
separate data sources,

52:04.700 --> 52:06.340
all via Perl, and

52:06.340 --> 52:07.280
combined it into one

52:07.280 --> 52:07.960
giant database.

52:07.960 --> 52:12.240
And it does it all

52:12.240 --> 52:13.000
automatically, too.

52:13.140 --> 52:14.060
Actually, the Nampa

52:14.060 --> 52:15.080
Daily Updates pulls

52:15.080 --> 52:17.900
the data from Nampa.

52:18.580 --> 52:19.860
They have an Excel

52:19.860 --> 52:20.800
spreadsheet that they

52:20.800 --> 52:21.660
release every day.

52:21.820 --> 52:22.680
And Perl takes the

52:22.680 --> 52:23.860
Excel spreadsheet,

52:24.420 --> 52:25.440
extracts all the data

52:25.440 --> 52:26.120
out of it, figures

52:26.120 --> 52:27.200
out which ones are

52:27.200 --> 52:28.680
table headers and

52:28.680 --> 52:29.400
which ones are actual

52:29.400 --> 52:30.420
cells of data, and

52:30.420 --> 52:31.900
then turns it into

52:31.900 --> 52:32.620
an insert statement

52:32.620 --> 52:33.840
and inserts it into

52:33.840 --> 52:35.840
the database.

52:35.840 --> 52:37.400
It also diffs it from

52:37.400 --> 52:37.840
the previous.

52:38.040 --> 52:38.960
It'll check to see if

52:38.960 --> 52:39.860
the record has changed

52:39.860 --> 52:40.240
or not.

52:40.320 --> 52:40.920
And if it has, it

52:40.920 --> 52:43.400
makes a note in the

52:43.400 --> 52:43.740
calendar.

52:44.120 --> 52:44.800
So it says, this

52:44.800 --> 52:45.720
record changed on this

52:45.720 --> 52:45.960
date.

52:46.800 --> 52:48.500
So it does a lot of

52:48.500 --> 52:48.820
stuff.

52:49.660 --> 52:52.660
So the file that you

52:52.660 --> 52:53.300
pulled down is an

52:53.300 --> 52:53.860
Excel file?

52:54.720 --> 52:55.200
Oh, yeah.

52:55.320 --> 52:55.720
It's an Excel

52:55.720 --> 52:56.120
spreadsheet.

52:56.280 --> 52:57.360
And can Perl read

52:57.360 --> 52:57.540
that?

52:57.540 --> 53:00.320
I just use a program

53:00.320 --> 53:02.560
called Excel HTML, and

53:02.560 --> 53:03.340
I take that and I

53:03.340 --> 53:04.620
type it into Perl and

53:04.620 --> 53:06.180
extract the data from

53:06.180 --> 53:06.380
there.

53:06.780 --> 53:07.980
See, that's just, I

53:07.980 --> 53:09.380
mean, that's just

53:09.380 --> 53:10.160
Perl excels.

53:10.340 --> 53:11.860
It's just, it's amazing

53:11.860 --> 53:12.520
all the crap that it

53:12.520 --> 53:12.820
can do.

53:13.220 --> 53:13.780
It really is.

53:13.780 --> 53:14.380
Yeah, I think there

53:14.380 --> 53:15.460
actually is a module

53:15.460 --> 53:16.340
for Perl that does

53:16.340 --> 53:17.560
read Excel files.

53:17.840 --> 53:19.180
But at the time when

53:19.180 --> 53:19.960
I was doing a

53:19.960 --> 53:20.680
development, I just

53:20.680 --> 53:21.380
didn't have time to

53:21.380 --> 53:22.040
play with it.

53:22.380 --> 53:22.740
Yeah.

53:24.020 --> 53:25.900
And, you know, Perl

53:25.900 --> 53:27.100
doesn't do everything,

53:27.260 --> 53:27.940
I will admit.

53:29.140 --> 53:30.040
Wait a second.

53:30.500 --> 53:30.660
Hmm?

53:31.180 --> 53:32.180
Are you sure it

53:32.180 --> 53:32.780
doesn't do everything?

53:33.340 --> 53:34.120
Okay, how about

53:34.120 --> 53:34.260
this?

53:34.280 --> 53:34.640
It doesn't do

53:34.640 --> 53:35.440
everything easily.

53:36.440 --> 53:37.580
Okay, that's fair.

53:38.600 --> 53:39.260
Actually, that

53:39.260 --> 53:39.900
actually reminds me

53:39.900 --> 53:40.460
of one of my slides

53:40.460 --> 53:41.080
from my asterisk

53:41.080 --> 53:43.760
presentation when I

53:43.760 --> 53:44.340
was talking about

53:44.340 --> 53:45.160
the module that

53:45.160 --> 53:46.340
talks to asterisk

53:46.340 --> 53:47.180
with Perl.

53:47.960 --> 53:48.800
One of the lines

53:48.800 --> 53:49.260
was, you know,

53:49.480 --> 53:50.420
easily integratable

53:50.420 --> 53:51.380
with Perl, which

53:51.380 --> 53:52.560
easily integrates

53:52.560 --> 53:52.980
with everything.

53:53.080 --> 53:53.580
And I actually had

53:53.580 --> 53:54.400
the second easily

53:54.400 --> 53:55.700
crossed out,

53:55.700 --> 53:58.400
because, you know,

53:58.440 --> 53:59.620
sometimes Perl

53:59.620 --> 54:00.640
can be interesting.

54:00.760 --> 54:01.420
But basically, if

54:01.420 --> 54:03.300
you toss enough

54:03.300 --> 54:03.900
time and effort

54:03.900 --> 54:05.980
to it, you'll

54:05.980 --> 54:06.420
get it done.

54:06.720 --> 54:07.640
You really will.

54:07.720 --> 54:08.320
It just, it'll

54:08.320 --> 54:09.320
sit there and,

54:09.580 --> 54:10.080
you know, it'll

54:10.080 --> 54:10.800
just function away.

54:10.900 --> 54:11.480
I mean, it may

54:11.480 --> 54:12.060
not look pretty.

54:12.460 --> 54:13.080
One of the major

54:13.080 --> 54:13.720
complaints with,

54:13.800 --> 54:14.440
you know, more of

54:14.440 --> 54:15.040
the classical

54:15.040 --> 54:16.540
programmers, they

54:16.540 --> 54:17.200
complain that, you

54:17.200 --> 54:17.800
know, Perl's not

54:17.800 --> 54:18.920
pretty enough and,

54:19.580 --> 54:21.340
you know, it's not

54:21.340 --> 54:21.800
elegant.

54:23.060 --> 54:24.220
But basically, you

54:24.220 --> 54:24.940
know, Larry Wall,

54:24.940 --> 54:25.560
when he designed

54:25.560 --> 54:27.180
this, I think I

54:27.180 --> 54:27.700
talked about him,

54:27.740 --> 54:28.020
didn't I?

54:28.740 --> 54:29.040
Yes.

54:29.200 --> 54:29.760
Yes, I did

54:29.760 --> 54:30.160
mention him.

54:30.160 --> 54:30.700
Larry Wall, the

54:30.700 --> 54:31.300
creator of Perl.

54:31.440 --> 54:32.680
He's a god, in

54:32.680 --> 54:33.040
my opinion.

54:35.000 --> 54:35.980
He just designed

54:35.980 --> 54:36.100
it.

54:36.180 --> 54:37.180
He basically, the

54:37.180 --> 54:37.760
way he designed

54:37.760 --> 54:38.320
it was, he was

54:38.320 --> 54:38.800
at his government

54:38.800 --> 54:40.000
job, I believe it

54:40.000 --> 54:40.600
was government or

54:40.600 --> 54:40.800
something.

54:40.860 --> 54:41.280
He was at his

54:41.280 --> 54:42.200
job, and his

54:42.200 --> 54:42.880
boss came to him

54:42.880 --> 54:43.540
and said, hey, we

54:43.540 --> 54:44.480
need something that

54:44.480 --> 54:46.060
will do this.

54:46.820 --> 54:47.820
So he said, well,

54:47.920 --> 54:48.620
geez, all these

54:48.620 --> 54:49.480
tools, like, you

54:49.480 --> 54:49.820
know, Krep

54:49.820 --> 54:51.520
Auken said, will

54:51.520 --> 54:52.100
kind of work

54:52.100 --> 54:52.500
together.

54:52.500 --> 54:54.100
But I think it

54:54.100 --> 54:54.560
would be easier if

54:54.560 --> 54:55.240
I just designed my

54:55.240 --> 54:55.720
own programming

54:55.720 --> 54:56.400
language, at which

54:56.400 --> 54:57.040
point Perl was

54:57.040 --> 54:57.360
born.

54:59.040 --> 55:00.060
And, you know, it

55:00.060 --> 55:00.960
really is.

55:01.080 --> 55:01.600
You know, Perl can

55:01.600 --> 55:02.140
be a giant

55:02.140 --> 55:03.020
kludget sometimes,

55:03.280 --> 55:05.180
and I've seen

55:05.180 --> 55:05.760
more than enough

55:05.760 --> 55:07.340
code that you

55:07.340 --> 55:07.920
write, and then

55:07.920 --> 55:08.420
you come back

55:08.420 --> 55:09.020
about two months

55:09.020 --> 55:09.500
later, and you

55:09.500 --> 55:09.920
look at your

55:09.920 --> 55:10.680
source code, and

55:10.680 --> 55:11.260
you say, what

55:11.260 --> 55:11.900
was I thinking?

55:12.560 --> 55:14.280
That's, I don't

55:14.280 --> 55:14.960
understand that.

55:15.320 --> 55:15.920
And you have to,

55:15.920 --> 55:16.580
like, sit there and

55:16.580 --> 55:17.300
relearn your code,

55:17.380 --> 55:18.060
because unless you

55:18.060 --> 55:18.980
properly document it,

55:18.980 --> 55:19.460
and I guess you

55:19.460 --> 55:19.900
could technically

55:19.900 --> 55:22.000
say this for, you

55:22.000 --> 55:22.780
know, all types of

55:22.780 --> 55:23.620
code, if you don't

55:23.620 --> 55:24.440
properly document it,

55:24.460 --> 55:24.740
you'll never

55:24.740 --> 55:25.280
understand it

55:25.280 --> 55:25.700
afterwards.

55:26.980 --> 55:27.780
Can you attest to

55:27.780 --> 55:27.960
that?

55:28.820 --> 55:29.540
Oh, yeah, definitely.

55:29.660 --> 55:30.660
But I think Perl is a

55:30.660 --> 55:31.080
little different.

55:31.240 --> 55:32.000
I think Perl gives

55:32.000 --> 55:32.900
you the freedom to be

55:32.900 --> 55:34.800
a little more clever,

55:34.940 --> 55:35.640
and I'm putting clever

55:35.640 --> 55:36.760
in double quotes there,

55:37.160 --> 55:38.280
because you may have a

55:38.280 --> 55:38.960
great idea and say,

55:39.000 --> 55:39.780
oh, I can do this a

55:39.780 --> 55:40.540
little bit simpler and

55:40.540 --> 55:41.240
save a couple of lines

55:41.240 --> 55:42.260
of code by doing this.

55:42.700 --> 55:44.160
But when you do it and

55:44.160 --> 55:45.140
then forget to document

55:45.140 --> 55:48.160
it, I think Perl can

55:48.160 --> 55:49.400
trip you up a little

55:49.400 --> 55:49.980
bit more than any

55:49.980 --> 55:50.480
other language.

55:50.920 --> 55:51.800
So, yes, you will

55:51.800 --> 55:52.280
start to cry.

55:52.380 --> 55:52.880
I've done it before.

55:53.560 --> 55:54.900
Yeah, Perl has an

55:54.900 --> 55:56.380
uncanny ability to come

55:56.380 --> 55:57.820
back after you've left

55:57.820 --> 55:58.400
it for a couple of

55:58.400 --> 55:59.340
months, and you come

55:59.340 --> 55:59.920
back to your script

55:59.920 --> 56:00.460
to edit it, and it

56:00.460 --> 56:01.400
looks completely like a

56:01.400 --> 56:01.920
line noise.

56:02.020 --> 56:02.760
And what line noise

56:02.760 --> 56:03.380
is, for those of you

56:03.380 --> 56:05.440
who don't know, back in

56:05.440 --> 56:06.400
the days of modems and

56:06.400 --> 56:07.160
everything, if your

56:07.160 --> 56:09.000
line was staticky,

56:10.160 --> 56:11.060
you'd start seeing,

56:11.120 --> 56:11.780
like, you know, random

56:11.780 --> 56:12.680
bits of data showing

56:12.680 --> 56:13.560
up, like, you know,

56:15.080 --> 56:16.400
like little pounds and

56:16.400 --> 56:17.460
asterisks and,

56:18.160 --> 56:19.160
just random ASCII

56:19.160 --> 56:19.980
characters show up,

56:20.040 --> 56:20.660
which was, you know,

56:20.700 --> 56:21.360
your computer was

56:21.360 --> 56:22.080
trying to interpret

56:22.080 --> 56:23.340
this crackling on the

56:23.340 --> 56:24.260
line, when in reality

56:24.260 --> 56:25.040
it was just, you know,

56:25.420 --> 56:26.560
the wind blowing your

56:26.560 --> 56:27.960
line about from

56:27.960 --> 56:28.900
between you and the

56:28.900 --> 56:30.100
central office.

56:32.240 --> 56:33.320
Yeah, I just thought

56:33.320 --> 56:33.720
about that.

56:33.780 --> 56:34.340
I was like, wow, I

56:34.340 --> 56:34.860
haven't thought about

56:34.860 --> 56:36.200
line noise in a long

56:36.200 --> 56:36.660
time.

56:36.780 --> 56:37.200
Yeah, isn't that

56:37.200 --> 56:37.520
amazing?

56:37.700 --> 56:38.600
Like, everyone has

56:38.600 --> 56:39.520
DSL now, and you

56:39.520 --> 56:40.240
have to, well, I

56:40.240 --> 56:40.780
wouldn't say everyone

56:40.780 --> 56:41.640
has DSL now.

56:42.240 --> 56:43.180
All the people that we

56:43.180 --> 56:44.100
know have DSL.

56:44.100 --> 56:46.120
I know, but the

56:46.120 --> 56:46.820
thing about it is,

56:46.880 --> 56:47.420
even if you don't

56:47.420 --> 56:48.160
have DSL, if you're

56:48.160 --> 56:49.040
not calling a dial-up

56:49.040 --> 56:49.740
bulletin board, you

56:49.740 --> 56:50.340
don't know what line

56:50.340 --> 56:51.120
noise is, because you

56:51.120 --> 56:51.620
don't see it.

56:52.000 --> 56:53.060
When you have a PPP or

56:53.060 --> 56:53.960
slip connection, or

56:53.960 --> 56:55.000
hopefully nobody still

56:55.000 --> 56:55.920
has a slip connection,

56:56.320 --> 56:56.920
but when you have a

56:56.920 --> 56:58.060
PPP connection to your

56:58.060 --> 56:58.940
provider, you don't see

56:58.940 --> 56:59.420
line noise.

56:59.820 --> 57:00.800
I believe my

57:00.800 --> 57:02.120
university, I don't

57:02.120 --> 57:02.640
think they have it

57:02.640 --> 57:03.980
anymore, but they've

57:03.980 --> 57:06.780
recently terminated all

57:06.780 --> 57:07.620
their slip stuff,

57:07.740 --> 57:08.700
because what they used

57:08.700 --> 57:09.360
to do is they'd have

57:09.360 --> 57:10.360
the modem, and over,

57:10.360 --> 57:12.860
they'd have this giant

57:12.860 --> 57:13.880
modem rack, and they'd

57:13.880 --> 57:14.820
be talking a slip to

57:14.820 --> 57:15.720
the terminal servers.

57:16.980 --> 57:17.120
Oh.

57:17.300 --> 57:18.260
Yeah, that was pretty

57:18.260 --> 57:19.460
scary when I got the

57:19.460 --> 57:20.060
email saying, oh,

57:20.120 --> 57:21.460
yeah, we're going to

57:21.460 --> 57:23.060
retire all of these

57:23.060 --> 57:23.380
things.

57:23.780 --> 57:24.840
I was like, oh, God,

57:24.900 --> 57:25.680
you still have that?

57:25.740 --> 57:26.480
This is 2004.

57:27.540 --> 57:28.340
Yeah, exactly.

57:29.360 --> 57:30.940
And also, now that I

57:30.940 --> 57:31.760
think about it, even if

57:31.760 --> 57:33.040
you have, even if you're

57:33.040 --> 57:33.880
calling up that at

57:33.880 --> 57:34.680
bulletin boards, if you

57:34.680 --> 57:37.480
have, like, MMP5 or any

57:37.480 --> 57:38.660
of those types of error

57:38.660 --> 57:39.740
correction, you're

57:39.740 --> 57:40.200
probably not going to

57:40.200 --> 57:40.600
see it either.

57:40.800 --> 57:42.240
So, if you've seen

57:42.240 --> 57:43.480
line noise, you are

57:43.480 --> 57:44.660
old school, officially.

57:45.740 --> 57:48.900
Yeah, you see it for a

57:48.900 --> 57:49.340
little extent.

57:49.460 --> 57:50.380
I mean, depends on

57:50.380 --> 57:51.740
what the, we're kind

57:51.740 --> 57:52.400
of drifting here, but

57:52.400 --> 57:53.040
let's go take a strip

57:53.040 --> 57:53.660
down memory lane,

57:53.780 --> 57:55.460
because, hey, why

57:55.460 --> 57:55.700
not?

57:56.040 --> 57:56.880
We're running low on

57:56.880 --> 57:57.200
material.

57:58.680 --> 57:59.580
No, we have plenty

57:59.580 --> 57:59.960
of material.

58:00.120 --> 58:00.240
Yeah.

58:03.040 --> 58:04.080
I mean, if you had a

58:04.080 --> 58:04.940
lot of stuff that would

58:04.940 --> 58:06.680
update stuff, like

58:06.680 --> 58:07.900
ANSI feeds and, you

58:07.900 --> 58:08.760
know, trying to get

58:08.760 --> 58:09.520
complicated displays,

58:09.520 --> 58:10.060
you'll start running

58:10.060 --> 58:11.340
into that as, you

58:11.340 --> 58:12.560
know, something along

58:12.560 --> 58:13.440
the line told it to

58:13.440 --> 58:14.300
update, you know, the

58:14.300 --> 58:15.840
cursor at 8025 and

58:15.840 --> 58:16.600
accidentally interpret

58:16.600 --> 58:17.880
that as 8023, so you

58:17.880 --> 58:18.660
got this little bit of

58:18.660 --> 58:19.420
data down there that

58:19.420 --> 58:20.080
doesn't look correctly.

58:20.080 --> 58:22.900
I remember back in the day

58:22.900 --> 58:24.400
playing multiplayer Star

58:24.400 --> 58:25.080
Trek, which was

58:25.080 --> 58:26.340
essentially this giant

58:26.340 --> 58:29.280
ASCII board, and they

58:29.280 --> 58:30.460
had a key that would

58:30.460 --> 58:31.500
say, redraw screen, and

58:31.500 --> 58:32.140
I'd hit it, like, you

58:32.140 --> 58:33.340
know, about once every

58:33.340 --> 58:34.780
20 seconds, because my

58:34.780 --> 58:35.920
screen would just start

58:35.920 --> 58:36.680
looking at crap.

58:37.940 --> 58:39.740
I'd be firing on a

58:39.740 --> 58:41.020
Romulan warbird that was

58:41.020 --> 58:42.080
at a certain coordinate,

58:42.200 --> 58:43.220
and it was in reality

58:43.220 --> 58:44.960
just, you know, some

58:44.960 --> 58:46.220
badly updated piece of

58:46.220 --> 58:46.500
data.

58:46.500 --> 58:48.920
Yeah, I remember

58:48.920 --> 58:49.120
that.

58:49.200 --> 58:50.720
Not in that game, but

58:50.720 --> 58:51.420
there was a game called

58:51.420 --> 58:52.360
the, I think it was

58:52.360 --> 58:55.000
called The Pit, and you

58:55.000 --> 58:56.220
would fight other

58:56.220 --> 58:58.660
people, other computer

58:58.660 --> 59:00.120
players, or if you were on

59:00.120 --> 59:01.660
a multi-node BBS, oh my

59:01.660 --> 59:02.520
God, that had, like, two

59:02.520 --> 59:03.320
or three people calling

59:03.320 --> 59:04.560
in, you could play in

59:04.560 --> 59:05.680
real time against the

59:05.680 --> 59:06.180
other players.

59:06.180 --> 59:09.200
And I remember on that,

59:09.280 --> 59:09.780
you would get a little

59:09.780 --> 59:10.580
bit of blindness, and

59:10.580 --> 59:10.840
you would throw the

59:10.840 --> 59:11.560
whole fight off, because

59:11.560 --> 59:12.040
you wouldn't know where

59:12.040 --> 59:12.760
the other person was.

59:12.840 --> 59:13.360
So you'd sit there and

59:13.360 --> 59:14.620
hit Control-L, Control-L,

59:14.720 --> 59:15.800
Control-L to update the

59:15.800 --> 59:17.120
screen, and hope that it

59:17.120 --> 59:17.520
would work.

59:17.700 --> 59:18.820
That was the same key for

59:18.820 --> 59:19.680
Star Trek.

59:22.060 --> 59:22.420
Memories!

59:23.780 --> 59:25.540
Oh, man, old school.

59:25.880 --> 59:27.040
I'm so glad that somebody

59:27.040 --> 59:27.860
else remembers some of

59:27.860 --> 59:28.300
this stuff, because

59:28.300 --> 59:29.240
sometimes I mention it to

59:29.240 --> 59:29.860
people, and they just

59:29.860 --> 59:31.500
look at me like I'm a

59:31.500 --> 59:32.200
thousand years old.

59:32.340 --> 59:33.200
Oh, yeah, no, it's

59:33.200 --> 59:33.580
depressing.

59:33.960 --> 59:34.760
We're not trying to

59:34.760 --> 59:35.460
knock any of you

59:35.460 --> 59:37.260
younger crowd out there,

59:37.360 --> 59:39.160
but you make these

59:39.160 --> 59:40.880
jokes about, you know,

59:41.100 --> 59:41.720
people are talking

59:41.720 --> 59:42.560
about Telnet, what the

59:42.560 --> 59:43.020
hell is that?

59:43.120 --> 59:43.480
And you're like,

59:43.580 --> 59:43.860
what?

59:44.040 --> 59:44.440
What do you mean?

59:44.440 --> 59:44.820
You never used

59:44.820 --> 59:45.400
Telnet before?

59:46.160 --> 59:46.820
Yeah, seriously.

59:47.020 --> 59:47.820
It's kind of sad.

59:48.080 --> 59:49.480
I mean, even now,

59:49.540 --> 59:50.140
because everyone uses

59:50.140 --> 59:51.680
SSH, people don't use

59:51.680 --> 59:52.260
Telnet anymore.

59:52.740 --> 59:53.620
People shouldn't use

59:53.620 --> 59:54.140
Telnet anymore.

59:54.280 --> 59:55.040
People probably still

59:55.040 --> 59:55.560
use it because they

59:55.560 --> 59:56.180
don't know any better.

59:57.300 --> 59:57.880
Oh, yeah, I know

59:57.880 --> 59:58.660
some people that do.

59:59.000 --> 01:00:00.220
Oh, yeah, I remember,

01:00:00.480 --> 01:00:01.800
God, SSH, what the

01:00:01.800 --> 01:00:02.180
hell is that?

01:00:02.240 --> 01:00:03.060
No one ever had that.

01:00:03.060 --> 01:00:03.720
I remember using

01:00:03.720 --> 01:00:05.180
Telnet, you know,

01:00:05.740 --> 01:00:07.060
TelnetSurfers.org,

01:00:07.180 --> 01:00:08.320
slash, no, sorry,

01:00:08.440 --> 01:00:09.760
not TelnetSurfers.org,

01:00:09.860 --> 01:00:11.280
space 4242.

01:00:12.120 --> 01:00:12.820
Connect you over to

01:00:12.820 --> 01:00:13.920
port 4242, and I

01:00:13.920 --> 01:00:14.540
used to go on my

01:00:14.540 --> 01:00:17.080
multi-user dimension.

01:00:17.280 --> 01:00:17.640
Actually, it was at

01:00:17.640 --> 01:00:18.500
org or dot org,

01:00:18.620 --> 01:00:19.400
org.uk.

01:00:19.940 --> 01:00:20.780
I completely forget.

01:00:20.980 --> 01:00:21.540
Back in the, oh,

01:00:21.600 --> 01:00:21.840
God.

01:00:22.180 --> 01:00:22.860
What are my accounts

01:00:22.860 --> 01:00:23.220
still there?

01:00:23.280 --> 01:00:23.760
That'd be a hoot.

01:00:24.700 --> 01:00:25.500
Oh, my God.

01:00:26.040 --> 01:00:26.980
Yeah, I got on the

01:00:26.980 --> 01:00:28.180
internet back in 1995,

01:00:28.440 --> 01:00:28.940
for those of you who

01:00:28.940 --> 01:00:29.340
don't know.

01:00:29.920 --> 01:00:31.640
So, I'm a bit of an

01:00:31.640 --> 01:00:32.080
old-timer.

01:00:32.180 --> 01:00:33.040
It was very scary when

01:00:33.040 --> 01:00:33.740
I realized that I'd

01:00:33.740 --> 01:00:34.200
been on the internet

01:00:34.200 --> 01:00:34.900
for 10 years.

01:00:36.200 --> 01:00:37.000
Wow, you know, I

01:00:37.000 --> 01:00:37.600
hadn't really thought

01:00:37.600 --> 01:00:37.980
about it.

01:00:38.860 --> 01:00:41.020
I don't remember what

01:00:41.020 --> 01:00:42.140
year it was, but I was

01:00:42.140 --> 01:00:43.480
still in high school, so

01:00:43.480 --> 01:00:46.100
it was definitely either

01:00:46.100 --> 01:00:49.440
92 or 93, I suppose.

01:00:49.560 --> 01:00:50.440
And that was a big

01:00:50.440 --> 01:00:50.840
event.

01:00:50.980 --> 01:00:51.540
Like, nowadays,

01:00:52.220 --> 01:00:52.860
everybody's got

01:00:52.860 --> 01:00:54.140
internet access, and

01:00:54.140 --> 01:00:55.400
you know, it's no big

01:00:55.400 --> 01:00:55.740
deal.

01:00:56.140 --> 01:00:56.880
When I had internet

01:00:56.880 --> 01:00:58.000
access, at least for me,

01:00:58.040 --> 01:00:58.940
because I was a

01:00:58.940 --> 01:00:59.740
hardcore geek, and

01:00:59.740 --> 01:01:01.660
still am, I was like,

01:01:01.760 --> 01:01:03.260
wow, I am on the

01:01:03.260 --> 01:01:03.600
internet.

01:01:03.780 --> 01:01:05.120
People don't understand

01:01:05.120 --> 01:01:06.360
how cool this is.

01:01:06.420 --> 01:01:07.180
People didn't know what

01:01:07.180 --> 01:01:07.800
the hell the internet

01:01:07.800 --> 01:01:08.280
was back then.

01:01:08.280 --> 01:01:08.820
No, nobody knew

01:01:08.820 --> 01:01:09.480
what the internet was.

01:01:10.420 --> 01:01:11.340
None of that kind of

01:01:11.340 --> 01:01:11.580
crap.

01:01:11.700 --> 01:01:12.760
And, like, I remember

01:01:12.760 --> 01:01:13.680
telnetting to different

01:01:13.680 --> 01:01:14.700
systems, and, like,

01:01:14.960 --> 01:01:15.780
talking to people

01:01:15.780 --> 01:01:16.960
online through Usenet

01:01:16.960 --> 01:01:17.600
in, like, different

01:01:17.600 --> 01:01:18.280
places over the world.

01:01:18.340 --> 01:01:19.180
I had math on my

01:01:19.180 --> 01:01:20.040
wall, like a true

01:01:20.040 --> 01:01:20.380
loser.

01:01:20.380 --> 01:01:21.300
And true loser

01:01:21.300 --> 01:01:22.620
style, I had a map

01:01:22.620 --> 01:01:23.540
on my wall, like a

01:01:23.540 --> 01:01:24.360
world map, and I

01:01:24.360 --> 01:01:25.000
had, like, little,

01:01:25.360 --> 01:01:26.280
like, pushpins, like

01:01:26.280 --> 01:01:26.960
people that I knew

01:01:26.960 --> 01:01:27.460
that were on the

01:01:27.460 --> 01:01:28.080
internet, and I

01:01:28.080 --> 01:01:28.880
would, like, put a

01:01:28.880 --> 01:01:30.080
little pin for, you

01:01:30.080 --> 01:01:31.120
know, for people that

01:01:31.120 --> 01:01:31.640
I had met on the

01:01:31.640 --> 01:01:31.900
internet.

01:01:32.160 --> 01:01:33.000
And I had tons of

01:01:33.000 --> 01:01:33.600
them all over the

01:01:33.600 --> 01:01:33.860
place.

01:01:34.300 --> 01:01:35.280
I gotta say, I

01:01:35.280 --> 01:01:36.120
never actually did

01:01:36.120 --> 01:01:36.600
that, although I

01:01:36.600 --> 01:01:37.360
did have my world

01:01:37.360 --> 01:01:39.160
map for radio

01:01:39.160 --> 01:01:39.980
contacts, which was

01:01:39.980 --> 01:01:42.440
my other, I don't

01:01:42.440 --> 01:01:43.880
know, weapon of

01:01:43.880 --> 01:01:44.420
choice, I guess you

01:01:44.420 --> 01:01:44.780
could call it.

01:01:45.800 --> 01:01:46.440
That's what I used

01:01:46.440 --> 01:01:47.020
to use mine for.

01:01:47.140 --> 01:01:47.700
I got on the

01:01:47.700 --> 01:01:48.060
internet, but,

01:01:48.140 --> 01:01:48.920
you know, on

01:01:48.920 --> 01:01:49.360
December

01:01:49.360 --> 01:01:51.140
94, I think.

01:01:51.380 --> 01:01:52.000
That's what it was.

01:01:52.080 --> 01:01:53.000
I got a modem for

01:01:53.000 --> 01:01:54.400
my, for Christmas, and

01:01:54.400 --> 01:01:55.280
that's where I

01:01:55.280 --> 01:01:56.040
started, and I got

01:01:56.040 --> 01:01:58.260
this little ISP, and

01:01:58.260 --> 01:01:58.720
it was, you know,

01:01:58.720 --> 01:01:59.400
mom and pop, and

01:01:59.400 --> 01:02:00.140
they've since been

01:02:00.140 --> 01:02:00.900
sold, like, two or

01:02:00.900 --> 01:02:01.880
three times, and I

01:02:01.880 --> 01:02:02.440
don't even know what

01:02:02.440 --> 01:02:02.840
they were, I think

01:02:02.840 --> 01:02:03.360
they're owned by

01:02:03.360 --> 01:02:04.280
Primus now, which is

01:02:04.280 --> 01:02:04.940
very depressing.

01:02:04.940 --> 01:02:06.940
And that's what I

01:02:06.940 --> 01:02:07.420
used to do, and I

01:02:07.420 --> 01:02:07.980
used to do the same

01:02:07.980 --> 01:02:08.480
thing I used to do,

01:02:08.560 --> 01:02:09.820
Usenet, and God,

01:02:10.000 --> 01:02:10.580
God, I haven't been

01:02:10.580 --> 01:02:11.080
in Usenet in

01:02:11.080 --> 01:02:11.360
forever.

01:02:12.120 --> 01:02:12.660
I think I had that

01:02:12.660 --> 01:02:13.260
in my Speakeasy

01:02:13.260 --> 01:02:13.540
account.

01:02:13.640 --> 01:02:13.940
I think I have to

01:02:13.940 --> 01:02:14.640
fire that up.

01:02:16.000 --> 01:02:17.400
And it was just,

01:02:17.760 --> 01:02:18.560
and people, like, I

01:02:18.560 --> 01:02:19.660
used to, oh, email,

01:02:19.900 --> 01:02:20.620
and people used to

01:02:20.620 --> 01:02:21.020
look at me and say,

01:02:21.100 --> 01:02:21.760
email, what the

01:02:21.760 --> 01:02:22.280
hell is that?

01:02:22.780 --> 01:02:23.840
And I distinctly

01:02:23.840 --> 01:02:24.460
remember saying to

01:02:24.460 --> 01:02:25.240
myself, you know,

01:02:25.260 --> 01:02:26.060
World Wide Web, what

01:02:26.060 --> 01:02:26.660
the hell is that?

01:02:27.740 --> 01:02:28.540
Oh, yeah, I remember

01:02:28.540 --> 01:02:29.600
being a real fan of

01:02:29.600 --> 01:02:30.420
Gopher back in the

01:02:30.420 --> 01:02:30.600
day.

01:02:30.600 --> 01:02:31.820
Yeah, Gopher was

01:02:31.820 --> 01:02:32.420
the shit.

01:02:33.620 --> 01:02:35.080
I actually think

01:02:35.080 --> 01:02:35.480
there's, like, a

01:02:35.480 --> 01:02:36.160
couple of ports out

01:02:36.160 --> 01:02:36.320
there.

01:02:36.560 --> 01:02:37.720
I'm going to set up

01:02:37.720 --> 01:02:39.100
a Gopher server on

01:02:39.100 --> 01:02:40.640
my, you know, on

01:02:40.640 --> 01:02:41.100
my server.

01:02:42.020 --> 01:02:42.380
I'm going to put,

01:02:42.460 --> 01:02:43.160
like, old school

01:02:43.160 --> 01:02:43.940
freaking test on

01:02:43.940 --> 01:02:44.080
there.

01:02:44.240 --> 01:02:44.560
That's what I'm

01:02:44.560 --> 01:02:44.860
going to do.

01:02:45.560 --> 01:02:46.100
Add that to my

01:02:46.100 --> 01:02:46.620
to-do list.

01:02:47.020 --> 01:02:47.240
I'm going to be

01:02:47.240 --> 01:02:47.760
like, yeah.

01:02:48.900 --> 01:02:49.640
Dude, Gopher

01:02:49.640 --> 01:02:50.940
colon slash slash,

01:02:51.020 --> 01:02:51.300
man.

01:02:52.460 --> 01:02:53.540
Oh, my God.

01:02:53.720 --> 01:02:54.240
Does Firefox

01:02:54.240 --> 01:02:54.960
support that?

01:02:55.000 --> 01:02:55.480
I don't even know.

01:02:55.540 --> 01:02:56.100
I know Mozilla

01:02:56.100 --> 01:02:56.240
used to do it.

01:02:56.240 --> 01:02:56.900
You know something?

01:02:57.080 --> 01:02:58.200
I'll bet you that

01:02:58.200 --> 01:02:58.600
it does.

01:02:58.780 --> 01:03:00.080
Gopher colon slash slash.

01:03:01.440 --> 01:03:02.220
Oh, look at that.

01:03:02.260 --> 01:03:02.640
It does.

01:03:04.100 --> 01:03:04.460
Wow.

01:03:04.580 --> 01:03:05.280
Oh, my God.

01:03:05.320 --> 01:03:05.920
That's pretty neat.

01:03:06.440 --> 01:03:07.060
I'm going to try that

01:03:07.060 --> 01:03:07.220
out.

01:03:07.320 --> 01:03:07.780
I'm going to find a

01:03:07.780 --> 01:03:08.600
Gopher server someplace

01:03:08.600 --> 01:03:08.960
now.

01:03:10.680 --> 01:03:11.680
Essentially, Gopher

01:03:11.680 --> 01:03:12.780
was, for those of you

01:03:12.780 --> 01:03:13.060
who don't know,

01:03:13.140 --> 01:03:15.000
Gopher was the stuff

01:03:15.000 --> 01:03:16.620
before the web, and

01:03:16.620 --> 01:03:18.640
what it was is it used

01:03:18.640 --> 01:03:19.420
to have just a bunch

01:03:19.420 --> 01:03:20.580
of cascading menus.

01:03:20.780 --> 01:03:21.460
It didn't actually

01:03:21.460 --> 01:03:22.300
have, like, hypertext

01:03:22.300 --> 01:03:22.640
or anything.

01:03:23.180 --> 01:03:24.380
It's vaguely related

01:03:24.380 --> 01:03:28.460
to HTTP, the transfer

01:03:28.460 --> 01:03:29.300
protocol, at least, but

01:03:29.300 --> 01:03:30.200
nothing like HTML.

01:03:30.880 --> 01:03:31.620
Basically, you know,

01:03:31.780 --> 01:03:33.140
you'd say, you know,

01:03:33.180 --> 01:03:34.240
oh, I want to see

01:03:34.240 --> 01:03:35.920
stuff, you know, see

01:03:35.920 --> 01:03:37.040
stuff in archaeology,

01:03:37.200 --> 01:03:37.760
and then it's like,

01:03:37.820 --> 01:03:38.660
okay, well, you want

01:03:38.660 --> 01:03:39.480
to classify stuff by

01:03:39.480 --> 01:03:40.860
author, and you go

01:03:40.860 --> 01:03:41.620
down, and basically,

01:03:41.760 --> 01:03:42.260
it's just like this

01:03:42.260 --> 01:03:43.060
giant directory, and

01:03:43.060 --> 01:03:43.600
you'd have, like,

01:03:43.720 --> 01:03:45.160
archaeology, authors,

01:03:45.380 --> 01:03:46.420
authors starting with

01:03:46.420 --> 01:03:48.580
the letter Z, and,

01:03:48.700 --> 01:03:51.540
you know, Zimler, I

01:03:51.540 --> 01:03:52.220
can't think of a Z

01:03:52.220 --> 01:03:52.640
starting name.

01:03:52.720 --> 01:03:53.940
Some authors starting

01:03:53.940 --> 01:03:54.800
with Z, and you'd get

01:03:54.800 --> 01:03:55.840
like a list of text,

01:03:55.840 --> 01:03:57.860
text, and I've got to

01:03:57.860 --> 01:03:58.580
say, it was pretty

01:03:58.580 --> 01:03:59.260
cool at the time.

01:03:59.480 --> 01:04:00.240
I thought it was

01:04:00.240 --> 01:04:00.960
pretty nice.

01:04:03.080 --> 01:04:03.800
Back in the day,

01:04:04.000 --> 01:04:05.460
what we used to

01:04:05.460 --> 01:04:06.260
use to is, like, you

01:04:06.260 --> 01:04:07.140
know, graphics and

01:04:07.140 --> 01:04:07.440
everything.

01:04:07.660 --> 01:04:08.340
God, we didn't have

01:04:08.340 --> 01:04:08.920
those, did we?

01:04:09.540 --> 01:04:10.300
Unless you were, like,

01:04:10.300 --> 01:04:11.040
really cool back in the

01:04:11.040 --> 01:04:11.060
time.

01:04:11.060 --> 01:04:14.420
No, I remember hearing

01:04:14.420 --> 01:04:15.340
about the World Wide

01:04:15.340 --> 01:04:16.800
Web and Gopher, and I

01:04:16.800 --> 01:04:17.480
remember I had a Gopher

01:04:17.480 --> 01:04:18.200
client that had no

01:04:18.200 --> 01:04:19.900
graphics, and I remember

01:04:19.900 --> 01:04:20.800
actually making fun of

01:04:20.800 --> 01:04:21.420
somebody, because I was

01:04:21.420 --> 01:04:22.700
like, ooh, I can't just

01:04:22.700 --> 01:04:23.780
read my information, I

01:04:23.780 --> 01:04:24.520
need to have pretty

01:04:24.520 --> 01:04:25.580
graphics to go along

01:04:25.580 --> 01:04:25.900
with it.

01:04:27.980 --> 01:04:29.060
It's funny how things

01:04:29.060 --> 01:04:29.540
change.

01:04:31.000 --> 01:04:32.320
So, yeah, my first

01:04:32.320 --> 01:04:33.140
internet account,

01:04:33.500 --> 01:04:34.780
definitely no graphics,

01:04:34.960 --> 01:04:35.680
all text mode.

01:04:35.720 --> 01:04:36.120
No PPP.

01:04:36.120 --> 01:04:37.380
It was all text for me,

01:04:37.440 --> 01:04:37.560
too.

01:04:37.880 --> 01:04:38.460
Just text.

01:04:38.800 --> 01:04:40.200
And even before

01:04:40.200 --> 01:04:41.040
internet access, I

01:04:41.060 --> 01:04:42.920
did have a motive, but

01:04:42.920 --> 01:04:43.780
I just had dial-up

01:04:43.780 --> 01:04:44.800
BBS that I connected

01:04:44.800 --> 01:04:46.720
to, and some of them

01:04:46.720 --> 01:04:48.700
had graphics, but not

01:04:48.700 --> 01:04:49.220
most of them.

01:04:49.660 --> 01:04:50.280
It used to be, like,

01:04:50.340 --> 01:04:50.860
ASCII art.

01:04:51.760 --> 01:04:52.700
Yeah, they had ASCII

01:04:52.700 --> 01:04:53.240
art, and then they

01:04:53.240 --> 01:04:54.100
came out, if anybody's

01:04:54.100 --> 01:04:54.820
really interested in

01:04:54.820 --> 01:04:55.820
looking this up, there

01:04:55.820 --> 01:04:56.740
was a protocol called

01:04:56.740 --> 01:04:58.500
RIP, not the routing

01:04:58.500 --> 01:04:59.700
protocol, but there was

01:04:59.700 --> 01:05:00.500
another protocol called

01:05:00.500 --> 01:05:01.580
RIP, where you could

01:05:01.580 --> 01:05:02.620
connect with a special

01:05:02.620 --> 01:05:04.440
client and dial up and

01:05:04.440 --> 01:05:05.560
get, like, you know,

01:05:05.600 --> 01:05:06.740
these weird, like,

01:05:06.800 --> 01:05:07.860
vector-based graphics

01:05:07.860 --> 01:05:08.600
that it would draw, you

01:05:08.600 --> 01:05:09.420
know, it would draw a

01:05:09.420 --> 01:05:10.420
couple of lines and then

01:05:10.420 --> 01:05:11.060
fill it in.

01:05:11.700 --> 01:05:12.260
Oh, that's pretty

01:05:12.260 --> 01:05:12.400
cool.

01:05:13.480 --> 01:05:14.720
See, I sort of skipped

01:05:14.720 --> 01:05:15.640
the whole BBS thing.

01:05:15.760 --> 01:05:16.940
I came in and basically

01:05:16.940 --> 01:05:17.920
plunged straight onto the

01:05:17.920 --> 01:05:18.100
internet.

01:05:18.280 --> 01:05:19.160
I never really got

01:05:19.160 --> 01:05:19.920
interested in anything

01:05:19.920 --> 01:05:20.680
else beyond that.

01:05:21.720 --> 01:05:22.600
You know, where I

01:05:22.600 --> 01:05:23.940
lived, I had no option

01:05:23.940 --> 01:05:24.720
to get internet access

01:05:24.720 --> 01:05:25.380
for years.

01:05:25.500 --> 01:05:26.680
I looked everywhere for

01:05:26.680 --> 01:05:26.780
it.

01:05:26.780 --> 01:05:27.940
I called up all of the

01:05:27.940 --> 01:05:28.720
universities, and I

01:05:28.720 --> 01:05:31.160
all said, no, either we

01:05:31.160 --> 01:05:32.040
don't have internet

01:05:32.040 --> 01:05:33.760
access, or we do, but

01:05:33.760 --> 01:05:34.740
it's only available to

01:05:34.740 --> 01:05:35.060
students.

01:05:35.280 --> 01:05:36.180
And being that I was

01:05:36.180 --> 01:05:37.880
12, I didn't really

01:05:37.880 --> 01:05:38.300
qualify.

01:05:38.300 --> 01:05:39.320
You weren't in

01:05:39.320 --> 01:05:39.800
college when you

01:05:39.800 --> 01:05:40.220
were 12?

01:05:42.220 --> 01:05:42.960
Maybe I could have

01:05:42.960 --> 01:05:43.520
gone to community

01:05:43.520 --> 01:05:43.960
college.

01:05:44.340 --> 01:05:44.840
Dude, you could have

01:05:44.840 --> 01:05:46.440
social engineered your

01:05:46.440 --> 01:05:46.860
way in, though.

01:05:47.860 --> 01:05:48.560
But elite?

01:05:49.620 --> 01:05:50.900
Yeah, I should have, but

01:05:50.900 --> 01:05:52.420
I was lame at the

01:05:52.420 --> 01:05:52.760
time.

01:05:52.860 --> 01:05:53.920
I still am lame, but

01:05:53.920 --> 01:05:55.120
I was more lame.

01:05:55.280 --> 01:05:56.140
Obviously, this is a

01:05:56.140 --> 01:05:57.140
kind of lameness other

01:05:57.140 --> 01:05:58.140
people like me try to

01:05:58.140 --> 01:05:58.780
aspire to.

01:06:00.320 --> 01:06:01.700
Yeah, well, let's see if

01:06:01.700 --> 01:06:02.220
I ever get another

01:06:02.220 --> 01:06:02.940
project done, then

01:06:02.940 --> 01:06:03.740
people can start saying

01:06:03.740 --> 01:06:04.220
I'm not lame.

01:06:04.220 --> 01:06:06.140
But my motivation now

01:06:06.140 --> 01:06:07.360
is that I'm feeling

01:06:07.360 --> 01:06:07.840
very lame.

01:06:09.700 --> 01:06:11.200
Okay, so we've

01:06:11.200 --> 01:06:12.120
completely drifted off

01:06:12.120 --> 01:06:13.540
topic here, so let's

01:06:13.540 --> 01:06:14.220
go get back to

01:06:14.220 --> 01:06:14.460
Perl.

01:06:15.080 --> 01:06:15.760
Yeah, Perl.

01:06:15.860 --> 01:06:16.600
I think we pretty much

01:06:16.600 --> 01:06:17.660
explained everything.

01:06:17.980 --> 01:06:18.900
Just try the

01:06:18.900 --> 01:06:19.680
tutorials, figure it

01:06:19.680 --> 01:06:19.820
out.

01:06:19.900 --> 01:06:20.580
It's a lot of fun.

01:06:21.720 --> 01:06:23.180
Basically, I think

01:06:23.180 --> 01:06:24.400
Perl, I have a quote

01:06:24.400 --> 01:06:25.520
here, and basically I

01:06:25.520 --> 01:06:25.980
feel that it

01:06:25.980 --> 01:06:26.620
submises Perl

01:06:26.620 --> 01:06:27.060
perfectly.

01:06:28.000 --> 01:06:28.760
I found it on the

01:06:28.760 --> 01:06:28.920
web.

01:06:28.920 --> 01:06:30.000
It's by Charles

01:06:30.000 --> 01:06:32.300
C-A-Z-A-B-A-O-N.

01:06:32.560 --> 01:06:34.280
I'm sorry, C-A-Z-A-B-O-N.

01:06:34.800 --> 01:06:35.680
Cazabon or something.

01:06:36.440 --> 01:06:37.840
And he says, Perl

01:06:37.840 --> 01:06:38.560
isn't really a Swiss

01:06:38.560 --> 01:06:39.040
Army knife.

01:06:39.160 --> 01:06:39.940
That's more like C.

01:06:40.340 --> 01:06:41.280
Perl is a large

01:06:41.280 --> 01:06:42.000
metallic toolbox

01:06:42.000 --> 01:06:44.240
containing, one, a

01:06:44.240 --> 01:06:44.840
complete set of

01:06:44.840 --> 01:06:45.600
boxed end wrenches,

01:06:45.760 --> 01:06:46.420
both metric and

01:06:46.420 --> 01:06:47.500
imperial, except for

01:06:47.500 --> 01:06:48.380
10 millimeters and

01:06:48.380 --> 01:06:49.160
3-eighths inch.

01:06:49.840 --> 01:06:51.440
Two, a selection of

01:06:51.440 --> 01:06:52.100
five machinist

01:06:52.100 --> 01:06:52.420
hammers.

01:06:52.920 --> 01:06:54.180
Three, one regular

01:06:54.180 --> 01:06:54.960
construction hammer.

01:06:55.600 --> 01:06:57.660
Four, 10 and 12

01:06:57.660 --> 01:06:58.240
pound sledge

01:06:58.240 --> 01:06:58.580
hammers.

01:06:58.920 --> 01:07:00.520
Five, a complete

01:07:00.520 --> 01:07:01.460
set of Robertson

01:07:01.460 --> 01:07:02.140
screwdrivers.

01:07:02.740 --> 01:07:03.920
And six, an infinite

01:07:03.920 --> 01:07:04.900
length of duct tape.

01:07:05.180 --> 01:07:06.160
And I've got to say

01:07:06.160 --> 01:07:07.420
that fits Perl to a

01:07:07.420 --> 01:07:07.540
T.

01:07:08.460 --> 01:07:09.220
Yeah, that's

01:07:09.220 --> 01:07:10.260
really clever.

01:07:10.380 --> 01:07:11.080
I've never heard

01:07:11.080 --> 01:07:11.500
that before.

01:07:11.900 --> 01:07:13.120
I think I got it

01:07:13.120 --> 01:07:14.160
from Alt-SysAdmin

01:07:14.160 --> 01:07:14.940
Recovery, which is

01:07:14.940 --> 01:07:15.780
another, actually, no,

01:07:15.820 --> 01:07:16.380
I'm not going to say

01:07:16.380 --> 01:07:16.840
it out loud.

01:07:17.120 --> 01:07:17.740
No one go there,

01:07:17.880 --> 01:07:18.140
please.

01:07:20.220 --> 01:07:20.940
Don't go there

01:07:20.940 --> 01:07:21.520
unless you're used

01:07:21.520 --> 01:07:22.020
to Usenet.

01:07:24.740 --> 01:07:25.760
Hopefully nobody's

01:07:25.760 --> 01:07:26.340
used to Usenet

01:07:26.340 --> 01:07:26.680
anymore.

01:07:26.940 --> 01:07:27.480
Yeah, I don't think

01:07:27.480 --> 01:07:28.140
anyone really does

01:07:28.140 --> 01:07:28.860
besides spammers.

01:07:30.220 --> 01:07:30.740
And people who

01:07:30.740 --> 01:07:31.280
trade wares.

01:07:32.560 --> 01:07:33.220
Wares, really?

01:07:33.960 --> 01:07:35.140
Yeah, yeah, you'd be

01:07:35.140 --> 01:07:35.540
surprised.

01:07:35.860 --> 01:07:37.020
Oh, I'll have to

01:07:37.020 --> 01:07:37.600
check that out.

01:07:38.600 --> 01:07:39.400
That's not what I'm

01:07:39.400 --> 01:07:39.700
saying.

01:07:40.100 --> 01:07:40.880
But I do know

01:07:40.880 --> 01:07:41.540
people who get

01:07:41.540 --> 01:07:43.040
like Super News

01:07:43.040 --> 01:07:43.680
or Air News

01:07:43.680 --> 01:07:44.460
accounts or something

01:07:44.460 --> 01:07:45.660
like that, and

01:07:45.660 --> 01:07:46.580
they go on there

01:07:46.580 --> 01:07:47.280
because they say

01:07:47.280 --> 01:07:47.780
that it's the best

01:07:47.780 --> 01:07:48.280
place to find

01:07:48.280 --> 01:07:48.640
wares.

01:07:49.280 --> 01:07:50.000
Essentially what I'll

01:07:50.000 --> 01:07:50.860
do is I will look at

01:07:50.860 --> 01:07:51.340
it and say,

01:07:51.440 --> 01:07:52.000
oh, look at that.

01:07:52.060 --> 01:07:52.440
That's neat

01:07:52.440 --> 01:07:53.120
because I do not

01:07:53.120 --> 01:07:53.800
believe in software

01:07:53.800 --> 01:07:54.520
piracy because

01:07:54.520 --> 01:07:55.400
software piracy is

01:07:55.400 --> 01:07:55.640
bad.

01:07:55.780 --> 01:07:56.160
Neither does

01:07:56.160 --> 01:07:56.480
DDP.

01:07:56.580 --> 01:07:56.900
Ah.

01:07:57.500 --> 01:07:58.040
You could believe

01:07:58.040 --> 01:07:58.640
in porn, though.

01:07:58.660 --> 01:07:59.100
They said there's a

01:07:59.100 --> 01:07:59.660
lot of porn there,

01:07:59.720 --> 01:07:59.880
too.

01:08:00.080 --> 01:08:00.660
Oh, I know there's

01:08:00.660 --> 01:08:01.260
a lot of porn there.

01:08:01.340 --> 01:08:01.900
What do you think I

01:08:01.900 --> 01:08:02.420
was doing on the

01:08:02.420 --> 01:08:03.020
Usenet when I was

01:08:03.020 --> 01:08:03.500
13?

01:08:03.700 --> 01:08:03.900
Jeez.

01:08:04.520 --> 01:08:05.240
Ah, yes.

01:08:05.340 --> 01:08:05.620
Okay.

01:08:05.880 --> 01:08:06.140
Fair enough.

01:08:06.140 --> 01:08:06.800
We no longer

01:08:06.800 --> 01:08:07.900
actually support that

01:08:07.900 --> 01:08:08.120
either.

01:08:08.480 --> 01:08:10.980
Any other fun

01:08:10.980 --> 01:08:11.700
Perl-related

01:08:11.700 --> 01:08:12.700
things to wrap up

01:08:12.700 --> 01:08:12.900
with?

01:08:14.900 --> 01:08:15.940
No, not really.

01:08:16.080 --> 01:08:17.420
Just, you know,

01:08:17.760 --> 01:08:18.560
mess around with it,

01:08:18.900 --> 01:08:19.380
play with it,

01:08:19.380 --> 01:08:19.940
and look for all

01:08:19.940 --> 01:08:20.740
the modules first.

01:08:20.820 --> 01:08:21.460
Before you go write

01:08:21.460 --> 01:08:22.580
anything huge,

01:08:22.780 --> 01:08:23.480
definitely check out

01:08:23.480 --> 01:08:24.260
CPAM like we were

01:08:24.260 --> 01:08:24.580
saying.

01:08:24.840 --> 01:08:25.020
Yeah.

01:08:25.820 --> 01:08:26.400
Somebody's probably

01:08:26.400 --> 01:08:28.280
implemented, you

01:08:28.280 --> 01:08:29.040
know, whatever you've

01:08:29.040 --> 01:08:30.540
thought of already.

01:08:30.920 --> 01:08:31.100
Yeah.

01:08:31.640 --> 01:08:32.220
And essentially,

01:08:32.360 --> 01:08:32.940
a lot of the times

01:08:32.940 --> 01:08:34.220
it's just one module

01:08:34.220 --> 01:08:34.900
will do one thing,

01:08:34.960 --> 01:08:35.580
another module will

01:08:35.580 --> 01:08:36.100
do the other thing,

01:08:36.140 --> 01:08:36.640
and what you have to

01:08:36.640 --> 01:08:37.400
do is just interhook

01:08:37.400 --> 01:08:38.400
them together in one

01:08:38.400 --> 01:08:39.140
way, shape, or form.

01:08:39.660 --> 01:08:40.560
I mean, that's

01:08:40.560 --> 01:08:41.240
essentially what I do

01:08:41.240 --> 01:08:41.960
with Asterisk in a

01:08:41.960 --> 01:08:43.220
lot of my more

01:08:43.220 --> 01:08:43.860
quote-unquote

01:08:43.860 --> 01:08:44.820
cooler programs.

01:08:45.440 --> 01:08:47.000
I took the email

01:08:47.000 --> 01:08:47.640
reading program,

01:08:47.760 --> 01:08:48.820
I took the Asterisk

01:08:48.820 --> 01:08:49.860
AGI module which

01:08:49.860 --> 01:08:50.340
interfaced with

01:08:50.340 --> 01:08:50.940
Asterisk, and I

01:08:50.940 --> 01:08:51.840
took an IMAP module

01:08:51.840 --> 01:08:52.700
that interfaced with

01:08:52.700 --> 01:08:54.760
the Internet Mail

01:08:54.760 --> 01:08:56.220
application protocol,

01:08:56.460 --> 01:08:57.260
access protocol or

01:08:57.260 --> 01:08:58.720
something, and I

01:08:58.720 --> 01:08:59.340
just basically

01:08:59.340 --> 01:09:00.440
hammered it out

01:09:00.440 --> 01:09:01.280
together with my,

01:09:01.320 --> 01:09:01.860
you know, 10 and

01:09:01.860 --> 01:09:02.780
12-pound sledge

01:09:02.780 --> 01:09:04.020
hammers and made

01:09:04.020 --> 01:09:04.560
them work together

01:09:04.560 --> 01:09:05.120
and talk to each

01:09:05.120 --> 01:09:05.280
other.

01:09:05.540 --> 01:09:06.560
And that's all it

01:09:06.560 --> 01:09:07.680
was, and that's

01:09:07.680 --> 01:09:08.460
what make modules so

01:09:08.460 --> 01:09:08.680
cool.

01:09:09.940 --> 01:09:10.180
Yep.

01:09:10.180 --> 01:09:10.780
So I think we'll

01:09:10.780 --> 01:09:11.460
just kind of move

01:09:11.460 --> 01:09:12.060
on to the wrapping

01:09:12.060 --> 01:09:12.840
up here because we're

01:09:12.840 --> 01:09:15.280
talking about line

01:09:15.280 --> 01:09:16.580
noise and BBSs and

01:09:16.580 --> 01:09:17.140
then talking about

01:09:17.140 --> 01:09:17.840
sledgehammers and

01:09:17.840 --> 01:09:18.100
Perl.

01:09:18.100 --> 01:09:19.540
Oh, hey, you

01:09:19.540 --> 01:09:19.960
know, if people

01:09:19.960 --> 01:09:20.560
don't appreciate

01:09:20.560 --> 01:09:22.280
that, then that

01:09:22.280 --> 01:09:23.000
would really hurt my

01:09:23.000 --> 01:09:23.360
feelings.

01:09:23.560 --> 01:09:24.420
Yes, I think we'll

01:09:24.420 --> 01:09:25.180
get a couple of

01:09:25.180 --> 01:09:25.700
emails saying,

01:09:25.780 --> 01:09:26.440
line noise, what's

01:09:26.440 --> 01:09:26.660
that?

01:09:26.800 --> 01:09:27.420
Or, oh, I

01:09:27.420 --> 01:09:28.420
remember doing the

01:09:28.420 --> 01:09:29.100
BBS thing.

01:09:30.020 --> 01:09:31.200
Yeah, if anybody

01:09:31.200 --> 01:09:32.320
out there remembers

01:09:32.320 --> 01:09:34.240
line noise and

01:09:34.240 --> 01:09:36.700
MMP4 and MMP5 and

01:09:36.700 --> 01:09:38.480
V32 and V42 and

01:09:38.480 --> 01:09:39.680
V42 bits and all

01:09:39.680 --> 01:09:40.460
those other standards

01:09:40.460 --> 01:09:41.140
that everyone would

01:09:41.140 --> 01:09:42.760
brag about, yeah,

01:09:43.060 --> 01:09:44.380
when somebody got

01:09:44.380 --> 01:09:45.360
one of these modems,

01:09:45.360 --> 01:09:46.800
so I started on a

01:09:46.800 --> 01:09:47.820
2400 board modem,

01:09:47.900 --> 01:09:48.560
but when I

01:09:48.560 --> 01:09:49.640
upgraded to a

01:09:49.640 --> 01:09:50.980
14-4 and it had

01:09:50.980 --> 01:09:51.800
like all these

01:09:51.800 --> 01:09:53.120
crazy standards and

01:09:53.120 --> 01:09:54.320
like no more line

01:09:54.320 --> 01:09:55.120
noise because it had

01:09:55.120 --> 01:09:56.300
MMP5 and all this

01:09:56.300 --> 01:09:57.200
other crap, if

01:09:57.200 --> 01:09:58.140
anybody remembers

01:09:58.140 --> 01:09:59.080
going through that

01:09:59.080 --> 01:10:00.100
phase of buying a

01:10:00.100 --> 01:10:02.260
$500 14-4 modem,

01:10:02.640 --> 01:10:03.760
please, write us

01:10:03.760 --> 01:10:04.500
email because I

01:10:04.500 --> 01:10:05.160
would love to hear

01:10:05.160 --> 01:10:05.540
about it.

01:10:06.540 --> 01:10:07.120
Radio at

01:10:07.120 --> 01:10:08.100
BinRev.com and

01:10:08.100 --> 01:10:08.640
we'll go set up a

01:10:08.640 --> 01:10:09.340
mailing list like

01:10:09.340 --> 01:10:09.600
the, you know,

01:10:09.660 --> 01:10:10.980
oldfarts-l or

01:10:10.980 --> 01:10:11.260
something.

01:10:12.340 --> 01:10:13.160
Yes, definitely.

01:10:14.100 --> 01:10:14.800
Anyway, we have

01:10:14.800 --> 01:10:16.040
actually a lot of

01:10:16.040 --> 01:10:17.100
announcements this

01:10:17.100 --> 01:10:17.360
week.

01:10:17.660 --> 01:10:18.740
So far, we got an

01:10:18.740 --> 01:10:20.020
email from 2600

01:10:20.020 --> 01:10:21.880
Denver and I'm not

01:10:21.880 --> 01:10:22.480
sure if this is a

01:10:22.480 --> 01:10:23.660
real Denver 2600

01:10:23.660 --> 01:10:24.340
group or just a

01:10:24.340 --> 01:10:25.140
handle, but he's

01:10:25.140 --> 01:10:25.800
starting a meeting

01:10:25.800 --> 01:10:27.360
in Denver, takes

01:10:27.360 --> 01:10:28.160
place at the

01:10:28.160 --> 01:10:30.540
Borders Cafe, and

01:10:30.540 --> 01:10:31.440
I'm going to

01:10:31.440 --> 01:10:32.160
mispronounce this,

01:10:32.280 --> 01:10:33.140
Parker and

01:10:33.140 --> 01:10:38.600
Arafo, A-R-A-P-A-H-O-E,

01:10:38.760 --> 01:10:39.640
and it starts at

01:10:39.640 --> 01:10:41.500
about 5 and ends

01:10:41.500 --> 01:10:42.380
about between 8

01:10:42.380 --> 01:10:44.020
to 9 or so, and

01:10:44.020 --> 01:10:44.600
is held on the

01:10:44.600 --> 01:10:45.180
first and third

01:10:45.180 --> 01:10:45.780
Fridays of the

01:10:45.780 --> 01:10:46.400
month, and that

01:10:46.400 --> 01:10:46.760
would mean that

01:10:46.760 --> 01:10:47.200
would be this

01:10:47.200 --> 01:10:47.520
Friday.

01:10:47.720 --> 01:10:48.220
I think that's the

01:10:48.220 --> 01:10:48.680
third Friday,

01:10:48.820 --> 01:10:49.240
wouldn't it?

01:10:49.320 --> 01:10:49.480
Yeah.

01:10:50.780 --> 01:10:51.780
I believe BinRev

01:10:51.780 --> 01:10:52.420
meetings are this

01:10:52.420 --> 01:10:52.660
week.

01:10:52.960 --> 01:10:53.300
Do you have a

01:10:53.300 --> 01:10:53.940
BinRev meeting in

01:10:53.940 --> 01:10:54.260
New York?

01:10:54.700 --> 01:10:55.220
I don't have one

01:10:55.220 --> 01:10:55.460
in Boston.

01:10:55.460 --> 01:10:56.580
No, no.

01:10:57.520 --> 01:10:58.080
Not yet.

01:10:59.540 --> 01:11:00.280
I've been thinking

01:11:00.280 --> 01:11:01.740
about doing a

01:11:01.740 --> 01:11:02.740
meeting for a

01:11:02.740 --> 01:11:04.100
while.

01:11:04.280 --> 01:11:04.760
I just, I've

01:11:04.760 --> 01:11:05.220
got to make sure

01:11:05.220 --> 01:11:05.700
that the time

01:11:05.700 --> 01:11:06.360
works out, which

01:11:06.360 --> 01:11:06.880
it never does.

01:11:07.080 --> 01:11:07.560
Yeah, no, it

01:11:07.560 --> 01:11:08.220
never does for me

01:11:08.220 --> 01:11:08.400
either.

01:11:09.640 --> 01:11:10.920
Let's see.

01:11:11.080 --> 01:11:11.980
And for those

01:11:11.980 --> 01:11:12.540
of you in Boston,

01:11:12.640 --> 01:11:13.760
the MIT flea market

01:11:13.760 --> 01:11:14.860
this Sunday from

01:11:14.860 --> 01:11:17.380
9 to 2, basically, I

01:11:17.380 --> 01:11:18.080
think I've discussed

01:11:18.080 --> 01:11:18.640
this before, it's

01:11:18.640 --> 01:11:19.380
essentially a flea

01:11:19.380 --> 01:11:20.040
market for geeks.

01:11:20.120 --> 01:11:20.580
Every type of

01:11:20.580 --> 01:11:21.420
electronic piece of

01:11:21.420 --> 01:11:22.120
equipment you can

01:11:22.120 --> 01:11:23.920
find there, it's a

01:11:23.920 --> 01:11:24.260
treacherous.

01:11:24.500 --> 01:11:25.220
It's a religious

01:11:25.220 --> 01:11:26.160
experience, really.

01:11:26.760 --> 01:11:27.220
You should go

01:11:27.220 --> 01:11:27.440
there.

01:11:27.980 --> 01:11:28.760
I'll be there.

01:11:28.880 --> 01:11:29.860
Boston 2600 will be

01:11:29.860 --> 01:11:31.040
there, and if you're

01:11:31.040 --> 01:11:31.640
anywhere around

01:11:31.640 --> 01:11:32.460
Boston, you should be

01:11:32.460 --> 01:11:33.880
too, so no excuses.

01:11:34.040 --> 01:11:34.600
Come on, let's go.

01:11:34.600 --> 01:11:37.180
I think next week

01:11:37.180 --> 01:11:37.520
we're going to

01:11:37.520 --> 01:11:38.140
start blending over

01:11:38.140 --> 01:11:38.880
to freaking, and

01:11:38.880 --> 01:11:39.920
Strom and I, if he

01:11:39.920 --> 01:11:40.980
gets back from his

01:11:40.980 --> 01:11:41.740
camp x-ray or

01:11:41.740 --> 01:11:42.360
wherever it is, we're

01:11:42.360 --> 01:11:43.160
going to try to do

01:11:43.160 --> 01:11:44.040
our asterisk

01:11:44.040 --> 01:11:45.540
presentation, but no

01:11:45.540 --> 01:11:46.220
promises on that

01:11:46.220 --> 01:11:46.660
one, we're not

01:11:46.660 --> 01:11:46.860
sure.

01:11:48.640 --> 01:11:49.260
Shouts, you got

01:11:49.260 --> 01:11:49.620
any shouts?

01:11:53.100 --> 01:11:55.240
My shouts go to

01:11:55.240 --> 01:11:56.400
Natus, because he

01:11:56.400 --> 01:11:58.600
is very quickly

01:11:58.600 --> 01:12:01.480
learning PHP and I

01:12:01.480 --> 01:12:02.440
think Pearl as

01:12:02.440 --> 01:12:04.740
well, so let's

01:12:04.740 --> 01:12:07.300
not for this project

01:12:07.300 --> 01:12:07.800
that he's doing

01:12:07.800 --> 01:12:08.240
right now.

01:12:08.360 --> 01:12:08.760
I mean, he's been

01:12:08.760 --> 01:12:09.880
asking me PHP-related

01:12:09.880 --> 01:12:10.680
questions all week

01:12:10.680 --> 01:12:11.100
too, so.

01:12:11.900 --> 01:12:12.700
Yeah, yeah, yeah,

01:12:12.700 --> 01:12:13.580
but, you know, he's

01:12:13.580 --> 01:12:14.360
picking it up fast.

01:12:14.960 --> 01:12:15.800
It's kind of creepy

01:12:15.800 --> 01:12:16.620
how fast he's picking

01:12:16.620 --> 01:12:16.940
it up.

01:12:17.460 --> 01:12:18.400
We should do another

01:12:18.400 --> 01:12:19.200
PHP thing.

01:12:19.420 --> 01:12:19.920
There we go.

01:12:20.000 --> 01:12:20.620
There's a topic for

01:12:20.620 --> 01:12:21.320
some other week.

01:12:23.200 --> 01:12:23.780
Whatever week

01:12:23.780 --> 01:12:24.380
Strom doesn't show

01:12:24.380 --> 01:12:24.900
up, PHP.

01:12:25.300 --> 01:12:25.440
Yeah.

01:12:25.920 --> 01:12:26.700
Oh, no, Strom does

01:12:26.700 --> 01:12:27.020
PHP.

01:12:27.500 --> 01:12:28.180
Oh, really?

01:12:28.560 --> 01:12:29.520
I have no idea.

01:12:29.720 --> 01:12:30.640
He uses Pearl, too.

01:12:30.640 --> 01:12:32.020
He does some crazy

01:12:32.020 --> 01:12:32.560
shit with Pearl.

01:12:33.720 --> 01:12:34.820
I had no idea

01:12:34.820 --> 01:12:35.740
Strom was programming.

01:12:36.100 --> 01:12:37.440
Yeah, not as much

01:12:37.440 --> 01:12:39.680
as us, but otherwise,

01:12:39.920 --> 01:12:41.020
I know, we wouldn't

01:12:41.020 --> 01:12:41.680
insult him for that.

01:12:42.700 --> 01:12:43.700
Let's see, I'm not

01:12:43.700 --> 01:12:44.440
sure if I...

01:12:44.440 --> 01:12:45.840
Shouts to Chris for

01:12:45.840 --> 01:12:46.480
sending me that

01:12:46.480 --> 01:12:48.640
Ubuntu pronunciation.

01:12:49.680 --> 01:12:50.040
Ubuntu.

01:12:50.220 --> 01:12:50.720
I need to start

01:12:50.720 --> 01:12:51.240
reading that, because

01:12:51.240 --> 01:12:52.240
I'm still using

01:12:52.240 --> 01:12:54.680
Ubuntu, but whatever.

01:12:55.280 --> 01:12:56.200
And Steve-O for

01:12:56.200 --> 01:12:56.940
correcting my stupid

01:12:56.940 --> 01:12:57.740
mistake on saying

01:12:57.740 --> 01:12:58.980
silence the feed is a

01:12:58.980 --> 01:12:59.820
Linux shell account

01:12:59.820 --> 01:13:00.360
when in reality

01:13:00.360 --> 01:13:02.060
it's BSD-based.

01:13:02.200 --> 01:13:02.620
Pardon me.

01:13:02.820 --> 01:13:04.040
I, you know,

01:13:04.080 --> 01:13:05.120
apologize profusely.

01:13:06.020 --> 01:13:06.880
You're a terrible

01:13:06.880 --> 01:13:07.320
person.

01:13:07.440 --> 01:13:08.460
I'm horrible, aren't

01:13:08.460 --> 01:13:08.640
I?

01:13:08.820 --> 01:13:09.720
You'll never be

01:13:09.720 --> 01:13:10.060
forgiven.

01:13:11.000 --> 01:13:11.780
Site of the week,

01:13:11.900 --> 01:13:12.700
bellsmind.net,

01:13:13.240 --> 01:13:13.760
since not

01:13:13.760 --> 01:13:14.360
theories on the show.

01:13:15.200 --> 01:13:15.660
Yeah, it's free

01:13:15.660 --> 01:13:16.700
and if you haven't

01:13:16.700 --> 01:13:17.720
been there, go there

01:13:17.720 --> 01:13:18.320
right now.

01:13:18.740 --> 01:13:19.140
Check it out.

01:13:19.280 --> 01:13:20.000
Oh, my God.

01:13:20.700 --> 01:13:21.800
I'm almost motivated

01:13:21.800 --> 01:13:22.600
to finish up some of

01:13:22.600 --> 01:13:23.240
these features now,

01:13:23.300 --> 01:13:23.840
but I have so much

01:13:23.840 --> 01:13:24.680
work to do, I can't.

01:13:24.980 --> 01:13:25.280
Well, there you go.

01:13:25.280 --> 01:13:25.900
I promise there

01:13:25.900 --> 01:13:26.640
will be neat things

01:13:26.640 --> 01:13:27.460
coming, and whenever

01:13:27.460 --> 01:13:28.840
I can, and whenever

01:13:28.840 --> 01:13:29.680
I get it done, there

01:13:29.680 --> 01:13:30.260
will be an announcement

01:13:30.260 --> 01:13:31.980
on the show, if you

01:13:31.980 --> 01:13:32.580
guys have time.

01:13:32.720 --> 01:13:33.700
You have, I'm just

01:13:33.700 --> 01:13:34.080
going to send it on

01:13:34.080 --> 01:13:35.060
over, I'll gladly

01:13:35.060 --> 01:13:35.840
take shots for that.

01:13:37.100 --> 01:13:37.960
Yeah, you have 22

01:13:37.960 --> 01:13:38.660
hours if you want to

01:13:38.660 --> 01:13:39.200
get it done, because

01:13:39.200 --> 01:13:39.560
that's when the

01:13:39.560 --> 01:13:40.120
stands in the air.

01:13:41.960 --> 01:13:42.980
Let's see, email,

01:13:43.120 --> 01:13:43.800
as always, radio

01:13:43.800 --> 01:13:44.700
at binrev.com.

01:13:45.280 --> 01:13:46.180
The closing music for

01:13:46.180 --> 01:13:48.780
this week, I'm doing

01:13:48.780 --> 01:13:49.560
a little bit of risque

01:13:49.560 --> 01:13:51.880
here, because this is a

01:13:51.880 --> 01:13:53.140
band that I've fallen

01:13:53.140 --> 01:13:53.620
in love with.

01:13:53.620 --> 01:13:55.000
It was around back in

01:13:55.000 --> 01:13:57.080
mid-2000s, about

01:13:57.080 --> 01:13:58.940
2000 or so, and it's

01:13:58.940 --> 01:13:59.360
a band called

01:13:59.360 --> 01:14:00.260
Splashdown, and what

01:14:00.260 --> 01:14:02.400
it was is, this is

01:14:02.400 --> 01:14:03.400
why MP3s are so

01:14:03.400 --> 01:14:03.640
cool.

01:14:04.120 --> 01:14:04.840
They recorded an

01:14:04.840 --> 01:14:06.720
album, no one wanted

01:14:06.720 --> 01:14:07.440
to produce it, or

01:14:07.440 --> 01:14:09.840
actually sell it, and

01:14:09.840 --> 01:14:11.860
they fought with them

01:14:11.860 --> 01:14:12.540
for about a year and

01:14:12.540 --> 01:14:13.140
a half, and at which

01:14:13.140 --> 01:14:13.820
point they finally

01:14:13.820 --> 01:14:14.800
said, we're breaking

01:14:14.800 --> 01:14:15.580
up, we're sorry,

01:14:15.960 --> 01:14:16.900
they had some

01:14:16.900 --> 01:14:17.540
creative differences,

01:14:17.680 --> 01:14:17.900
whatever.

01:14:18.620 --> 01:14:19.820
At which point, they

01:14:19.820 --> 01:14:20.500
took all their

01:14:20.500 --> 01:14:22.780
albums, and they

01:14:22.780 --> 01:14:23.600
made them an MP3

01:14:23.600 --> 01:14:24.740
and they sent

01:14:24.740 --> 01:14:25.300
around saying,

01:14:25.720 --> 01:14:26.520
guys, do whatever

01:14:26.520 --> 01:14:27.080
you want with this,

01:14:27.100 --> 01:14:27.820
it's all yours, we

01:14:27.820 --> 01:14:28.440
don't care anymore.

01:14:29.160 --> 01:14:30.380
So I'm going to try

01:14:30.380 --> 01:14:31.160
to do it, and

01:14:31.160 --> 01:14:32.180
hopefully we won't

01:14:32.180 --> 01:14:32.940
get sued, and I

01:14:32.940 --> 01:14:33.420
won't have to edit

01:14:33.420 --> 01:14:34.000
this out at some

01:14:34.000 --> 01:14:35.520
point, because I

01:14:35.520 --> 01:14:36.480
mean, I have a copy

01:14:36.480 --> 01:14:36.880
of the email

01:14:36.880 --> 01:14:37.780
someplace saying,

01:14:38.240 --> 01:14:39.020
this is open for

01:14:39.020 --> 01:14:39.440
distribution.

01:14:39.640 --> 01:14:40.200
So they basically

01:14:40.200 --> 01:14:40.780
open-sourced

01:14:40.780 --> 01:14:41.400
everything, and this

01:14:41.400 --> 01:14:42.420
is what MP3s are so

01:14:42.420 --> 01:14:43.100
cool, because

01:14:43.100 --> 01:14:44.340
essentially you would

01:14:44.340 --> 01:14:45.200
never find this

01:14:45.200 --> 01:14:47.060
unless they

01:14:47.060 --> 01:14:48.460
released it like

01:14:48.460 --> 01:14:48.980
this, because

01:14:48.980 --> 01:14:49.940
right now I'd

01:14:49.940 --> 01:14:51.080
probably be sitting

01:14:51.080 --> 01:14:51.720
in some record

01:14:51.720 --> 01:14:52.700
company's closet just

01:14:52.700 --> 01:14:53.360
collecting dust.

01:14:53.600 --> 01:14:54.780
And the music

01:14:54.780 --> 01:14:55.480
tonight is called

01:14:55.480 --> 01:14:56.540
Iron Spy, which I

01:14:56.540 --> 01:14:57.980
think is one of

01:14:57.980 --> 01:14:58.760
their best songs.

01:14:59.880 --> 01:15:01.480
So, anything else

01:15:01.480 --> 01:15:01.880
you would like to

01:15:01.880 --> 01:15:02.240
say tonight?

01:15:03.520 --> 01:15:04.440
No, that's it.

01:15:04.640 --> 01:15:05.340
So I guess we'll

01:15:05.340 --> 01:15:06.080
see you next week,

01:15:06.200 --> 01:15:06.960
same hack time.

01:15:07.760 --> 01:15:08.780
Same hack channel.

01:15:08.780 --> 01:15:29.060
Iron Spy, I didn't hear you

01:15:29.060 --> 01:15:37.340
coming from behind, yes I'm afraid

01:15:37.340 --> 01:15:47.440
to turn around, no one to point, no whisper, like a child.

01:15:47.440 --> 01:15:50.540
I'm so surprised to hear you now.

01:15:51.440 --> 01:15:57.060
I understand someone who lays down on the top of the screen

01:15:57.060 --> 01:15:59.860
I don't see

01:15:59.860 --> 01:16:00.520
through the переж optimal

01:16:00.520 --> 01:16:00.940
ねぇ

01:16:00.940 --> 01:16:03.680
I thought five or three

01:16:03.680 --> 01:16:04.260
but I saw you

01:16:04.260 --> 01:16:14.100
Yeah, you've never been truly mine, but if you were, yes, if you were, I wouldn't want you anyway.

01:16:14.100 --> 01:16:36.580
I'm free to stay. I promise I'm trying to hide it now. You've made the guts to stay to watch this dream.

01:16:36.580 --> 01:16:45.600
Just make sure if she just stays with me.

01:16:46.600 --> 01:16:56.080
Stop my hands from taking my hurt and my fine time.

01:16:56.080 --> 01:17:10.180
Stopped in lightning, raging anger. Yeah, you've never been truly mine, but if you were, yes, if you were, I wouldn't want you anyway.

01:17:10.180 --> 01:17:40.160
Yeah, you've never been truly mine.

01:17:40.180 --> 01:18:10.160
Stopped in lightning.

01:18:10.160 --> 01:18:12.160
Stopped in lightning.

01:18:12.160 --> 01:18:14.160
Stopped in lightning.

01:18:14.160 --> 01:18:38.160
Stopped in lightning, raging anger. Yeah, you've never been truly mine, but if you were, yes, if you were.

01:18:38.160 --> 01:18:40.160
If you were, yes, if you were.

01:18:40.160 --> 01:18:44.160
I wouldn't want you anyway.

01:18:44.160 --> 01:18:46.160
Oh, Lord.

01:18:46.160 --> 01:18:50.160
Stopped in lightning, raging anger. Yeah, you've never been truly mine.

01:18:50.160 --> 01:18:52.160
Stopped in lightning.

01:18:52.160 --> 01:18:54.160
Stopped in lightning.

01:18:54.160 --> 01:18:56.160
Stopped in lightning.

01:18:56.160 --> 01:19:00.160
Stopped in lightning, raging anger. Yeah, you've never been truly mine.

01:19:00.160 --> 01:19:02.160
But if you were, yes, if you were, yes, if you were.

01:19:02.160 --> 01:19:04.160
I wouldn't want you anyway.

01:19:04.160 --> 01:19:08.160
I wouldn't want you anyway.

01:19:08.160 --> 01:19:10.160
I wouldn't want you anyway.

01:19:10.160 --> 01:19:12.160
I wouldn't want you anyway.

01:19:12.160 --> 01:19:14.160
Stopped in lightning.

01:19:14.160 --> 01:19:16.160
Stopped in lightning.

01:19:16.160 --> 01:19:18.160
Stopped in lightning.

01:19:18.160 --> 01:19:20.160
I wouldn't want you anyway.

01:19:20.160 --> 01:19:22.160
I wouldn't want you anyway.

01:19:22.160 --> 01:19:24.160
I wouldn't want you anyway.

01:19:24.160 --> 01:19:26.160
Stopped in lightning.

01:19:26.160 --> 01:19:28.160
Stopped in lightning.

01:19:28.160 --> 01:19:30.160
I wouldn't want you anyway.

01:19:30.160 --> 01:19:32.160
I wouldn't want you anyway.

01:19:32.160 --> 01:19:34.160
I wouldn't want you anyway.

01:19:34.160 --> 01:19:35.160
I wouldn't want you anyway.

01:19:35.160 --> 01:19:36.160
I wouldn't want you anyway.

01:19:36.160 --> 01:19:58.280
I wouldn't want you anyway.

01:20:04.160 --> 01:20:34.140
Thank you.