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.660
in a fag pose, in your digital stance, getting firewalled hoes, cause I'm riding the net

00:20.660 --> 00:26.440
in 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, and 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 packed out Jones, and NASDAQ leaves you flat on your

00:58.140 --> 01:03.580
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:10.920
This is dedicated to the hackers and the crackers, serial phones, source codes, ISO, RAM, this,

01:11.160 --> 01:13.200
this, this, this, this, this, this, this, this, this, this, this, this, this, this, this,

01:13.200 --> 01:20.160
Hello and welcome to Binary Revolution Radio, episode 181, and today's date is January

01:20.160 --> 01:29.940
9th, 2007. I'm Black Ratchet. And I'm Not Theory. And I'm going to cruise in this evening.

01:30.500 --> 01:36.120
When's the last time you've been on? I think I was last on episode two.

01:38.920 --> 01:45.680
It was a long time, it's been a long time. I've been... I think you did one with Stank

01:45.680 --> 01:49.560
Doug, and then right before I took over, and that, that, that was the last time you were

01:49.560 --> 01:52.800
on, but I don't, I don't even remember how many shows I've been doing, so.

01:53.320 --> 01:57.140
Yeah, that sounds about right. I've been, I've been wrapped up in, in real life for a while.

01:58.100 --> 01:58.280
So.

01:59.780 --> 02:00.600
Damn real life.

02:00.820 --> 02:01.620
I know, it's the worst.

02:02.740 --> 02:03.060
Yeah.

02:05.580 --> 02:07.740
All right, I don't have any housekeeping. Do you have any housekeeping?

02:09.500 --> 02:12.240
Um, I wish I did, but I don't, so.

02:12.240 --> 02:16.300
Well, the only housekeeping I have is, like, you know, I need to clean up my room, because

02:16.300 --> 02:21.160
it's still a bit of shambles from Christmas. I have, like, all my stuff sitting around,

02:21.260 --> 02:21.920
and it's driving me nuts.

02:22.200 --> 02:24.600
Do you get any cool stuff for Christmas? Any cool geek stuff?

02:25.960 --> 02:29.700
I, I got a wireless weather station. That, that's my cool geek thing.

02:30.040 --> 02:33.080
Cool. Wireless, it's like a standard, or wireless, like Wi-Fi?

02:35.440 --> 02:39.720
Wireless, like, uh, it's, it, it, it, the, it has a sensor on the outside that picks up all

02:39.720 --> 02:43.240
the weather, and that's how it relays it back to my comfort of my own home.

02:43.300 --> 02:47.020
Ah, okay, okay. So it was one of those, like, ones that hooks up to the computer, and then

02:47.020 --> 02:48.040
does all kinds of craziness.

02:49.180 --> 02:55.080
That would be cool, and it, it, the thought has crossed my mind. However, it's like, 915

02:55.080 --> 02:58.220
megahertz, and I'm like, yeah, I'm never going to reverse engineer this.

02:58.280 --> 02:58.580
Oh, yeah.

02:59.260 --> 03:00.200
Yeah, radio is such a thing.

03:00.200 --> 03:01.680
I do not have the elite skills.

03:03.520 --> 03:03.840
Word.

03:03.840 --> 03:07.160
All right. How, did, are you getting anything good for Christmas?

03:07.360 --> 03:15.720
Um, well, Verizon gave me a PPC 6700, or, sorry, an XV 6700, uh, to replace the pre-dose.

03:16.040 --> 03:19.900
Yeah, I can't, can't have that PPC, you know, PPC has tethering in it. I can't have that.

03:20.360 --> 03:24.100
Tethering? Wait a second. Maybe I'm new. What exactly? Are you talking about, like, using

03:24.100 --> 03:24.620
it as a modem?

03:26.560 --> 03:26.880
Oh.

03:27.000 --> 03:27.160
Yeah.

03:27.320 --> 03:31.580
Okay. Uh, you know, you can do that on this phone, too. You just have to, you know, break

03:31.580 --> 03:36.040
it in terms of service and all kinds of stuff. Yes, the Ryzen really sucks. I understand

03:36.040 --> 03:41.500
that. Uh, but, I actually get service in places, which is nice, and when I had Sprint, I didn't.

03:43.200 --> 03:48.020
So, even though Sprint has the same phone, and the wireless plan is $15 a month, and you

03:48.020 --> 03:52.580
can use it as a modem, uh, if I can't use it anywhere, I'm spending $15 a month for a

03:52.580 --> 03:52.780
modem.

03:55.920 --> 03:56.600
That's very true.

03:56.820 --> 04:00.400
But, uh, yeah, I like it. It's, uh, it's good so far. It's better than the Trio. It's

04:00.400 --> 04:05.660
faster. Uh, the keyboard's not as nice, but the screen is a little bit bigger. It seems

04:05.660 --> 04:09.800
like if Bluetooth works a little bit better. The camera is definitely better, and it has

04:09.800 --> 04:10.200
Wi-Fi.

04:12.320 --> 04:12.680
Yeah.

04:12.820 --> 04:13.160
Ooh.

04:13.760 --> 04:13.960
And?

04:14.720 --> 04:15.800
Trio doesn't have Wi-Fi?

04:17.460 --> 04:19.280
You can get a Wi-Fi card for it.

04:19.400 --> 04:20.080
I wasn't aware, though.

04:20.080 --> 04:24.260
It has to take up the SD slot, which then means that you can't use a memory card, because

04:24.260 --> 04:28.820
they've discontinued the combination memory card, Wi-Fi. So.

04:28.820 --> 04:31.700
No matter what you do with the Trio, you're screwed.

04:33.980 --> 04:34.920
I'm just not a fan.

04:35.960 --> 04:36.280
Yeah.

04:36.400 --> 04:37.080
Which is why you dropped it.

04:37.080 --> 04:40.760
I have so many problems with it, and finally, um, if you, if you bitch at them enough, and

04:40.760 --> 04:43.660
you tell them that you've had a lot of problems, and you've been a customer for a long time,

04:43.720 --> 04:47.400
and just go on and on and on, eventually they'll say, okay, we can swap it. Which they should

04:47.400 --> 04:53.960
do, because for whatever reason, the 6700 is $100 cheaper than the Trio, even though it's

04:53.960 --> 05:01.680
faster, and looks better, and works better, and has Wi-Fi, um, it's still cheaper. I don't

05:01.680 --> 05:06.500
get it. But, what the hell do I know? So, in any case, that was.

05:08.180 --> 05:12.180
Well, it doesn't have the, it hasn't, it hasn't, it's, A, it's not a Trio, and B, it doesn't

05:12.180 --> 05:17.620
have the, the ultra cool, you know, one-handed dialing thing, which all the Trio users like

05:17.620 --> 05:25.340
to tell, saying, oh, I can dial mine with one hand. Um, okay, yeah, and? Yeah, I can

05:25.340 --> 05:29.600
do two on mine, when I have the MDA, which is more or less, I think, the same form factor.

05:29.920 --> 05:35.880
I mean, size-wise, I mean, not the form factor, but, I mean, I can take it out, and I dial

05:35.880 --> 05:39.260
with one hand with my thumb, you just have to make sure you tap the buttons, and you've

05:39.260 --> 05:43.720
got to be careful, and you've got to hit it with your phone, your finger, your fingernail.

05:43.720 --> 05:48.280
Dialing straight-up numbers on my Trio, people said it was so easy, it's, I mean, it's, it's

05:48.280 --> 05:51.540
just the same as dialing on the screen, to me, it's just a pain in the ass, I don't like

05:51.540 --> 05:57.520
it, and I have everybody in my phone book anyway, so it doesn't really matter. So, so,

05:57.720 --> 05:58.520
blah to them.

06:01.960 --> 06:04.360
I just like voice-assisted dialing, that's good.

06:04.600 --> 06:09.900
I bought myself a, and I thought that voice-assisted dialing was the stupidest thing ever, but I

06:09.900 --> 06:13.540
programmed it once or twice, and, you know, it's, it's kind of convenient, I'm sitting

06:13.540 --> 06:18.140
in the car, and I can tap the button, and leave my phone on the floor, or on the windowsill,

06:18.240 --> 06:23.060
or, you know, wherever the hell I want, and, you know, I don't have to do anything, just

06:23.060 --> 06:25.800
calls, but calls a number for me, it lets me be fat and lazy, I love it.

06:29.760 --> 06:35.320
I, I have a Bluetooth headset, which I'll, technically, I still have one, and the audio

06:35.320 --> 06:38.960
is so low on it, I can't use it with my cell phone, it drives me, I was, like, really

06:38.960 --> 06:43.020
pissed off, because I said, oh, it has Bluetooth, and I already have a headset that I, I got

06:43.020 --> 06:48.960
for my PVA, because, I don't know, I just had money to burn, and I was like, oh, I'll

06:48.960 --> 06:53.260
set it up, and I'll use it, and I was like, oh, man, I can, I mean, I left myself a voicemail

06:53.260 --> 06:56.160
message, and I'm like, I can't hear my cell phone, this damn thing.

06:56.180 --> 07:02.160
Yeah, I had a lot of bad luck with, uh, with headsets, I, I had a really good one, um, maybe

07:02.160 --> 07:08.160
a year or two ago, it was Bluetooth, and it had caller ID on the headset, so if you had

07:08.160 --> 07:11.240
it laying on the desk, you could just pick it up and see what it was, even if your phone

07:11.240 --> 07:14.920
was in your bag, and I used it all the time, and I loved it, and I went out to a bar one

07:14.920 --> 07:18.960
night, and somebody bumped into me and smashed the whole thing, it was in my front pocket,

07:19.380 --> 07:24.100
and just crushed it, it was still usable, but it had no more display, and it didn't charge

07:24.100 --> 07:28.140
right anymore, and it started doing weird stuff, so I chucked it, um, and didn't care

07:28.140 --> 07:30.900
about it, but then when I got this new phone, I was like, all right, I'm going to get a Bluetooth

07:30.900 --> 07:36.320
headset, and let me tell you, I got a Plantronics headset, because it said something about

07:36.320 --> 07:42.120
15 hours talk time, and you could use, like, a AAA battery, or whatever, and I had rechargeable

07:42.120 --> 07:45.540
AAA, so I was like, all right, this is great, I can just pop a AAA in it, and just keep a

07:45.540 --> 07:49.000
couple around, and I don't have to worry about charging it if I'm on the road, because I

07:49.000 --> 07:55.360
was on the road all the time, um, maybe two months ago, so I get the thing, and I open

07:55.360 --> 08:00.100
it up, yeah, you can use a AAA battery to recharge it with this other weird thing that attaches

08:00.100 --> 08:04.200
to it, but you're still, you still can't use it, you know, when the battery's dead, you can't

08:04.200 --> 08:07.260
replace it with the AAA battery, so I was like, all right, this is stupid, and it sounds

08:07.260 --> 08:12.840
like shit, let me return it, so then I got a Motorola one that was half the price, and

08:12.840 --> 08:17.680
everybody said that it sounded like shit, so I was like, all right, so I took that one

08:17.680 --> 08:22.060
back, and then I got a Jabra one, which is the people who made my original caller ID

08:22.060 --> 08:28.000
headset, I got that one, which was half the price of the Motorola one, which is now a quarter

08:28.000 --> 08:33.160
of the price of the Plantronics one, and it seems to work fine, nobody's complained

08:33.160 --> 08:37.020
about it yet, I'm talking on it now, maybe if it sucks, then I'll go back to the store

08:37.020 --> 08:41.500
and return it again, but so far, it's been good enough where people haven't been complaining,

08:41.760 --> 08:45.260
and the battery life has been long enough where I don't have to worry about getting cut

08:45.260 --> 08:47.260
off, so hopefully those things will hold up tonight.

08:51.220 --> 09:00.080
I've got to say, it sounds pretty good to me, so, yeah, I don't know, yeah, who knows

09:00.080 --> 09:03.940
what's going on, that could be Bluetooth, it could be the VoIP connection, it could be

09:03.940 --> 09:12.540
GSM to CDMA to ULAW, and it could be the lame-ass Bell's Mind server, who knows?

09:12.540 --> 09:24.200
From Bluetooth to CDMA to Bell's Mind to, I don't know, what the hell you're on, you're on some

09:24.200 --> 09:34.300
kind of VoIP, probably? Yeah, I'm going, you're going Bell's Mind to new phone, to my computer

09:34.300 --> 09:39.320
at home, to my Cisco phone. I think that, I think that path is all ULAW.

09:39.380 --> 09:44.040
Well, we don't have a big round trip, because the, the phone company that I'm using is, like,

09:44.740 --> 09:49.980
you know, 1,500 miles, maybe 1,000 miles away from where my server is, so you've got round

09:49.980 --> 09:56.080
trip time to and from there twice. So, in any case, it's, it's a long route that this

09:56.080 --> 09:58.880
call is taking, so it's surprising that it's actually working at all.

10:03.920 --> 10:06.920
Hey, you never know, we could, like, bounce it off a few satellites or something. We could

10:06.920 --> 10:10.880
have, like, that scene in sneakers where they're, like, routing it through, like, 15 billion

10:10.880 --> 10:14.920
points, and we could have the really cool, really cool graphic of, like, the voice going

10:14.920 --> 10:19.780
back and forth. I was reading Winamp, and it's got all those, like, Melsa video channels,

10:19.880 --> 10:24.820
and I still think it's done, so I flipped it on, and it was that scene, where he's like,

10:24.900 --> 10:28.980
Bishop, Bishop, they've almost got us, you know, they've almost got us, hang up, hang

10:28.980 --> 10:34.280
up. I'm like, dude, this is the dumbest thing ever. Like, the blind guy is staring at the

10:34.280 --> 10:39.140
screen, seeing where the call trace is going through. It's just ridiculous.

10:39.140 --> 10:48.220
Well, you can listen to the South, I gotta say, that movie rocked. It still does. I

10:48.220 --> 10:52.040
mean, you, you look at it today, and it's, it's pure teeth, but at the same point, you

10:52.040 --> 10:54.700
look at it and go, man, that was a cool movie.

10:55.580 --> 11:01.760
Really, really, really pissed me off. It was just dumb. However, I gotta say, that, uh,

11:02.160 --> 11:03.560
man, what was that guy's name?

11:04.180 --> 11:06.080
Whistler? Blind guy? Yeah.

11:06.080 --> 11:09.140
His Braille terminal was the most badass thing I've ever seen.

11:09.140 --> 11:09.460
Whistler?

11:10.600 --> 11:11.880
I don't know if you remember that part.

11:15.140 --> 11:18.960
I actually know someone who has used one of those before, so.

11:22.120 --> 11:22.520
Okay.

11:23.600 --> 11:30.160
No, he's blind. He has to use one. Of course, that now uses text-to-speech, but he used to

11:30.160 --> 11:30.560
use one.

11:30.600 --> 11:31.120
Maybe he was.

11:31.120 --> 11:33.040
He actually used to work for the telephone company, so.

11:33.740 --> 11:33.980
Ooh.

11:33.980 --> 11:34.100
Ooh.

11:34.420 --> 11:35.220
Anyway, so.

11:37.160 --> 11:37.520
Yeah.

11:39.440 --> 11:44.860
Well, wasn't, wasn't, wasn't Joe Ingressia the, the, the inspiration for Whistler?

11:46.720 --> 11:50.920
Yeah, I think that was one of, one of the blind phone freaks. Of course, this man is also

11:50.920 --> 11:54.280
a blind phone freak, but I don't think he was the inspiration. So, who knows?

11:54.460 --> 11:59.480
I guess, uh, I don't know how we got on the topic of, well, I guess I do know how we got

11:59.480 --> 12:06.920
on the topic of sneakers, but in any case, headset is cool. Um, but like I said, I returned it

12:06.920 --> 12:11.800
a bunch of times and now I'm having problems. I'm trying to get a video camera, not a video

12:11.800 --> 12:18.440
camera, but like a webcam working with a microphone, USB on Windows. It's just not working for me.

12:18.440 --> 12:23.000
I've, I've, I've been through probably five of them now and every single one of them has

12:23.000 --> 12:28.920
a problem. Either the video's crappy or the audio's crappy. And the audio's crappy in almost

12:28.920 --> 12:33.220
the exact same way every time, even if it's a different manufacturer. So, I don't know

12:33.220 --> 12:37.100
what's going on. And on two different computers by two different manufacturers. However, on

12:37.100 --> 12:51.340
my, my, my, my father-in-law has been having an issue with his webcam and I, I, I think it's

12:51.340 --> 12:55.480
an issue with his computer. And I, I, I don't know if it's a physical hardware issue or something

12:55.480 --> 12:59.760
that's just really followed up in Windows, but when he starts chatting online with his

12:59.760 --> 13:05.160
video webcam conferencing software, which is, I think, I think he's in whatever they call

13:05.160 --> 13:11.620
Microsoft Messenger these days. Windows, Live, MSN, Messenger, Mobile. They keep on tacking

13:11.620 --> 13:16.620
new names onto it. I don't know what it does anymore. But, um, his processor overheats and

13:16.620 --> 13:20.560
it eventually shuts down. And I'm curious if there's something, you know, taxing the processor.

13:20.760 --> 13:22.680
There's something like seriously wrong with his fan.

13:24.460 --> 13:28.420
Oh, okay. You know, I've noticed that there's a creative something.

13:29.000 --> 13:33.880
The video is really crappy, but the video seems to always work at least. And it, it didn't

13:33.880 --> 13:37.680
have a microphone on it, so that wasn't a problem. But the Logitech ones, I could see

13:37.680 --> 13:45.800
the processor overheating because just capturing the video on my laptop, it takes like 60% of

13:45.800 --> 13:51.780
the CPU. And it's not like my laptop is all that great. It's like a 1.8 gigahertz, uh, uh,

13:51.780 --> 13:52.480
Holy crap.

13:53.160 --> 13:58.580
But, no. No, I'm just saying it's not like some, some...

13:58.580 --> 14:00.400
Oh, geez. You know, it's trash. Throw it out.

14:00.400 --> 14:03.300
Oh, some kind of crap. Um, okay.

14:05.940 --> 14:07.300
Uh, you know...

14:07.300 --> 14:09.900
Go take it down in Las Vegas and go film yourself destroying it.

14:10.020 --> 14:11.060
...might free me to that point.

14:11.620 --> 14:13.940
Uh, no, I don't think I'm going to do that again.

14:14.560 --> 14:15.300
I think...

14:15.300 --> 14:23.480
Actually, here's the question, you know, since, since, since you, you're, you're frustrated

14:23.480 --> 14:27.740
at the trio, is, is it intact? Is it, has it been broken off into 10 different pieces?

14:27.740 --> 14:30.100
I don't know how to answer that. I, I, I...

14:30.100 --> 14:34.420
Okay. Um, I had some...

14:34.420 --> 14:38.700
No, no, no, no, no, no.

14:39.120 --> 14:41.820
Or how's the anger management classes, uh, actually worked?

14:41.820 --> 14:47.060
The first couple of trios I had, um, one just stopped working entirely. It kept telling

14:47.060 --> 14:52.720
me it was flight mode. Uh, it turns out that it had lost the, uh, the programming that tells

14:52.720 --> 14:56.060
it my cell phone number, so it kept connecting to the network, disconnecting, and whatever.

14:56.060 --> 15:01.380
Verizon replaced it. Um, the next one had Bluetooth problems, the next one had Bluetooth problems,

15:01.380 --> 15:09.780
but in between, there was one that, uh, met with an untimely demise. So, I was trying, I

15:09.780 --> 15:15.300
was, I had lost a whole bunch of money, so hardware that I bought from my business had

15:15.300 --> 15:20.980
gone sour, and the warranty had just run out, like, the month before. Um, and everything

15:20.980 --> 15:25.960
that I had at the time was on it, because of a million other factors. I had backups and

15:25.960 --> 15:30.480
all that, but it's just frustrating, because I had to go down to this colo and spend all

15:30.480 --> 15:34.300
kinds of time there and fix things and rent new machines. It was a mess, so I was pissed

15:34.300 --> 15:37.760
off, and I figured, I was, I just got off the phone with somebody.

15:41.280 --> 15:46.960
And you saw the trio standing there, and it was, like, looking at you the bad way, and

15:46.960 --> 15:49.260
you're, like, you little shit, you're going to be destroyed.

15:49.340 --> 15:52.400
I just got off the phone with somebody. I was furious. They had, you know, it was completely

15:52.400 --> 15:57.500
unrelated, but they had just totally ruined my day with something else, and I took my phone,

15:57.500 --> 16:04.440
and I went to throw it into this couch that I have, and at the last second, I don't know

16:04.440 --> 16:09.840
what came over me. I was, like, no, fuck this. It's gone straight to the wall, and it just

16:09.840 --> 16:21.400
exploded everywhere. So, I lost the one gig memory card. I can't find it at all. But I

16:21.400 --> 16:24.980
didn't have insurance on the thing, and I was, you know, milliseconds away from returning

16:24.980 --> 16:31.440
it anyway. So, I was, like, all right, I'll learn my lesson. I'll pay the $50, and I'll

16:31.440 --> 16:34.860
get a new one, and I'll have them replace that with, so.

16:37.980 --> 16:38.820
Oh, I dropped it.

16:39.040 --> 16:42.160
So, how did you explain this to the insurance company?

16:42.240 --> 16:44.600
I dropped it into the wall very quickly without the incentive of gravity.

16:44.740 --> 16:44.920
Oh.

16:47.740 --> 16:52.480
I mean, they don't need to know that gravity is not a part.

16:52.480 --> 16:52.980
Not serious.

16:53.320 --> 16:53.680
Smash.

16:53.680 --> 16:54.720
Drop it.

16:54.800 --> 16:55.440
I let go of it.

16:56.540 --> 16:58.360
No, I don't stand by this.

16:59.360 --> 17:05.600
I guess not, but I don't know. Most people drop it from, like, a, most people drop it

17:05.600 --> 17:10.020
from, like, a, a, a, a, like, you know, five feet, six feet. You probably look like you

17:10.020 --> 17:11.660
dropped it off a 12-story building.

17:11.840 --> 17:15.760
Faster than terminal velocity for a trio. I don't know what that is, but I'd really like to find

17:15.760 --> 17:19.700
out what it is. I'm sure that this device was going faster than that. So, the only way

17:19.700 --> 17:25.200
I could say that I dropped this is if I put some type of aerodynamic, you know, casing

17:25.200 --> 17:27.760
around it and dropped it while I was skydiving.

17:29.860 --> 17:30.620
Not to an aerodynamic.

17:30.620 --> 17:35.060
Which could be possible. But, like I said, it was in my hand. I let go of it.

17:35.060 --> 17:36.240
Which could be possible.

17:36.760 --> 17:39.920
So, it's just not my fault.

17:39.920 --> 17:49.820
Here I was actually thinking, you know, oh, it's a trio is expensive. He's not, he's not,

17:49.920 --> 17:55.020
he's not going to hurl this at anything. Oh, no, no. He just got really angry one day and

17:55.020 --> 17:59.960
decided to throw it into a wall, you know, $400 piece of equipment.

18:00.060 --> 18:01.820
No, I'm, I'm actually fairly good with it.

18:01.820 --> 18:03.940
Remind me never to let you use my laptop, okay?

18:04.080 --> 18:09.220
If it's mine, I can deal with it if I smash it. No big deal. But, like I said, I had just

18:09.220 --> 18:13.740
lost, like, thousands of dollars and I was just, there was nothing I could do about it.

18:13.780 --> 18:20.540
I was also 150 miles away from the colo and I was just totally miserable. Everything was

18:20.540 --> 18:26.760
going wrong that day. So, I had to get a leak. Yeah, exactly. Like I said, had I, had I just

18:26.760 --> 18:31.980
thought at the last time, you know what, now it's no big deal, it'll be fine. But, I decided

18:31.980 --> 18:36.380
it's going to meet the wall or the floor. I was actually just, I threw it so hard, I don't

18:36.380 --> 18:40.220
even know where it hit. It had these weird, like, red marks on it and I looked around

18:40.220 --> 18:44.840
and I'm like, well, the wall's not red and the floor's not red. So, what the hell is

18:44.840 --> 18:51.380
this? So, yeah, the trio will bleed.

18:51.780 --> 18:53.200
You made it bleed.

18:58.380 --> 18:59.520
The streets will...

18:59.520 --> 19:02.820
You can't get blood from a strone, but you can get blood from a trio, just so you all

19:02.820 --> 19:03.000
know.

19:04.520 --> 19:10.020
So, anyway. So, yes. I have to admit, I did smash my device. I was so good. I didn't smash

19:10.020 --> 19:12.060
that thing for a year. Come on. You've got to give that to me.

19:19.560 --> 19:26.140
I'm still ticked off about, you know, for those of you who don't know, not theory-owned a sidekick,

19:26.140 --> 19:29.800
which we actually will cover in this show, because the topic is smartphones and stuff

19:29.800 --> 19:35.520
like that. So, we'll let not theory go flip out on the sidekick for us. And I had a sidekick

19:35.520 --> 19:40.700
one and he bought a sidekick two. And I was like, oh, okay, well, sidekick two, that's

19:40.700 --> 19:44.020
pretty cool. You know, when I initially asked him about it, he said, oh, it was pretty good.

19:44.340 --> 19:48.960
And then he ran into some issues with it. And I ran into a lot of issues. And not very much

19:48.960 --> 19:54.920
with the phone, more like the phones, the political side of using the phone. Am I correct

19:54.920 --> 20:05.660
in this? Yeah. So, not even the phone had an issue on it. It was just not theory being

20:05.660 --> 20:12.420
frustrated with the company who was in charge of software development. So, I'm talking to

20:12.420 --> 20:16.380
him one day. He said, oh, yeah, well, you know, I got rid of the sidekick. Oh, what

20:16.380 --> 20:20.200
happened? And he explained it to me. He said, yeah, so I got really frustrated one day and

20:20.200 --> 20:24.020
I just decided to throw it in the wall and the screen smashed. And I was like, you're

20:24.020 --> 20:29.200
not, you just wanted to get rid of it. So, you threw it against the wall. Yeah. I could

20:29.200 --> 20:31.180
have really used that. Oh, sorry, man.

20:37.180 --> 20:42.340
I didn't mind the sidekick two. I mean, initially I decided to grow up and, you know, actually

20:42.340 --> 20:47.300
get something that was not designed for the Paris Hilton crowd. But I mean, that could have

20:47.300 --> 20:51.240
got me a sidekick two about a year early and I probably could have lost it like I lost

20:51.240 --> 20:57.120
mine three months later. But nothing I can do about it now. Hey, I told you then, you

20:57.120 --> 21:05.220
knew then that I hated that phone and I made like no bones about what I hated and why. So,

21:05.740 --> 21:06.720
can't say I didn't warn you.

21:06.720 --> 21:21.620
And for those of you who haven't seen the opening to, what is it, Hack TV 2? Yeah, Hack TV 2,

21:21.760 --> 21:27.660
if you look at the opening sequence, you'll see Natus using a phone and typing on it and

21:27.660 --> 21:31.480
then you suddenly see Not Theory just come up to him and throw it out of his hand. And that

21:31.480 --> 21:36.720
is a sidekick two. Oh, yeah. It was great. It was, it was thoroughly destroyed after

21:36.720 --> 21:40.100
that. Oh, no. I got my, I got my use out of it. It was, it was good for a while, but

21:40.100 --> 21:45.720
my big problem was danger. Maybe we can talk about this later, but, but I don't know. I'm

21:45.720 --> 21:51.300
pretty happy. Yeah. I'm pretty happy with 600, 700 now. Yeah. I think we shouldn't do

21:51.300 --> 21:56.540
that. Let me think. What else? Oh, the last thing that I got for Christmas that I will not

21:56.540 --> 22:06.240
be smashing is a Wi-Fi camera, which is pretty cool. Yeah, the Nikon Coolpix P3. It's an

22:06.240 --> 22:12.480
8.1 megapixel Wi-Fi camera. So, there's basically just this little piece of software you install

22:12.480 --> 22:16.580
on Windows and you set up an ad hoc network and as you're taking pictures, you can transfer

22:16.580 --> 22:20.820
them right to your PC. Now, there's a bunch of DSLR cameras that already have this type

22:20.820 --> 22:26.720
feature, but this is the first consumer model that, that has it. And I'm in the process

22:26.720 --> 22:32.200
right now of trying to reverse engineer their, their protocol so that I can write my own application

22:32.200 --> 22:36.540
that'll pull the pictures off of the camera. Because their software is okay, but it doesn't

22:36.540 --> 22:41.720
do exactly what I want. So, that's what, that's what I've been fiddling with recently. And I

22:41.720 --> 22:46.520
got to tell you, reverse engineering, reverse engineering is a lot of fun, but it's, it's

22:46.520 --> 22:51.060
not theory is hardcore. It's really difficult with this particular piece of hardware because

22:51.060 --> 22:56.160
it sends back so much data. You know, it sends back like a two megabyte picture with all kinds

22:56.160 --> 23:01.280
of crazy header information. It's going to take me a while to figure this out, but hopefully

23:01.280 --> 23:01.520
I will.

23:06.040 --> 23:11.120
I assume you fired up Ethereum or WiderShark, whatever they call it this week.

23:11.380 --> 23:12.600
Yeah, definitely. I fired up WiderShark.

23:12.600 --> 23:15.300
Got it, right? You know, sniffed the stream.

23:15.300 --> 23:19.180
A bunch of negotiation back and forth from the camera when it starts up, when it goes

23:19.180 --> 23:24.320
into a certain mode, when it's taking a picture, all of that stuff. So, I've got all the data

23:24.320 --> 23:27.740
there. It's just, you know, kind of plotting through it, plotting through a bunch of different

23:27.740 --> 23:33.300
scenarios and, and seeing which bytes change, which bytes don't change, and trying to figure

23:33.300 --> 23:37.040
out what's going on. Some people have tried to document the protocol, but I don't think

23:37.040 --> 23:40.940
it's the exact protocol that, that they advertise it as. I think it's kind of their own

23:40.940 --> 23:44.820
magical thing. But it doesn't look complicated.

23:46.020 --> 23:48.380
Yeah, exactly. My little pony protocol.

23:48.380 --> 23:50.580
It's a magical protocol with ponies.

23:50.580 --> 23:56.460
I don't know. I think it's, uh...

23:56.460 --> 23:58.520
MLPP colon slash slash.

24:04.020 --> 24:11.020
Is it like, so can you, like, pop the camera up someplace and, like, fire it over the 802.11,

24:11.180 --> 24:14.260
like, have it, like, take a picture and, like, tell it from your computer to take the picture?

24:14.260 --> 24:18.760
I won't stop, you know, I won't derail the show to do it now, but I'll, I'll kind of fiddle

24:18.760 --> 24:23.540
with it as we're talking, see if I can find that. I know that they do have control, uh,

24:23.540 --> 24:28.000
applications for this, for some of their cameras. I don't know that this camera supports it.

24:28.060 --> 24:33.420
They do have something, when you go into Wi-Fi mode, um, it's got a listing of all of the

24:33.420 --> 24:41.000
different types of, uh, types of, like, Wi-Fi sub-modes that it can go into. Um, and I think

24:41.000 --> 24:45.740
there's PC mode, shoot and transfer, which is when you take the picture and

24:45.740 --> 24:50.420
save it to the internal card, it transfers it to the computer. Or you can save it to the card

24:50.420 --> 24:57.160
and transfer it to the computer simultaneously. Um, and then I forget, oh, there's, like,

24:57.320 --> 25:01.940
transfer all pictures, transfer marked pictures. So as you're taking pictures, like, you can mark

25:01.940 --> 25:04.740
them and say, yeah, I want to transfer this to my laptop. And then instead of hooking, instead

25:04.740 --> 25:09.060
of, like, swapping the card out, if you don't have a reader, you can just, you know, pop the

25:09.060 --> 25:12.500
thing online, set up your AdHawk network, and just move all the pictures across. It's, it's

25:12.500 --> 25:18.680
kind of convenient, but if you've got a reader, you know, it's faster to, to use the, um, to

25:18.680 --> 25:22.660
use a, to just take the card out, pop at the reader, and then drag all the pictures. But

25:22.660 --> 25:23.020
it is.

25:27.540 --> 25:32.480
Yeah, because the, the bandwidth, the bandwidth for 8 or 2 to 11, whatever it is, I mean,

25:32.480 --> 25:35.860
even if you're talking about, like, G, it's, it's not as fast as the reader would be.

25:35.860 --> 25:40.220
G, but I imagine that the process, unless you have, like, USB one, is really not all

25:40.220 --> 25:45.800
that beefy. And when it, when it's taking control of, you know, the Wi-Fi hardware and trying

25:45.800 --> 25:50.080
to read off the card and negotiating this protocol, it's got to take some type of formative. So

25:50.080 --> 25:53.920
hooking it up with a USB cable or putting it into your reader is probably faster. What

25:53.920 --> 25:59.600
I found out, actually, is I have a, it takes SD, I got a 2 gigabyte mini SD for Christmas

25:59.600 --> 26:04.500
also that I put into this thing. But when I put the 2 gigabyte card in my laptop, it doesn't

26:04.500 --> 26:08.360
work. Because my laptop's reader, for some reason, just doesn't understand 2 gigabyte

26:08.360 --> 26:13.720
cards or something. However, in my 6700, it works, no problem. I put it in, it says, hey,

26:13.800 --> 26:16.060
it looks, it looks like you've got a bunch of pictures on here. Would you like to check

26:16.060 --> 26:18.720
them out? Would you like to email them to your friends? It's crazy.

26:18.720 --> 26:28.540
Yeah, that's the one thing I did not get for Christmas that I was actually, can I just

26:28.540 --> 26:30.340
point out, I did not get a mini SD card.

26:30.460 --> 26:32.660
You have the MDA, which MDA is supposed to?

26:33.660 --> 26:34.700
Some point in the future.

26:34.700 --> 26:48.620
The MDA, it's the HTC Wizard, which is the T-Mobile MDA, which is the, I don't know what it's

26:48.620 --> 26:54.780
called internationally. But HTC makes it, Wizard is the, not what it's called, but over here

26:54.780 --> 27:09.620
it's marketed as the MDA. Magician, I think? No, no, no, the 6700 is the Apache. Yeah,

27:09.640 --> 27:13.360
which I always found amusing, because I always wanted to run, like, I got a 6700, I wanted

27:13.360 --> 27:26.260
to run Apache on it. I think there's probably some, well, the PPC, the 6700 is also CDMA

27:26.260 --> 27:31.360
and mine's GSM, and I think the processor's beefier on it, and I think it might have some

27:31.360 --> 27:35.680
more storage, and the hardware's slightly different. But, I mean, more or less, all of

27:35.680 --> 27:40.360
the phones, they all have the, more or less, the same form factor, I mean, different buttons

27:40.360 --> 27:48.700
and such, but the, ah, crap, I don't know if the, the next step up from mine, which is

27:48.700 --> 27:53.420
the new, oh, Hermes, Hermes, that's what it's called, is the one that just got released by

27:53.420 --> 27:57.840
Singular. It's, essentially, it's my phone, except it has, like, a couple more buttons

27:57.840 --> 28:02.480
on it, and the processor speeds faster. And the keyboard layout is slightly different.

28:03.140 --> 28:07.980
But, I mean, using it, it's, like, almost identical to my phone. The keyboard flips out the

28:07.980 --> 28:15.260
same way, all the storage slots are the right one. Titan is, like, the latest, greatest new

28:15.260 --> 28:18.160
one, and I think the only, I don't know what the Titan is, I've never heard that one.

28:18.160 --> 28:23.240
I think it may have either the 416 megahertz processor, 417 megahertz processor that mine

28:23.240 --> 28:30.200
has, and it has a 2 megapixel camera as opposed to one, as opposed to one 3. Ah, man. Are we,

28:30.200 --> 28:33.860
are we getting onto the, the show topic already? Maybe we should save this.

28:38.780 --> 28:42.880
I think we kind of, like, kind of, like, both on there. So, let's go, oh, maybe it is the

28:42.880 --> 28:47.220
Titan. Maybe that is the one I'm thinking of. I, I think it's slightly different because

28:47.220 --> 28:54.220
the Titan is, um, has certain features that, um, the one, from, the one in Europe has certain

28:54.220 --> 28:58.480
features that the one in America doesn't have. Like, for example, it has a, you could use the,

28:58.480 --> 29:02.880
you could use a built-in camera to make video phones calls, and Singular apparently doesn't

29:02.880 --> 29:09.440
want you to do that, but. I can't wait to check them out overseas, see how much better

29:09.440 --> 29:21.040
they are. Yeah. All right. So, actually, let, let's take a pause here and read the email

29:21.040 --> 29:26.120
and take a, and we'll let everyone slobber go over for more with, uh, talking about smartphones

29:26.120 --> 29:29.660
and generally just a, sort of a conversation between Knot Theory and I.

29:45.720 --> 29:56.100
Um, our first email tonight is from VoltageX and it's, hi, host and co-host. Uh, any ideas,

29:56.100 --> 30:04.760
for what? 1-800-418-6264 is. Has to be one of the stranger numbers I called. Keep up the great

30:04.760 --> 30:09.580
work, VoltageX. And I gotta say, this is the first time I actually gotta, we gotta have an email

30:09.580 --> 30:16.880
asking us to identify a number. And, uh, something, something, like, right now, if, like, people are

30:16.880 --> 30:21.600
listening to the stream, if this one streams, I guess that's kind of housekeeping, uh, that we haven't

30:21.600 --> 30:26.540
been streaming over the past weeks because of the, uh, server issues. And last week we had

30:26.540 --> 30:32.640
a twofer of 179 and 180 being released almost at the same time. So, I'm gonna add this up

30:32.640 --> 30:35.440
and we're gonna try to put it on the stream this time. I'm not sure if the stream's working,

30:35.600 --> 30:42.040
but we'll find out tomorrow night because we're recording this on a Monday. But, um, did you

30:42.040 --> 30:49.060
actually call this number? Oh, okay. Well, I, I, I, I, everyone's probably calling it right

30:49.060 --> 30:55.160
now as they're listening. But, um, I, I think, I think the older generation, like, the old

30:55.160 --> 31:01.340
farts like you and myself will actually understand if we, if, if we hear this number. Because it

31:01.340 --> 31:06.560
says, enter your message and then it beeps three times. And for those of you who don't

31:06.560 --> 31:12.100
know what that kind of stuff is, it's a beeper number. It's a 800 number that goes to someone's

31:12.100 --> 31:15.880
beeper. So, you can essentially, if you want to talk to this person, just dial in your phone

31:15.880 --> 31:21.000
number and hit, hang up and you'll get a phone call relatively soon. Probably becomes some

31:21.000 --> 31:30.940
guy saying, who is this? Yeah. What's a beeper? I've never heard of a beeper. Why don't

31:30.940 --> 31:37.700
they just use a cell phone? Actually, the, the, um, I, the beeper, my friend and I, we

31:37.700 --> 31:44.440
were trying to figure out when beepers will actually come back as a retro craze. Because

31:44.440 --> 31:49.020
he actually, he has, he has a beeper for his work because he goes into certain areas that

31:49.020 --> 31:55.880
he can't carry a cell phone in for certain security reasons. He works for the government.

31:55.880 --> 32:01.980
We'll just, we'll just leave it at that. And, um, he has this beeper and like, for the

32:01.980 --> 32:05.260
longest time when he says, well, here's my beeper number and you can get to me if, you

32:05.260 --> 32:10.380
know, if you need to contact me at work and I'm not at my desk. And like he, he told me

32:10.380 --> 32:14.420
and two friends and we all basically just looked at each other and saying, okay, well, how

32:14.420 --> 32:18.600
do you use a beeper? Cause we forget. Like we couldn't, we couldn't remember if it was

32:18.600 --> 32:23.240
like, I actually remembered how to use it, but my friend just kept on calling the number

32:23.240 --> 32:30.200
and hanging up thinking it was going to grab his caller ID, but it didn't. Oh, that was

32:30.200 --> 32:33.820
cool. I was smart. I knew how to punch in the digits after the things beeps and then

32:33.820 --> 32:35.780
hang up and wait for the phone call. I'm leet.

32:38.580 --> 32:43.360
Actually, I got into a discussion with a younger guy a couple of months ago about beepers and

32:43.360 --> 32:47.920
he was like, dude, I've never known anybody who had a beeper. Why would you have a beeper?

32:47.920 --> 32:54.020
Like cell phones were super expensive back in the day. That's why. Not even the cool

32:54.020 --> 32:59.600
alphanumeric pagers. I'm talking like straight up just. Yeah. Like the, like the 12 digit

32:59.600 --> 33:06.900
LCD display with like eight segments or seven segments or whatever. Oh yeah. Yep.

33:07.540 --> 33:13.840
That's what I was actually, I remember when I first actually got like played with one,

33:13.840 --> 33:20.880
like my, um, uh, I had, I had a friend who was able to, who gave, let me borrow his for

33:20.880 --> 33:24.960
like a, like an hour or so to like, let me fiddle with it. And I thought it was the coolest

33:24.960 --> 33:29.040
thing ever because I could call a phone number and make it, and make it like do something.

33:29.600 --> 33:33.200
I think it was like 12 at the time. So I was easily impressed.

33:36.380 --> 33:40.740
Well, surprisingly, there still is a lot of pager traffic out there. Like doctors have them.

33:40.740 --> 33:43.920
And then like you said, your buddy at work has them and all that kind of stuff. If anybody's

33:43.920 --> 33:48.200
interested and you've got an old scanner lying around, you can build what's called an FSK

33:48.200 --> 33:53.140
decoder, a two level or a four level FSK decoder. It's a very simple schematic. You can hook

33:53.140 --> 33:57.680
it up to your scanner and you can plug it into some, uh, I think, trying to think what the

33:57.680 --> 34:01.680
software, I think the software might be called WinFlex because there's a couple of pager

34:01.680 --> 34:08.300
protocol standards. There's POCSAG, that's P-O-C-S-A-G, GO-L-A-Y, G-O-L-A-Y, and

34:08.300 --> 34:13.480
FLEX. And if you've got a four level FSK decoder, you can listen to all of them and you can

34:13.480 --> 34:19.500
hook that up and you will just have a crazy time watching all these doctors' pages like,

34:19.760 --> 34:23.900
you know, patient, you know, so-and-so has gone into labor, please come to the hospital

34:23.900 --> 34:27.940
or, you know, so-and-so has had a heart attack, all kinds of stuff like that you'll see.

34:28.380 --> 34:32.540
So if you got, if you got a couple of spare bucks for some parts and you're willing to do

34:32.540 --> 34:37.160
some soldering, look up FSK decoder, hook it up to your scanner and, uh, and screw around

34:37.160 --> 34:37.420
with it.

34:37.460 --> 34:42.240
Well, can I, like, say if I have a scanner and I have, like, a line out, can I just

34:42.240 --> 34:45.700
literally, like, you know, put a, plug that into my computer and have my computer do all

34:45.700 --> 34:46.560
the FSK decoding?

34:49.740 --> 34:55.480
No, the problem with that is the audio out from it goes through a little bit of, uh, special

34:55.480 --> 34:58.020
processing to make voice sound a little bit better.

34:58.020 --> 35:02.000
So it kind of mangles the signal that comes out, like this, and it's very important,

35:02.200 --> 35:03.740
phase shift of different things.

35:04.120 --> 35:06.480
It's very important to be able to do the FSK decoding properly.

35:06.840 --> 35:11.380
On some scanners, supposedly it works because they have what's called a discriminator output

35:11.380 --> 35:13.880
as opposed to just a straight audio output.

35:14.640 --> 35:18.260
But if your scanner doesn't have that, you can wire up a discriminator output.

35:18.360 --> 35:22.820
You can just Google whatever your model scanner is, discriminator output, and there'll be somebody

35:22.820 --> 35:24.960
who's got a page that describes how to do the model.

35:24.960 --> 35:30.880
But it's usually just one very simple, um, you know, solder a wire to this part and hook

35:30.880 --> 35:31.920
it up to your FSK decoder.

35:32.940 --> 35:36.420
Should be, I mean, even if you haven't soldered all that much before, um, if you're feeling

35:36.420 --> 35:38.380
a little adventurous and you're willing to void your warranty.

35:38.500 --> 35:41.860
I'd be willing to void my warranty and I'd be willing to crack my scanner open.

35:41.960 --> 35:46.120
However, I wouldn't be willing to risk losing my scanner because that would make me sad.

35:50.260 --> 35:50.580
Yeah.

35:50.880 --> 35:53.540
Well, there are also places that you can take your scanner and send it away.

35:53.540 --> 35:55.860
Yeah, of course, that'd probably cost like an arm and a leg.

35:56.640 --> 36:00.360
You know, I don't think it's that expensive.

36:00.540 --> 36:05.220
And you know what, honestly, if you have like some type of local ham radio group or something

36:05.220 --> 36:08.520
like that, if you bring your scanner there and you tell people, yeah, you know, I want

36:08.520 --> 36:12.960
to do some, you know, amateur radio work and I want to listen to these signals, they'll

36:12.960 --> 36:15.140
probably hook you up and say, oh, this is how you do it.

36:15.160 --> 36:16.360
Oh, let me show you how to do it.

36:16.720 --> 36:18.340
You know, all those old timers will get excited.

36:18.380 --> 36:20.900
Yeah, I want to own some pagers there, old dudes.

36:20.900 --> 36:21.660
Can you help me out?

36:21.660 --> 36:28.680
Oh, you've got to tell them that you want to listen to like, I don't know, some type

36:28.680 --> 36:33.280
of Ritty or Bordeaux or some other weird obscure protocol that's coming.

36:33.520 --> 36:34.540
Dude, Ritty's elite.

36:37.840 --> 36:39.700
Ritty is elite, I've got to say.

36:39.880 --> 36:40.540
It's pretty cool.

36:40.760 --> 36:45.280
Oh, well, I mean, just go on a complete tangent here as we're talking about ham radio buffs.

36:45.280 --> 36:46.220
Have you heard the news?

36:50.620 --> 36:55.100
No, ham radio has dropped the Morse code requirement for HF.

36:58.320 --> 37:00.340
Oh, you know, I did hear that from someone.

37:00.420 --> 37:01.140
So what does that mean?

37:01.200 --> 37:08.440
That my old technician no code that then became like some kind of worthless?

37:08.440 --> 37:14.840
Oh, yeah, your previously worthless for HF no code license now entitles you to HF privileges.

37:18.060 --> 37:19.300
Now, does that mean I'm a technician or a general class?

37:19.300 --> 37:20.100
You're a technician.

37:20.300 --> 37:20.840
You're not general.

37:20.840 --> 37:27.220
So technically, you know how tech, for those of you who don't remember, listen to our ham

37:27.220 --> 37:29.380
radio episode with myself and not theory.

37:30.640 --> 37:33.040
I don't know when it was, but just look at the archives.

37:33.960 --> 37:40.840
And no code techs now have the same privileges as what was then just a pure technician class.

37:40.980 --> 37:43.040
So we can now operate on HF.

37:43.120 --> 37:50.080
I don't think we can operate yet, but they've released the bureaucratic processes.

37:50.080 --> 37:53.540
They say, we're going to go drop this requirement, get ready for it.

37:53.560 --> 37:56.060
And then they say, like, 30 days later, okay, the requirement's dropped.

37:56.120 --> 37:56.880
You can do this now.

37:57.560 --> 37:59.920
And I don't know why they do that, but.

38:03.200 --> 38:11.020
Yeah, see, when I did my license initially, there was novice, no code tech, tech plus, general, amateur, and extra.

38:11.480 --> 38:16.220
And then they dropped tech plus and then made it, I thought, novice, technician,

38:16.460 --> 38:18.420
and then anybody who was tech plus became general.

38:18.420 --> 38:19.880
No, I don't think that's how it happened.

38:21.080 --> 38:22.160
I think you're wrong.

38:22.600 --> 38:23.560
No, I think they dropped.

38:25.680 --> 38:27.220
I could be wrong.

38:27.300 --> 38:29.480
It's been like, I don't know, six years.

38:29.540 --> 38:34.280
I actually sort of fell back into it about, oh, six months ago,

38:34.380 --> 38:37.700
and then all of a sudden the antenna got ripped off my car.

38:38.260 --> 38:41.440
So that kind of dropped that right in the tracks.

38:41.440 --> 38:45.380
But I think as it's, I don't know.

38:45.580 --> 38:48.260
But if you, you know, get an amateur radio, it's cool.

38:48.480 --> 38:49.420
Just leave it at that.

38:49.840 --> 38:51.080
Listen to our, listen to.

38:52.340 --> 38:53.320
Oh, I want to hear this.

38:53.320 --> 38:57.240
Oh, I was driving, where was I driving?

38:57.340 --> 39:02.900
I was driving, no, I was driving to the Walmart parking lot in Dartmouth, Massachusetts.

39:02.900 --> 39:08.480
And I was driving along, and there was a low tree.

39:08.480 --> 39:12.360
And I heard my antenna scrape across it, and it just sounded funny.

39:12.480 --> 39:14.060
And I just thought it just scraped across it.

39:14.500 --> 39:19.100
And then I look when I get home, I just, you know, I think it was like the next day,

39:19.160 --> 39:23.240
I come out to my car, and the bag mounts there, but not the antenna.

39:23.240 --> 39:24.820
It got ripped out.

39:27.320 --> 39:29.000
Yeah, I was like, oh, man.

39:30.920 --> 39:35.680
And actually, I think this was, well, probably at least six, maybe even nine months ago.

39:36.560 --> 39:40.100
And I haven't taken the mag mount off by car.

39:40.200 --> 39:40.880
It's just sitting there.

39:40.980 --> 39:41.880
It looks cool, whatever.

39:43.860 --> 39:47.180
I'll go break down a coat hanger, bend it out, make it to the proper wavelengths,

39:47.340 --> 39:48.600
jam it in there, we'll be all set.

39:48.600 --> 39:54.600
Yeah, I'm insane.

40:00.940 --> 40:02.060
I'm Decoder Jr.

40:06.640 --> 40:07.400
Chats Decoder.

40:07.760 --> 40:10.120
I'm not even going to attempt to put myself up on that pedestal.

40:13.000 --> 40:15.860
So our next email is from Anonymous, and this is a long one,

40:15.920 --> 40:17.200
so I'm going to stumble through this one.

40:17.200 --> 40:20.420
I heard another listener bring up GUIDs again.

40:20.760 --> 40:23.880
I was the first guy to write in this using them in MySQL.

40:24.340 --> 40:27.040
GUIDs are called UUIDs in Unix environments.

40:27.680 --> 40:31.800
I probably should have mentioned that or just asked about 16-byte integers to avoid confusing.

40:32.700 --> 40:38.220
As for the Windows registry, classes are represented by GUIDs, not necessarily programs.

40:39.000 --> 40:43.780
The purpose of GUIDs is to uniquely identify something with sufficient assurance

40:43.780 --> 40:46.480
that unintentional collisions will not occur, ever.

40:46.480 --> 40:54.480
Second Life likely chose GUIDs to identify objects because they can rest assured that they will never run out of them

40:54.480 --> 41:01.260
and very likely never generate the same one twice, assuming the rules are followed for generating them.

41:01.520 --> 41:10.180
In times long past, UUIDs slash GUIDs were generated based in part on the MAC address of the computer and the date and time.

41:10.180 --> 41:13.980
People didn't trust computers to reliably generate random data.

41:14.360 --> 41:19.360
As technology advanced, computers began to have multiple MAC addresses or share MAC addresses in clusters,

41:19.860 --> 41:25.160
and were becoming capable of generating strong pseudo-random data to use in GUIDs.

41:25.300 --> 41:29.180
The current rules are to use pseudo-random number generators and generate GUIDs.

41:29.180 --> 41:40.100
UUIDs are certainly not new, and the general idea of whereas sequential primary keys must be generated or verified by a single central entity to avoid duplicates.

41:40.660 --> 41:52.760
UUIDs have sufficient entropy to be assumed unique regardless of where they were created so long as they were created following the rules.

41:52.760 --> 42:04.260
Also, from what I understand, if you throw enough money at MySQL, it can handle unimaginable amounts of use.

42:04.680 --> 42:06.040
And Second Life is liquid money.

42:06.140 --> 42:08.640
They virtually have no cost in our pure profit.

42:08.640 --> 42:13.280
At heart, a GUID slash UUID is really only 16 unique bytes.

42:13.480 --> 42:24.380
In Windows, this is commonly expressed by an opening brace, curly brace that is, 8-4-4-4-4-12 hexadecimal characters.

42:24.820 --> 42:25.600
Closing brace.

42:26.220 --> 42:30.640
Storing hexadecimal characters as a plain ASCII in a car 66...

42:30.640 --> 42:31.820
Is that car?

42:31.900 --> 42:32.800
I don't know how you pronounce that.

42:32.880 --> 42:33.600
Char or car?

42:33.680 --> 42:34.820
I always had a problem with that.

42:35.580 --> 42:36.840
Char 36...

42:36.840 --> 42:37.100
Hmm?

42:37.100 --> 42:37.160
Hmm?

42:38.640 --> 42:40.140
Char, okay.

42:40.280 --> 42:41.020
I think it's car.

42:41.600 --> 42:42.140
Sorry, I was right.

42:42.600 --> 42:44.660
Car 36 column is sloppy at best.

42:44.820 --> 42:49.500
Car 36 sounds like hyphens and braces are being stored in the column as characters.

42:49.940 --> 42:53.500
That's like storing date times by converting them to a string and saving them to a column.

42:53.620 --> 42:56.360
It's just not efficient, especially not for a primary key.

42:57.460 --> 43:01.100
It is good database practice to keep primary keys as concise as possible.

43:01.100 --> 43:05.400
If a GUID is 128 bits or 16 bytes and a byte is the same thing as a char,

43:05.400 --> 43:08.800
then it should be accurately represented in a char 16 field.

43:09.260 --> 43:13.080
It's not good practice to use a char as a primary key, so I didn't want to do that.

43:13.380 --> 43:16.700
If my memory served me right, my SQL also pitched a fit when I tried to.

43:17.440 --> 43:22.140
Even without assigning a primary key to a column, it merely displaying it in the terminal would scroll up the terminal,

43:22.140 --> 43:25.700
because it would literally be trying to print control characters,

43:25.700 --> 43:28.260
and that made DB maintenance a pain in the butt.

43:30.060 --> 43:33.420
The project I was working on was eventually canceled,

43:33.700 --> 43:39.840
but had it continued, I would have used an 8-byte integer column in lieu of a car route.

43:41.480 --> 43:42.160
Car route.

43:42.160 --> 43:49.160
It's a shame that to use MySQL, I'd have to sacrifice half the entropy of the primary keys, though.

43:49.560 --> 43:53.620
What do other people do when they use unique identifiers that can be generated disparately

43:53.620 --> 43:55.460
or merge into a central MySQL table?

43:55.660 --> 43:57.440
This cannot be a new problem.

43:58.000 --> 44:00.360
By the way, it just occurred to me that in the near future,

44:00.420 --> 44:03.780
we're going to have a new name to call these GUIDs or UUIDs.

44:03.780 --> 44:04.620
IP addresses.

44:04.860 --> 44:09.220
IPv6 addresses are, in fact, 16 bytes long.

44:10.280 --> 44:10.520
Whew.

44:11.100 --> 44:11.400
Boy.

44:12.640 --> 44:13.460
Yeah, I know.

44:13.560 --> 44:15.340
Seriously, people are writing, like, epic letters.

44:15.480 --> 44:19.560
I mean, not to discourage them, but, man, I'm just not good at reading this stuff.

44:21.180 --> 44:27.240
And I've got to say, that's the most complete definition of GUIDs slash UUIDs I have ever heard.

44:27.600 --> 44:27.780
Whew.

44:28.760 --> 44:31.500
He really should attach, like, a KRAD handle to the letter

44:31.500 --> 44:33.900
so he can give it to, like, proper attribution and stuff.

44:36.980 --> 44:37.420
Yeah.

44:38.140 --> 44:41.040
So you're the database genius.

44:41.040 --> 44:46.760
Do you know how to store a GUID into a, I can even say, Postgres table?

44:51.640 --> 44:52.000
Sure.

44:52.140 --> 44:54.060
You make a byte column and you put an index on it.

44:54.060 --> 44:54.460
I don't see.

44:54.560 --> 44:55.340
Just use Postgres.

44:56.620 --> 45:02.100
Yeah, you know, yeah, I'm pretty sure that Postgres doesn't have this type of limitation that he's talking about,

45:02.100 --> 45:07.800
where it kind of gets upset when you use a car 16 as a primary key.

45:07.800 --> 45:11.740
But, you know, I could be wrong.

45:11.740 --> 45:21.520
I'm pretty sure that Postgres does have some type of row ID mechanism that can be used so that if you have multiple machines,

45:21.640 --> 45:27.680
it sounds like he was talking about what do people do when they need unique identifiers that can be generated disparately

45:27.680 --> 45:34.360
and merge through central MySQL table, I think what a lot of places do is they take unique, like,

45:34.660 --> 45:38.760
each database server has a unique machine ID and it has its own row IDs,

45:39.160 --> 45:42.760
and when you take those two numbers and put them together, then you have a unique ID no matter what.

45:42.980 --> 45:46.660
Even if the row IDs overlap, you still have that machine ID to make it unique.

45:46.660 --> 45:54.280
So I worked on a database application for a retail application, and that's what they did.

45:54.280 --> 45:59.640
They had machine ID, row ID, and there was never a collision because all the machine IDs were unique.

45:59.780 --> 46:01.360
They were negotiated when the machines were configured.

46:02.120 --> 46:02.920
So it was very simple.

46:03.120 --> 46:09.120
And a lot easier than generating GU IDs because, you know, if your index is something like that,

46:09.180 --> 46:12.080
only index is the first couple of characters of it.

46:12.140 --> 46:15.140
You don't have to worry about collisions and the index and all kinds of other fancy nonsense.

46:15.140 --> 46:21.160
They just used two integer columns, made a composite key, and that was it.

46:21.300 --> 46:21.600
They never worried.

46:21.660 --> 46:24.360
Boy, leave it to not theory to solve the problem in, like, five minutes.

46:24.600 --> 46:25.180
Not even that.

46:28.100 --> 46:30.120
Well, it was the last job I had.

46:30.320 --> 46:31.140
That was what they did.

46:31.240 --> 46:33.600
It's definitely not the cleanest solution.

46:33.740 --> 46:38.520
I mean, it would be nice if you could just depend on these keys to be generated and never collide,

46:38.680 --> 46:42.240
but these guys didn't have faith in that, and they were dealing with a lot of money,

46:42.240 --> 46:44.280
so they said, let's make sure that they...

46:44.280 --> 46:48.220
Well, doesn't SHA-1 have no collisions found in it yet?

46:51.300 --> 46:53.040
No, I thought SHA-1 did.

46:53.120 --> 46:56.480
I thought the only safe ones were 256, 384, and 5.

46:56.500 --> 46:56.920
Oh, okay.

46:57.100 --> 46:57.500
Well...

46:57.500 --> 46:59.940
Perhaps I'm just not caught up with that kind of stuff.

47:01.120 --> 47:01.480
There we go.

47:01.520 --> 47:05.440
Just have a 256-by key for each row column.

47:05.440 --> 47:06.860
For each...

47:06.860 --> 47:08.140
For the primary key for each row.

47:08.540 --> 47:08.720
Yeah.

47:11.200 --> 47:12.160
That's face-efficient.

47:13.240 --> 47:13.600
Yeah.

47:14.380 --> 47:19.500
Just for shits and giggles, SHA-1 broken.

47:20.160 --> 47:20.580
Oh, boy.

47:20.700 --> 47:21.420
I'm way behind those.

47:24.380 --> 47:25.120
Ah, no big deal.

47:25.280 --> 47:26.720
It's not really like it's that important.

47:27.120 --> 47:28.160
Everybody's using 512.

47:28.340 --> 47:28.940
They're cool anyway.

47:28.940 --> 47:31.680
I still use MD5, because MD5 is elite.

47:31.820 --> 47:32.600
I'm old school.

47:34.760 --> 47:37.080
Dude, I use ROD-13 on everything.

47:37.260 --> 47:37.560
I don't care.

47:40.180 --> 47:40.820
Nobody figured it out.

47:40.820 --> 47:42.660
Yeah, but it's a hell...

47:42.660 --> 47:43.880
You've got to, like...

47:43.880 --> 47:46.560
For, like, not theories, like, you know, Uber Elite CD collection,

47:46.660 --> 47:47.700
you've got to download the CD,

47:48.120 --> 47:50.680
and then you have to download the ROD-13 of the CD

47:50.680 --> 47:52.840
for, like, you know, 650 megabytes each,

47:52.860 --> 47:54.320
and then you've got to run and compare against them,

47:54.440 --> 47:55.340
just to make sure it's okay.

47:55.340 --> 47:57.960
It works, though.

47:58.040 --> 47:58.540
It works.

47:58.680 --> 47:59.540
I mean, I'm not going to knock it.

48:01.320 --> 48:02.120
That's what I'm saying.

48:02.220 --> 48:03.940
I don't have to worry about people breaking it.

48:04.440 --> 48:04.740
Yeah.

48:05.580 --> 48:06.380
That's what I'm going to create.

48:06.420 --> 48:08.920
I'm going to create a ROD-13 project bovine.

48:13.060 --> 48:14.680
I'm going to get, like, 15 million computers

48:14.680 --> 48:16.380
and use, like, you know, a nanosecond each,

48:16.420 --> 48:17.620
and we're like, yeah, it's broken.

48:17.800 --> 48:18.220
All right.

48:21.740 --> 48:23.200
We broke all the RODs.

48:25.340 --> 48:28.360
All multiples of 13.

48:28.520 --> 48:28.860
Yeah.

48:29.480 --> 48:30.100
No problem.

48:31.640 --> 48:32.160
All right.

48:32.240 --> 48:33.000
So, let's, like...

48:33.000 --> 48:34.740
Well, technically, we've technically already covered

48:34.740 --> 48:35.700
personal hacking stories,

48:35.760 --> 48:37.680
and I guess we kind of already made headway

48:37.680 --> 48:39.280
into these specific show topics.

48:39.520 --> 48:41.740
So, we're talking about smartphones.

48:42.220 --> 48:44.860
Originally, this episode was going to be sort of a...

48:44.860 --> 48:46.920
This is one I've always kind of planned out

48:46.920 --> 48:48.880
and tried to get it to go this week,

48:48.940 --> 48:49.680
but it didn't work out.

48:49.740 --> 48:51.000
It was going to be a, you know,

48:51.040 --> 48:53.480
cell phone grudge match of why my cell phone

48:53.480 --> 48:54.760
kicks your cell phone's ass,

48:54.760 --> 48:56.500
and we're going to have Natus on here

48:56.500 --> 48:58.360
talking about, lead about his BlackBerry,

48:59.280 --> 49:03.100
and Savant was going to be on here

49:03.100 --> 49:04.980
talking about his Razer and his SDA,

49:05.220 --> 49:06.480
because he doesn't really like his SDA.

49:07.200 --> 49:08.940
But, of course, I think his SDA is kind of broken,

49:08.940 --> 49:11.900
so perhaps that's why he doesn't like it,

49:11.980 --> 49:15.200
but it's good stuff.

49:15.420 --> 49:17.260
But now it's just me and not theory.

49:17.340 --> 49:18.420
We're going to talk about smartphones.

49:20.480 --> 49:21.340
Word to your mother.

49:21.340 --> 49:21.940
Word.

49:22.940 --> 49:25.100
So, I don't know.

49:25.240 --> 49:27.560
For me, when it comes to smartphones,

49:27.900 --> 49:31.680
I guess that there's three platforms, maybe,

49:31.860 --> 49:33.520
that are relevant, maybe four.

49:34.020 --> 49:36.880
There's, like, the standard Java platform

49:36.880 --> 49:38.280
that just runs Java apps.

49:38.720 --> 49:40.460
There's the Windows Mobile platform,

49:40.620 --> 49:41.720
and there's Symbian.

49:41.800 --> 49:43.920
I can't really think of anything else that jumps to mind.

49:44.080 --> 49:46.580
Maybe Linux, if people are considering Linux phones now.

49:46.580 --> 49:49.060
Well, what does the BlackBerry run?

49:49.140 --> 49:51.320
Because I was actually curious about this,

49:51.360 --> 49:52.420
and I really couldn't find much.

49:52.940 --> 49:55.040
Is that just a Java-based?

49:58.300 --> 50:00.780
Yeah, it's got its own proprietary operating system,

50:00.880 --> 50:01.640
embedded operating system.

50:01.860 --> 50:03.300
It does run Java applications.

50:04.000 --> 50:05.080
I don't know which standard.

50:05.200 --> 50:06.260
That's my problem with Java,

50:06.420 --> 50:07.760
is that there's so many standards.

50:07.760 --> 50:13.260
It's just J2SE, J2EE, J2ME, J2ME,

50:13.740 --> 50:15.680
Midlip Profile 1, Midlip Profile 2,

50:15.820 --> 50:17.500
CLDC 1, CLDC 2.

50:17.680 --> 50:19.480
Like, guys, it's fucking Java.

50:19.600 --> 50:20.840
I thought it was supposed to be standard,

50:20.940 --> 50:21.780
so I can use it anywhere.

50:22.540 --> 50:24.960
I can't use Java apps on my MDA.

50:25.660 --> 50:31.060
Well, I can't use, what is it, Google Maps

50:31.060 --> 50:33.260
for my phone.

50:33.260 --> 50:36.100
Ah, that is...

50:36.100 --> 50:37.820
Well, there's a way, like,

50:37.940 --> 50:39.240
if you go to, like, the forums,

50:39.380 --> 50:41.940
you have to download this runtime environment

50:41.940 --> 50:44.140
from IBM, because it runs on Windows Mobile,

50:44.480 --> 50:45.660
and then you do that,

50:45.720 --> 50:46.840
and then you grab Windows Mobile,

50:47.060 --> 50:47.800
and then you, like, you know,

50:47.820 --> 50:50.000
run three times in a counterclockwise pattern,

50:50.480 --> 50:52.580
and you've got to do it while the moon's full.

50:53.220 --> 50:54.960
It was complicated enough that I looked at it

50:54.960 --> 50:55.880
and said, ah, screw this.

50:55.900 --> 50:56.680
I'll just deal with it.

50:59.500 --> 51:00.700
Do you have to use Windows

51:00.700 --> 51:02.900
Genuine Mobile Advantage or something crazy?

51:02.900 --> 51:03.900
Do you want to make sure

51:03.900 --> 51:05.820
your Windows update is correct or something?

51:07.160 --> 51:08.940
Actually, I was in my car...

51:08.940 --> 51:09.780
You want to make sure that...

51:09.780 --> 51:15.880
I was in my car the other day,

51:15.880 --> 51:17.960
and I heard on the radio

51:17.960 --> 51:19.460
an ad for Google Maps.

51:20.200 --> 51:21.660
It was kind of creepy.

51:23.300 --> 51:23.520
Really?

51:26.080 --> 51:26.360
That's...

51:26.360 --> 51:27.380
Yeah, I was like, whoa.

51:28.200 --> 51:30.000
They were advertising it for...

51:30.000 --> 51:32.040
It was Google Maps Mobile,

51:32.040 --> 51:33.560
and, like, they were, like,

51:33.560 --> 51:35.920
talking about this ditzy girl,

51:36.040 --> 51:36.440
and she was like,

51:36.720 --> 51:38.300
yeah, Google Maps folds up the maps

51:38.300 --> 51:39.200
and make them really small

51:39.200 --> 51:40.000
and they fit up in your phone.

51:40.040 --> 51:41.400
I'm like, oh, my God,

51:41.420 --> 51:43.440
I can't keep my car on the road.

51:43.500 --> 51:44.120
It's so bad.

51:47.380 --> 51:48.100
It burns.

51:48.160 --> 51:49.200
Oh, it burns.

51:49.420 --> 51:49.880
It's a deep...

51:49.880 --> 51:51.300
Bleeding out of my ears.

51:51.820 --> 51:52.800
Damn you, Eric Schmidt.

51:52.920 --> 51:53.420
Damn you.

51:53.420 --> 51:53.480
Damn you.

51:53.480 --> 51:59.040
Oh, man.

51:59.740 --> 52:00.340
It's crazy.

52:00.620 --> 52:02.040
I have not heard any...

52:02.040 --> 52:05.160
Perhaps Boston's just leading the way.

52:05.860 --> 52:06.440
Yay for me.

52:08.020 --> 52:09.480
Well, I have actually...

52:09.480 --> 52:10.600
I haven't really been listening

52:10.600 --> 52:11.320
to regular radio.

52:11.420 --> 52:12.820
I've been listening to XM a whole lot,

52:13.000 --> 52:14.800
and I've got to say,

52:14.920 --> 52:16.080
I feel like,

52:16.220 --> 52:17.460
unless it's on the BBC News,

52:17.600 --> 52:19.220
that I completely don't know

52:19.220 --> 52:19.820
about it at all,

52:20.140 --> 52:20.960
and I don't think the BBC

52:20.960 --> 52:21.340
is going to happen.

52:21.340 --> 52:21.880
Hey, you never know.

52:21.960 --> 52:25.040
Well, there's Google Maps in...

52:25.040 --> 52:26.360
They have them for London,

52:26.520 --> 52:27.220
so you never know.

52:29.520 --> 52:30.180
Oh, they do.

52:30.300 --> 52:30.700
I just...

52:30.700 --> 52:32.460
I don't think that the BBC

52:32.460 --> 52:34.020
would have somebody like that

52:34.020 --> 52:34.380
advertised.

52:34.920 --> 52:35.980
I don't know that they really

52:35.980 --> 52:36.980
had anybody advertised

52:36.980 --> 52:38.680
on the BBC at all,

52:38.740 --> 52:39.540
except their own shows.

52:39.640 --> 52:39.860
That's really...

52:39.860 --> 52:40.340
Yeah, they're all

52:40.340 --> 52:41.520
government support over there.

52:41.620 --> 52:42.320
That's socialism

52:42.320 --> 52:43.120
and all that stuff.

52:45.600 --> 52:46.800
Hey, the fucking BBC

52:46.800 --> 52:47.360
is awesome.

52:47.540 --> 52:48.660
I don't care what anybody says.

52:49.140 --> 52:50.880
BBC is like the coolest station ever.

52:51.340 --> 52:52.180
I listen to it

52:52.180 --> 52:53.100
pretty much all day.

52:53.160 --> 52:53.440
All right.

52:53.540 --> 52:55.040
So there's...

52:55.040 --> 52:57.260
I guess you could say

52:57.260 --> 52:58.140
three or four operations.

52:58.520 --> 52:58.920
I don't know.

52:59.320 --> 52:59.640
Technically,

53:00.040 --> 53:01.240
do you...

53:01.240 --> 53:02.840
I don't think you're

53:02.840 --> 53:03.940
the person I should be asking this,

53:04.000 --> 53:04.980
but do you count the hip-top

53:04.980 --> 53:05.520
as a smartphone?

53:08.680 --> 53:09.040
Okay.

53:09.380 --> 53:10.220
Actually, yeah, I would.

53:12.460 --> 53:13.500
It's like weird

53:13.500 --> 53:16.020
proprietary nonsense.

53:16.020 --> 53:16.620
You can't, like,

53:16.680 --> 53:17.400
download regular stations.

53:17.400 --> 53:18.160
No, you can't, no.

53:18.480 --> 53:19.420
Unless they change it

53:19.420 --> 53:21.200
with the Sidekick 3,

53:21.320 --> 53:23.400
which I would not really

53:23.400 --> 53:24.180
bet that they would.

53:28.140 --> 53:30.780
Yeah, I would definitely

53:30.780 --> 53:32.600
consider it a, you know,

53:32.620 --> 53:34.520
smartphone platform.

53:35.220 --> 53:35.980
I don't know how many...

53:35.980 --> 53:37.120
I mean, the last time

53:37.120 --> 53:38.400
you had your Sidekick,

53:38.520 --> 53:39.200
how many applications

53:39.200 --> 53:40.100
did they have released?

53:40.100 --> 53:40.120
Probably both.

53:40.120 --> 53:41.480
Applications or games?

53:42.820 --> 53:43.620
Or both?

53:44.940 --> 53:45.360
No.

53:45.520 --> 53:46.260
Oh, applications?

53:46.440 --> 53:47.480
Probably, like, under 10.

53:50.320 --> 53:50.680
Yeah.

53:51.000 --> 53:51.440
They had, like,

53:51.500 --> 53:52.440
Calorie Cruncher

53:52.440 --> 53:53.500
and, like,

53:53.780 --> 53:54.800
fucking Wallet

53:54.800 --> 53:55.760
something or other.

53:56.840 --> 53:58.040
Hey, it had SSH,

53:58.100 --> 53:59.040
so I was a happy duck.

54:01.760 --> 54:02.520
See, that's true.

54:02.580 --> 54:02.940
You know what?

54:02.960 --> 54:03.680
And I gotta admit,

54:04.080 --> 54:05.340
the SSH client

54:05.340 --> 54:07.060
on the Sidekick...

54:07.060 --> 54:08.040
Well, that originally

54:08.040 --> 54:08.920
was called...

54:08.920 --> 54:09.820
Yeah, I think it was called

54:09.820 --> 54:10.460
Monkey Terminal.

54:10.740 --> 54:11.500
And then they decided,

54:11.620 --> 54:12.020
oh, wait,

54:12.580 --> 54:13.680
we shouldn't co-op that.

54:13.720 --> 54:14.260
We should call it

54:14.260 --> 54:15.560
Terminal Client.

54:20.920 --> 54:21.620
Okay, well,

54:22.080 --> 54:23.000
it was pretty good.

54:23.080 --> 54:23.540
The only thing

54:23.540 --> 54:24.700
that I didn't like about it

54:24.700 --> 54:25.600
that they didn't really

54:25.600 --> 54:26.680
have any answer for me for,

54:26.720 --> 54:27.240
I had to figure out

54:27.240 --> 54:27.740
by myself,

54:28.140 --> 54:29.340
was that when you connect

54:29.340 --> 54:29.980
to a server,

54:30.080 --> 54:30.760
you have to have

54:30.760 --> 54:32.280
some SSH option enabled

54:32.280 --> 54:32.740
that's, like,

54:33.080 --> 54:35.340
allow passwords

54:35.340 --> 54:37.140
to be tunneled

54:37.140 --> 54:38.080
in clear text

54:38.080 --> 54:39.020
or something like that.

54:39.020 --> 54:40.340
Like, some option

54:40.340 --> 54:40.980
I had to set

54:40.980 --> 54:41.840
on my SSH server

54:41.840 --> 54:42.400
before it would

54:42.400 --> 54:43.140
accept the connection.

54:43.220 --> 54:43.420
Otherwise,

54:43.520 --> 54:44.560
it would just silently fail.

54:45.040 --> 54:46.380
And I told them about it,

54:46.680 --> 54:47.100
and they said,

54:47.140 --> 54:48.040
oh, thanks for the bug report.

54:48.100 --> 54:48.520
That's great.

54:49.000 --> 54:49.660
We'll be sure to

54:49.660 --> 54:50.260
update the document.

54:50.440 --> 54:51.280
We'll check back,

54:51.320 --> 54:51.940
and we never did it.

54:52.900 --> 54:53.100
Thanks.

54:53.100 --> 54:55.960
Yes, and this was part

54:55.960 --> 54:56.360
of the reason

54:56.360 --> 54:57.420
why Not Theory's

54:57.420 --> 54:57.840
hip-tough

54:57.840 --> 54:58.360
was in, like,

54:58.400 --> 54:59.180
three or four pieces

54:59.180 --> 54:59.660
by the time

54:59.660 --> 55:00.560
he was done with it.

55:03.520 --> 55:03.880
Listen,

55:03.980 --> 55:04.720
if your users

55:04.720 --> 55:06.280
report a genuine issue

55:06.280 --> 55:07.540
that affects them

55:07.540 --> 55:08.080
and you say,

55:08.160 --> 55:08.780
oh, we're going to put it

55:08.780 --> 55:09.400
in documentation,

55:09.520 --> 55:10.200
you never do,

55:10.580 --> 55:11.240
you're an asshole

55:11.240 --> 55:12.020
because they're doing

55:12.020 --> 55:12.760
your QA

55:12.760 --> 55:14.000
and all that other shit

55:14.000 --> 55:14.480
for you,

55:14.480 --> 55:15.020
and you're just

55:15.020 --> 55:15.820
throwing it away.

55:16.140 --> 55:16.960
You're just frustrating

55:16.960 --> 55:17.720
more of your users.

55:17.720 --> 55:19.080
I've dealt a lot

55:19.080 --> 55:19.800
in the past year

55:19.800 --> 55:20.520
with QA

55:20.520 --> 55:22.020
and documentation

55:22.020 --> 55:23.220
and all kinds of stuff

55:23.220 --> 55:24.100
at this, you know,

55:24.140 --> 55:24.940
fairly large company

55:24.940 --> 55:25.760
I was working for,

55:26.200 --> 55:27.440
and when users

55:27.440 --> 55:28.280
reported an issue

55:28.280 --> 55:28.680
to me

55:28.680 --> 55:29.220
and told me

55:29.220 --> 55:29.940
it was a big deal,

55:30.020 --> 55:30.560
we documented

55:30.560 --> 55:31.480
that shit right away,

55:31.620 --> 55:32.520
but nobody else

55:32.520 --> 55:33.220
seems to do it.

55:33.960 --> 55:34.980
So, screw them.

55:35.720 --> 55:36.380
Bad company.

55:36.640 --> 55:37.200
Naughty company.

55:37.440 --> 55:38.080
I slapped your wrist.

55:38.360 --> 55:39.420
I thought the only thing

55:39.420 --> 55:39.760
he slapped,

55:39.860 --> 55:40.280
so, oh, boy.

55:42.600 --> 55:43.000
Yeah.

55:43.460 --> 55:43.880
Oh, yeah.

55:44.100 --> 55:44.640
Go ahead.

55:45.280 --> 55:45.660
Yeah, hip,

55:45.920 --> 55:46.520
I've got to say,

55:46.520 --> 55:47.840
I enjoyed the hip-top.

55:48.180 --> 55:49.120
It was nice,

55:50.040 --> 55:50.820
but the problem is

55:50.820 --> 55:51.420
it was just,

55:51.620 --> 55:52.740
you were locked into it.

55:52.780 --> 55:53.880
There was no expandability.

55:54.540 --> 55:55.720
Like, those six apps

55:55.720 --> 55:56.640
that we were talking about,

55:56.740 --> 55:57.620
those were the six apps

55:57.620 --> 55:58.180
you could download,

55:58.560 --> 55:59.300
and I'm not sure

55:59.300 --> 56:00.260
if they've improved it

56:00.260 --> 56:01.980
with further versions,

56:02.180 --> 56:03.260
but I think they're all

56:03.260 --> 56:04.360
connected to the same one.

56:06.580 --> 56:06.760
So,

56:08.380 --> 56:09.520
it's definitely,

56:09.940 --> 56:10.600
Yeah, I don't really know.

56:10.840 --> 56:11.600
My real big,

56:11.940 --> 56:13.980
I was just saying,

56:14.040 --> 56:14.780
my real big issue

56:14.780 --> 56:15.220
with them

56:15.220 --> 56:16.200
was how close

56:16.200 --> 56:16.980
the platform was,

56:17.020 --> 56:17.820
and even if you wanted

56:17.820 --> 56:18.580
to be a developer,

56:19.000 --> 56:19.840
apparently with the

56:19.840 --> 56:20.980
original sidekick,

56:21.020 --> 56:21.940
it was a lot easier

56:21.940 --> 56:23.200
to get developer access,

56:23.880 --> 56:24.580
but then they started

56:24.580 --> 56:25.340
seeing that everybody

56:25.340 --> 56:26.400
who wanted free ringtones

56:26.400 --> 56:26.820
and stuff

56:26.820 --> 56:27.660
was signing up

56:27.660 --> 56:28.160
as a developer,

56:28.320 --> 56:29.280
so they just locked it down,

56:29.360 --> 56:29.600
and they said,

56:29.660 --> 56:29.780
nope,

56:29.840 --> 56:30.180
you've got to go

56:30.180 --> 56:31.340
through this approval process,

56:31.740 --> 56:32.380
and if you ever want

56:32.380 --> 56:33.300
to release an application,

56:33.440 --> 56:34.080
you can only release

56:34.080 --> 56:34.880
to other developers

56:34.880 --> 56:36.000
unless you go through us,

56:36.060 --> 56:36.600
and you're screwed.

56:36.600 --> 56:37.020
And then,

56:37.140 --> 56:37.540
for me,

56:38.160 --> 56:38.880
it's no motivation

56:38.880 --> 56:40.600
to work on an application

56:40.600 --> 56:41.760
because what if I found

56:41.760 --> 56:42.280
something that was,

56:42.740 --> 56:43.020
you know,

56:43.760 --> 56:45.360
a viable application,

56:45.560 --> 56:45.980
and then they said,

56:46.040 --> 56:46.120
no,

56:46.160 --> 56:47.000
we're not going to support it

56:47.000 --> 56:47.360
because I'm not

56:47.360 --> 56:47.720
going to have people

56:47.720 --> 56:48.180
who use it.

56:48.300 --> 56:48.460
So,

56:48.520 --> 56:48.880
I was like,

56:48.920 --> 56:49.260
you know what,

56:49.380 --> 56:49.740
fuck you.

56:50.160 --> 56:51.000
My sidekick's getting back.

56:51.000 --> 56:52.360
Right before the trio.

56:53.520 --> 56:53.840
Yeah,

56:53.960 --> 56:55.300
that was the major issue.

56:55.420 --> 56:55.520
I mean,

56:55.560 --> 56:56.420
I got into the developer

56:56.420 --> 56:56.980
program,

56:57.100 --> 56:57.500
I think.

56:57.780 --> 56:58.260
I don't know.

56:58.780 --> 56:59.560
I'm not sure exactly

56:59.560 --> 56:59.960
where it goes,

57:00.300 --> 57:00.960
but if you got into

57:00.960 --> 57:01.780
the developer program,

57:01.880 --> 57:02.520
you had to void your

57:02.520 --> 57:03.540
warranty with T-Mobile,

57:03.640 --> 57:04.120
and I was like,

57:04.220 --> 57:04.880
no,

57:04.880 --> 57:05.800
I don't want to do that.

57:06.180 --> 57:07.040
I spent a lot of money

57:07.040 --> 57:07.560
on this phone.

57:07.660 --> 57:07.880
Sorry.

57:09.720 --> 57:10.080
And,

57:10.140 --> 57:10.740
I mean,

57:10.960 --> 57:11.620
it was,

57:11.720 --> 57:12.720
I actually played around

57:12.720 --> 57:13.260
with the emulator

57:13.260 --> 57:13.560
and,

57:13.660 --> 57:14.140
like,

57:14.180 --> 57:15.540
looked at the developer forums,

57:15.700 --> 57:16.720
and there was basically,

57:16.720 --> 57:16.980
like,

57:17.040 --> 57:17.240
you know,

57:17.440 --> 57:18.360
tons of software

57:18.360 --> 57:18.960
you could download

57:18.960 --> 57:19.860
because you were a developer,

57:20.460 --> 57:21.380
and some of them

57:21.380 --> 57:23.220
were pretty interesting.

57:23.340 --> 57:23.860
I will say,

57:23.960 --> 57:24.060
like,

57:24.100 --> 57:24.300
there was,

57:24.400 --> 57:24.420
like,

57:24.440 --> 57:25.120
a peer-to-peer

57:25.120 --> 57:26.220
messaging client,

57:26.560 --> 57:29.480
and I actually think

57:29.480 --> 57:30.500
someone wrote a peer-to-peer

57:30.500 --> 57:31.420
file trading app.

57:31.520 --> 57:32.100
They just couldn't

57:32.100 --> 57:33.520
actually put files on it.

57:33.520 --> 57:35.580
And there was just some,

57:35.640 --> 57:36.640
there was some really cool

57:36.640 --> 57:37.320
stuff out there,

57:37.420 --> 57:38.740
and just none of this stuff

57:38.740 --> 57:39.220
got published.

57:39.340 --> 57:39.640
That was,

57:39.700 --> 57:40.760
that was really frustrating.

57:41.620 --> 57:41.940
And,

57:42.060 --> 57:43.400
when I looked at it,

57:43.440 --> 57:44.240
I had the choice to go,

57:44.380 --> 57:44.920
when I,

57:44.980 --> 57:46.880
so I upgraded to a Sidekick 2

57:46.880 --> 57:47.260
because,

57:47.800 --> 57:48.060
ah,

57:48.100 --> 57:48.720
there was really nothing,

57:48.860 --> 57:50.060
nothing else out there

57:50.060 --> 57:50.940
at that time

57:50.940 --> 57:51.920
within the market.

57:52.300 --> 57:52.640
So,

57:52.760 --> 57:53.060
you know,

57:53.120 --> 57:54.460
I went up to a Sidekick 2,

57:54.540 --> 57:55.680
and I eventually lost

57:55.680 --> 57:56.460
my Sidekick 2,

57:56.560 --> 57:56.760
like,

57:56.820 --> 57:57.760
three months after I got it,

57:57.800 --> 57:58.580
and that was very sad.

57:59.180 --> 58:00.120
And so I went back

58:00.120 --> 58:00.900
to Sidekick 1,

58:01.060 --> 58:02.560
and my contract was up,

58:02.580 --> 58:02.840
and I said,

58:02.900 --> 58:03.140
okay,

58:03.360 --> 58:05.200
I can either get the MDA,

58:05.340 --> 58:06.180
which runs Windows Mobile,

58:06.440 --> 58:07.840
or the Sidekick 3.

58:08.220 --> 58:09.100
And I looked at it,

58:09.120 --> 58:09.440
and I said,

58:09.500 --> 58:09.780
you know,

58:09.940 --> 58:10.660
I really want to go

58:10.660 --> 58:11.280
with Windows Mobile

58:11.280 --> 58:13.220
because the Sidekick

58:13.220 --> 58:13.900
was really starting

58:13.900 --> 58:14.820
to get frustrating on me.

58:15.640 --> 58:15.980
So,

58:16.080 --> 58:16.740
here I am today.

58:18.460 --> 58:18.780
And I'm,

58:19.940 --> 58:20.740
there you are.

58:20.800 --> 58:21.580
It's really sad,

58:21.700 --> 58:22.140
when Windows Mobile 4

58:22.140 --> 58:22.280
Yeah,

58:22.380 --> 58:23.020
that's actually kind of

58:23.020 --> 58:23.220
weird,

58:23.340 --> 58:23.920
isn't it?

58:25.020 --> 58:25.380
Hey,

58:25.420 --> 58:25.760
I've got to say,

58:25.820 --> 58:26.680
Windows Mobile 5

58:26.680 --> 58:27.680
isn't half bad.

58:28.020 --> 58:28.280
I mean,

58:28.320 --> 58:29.040
there's some odd quirks

58:29.040 --> 58:29.440
about it,

58:29.580 --> 58:31.600
but there was some odd quirks

58:31.600 --> 58:32.520
about the Sidekick 2,

58:32.740 --> 58:35.160
and you just learn

58:35.160 --> 58:35.820
to work your health

58:35.820 --> 58:36.280
around them.

58:38.880 --> 58:39.620
Have you actually

58:39.620 --> 58:40.040
ever used,

58:40.520 --> 58:40.740
hmm?

58:43.260 --> 58:44.040
Have you ever used

58:44.040 --> 58:44.380
a HIPTA,

58:44.500 --> 58:45.040
not a HIPTA,

58:45.160 --> 58:45.880
a BlackBerry?

58:49.460 --> 58:49.940
You know,

58:50.020 --> 58:50.500
I've turned around

58:50.500 --> 58:51.480
with Nattices a little bit,

58:51.480 --> 58:52.140
and it was,

58:52.240 --> 58:52.540
you know,

58:52.600 --> 58:53.020
overwhelming.

58:53.200 --> 58:53.840
It seemed like,

58:54.360 --> 58:54.560
okay,

58:54.620 --> 58:55.120
it's a phone,

58:55.120 --> 58:55.980
and it can run

58:55.980 --> 58:56.840
Java applications,

58:57.260 --> 58:58.260
but other than that,

58:58.360 --> 58:58.560
it was,

58:59.260 --> 58:59.440
I mean,

58:59.460 --> 59:00.140
that's all it did.

59:00.360 --> 59:00.960
And for some people,

59:01.000 --> 59:01.400
that's great,

59:01.460 --> 59:02.160
because it's simple,

59:02.280 --> 59:02.660
and it's,

59:03.060 --> 59:03.340
you know,

59:03.400 --> 59:04.160
serves its purpose,

59:04.260 --> 59:05.020
and it doesn't crash

59:05.020 --> 59:06.300
like my Windows phone does.

59:06.360 --> 59:07.480
I will admit wholeheartedly

59:07.480 --> 59:08.260
that my Windows phone

59:08.260 --> 59:08.620
crashes,

59:09.000 --> 59:09.820
even my new one,

59:10.260 --> 59:11.480
but you know what?

59:11.520 --> 59:12.040
I need something

59:12.040 --> 59:12.840
that I can get in

59:12.840 --> 59:14.120
and screw around it,

59:14.120 --> 59:14.380
so.

59:15.160 --> 59:16.160
I can't say I've ever

59:16.160 --> 59:17.440
actually had my phone crash.

59:17.740 --> 59:19.060
I've just had applications

59:19.060 --> 59:20.880
that walk up on my phone.

59:20.880 --> 59:23.240
Like I have this little,

59:23.920 --> 59:24.320
I have,

59:24.540 --> 59:25.320
like I said,

59:25.380 --> 59:26.320
I have a T-Mobile MDA,

59:26.840 --> 59:27.860
and I have like on my

59:27.860 --> 59:28.340
today screen,

59:28.440 --> 59:29.300
like it grabs the weather

59:29.300 --> 59:30.360
for me for like the next

59:30.360 --> 59:31.380
four or five days,

59:31.580 --> 59:33.420
and I told it to update it

59:33.420 --> 59:33.680
once,

59:33.720 --> 59:34.740
and I lost my connection,

59:34.940 --> 59:36.560
and the program locked up,

59:37.360 --> 59:38.100
and it was just like,

59:38.140 --> 59:38.300
you know,

59:38.380 --> 59:38.640
constantly,

59:39.400 --> 59:40.340
in Windows Mobile 5,

59:40.380 --> 59:41.240
you don't have an hourglass,

59:41.300 --> 59:43.100
you have this little round thing

59:43.100 --> 59:44.580
that like changes color,

59:44.800 --> 59:46.460
and it was just sitting there,

59:46.600 --> 59:47.400
and actually,

59:47.620 --> 59:48.540
I let it sit there

59:48.540 --> 59:49.120
for a while,

59:49.280 --> 59:50.440
and then I got a phone call,

59:50.640 --> 59:51.940
and none of my buttons work.

59:51.980 --> 59:52.820
I couldn't answer the phone,

59:53.120 --> 59:53.560
and I was like,

59:53.900 --> 59:54.140
ooh,

59:54.380 --> 59:54.780
okay,

59:55.100 --> 59:56.240
I think I'm going to

59:56.240 --> 59:57.160
have to reboot now.

59:57.940 --> 59:58.220
Yeah.

01:00:00.820 --> 01:00:01.500
Yeah,

01:00:01.620 --> 01:00:02.260
that's unfortunate,

01:00:02.560 --> 01:00:02.820
but,

01:00:03.840 --> 01:00:04.120
you know,

01:00:04.180 --> 01:00:04.440
again,

01:00:04.540 --> 01:00:04.980
for me,

01:00:05.600 --> 01:00:06.340
it's worth it,

01:00:06.380 --> 01:00:07.800
because I can get in there

01:00:07.800 --> 01:00:09.060
and write applications for it,

01:00:09.120 --> 01:00:10.080
and it's just stupid.

01:00:10.080 --> 01:00:10.220
Oh,

01:00:10.240 --> 01:00:11.180
it's amazingly easy,

01:00:11.300 --> 01:00:12.500
and you don't have to

01:00:12.500 --> 01:00:13.620
void your warranty,

01:00:14.980 --> 01:00:15.540
but,

01:00:15.840 --> 01:00:17.100
yeah,

01:00:17.100 --> 01:00:17.420
exactly.

01:00:17.540 --> 01:00:18.600
And the emulators are amazing.

01:00:18.600 --> 01:00:19.780
The emulators are amazing.

01:00:21.820 --> 01:00:22.280
I mean,

01:00:22.340 --> 01:00:23.540
you get a copy,

01:00:23.700 --> 01:00:23.900
I mean,

01:00:23.920 --> 01:00:24.500
you have to buy,

01:00:25.080 --> 01:00:25.860
unless you have,

01:00:25.900 --> 01:00:26.020
like,

01:00:26.040 --> 01:00:26.820
connections someplace,

01:00:26.920 --> 01:00:27.420
like not there,

01:00:27.460 --> 01:00:27.780
and I do,

01:00:27.880 --> 01:00:28.220
yeah.

01:00:31.280 --> 01:00:32.620
Or you go to a release event,

01:00:32.660 --> 01:00:33.660
and they give you a free copy

01:00:33.660 --> 01:00:34.880
of Visual Studio 2005,

01:00:35.080 --> 01:00:35.320
you're like,

01:00:35.380 --> 01:00:35.900
thank you.

01:00:38.480 --> 01:00:38.840
Like,

01:00:38.980 --> 01:00:40.340
you have to pay,

01:00:40.480 --> 01:00:40.720
like,

01:00:40.760 --> 01:00:41.860
a good chunk of change for it.

01:00:41.920 --> 01:00:42.460
I think it's,

01:00:43.180 --> 01:00:44.000
I don't even want to know

01:00:44.000 --> 01:00:45.080
how expensive it is,

01:00:45.140 --> 01:00:45.920
but you have all,

01:00:45.960 --> 01:00:46.060
like,

01:00:46.060 --> 01:00:47.320
the mobile emulators there,

01:00:47.400 --> 01:00:48.060
and you can grab them,

01:00:48.140 --> 01:00:48.680
install them,

01:00:48.740 --> 01:00:49.860
and you essentially have

01:00:49.860 --> 01:00:50.000
this,

01:00:50.080 --> 01:00:50.160
like,

01:00:50.220 --> 01:00:51.340
smartphone up on your screen

01:00:51.340 --> 01:00:52.280
that emulates everything

01:00:52.280 --> 01:00:54.100
that it would on an actual phone.

01:00:54.220 --> 01:00:55.000
It's uncanny.

01:00:56.960 --> 01:00:57.320
But,

01:00:57.360 --> 01:00:58.720
it's easy to develop before.

01:00:59.120 --> 01:01:00.040
And you can develop stuff

01:01:00.040 --> 01:01:00.160
for,

01:01:00.260 --> 01:01:00.300
like,

01:01:00.380 --> 01:01:00.880
BlackBerrys,

01:01:00.880 --> 01:01:01.280
but I like,

01:01:01.380 --> 01:01:03.000
I had to set my,

01:01:03.180 --> 01:01:04.900
I'm basically the support person

01:01:04.900 --> 01:01:06.120
for my supervisor

01:01:06.120 --> 01:01:07.180
and her BlackBerry,

01:01:07.840 --> 01:01:09.220
because she doesn't understand

01:01:09.220 --> 01:01:10.100
really how to use it.

01:01:10.180 --> 01:01:10.440
Actually,

01:01:10.540 --> 01:01:10.620
she,

01:01:10.720 --> 01:01:11.640
I won't say that.

01:01:11.640 --> 01:01:13.200
She has improved greatly

01:01:13.200 --> 01:01:14.340
over the past couple of months.

01:01:14.420 --> 01:01:15.040
I've actually become

01:01:15.040 --> 01:01:15.680
quite impressed.

01:01:16.420 --> 01:01:16.600
But,

01:01:16.640 --> 01:01:16.720
like,

01:01:16.760 --> 01:01:17.840
I played with her BlackBerry,

01:01:17.960 --> 01:01:18.880
and I was just,

01:01:19.020 --> 01:01:20.420
I was very underwhelmed

01:01:20.420 --> 01:01:20.940
compared to,

01:01:21.020 --> 01:01:21.080
like,

01:01:21.100 --> 01:01:22.020
my Windows mobile phone.

01:01:23.320 --> 01:01:23.720
I mean,

01:01:23.800 --> 01:01:23.940
it,

01:01:24.060 --> 01:01:24.440
it was,

01:01:24.560 --> 01:01:24.860
it's,

01:01:24.980 --> 01:01:25.660
I,

01:01:25.660 --> 01:01:25.980
I,

01:01:25.980 --> 01:01:27.020
I wholeheartedly agree

01:01:27.020 --> 01:01:27.280
with,

01:01:27.280 --> 01:01:27.940
uh,

01:01:27.940 --> 01:01:28.400
not theory.

01:01:28.620 --> 01:01:29.300
It's simple,

01:01:29.440 --> 01:01:29.940
it works,

01:01:30.060 --> 01:01:31.560
but I just was like,

01:01:31.660 --> 01:01:32.440
this is,

01:01:32.560 --> 01:01:32.960
this sucks.

01:01:34.540 --> 01:01:35.440
I really didn't like

01:01:35.440 --> 01:01:36.320
the interface either.

01:01:37.120 --> 01:01:37.260
Yeah,

01:01:37.380 --> 01:01:40.660
it seemed kind of clunky

01:01:40.660 --> 01:01:41.500
even the thumb wheel

01:01:41.500 --> 01:01:42.100
to get around.

01:01:42.240 --> 01:01:42.940
I didn't really like it.

01:01:43.040 --> 01:01:43.800
I'd like to be able to,

01:01:43.800 --> 01:01:44.000
like,

01:01:44.040 --> 01:01:44.680
touch the screen

01:01:44.680 --> 01:01:45.180
and do things.

01:01:45.280 --> 01:01:45.980
I don't think any BlackBerry

01:01:45.980 --> 01:01:46.080
No,

01:01:46.180 --> 01:01:46.680
I don't think so.

01:01:49.320 --> 01:01:49.640
Yeah.

01:01:51.180 --> 01:01:51.460
Yeah,

01:01:51.520 --> 01:01:51.760
for me,

01:01:51.800 --> 01:01:52.220
that's a problem.

01:01:52.340 --> 01:01:52.980
I like the touch screen.

01:01:53.080 --> 01:01:53.700
I like to be able to

01:01:53.700 --> 01:01:54.860
click around on my applications,

01:01:55.040 --> 01:01:56.060
click around on the web browser,

01:01:56.200 --> 01:01:56.340
you know,

01:01:56.340 --> 01:01:57.300
draw shit on the screen.

01:01:57.540 --> 01:01:57.860
Boobies.

01:01:57.860 --> 01:01:58.960
I like to do all that kind of stuff.

01:01:59.740 --> 01:02:01.000
I have a strike again.

01:02:01.740 --> 01:02:02.060
Yeah,

01:02:02.160 --> 01:02:02.280
I,

01:02:02.280 --> 01:02:02.560
I mean,

01:02:02.620 --> 01:02:03.060
I,

01:02:03.060 --> 01:02:03.140
I,

01:02:03.140 --> 01:02:03.420
I'm,

01:02:03.460 --> 01:02:04.660
I'm pretty much the same way,

01:02:04.760 --> 01:02:04.940
but,

01:02:05.380 --> 01:02:05.840
um,

01:02:05.840 --> 01:02:06.380
like,

01:02:06.460 --> 01:02:06.560
I,

01:02:06.560 --> 01:02:08.080
I see people with like BlackBerry

01:02:08.080 --> 01:02:08.400
is like,

01:02:08.460 --> 01:02:10.320
like the first generation models almost,

01:02:10.320 --> 01:02:10.860
like the,

01:02:10.940 --> 01:02:12.060
like black and white screens

01:02:12.060 --> 01:02:13.500
and they're still plugging away on them.

01:02:13.560 --> 01:02:13.700
So,

01:02:13.900 --> 01:02:14.080
I,

01:02:14.080 --> 01:02:14.340
I,

01:02:14.340 --> 01:02:14.840
I will give,

01:02:14.940 --> 01:02:16.440
I will give RIM like lots of props

01:02:16.440 --> 01:02:18.640
for making a hell of a reliable system

01:02:18.640 --> 01:02:21.080
that seemed to work for years on end.

01:02:21.200 --> 01:02:21.340
So,

01:02:21.960 --> 01:02:23.060
you really don't see that much

01:02:23.060 --> 01:02:23.900
with Windows Mobile Phone.

01:02:23.980 --> 01:02:24.140
I mean,

01:02:24.140 --> 01:02:24.940
how many people do you know

01:02:24.940 --> 01:02:26.860
that are actually running Pocket PC 2003

01:02:26.860 --> 01:02:27.520
on their phone?

01:02:30.700 --> 01:02:31.060
Yeah,

01:02:31.120 --> 01:02:31.700
not too many.

01:02:31.840 --> 01:02:31.900
I,

01:02:31.980 --> 01:02:32.120
you know,

01:02:32.140 --> 01:02:33.020
I have one phone

01:02:33.020 --> 01:02:33.380
that I,

01:02:33.460 --> 01:02:35.460
that I plan on using for a little bit

01:02:35.460 --> 01:02:36.020
that's got,

01:02:36.020 --> 01:02:36.600
uh,

01:02:36.600 --> 01:02:37.700
Windows Mobile 2003,

01:02:37.860 --> 01:02:38.320
but honestly,

01:02:38.700 --> 01:02:39.060
I'm,

01:02:39.180 --> 01:02:40.840
I've gotten so used to Windows Mobile 5,

01:02:40.920 --> 01:02:42.920
I'm just not excited about going back to it.

01:02:43.520 --> 01:02:43.720
So,

01:02:44.740 --> 01:02:45.320
and who knows,

01:02:45.400 --> 01:02:47.100
I'm sure they'll come out with another version soon

01:02:47.100 --> 01:02:47.980
that'll make me decide.

01:02:48.080 --> 01:02:48.240
Yeah.

01:02:48.320 --> 01:02:48.640
Yeah.

01:02:48.640 --> 01:02:48.780
Well,

01:02:48.840 --> 01:02:50.240
apparently it's already out there.

01:02:50.320 --> 01:02:50.800
They call them there.

01:02:50.860 --> 01:02:52.000
It's codenamed Crossbow.

01:02:54.320 --> 01:02:54.680
Yeah.

01:02:55.040 --> 01:02:55.400
Ooh.

01:02:56.040 --> 01:02:56.480
Um,

01:02:56.520 --> 01:02:57.460
I've never used Symbion.

01:02:57.540 --> 01:02:57.800
Have you?

01:02:57.860 --> 01:02:58.180
Have you?

01:02:58.180 --> 01:02:58.260
Um,

01:03:03.140 --> 01:03:03.540
actually,

01:03:03.740 --> 01:03:05.020
I have a,

01:03:05.420 --> 01:03:05.800
sorry,

01:03:05.880 --> 01:03:06.080
I don't know,

01:03:06.140 --> 01:03:07.580
I just got a bad reception.

01:03:07.780 --> 01:03:08.020
Um,

01:03:09.360 --> 01:03:12.740
I have a Sony Ericsson P910,

01:03:13.360 --> 01:03:14.360
and I have a Nokia,

01:03:14.600 --> 01:03:16.080
I think it's a 3650.

01:03:16.500 --> 01:03:17.560
They both run Symbion.

01:03:18.120 --> 01:03:18.440
Um,

01:03:18.780 --> 01:03:19.340
Symbion,

01:03:19.700 --> 01:03:20.500
by far,

01:03:20.940 --> 01:03:23.140
lets you do way cooler stuff

01:03:23.140 --> 01:03:23.760
than Windows Mobile.

01:03:23.760 --> 01:03:24.360
Blast for me.

01:03:24.920 --> 01:03:26.620
But when I went to get into the phone,

01:03:27.040 --> 01:03:27.240
no,

01:03:27.400 --> 01:03:28.180
I'm serious,

01:03:28.260 --> 01:03:29.680
you can access anything on the phone.

01:03:29.940 --> 01:03:30.640
That's why there's all,

01:03:30.720 --> 01:03:31.700
there's so many viruses

01:03:31.700 --> 01:03:33.180
and all kinds of worms

01:03:33.180 --> 01:03:34.120
and crap like that

01:03:34.120 --> 01:03:34.920
for Symbion phones.

01:03:35.300 --> 01:03:36.520
Because anything you want to do

01:03:36.520 --> 01:03:37.000
with the phone,

01:03:37.300 --> 01:03:38.800
you want to turn the phone on silently

01:03:38.800 --> 01:03:39.660
and call a number

01:03:39.660 --> 01:03:41.020
and hide it from the user,

01:03:41.120 --> 01:03:41.240
yeah,

01:03:41.300 --> 01:03:41.760
you can do that,

01:03:41.800 --> 01:03:42.220
no problem.

01:03:42.600 --> 01:03:42.780
You know,

01:03:42.800 --> 01:03:44.320
you want to turn on the microphone

01:03:44.320 --> 01:03:45.720
and record something

01:03:45.720 --> 01:03:46.220
and then,

01:03:46.360 --> 01:03:46.600
you know,

01:03:46.620 --> 01:03:48.100
send MP3 files

01:03:48.100 --> 01:03:48.820
or whatever,

01:03:48.920 --> 01:03:49.040
you know,

01:03:49.040 --> 01:03:49.940
encode them into MP3

01:03:49.940 --> 01:03:51.500
and send them off to some website

01:03:51.500 --> 01:03:52.740
and just spy on people,

01:03:52.920 --> 01:03:53.060
yeah,

01:03:53.120 --> 01:03:53.980
you can write an application

01:03:53.980 --> 01:03:54.540
to do that.

01:03:55.200 --> 01:03:56.000
All silently

01:03:56.000 --> 01:03:57.060
without the user having

01:03:57.060 --> 01:03:58.480
any clue what's going on.

01:04:00.320 --> 01:04:00.840
Windows Mobile,

01:04:00.920 --> 01:04:01.620
you really can't do that.

01:04:01.680 --> 01:04:01.800
Like,

01:04:01.820 --> 01:04:02.440
you make a call

01:04:02.440 --> 01:04:03.480
and it shows up on the screen

01:04:03.480 --> 01:04:04.160
and there's just no way

01:04:04.160 --> 01:04:04.600
to hide it.

01:04:04.640 --> 01:04:05.100
But Symbion,

01:04:05.200 --> 01:04:06.000
you can get right down

01:04:06.000 --> 01:04:06.800
into the guts of it

01:04:06.800 --> 01:04:07.640
and you can say,

01:04:07.760 --> 01:04:08.500
I want to do this,

01:04:08.560 --> 01:04:08.680
this,

01:04:08.720 --> 01:04:08.940
and this.

01:04:09.040 --> 01:04:10.180
I want to turn on the camera,

01:04:10.580 --> 01:04:12.000
I want to illicitly send pictures

01:04:12.000 --> 01:04:12.680
to Russia,

01:04:13.200 --> 01:04:13.420
you know,

01:04:13.480 --> 01:04:14.280
whatever you want to do,

01:04:14.540 --> 01:04:15.040
you can do it.

01:04:15.300 --> 01:04:16.720
But the development

01:04:16.720 --> 01:04:17.980
is a lot more complicated

01:04:17.980 --> 01:04:19.640
than Windows Mobile.

01:04:19.940 --> 01:04:20.500
You've got a program,

01:04:20.600 --> 01:04:21.540
I think you've programmed

01:04:21.540 --> 01:04:22.040
I think so,

01:04:22.120 --> 01:04:22.200
yeah.

01:04:22.200 --> 01:04:24.780
I don't know

01:04:24.780 --> 01:04:25.480
that there's anything

01:04:25.480 --> 01:04:27.000
any easier than that.

01:04:27.100 --> 01:04:28.040
It's not really a big deal.

01:04:28.120 --> 01:04:28.680
It's not like it's hard

01:04:28.680 --> 01:04:29.560
to program in C++,

01:04:29.820 --> 01:04:30.060
it's just,

01:04:30.460 --> 01:04:30.620
you know,

01:04:30.620 --> 01:04:31.000
you've got to be

01:04:31.000 --> 01:04:31.840
a little more careful

01:04:31.840 --> 01:04:32.280
about it.

01:04:32.980 --> 01:04:33.960
But I just remember

01:04:33.960 --> 01:04:34.860
getting the development

01:04:34.860 --> 01:04:35.440
environment

01:04:35.440 --> 01:04:38.680
was just really annoying.

01:04:38.800 --> 01:04:39.560
It reminded me a lot

01:04:39.560 --> 01:04:40.520
of Palm development.

01:04:40.640 --> 01:04:40.820
I don't know

01:04:40.820 --> 01:04:41.700
if you've done any of that,

01:04:42.060 --> 01:04:44.280
but Palm development

01:04:44.280 --> 01:04:45.040
is a nightmare.

01:04:45.560 --> 01:04:46.200
I guess that's another

01:04:46.200 --> 01:04:46.940
platform we could say

01:04:46.940 --> 01:04:47.500
for smartphones.

01:04:47.680 --> 01:04:48.120
The Palm,

01:04:48.120 --> 01:04:49.520
like Trio 600,

01:04:49.740 --> 01:04:50.380
Trio 650,

01:04:50.780 --> 01:04:51.000
700.

01:04:51.000 --> 01:04:51.400
That's something

01:04:51.400 --> 01:04:52.040
I didn't think of.

01:04:54.280 --> 01:04:54.640
Yeah,

01:04:54.740 --> 01:04:55.640
I didn't think of it now,

01:04:55.700 --> 01:04:55.920
honestly,

01:04:56.000 --> 01:04:56.900
because I've had

01:04:56.900 --> 01:04:57.760
such bad experiences

01:04:57.760 --> 01:04:58.220
with Palm.

01:04:58.480 --> 01:04:59.080
I know people

01:04:59.080 --> 01:05:00.240
that have old Trios

01:05:00.240 --> 01:05:00.640
and they're like,

01:05:00.740 --> 01:05:00.860
oh,

01:05:00.880 --> 01:05:01.940
it's so easy to use,

01:05:01.980 --> 01:05:02.660
it's so great.

01:05:03.020 --> 01:05:03.220
You know,

01:05:03.260 --> 01:05:04.900
I love feature X,

01:05:04.960 --> 01:05:05.080
Y,

01:05:05.100 --> 01:05:05.800
and Z about it.

01:05:06.040 --> 01:05:06.540
And I looked

01:05:06.540 --> 01:05:07.360
at my 700,

01:05:07.620 --> 01:05:09.740
my 700W

01:05:09.740 --> 01:05:10.180
that I had

01:05:10.180 --> 01:05:10.700
from Verizon

01:05:10.700 --> 01:05:11.520
and it had

01:05:11.520 --> 01:05:12.180
all these features,

01:05:12.400 --> 01:05:13.780
but only because,

01:05:13.920 --> 01:05:14.860
as I find out now,

01:05:14.960 --> 01:05:15.960
going to the 6700,

01:05:15.960 --> 01:05:17.860
that Palm had gone in

01:05:17.860 --> 01:05:18.560
and made those

01:05:18.560 --> 01:05:19.860
modifications to Windows.

01:05:20.160 --> 01:05:20.360
Like,

01:05:20.480 --> 01:05:21.400
Windows by default

01:05:21.400 --> 01:05:22.480
is definitely not

01:05:22.480 --> 01:05:23.880
as user-friendly

01:05:23.880 --> 01:05:26.880
on the Today screen

01:05:26.880 --> 01:05:28.400
as the Palm.

01:05:29.100 --> 01:05:29.860
That's interesting.

01:05:30.220 --> 01:05:30.940
It's easier to search

01:05:30.940 --> 01:05:31.880
for a contact.

01:05:32.420 --> 01:05:32.780
Yeah,

01:05:32.900 --> 01:05:33.380
like if you want

01:05:33.380 --> 01:05:34.160
to search for a contact,

01:05:34.560 --> 01:05:35.320
you just start typing

01:05:35.320 --> 01:05:36.080
it on the main screen.

01:05:36.200 --> 01:05:36.880
I'm pretty sure

01:05:36.880 --> 01:05:37.880
on my phone,

01:05:37.920 --> 01:05:38.860
if I try to do that now,

01:05:38.940 --> 01:05:39.520
it'll just start.

01:05:40.220 --> 01:05:40.940
Hold on,

01:05:40.980 --> 01:05:41.600
I think I have my phone

01:05:41.600 --> 01:05:42.020
right here,

01:05:42.140 --> 01:05:43.520
so let's go try that

01:05:43.520 --> 01:05:43.860
on mine.

01:05:44.540 --> 01:05:44.680
But,

01:05:44.760 --> 01:05:45.140
yeah,

01:05:45.140 --> 01:05:47.120
I used a Palm

01:05:47.120 --> 01:05:47.880
Trio

01:05:47.880 --> 01:05:49.360
and it was nice,

01:05:49.540 --> 01:05:50.060
but I just,

01:05:51.100 --> 01:05:51.780
I don't know,

01:05:51.920 --> 01:05:52.980
Palm seems to have

01:05:52.980 --> 01:05:55.620
lost the usability war,

01:05:55.720 --> 01:05:55.980
or at least

01:05:55.980 --> 01:05:57.460
the mindshare war.

01:05:58.640 --> 01:05:59.220
And it just

01:05:59.220 --> 01:06:00.120
doesn't really seem

01:06:00.120 --> 01:06:00.700
to be going here.

01:06:01.020 --> 01:06:01.340
Actually,

01:06:01.400 --> 01:06:02.200
I really need to reboot

01:06:02.200 --> 01:06:03.340
my Windows mobile phone

01:06:03.340 --> 01:06:04.320
because it just woke up.

01:06:05.260 --> 01:06:05.440
Yep,

01:06:05.480 --> 01:06:06.920
it's just staring at me

01:06:06.920 --> 01:06:07.920
as I type away here.

01:06:09.140 --> 01:06:09.920
Theory sucks.

01:06:11.160 --> 01:06:11.280
Well,

01:06:11.380 --> 01:06:11.480
the,

01:06:11.620 --> 01:06:14.220
I don't know,

01:06:14.300 --> 01:06:14.480
the,

01:06:14.480 --> 01:06:16.260
the Palm

01:06:16.260 --> 01:06:16.860
based phones,

01:06:17.260 --> 01:06:17.920
they're nice

01:06:17.920 --> 01:06:18.440
from a usability

01:06:18.440 --> 01:06:19.060
standpoint,

01:06:19.640 --> 01:06:20.100
but again,

01:06:20.160 --> 01:06:20.700
from a developer

01:06:20.700 --> 01:06:21.160
standpoint,

01:06:21.360 --> 01:06:22.080
just like Symbian,

01:06:22.520 --> 01:06:23.260
it's too much.

01:06:23.360 --> 01:06:24.060
If I want to make

01:06:24.060 --> 01:06:25.000
a simple application

01:06:25.000 --> 01:06:25.720
that does something,

01:06:26.280 --> 01:06:26.500
you know,

01:06:26.540 --> 01:06:27.540
like connects

01:06:27.540 --> 01:06:28.140
to a website

01:06:28.140 --> 01:06:28.600
or,

01:06:28.680 --> 01:06:28.940
you know,

01:06:29.380 --> 01:06:30.040
draws something

01:06:30.040 --> 01:06:30.600
on the screen,

01:06:30.680 --> 01:06:31.220
I should be able

01:06:31.220 --> 01:06:31.700
to do it

01:06:31.700 --> 01:06:32.520
in 10 minutes.

01:06:32.640 --> 01:06:33.160
It should be

01:06:33.160 --> 01:06:34.260
stupidly simple.

01:06:34.260 --> 01:06:36.240
If I want to get

01:06:36.240 --> 01:06:37.440
in and do crazy stuff,

01:06:37.520 --> 01:06:37.620
yeah,

01:06:37.640 --> 01:06:38.120
it's going to take

01:06:38.120 --> 01:06:38.420
longer,

01:06:38.600 --> 01:06:39.880
but it seems like

01:06:39.880 --> 01:06:41.340
Palm and Symbian

01:06:41.340 --> 01:06:42.100
err on the side

01:06:42.100 --> 01:06:42.940
of letting you do

01:06:42.940 --> 01:06:44.180
nearly anything

01:06:44.180 --> 01:06:44.940
you want to do

01:06:44.940 --> 01:06:45.840
at the expense

01:06:45.840 --> 01:06:46.740
of making everything

01:06:46.740 --> 01:06:47.760
really hard to do,

01:06:47.840 --> 01:06:49.100
whereas Windows mobile

01:06:49.100 --> 01:06:50.060
lets you do

01:06:50.060 --> 01:06:50.820
some things,

01:06:51.460 --> 01:06:53.200
but not really

01:06:53.200 --> 01:06:53.640
everything,

01:06:53.920 --> 01:06:55.380
but almost everything

01:06:55.380 --> 01:06:55.820
you do

01:06:55.820 --> 01:06:56.520
is really,

01:06:56.700 --> 01:06:57.080
really simple.

01:06:57.200 --> 01:06:57.700
You can get

01:06:57.700 --> 01:06:58.620
into native code,

01:06:59.080 --> 01:07:00.000
which is C plus,

01:07:00.120 --> 01:07:00.300
you know,

01:07:00.300 --> 01:07:01.780
embedded visual C plus plus

01:07:01.780 --> 01:07:02.980
code and do

01:07:02.980 --> 01:07:04.020
complicated things,

01:07:04.340 --> 01:07:05.960
but for the most part

01:07:05.960 --> 01:07:06.540
you can stay

01:07:06.540 --> 01:07:07.160
in C Sharp

01:07:07.160 --> 01:07:08.000
or Visual Basic

01:07:08.000 --> 01:07:08.980
and make,

01:07:09.600 --> 01:07:10.120
you can just

01:07:10.120 --> 01:07:10.840
churn out apps.

01:07:10.840 --> 01:07:11.460
You can even

01:07:11.460 --> 01:07:12.300
stay in C Sharp

01:07:12.300 --> 01:07:12.840
and import

01:07:12.840 --> 01:07:14.240
native code into it,

01:07:14.300 --> 01:07:14.460
like,

01:07:14.820 --> 01:07:15.420
for example,

01:07:16.660 --> 01:07:18.060
if I wrote

01:07:18.060 --> 01:07:18.680
an application

01:07:18.680 --> 01:07:19.700
for Pocket PC

01:07:19.700 --> 01:07:20.780
called MFR cubed

01:07:20.780 --> 01:07:21.300
and it was

01:07:21.300 --> 01:07:22.300
a blue box,

01:07:22.380 --> 01:07:22.860
red box,

01:07:23.040 --> 01:07:26.260
and 16 touch zone,

01:07:28.420 --> 01:07:28.980
yeah,

01:07:29.020 --> 01:07:29.560
that was pretty cool.

01:07:29.960 --> 01:07:30.980
I got to say

01:07:30.980 --> 01:07:31.420
I was kind of

01:07:31.420 --> 01:07:31.760
impressed with that.

01:07:31.780 --> 01:07:33.140
I think I wrote it

01:07:33.140 --> 01:07:33.420
in, like,

01:07:33.760 --> 01:07:34.320
quite literally

01:07:34.320 --> 01:07:35.020
an afternoon

01:07:35.020 --> 01:07:36.060
and I think

01:07:36.060 --> 01:07:36.840
most of that time

01:07:36.840 --> 01:07:37.300
was actually

01:07:37.300 --> 01:07:37.960
sat down

01:07:37.960 --> 01:07:38.880
trying to figure out

01:07:38.880 --> 01:07:39.760
how to get it

01:07:39.760 --> 01:07:40.460
to play sounds

01:07:40.460 --> 01:07:41.000
because that's

01:07:41.000 --> 01:07:41.700
kind of important

01:07:41.700 --> 01:07:41.980
when you're

01:07:41.980 --> 01:07:42.740
making a blue box.

01:07:43.860 --> 01:07:44.140
Yeah,

01:07:44.300 --> 01:07:44.640
you know,

01:07:44.960 --> 01:07:46.100
I wanted to ask

01:07:46.100 --> 01:07:46.540
you about that.

01:07:46.600 --> 01:07:46.780
I remember

01:07:46.780 --> 01:07:47.320
you had mentioned

01:07:47.320 --> 01:07:47.640
you wrote

01:07:47.640 --> 01:07:48.640
something like this

01:07:48.640 --> 01:07:49.300
a while back

01:07:49.300 --> 01:07:50.040
and I haven't

01:07:50.040 --> 01:07:50.460
really played

01:07:50.460 --> 01:07:51.180
around with sound yet

01:07:51.180 --> 01:07:51.540
so I'm going to

01:07:51.540 --> 01:07:53.280
have to find out

01:07:53.280 --> 01:07:53.900
where you found

01:07:53.900 --> 01:07:54.740
all your cool

01:07:54.740 --> 01:07:55.240
sound info.

01:07:55.340 --> 01:07:55.900
I know I found

01:07:55.900 --> 01:07:56.640
it back in the day

01:07:56.640 --> 01:07:57.080
but I don't know

01:07:57.080 --> 01:07:57.520
where anybody was.

01:07:57.520 --> 01:07:59.340
It's all MSDN

01:07:59.340 --> 01:08:00.100
and it's actually

01:08:00.100 --> 01:08:00.920
you kind of import

01:08:00.920 --> 01:08:02.520
this unsafe library

01:08:02.520 --> 01:08:04.580
and do some

01:08:04.580 --> 01:08:05.160
like slight

01:08:05.160 --> 01:08:05.840
technical

01:08:05.840 --> 01:08:06.820
tiggerly pokery

01:08:06.820 --> 01:08:08.920
and get it working

01:08:08.920 --> 01:08:10.080
but after that

01:08:10.080 --> 01:08:11.040
it works fine.

01:08:11.280 --> 01:08:12.060
It's simple

01:08:12.060 --> 01:08:12.560
and I mean

01:08:12.560 --> 01:08:13.960
the one plus

01:08:13.960 --> 01:08:14.600
about Windows Mobile

01:08:14.600 --> 01:08:15.440
is that when you're

01:08:15.440 --> 01:08:16.420
developing stuff

01:08:16.420 --> 01:08:17.360
the documentation

01:08:17.360 --> 01:08:19.500
is incredibly impressive.

01:08:20.360 --> 01:08:21.180
The one thing

01:08:21.180 --> 01:08:22.100
Microsoft does right

01:08:22.100 --> 01:08:23.260
is their MSDN.

01:08:23.480 --> 01:08:24.400
They document

01:08:24.400 --> 01:08:25.740
everything for you.

01:08:25.740 --> 01:08:28.440
I was having

01:08:28.440 --> 01:08:29.140
this conversation

01:08:29.140 --> 01:08:29.860
today with

01:08:29.860 --> 01:08:30.620
Blunderbuss

01:08:30.620 --> 01:08:31.260
and IRC

01:08:31.260 --> 01:08:32.500
about how we

01:08:32.500 --> 01:08:33.180
were comparing

01:08:33.180 --> 01:08:34.020
the PHP

01:08:34.020 --> 01:08:34.980
documentation

01:08:34.980 --> 01:08:36.040
website to the

01:08:36.040 --> 01:08:36.540
MSDN

01:08:36.540 --> 01:08:37.160
and MSDN

01:08:37.160 --> 01:08:37.760
just blows it

01:08:37.760 --> 01:08:38.560
out of the water

01:08:38.560 --> 01:08:39.560
and PHP

01:08:39.560 --> 01:08:40.220
is pretty good

01:08:40.220 --> 01:08:40.940
for documentation

01:08:40.940 --> 01:08:43.600
but it just

01:08:43.600 --> 01:08:44.380
pales in comparison

01:08:44.380 --> 01:08:44.880
to MSDN.

01:08:46.520 --> 01:08:47.880
I really wasn't

01:08:47.880 --> 01:08:48.560
all that impressed

01:08:48.560 --> 01:08:49.280
with MSDN.

01:08:49.420 --> 01:08:49.960
I guess the things

01:08:49.960 --> 01:08:50.660
I was looking for

01:08:50.660 --> 01:08:51.320
just weren't really

01:08:51.320 --> 01:08:52.620
documented all that well

01:08:52.620 --> 01:08:53.560
or maybe I just

01:08:53.560 --> 01:08:54.020
I don't know

01:08:54.020 --> 01:08:55.220
where it looks

01:08:55.220 --> 01:08:55.680
for the stuff

01:08:55.680 --> 01:08:56.080
I was talking about.

01:08:56.080 --> 01:08:56.600
Well Nathiri

01:08:56.600 --> 01:08:57.120
was sitting there

01:08:57.120 --> 01:08:57.700
on MSDN

01:08:57.700 --> 01:08:58.680
typing in

01:08:58.680 --> 01:08:59.260
search for

01:08:59.260 --> 01:09:00.140
mobile phone

01:09:00.140 --> 01:09:01.140
virus creation.

01:09:01.740 --> 01:09:02.180
Damn it.

01:09:03.240 --> 01:09:04.260
Mobile phone

01:09:04.260 --> 01:09:04.800
rootkit.

01:09:05.120 --> 01:09:05.340
Damn.

01:09:07.180 --> 01:09:08.200
I hold the mouse

01:09:08.200 --> 01:09:09.340
up to my mouth

01:09:09.340 --> 01:09:09.660
and say

01:09:09.660 --> 01:09:10.240
computer

01:09:10.240 --> 01:09:11.240
transparent

01:09:11.240 --> 01:09:11.840
aluminum

01:09:11.840 --> 01:09:14.220
and MSDN

01:09:14.220 --> 01:09:15.400
didn't do a damn thing.

01:09:15.700 --> 01:09:16.120
Well that's because

01:09:16.120 --> 01:09:16.820
you were on a Mac.

01:09:17.260 --> 01:09:17.440
Very.

01:09:19.300 --> 01:09:20.400
Oh that's right.

01:09:20.460 --> 01:09:21.220
I didn't have the button

01:09:21.220 --> 01:09:21.700
to click.

01:09:22.080 --> 01:09:22.600
Damn it.

01:09:22.900 --> 01:09:23.400
I needed to

01:09:23.400 --> 01:09:23.840
right click

01:09:23.840 --> 01:09:24.140
for that.

01:09:26.160 --> 01:09:27.640
Wasn't Scotty

01:09:27.640 --> 01:09:28.060
on a Mac

01:09:28.060 --> 01:09:28.760
for that I think?

01:09:31.100 --> 01:09:32.080
I think he was.

01:09:32.220 --> 01:09:32.840
I think back then

01:09:32.840 --> 01:09:33.200
those were the

01:09:33.200 --> 01:09:33.860
only computers

01:09:33.860 --> 01:09:34.680
that had mice.

01:09:35.780 --> 01:09:36.100
It was like

01:09:36.100 --> 01:09:36.940
1984.

01:09:37.380 --> 01:09:37.940
It was good stuff.

01:09:39.880 --> 01:09:40.720
A keyboard.

01:09:40.920 --> 01:09:41.500
How quaint.

01:09:42.780 --> 01:09:43.640
Best line ever.

01:09:44.280 --> 01:09:44.740
Yeah and then

01:09:44.740 --> 01:09:45.400
you know what?

01:09:45.820 --> 01:09:46.640
That's ridiculous.

01:09:46.920 --> 01:09:47.100
Okay.

01:09:47.800 --> 01:09:48.480
Somebody who

01:09:48.480 --> 01:09:49.280
types on a keyboard

01:09:49.280 --> 01:09:50.400
their whole life

01:09:50.400 --> 01:09:50.980
they can't type

01:09:50.980 --> 01:09:51.860
as fast as a guy

01:09:51.860 --> 01:09:52.960
who never had to

01:09:52.960 --> 01:09:53.580
use a keyboard

01:09:53.580 --> 01:09:54.260
before because

01:09:54.260 --> 01:09:54.780
everything was

01:09:54.780 --> 01:09:55.440
voice commands

01:09:55.440 --> 01:09:56.860
and now all of a sudden

01:09:56.860 --> 01:09:57.520
he's like one

01:09:57.520 --> 01:09:58.160
with the computer.

01:09:58.600 --> 01:09:59.220
He's Scotty.

01:09:59.300 --> 01:09:59.760
He can do that

01:09:59.760 --> 01:10:00.400
kind of stuff.

01:10:02.080 --> 01:10:03.140
What an asshat.

01:10:03.280 --> 01:10:03.620
I don't like that.

01:10:03.620 --> 01:10:04.940
Dude if Spock's

01:10:04.940 --> 01:10:05.480
walking over there

01:10:05.480 --> 01:10:06.040
he just has to put

01:10:06.040 --> 01:10:06.740
his hand up to the

01:10:06.740 --> 01:10:07.520
monitor and like

01:10:07.520 --> 01:10:07.740
you know

01:10:07.740 --> 01:10:08.840
controls everything.

01:10:09.240 --> 01:10:09.780
He becomes one

01:10:09.780 --> 01:10:10.520
with the interweb.

01:10:12.920 --> 01:10:13.580
He's got like

01:10:13.580 --> 01:10:13.960
some kind of

01:10:13.960 --> 01:10:14.820
crazy Jedi mind

01:10:14.820 --> 01:10:15.000
trick.

01:10:16.060 --> 01:10:16.460
Spocky

01:10:16.460 --> 01:10:17.100
mind melds.

01:10:17.160 --> 01:10:17.640
Good stuff.

01:10:19.140 --> 01:10:19.780
There you go.

01:10:21.220 --> 01:10:22.740
All right.

01:10:22.860 --> 01:10:24.020
So another thing

01:10:24.020 --> 01:10:24.560
with smartphones

01:10:24.560 --> 01:10:25.580
is the whole

01:10:25.580 --> 01:10:27.580
everyone's talking

01:10:27.580 --> 01:10:28.280
about you know

01:10:28.280 --> 01:10:28.920
new stuff.

01:10:29.060 --> 01:10:29.480
I mean we're

01:10:29.480 --> 01:10:30.140
putting out

01:10:30.140 --> 01:10:30.620
acronyms.

01:10:30.880 --> 01:10:31.320
GPRS,

01:10:31.460 --> 01:10:31.660
ED,

01:10:31.780 --> 01:10:32.340
CDMA,

01:10:32.520 --> 01:10:33.180
UMTS.

01:10:33.980 --> 01:10:34.420
Did we talk

01:10:34.420 --> 01:10:35.780
about HSPDA?

01:10:35.960 --> 01:10:36.280
I don't think

01:10:36.280 --> 01:10:36.600
we did.

01:10:39.860 --> 01:10:40.300
HSDPA.

01:10:40.500 --> 01:10:41.040
I kind of

01:10:41.040 --> 01:10:41.420
completely

01:10:41.420 --> 01:10:41.880
bumble over

01:10:41.880 --> 01:10:42.080
that.

01:10:43.180 --> 01:10:43.740
That's the

01:10:43.740 --> 01:10:44.920
old when you're

01:10:44.920 --> 01:10:45.520
talking about a

01:10:45.520 --> 01:10:45.900
smartphone.

01:10:46.180 --> 01:10:46.460
I mean a

01:10:46.460 --> 01:10:47.500
smartphone is a

01:10:47.500 --> 01:10:48.480
phone basically

01:10:48.480 --> 01:10:49.280
with you know

01:10:49.280 --> 01:10:50.080
all the interweb

01:10:50.080 --> 01:10:50.780
stuff included

01:10:50.780 --> 01:10:52.080
like email

01:10:52.080 --> 01:10:54.160
and you know

01:10:54.160 --> 01:10:54.980
internet connection

01:10:54.980 --> 01:10:55.840
web surfing.

01:10:56.640 --> 01:10:57.400
Mine has an

01:10:57.400 --> 01:10:58.380
SSH client on

01:10:58.380 --> 01:10:58.800
there and there's

01:10:58.800 --> 01:10:59.220
all kinds of

01:10:59.220 --> 01:11:00.420
like you basically

01:11:00.420 --> 01:11:01.100
have a network

01:11:01.100 --> 01:11:01.720
connection on the

01:11:01.720 --> 01:11:02.000
phone.

01:11:02.600 --> 01:11:03.240
Depending on

01:11:03.240 --> 01:11:03.720
what you're going

01:11:03.720 --> 01:11:04.960
to what kind of

01:11:04.960 --> 01:11:05.460
smartphone you're

01:11:05.460 --> 01:11:05.880
going to get

01:11:05.880 --> 01:11:06.180
you're going

01:11:06.180 --> 01:11:06.420
to get

01:11:06.420 --> 01:11:07.120
various you

01:11:07.120 --> 01:11:08.120
know speeds

01:11:08.120 --> 01:11:09.020
depending on

01:11:09.020 --> 01:11:09.640
what protocols

01:11:09.640 --> 01:11:10.060
it uses.

01:11:12.120 --> 01:11:12.440
GPRS,

01:11:12.640 --> 01:11:13.980
GPRS is 2G

01:11:13.980 --> 01:11:14.760
right isn't it?

01:11:14.860 --> 01:11:15.900
Or is that 2.5?

01:11:15.940 --> 01:11:16.360
I always get

01:11:16.360 --> 01:11:17.160
confused on the

01:11:17.160 --> 01:11:18.640
whole .5 thing.

01:11:18.860 --> 01:11:19.220
No I don't

01:11:19.220 --> 01:11:19.780
really know

01:11:19.780 --> 01:11:21.140
what they

01:11:21.140 --> 01:11:22.460
consider 2.5

01:11:22.460 --> 01:11:23.400
or 2 or

01:11:23.400 --> 01:11:23.840
whatever but

01:11:23.840 --> 01:11:24.540
it's definitely

01:11:24.540 --> 01:11:25.760
not 3G.

01:11:25.780 --> 01:11:26.460
No it's not.

01:11:27.680 --> 01:11:28.420
But I want to

01:11:28.420 --> 01:11:29.080
say that too

01:11:29.080 --> 01:11:29.980
GPRS has been

01:11:29.980 --> 01:11:30.560
around for a

01:11:30.560 --> 01:11:31.140
long time.

01:11:31.160 --> 01:11:31.660
Yes it has

01:11:31.660 --> 01:11:32.080
actually.

01:11:33.360 --> 01:11:33.920
GPRS is

01:11:33.920 --> 01:11:34.240
pretty good.

01:11:34.240 --> 01:11:35.620
GPRS averages

01:11:35.620 --> 01:11:36.320
about 60

01:11:36.320 --> 01:11:36.880
kilobits a

01:11:36.880 --> 01:11:37.280
second so

01:11:37.280 --> 01:11:37.760
you're basically

01:11:37.760 --> 01:11:38.420
going to get

01:11:38.420 --> 01:11:40.880
the maximum

01:11:40.880 --> 01:11:41.820
throughput because

01:11:41.820 --> 01:11:42.340
you know when

01:11:42.340 --> 01:11:42.640
you're talking

01:11:42.640 --> 01:11:43.160
about wireless

01:11:43.160 --> 01:11:44.000
connections and

01:11:44.000 --> 01:11:45.740
telephones you

01:11:45.740 --> 01:11:46.420
know we can

01:11:46.420 --> 01:11:47.080
talk about we're

01:11:47.080 --> 01:11:47.420
going to talk

01:11:47.420 --> 01:11:47.760
about some

01:11:47.760 --> 01:11:48.420
crazy numbers

01:11:48.420 --> 01:11:50.080
here but the

01:11:50.080 --> 01:11:51.000
lag is noticeable

01:11:51.000 --> 01:11:51.900
like there's a

01:11:51.900 --> 01:11:52.860
definite lag to

01:11:52.860 --> 01:11:53.040
it.

01:11:53.800 --> 01:11:54.660
I don't really

01:11:54.660 --> 01:11:55.000
know how to

01:11:55.000 --> 01:11:55.720
compare it but

01:11:55.720 --> 01:11:56.220
like you know

01:11:56.220 --> 01:11:56.720
when I'm talking

01:11:56.720 --> 01:11:58.100
my hip top was

01:11:58.100 --> 01:12:00.160
GPRS and like I

01:12:00.160 --> 01:12:00.980
would come back I

01:12:00.980 --> 01:12:01.500
would like tell it

01:12:01.500 --> 01:12:01.980
to load up a

01:12:01.980 --> 01:12:02.520
web page and

01:12:02.520 --> 01:12:02.920
it would take

01:12:02.920 --> 01:12:05.800
about anywhere

01:12:05.800 --> 01:12:06.420
between 30

01:12:06.420 --> 01:12:06.960
seconds to a

01:12:06.960 --> 01:12:07.360
minute for it

01:12:07.360 --> 01:12:07.900
to haul down

01:12:07.900 --> 01:12:09.120
which I mean

01:12:09.120 --> 01:12:09.720
it's good in a

01:12:09.720 --> 01:12:10.420
pinch but it

01:12:10.420 --> 01:12:12.940
was slow and

01:12:12.940 --> 01:12:13.620
even with my

01:12:13.620 --> 01:12:14.380
MDA I mean

01:12:14.380 --> 01:12:15.640
it's much

01:12:15.640 --> 01:12:16.720
better I think

01:12:16.720 --> 01:12:17.060
it's much

01:12:17.060 --> 01:12:18.260
zippier but

01:12:18.260 --> 01:12:20.320
the lag's still

01:12:20.320 --> 01:12:21.220
there and I

01:12:21.220 --> 01:12:21.680
mean it's not

01:12:21.680 --> 01:12:21.940
going to be

01:12:21.940 --> 01:12:22.520
replacing my

01:12:22.520 --> 01:12:23.260
broadband connection

01:12:23.260 --> 01:12:24.120
anytime soon.

01:12:25.520 --> 01:12:26.460
No definitely

01:12:26.460 --> 01:12:26.760
not.

01:12:26.880 --> 01:12:27.620
Yeah well since

01:12:27.620 --> 01:12:27.940
we're talking

01:12:27.940 --> 01:12:28.700
about MDAs

01:12:28.700 --> 01:12:30.080
MDAs and

01:12:30.080 --> 01:12:32.260
no you're

01:12:32.260 --> 01:12:33.000
just CDMA

01:12:33.000 --> 01:12:33.360
why am I

01:12:33.360 --> 01:12:33.800
thinking that

01:12:33.800 --> 01:12:37.260
MDAs and

01:12:37.260 --> 01:12:37.860
a lot of

01:12:37.860 --> 01:12:39.140
other GSM

01:12:39.140 --> 01:12:39.920
phones now in

01:12:39.920 --> 01:12:40.220
the United

01:12:40.220 --> 01:12:40.700
States are

01:12:40.700 --> 01:12:41.280
actually using

01:12:41.280 --> 01:12:42.180
EDGE which

01:12:42.180 --> 01:12:43.400
I did not

01:12:43.400 --> 01:12:43.920
write down the

01:12:43.920 --> 01:12:44.540
acronym and I'm

01:12:44.540 --> 01:12:45.020
a moron.

01:12:46.040 --> 01:12:46.720
EDGE is like

01:12:46.720 --> 01:12:47.420
something like

01:12:47.420 --> 01:12:48.700
extended data for

01:12:48.700 --> 01:12:50.480
GPRS something

01:12:50.480 --> 01:12:51.160
I don't know

01:12:51.160 --> 01:12:53.000
it's basically

01:12:53.000 --> 01:12:54.800
it's GPRS with

01:12:54.800 --> 01:12:55.560
a speed boost on

01:12:55.560 --> 01:12:56.100
it and that can

01:12:56.100 --> 01:12:56.680
go up to all

01:12:56.680 --> 01:12:57.120
the way up to

01:12:57.120 --> 01:12:58.640
236.8

01:12:58.640 --> 01:12:59.220
kilobytes a

01:12:59.220 --> 01:13:00.220
second theoretically

01:13:00.220 --> 01:13:02.880
I did some

01:13:02.880 --> 01:13:03.600
speed tests with

01:13:03.600 --> 01:13:04.800
my edge

01:13:04.800 --> 01:13:06.340
connection and

01:13:06.340 --> 01:13:07.100
I think I

01:13:07.100 --> 01:13:07.880
averaged on a

01:13:07.880 --> 01:13:08.500
download about

01:13:08.500 --> 01:13:09.500
20 kilobytes a

01:13:09.500 --> 01:13:11.120
second so I

01:13:11.120 --> 01:13:11.560
don't know what

01:13:11.560 --> 01:13:11.940
did that average

01:13:11.940 --> 01:13:12.400
out to about

01:13:12.400 --> 01:13:13.540
160 kilobytes

01:13:13.540 --> 01:13:16.820
and that was in

01:13:16.820 --> 01:13:17.180
the middle of

01:13:17.180 --> 01:13:17.940
downtown Boston

01:13:17.940 --> 01:13:19.160
so that's

01:13:19.160 --> 01:13:19.980
probably as good

01:13:19.980 --> 01:13:20.440
as it's going to

01:13:20.440 --> 01:13:21.140
get for you.

01:13:24.480 --> 01:13:25.540
EVDO which is

01:13:25.540 --> 01:13:26.220
not GSM

01:13:26.220 --> 01:13:28.020
but GPRS and

01:13:28.020 --> 01:13:29.060
EDGE are all

01:13:29.060 --> 01:13:29.860
GSM based.

01:13:30.920 --> 01:13:32.800
EVDO which is

01:13:32.800 --> 01:13:33.860
currently in use

01:13:33.860 --> 01:13:34.320
in the United

01:13:34.320 --> 01:13:35.360
States and I

01:13:35.360 --> 01:13:35.720
think that's

01:13:35.720 --> 01:13:36.380
about it right?

01:13:38.620 --> 01:13:39.920
I thought that

01:13:39.920 --> 01:13:40.700
Japan used it.

01:13:40.780 --> 01:13:41.380
I don't know why

01:13:41.380 --> 01:13:42.900
I think that but

01:13:42.900 --> 01:13:46.120
I don't know.

01:13:46.320 --> 01:13:48.640
I think WCDMA is

01:13:48.640 --> 01:13:49.480
something completely

01:13:49.480 --> 01:13:49.820
different.

01:13:50.540 --> 01:13:51.360
Who knows?

01:13:51.360 --> 01:13:52.840
I don't know.

01:13:52.840 --> 01:13:55.080
I just googled

01:13:55.080 --> 01:13:56.060
Japan and EVDO

01:13:56.060 --> 01:13:56.540
and it's just

01:13:56.540 --> 01:13:57.100
something about

01:13:57.100 --> 01:13:58.840
Japan rolls out

01:13:58.840 --> 01:14:00.060
new EVDO

01:14:00.060 --> 01:14:00.580
phones.

01:14:01.180 --> 01:14:01.880
Oh perhaps I'm

01:14:01.880 --> 01:14:02.100
wrong.

01:14:03.560 --> 01:14:04.940
Anyway EVDO is

01:14:04.940 --> 01:14:07.120
a CDMA base

01:14:07.120 --> 01:14:07.740
which is a

01:14:07.740 --> 01:14:08.840
code division

01:14:08.840 --> 01:14:09.560
multiple access.

01:14:10.700 --> 01:14:11.820
That's just a

01:14:11.820 --> 01:14:12.640
meaningless real

01:14:12.640 --> 01:14:13.420
acronym unless you're

01:14:13.420 --> 01:14:14.000
really getting into

01:14:14.000 --> 01:14:14.740
cell phone networks.

01:14:14.740 --> 01:14:16.900
EVDO goes up to

01:14:16.900 --> 01:14:18.000
about 2.5

01:14:18.000 --> 01:14:18.720
megabits a

01:14:18.720 --> 01:14:20.540
second download

01:14:20.540 --> 01:14:21.660
and 154

01:14:21.660 --> 01:14:22.320
kilobits a

01:14:22.320 --> 01:14:23.020
second upload.

01:14:24.340 --> 01:14:25.260
EDGE on the

01:14:25.260 --> 01:14:26.060
other hand has

01:14:26.060 --> 01:14:26.780
20 kilobytes

01:14:26.780 --> 01:14:27.940
both ways or so.

01:14:28.320 --> 01:14:29.180
20 kilobytes

01:14:29.180 --> 01:14:29.680
both ways.

01:14:30.660 --> 01:14:31.500
My elite speed

01:14:31.500 --> 01:14:31.880
tests.

01:14:32.360 --> 01:14:32.660
I think I

01:14:32.660 --> 01:14:33.940
actually I

01:14:33.940 --> 01:14:34.920
think when I

01:14:34.920 --> 01:14:35.520
uploaded bin

01:14:35.520 --> 01:14:36.600
rev 178 I

01:14:36.600 --> 01:14:37.980
uploaded it via my

01:14:37.980 --> 01:14:38.460
EDGE headset.

01:14:38.700 --> 01:14:39.380
My EDGE

01:14:39.380 --> 01:14:39.660
headset.

01:14:40.540 --> 01:14:41.260
Let's try it

01:14:41.260 --> 01:14:41.420
again.

01:14:41.540 --> 01:14:42.260
My EDGE

01:14:42.260 --> 01:14:43.620
handset.

01:14:44.580 --> 01:14:45.500
Boy I guess I'm

01:14:45.500 --> 01:14:45.900
getting tired.

01:14:47.640 --> 01:14:48.800
Yeah I think

01:14:48.800 --> 01:14:49.560
I think upload

01:14:49.560 --> 01:14:50.080
speeds were

01:14:50.080 --> 01:14:50.880
slightly slower

01:14:50.880 --> 01:14:51.500
but I think it

01:14:51.500 --> 01:14:54.440
was actually the

01:14:54.440 --> 01:14:55.200
ironic part is

01:14:55.200 --> 01:14:56.060
it's faster than

01:14:56.060 --> 01:14:56.680
my DSL

01:14:56.680 --> 01:14:57.480
connection on the

01:14:57.480 --> 01:14:58.340
upload side for

01:14:58.340 --> 01:14:59.080
throughput because

01:14:59.080 --> 01:15:00.000
my upload on

01:15:00.000 --> 01:15:03.580
my DSL at home

01:15:03.580 --> 01:15:04.580
is only 128

01:15:04.580 --> 01:15:05.500
kilobits.

01:15:06.700 --> 01:15:07.340
So my EDGE

01:15:07.340 --> 01:15:08.620
I can upload an

01:15:08.620 --> 01:15:09.560
episode faster over

01:15:09.560 --> 01:15:10.400
my cell phone than

01:15:10.400 --> 01:15:12.240
my DSL at home.

01:15:12.260 --> 01:15:12.980
my DSL connection

01:15:12.980 --> 01:15:13.460
which I found

01:15:13.460 --> 01:15:14.100
kind of sad.

01:15:17.080 --> 01:15:17.780
That's crazy.

01:15:18.380 --> 01:15:18.560
Yeah.

01:15:19.700 --> 01:15:20.100
Another

01:15:20.100 --> 01:15:20.560
standard out

01:15:20.560 --> 01:15:20.900
there is

01:15:20.900 --> 01:15:22.800
UMTS which is

01:15:22.800 --> 01:15:26.060
not deployed in

01:15:26.060 --> 01:15:26.600
the United States

01:15:26.600 --> 01:15:27.680
yet but Singular

01:15:27.680 --> 01:15:28.600
is touting that as

01:15:28.600 --> 01:15:29.320
their new protocol

01:15:29.320 --> 01:15:29.760
and they said

01:15:29.760 --> 01:15:30.060
they're going to

01:15:30.060 --> 01:15:30.460
come up with

01:15:30.460 --> 01:15:31.480
stuff in 2007.

01:15:31.880 --> 01:15:32.280
They're already

01:15:32.280 --> 01:15:33.260
selling handsets

01:15:33.260 --> 01:15:33.660
for it.

01:15:34.720 --> 01:15:35.340
We're talking

01:15:35.340 --> 01:15:36.200
about the HTC

01:15:36.200 --> 01:15:37.100
Titan and that's

01:15:37.100 --> 01:15:40.320
their 8525 I

01:15:40.320 --> 01:15:40.640
think that's

01:15:40.640 --> 01:15:41.020
their model.

01:15:41.020 --> 01:15:42.280
and that's

01:15:42.280 --> 01:15:42.680
a new thing

01:15:42.680 --> 01:15:43.180
and that has

01:15:43.180 --> 01:15:44.340
UMTS support.

01:15:45.760 --> 01:15:45.880
Hmm?

01:15:47.140 --> 01:15:47.600
I said

01:15:47.600 --> 01:15:48.060
no no that

01:15:48.060 --> 01:15:48.800
sounds I think

01:15:48.800 --> 01:15:49.180
that sounds

01:15:49.180 --> 01:15:50.140
right 8525.

01:15:50.720 --> 01:15:51.220
Yeah I think

01:15:51.220 --> 01:15:52.160
the old one

01:15:52.160 --> 01:15:52.420
was the

01:15:52.420 --> 01:15:52.940
8125.

01:15:54.380 --> 01:15:55.260
UMTS supports

01:15:55.260 --> 01:15:56.660
up to 11

01:15:56.660 --> 01:15:57.540
megabits a second

01:15:57.540 --> 01:16:00.440
down and up

01:16:00.440 --> 01:16:01.360
to 384

01:16:01.360 --> 01:16:02.040
kilobits a second

01:16:02.040 --> 01:16:02.400
up.

01:16:03.000 --> 01:16:04.800
So I've got to

01:16:04.800 --> 01:16:05.360
say that's

01:16:05.360 --> 01:16:05.940
pretty impressive.

01:16:05.940 --> 01:16:07.360
and eventually

01:16:07.360 --> 01:16:07.820
it might go

01:16:07.820 --> 01:16:09.840
up to 3.6

01:16:09.840 --> 01:16:10.560
megabits a second

01:16:10.560 --> 01:16:10.840
up.

01:16:11.220 --> 01:16:13.060
So hey I beat

01:16:13.060 --> 01:16:13.460
the hell out of

01:16:13.460 --> 01:16:14.000
my edge connection

01:16:14.000 --> 01:16:14.560
what can I say?

01:16:16.700 --> 01:16:18.060
Also there's

01:16:18.060 --> 01:16:20.180
HSDPA which I

01:16:20.180 --> 01:16:20.720
don't think is in

01:16:20.720 --> 01:16:21.320
the United States.

01:16:21.460 --> 01:16:22.140
I haven't heard

01:16:22.140 --> 01:16:22.380
of it.

01:16:22.440 --> 01:16:23.960
I heard Moo

01:16:23.960 --> 01:16:24.680
talking about it

01:16:24.680 --> 01:16:25.560
on IRC a lot

01:16:25.560 --> 01:16:26.100
over in Britain

01:16:26.100 --> 01:16:27.400
and I don't

01:16:27.400 --> 01:16:28.120
think it's even

01:16:28.120 --> 01:16:28.880
released over there

01:16:28.880 --> 01:16:29.120
yet.

01:16:29.700 --> 01:16:30.760
It's coming

01:16:30.760 --> 01:16:31.420
though so who

01:16:31.420 --> 01:16:31.660
knows.

01:16:31.660 --> 01:16:33.960
The current

01:16:33.960 --> 01:16:35.000
AHSPDA

01:16:35.000 --> 01:16:36.020
deployment support

01:16:36.020 --> 01:16:37.560
101.8

01:16:37.560 --> 01:16:38.360
megabits or

01:16:38.360 --> 01:16:39.020
3.6

01:16:39.020 --> 01:16:39.860
megabits down

01:16:39.860 --> 01:16:41.940
and actually

01:16:41.940 --> 01:16:42.620
further steps

01:16:42.620 --> 01:16:43.120
are going to

01:16:43.120 --> 01:16:43.840
come out soon

01:16:43.840 --> 01:16:45.880
to do 14.4

01:16:45.880 --> 01:16:46.600
megabits both

01:16:46.600 --> 01:16:47.620
ways which is

01:16:47.620 --> 01:16:48.720
just crazy.

01:16:50.720 --> 01:16:51.520
I remember

01:16:51.520 --> 01:16:51.980
when I thought

01:16:51.980 --> 01:16:52.340
I was hot

01:16:52.340 --> 01:16:52.720
shit when I

01:16:52.720 --> 01:16:53.100
had a 10

01:16:53.100 --> 01:16:53.440
megabit

01:16:53.440 --> 01:16:53.720
ethernet

01:16:53.720 --> 01:16:54.100
connection.

01:16:56.860 --> 01:16:57.580
Yeah not

01:16:57.580 --> 01:16:58.160
anymore man

01:16:58.160 --> 01:16:58.600
it's no big

01:16:58.600 --> 01:16:58.880
deal.

01:16:59.440 --> 01:16:59.640
Yeah.

01:17:00.320 --> 01:17:01.080
Now you look

01:17:01.080 --> 01:17:01.340
at 10

01:17:01.340 --> 01:17:01.620
megabit

01:17:01.620 --> 01:17:02.000
cards and

01:17:02.000 --> 01:17:02.480
go crap

01:17:02.480 --> 01:17:03.000
I can't

01:17:03.000 --> 01:17:03.340
sell this

01:17:03.340 --> 01:17:03.640
anywhere.

01:17:06.760 --> 01:17:07.340
Yeah I'm

01:17:07.340 --> 01:17:07.740
looking at

01:17:07.740 --> 01:17:08.520
sorry I'm

01:17:08.520 --> 01:17:08.920
looking at

01:17:08.920 --> 01:17:09.900
HSDPA

01:17:09.900 --> 01:17:10.960
on Wikipedia

01:17:10.960 --> 01:17:12.020
and they

01:17:12.020 --> 01:17:12.620
show the

01:17:12.620 --> 01:17:13.720
category 10

01:17:13.720 --> 01:17:14.220
the fastest

01:17:14.220 --> 01:17:15.180
is max

01:17:15.180 --> 01:17:15.720
data speed

01:17:15.720 --> 01:17:16.700
14.4

01:17:16.700 --> 01:17:17.200
megabits

01:17:17.200 --> 01:17:17.700
per second.

01:17:18.620 --> 01:17:18.780
Do you

01:17:18.780 --> 01:17:19.220
imagine all

01:17:19.220 --> 01:17:19.580
the porn

01:17:19.580 --> 01:17:19.820
you can

01:17:19.820 --> 01:17:20.120
possibly

01:17:20.120 --> 01:17:20.380
download

01:17:20.380 --> 01:17:20.740
for that?

01:17:21.780 --> 01:17:22.160
Oh yeah

01:17:22.160 --> 01:17:22.500
you could

01:17:22.500 --> 01:17:23.000
have like

01:17:23.000 --> 01:17:23.440
four windows

01:17:23.440 --> 01:17:23.820
with porn

01:17:23.820 --> 01:17:24.400
open easily.

01:17:29.520 --> 01:17:30.140
I'm pretty

01:17:30.140 --> 01:17:30.660
sure more

01:17:30.660 --> 01:17:31.000
than a few

01:17:31.000 --> 01:17:31.360
people are

01:17:31.360 --> 01:17:31.720
actually saying

01:17:31.720 --> 01:17:32.900
what good

01:17:32.900 --> 01:17:33.460
does this

01:17:33.460 --> 01:17:34.000
do on my

01:17:34.000 --> 01:17:34.340
phone?

01:17:34.540 --> 01:17:35.180
But you

01:17:35.180 --> 01:17:36.240
do surf

01:17:36.240 --> 01:17:36.500
the web

01:17:36.500 --> 01:17:36.780
on your

01:17:36.780 --> 01:17:37.060
phone.

01:17:38.060 --> 01:17:38.720
Pulling down

01:17:38.720 --> 01:17:39.160
email you

01:17:39.160 --> 01:17:39.380
can pull

01:17:39.380 --> 01:17:39.860
down like

01:17:39.860 --> 01:17:40.880
if you

01:17:40.880 --> 01:17:41.720
watch TV

01:17:41.720 --> 01:17:42.080
you see

01:17:42.080 --> 01:17:42.520
those stupid

01:17:42.520 --> 01:17:43.060
little sprint

01:17:43.060 --> 01:17:43.520
ads when

01:17:43.520 --> 01:17:43.960
they're comparing

01:17:43.960 --> 01:17:44.520
themselves to

01:17:44.520 --> 01:17:45.060
singular going

01:17:45.060 --> 01:17:46.040
look sprint is

01:17:46.040 --> 01:17:46.780
so much faster

01:17:46.780 --> 01:17:47.400
never mind we

01:17:47.400 --> 01:17:47.700
don't have

01:17:47.700 --> 01:17:48.100
coverage

01:17:48.100 --> 01:17:48.740
anywhere.

01:17:48.740 --> 01:17:49.120
But

01:17:49.120 --> 01:17:53.140
what really

01:17:53.140 --> 01:17:53.700
pisses me off

01:17:53.700 --> 01:17:54.260
about sprint

01:17:54.260 --> 01:17:55.220
have you seen

01:17:55.220 --> 01:17:55.840
these commercials

01:17:55.840 --> 01:17:56.520
is you're

01:17:56.520 --> 01:17:56.860
using the

01:17:56.860 --> 01:17:57.180
guy from

01:17:57.180 --> 01:17:57.780
office space

01:17:57.780 --> 01:17:58.040
now.

01:17:58.820 --> 01:17:59.020
And I'm

01:17:59.020 --> 01:17:59.540
like I've

01:17:59.540 --> 01:17:59.920
lost all

01:17:59.920 --> 01:18:00.460
respect for

01:18:00.460 --> 01:18:00.660
you.

01:18:01.940 --> 01:18:02.360
Oh really?

01:18:02.480 --> 01:18:02.820
I haven't

01:18:02.820 --> 01:18:03.240
seen that.

01:18:03.880 --> 01:18:04.060
Yeah.

01:18:04.680 --> 01:18:05.440
I don't

01:18:05.440 --> 01:18:05.880
actually have

01:18:05.880 --> 01:18:06.780
TV so I

01:18:06.780 --> 01:18:07.040
can't.

01:18:07.120 --> 01:18:07.500
Oh you're

01:18:07.500 --> 01:18:07.720
lame.

01:18:08.220 --> 01:18:10.560
I actually

01:18:10.560 --> 01:18:11.860
have everything

01:18:11.860 --> 01:18:12.780
TV-ed so it's

01:18:12.780 --> 01:18:13.160
sort of like I

01:18:13.160 --> 01:18:13.520
don't watch

01:18:13.520 --> 01:18:14.180
commercials but I

01:18:14.180 --> 01:18:14.940
slowed it down

01:18:14.940 --> 01:18:15.440
when I saw the

01:18:15.440 --> 01:18:15.880
close movie.

01:18:16.120 --> 01:18:16.880
Oh cool I

01:18:16.880 --> 01:18:17.200
wonder what the

01:18:17.200 --> 01:18:17.720
hill he's in.

01:18:17.840 --> 01:18:18.640
Oh he's working

01:18:18.640 --> 01:18:19.120
for sprint?

01:18:19.340 --> 01:18:20.120
Oh fuck him.

01:18:20.120 --> 01:18:22.800
So that may

01:18:22.800 --> 01:18:23.260
be sad.

01:18:25.020 --> 01:18:25.660
The main

01:18:25.660 --> 01:18:26.040
character.

01:18:26.220 --> 01:18:26.960
I'm drawing a

01:18:26.960 --> 01:18:27.380
blank on his

01:18:27.380 --> 01:18:27.580
name.

01:18:27.660 --> 01:18:28.060
I can't even

01:18:28.060 --> 01:18:28.600
remember it.

01:18:30.640 --> 01:18:31.460
In the movie

01:18:31.460 --> 01:18:33.440
Peter Gibbons?

01:18:33.540 --> 01:18:34.440
Peter yes that's

01:18:34.440 --> 01:18:34.620
it.

01:18:36.700 --> 01:18:37.260
See if they had

01:18:37.260 --> 01:18:38.120
like Lumberg on

01:18:38.120 --> 01:18:38.800
their advertising

01:18:38.800 --> 01:18:39.280
sprint I'd be

01:18:39.280 --> 01:18:39.960
like yeah.

01:18:40.960 --> 01:18:41.660
Go do it.

01:18:44.040 --> 01:18:44.600
But whatever.

01:18:45.540 --> 01:18:45.800
Yeah I'm

01:18:45.800 --> 01:18:46.280
looking at some

01:18:46.280 --> 01:18:46.840
sprint commercials

01:18:46.840 --> 01:18:47.560
on YouTube but

01:18:47.560 --> 01:18:48.100
I don't see that

01:18:48.100 --> 01:18:48.580
guy on it.

01:18:48.580 --> 01:18:50.680
I don't know

01:18:50.680 --> 01:18:51.000
he's talking

01:18:51.000 --> 01:18:52.560
about this is

01:18:52.560 --> 01:18:53.020
the other thing

01:18:53.020 --> 01:18:53.400
that gets me.

01:18:53.480 --> 01:18:53.840
They're talking

01:18:53.840 --> 01:18:54.400
about how they

01:18:54.400 --> 01:18:55.360
moved their

01:18:55.360 --> 01:18:57.300
free nights and

01:18:57.300 --> 01:18:58.420
weekends to 7pm

01:18:58.420 --> 01:19:00.140
for us and

01:19:00.140 --> 01:19:01.280
that just really

01:19:01.280 --> 01:19:02.020
that totally

01:19:02.020 --> 01:19:03.080
reeks of 1984

01:19:03.080 --> 01:19:04.720
because I

01:19:04.720 --> 01:19:05.400
remember when

01:19:05.400 --> 01:19:06.060
like my parents

01:19:06.060 --> 01:19:06.640
got their first

01:19:06.640 --> 01:19:07.180
cell phone and

01:19:07.180 --> 01:19:07.540
they had the

01:19:07.540 --> 01:19:08.020
free nights and

01:19:08.020 --> 01:19:08.580
weekends on it

01:19:08.580 --> 01:19:09.460
they started at

01:19:09.460 --> 01:19:10.820
7pm and then

01:19:10.820 --> 01:19:11.300
they creeped it

01:19:11.300 --> 01:19:12.360
up to 8 and

01:19:12.360 --> 01:19:12.860
then they creeped

01:19:12.860 --> 01:19:13.380
it up to 9.

01:19:13.480 --> 01:19:13.840
Now they're

01:19:13.840 --> 01:19:14.460
moving us back

01:19:14.460 --> 01:19:15.540
to 7 and

01:19:15.540 --> 01:19:16.000
thinking they're

01:19:16.000 --> 01:19:16.520
doing us a

01:19:16.520 --> 01:19:16.760
favor.

01:19:16.760 --> 01:19:18.340
I mean

01:19:18.340 --> 01:19:19.120
seriously I

01:19:19.120 --> 01:19:19.480
expect to get

01:19:19.480 --> 01:19:19.960
a little memo

01:19:19.960 --> 01:19:20.340
in the mail

01:19:20.340 --> 01:19:20.760
saying my

01:19:20.760 --> 01:19:21.440
chocolate ration

01:19:21.440 --> 01:19:21.940
has gone up

01:19:21.940 --> 01:19:22.720
to 3 grams or

01:19:22.720 --> 01:19:23.000
something.

01:19:23.980 --> 01:19:24.420
Nice.

01:19:30.120 --> 01:19:30.940
But yeah

01:19:30.940 --> 01:19:31.760
there's my

01:19:31.760 --> 01:19:32.420
tirade against

01:19:32.420 --> 01:19:32.820
sprint here.

01:19:33.360 --> 01:19:34.140
But like so

01:19:34.140 --> 01:19:35.120
like these

01:19:35.120 --> 01:19:35.680
fast speeds

01:19:35.680 --> 01:19:35.980
you're like

01:19:35.980 --> 01:19:36.600
oh no just

01:19:36.600 --> 01:19:37.060
this to my

01:19:37.060 --> 01:19:37.460
cell phone.

01:19:37.560 --> 01:19:37.800
One of the

01:19:37.800 --> 01:19:38.300
cool things

01:19:38.300 --> 01:19:39.040
about like I

01:19:39.040 --> 01:19:40.160
know that

01:19:40.160 --> 01:19:41.260
my hip top

01:19:41.260 --> 01:19:41.800
didn't do it

01:19:41.800 --> 01:19:42.360
and this was

01:19:42.360 --> 01:19:42.700
one of the

01:19:42.700 --> 01:19:43.120
things that I

01:19:43.120 --> 01:19:43.580
constantly

01:19:43.580 --> 01:19:44.340
waited for when

01:19:44.340 --> 01:19:45.180
I was sitting

01:19:45.180 --> 01:19:45.720
on my train

01:19:45.720 --> 01:19:46.480
diddling with

01:19:46.480 --> 01:19:47.020
my hip top

01:19:47.020 --> 01:19:48.080
and that

01:19:48.080 --> 01:19:48.480
just sounded

01:19:48.480 --> 01:19:48.980
really bad

01:19:48.980 --> 01:19:49.280
but we won't

01:19:49.280 --> 01:19:49.760
get into that.

01:19:50.540 --> 01:19:50.980
Diddle yourself

01:19:50.980 --> 01:19:51.400
on the train

01:19:51.400 --> 01:19:51.820
that's cool.

01:19:52.560 --> 01:19:52.780
Yeah.

01:19:53.340 --> 01:19:53.860
I bet you

01:19:53.860 --> 01:19:54.260
could do it.

01:19:54.520 --> 01:19:54.960
Actually one of

01:19:54.960 --> 01:19:55.360
the first thing

01:19:55.360 --> 01:19:55.760
I did when I

01:19:55.760 --> 01:19:56.040
get with a

01:19:56.040 --> 01:19:56.620
hip top was

01:19:56.620 --> 01:19:57.780
dude I can

01:19:57.780 --> 01:19:58.540
surf porn

01:19:58.540 --> 01:19:59.280
anywhere and

01:19:59.280 --> 01:19:59.760
I like loaded

01:19:59.760 --> 01:20:00.300
up like this

01:20:00.300 --> 01:20:00.880
little cheesy

01:20:00.880 --> 01:20:01.600
porn site and

01:20:01.600 --> 01:20:02.060
I showed it to

01:20:02.060 --> 01:20:02.640
all my roommates

01:20:02.640 --> 01:20:02.880
and they're

01:20:02.880 --> 01:20:03.800
like that you

01:20:03.800 --> 01:20:04.580
can get porn

01:20:04.580 --> 01:20:05.100
anywhere.

01:20:06.880 --> 01:20:07.680
Ah college.

01:20:08.860 --> 01:20:09.540
Very nice.

01:20:10.480 --> 01:20:11.040
But like the

01:20:11.040 --> 01:20:12.380
newer phones out

01:20:12.380 --> 01:20:12.820
there you can

01:20:12.820 --> 01:20:13.480
actually plug

01:20:13.480 --> 01:20:13.920
them into your

01:20:13.920 --> 01:20:14.820
computer and use

01:20:14.820 --> 01:20:15.300
them as a

01:20:15.300 --> 01:20:15.580
modem.

01:20:16.380 --> 01:20:16.840
So like for

01:20:16.840 --> 01:20:17.880
example like when

01:20:17.880 --> 01:20:18.560
I take the

01:20:18.560 --> 01:20:19.260
commuter rail back

01:20:19.260 --> 01:20:19.720
and forth from

01:20:19.720 --> 01:20:20.920
work so on the

01:20:20.920 --> 01:20:21.300
train in the

01:20:21.300 --> 01:20:21.760
morning on the

01:20:21.760 --> 01:20:22.060
train in the

01:20:22.060 --> 01:20:22.740
afternoon you'll

01:20:22.740 --> 01:20:23.280
see me at one

01:20:23.280 --> 01:20:23.960
of the desks with

01:20:23.960 --> 01:20:24.720
my phone hooked

01:20:24.720 --> 01:20:25.080
up to my

01:20:25.080 --> 01:20:26.460
laptop and

01:20:26.460 --> 01:20:26.980
chugging away

01:20:26.980 --> 01:20:28.200
there and it's

01:20:28.200 --> 01:20:28.660
amazing.

01:20:28.940 --> 01:20:29.500
It's just the

01:20:29.500 --> 01:20:30.120
fact that I can

01:20:30.120 --> 01:20:30.880
surf on the

01:20:30.880 --> 01:20:31.980
train do

01:20:31.980 --> 01:20:32.600
anywhere catch up

01:20:32.600 --> 01:20:33.280
on my email

01:20:33.280 --> 01:20:35.180
you know upload

01:20:35.180 --> 01:20:35.960
a bin rev episode

01:20:35.960 --> 01:20:36.920
or check the

01:20:36.920 --> 01:20:37.780
bin rev email or

01:20:37.780 --> 01:20:38.220
check my own

01:20:38.220 --> 01:20:39.460
email and surf

01:20:39.460 --> 01:20:40.420
the web or I

01:20:40.420 --> 01:20:41.020
mean do whatever

01:20:41.020 --> 01:20:41.580
you want the

01:20:41.580 --> 01:20:42.040
full fledged

01:20:42.040 --> 01:20:42.560
interconnection.

01:20:42.760 --> 01:20:43.360
It's kind of

01:20:43.360 --> 01:20:43.900
slow I will

01:20:43.900 --> 01:20:44.160
admit.

01:20:44.160 --> 01:20:45.560
I mean it's

01:20:45.560 --> 01:20:46.980
not pulling down

01:20:46.980 --> 01:20:47.580
uber fast

01:20:47.580 --> 01:20:48.720
internet but it

01:20:48.720 --> 01:20:50.620
works and I

01:20:50.620 --> 01:20:52.060
think mine

01:20:52.060 --> 01:20:53.040
supports natively

01:20:53.040 --> 01:20:54.340
but you're you

01:20:54.340 --> 01:20:55.000
just have to break

01:20:55.000 --> 01:20:56.280
Verizon's rules to

01:20:56.280 --> 01:20:56.860
get yours.

01:20:56.860 --> 01:21:01.420
What do you mean

01:21:01.420 --> 01:21:01.980
exactly?

01:21:02.800 --> 01:21:03.920
Well you're

01:21:03.920 --> 01:21:04.680
tethering or

01:21:04.680 --> 01:21:05.680
using your phone

01:21:05.680 --> 01:21:06.220
as a modem

01:21:06.220 --> 01:21:06.920
because Verizon

01:21:06.920 --> 01:21:07.620
says no no?

01:21:08.680 --> 01:21:09.480
Right yeah they

01:21:09.480 --> 01:21:10.340
don't allow it but

01:21:10.340 --> 01:21:10.880
there's a program

01:21:10.880 --> 01:21:11.720
called I think it's

01:21:11.720 --> 01:21:13.420
called PDA net and

01:21:13.420 --> 01:21:14.000
you can download

01:21:14.000 --> 01:21:14.720
that and I think

01:21:14.720 --> 01:21:15.460
they want like 25

01:21:15.460 --> 01:21:16.180
bucks for it and

01:21:16.180 --> 01:21:17.000
it re-enables

01:21:17.000 --> 01:21:17.840
everything for you

01:21:17.840 --> 01:21:18.560
so you can use it.

01:21:18.960 --> 01:21:19.660
You're not supposed

01:21:19.660 --> 01:21:21.120
to but honestly you

01:21:21.120 --> 01:21:21.620
know what you want

01:21:21.620 --> 01:21:22.380
to charge me 45

01:21:22.380 --> 01:21:23.380
bucks a month for

01:21:23.380 --> 01:21:25.380
unlimited data you

01:21:25.380 --> 01:21:26.360
know you've got to

01:21:26.360 --> 01:21:27.020
expect people are

01:21:27.020 --> 01:21:27.660
going to use that

01:21:27.660 --> 01:21:28.980
and from what I've

01:21:28.980 --> 01:21:29.920
heard the way that

01:21:29.920 --> 01:21:30.940
they detect to see

01:21:30.940 --> 01:21:32.440
who's using this is

01:21:32.440 --> 01:21:33.020
they just give you

01:21:33.020 --> 01:21:34.180
this artificial cap of

01:21:34.180 --> 01:21:35.000
how much data you can

01:21:35.000 --> 01:21:36.340
use per month and

01:21:36.340 --> 01:21:37.180
go over it.

01:21:37.280 --> 01:21:38.480
Oh what's that?

01:21:39.200 --> 01:21:40.280
Two gigabytes I think

01:21:40.280 --> 01:21:40.600
it was.

01:21:41.540 --> 01:21:43.440
I thought it was I

01:21:43.440 --> 01:21:44.340
thought it was five

01:21:44.340 --> 01:21:46.460
gigs or five

01:21:46.460 --> 01:21:47.900
gigs three months in a

01:21:47.900 --> 01:21:50.120
row and then ten

01:21:50.120 --> 01:21:51.520
gigs one month or

01:21:51.520 --> 01:21:52.200
something like that.

01:21:52.200 --> 01:21:55.100
I don't know in any

01:21:55.100 --> 01:21:56.400
case it's really not

01:21:56.400 --> 01:21:57.160
that much data when

01:21:57.160 --> 01:21:58.220
you think about for

01:21:58.220 --> 01:21:58.880
a whole month but

01:21:58.880 --> 01:21:59.520
then again you know

01:21:59.520 --> 01:22:02.560
what I use I actually

01:22:02.560 --> 01:22:03.840
do have a PC card

01:22:03.840 --> 01:22:06.320
and they have the

01:22:06.320 --> 01:22:07.160
same limitations on

01:22:07.160 --> 01:22:08.640
that and I don't

01:22:08.640 --> 01:22:09.840
even come close any

01:22:09.840 --> 01:22:10.760
month going over

01:22:10.760 --> 01:22:11.400
because I'm just

01:22:11.400 --> 01:22:12.520
using it for SSH

01:22:12.520 --> 01:22:13.240
and you know some

01:22:13.240 --> 01:22:14.640
other kind of database

01:22:14.640 --> 01:22:15.600
work and things like

01:22:15.600 --> 01:22:16.220
that stuff that's

01:22:16.220 --> 01:22:17.300
really not bandwidth

01:22:17.300 --> 01:22:19.200
intensive so I never

01:22:19.200 --> 01:22:20.000
come close so it works

01:22:20.000 --> 01:22:20.740
pretty well for me.

01:22:20.740 --> 01:22:22.700
I think Robert X

01:22:22.700 --> 01:22:24.040
cringely decided to

01:22:24.040 --> 01:22:24.800
put a test because he

01:22:24.800 --> 01:22:26.360
has a PC card and he

01:22:26.360 --> 01:22:27.920
just he basically he

01:22:27.920 --> 01:22:28.860
found this program

01:22:28.860 --> 01:22:29.700
that you know

01:22:29.700 --> 01:22:30.480
meters your internet

01:22:30.480 --> 01:22:31.540
access and keeps track

01:22:31.540 --> 01:22:34.040
of it and he just

01:22:34.040 --> 01:22:35.020
set it up over one

01:22:35.020 --> 01:22:36.300
month just to grab

01:22:36.300 --> 01:22:38.320
his email and he

01:22:38.320 --> 01:22:39.040
went over the limit

01:22:39.040 --> 01:22:40.260
whatever the limit

01:22:40.260 --> 01:22:41.180
was I'm not sure if

01:22:41.180 --> 01:22:41.940
it was five or two

01:22:41.940 --> 01:22:44.280
and he got like and

01:22:44.280 --> 01:22:45.140
he just said I just

01:22:45.140 --> 01:22:46.080
use this for my email

01:22:46.080 --> 01:22:47.140
and yes I get a lot

01:22:47.140 --> 01:22:47.500
of email.

01:22:47.500 --> 01:22:50.860
Yeah well you

01:22:50.860 --> 01:22:52.560
gotta I also I also

01:22:52.560 --> 01:22:54.900
think if you're

01:22:54.900 --> 01:22:55.540
working for a big

01:22:55.540 --> 01:22:56.200
company and the

01:22:56.200 --> 01:22:57.900
company is like you

01:22:57.900 --> 01:22:58.820
know putting the

01:22:58.820 --> 01:22:59.820
bill for you in

01:22:59.820 --> 01:23:00.760
order to not lose

01:23:00.760 --> 01:23:01.420
that company's

01:23:01.420 --> 01:23:02.300
contract a lot of

01:23:02.300 --> 01:23:03.160
time they'll make

01:23:03.160 --> 01:23:04.080
deals usually if

01:23:04.080 --> 01:23:04.460
you're a regular

01:23:04.460 --> 01:23:05.200
person from the

01:23:05.200 --> 01:23:05.780
stories that I've

01:23:05.780 --> 01:23:06.840
heard Verizon will

01:23:06.840 --> 01:23:07.460
be like no it's

01:23:07.460 --> 01:23:08.340
impossible they send

01:23:08.340 --> 01:23:08.940
you a form letter

01:23:08.940 --> 01:23:09.680
that says the only

01:23:09.680 --> 01:23:10.480
way you could use

01:23:10.480 --> 01:23:12.100
more than 256

01:23:12.100 --> 01:23:13.280
megabytes in one

01:23:13.280 --> 01:23:14.480
month is to because

01:23:14.480 --> 01:23:15.120
they say that you've

01:23:15.120 --> 01:23:17.080
used you know 40 or

01:23:17.080 --> 01:23:19.740
80 or 160 times the

01:23:19.740 --> 01:23:20.680
amount that a

01:23:20.680 --> 01:23:21.320
normal user would

01:23:21.320 --> 01:23:22.180
use and they say

01:23:22.180 --> 01:23:22.920
the only way that

01:23:22.920 --> 01:23:23.700
you could possibly do

01:23:23.700 --> 01:23:24.640
that is by streaming

01:23:24.640 --> 01:23:25.920
video and audio and

01:23:25.920 --> 01:23:26.940
shit so.

01:23:27.540 --> 01:23:28.180
Yeah like their

01:23:28.180 --> 01:23:29.280
term Verizon's terms

01:23:29.280 --> 01:23:30.160
of services are like

01:23:30.160 --> 01:23:31.520
draconian you can't

01:23:31.520 --> 01:23:32.460
use like streaming

01:23:32.460 --> 01:23:33.740
video can't use VoIP

01:23:33.740 --> 01:23:36.320
can't use streaming

01:23:36.320 --> 01:23:37.160
audio like for

01:23:37.160 --> 01:23:38.260
example can't stream

01:23:38.260 --> 01:23:39.220
your MP3s from your

01:23:39.220 --> 01:23:39.940
home server because

01:23:39.940 --> 01:23:41.920
that's a no-no it's

01:23:41.920 --> 01:23:45.920
it's crazy like it's

01:23:45.920 --> 01:23:48.320
stupid stupid Verizon's

01:23:48.320 --> 01:23:48.900
a poopy hidden.

01:23:52.280 --> 01:23:53.280
All right well I

01:23:53.280 --> 01:23:54.180
think we didn't

01:23:54.180 --> 01:23:55.300
really cover most of

01:23:55.300 --> 01:23:55.900
the topics we

01:23:55.900 --> 01:23:56.520
actually wanted to

01:23:56.520 --> 01:23:57.320
cover but hey you

01:23:57.320 --> 01:23:58.020
know it was a fun

01:23:58.020 --> 01:23:59.340
show but I think

01:23:59.340 --> 01:23:59.760
we're gonna have to

01:23:59.760 --> 01:24:00.640
wrap it up right now.

01:24:01.560 --> 01:24:02.460
Really already huh?

01:24:03.620 --> 01:24:04.300
Yeah I think we're

01:24:04.300 --> 01:24:04.720
actually kind of

01:24:04.720 --> 01:24:05.260
running out of time.

01:24:06.060 --> 01:24:06.940
If not you know

01:24:06.940 --> 01:24:07.560
we'll try to get it

01:24:07.560 --> 01:24:08.240
short this week we'll

01:24:08.240 --> 01:24:08.960
make up for all those

01:24:08.960 --> 01:24:10.420
two hour epic episodes

01:24:10.420 --> 01:24:11.220
we've had over the

01:24:11.220 --> 01:24:12.020
past couple of weeks.

01:24:12.020 --> 01:24:16.140
All right um no

01:24:16.140 --> 01:24:16.680
announcements is

01:24:16.680 --> 01:24:17.240
actually the

01:24:17.240 --> 01:24:17.880
announcements we do

01:24:17.880 --> 01:24:18.580
have we announced

01:24:18.580 --> 01:24:19.440
that Pooder was still

01:24:19.440 --> 01:24:20.420
looking for people for

01:24:20.420 --> 01:24:21.120
his Jenny scan.

01:24:21.460 --> 01:24:22.520
Pooder's Jenny scan is

01:24:22.520 --> 01:24:22.900
done.

01:24:23.080 --> 01:24:24.380
I think we uh I

01:24:24.380 --> 01:24:25.180
talked to StankDog

01:24:25.180 --> 01:24:26.640
StankDog made that

01:24:26.640 --> 01:24:27.880
announcement so it's

01:24:27.880 --> 01:24:29.280
on DocDroppers.org if

01:24:29.280 --> 01:24:29.780
you want to check it

01:24:29.780 --> 01:24:31.380
out and call up some

01:24:31.380 --> 01:24:31.760
Jenny's.

01:24:32.920 --> 01:24:33.340
Do you have any

01:24:33.340 --> 01:24:33.580
shouts?

01:24:34.860 --> 01:24:37.560
Um I'm gonna shout out

01:24:37.560 --> 01:24:38.460
StankDiggy.

01:24:38.460 --> 01:24:42.120
Aww that's so nice.

01:24:42.520 --> 01:24:43.420
That's love right

01:24:43.420 --> 01:24:43.720
there.

01:24:44.960 --> 01:24:45.860
That is total love.

01:24:46.640 --> 01:24:47.840
Um I'll send shouts

01:24:47.840 --> 01:24:49.760
out to I'll send a

01:24:49.760 --> 01:24:50.280
shout out to you.

01:24:50.380 --> 01:24:50.900
Thank you for coming

01:24:50.900 --> 01:24:51.200
on.

01:24:51.300 --> 01:24:51.780
I mean I haven't

01:24:51.780 --> 01:24:52.260
talked to you in

01:24:52.260 --> 01:24:52.500
forever.

01:24:53.280 --> 01:24:55.000
Um shouts out to the

01:24:55.000 --> 01:24:56.300
guy who's talking way

01:24:56.300 --> 01:24:58.220
too much about GUIDs

01:24:58.220 --> 01:24:59.180
and uh shouts out to

01:24:59.180 --> 01:25:00.060
people who still use

01:25:00.060 --> 01:25:01.120
pagers because people

01:25:01.120 --> 01:25:01.880
who still use pagers

01:25:01.880 --> 01:25:02.540
are cool.

01:25:04.060 --> 01:25:05.580
Uh closing do we have

01:25:05.580 --> 01:25:06.400
a site I don't have a

01:25:06.400 --> 01:25:06.980
site of the week this

01:25:06.980 --> 01:25:07.160
week.

01:25:07.260 --> 01:25:07.860
A site of the week is

01:25:07.860 --> 01:25:09.460
ocremix.org where we

01:25:09.460 --> 01:25:10.280
get all of our closing

01:25:10.280 --> 01:25:13.680
music and um we are

01:25:13.680 --> 01:25:14.660
closing music tonight is

01:25:14.660 --> 01:25:16.200
the Hyrule Party Mix

01:25:16.200 --> 01:25:17.480
by Knops from uh

01:25:17.480 --> 01:25:20.160
Zelda 64 or Ocarina of

01:25:20.160 --> 01:25:20.500
Time.

01:25:20.720 --> 01:25:21.820
I probably mispronounced

01:25:21.820 --> 01:25:22.080
that.

01:25:22.800 --> 01:25:23.880
Uh email radio at

01:25:23.880 --> 01:25:27.060
binrev.com and um I

01:25:27.060 --> 01:25:27.700
guess we'll see you next

01:25:27.700 --> 01:25:27.920
week.

01:25:28.020 --> 01:25:28.660
Same hack time.

01:25:29.060 --> 01:25:30.000
Same hack channel.

01:25:38.200 --> 01:25:38.980
I'll see you next week.

01:25:39.120 --> 01:25:40.660
Take care.

01:25:40.720 --> 01:25:47.760
meet you next week.

01:25:49.900 --> 01:25:50.440
Take care.

01:25:50.820 --> 01:25:51.480
Bye.

01:25:51.540 --> 01:25:52.580
Take care.

01:25:52.780 --> 01:25:53.400
Bye.

01:25:53.500 --> 01:25:53.620
Bye.

01:25:53.700 --> 01:25:53.980
Bye.

01:25:54.100 --> 01:25:54.120
Bye.

01:25:54.280 --> 01:25:54.600
Bye.

01:25:54.680 --> 01:25:54.700
Bye.

01:25:54.740 --> 01:25:54.820
Bye.

01:25:54.820 --> 01:25:55.420
Bye.

01:25:55.460 --> 01:25:55.820
Bye.

01:25:56.180 --> 01:25:56.540
Bye.

01:25:57.080 --> 01:25:57.500
Bye.

01:25:57.580 --> 01:25:57.920
Bye.

01:25:58.080 --> 01:25:58.440
Bye.

01:25:59.220 --> 01:25:59.300
Bye.

01:26:00.240 --> 01:26:01.160
Bye.

01:26:01.320 --> 01:26:01.620
Bye.

01:26:05.560 --> 01:26:05.880
Bye.

01:26:05.880 --> 01:26:06.280
Bye.

01:26:06.380 --> 01:26:06.820
Bye.

01:26:06.820 --> 01:26:06.840
Bye.

01:26:06.840 --> 01:26:07.000
Bye.

01:26:07.160 --> 01:26:07.240
Bye.

01:26:07.240 --> 01:26:37.220
Thank you.

01:26:37.240 --> 01:27:07.220
Thank you.

01:27:07.240 --> 01:27:37.220
Thank you.

01:27:37.240 --> 01:28:07.220
Thank you.

01:28:07.240 --> 01:28:37.220
Thank you.

01:28:37.240 --> 01:29:07.220
Thank you.

01:29:07.240 --> 01:29:37.220
Thank you.

01:29:37.240 --> 01:30:07.220
Thank you.

01:30:07.240 --> 01:30:37.220
Thank you.