WEBVTT

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

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

00:15.480 --> 00:16.420
in a fag pose.

00:16.660 --> 00:21.640
In your digital stance, getting firewalled ho, cause I'm riding the net in my six foe.

00:21.820 --> 00:26.400
I was a dick with my 56, now with my cable I'm able to get that stable.

00:26.400 --> 00:32.420
On the out, my name is Ace and I'm a Leo. On the digital highway, my name is Neo and I'm a hero.

00:32.620 --> 00:38.300
In a flash, I'll screw you on burning dreamcasts. You need some ISOs? Let me through my hard drive rifle.

00:38.640 --> 00:43.460
Our exchange you could never stifle. And a digital hug, you just caught the love bug.

00:43.760 --> 00:47.480
I bootlegged your CD, I caused a fight between Un and Jay-Z.

00:47.820 --> 00:52.100
Your CG, it's all gonna be free, whether we take it by force or we take it nicely.

00:52.100 --> 00:56.220
You feel that rattle in your bones when I tell you we just hacked out Jones?

00:56.400 --> 01:00.660
And NASDAQ, leave your plot on your back, cause I am he who loves to hack and crack.

01:01.040 --> 01:03.440
Cause I am he who loves to hack and crack.

01:03.900 --> 01:06.480
This is dedicated to the hackers and the criminals.

01:06.980 --> 01:11.560
Serial codes, source codes, ISOs, RAMs, SIPs, SIPs.

01:11.820 --> 01:14.160
This is dedicated to the hackers and the crack.

01:15.160 --> 01:15.760
Awesome!

01:17.980 --> 01:20.420
This radio show is awesome!

01:21.960 --> 01:23.380
What the hell?

01:23.380 --> 01:25.640
I don't know how to open the show anymore.

01:25.800 --> 01:26.320
I'm getting...

01:26.320 --> 01:27.820
Welcome to Sand Demon!

01:30.540 --> 01:34.220
Rock on! We are Wild Stallions!

01:35.560 --> 01:38.760
Dude, we're getting... we're scraping the bottom of the barrel for funny openings.

01:39.480 --> 01:40.240
Yeah, it's pretty terrible.

01:40.280 --> 01:43.260
But you know what? I'm gonna leave that in because I'm too lazy to start over.

01:43.260 --> 01:50.980
And in case you guys haven't recognized, maybe you were Mieber, today's co-host, for being on the show so many times in the past.

01:51.380 --> 01:53.740
But it's none other than Not Theory himself.

01:54.280 --> 01:55.200
Yeah, what's the problem?

01:55.740 --> 02:00.220
And you are listening to episode 57 of Binary Revolution Radio.

02:01.060 --> 02:03.960
Joining Not Theory today will be myself, Stank Dog.

02:03.960 --> 02:09.320
And today, we're gonna talk about databases.

02:10.020 --> 02:15.740
Specifically relational databases, but we'll talk about the differences between some different types of databases.

02:15.980 --> 02:19.080
And some... go into a little bit of detail about some relational databases.

02:20.020 --> 02:24.140
But, before we do, let's take care of a little housekeeping.

02:24.140 --> 02:31.440
First thing, I am happy to announce, we have an update on the status of the magazines.

02:32.120 --> 02:34.620
I have them in my hands.

02:35.380 --> 02:38.260
Well, not in my hands right now, but they're over in a box on the other side of the room.

02:39.040 --> 02:41.500
I have all three issues printed.

02:42.020 --> 02:44.200
Very nice quality. Looked very good.

02:44.300 --> 02:49.680
I have them in large quantities, so shouldn't be running out anytime soon.

02:49.680 --> 02:55.260
So, all orders will have been shipped by the time you hear this.

02:55.720 --> 02:57.120
So, give it a couple weeks.

02:57.220 --> 02:58.600
Give it a week or two, a week and a half.

02:59.060 --> 03:01.940
Usually takes about 10 days to get there, up to 10 days to get there.

03:02.100 --> 03:03.820
So, they'll probably be shipped out.

03:04.620 --> 03:06.820
Probably be postmarked Tuesday, actually.

03:07.520 --> 03:10.940
And everybody who's put in orders and been waiting, thank you for being patient.

03:11.040 --> 03:12.280
You should have them very soon.

03:12.340 --> 03:14.920
And if not, we'll figure out what happened.

03:15.020 --> 03:17.760
But I'm pretty sure I have a list of everybody who's still waiting on orders.

03:17.760 --> 03:19.400
So, it should not be any problems like that.

03:20.500 --> 03:25.260
And that also means that issue 2.1 is available.

03:25.520 --> 03:30.320
And I will put that link up to order that on the website very soon.

03:31.420 --> 03:36.260
And I also put up a little three-pack where people who are new to BinRev

03:36.260 --> 03:39.100
and don't have any of the issues can buy all three of them at the same time.

03:39.300 --> 03:43.660
So, we'll have all that up on the website hopefully Tuesday.

03:43.660 --> 03:47.200
But if not, it will be up by the end of the week for sure.

03:47.340 --> 03:48.160
No doubt about it.

03:48.480 --> 03:50.300
Okay, possibly a little bit of doubt about it.

03:50.360 --> 03:51.540
But I'm going to try my best.

03:52.880 --> 03:54.780
Everyone's been waiting for this damn thing forever.

03:55.280 --> 03:56.960
And it makes me sick, actually.

03:57.340 --> 03:59.400
And I don't think I want to do the show anymore.

03:59.660 --> 04:02.020
Are you so insulted that you're going to hang up now?

04:02.120 --> 04:03.260
Because you could do the show naked.

04:04.560 --> 04:05.580
Who says I'm not?

04:05.580 --> 04:09.340
Oh, man.

04:09.480 --> 04:10.900
We got owned last week.

04:10.960 --> 04:12.400
And when I say we, I mean me.

04:13.540 --> 04:16.120
We had an email from El Taco Frio.

04:16.800 --> 04:23.540
We mentioned a link to someone who allegedly turned a Mini Cooper into a little transformer,

04:23.740 --> 04:25.660
not a little, a transformer robot thing.

04:25.660 --> 04:30.680
And Pixel Fiend emailed and pointed out that that was a hoax, unfortunately.

04:31.440 --> 04:32.600
Cool looking pictures.

04:32.740 --> 04:33.880
And I didn't look into it too much.

04:33.920 --> 04:39.180
But apparently it was done by some advertising agency for the Mini Cooper people or whatever.

04:39.180 --> 04:40.900
So, that kind of sucks.

04:41.020 --> 04:42.940
But, it was still kind of a cool looking robot.

04:43.320 --> 04:47.440
So, still a cool link to share with the listeners, even though we are noobs.

04:48.480 --> 04:51.900
And once again, when I say we, I mean not theory.

04:52.620 --> 04:55.300
Oh, I need to call myself a stifu.

04:57.060 --> 04:57.460
Stifu.

04:58.540 --> 04:58.980
Pajir.

04:58.980 --> 05:00.840
Oh, my God.

05:00.900 --> 05:02.160
Okay, that needs to stop right now.

05:03.980 --> 05:04.980
Oh, you went there.

05:05.020 --> 05:05.600
I just followed.

05:07.080 --> 05:11.340
Oh, and speaking of Pixel Fiend, let's see.

05:11.500 --> 05:15.180
Let me play our email theme music here real quickly.

05:15.300 --> 05:17.000
I've got to start putting that in the show more often.

05:17.000 --> 05:39.140
And, we're going to go to our first email.

05:40.240 --> 05:42.360
And, that again is from Pixel Fiend.

05:43.220 --> 05:47.060
After showing us how I got owned by falling for a hoax without doing my homework.

05:47.240 --> 05:48.720
Something that I hate other people doing.

05:48.800 --> 05:49.500
But, I did myself.

05:49.600 --> 05:50.020
I admit it.

05:50.060 --> 05:50.360
Shut up.

05:51.520 --> 05:53.040
Pixel Fiend says,

05:53.320 --> 05:59.540
One thing that I wanted to mention is your subject from episode 53, I think.

05:59.740 --> 06:00.760
The ethical hacker.

06:01.460 --> 06:02.460
Maybe I misunderstood.

06:02.460 --> 06:08.400
But, I have a different understanding of what an ethical hacker is supposed to be.

06:08.840 --> 06:12.300
I thought that an ethical hacker was basically equivalent to a penetration.

06:12.360 --> 06:12.840
Tester.

06:13.280 --> 06:14.720
My idea of a dream job.

06:15.200 --> 06:16.000
That would be the life.

06:16.060 --> 06:19.240
To be paid for finding security holes and exploring a company's network.

06:19.660 --> 06:22.500
Assessing strengths and weaknesses without worry of retribution.

06:23.460 --> 06:26.900
Unfortunately, the term ethical hacker plays to the derogatory.

06:27.440 --> 06:30.460
Insinuating that hackers are inherently unethical.

06:30.960 --> 06:33.040
So, yeah, the term is distasteful.

06:34.160 --> 06:36.240
The certification follows this mindset.

06:36.540 --> 06:39.040
And, whether or not the classwork or tests have merit,

06:39.500 --> 06:41.480
Businesses see the sexy title.

06:41.700 --> 06:45.280
Ethical hacker has more pizzazz than penetration tester.

06:45.720 --> 06:47.620
And, plays to the current hacker hype.

06:48.320 --> 06:51.760
Of course, the cash that they charge for the courses and tests is outrageous.

06:52.120 --> 06:53.420
You hit that right on the head.

06:53.420 --> 07:00.060
I don't think, however, that the idea behind the cert is to have a bunch of business owners take a class to tighten their network security

07:00.060 --> 07:03.860
and earn the right to call themselves ethical hackers.

07:04.300 --> 07:05.960
Whether that has happened or not.

07:06.340 --> 07:10.540
I know a couple of people from the security focus forums and lists who have the cert.

07:10.940 --> 07:13.520
And, they're quite knowledgeable penetration testers.

07:13.520 --> 07:19.080
Although, I do have a feeling that their hat changes from white to a muddy gray or darker every once in a while.

07:19.420 --> 07:20.240
Did they sell out?

07:20.540 --> 07:21.140
I don't know.

07:21.380 --> 07:24.200
But, I expect that they have a lot more fun at work than me.

07:24.560 --> 07:27.400
And, are making boatloads of cash.

07:28.760 --> 07:30.660
A belated congrats on the one year anniversary.

07:30.820 --> 07:35.100
Your show is helping to balance out a lot of the negative politics that are around now.

07:35.260 --> 07:37.260
And, from what I see, it's contagious.

07:37.260 --> 07:42.340
Judging from the several spin-off shows that have come about in the past few months.

07:43.960 --> 07:47.520
Well, thank you for recognizing the anniversary.

07:47.740 --> 07:49.720
We've done a year and we're well into year two.

07:49.800 --> 07:50.380
So, that's cool.

07:51.120 --> 07:54.000
As far as the ethical hacker.

07:55.540 --> 08:05.680
Now, I actually think he made a very good point that the term ethical hacker insinuates that hackers are inherently unethical.

08:05.680 --> 08:07.320
And, I actually did.

08:07.380 --> 08:08.260
I had not thought of that.

08:08.340 --> 08:10.140
I thought that was a good point.

08:10.280 --> 08:11.680
Does that...

08:11.680 --> 08:14.680
I mean, did that strike you as, um...

08:15.320 --> 08:16.780
It didn't strike me.

08:17.720 --> 08:19.760
But, I mean, it doesn't make a very good point.

08:19.840 --> 08:23.700
But, on the other hand, if it didn't strike me and it didn't strike you, who else is looking at it like that?

08:23.800 --> 08:24.720
I mean, some people, sure.

08:24.860 --> 08:27.340
But, hopefully not the bulk of people.

08:27.460 --> 08:29.420
Hopefully, the bulk of people are dumb like me.

08:29.460 --> 08:30.100
I never thought of it.

08:31.380 --> 08:33.040
But, seriously, because, um...

08:33.040 --> 08:40.060
I really hadn't, but I worry that he may have a true point that, like, does that how the general populace thinks?

08:40.680 --> 08:41.320
Yeah, it could be.

08:41.480 --> 08:46.260
I guess somebody maybe with no contact to the scene might make that connection very quickly.

08:46.780 --> 08:47.060
Hmm.

08:47.120 --> 08:48.320
Or, it wouldn't even cross my mind.

08:48.800 --> 08:51.000
Yeah, I mean, hackers equals bad guys.

08:51.060 --> 08:52.500
Is that not the common perception?

08:53.000 --> 08:53.560
Yeah, yeah.

08:53.620 --> 08:55.220
So, I think he makes a very, very good point.

08:55.220 --> 08:55.740
Hmm.

08:56.680 --> 08:58.380
Well, um...

08:58.380 --> 09:03.480
I guess it's perfect timing to pimp Binary Revolution magazine issue 2.1,

09:03.560 --> 09:12.680
because I wrote an introduction for 2.1 that kind of clarifies at least my personal views on the different types of hackers

09:12.680 --> 09:15.860
and what's ethical and what's not ethical and how they're labeled.

09:15.860 --> 09:23.360
Um, but I do not believe that, you know, I think you said, let me see your exact wording earlier there,

09:24.040 --> 09:27.980
you thought that an ethical hacker was basically equivalent to a penetration tester.

09:28.500 --> 09:31.820
Now, a penetration tester can very well be an ethical hacker.

09:31.920 --> 09:36.940
That could be a subset of ethical hackers, but I'm not a penetration tester.

09:38.720 --> 09:40.220
You know, it's not my job.

09:40.280 --> 09:41.720
I'm not a certified ethical hacker.

09:41.780 --> 09:43.580
I don't do penetration testing for a living.

09:43.580 --> 09:49.540
But I still like to think of myself as ethical, so I don't think they're mutually exclusive terms.

09:51.780 --> 09:58.020
You certainly can be an ethical hacker, I guess, or certainly can be a penetration tester and be an ethical hacker.

09:58.080 --> 10:00.080
That's one type, but aren't there others out there?

10:00.140 --> 10:02.640
Can you be, you know, another type?

10:02.700 --> 10:04.520
Can you just be an ethical hacker in general?

10:05.460 --> 10:07.320
Um, I guess.

10:07.600 --> 10:09.860
Isn't that the distinction of white hat, black hat, gray hat?

10:10.260 --> 10:12.420
Well, and again, those are up for debate, too,

10:12.420 --> 10:15.120
and I mentioned that in my article, in my introduction to the magazine,

10:15.280 --> 10:18.420
is, you know, one person's definition of those is different than another.

10:18.860 --> 10:19.120
Oh, yeah.

10:19.160 --> 10:22.560
I can't stand the common, you know, I see it on a lot of websites

10:22.560 --> 10:26.860
where they say that white hat hackers are computer security professionals.

10:26.980 --> 10:27.880
I think that's bullshit.

10:29.440 --> 10:31.140
Oh, there's going to be a lot of cussing coming up soon,

10:31.180 --> 10:32.780
so I might as well just warn everybody up front.

10:33.360 --> 10:33.920
Oh, yeah.

10:33.920 --> 10:37.220
Yeah, I think that's a load.

10:37.940 --> 10:42.440
To be a white hat hacker, you have to be a computer security professional.

10:43.620 --> 10:46.800
That's what a white hat, that's what they try to define white hat hackers as,

10:46.820 --> 10:48.380
and I think that's just ludicrous.

10:48.380 --> 10:51.540
I don't, I think that that's just a generalization that they make

10:51.540 --> 10:54.300
so that people understand, like, what white hat means.

10:54.540 --> 10:56.820
Like, somebody who's a certified, not certified,

10:57.040 --> 10:58.400
a computer security professional,

10:58.620 --> 11:01.540
they do a certain set of things, and they do it, like, you know,

11:01.720 --> 11:05.300
for a good cause, and I think it's easier to explain that

11:05.300 --> 11:08.740
than just to say computer security professional,

11:08.880 --> 11:10.960
have people have that idea pop in their head

11:10.960 --> 11:12.860
than explain white hat hacker all the way out.

11:12.860 --> 11:14.840
So, I just think it's a generalization.

11:15.360 --> 11:18.780
Yeah, that's probably true for the layman, or layperson,

11:19.280 --> 11:21.020
to be politically correct, the layperson,

11:21.140 --> 11:23.760
but bottom line is I think you can be an ethical hacker

11:23.760 --> 11:27.520
without being a computer security professional.

11:27.800 --> 11:32.380
If anything, I've met and know several computer security professionals

11:32.380 --> 11:36.060
who do the most evil things you've ever imagined.

11:36.740 --> 11:40.080
So, if anything, they're the opposite of white hat.

11:40.080 --> 11:45.680
They have no ethics, selling out mailing lists of the users to make money

11:45.680 --> 11:49.520
and violating privacy of their users and stuff like that.

11:50.120 --> 11:51.500
What ethics are they following?

11:51.700 --> 11:52.660
What makes them white hat?

11:52.700 --> 11:53.640
What ethics are they following?

11:53.740 --> 11:55.040
It's certainly not the hacker ethic.

11:56.000 --> 11:58.440
And I think that's another point here that needs to be made is

11:58.440 --> 12:01.500
when you say ethical, you've got to define which ethics you're talking about

12:01.500 --> 12:04.060
because hackers do have a code of ethics.

12:04.760 --> 12:07.640
The hacker ethic has been well known for quite some time,

12:07.640 --> 12:13.040
and it has several conflicts with ethics of the general populace, I guess,

12:13.520 --> 12:14.760
is the best way to describe it.

12:15.820 --> 12:21.120
So, just because I might not meet with the ethics of one particular town or city

12:21.120 --> 12:24.640
or even country doesn't mean I don't have my own set of ethics.

12:25.680 --> 12:26.980
I just don't agree with yours.

12:27.580 --> 12:28.480
Well, then you must be wrong.

12:29.320 --> 12:31.480
Well, yeah, I frequently am.

12:31.480 --> 12:37.220
So, as far as the certification itself, I mean, what we said on the show,

12:37.420 --> 12:41.320
to kind of recap or summarize, I don't know if it was 53 or not,

12:41.360 --> 12:43.120
but it sounds all right, I guess, somewhere around there.

12:43.580 --> 12:47.560
We were talking about a company that is giving out, excuse me,

12:47.580 --> 12:51.520
they have a training series where at the end of it you get a certificate,

12:52.220 --> 12:55.260
a certification that you are a certified ethical hacker.

12:55.260 --> 12:59.460
And I think my, you know, when I summarized the whole thing,

12:59.520 --> 13:04.180
I said, basically, people educating themselves and learning how to do this is great.

13:04.320 --> 13:08.260
I just question the validity of the certification itself.

13:09.680 --> 13:16.860
Who is the person who's going to justify, or who is it to judge what is certified and ethical?

13:18.040 --> 13:20.040
And hacking, for that matter, all three words.

13:20.700 --> 13:20.920
Right.

13:20.920 --> 13:25.000
You know, they have different qualifications for ethical, like I just said.

13:25.100 --> 13:27.100
Everybody has different qualifications for ethics.

13:27.240 --> 13:28.940
So, that was my big question.

13:29.120 --> 13:32.120
But, just to throw out a little bit of a teaser,

13:32.400 --> 13:34.320
and that's all this is, is a teaser,

13:34.460 --> 13:40.160
is I am going to be doing some very, very detailed research on this in the near future.

13:40.880 --> 13:42.560
And you can read into that what you will.

13:43.680 --> 13:45.960
So, again, thanks for shouts for the anniversary,

13:46.300 --> 13:49.100
and we're going to try to make year two better.

13:49.100 --> 13:51.320
We're, how many episodes into year two now?

13:51.900 --> 13:55.580
This is 57, so we're five into year two.

13:55.780 --> 13:59.900
So, I think, I don't know about you,

14:00.040 --> 14:02.560
but I think it's probably time for a rant, don't you?

14:03.420 --> 14:04.320
Yeah, man, go for it.

14:04.340 --> 14:07.020
Is it time for me to really just break down and start cussing?

14:07.080 --> 14:09.440
Because that's what's going to happen.

14:09.440 --> 14:17.120
Because I got an email from Psycho Mind Lent sent me an email.

14:18.180 --> 14:19.360
And he says,

14:19.860 --> 14:22.860
Hey, Stank Dog, thought you should know about this if you didn't already.

14:23.440 --> 14:27.860
Check out the following links for more info on the Induce Act.

14:28.200 --> 14:29.620
And he sends several links.

14:29.620 --> 14:32.440
And the one that I'm going to read on the air,

14:32.840 --> 14:39.220
just go to savetheth.org.

14:39.720 --> 14:43.000
That's the cleanest and most straightforward explanation.

14:43.660 --> 14:47.500
And you will find links from that to other sites that go into more detail

14:47.500 --> 14:48.660
and more specifics on it.

14:48.980 --> 14:52.600
The EFF has a great case up there.

14:52.600 --> 14:54.380
And I think you liked the EFFs.

14:54.860 --> 14:58.540
You thought that was a good demonstration of the danger of this?

15:00.460 --> 15:01.820
Well, yeah, kind of.

15:01.980 --> 15:05.380
I can see, when I originally went to savetheth.org,

15:06.080 --> 15:08.460
they made a lot of assertions that say,

15:08.580 --> 15:11.400
Oh, this act will do this, this act will do that.

15:11.460 --> 15:13.780
But the EFF did a good job of going through,

15:14.660 --> 15:18.240
taking the wording directly from the act

15:18.240 --> 15:22.060
and explaining how they could apply it to a complaint against Apple.

15:22.600 --> 15:23.720
And specifically the iPod.

15:23.820 --> 15:25.940
And I thought that the EFF did an awesome job

15:25.940 --> 15:30.000
of explaining how this could be abused in the legal system.

15:31.180 --> 15:34.820
Yeah, and I think that's kind of a smart move, honestly,

15:35.720 --> 15:37.400
using the iPod as an example

15:37.400 --> 15:40.900
because it gets those millions of iPod users on the cause

15:40.900 --> 15:42.920
and brings it to the public attention.

15:42.920 --> 15:44.680
And it's not just a little, you know,

15:44.820 --> 15:48.780
Oh, it's just a few hackers complaining about another privacy act

15:48.780 --> 15:50.080
like we've done about the Patriot Act.

15:50.200 --> 15:52.020
Luckily, when we get more people involved,

15:52.060 --> 15:54.080
and people outside of the hacking community

15:54.080 --> 15:56.540
and the, well, the privacy community,

15:56.960 --> 15:59.260
people are starting to respect and understand privacy more.

15:59.340 --> 16:00.980
So the more publicity they get

16:00.980 --> 16:02.500
and the more people they get involved,

16:02.580 --> 16:04.620
the better it is to stop stuff like this.

16:04.940 --> 16:05.760
Well, I don't know, man.

16:05.780 --> 16:07.200
I saw the Save the iPod thing

16:07.200 --> 16:08.900
and I knew right away, whatever it was,

16:09.320 --> 16:10.160
I was against it

16:10.160 --> 16:12.340
because I personally hate the iPod.

16:12.520 --> 16:13.260
And I hate Apple.

16:13.480 --> 16:16.780
So hopefully this complaint with Apple will go through

16:16.780 --> 16:17.760
if this act gets passed

16:17.760 --> 16:18.940
and Apple will just be out of business.

16:19.340 --> 16:21.140
Well, maybe we can come up with another way

16:21.140 --> 16:22.120
to topple Apple.

16:23.460 --> 16:24.940
See, I don't have a problem with Apple.

16:25.260 --> 16:26.580
I agree with you.

16:26.660 --> 16:27.480
I know what your problem,

16:27.580 --> 16:28.960
I know what your beef with Apple is,

16:29.220 --> 16:31.000
and I agree with it 100%.

16:31.000 --> 16:33.940
But I like the hardware.

16:35.020 --> 16:37.440
I don't like the fact that it's closed,

16:38.120 --> 16:39.880
which is your beef.

16:40.080 --> 16:41.420
Well, why don't you explain

16:41.420 --> 16:42.720
what you don't like about Apple?

16:43.020 --> 16:44.480
This is your rant.

16:44.540 --> 16:46.200
You can have your rant on Apple.

16:46.300 --> 16:46.660
My rant.

16:46.780 --> 16:48.640
And I don't need to really make it that long.

16:48.720 --> 16:50.340
I'm pretty sure I did this rant once before,

16:50.460 --> 16:51.600
maybe if not on this show or another.

16:51.860 --> 16:52.680
Well, it hurts to do it.

16:52.740 --> 16:53.900
It never hurts to do it again.

16:54.420 --> 16:54.820
Exactly.

16:55.360 --> 16:57.800
I look at Apple as the Microsoft

16:57.800 --> 16:59.600
of the hardware industry.

17:00.240 --> 17:02.920
Like, Microsoft has the software industry locked down.

17:03.240 --> 17:05.260
Apple has their own little niche market

17:05.260 --> 17:07.920
where people will pay pretty much

17:07.920 --> 17:09.560
whatever Apple says for their hardware.

17:09.700 --> 17:10.160
Now, I know.

17:10.280 --> 17:11.140
People have benchmarks,

17:11.300 --> 17:11.620
and they say,

17:11.700 --> 17:16.020
oh, my G5 runs DNet-C like 10 times faster

17:16.020 --> 17:17.400
than your machine does.

17:17.500 --> 17:18.080
And it does.

17:18.220 --> 17:18.400
Great.

17:18.920 --> 17:20.740
I don't deny that at all.

17:20.780 --> 17:21.240
That's great.

17:21.760 --> 17:24.080
Running DNet-C fast is really cool.

17:24.340 --> 17:25.600
But on the other hand,

17:25.600 --> 17:27.240
does it do what I want it to do?

17:27.600 --> 17:29.000
Like, work that's useful to me?

17:29.060 --> 17:30.660
Does it do it that much faster

17:30.660 --> 17:33.320
and that much faster to warrant that price increase?

17:34.000 --> 17:34.800
Probably not.

17:35.260 --> 17:36.020
Would be my guess.

17:36.220 --> 17:36.820
Like, does it...

17:36.820 --> 17:39.180
My real beef with them would be,

17:39.360 --> 17:40.600
does it run Postgres faster?

17:40.860 --> 17:41.620
Because if it doesn't,

17:41.700 --> 17:42.420
I really don't care.

17:43.500 --> 17:45.180
You know, does it run Apache that much faster?

17:45.300 --> 17:46.320
If it doesn't, I don't care.

17:47.060 --> 17:49.080
Running DNet-C is, you know,

17:49.940 --> 17:51.860
it does something good for somebody else.

17:51.940 --> 17:52.980
It helps distribute it.net,

17:53.100 --> 17:55.100
but I'm basically buying a processor

17:55.100 --> 17:56.580
so I can do somebody else's work.

17:56.860 --> 17:57.920
That doesn't do it for me.

17:57.980 --> 17:59.760
So somebody can show me real stats on that.

18:00.380 --> 18:02.360
Well, you're using one example of DNet

18:02.360 --> 18:04.420
just because we have that project going on

18:04.420 --> 18:06.660
and we've seen that the Apples do great on that.

18:07.080 --> 18:08.400
But, I mean, it's a known,

18:08.660 --> 18:12.060
you know, it's a commonly accepted fact

18:12.060 --> 18:15.080
that Macintosh is the primary machine

18:15.080 --> 18:16.780
used in most graphics shops.

18:17.740 --> 18:19.060
Yeah, well, here we go.

18:19.200 --> 18:19.920
It excels at that.

18:20.380 --> 18:21.720
I don't do any graphics, though.

18:21.720 --> 18:23.980
Well, for you personally, right, but...

18:23.980 --> 18:25.000
That's what I'm saying.

18:25.000 --> 18:26.840
If it ran Postgres faster,

18:26.900 --> 18:28.540
and this is, I think, the second,

18:28.640 --> 18:30.320
this is what I agree with more about your point,

18:30.380 --> 18:32.340
is let's say it did run Postgres faster.

18:33.040 --> 18:37.240
Does it still justify the cost hike?

18:37.540 --> 18:39.580
If it ran Postgres 10 times faster,

18:39.660 --> 18:41.280
like it runs DNet-C 10 times faster,

18:41.320 --> 18:42.780
and it costs three times as much,

18:43.080 --> 18:44.740
it's worth every penny.

18:45.020 --> 18:47.380
If, if and only if,

18:47.480 --> 18:48.680
let's be very strict here,

18:48.680 --> 18:50.460
if, and only if,

18:50.600 --> 18:53.660
I can repair the machine cost-effectively,

18:53.900 --> 18:55.480
I can upgrade it cost-effectively,

18:55.720 --> 18:58.380
and, like, operating system-wise,

18:58.440 --> 18:59.240
it's easy to maintain.

18:59.940 --> 19:02.420
Now, I know OSX is based on BSD.

19:02.640 --> 19:03.900
I used to be a BSD nut.

19:03.980 --> 19:05.060
I was a BSD zealot.

19:05.740 --> 19:06.820
And then I switched to Linux,

19:06.980 --> 19:08.100
and I haven't used BSD.

19:08.260 --> 19:09.160
Now, the BSD is bad.

19:09.480 --> 19:10.820
I just don't use it anymore.

19:10.940 --> 19:12.140
From what I've seen, like,

19:12.400 --> 19:13.700
Linux is easier for me to manage.

19:14.080 --> 19:15.180
Can I run Linux on it?

19:15.180 --> 19:16.360
It's a big question for me.

19:16.620 --> 19:17.300
If I can't,

19:17.300 --> 19:19.780
that's a huge slam to the thing for me.

19:19.860 --> 19:21.740
I don't want to learn BSD

19:21.740 --> 19:23.180
just to get this thing up and running.

19:24.340 --> 19:24.740
So.

19:24.980 --> 19:25.560
Well, I,

19:25.700 --> 19:27.740
I can't speak,

19:27.840 --> 19:29.220
I, it seems like I've seen

19:29.220 --> 19:31.100
some of the Mac guys talking about,

19:31.180 --> 19:32.440
is it Yellow Dog Linux

19:32.440 --> 19:33.220
is the Mac,

19:33.860 --> 19:34.820
Linux for the Mac hardware?

19:34.820 --> 19:35.020
Yeah, yeah.

19:35.220 --> 19:36.580
I've heard of Linux variants

19:36.580 --> 19:37.240
that work on it,

19:37.280 --> 19:38.080
but everybody I know,

19:38.160 --> 19:38.660
they always say,

19:38.700 --> 19:39.840
oh, just, just run OSX,

19:39.900 --> 19:40.620
just run OSX.

19:40.700 --> 19:41.020
Right.

19:41.220 --> 19:42.160
Um, I don't,

19:42.220 --> 19:43.800
and that makes me feel like

19:43.800 --> 19:44.740
maybe their Linux project

19:44.740 --> 19:46.100
really isn't all that well supported,

19:46.100 --> 19:47.000
and that's not,

19:47.460 --> 19:47.960
that's not something

19:47.960 --> 19:48.680
I want to deal with.

19:48.800 --> 19:49.400
But, again,

19:49.900 --> 19:51.020
if it really did run Postgres

19:51.020 --> 19:51.700
10 times faster

19:51.700 --> 19:53.020
and I just needed a database server

19:53.020 --> 19:54.100
and I had to deal with BSD

19:54.100 --> 19:54.460
for, like,

19:54.460 --> 19:55.160
a business project,

19:55.260 --> 19:55.740
you know what?

19:56.140 --> 19:57.040
Shit, I'd go for it.

19:57.220 --> 19:58.100
I have no problem with that.

19:58.100 --> 19:58.600
Yeah, but, again,

19:58.700 --> 20:00.240
you said the point being,

20:00.320 --> 20:01.180
the sticking point of

20:01.180 --> 20:03.040
if you could repair it easily,

20:03.260 --> 20:03.700
cheaply,

20:03.820 --> 20:04.800
buy parts for it,

20:04.840 --> 20:05.260
et cetera,

20:05.400 --> 20:07.080
and the fact is you can't.

20:07.100 --> 20:08.220
You have to buy them

20:08.220 --> 20:09.600
from Apple.

20:10.360 --> 20:10.620
Yeah.

20:10.720 --> 20:11.640
And you have to pay...

20:11.640 --> 20:11.940
You could put,

20:11.980 --> 20:13.040
you could slap any hard drive

20:13.040 --> 20:13.980
in there and stuff like that.

20:14.040 --> 20:14.440
That's cool.

20:14.580 --> 20:14.940
But RAM,

20:15.080 --> 20:15.540
I don't know,

20:15.780 --> 20:17.260
I don't know what type of RAM it takes.

20:17.500 --> 20:19.120
And maybe it does take regular RAM.

20:19.200 --> 20:20.360
I'm not going to say that it doesn't.

20:20.800 --> 20:22.560
But, I don't know.

20:22.960 --> 20:24.400
They, the whole thing just scares me.

20:24.460 --> 20:25.040
Like, Apple just,

20:25.780 --> 20:27.140
they used to let people make clones

20:27.140 --> 20:28.220
and then they stopped.

20:28.600 --> 20:30.280
Yeah, that's the thing that got me.

20:30.380 --> 20:31.940
If they started letting Dell

20:31.940 --> 20:32.920
and other companies,

20:32.920 --> 20:33.780
maybe not Dell,

20:34.220 --> 20:35.580
but they started letting other companies

20:35.580 --> 20:36.920
make the hardware as well

20:36.920 --> 20:39.200
so there was some price competition.

20:40.080 --> 20:40.480
Yeah.

20:41.240 --> 20:42.480
I think that would be cool.

20:43.020 --> 20:43.580
Yeah, but,

20:44.080 --> 20:44.480
the people,

20:44.580 --> 20:45.640
the argument that people give me

20:45.640 --> 20:46.500
about that is they say,

20:46.540 --> 20:47.160
oh, well, you know,

20:47.620 --> 20:48.840
having this one supplier

20:48.840 --> 20:49.620
makes the platform

20:49.620 --> 20:50.580
that much more stable.

20:51.160 --> 20:52.160
And everyone always tells me

20:52.160 --> 20:53.020
Macs are so stable,

20:53.220 --> 20:54.220
but I have a friend

20:54.220 --> 20:55.060
who went to art school

20:55.060 --> 20:56.340
and he told me

20:56.340 --> 20:57.420
that Macs would crash

20:57.420 --> 20:59.000
all the time.

21:00.080 --> 21:00.720
Every day,

21:00.920 --> 21:01.820
multiple times a day.

21:02.220 --> 21:02.440
You know,

21:02.500 --> 21:03.340
he said it was much worse

21:03.340 --> 21:03.720
than Windows.

21:03.840 --> 21:04.980
He would do his work

21:04.980 --> 21:05.760
on a Mac at school

21:05.760 --> 21:06.580
because he had to

21:06.580 --> 21:07.300
and then when he went home

21:07.300 --> 21:08.240
he would do it on Windows

21:08.240 --> 21:09.340
because he couldn't deal

21:09.340 --> 21:10.120
with the Mac crashing

21:10.120 --> 21:10.620
all the time.

21:10.940 --> 21:11.200
Well,

21:11.300 --> 21:12.220
again,

21:12.340 --> 21:13.880
that's a specific case

21:13.880 --> 21:14.560
and that could be

21:14.560 --> 21:15.260
poor management

21:15.260 --> 21:16.000
of the systems

21:16.000 --> 21:16.580
or whatever.

21:17.200 --> 21:17.600
Could be.

21:17.800 --> 21:18.160
Could be.

21:18.400 --> 21:18.760
Well,

21:18.940 --> 21:19.440
I don't know,

21:19.520 --> 21:19.860
but yes,

21:19.920 --> 21:20.640
I think your point's

21:20.640 --> 21:21.060
well-founded.

21:21.160 --> 21:21.740
I agree with you

21:21.740 --> 21:23.120
on the hardware issue,

21:23.280 --> 21:25.820
but I still also admit

21:25.820 --> 21:27.520
that they make good products.

21:27.520 --> 21:27.740
Yeah,

21:27.740 --> 21:28.540
they make neat stuff

21:28.540 --> 21:29.220
and people say

21:29.220 --> 21:30.020
the iPod's great,

21:30.120 --> 21:30.600
but you know what?

21:30.640 --> 21:32.220
The iPod is way more expensive

21:32.220 --> 21:32.980
than every other

21:32.980 --> 21:34.040
MP3 player out there.

21:35.000 --> 21:35.140
So.

21:35.620 --> 21:36.420
But you get iTunes.

21:36.420 --> 21:38.360
Yeah,

21:38.480 --> 21:39.180
iTunes for Windows

21:39.180 --> 21:40.320
I've heard is a real disaster.

21:40.740 --> 21:41.080
Really?

21:41.260 --> 21:41.580
Changed?

21:41.760 --> 21:41.980
Yeah.

21:42.320 --> 21:42.540
Hmm.

21:43.100 --> 21:43.980
I heard for macOS

21:43.980 --> 21:44.520
it's great,

21:44.900 --> 21:45.840
but I heard for Windows

21:45.840 --> 21:46.680
it installs all kinds

21:46.680 --> 21:47.380
of weird crap

21:47.380 --> 21:48.480
and it's just a mess.

21:48.640 --> 21:49.480
Maybe it's been fixed.

21:49.840 --> 21:50.600
Please tell me

21:50.600 --> 21:51.520
it doesn't install Gator.

21:52.440 --> 21:52.720
No,

21:52.760 --> 21:52.880
no,

21:52.880 --> 21:53.000
no,

21:53.000 --> 21:53.320
I'm sure,

21:53.320 --> 21:53.600
well,

21:53.800 --> 21:54.500
I can't say I'm sure,

21:54.580 --> 21:55.340
but I would hope Apple's

21:55.340 --> 21:55.920
not that stupid.

21:56.320 --> 21:57.280
I don't know.

21:57.520 --> 21:59.160
iPod's just overpriced.

22:00.160 --> 22:00.960
That's what I think.

22:01.120 --> 22:01.980
And I think it's just like

22:01.980 --> 22:02.580
the rest of the hardware.

22:02.680 --> 22:03.320
It's overpriced,

22:03.320 --> 22:05.080
but they've got this cult following

22:05.080 --> 22:06.860
so they can get whatever they want.

22:06.940 --> 22:07.200
People say,

22:07.240 --> 22:07.300
oh,

22:07.320 --> 22:08.240
it's designed so nicely.

22:08.340 --> 22:08.760
You know what?

22:09.100 --> 22:10.020
I need an MP3 player

22:10.020 --> 22:10.660
to play music

22:10.660 --> 22:12.180
and that's it.

22:12.260 --> 22:13.280
I don't really care how it looks.

22:13.500 --> 22:13.720
Well,

22:13.740 --> 22:14.800
I can do that with my phone.

22:15.780 --> 22:16.280
There you go.

22:17.100 --> 22:18.120
I don't need an iPod

22:18.120 --> 22:18.840
to play MP3.

22:19.700 --> 22:20.280
There you go.

22:20.300 --> 22:21.360
And it's not a cult following.

22:21.480 --> 22:21.720
What are there,

22:21.780 --> 22:23.040
three million or something

22:23.040 --> 22:24.500
units sold

22:24.500 --> 22:25.440
or something like that?

22:26.580 --> 22:27.240
That's a lot.

22:28.460 --> 22:29.160
I suppose.

22:29.440 --> 22:29.620
I mean,

22:29.640 --> 22:30.280
compared to the rest

22:30.280 --> 22:30.980
of the market though,

22:31.140 --> 22:32.280
I think it's a cult following.

22:33.260 --> 22:34.540
How much market share

22:34.540 --> 22:35.180
does Apple have?

22:35.680 --> 22:36.720
I have no idea.

22:36.920 --> 22:37.140
I mean,

22:37.560 --> 22:38.540
I couldn't even tell you

22:38.540 --> 22:40.360
another competing MP3 player.

22:40.800 --> 22:41.160
Rio?

22:41.420 --> 22:42.320
Do they still make the Rio?

22:43.240 --> 22:43.600
Oh,

22:43.940 --> 22:44.180
okay.

22:44.360 --> 22:45.160
I thought you were talking about

22:45.160 --> 22:46.480
just Apple in general.

22:46.780 --> 22:47.000
Oh,

22:47.080 --> 22:47.220
no,

22:47.280 --> 22:47.420
no,

22:47.460 --> 22:47.560
no,

22:47.560 --> 22:47.660
no.

22:47.660 --> 22:48.100
I'm talking about

22:48.100 --> 22:48.760
just the iPod,

22:48.840 --> 22:50.400
just the portable MP3 player market.

22:51.740 --> 22:51.960
yeah,

22:52.000 --> 22:52.580
there's the Arcos.

22:52.680 --> 22:53.740
The Arcos makes a whole bunch

22:53.740 --> 22:55.100
of MP3 players

22:55.100 --> 22:55.900
and video players

22:55.900 --> 22:56.640
and stuff like that.

22:56.940 --> 22:57.920
There's another company

22:57.920 --> 22:58.720
that I can't remember

22:58.720 --> 22:59.360
the name of.

22:59.460 --> 23:00.760
I think it's Neo something.

23:00.760 --> 23:03.460
They have an MP3 player

23:03.460 --> 23:05.400
that has open source firmware

23:05.400 --> 23:06.320
so people have added

23:06.320 --> 23:07.180
like Ogg support

23:07.180 --> 23:07.820
and stuff to it.

23:07.900 --> 23:08.520
I think that is

23:08.520 --> 23:09.620
the coolest thing ever.

23:10.960 --> 23:12.300
And it's significantly cheaper

23:12.300 --> 23:13.200
than the iPod

23:13.200 --> 23:13.880
from what I remember.

23:14.880 --> 23:15.240
Hmm.

23:15.240 --> 23:16.100
Well,

23:16.260 --> 23:16.800
you know what?

23:16.980 --> 23:18.300
I'm going to look into that

23:18.300 --> 23:19.400
just for the simple fact

23:19.400 --> 23:20.560
of putting those links up

23:20.560 --> 23:21.100
in the show notes

23:21.100 --> 23:21.700
when the time comes

23:21.700 --> 23:22.920
so people can compare them

23:22.920 --> 23:23.240
and see.

23:23.780 --> 23:23.920
Yeah.

23:24.400 --> 23:25.040
Very cool.

23:25.620 --> 23:25.860
Damn,

23:25.940 --> 23:26.060
this,

23:26.340 --> 23:27.340
Apple ate up a whole bunch

23:27.340 --> 23:27.680
of time.

23:27.780 --> 23:27.880
See,

23:27.920 --> 23:28.400
that's the other thing

23:28.400 --> 23:29.080
I hate about Apple.

23:29.360 --> 23:30.320
We always get on rants

23:30.320 --> 23:30.880
about Apple

23:30.880 --> 23:31.880
and they waste all our time

23:31.880 --> 23:32.280
on the show

23:32.280 --> 23:32.820
and then we never get

23:32.820 --> 23:33.640
to talk about cool stuff.

23:33.760 --> 23:33.940
Oh,

23:34.000 --> 23:34.460
we're going to talk

23:34.460 --> 23:35.160
about cool stuff.

23:35.380 --> 23:35.580
Does it matter?

23:36.020 --> 23:36.380
All right,

23:36.460 --> 23:36.720
fair enough.

23:37.240 --> 23:37.500
Yeah,

23:37.600 --> 23:38.980
yeah,

23:39.380 --> 23:40.280
we've got plenty of time.

23:40.340 --> 23:41.000
We've got plenty of time

23:41.000 --> 23:41.880
to talk about cool stuff

23:41.880 --> 23:43.360
and we don't get into rants

23:43.360 --> 23:44.740
about Apple all the time.

23:45.400 --> 23:45.620
Yeah.

23:45.780 --> 23:46.400
There's some things

23:46.400 --> 23:47.180
I don't like about it,

23:47.180 --> 23:47.540
like I said,

23:47.600 --> 23:48.000
but I think,

23:48.100 --> 23:49.060
I like Apple's hardware.

23:49.180 --> 23:49.960
I think they make good hardware.

23:50.080 --> 23:50.960
I just wish they weren't

23:50.960 --> 23:51.840
the only ones that made it.

23:51.900 --> 23:52.240
That's all.

23:52.340 --> 23:53.420
That's my only beef with them.

23:54.980 --> 23:55.300
Oh,

23:55.460 --> 23:56.160
but anyway,

23:56.320 --> 23:57.300
this email again,

23:57.380 --> 23:58.220
we did get off that

23:58.220 --> 23:59.180
and this is very important

23:59.180 --> 24:00.860
and that is the Induce Act

24:00.860 --> 24:01.980
that it's called.

24:01.980 --> 24:02.220
Now,

24:02.360 --> 24:02.800
again,

24:03.020 --> 24:04.820
the reason we got on the Apple tangents

24:04.820 --> 24:06.340
is because I hope they do bring

24:06.340 --> 24:07.500
those Apple fanatics over

24:07.500 --> 24:08.640
to help fight the cause.

24:09.080 --> 24:09.820
That's more people

24:09.820 --> 24:11.660
to help stop this stupid Induce Act.

24:11.880 --> 24:12.780
And I've got to say,

24:12.860 --> 24:13.660
about Apple people,

24:13.780 --> 24:15.620
they are fanatical about Apple.

24:15.760 --> 24:16.040
Oh, yeah.

24:16.040 --> 24:16.720
When they hear about this

24:16.720 --> 24:17.780
and when this gets big,

24:18.060 --> 24:18.460
they're going to have

24:18.460 --> 24:19.260
a lot of support.

24:19.680 --> 24:19.860
Yeah.

24:19.900 --> 24:20.560
If nothing else,

24:20.620 --> 24:22.140
Apple's built tons of support

24:22.140 --> 24:23.700
for their hardware,

24:23.880 --> 24:24.140
software,

24:24.260 --> 24:25.160
and their company in general.

24:25.540 --> 24:25.900
Yeah,

24:25.940 --> 24:27.120
I think I can count on

24:27.120 --> 24:28.600
two definite emails

24:28.600 --> 24:30.020
from two specific people

24:30.020 --> 24:31.820
that I have in mind

24:31.820 --> 24:33.360
and they know who they are

24:33.360 --> 24:37.100
that are going to correct us

24:37.100 --> 24:38.260
on some of the stuff we said.

24:38.320 --> 24:39.080
I can guarantee it.

24:39.800 --> 24:40.760
Probably more than that,

24:40.820 --> 24:41.080
actually.

24:41.880 --> 24:42.480
But anyway,

24:42.700 --> 24:43.060
this was,

24:43.280 --> 24:43.680
and again,

24:43.780 --> 24:44.340
this email from

24:44.340 --> 24:45.240
Psycho Mind Lent,

24:45.340 --> 24:45.900
thought you should know

24:45.900 --> 24:46.940
about the Induce Act.

24:47.260 --> 24:48.140
I'm beyond words

24:48.140 --> 24:49.720
on how fucking ignorant this is.

24:49.800 --> 24:50.120
By the way,

24:50.180 --> 24:50.920
keep up the great work

24:50.920 --> 24:51.320
on the show.

24:51.400 --> 24:52.000
It's highly informative.

24:52.120 --> 24:52.680
I've learned a lot

24:52.680 --> 24:53.400
from listening to it.

24:53.840 --> 24:54.040
Okay.

24:54.840 --> 24:55.540
Thank you for that.

24:55.620 --> 24:56.920
But the Induce Act,

24:56.960 --> 24:57.780
let's talk about this

24:57.780 --> 24:58.120
for a minute

24:58.120 --> 24:58.940
because this really

24:58.940 --> 24:59.900
pisses me off

24:59.900 --> 25:01.860
real,

25:02.000 --> 25:02.380
real,

25:02.500 --> 25:02.960
real bad.

25:03.440 --> 25:03.960
Go for it.

25:03.960 --> 25:04.720
Yeah.

25:04.960 --> 25:06.200
If you have a heart condition

25:06.200 --> 25:07.280
or are pregnant

25:07.280 --> 25:08.140
or are nursing a child,

25:08.220 --> 25:08.940
you probably want to

25:08.940 --> 25:09.740
step away from the radio.

25:11.020 --> 25:11.320
See,

25:12.360 --> 25:13.240
the problem with it,

25:13.280 --> 25:13.480
again,

25:13.560 --> 25:13.860
you know what,

25:13.860 --> 25:15.080
I'm also going to

25:15.080 --> 25:16.200
clarify something else here.

25:17.720 --> 25:19.380
If we get right down to it,

25:19.420 --> 25:20.400
the fact and the truth

25:20.400 --> 25:21.140
of the matter is,

25:21.180 --> 25:21.440
and yes,

25:21.500 --> 25:22.400
people can debate this,

25:22.460 --> 25:23.920
but my opinion on this is,

25:24.260 --> 25:25.540
it's well-founded.

25:26.500 --> 25:27.860
They want to stop

25:27.860 --> 25:29.840
out-and-out piracy,

25:30.360 --> 25:31.480
or at least so they claim.

25:31.600 --> 25:31.740
Now,

25:31.760 --> 25:32.820
I don't think that's true,

25:32.960 --> 25:35.180
but I'm not in any way

25:35.180 --> 25:36.360
condoning or insinuating

25:36.360 --> 25:36.700
that,

25:36.780 --> 25:37.520
you know,

25:38.440 --> 25:39.420
mass pirating

25:39.420 --> 25:40.140
and selling,

25:40.340 --> 25:40.640
you know,

25:40.760 --> 25:41.560
bootleg and all that

25:41.560 --> 25:42.120
kind of stuff,

25:42.540 --> 25:43.980
that's absolutely morally

25:43.980 --> 25:45.200
wrong in my eyes.

25:45.260 --> 25:45.460
Now,

25:45.580 --> 25:46.440
I'm not talking about

25:46.440 --> 25:47.460
personal downloads

25:47.460 --> 25:48.340
and stuff like that.

25:48.580 --> 25:49.440
My feelings on that

25:49.440 --> 25:50.080
I've made clear.

25:50.180 --> 25:51.320
I've bought a lot of albums

25:51.320 --> 25:52.600
and gone to a lot of movies

25:52.600 --> 25:53.000
and stuff

25:53.000 --> 25:54.780
after checking them out first,

25:54.880 --> 25:56.020
try before you buy a thing.

25:56.340 --> 25:57.720
But out-and-out piracy

25:57.720 --> 25:59.260
is absolutely wrong.

25:59.600 --> 26:00.880
And if the intent on this,

26:00.980 --> 26:01.200
which,

26:01.200 --> 26:04.580
in a perfect world

26:04.580 --> 26:05.320
would be

26:05.320 --> 26:06.760
passing this act

26:06.760 --> 26:07.900
to try to give them

26:07.900 --> 26:09.280
protection

26:09.280 --> 26:10.380
from out-and-out

26:10.380 --> 26:12.380
hardcore piracy.

26:12.460 --> 26:12.620
Like,

26:12.660 --> 26:13.340
when I was at Hope

26:13.340 --> 26:13.820
in New York,

26:13.900 --> 26:14.800
I don't know how many people

26:14.800 --> 26:15.360
I saw on the street

26:15.360 --> 26:17.040
selling me bootlegs DVDs

26:17.040 --> 26:18.100
of movies that were

26:18.100 --> 26:18.700
in the theater.

26:20.080 --> 26:20.260
Yeah.

26:20.600 --> 26:20.960
You know?

26:21.080 --> 26:21.360
So,

26:21.460 --> 26:22.080
they're out there

26:22.080 --> 26:23.220
and that kind of stuff,

26:24.560 --> 26:25.620
even though I might have

26:25.620 --> 26:25.960
bought one,

26:26.180 --> 26:27.940
I don't condone.

26:28.260 --> 26:28.540
Actually,

26:28.600 --> 26:29.060
I did not.

26:29.120 --> 26:29.740
I honestly didn't.

26:29.840 --> 26:30.040
But,

26:30.040 --> 26:31.520
I was tempted.

26:33.260 --> 26:34.640
That is what this is

26:34.640 --> 26:35.800
trying to protect.

26:35.900 --> 26:36.220
And I

26:36.220 --> 26:38.500
agree with the

26:38.500 --> 26:39.600
heart of what

26:39.600 --> 26:40.280
they're trying to do

26:40.280 --> 26:40.800
with this,

26:41.200 --> 26:42.360
but they're trying to

26:42.360 --> 26:43.600
make it so overly

26:43.600 --> 26:45.160
liberal and so broad

26:45.160 --> 26:46.660
that it's going to

26:46.660 --> 26:48.160
restrict everything.

26:48.820 --> 26:49.780
And of course,

26:50.500 --> 26:51.380
that is what the

26:51.380 --> 26:51.940
MPAA

26:51.940 --> 26:52.980
and the RIAA

26:52.980 --> 26:53.760
and all the other

26:53.760 --> 26:54.280
AA's,

26:54.360 --> 26:54.660
AAA,

26:54.940 --> 26:55.660
every other fucking

26:55.660 --> 26:57.340
AAA out there

26:57.340 --> 26:58.780
is trying to do

26:58.780 --> 26:59.140
with this.

26:59.240 --> 26:59.980
They want to stop

26:59.980 --> 27:01.160
all sharing.

27:01.620 --> 27:02.760
They've been trying it.

27:03.240 --> 27:04.000
And that's what just

27:04.000 --> 27:05.280
really pisses me off

27:05.280 --> 27:06.100
about this whole thing

27:06.100 --> 27:06.660
is they won't

27:06.660 --> 27:07.700
fucking give up.

27:08.360 --> 27:09.060
Guess what?

27:09.180 --> 27:10.100
It's over.

27:10.680 --> 27:11.600
It was over

27:11.600 --> 27:13.540
when Napster blew up.

27:14.000 --> 27:14.960
You had already

27:14.960 --> 27:16.320
lost this fight.

27:17.000 --> 27:17.820
You will never

27:17.820 --> 27:18.560
come back

27:18.560 --> 27:19.140
and win.

27:19.320 --> 27:20.420
It's the 12th round.

27:20.840 --> 27:21.620
You're coming out

27:21.620 --> 27:22.500
the corner swinging,

27:22.740 --> 27:23.120
trying.

27:23.320 --> 27:24.040
I give you credit

27:24.040 --> 27:24.500
for that,

27:24.700 --> 27:25.320
but you've already

27:25.320 --> 27:25.780
lost.

27:26.220 --> 27:27.000
You're down on the

27:27.000 --> 27:27.860
judge's scorecard.

27:27.920 --> 27:28.460
You haven't won a

27:28.460 --> 27:29.460
single fucking round

27:29.460 --> 27:30.180
of this match.

27:31.160 --> 27:32.320
Fucking sickens me

27:32.320 --> 27:32.920
that they're still

27:32.920 --> 27:33.860
trying to fight

27:33.860 --> 27:36.040
so they don't want

27:36.040 --> 27:36.980
to lose control.

27:37.940 --> 27:38.440
And that's what

27:38.440 --> 27:39.100
the Induce Act,

27:39.180 --> 27:39.700
that's the problem.

27:39.800 --> 27:40.380
It reminds me of

27:40.380 --> 27:41.060
the Patriot Act.

27:41.140 --> 27:42.800
It's so restrictive

27:42.800 --> 27:43.760
that it doesn't want

27:43.760 --> 27:45.020
to allow people to do

27:45.020 --> 27:46.400
what things that they

27:46.400 --> 27:47.240
should be able to do

27:47.240 --> 27:47.800
with their,

27:48.860 --> 27:49.940
they should have the

27:49.940 --> 27:50.840
freedom to use,

27:50.940 --> 27:51.640
fair use.

27:51.780 --> 27:52.280
And they're trying

27:52.280 --> 27:53.240
to get rid of fair use

27:53.240 --> 27:54.040
like they've always

27:54.040 --> 27:54.940
been trying to get rid

27:54.940 --> 27:55.180
of it.

27:55.640 --> 27:56.420
They're absolutely

27:56.420 --> 27:57.380
locking this down

27:57.380 --> 27:58.240
and it's because

27:58.240 --> 28:00.200
they think with all

28:00.200 --> 28:01.020
that money they have,

28:01.100 --> 28:01.860
they go in and they

28:01.860 --> 28:03.160
pay off the lobbyists,

28:03.620 --> 28:04.500
they send their

28:04.500 --> 28:05.080
lobbyists in there

28:05.080 --> 28:05.860
to pay off the,

28:05.860 --> 28:08.540
our elected officials,

28:09.260 --> 28:10.540
which should disgust

28:10.540 --> 28:11.060
us all.

28:11.700 --> 28:12.560
And on one of these

28:12.560 --> 28:13.240
sites I think it

28:13.240 --> 28:14.320
showed how much

28:14.320 --> 28:15.260
money goes to a lot

28:15.260 --> 28:15.800
of these people.

28:15.900 --> 28:17.240
And it's bipartisan,

28:17.460 --> 28:18.320
it goes across the

28:18.320 --> 28:19.040
board, so it's not

28:19.040 --> 28:19.640
a Democrat or

28:19.640 --> 28:20.340
Republican thing.

28:20.560 --> 28:22.320
They're all taking

28:22.320 --> 28:23.320
money under the table.

28:24.440 --> 28:25.820
So the problem

28:25.820 --> 28:28.620
with this is trying

28:28.620 --> 28:29.360
to fight everything

28:29.360 --> 28:30.260
through legislation

28:30.260 --> 28:32.400
does nothing but

28:32.400 --> 28:33.460
stifle creativity

28:33.460 --> 28:34.620
and stifle innovation

28:34.620 --> 28:35.360
in this country.

28:36.740 --> 28:37.820
And I don't

28:37.820 --> 28:38.540
understand, to me

28:38.540 --> 28:39.660
I'm a logical guy.

28:39.860 --> 28:40.580
I mean, stop me,

28:40.920 --> 28:41.900
correct me if any

28:41.900 --> 28:42.800
point in here I say

28:42.800 --> 28:43.400
something that is

28:43.400 --> 28:44.520
illogical or something

28:44.520 --> 28:45.780
that you, that I,

28:45.880 --> 28:46.620
that I'm just off

28:46.620 --> 28:47.020
about, okay?

28:47.060 --> 28:48.020
You stop me anytime

28:48.020 --> 28:48.600
and tell me.

28:49.000 --> 28:49.580
I'll do that.

28:49.680 --> 28:50.660
Okay, here's the

28:50.660 --> 28:50.920
thing.

28:51.940 --> 28:52.940
It was like, what,

28:53.000 --> 28:53.900
then, I, we'll say

28:53.900 --> 28:54.720
the 80s, somewhere

28:54.720 --> 28:55.880
around the 70s, 80s,

28:55.900 --> 28:56.300
I don't know, when

28:56.300 --> 28:57.540
VCRs first came out.

28:58.480 --> 28:59.560
And they tried this

28:59.560 --> 29:00.340
shit back then.

29:00.620 --> 29:01.280
They didn't want to

29:01.280 --> 29:03.420
lose control the same

29:03.420 --> 29:04.100
way they're trying not

29:04.100 --> 29:04.900
to lose control now.

29:04.980 --> 29:05.980
Again, it's lost, it's

29:05.980 --> 29:06.180
over.

29:06.340 --> 29:07.080
They already lost this

29:07.080 --> 29:07.540
battle, they're still

29:07.540 --> 29:07.760
fighting.

29:07.860 --> 29:08.940
But again, they didn't

29:08.940 --> 29:09.740
want to lose control.

29:10.420 --> 29:11.660
But look what

29:11.660 --> 29:12.560
happened!

29:12.560 --> 29:14.960
This is factual

29:14.960 --> 29:16.200
information, you

29:16.200 --> 29:16.800
fuckers.

29:17.060 --> 29:17.740
God, I can't

29:17.740 --> 29:18.420
understand this.

29:19.120 --> 29:20.580
Because, thankfully,

29:21.460 --> 29:22.760
they lost those

29:22.760 --> 29:23.800
cases and the VCR

29:23.800 --> 29:24.760
was allowed to be

29:24.760 --> 29:25.440
created and people

29:25.440 --> 29:26.380
were allowed to copy

29:26.380 --> 29:27.160
and record movies.

29:27.480 --> 29:28.320
What came out of

29:28.320 --> 29:28.520
that?

29:28.920 --> 29:30.600
A multi-billion

29:30.600 --> 29:31.460
dollar fucking

29:31.460 --> 29:32.500
industry came out

29:32.500 --> 29:32.840
of that.

29:33.500 --> 29:34.460
The United States

29:34.460 --> 29:35.760
prospered, electronics

29:35.760 --> 29:37.280
manufacturers prospered,

29:37.540 --> 29:38.460
the movie industry

29:38.460 --> 29:39.400
prospered as much as

29:39.400 --> 29:39.880
they don't want to

29:39.880 --> 29:40.440
admit it.

29:41.000 --> 29:42.140
VCR movies started

29:42.140 --> 29:42.940
selling through the

29:42.940 --> 29:43.120
roof.

29:43.240 --> 29:44.740
They made multi-billions

29:44.740 --> 29:46.660
of dollars on selling

29:46.660 --> 29:47.660
VCR movies.

29:48.160 --> 29:48.800
You know what we

29:48.800 --> 29:49.800
didn't have before the

29:49.800 --> 29:50.240
VCR?

29:50.880 --> 29:51.400
Blockbuster.

29:51.780 --> 29:52.700
We didn't have video

29:52.700 --> 29:53.800
rental stores of any

29:53.800 --> 29:54.160
kind.

29:54.480 --> 29:56.360
Now you have multi-bazillion

29:56.360 --> 29:57.900
dollar industries.

29:58.260 --> 29:58.720
You have a

29:58.720 --> 29:59.760
Blockbuster, a Fortune

29:59.760 --> 30:00.800
100 company?

30:01.560 --> 30:02.360
Fortune 500?

30:02.500 --> 30:02.900
I don't know what

30:02.900 --> 30:03.100
they are.

30:03.160 --> 30:03.920
This multi-billion

30:03.920 --> 30:06.480
dollar company based

30:06.480 --> 30:07.020
on this.

30:07.340 --> 30:08.380
Based on innovation,

30:08.820 --> 30:09.360
technology,

30:09.520 --> 30:10.800
creativity, all these

30:10.800 --> 30:11.720
things that sprung up

30:11.720 --> 30:12.360
around it.

30:13.220 --> 30:14.420
These are facts!

30:15.000 --> 30:16.160
This is what happens

30:16.160 --> 30:17.220
when you progress with

30:17.220 --> 30:18.840
ideas and move into

30:18.840 --> 30:19.460
the future.

30:20.520 --> 30:21.040
I agree.

30:21.320 --> 30:22.560
It happened again with

30:22.560 --> 30:23.420
DVDs.

30:23.920 --> 30:25.300
DVD players took off.

30:25.360 --> 30:26.120
You can buy DVD

30:26.120 --> 30:28.100
movies and it's a

30:28.100 --> 30:29.080
multi-billion dollar

30:29.080 --> 30:29.340
industry.

30:29.460 --> 30:29.960
They're selling the

30:29.960 --> 30:30.320
hardware.

30:30.460 --> 30:31.020
They're selling the

30:31.020 --> 30:31.340
media.

30:31.620 --> 30:32.360
They're selling DVD

30:32.360 --> 30:32.860
burners.

30:32.940 --> 30:33.680
They're selling DVD

30:33.680 --> 30:34.420
ROM drives.

30:34.520 --> 30:34.860
They're selling

30:34.860 --> 30:35.940
everything.

30:36.080 --> 30:37.340
Multi-bazillions of

30:37.340 --> 30:37.780
dollars.

30:38.580 --> 30:38.920
What?

30:38.920 --> 30:40.540
Please, please, dear

30:40.540 --> 30:42.200
God in heaven, tell me

30:42.200 --> 30:42.900
what am I missing?

30:43.620 --> 30:44.640
Tell me why they would

30:44.640 --> 30:45.400
not want...

30:45.400 --> 30:45.540
Why?

30:46.380 --> 30:48.740
I can't even...

30:48.740 --> 30:50.120
I think there's steam

30:50.120 --> 30:50.900
coming out of my ears.

30:51.000 --> 30:52.180
I can't understand this

30:52.180 --> 30:53.160
for the life of me.

30:53.600 --> 30:55.520
What in the hell are

30:55.520 --> 30:56.420
they thinking about?

30:56.420 --> 30:58.420
I'm not really sure.

30:58.880 --> 30:59.800
And maybe...

30:59.800 --> 31:00.780
Hopefully this doesn't

31:00.780 --> 31:01.380
hit you with too

31:01.380 --> 31:02.220
rectum of a point.

31:02.380 --> 31:04.740
I know that in Canada,

31:04.920 --> 31:06.920
at least, there's a tax

31:06.920 --> 31:09.280
on CD recorders and CDR

31:09.280 --> 31:10.400
media and all this stuff

31:10.400 --> 31:11.340
like that so that the

31:11.340 --> 31:12.520
recording industry is not

31:12.520 --> 31:12.980
a tax.

31:13.120 --> 31:14.700
It's some type of...

31:14.700 --> 31:15.060
I don't know.

31:15.100 --> 31:16.220
They have a term for it

31:16.220 --> 31:17.180
so that it's not taxed.

31:17.680 --> 31:18.180
A levy.

31:18.960 --> 31:19.820
Yeah, something like that.

31:19.820 --> 31:20.440
Yeah, it's a levy.

31:20.540 --> 31:21.340
We talked about it on the

31:21.340 --> 31:21.680
show before.

31:21.760 --> 31:22.600
Gluco from Canada

31:22.600 --> 31:23.700
notified us about that.

31:23.780 --> 31:24.440
I remember that.

31:24.940 --> 31:25.440
Right, okay.

31:25.620 --> 31:26.460
And then, you know,

31:26.480 --> 31:27.140
the recording industry

31:27.140 --> 31:27.960
up there gets money

31:27.960 --> 31:30.100
off every CD recordable

31:30.100 --> 31:31.580
disc that's sold in Canada.

31:32.080 --> 31:33.040
Maybe they're...

31:33.040 --> 31:34.020
You know, I thought

31:34.020 --> 31:34.700
for a little while

31:34.700 --> 31:35.500
that they had that

31:35.500 --> 31:36.340
in the U.S. already,

31:36.440 --> 31:37.120
but if they don't have it,

31:37.140 --> 31:37.740
maybe that's something

31:37.740 --> 31:38.500
that they're looking for.

31:38.780 --> 31:39.780
They want a piece of

31:39.780 --> 31:41.580
any piece of technology

31:41.580 --> 31:44.040
that's allowed to record

31:44.040 --> 31:44.540
or...

31:44.540 --> 31:46.120
Well, see, no, I disagree.

31:46.280 --> 31:46.940
I don't think they want

31:46.940 --> 31:47.420
a piece.

31:47.680 --> 31:48.860
I think they want it all.

31:50.300 --> 31:51.480
They want it all.

31:52.480 --> 31:53.340
What they want...

31:53.340 --> 31:53.740
The reason they're

31:53.740 --> 31:54.320
fighting this

31:54.320 --> 31:55.920
is all those things

31:55.920 --> 31:56.620
I just mentioned,

31:57.080 --> 31:58.240
a multi-billion dollar

31:58.240 --> 31:59.580
Fortune 100 company

31:59.580 --> 32:00.560
of Blockbuster.

32:01.460 --> 32:02.240
They don't think

32:02.240 --> 32:03.480
Blockbuster should have that.

32:03.620 --> 32:04.340
They want that

32:04.340 --> 32:05.300
multi-billion dollar.

32:05.380 --> 32:05.840
They don't want to

32:05.840 --> 32:06.500
give that control

32:06.500 --> 32:07.380
and let somebody else

32:07.380 --> 32:07.880
make money.

32:08.220 --> 32:09.100
They want it all

32:09.100 --> 32:09.700
for themselves

32:09.700 --> 32:10.840
to pad their pockets.

32:11.520 --> 32:12.160
Well, shit,

32:12.240 --> 32:12.980
if that's the case,

32:13.060 --> 32:13.860
then they can start

32:13.860 --> 32:14.800
another chain

32:14.800 --> 32:15.360
of these fucking

32:15.360 --> 32:15.980
rental places

32:15.980 --> 32:17.340
and knock Blockbuster out.

32:17.400 --> 32:18.180
What's the problem with that?

32:18.420 --> 32:19.180
They don't have

32:19.180 --> 32:20.140
the ability to do it.

32:20.560 --> 32:21.580
They'd rather sue.

32:21.580 --> 32:22.560
They would rather go

32:22.560 --> 32:23.740
through the legislation

32:23.740 --> 32:25.340
process.

32:26.280 --> 32:27.100
They would rather sue

32:27.100 --> 32:27.880
everybody to try

32:27.880 --> 32:28.500
to maintain that

32:28.500 --> 32:29.100
control back

32:29.100 --> 32:30.480
instead of innovating.

32:31.000 --> 32:32.200
And that's my whole problem.

32:32.440 --> 32:33.540
It stops innovation.

32:33.760 --> 32:34.220
And you know what?

32:34.300 --> 32:35.360
It's going to end up...

32:35.360 --> 32:35.860
And this is why

32:35.860 --> 32:36.600
right now there's a

32:36.600 --> 32:37.660
phenomenon going on

32:37.660 --> 32:39.400
of outsourcing

32:39.400 --> 32:40.540
to offshore places.

32:41.420 --> 32:42.240
This country,

32:42.340 --> 32:43.460
the United States of America,

32:43.560 --> 32:44.580
is losing business.

32:45.580 --> 32:46.920
We're losing jobs.

32:46.920 --> 32:47.900
And don't turn it

32:47.900 --> 32:48.360
into a bunch

32:48.360 --> 32:49.400
of political bullshit.

32:49.860 --> 32:50.520
The bottom line

32:50.520 --> 32:51.300
is it's these kind

32:51.300 --> 32:51.820
of companies

32:51.820 --> 32:53.140
and these frivolous lawsuits

32:53.140 --> 32:54.020
and these frivolous,

32:54.280 --> 32:55.300
these stupid laws

32:55.300 --> 32:56.120
that we pass.

32:56.600 --> 32:57.640
Again, bipartisan.

32:57.900 --> 32:59.180
It's not a particular...

32:59.180 --> 33:00.420
Everybody fucking

33:00.420 --> 33:00.940
getting paid

33:00.940 --> 33:01.720
under the table

33:01.720 --> 33:02.760
that's ruining

33:02.760 --> 33:03.420
this country.

33:03.960 --> 33:05.400
And then we outsource jobs

33:05.400 --> 33:06.300
and we have people

33:06.300 --> 33:07.220
manufacturing all

33:07.220 --> 33:07.780
of our hardware

33:07.780 --> 33:08.940
in Hong Kong

33:08.940 --> 33:09.520
and China

33:09.520 --> 33:10.180
and Mexico

33:10.180 --> 33:11.320
and South America.

33:11.700 --> 33:12.360
Well, that's great

33:12.360 --> 33:12.720
for them

33:12.720 --> 33:13.180
and I'm all

33:13.180 --> 33:14.140
for the global economy.

33:14.500 --> 33:15.180
But understand

33:15.180 --> 33:16.260
why it's become this.

33:16.260 --> 33:17.180
Don't bitch and say,

33:17.560 --> 33:18.240
oh, so-and-so

33:18.240 --> 33:19.220
outsourced my job.

33:19.280 --> 33:19.880
Well, guess what?

33:20.400 --> 33:21.620
You let stuff like this

33:21.620 --> 33:23.060
happen as a voting citizen.

33:23.680 --> 33:24.860
You stay uneducated

33:24.860 --> 33:25.580
and you don't realize

33:25.580 --> 33:26.580
that this stuff goes on.

33:26.940 --> 33:27.460
I'm sorry.

33:27.540 --> 33:28.440
I don't feel real sorry

33:28.440 --> 33:28.900
for you.

33:29.700 --> 33:30.640
Educate yourself

33:30.640 --> 33:31.920
and watch this shit

33:31.920 --> 33:32.900
go on and fight it

33:32.900 --> 33:34.080
so that it doesn't happen.

33:35.140 --> 33:36.820
Let this country innovate.

33:37.500 --> 33:39.000
Let this country progress.

33:39.320 --> 33:41.300
Let this country move forward,

33:41.840 --> 33:42.720
not backward.

33:43.120 --> 33:44.620
Don't tie everything up

33:44.620 --> 33:46.540
and the legal system.

33:48.540 --> 33:49.220
I agree.

33:50.420 --> 33:51.240
The legal system

33:51.240 --> 33:52.180
is definitely overused

33:52.180 --> 33:53.460
for profit

33:53.460 --> 33:54.520
in these huge companies.

33:54.880 --> 33:56.200
But, you know.

33:56.540 --> 33:57.760
Our legal system...

33:57.760 --> 33:58.940
They control the legal system.

33:59.100 --> 33:59.880
So what are you going to do?

34:00.000 --> 34:01.160
Well, and that's a damn shame.

34:01.240 --> 34:02.020
The legal system

34:02.020 --> 34:03.540
has stunted

34:03.540 --> 34:04.640
the growth of this country.

34:05.300 --> 34:06.560
And that's an absolute

34:06.560 --> 34:07.840
factual statement.

34:07.940 --> 34:08.740
You can quote that.

34:08.960 --> 34:09.760
Our legal system,

34:09.820 --> 34:11.280
the United States legal system,

34:11.360 --> 34:12.260
the judicial system,

34:12.260 --> 34:13.920
has stunted the growth

34:13.920 --> 34:15.280
of the United States of America

34:15.280 --> 34:16.900
with the government's help.

34:17.380 --> 34:18.620
Well, you know what's amazing

34:18.620 --> 34:19.060
to me, though?

34:19.100 --> 34:19.600
Like you said,

34:19.640 --> 34:20.160
on that webpage

34:20.160 --> 34:20.980
they have lists

34:20.980 --> 34:22.800
of people that take money

34:22.800 --> 34:25.320
from the recording industry

34:25.320 --> 34:26.180
and Hollywood

34:26.180 --> 34:27.240
and all this other kind of crap.

34:27.460 --> 34:27.680
Right.

34:28.460 --> 34:29.760
Obviously, people know

34:29.760 --> 34:30.360
that this money

34:30.360 --> 34:31.380
is going into

34:31.380 --> 34:32.140
these people's pockets.

34:32.560 --> 34:33.900
And I don't want to

34:33.900 --> 34:35.500
start anti-Democrat

34:35.500 --> 34:36.280
or anti-Republican,

34:36.320 --> 34:36.460
whatever.

34:36.620 --> 34:38.440
The only person's name

34:38.440 --> 34:39.020
that I remember

34:39.020 --> 34:39.620
on that list

34:39.620 --> 34:41.180
is Hillary Clinton.

34:41.180 --> 34:41.760
Because she was

34:41.760 --> 34:42.800
at the very, very top.

34:42.880 --> 34:43.360
And she had like

34:43.360 --> 34:45.780
$1.16 million from them.

34:46.440 --> 34:47.420
A lot of fucking money.

34:47.500 --> 34:48.260
How does this happen?

34:48.500 --> 34:49.400
And, you know,

34:49.720 --> 34:52.140
what makes it legal?

34:53.200 --> 34:55.340
I can't for the life of me

34:55.340 --> 34:56.000
figure that out.

34:56.520 --> 34:56.760
I mean,

34:56.800 --> 34:57.680
if that's not a conflict

34:57.680 --> 34:58.200
of interest,

34:58.280 --> 34:59.140
I don't know what is.

34:59.640 --> 34:59.900
Yeah.

35:00.180 --> 35:01.220
Just the whole concept

35:01.220 --> 35:01.840
of lobbying

35:01.840 --> 35:02.700
and giving money

35:02.700 --> 35:03.240
to these people

35:03.240 --> 35:04.160
is a complete conflict

35:04.160 --> 35:04.600
of interest.

35:04.720 --> 35:05.400
And it's not something

35:05.400 --> 35:05.980
that should be allowed

35:05.980 --> 35:06.420
in government.

35:07.280 --> 35:07.420
Yeah.

35:08.540 --> 35:09.560
But somehow,

35:09.820 --> 35:10.100
obviously,

35:10.100 --> 35:11.040
somehow the law is written.

35:11.520 --> 35:12.380
Either the law is written

35:12.380 --> 35:12.860
in such a way

35:12.860 --> 35:13.300
where they're allowed

35:13.300 --> 35:13.720
to do it

35:13.720 --> 35:14.780
or they just never

35:14.780 --> 35:15.720
get prosecuted

35:15.720 --> 35:16.560
for any of this crap.

35:16.920 --> 35:16.980
Yeah.

35:17.080 --> 35:18.860
I wish people,

35:18.980 --> 35:19.540
I wish that we weren't

35:19.540 --> 35:19.960
allowed to have

35:19.960 --> 35:21.220
any kind of multiple terms.

35:21.300 --> 35:22.000
I think there should be

35:22.000 --> 35:22.820
no incumbents.

35:23.840 --> 35:24.500
Because the longer

35:24.500 --> 35:25.140
they stay in there,

35:25.180 --> 35:25.860
the longer time

35:25.860 --> 35:26.620
they have to get corrupt.

35:27.160 --> 35:27.620
Oh, yeah.

35:27.700 --> 35:28.020
Definitely.

35:30.980 --> 35:31.300
Anyway,

35:32.740 --> 35:32.880
I,

35:33.420 --> 35:33.580
the,

35:33.960 --> 35:34.220
if,

35:34.340 --> 35:34.500
okay,

35:34.560 --> 35:34.980
here's what,

35:35.440 --> 35:36.480
here's Stank Dog's

35:36.480 --> 35:37.280
ideal world.

35:37.380 --> 35:38.400
Here's how it should happen.

35:38.480 --> 35:39.480
Here's what should happen

35:39.480 --> 35:40.280
out of this whole thing.

35:40.820 --> 35:41.760
What should happen

35:41.760 --> 35:43.140
is the RAAA

35:43.140 --> 35:44.600
needs to shut

35:44.600 --> 35:45.960
the fuck up.

35:46.920 --> 35:48.240
Stop suing everybody.

35:49.100 --> 35:49.800
Put your hands

35:49.800 --> 35:50.460
on your desk.

35:50.620 --> 35:51.380
Count to ten

35:51.380 --> 35:51.960
and say,

35:52.120 --> 35:53.320
we lost.

35:54.020 --> 35:55.020
We are not

35:55.020 --> 35:56.480
ever going to be able

35:56.480 --> 35:57.580
to sue everybody

35:57.580 --> 35:58.520
and catch up

35:58.520 --> 35:59.240
with the,

35:59.720 --> 36:00.500
the pace

36:00.500 --> 36:01.200
and the growth

36:01.200 --> 36:01.860
of the internet

36:01.860 --> 36:03.240
and technology

36:03.240 --> 36:03.900
in general.

36:03.900 --> 36:05.160
just put your hands

36:05.160 --> 36:05.660
down and say,

36:05.740 --> 36:06.140
you know what?

36:06.540 --> 36:07.340
We give up.

36:07.660 --> 36:08.460
We lost.

36:09.120 --> 36:10.060
Let's figure out

36:10.060 --> 36:10.660
a nice,

36:10.820 --> 36:11.260
fair,

36:11.600 --> 36:12.400
balanced way

36:12.400 --> 36:13.980
to make this work.

36:14.600 --> 36:15.280
Let's come up

36:15.280 --> 36:15.700
with something

36:15.700 --> 36:16.260
that's fair

36:16.260 --> 36:17.220
to all parties.

36:17.860 --> 36:18.640
But they're not

36:18.640 --> 36:19.400
willing to do that

36:19.400 --> 36:20.200
for reasons I said

36:20.200 --> 36:20.500
earlier.

36:20.600 --> 36:21.960
They want full control.

36:22.080 --> 36:22.780
They're not going

36:22.780 --> 36:23.440
to compromise

36:23.440 --> 36:24.580
anything

36:24.580 --> 36:26.020
at all.

36:26.700 --> 36:28.040
They knew about this

36:28.040 --> 36:28.920
a long time ago.

36:29.080 --> 36:29.520
Again,

36:29.720 --> 36:30.540
it was Napster.

36:31.500 --> 36:32.180
And then everything

36:32.180 --> 36:33.360
that came after Napster,

36:33.480 --> 36:33.860
of course,

36:34.000 --> 36:35.100
the floodgates were open

36:35.100 --> 36:35.340
then.

36:35.420 --> 36:36.340
You could stop Napster,

36:36.480 --> 36:36.720
fine.

36:36.780 --> 36:37.800
You can try to stop Napster.

36:38.180 --> 36:38.940
You never stopped

36:38.940 --> 36:39.460
peer-to-peer

36:39.460 --> 36:40.640
because every time,

36:41.100 --> 36:42.040
every one you sue,

36:42.140 --> 36:42.660
there's another one

36:42.660 --> 36:43.260
popping up

36:43.260 --> 36:44.460
and then encrypted ones

36:44.460 --> 36:45.400
and,

36:45.520 --> 36:46.080
you know,

36:46.660 --> 36:47.380
it's just,

36:47.500 --> 36:47.960
you're not going

36:47.960 --> 36:48.360
to stop it.

36:48.440 --> 36:49.840
It's too late.

36:50.540 --> 36:51.460
It's too late.

36:52.340 --> 36:52.740
So,

36:53.760 --> 36:54.760
while they were busy

36:54.760 --> 36:55.440
suing the hell out

36:55.440 --> 36:55.940
of everybody,

36:56.340 --> 36:57.280
as much as we just

36:57.280 --> 36:58.220
bashed Apple a little

36:58.220 --> 36:58.620
bit ago,

36:58.920 --> 37:00.280
somebody came up

37:00.280 --> 37:00.920
and realized that

37:00.920 --> 37:02.840
iTunes is a fair way.

37:03.020 --> 37:04.220
Some would debate that,

37:04.280 --> 37:05.020
but at least it's a

37:05.020 --> 37:06.200
compromise of some sort.

37:07.780 --> 37:08.940
There's been several

37:08.940 --> 37:10.200
things like iTunes,

37:10.460 --> 37:11.600
several other places

37:11.600 --> 37:12.440
where you can

37:12.440 --> 37:14.360
download music

37:14.360 --> 37:15.540
and pay per song

37:15.540 --> 37:16.320
or pay a reasonable

37:16.320 --> 37:17.180
price for it.

37:17.520 --> 37:17.720
Right.

37:17.720 --> 37:18.800
Or pay a monthly price

37:18.800 --> 37:19.480
and download a few

37:19.480 --> 37:19.920
at a time.

37:20.220 --> 37:20.460
Now,

37:20.680 --> 37:21.540
if you want to debate

37:21.540 --> 37:22.800
those individually,

37:23.000 --> 37:23.460
that's fine.

37:23.520 --> 37:24.220
I know a lot of people

37:24.220 --> 37:25.000
don't think that you

37:25.000 --> 37:25.860
should pay anything.

37:26.620 --> 37:26.880
You know,

37:26.940 --> 37:27.740
that's some person's

37:27.740 --> 37:28.060
opinion,

37:28.180 --> 37:28.340
whatever.

37:28.340 --> 37:29.580
I'm saying at least

37:29.580 --> 37:30.900
these are compromises

37:30.900 --> 37:32.180
and options that you

37:32.180 --> 37:32.560
have.

37:33.080 --> 37:34.460
Where the RIA and the

37:34.460 --> 37:34.860
MPAA,

37:35.000 --> 37:35.480
they don't want you

37:35.480 --> 37:36.200
to have options.

37:36.300 --> 37:37.240
They want full control

37:37.240 --> 37:38.100
and they want to tell

37:38.100 --> 37:38.780
you how you're going

37:38.780 --> 37:40.840
to use their movies

37:40.840 --> 37:41.920
and their intellectual

37:41.920 --> 37:42.520
property.

37:43.360 --> 37:43.600
Okay?

37:43.700 --> 37:44.460
At least these are

37:44.460 --> 37:44.900
options.

37:45.080 --> 37:45.240
So,

37:45.380 --> 37:46.140
debating any one of

37:46.140 --> 37:46.280
those,

37:46.380 --> 37:46.940
that's fine.

37:47.340 --> 37:47.780
But,

37:48.180 --> 37:49.080
they've proven,

37:49.220 --> 37:50.120
they're proof of concept

37:50.120 --> 37:51.420
that they do work.

37:51.840 --> 37:52.240
Obviously,

37:52.380 --> 37:52.800
iTunes,

37:52.980 --> 37:53.340
you know,

37:53.440 --> 37:54.080
jumped up in the

37:54.080 --> 37:54.840
first week and made

37:54.840 --> 37:55.600
millions of dollars,

37:55.700 --> 37:56.420
millions of downloads

37:56.420 --> 37:56.880
or whatever,

37:57.400 --> 37:57.840
immediately.

37:58.200 --> 37:59.000
People wanted it.

37:59.360 --> 38:00.040
People were willing

38:00.040 --> 38:00.540
to pay it.

38:00.620 --> 38:01.820
99 cents a song.

38:02.320 --> 38:03.340
You buy the one song

38:03.340 --> 38:03.980
off the album

38:03.980 --> 38:04.640
instead of paying

38:04.640 --> 38:06.380
20 bucks for an album

38:06.380 --> 38:07.040
that only has one

38:07.040 --> 38:07.820
good song on it.

38:08.120 --> 38:08.840
People thought that

38:08.840 --> 38:09.680
was a good compromise,

38:09.800 --> 38:10.360
a lot of them.

38:10.880 --> 38:11.280
To me,

38:11.340 --> 38:11.600
personally,

38:11.660 --> 38:12.280
I still think that's

38:12.280 --> 38:12.740
a little high.

38:12.820 --> 38:13.380
I'd rather see like

38:13.380 --> 38:14.400
50 cents a song or

38:14.400 --> 38:14.640
something.

38:14.760 --> 38:15.060
But hey,

38:15.760 --> 38:16.160
again,

38:16.220 --> 38:16.820
that's a personal

38:16.820 --> 38:17.220
opinion.

38:17.220 --> 38:17.940
so far,

38:18.040 --> 38:18.500
so they must be

38:18.500 --> 38:18.900
doing something

38:18.900 --> 38:19.180
right,

38:19.240 --> 38:19.480
you know?

38:19.880 --> 38:19.900
Yeah,

38:20.020 --> 38:20.480
absolutely.

38:21.240 --> 38:21.640
Absolutely.

38:21.860 --> 38:22.560
It hasn't hit my

38:22.560 --> 38:23.320
personal level yet,

38:23.360 --> 38:23.760
but a lot of

38:23.760 --> 38:24.360
people's it has,

38:24.420 --> 38:24.820
and that's

38:24.820 --> 38:26.000
fan-freaking-tastic.

38:26.500 --> 38:27.160
Another thing

38:27.160 --> 38:27.760
that's happened

38:27.760 --> 38:28.780
is,

38:29.040 --> 38:29.640
and I did,

38:29.740 --> 38:30.260
I talked about

38:30.260 --> 38:30.840
this in the show

38:30.840 --> 38:31.900
fairly recently,

38:32.000 --> 38:32.440
and that is I

38:32.440 --> 38:33.140
ordered a CD

38:33.140 --> 38:36.200
from a group

38:36.200 --> 38:36.840
online,

38:37.200 --> 38:39.260
Deltron 3030,

38:39.360 --> 38:39.760
something like

38:39.760 --> 38:40.000
that.

38:40.380 --> 38:40.580
Yeah,

38:40.640 --> 38:40.980
I know what you're

38:40.980 --> 38:41.240
talking about.

38:41.260 --> 38:42.440
And I could order

38:42.440 --> 38:43.280
that directly from

38:43.280 --> 38:43.560
them,

38:43.720 --> 38:43.900
which,

38:44.020 --> 38:44.140
oh,

38:44.220 --> 38:44.800
I'm glad I brought

38:44.800 --> 38:45.120
this up,

38:45.260 --> 38:45.400
actually.

38:45.460 --> 38:46.020
This is a negative.

38:46.020 --> 38:46.660
I haven't gotten

38:46.660 --> 38:47.420
that CD yet,

38:47.720 --> 38:48.120
and it's been

38:48.120 --> 38:48.740
like a month or

38:48.740 --> 38:49.000
more.

38:49.880 --> 38:50.280
But,

38:50.360 --> 38:51.100
I did have the

38:51.100 --> 38:51.720
option of buying

38:51.720 --> 38:52.620
it directly from

38:52.620 --> 38:52.980
them.

38:53.580 --> 38:53.840
You know,

38:53.900 --> 38:54.620
they can burn

38:54.620 --> 38:55.200
and make their

38:55.200 --> 38:55.980
own CDs and

38:55.980 --> 38:57.220
cut out the

38:57.220 --> 38:58.300
RAA and all

38:58.300 --> 38:58.920
the middlemen

38:58.920 --> 38:59.280
because,

38:59.380 --> 38:59.540
you know,

38:59.600 --> 39:00.140
they jack up

39:00.140 --> 39:00.840
the prices for

39:00.840 --> 39:02.020
distribution and

39:02.020 --> 39:02.640
advertising,

39:02.880 --> 39:03.900
and they charge

39:03.900 --> 39:04.420
these artists

39:04.420 --> 39:05.320
because in the

39:05.320 --> 39:05.860
past they had

39:05.860 --> 39:06.500
full control.

39:06.820 --> 39:07.280
The artists had

39:07.280 --> 39:08.000
no other options

39:08.000 --> 39:08.580
to get CDs

39:08.580 --> 39:09.400
burnt and mass

39:09.400 --> 39:09.840
produced.

39:10.620 --> 39:11.020
But,

39:11.120 --> 39:11.860
as hardware was

39:11.860 --> 39:12.580
developed and came

39:12.580 --> 39:12.780
up,

39:12.880 --> 39:13.680
they had alternatives

39:13.680 --> 39:14.220
and they had

39:14.220 --> 39:14.800
options,

39:15.300 --> 39:16.000
and that helped

39:16.000 --> 39:16.760
the industry,

39:16.880 --> 39:17.300
it helped the

39:17.300 --> 39:17.640
artists,

39:17.960 --> 39:18.380
it helped the

39:18.380 --> 39:18.840
consumers,

39:19.440 --> 39:20.160
but the RAA

39:20.160 --> 39:20.920
lost a little bit

39:20.920 --> 39:21.380
more control.

39:21.480 --> 39:21.920
And like I said,

39:21.980 --> 39:22.380
they didn't want

39:22.380 --> 39:23.020
to lose business

39:23.020 --> 39:23.700
to Blockbuster,

39:23.780 --> 39:24.100
they don't want

39:24.100 --> 39:24.600
to lose business

39:24.600 --> 39:25.240
to other hardware

39:25.240 --> 39:25.960
manufacturers,

39:26.260 --> 39:27.100
other distributors,

39:27.100 --> 39:29.520
consumers, but they

39:29.520 --> 39:30.120
don't care about

39:30.120 --> 39:30.780
what's best for the

39:30.780 --> 39:31.220
consumer.

39:31.620 --> 39:32.060
They don't care

39:32.060 --> 39:32.640
what's best for

39:32.640 --> 39:33.320
the economy or

39:33.320 --> 39:33.780
the American,

39:33.960 --> 39:34.160
yeah,

39:34.220 --> 39:34.580
the American

39:34.580 --> 39:35.060
economy.

39:35.640 --> 39:36.260
They want

39:36.260 --> 39:37.060
everything.

39:38.160 --> 39:38.860
So there are

39:38.860 --> 39:41.420
lots of ways to

39:41.420 --> 39:42.020
come up with a

39:42.020 --> 39:43.040
fair and balanced

39:43.040 --> 39:44.980
compromise with

39:44.980 --> 39:45.920
consumers.

39:46.680 --> 39:47.480
And make sure,

39:47.560 --> 39:48.080
still make sure

39:48.080 --> 39:48.460
that people,

39:48.960 --> 39:49.160
you know,

39:49.220 --> 39:49.640
artists,

39:50.320 --> 39:50.780
musicians,

39:51.020 --> 39:51.360
whatever,

39:51.580 --> 39:51.900
actors,

39:52.040 --> 39:52.580
everybody,

39:53.140 --> 39:53.800
get paid.

39:54.680 --> 39:54.900
You know?

39:55.320 --> 39:56.220
And that's just,

39:57.740 --> 39:58.720
it's too late.

39:59.140 --> 39:59.720
And until they

39:59.720 --> 40:00.720
stop suing everybody

40:00.720 --> 40:01.540
and recognize that

40:01.540 --> 40:02.040
it's too late,

40:02.240 --> 40:03.040
this is going to

40:03.040 --> 40:03.440
continue.

40:03.880 --> 40:04.460
And we have to

40:04.460 --> 40:05.160
keep bringing it up

40:05.160 --> 40:06.200
and telling people

40:06.200 --> 40:06.620
about it.

40:06.840 --> 40:08.140
And again,

40:08.360 --> 40:09.880
savethethe.org.

40:10.500 --> 40:11.280
And it's the

40:11.280 --> 40:12.060
Induce Act.

40:12.560 --> 40:13.300
And the other

40:13.300 --> 40:14.000
thing that's sleazy

40:14.000 --> 40:14.660
about this is they

40:14.660 --> 40:15.360
tried to slip this

40:15.360 --> 40:15.880
under the radar.

40:16.240 --> 40:16.980
They tried to pass

40:16.980 --> 40:17.680
this with a verbal

40:17.680 --> 40:18.540
vote real quick,

40:18.640 --> 40:19.300
slipped it through

40:19.300 --> 40:20.600
without any publicity.

40:21.620 --> 40:22.440
And that's just

40:22.440 --> 40:22.900
underhanded.

40:22.980 --> 40:23.440
They knew they

40:23.440 --> 40:23.740
were wrong.

40:23.800 --> 40:24.180
When you try to

40:24.180 --> 40:24.900
sneak something in

40:24.900 --> 40:25.360
like that,

40:26.020 --> 40:26.740
you know you're

40:26.740 --> 40:27.060
wrong.

40:28.240 --> 40:28.540
So,

40:29.260 --> 40:30.720
the EFF is trying

40:30.720 --> 40:31.360
to bring attention

40:31.360 --> 40:32.580
to this with that

40:32.580 --> 40:33.860
lawsuit to Apple

40:33.860 --> 40:34.540
or a demonstration

40:34.540 --> 40:35.080
lawsuit.

40:35.700 --> 40:36.500
And not only to Apple,

40:36.580 --> 40:37.120
they showed that

40:37.120 --> 40:38.320
CNET could get sued

40:38.320 --> 40:39.680
and Toshiba,

40:39.940 --> 40:40.520
and they made up

40:40.520 --> 40:40.940
a bunch of,

40:40.960 --> 40:41.620
just about everybody

40:41.620 --> 40:42.780
because it's so broad.

40:43.940 --> 40:44.340
So,

40:44.760 --> 40:45.940
get this to a vote.

40:46.720 --> 40:47.060
Let your

40:47.060 --> 40:47.940
congresspeople know.

40:48.020 --> 40:48.440
And if you go to

40:48.440 --> 40:49.000
those sites,

40:49.580 --> 40:50.460
you'll find ways

40:50.460 --> 40:51.240
that you can fax

40:51.240 --> 40:51.780
and you can send

40:51.780 --> 40:52.720
emails to these people.

40:52.820 --> 40:53.440
And I've done it.

40:53.440 --> 40:54.300
I sent mine.

40:56.220 --> 40:57.200
And let them know

40:57.200 --> 40:57.960
that it needs to be

40:57.960 --> 40:58.860
looked deeper into.

40:58.980 --> 41:00.320
Do not blindly pass

41:00.320 --> 41:01.360
another bill

41:01.360 --> 41:02.160
like they did

41:02.160 --> 41:03.000
the Patriot Act.

41:03.220 --> 41:03.500
You know,

41:03.600 --> 41:04.140
unanimously.

41:04.920 --> 41:05.500
Don't let it

41:05.500 --> 41:06.040
happen again.

41:06.740 --> 41:06.980
All right,

41:07.040 --> 41:07.580
I need a drink

41:07.580 --> 41:08.060
and I didn't bring

41:08.060 --> 41:08.660
a drink in here.

41:09.200 --> 41:09.360
Yeah,

41:09.380 --> 41:10.160
I got no drink either.

41:10.360 --> 41:10.600
Oh well,

41:10.700 --> 41:11.100
we're stuck.

41:12.100 --> 41:12.460
Man,

41:12.580 --> 41:12.840
I'm in,

41:12.960 --> 41:13.140
yeah.

41:13.320 --> 41:13.520
Well,

41:13.600 --> 41:14.040
I tell you what

41:14.040 --> 41:14.640
I'm going to do.

41:14.760 --> 41:14.960
Well,

41:15.000 --> 41:15.260
let's see.

41:15.320 --> 41:16.000
Let's move into

41:16.000 --> 41:16.700
the show and tell

41:16.700 --> 41:18.820
because I know

41:18.820 --> 41:19.360
you've got a lot

41:19.360 --> 41:19.920
of show and tell

41:19.920 --> 41:20.180
stuff.

41:20.260 --> 41:20.440
Let me,

41:20.620 --> 41:21.360
I'll give a couple

41:21.360 --> 41:22.020
quick things

41:22.020 --> 41:22.420
and then I'll

41:22.420 --> 41:23.080
turn it over to you

41:23.080 --> 41:23.540
and I'll try to

41:23.540 --> 41:24.160
catch my breath

41:24.160 --> 41:24.900
and lower my blood

41:24.900 --> 41:25.540
pressure.

41:25.540 --> 41:28.280
We had,

41:28.380 --> 41:29.420
I had anyway,

41:29.860 --> 41:31.120
a 2600 meeting

41:31.120 --> 41:32.000
last week,

41:32.720 --> 41:33.880
the August 2600

41:33.880 --> 41:34.220
meeting.

41:34.700 --> 41:35.720
So I went to that.

41:36.240 --> 41:36.960
I've been writing

41:36.960 --> 41:37.780
some new articles.

41:38.220 --> 41:38.900
I actually submitted

41:38.900 --> 41:39.560
a couple articles,

41:39.660 --> 41:40.240
2600.

41:40.380 --> 41:40.880
I've been working

41:40.880 --> 41:41.440
on some others

41:41.440 --> 41:41.880
that you and I

41:41.880 --> 41:42.400
have been actually

41:42.400 --> 41:43.160
talking about.

41:43.840 --> 41:44.700
Some fun stuff.

41:45.640 --> 41:46.800
I went to my 2600

41:46.800 --> 41:47.560
meeting two months

41:47.560 --> 41:48.280
in a row now.

41:48.840 --> 41:49.520
My cookie girl

41:49.520 --> 41:50.320
has not been there.

41:50.380 --> 41:50.660
I don't know

41:50.660 --> 41:51.100
what's up.

41:51.620 --> 41:52.400
I'm starting to get

41:52.400 --> 41:52.980
a little bit worried.

41:54.220 --> 41:55.320
I go in,

41:55.540 --> 41:56.160
I hook up with

41:56.160 --> 41:56.900
my cookie girl.

41:57.060 --> 41:58.180
I put the Mac down,

41:58.740 --> 41:59.500
hook up some free

41:59.500 --> 41:59.920
cookies.

42:00.360 --> 42:01.180
I haven't been able

42:01.180 --> 42:01.680
to get my free

42:01.680 --> 42:02.660
cookies in two months

42:02.660 --> 42:02.900
now.

42:03.020 --> 42:03.600
So today,

42:04.160 --> 42:05.320
so this past meeting

42:05.320 --> 42:05.820
I should say,

42:05.860 --> 42:06.420
last week,

42:06.880 --> 42:08.980
I had to go Mac

42:08.980 --> 42:09.700
on an old lady,

42:09.800 --> 42:10.040
dude,

42:10.120 --> 42:10.860
to get my free

42:10.860 --> 42:11.220
cookies.

42:13.100 --> 42:13.780
Does that make me

42:13.780 --> 42:14.260
a sellout?

42:14.820 --> 42:15.060
No,

42:15.140 --> 42:15.620
not at all.

42:15.860 --> 42:17.140
She could support

42:17.140 --> 42:17.700
you and you could

42:17.700 --> 42:18.380
sit around and hack

42:18.380 --> 42:18.680
all day.

42:18.720 --> 42:19.120
That's great.

42:19.360 --> 42:19.760
Then again,

42:19.780 --> 42:20.360
she's working at a

42:20.360 --> 42:20.800
cookie shop.

42:20.980 --> 42:21.180
Maybe she doesn't

42:21.180 --> 42:21.580
have that much.

42:21.760 --> 42:21.960
Yeah,

42:22.060 --> 42:24.320
as long as she keeps

42:24.320 --> 42:25.080
me in free cookies.

42:26.160 --> 42:26.560
That's true.

42:26.700 --> 42:26.840
Yeah,

42:26.920 --> 42:27.960
I told her I loved

42:27.960 --> 42:28.080
her,

42:28.160 --> 42:28.280
man.

42:28.340 --> 42:28.740
I don't know,

42:28.780 --> 42:29.260
I feel kind of

42:29.260 --> 42:29.540
wrong.

42:29.800 --> 42:30.280
I feel kind of

42:30.280 --> 42:30.480
dirty.

42:30.540 --> 42:30.980
I took a shower

42:30.980 --> 42:31.600
when I came home.

42:32.700 --> 42:33.240
She's dreaming

42:33.240 --> 42:33.940
about you right

42:33.940 --> 42:34.260
now.

42:35.360 --> 42:36.280
She loves me.

42:36.280 --> 42:37.200
I came home and

42:37.200 --> 42:38.120
took a shower and

42:38.120 --> 42:39.540
then I ate the

42:39.540 --> 42:40.000
other half of my

42:40.000 --> 42:40.220
cookie,

42:40.320 --> 42:40.620
but neither

42:40.620 --> 42:40.980
anyway.

42:43.340 --> 42:44.180
And ZeroDB

42:44.180 --> 42:44.920
actually gave a

42:44.920 --> 42:45.760
presentation at our

42:45.760 --> 42:46.400
meeting on Plan

42:46.400 --> 42:46.800
9,

42:46.940 --> 42:47.960
which he's talked

42:47.960 --> 42:48.440
about on the show

42:48.440 --> 42:49.020
a few times.

42:49.220 --> 42:50.560
And he put Plan

42:50.560 --> 42:51.760
9 on his IBM

42:51.760 --> 42:52.720
ThinkPad and gave

42:52.720 --> 42:53.820
a little hands-on

42:53.820 --> 42:54.400
demonstration,

42:54.600 --> 42:55.220
which went really

42:55.220 --> 42:55.480
well.

42:55.600 --> 42:56.120
A lot of people

42:56.120 --> 42:56.660
were interested in

42:56.660 --> 42:56.880
that.

42:57.140 --> 42:58.180
And that was

42:58.180 --> 42:58.600
really cool.

42:58.680 --> 42:59.300
I tried to film

42:59.300 --> 42:59.900
some of it and

42:59.900 --> 43:00.660
then the security

43:00.660 --> 43:01.460
card came over and

43:01.460 --> 43:02.460
told me that I

43:02.460 --> 43:03.220
wasn't allowed to

43:03.220 --> 43:04.640
film inside of the

43:04.640 --> 43:05.900
commerce area known as

43:05.900 --> 43:06.320
the mall.

43:06.900 --> 43:07.280
Now wait,

43:07.360 --> 43:08.540
can you back this

43:08.540 --> 43:08.700
up?

43:08.740 --> 43:09.200
Because I've heard

43:09.200 --> 43:09.920
many people say

43:09.920 --> 43:11.260
this about malls as

43:11.260 --> 43:11.500
well.

43:11.900 --> 43:13.160
What's the rationale?

43:13.460 --> 43:14.260
Is it just that it's

43:14.260 --> 43:15.000
their property and

43:15.000 --> 43:15.540
they don't want you

43:15.540 --> 43:16.240
to film or is there

43:16.240 --> 43:16.900
something more that

43:16.900 --> 43:17.300
I'm missing?

43:17.480 --> 43:17.980
I don't know.

43:18.040 --> 43:18.480
He didn't give me

43:18.480 --> 43:18.960
an explanation.

43:19.160 --> 43:19.740
He just said you're

43:19.740 --> 43:20.360
not allowed to film

43:20.360 --> 43:20.800
in the mall.

43:22.300 --> 43:22.740
I didn't.

43:22.840 --> 43:23.440
I'm like, oh,

43:23.500 --> 43:23.700
really?

43:23.780 --> 43:24.380
What's that about?

43:24.500 --> 43:25.160
He's like, well,

43:25.180 --> 43:25.740
it's just a rule.

43:25.800 --> 43:26.180
They're not allowed

43:26.180 --> 43:26.940
to film inside of

43:26.940 --> 43:27.420
the mall area.

43:27.480 --> 43:28.200
You can go outside

43:28.200 --> 43:29.260
of the mall, but

43:29.260 --> 43:29.760
you can't film

43:29.760 --> 43:30.360
inside of the

43:30.360 --> 43:30.640
building.

43:31.640 --> 43:32.200
So I didn't want

43:32.200 --> 43:33.000
I'm like, oh,

43:33.100 --> 43:33.500
okay, I just

43:33.500 --> 43:33.940
didn't know.

43:34.040 --> 43:34.360
I didn't think

43:34.360 --> 43:34.760
it was that big

43:34.760 --> 43:35.100
of a deal.

43:35.340 --> 43:36.860
So I put it up

43:36.860 --> 43:38.300
and he kept on

43:38.300 --> 43:38.620
presenting.

43:38.800 --> 43:39.860
But yeah, I don't

43:39.860 --> 43:40.200
know what the

43:40.200 --> 43:40.860
rationale behind

43:40.860 --> 43:41.300
that is.

43:43.600 --> 43:44.240
Now I know

43:44.240 --> 43:44.700
they've also

43:44.700 --> 43:45.540
hassled us in the

43:45.540 --> 43:46.820
past about

43:46.820 --> 43:47.440
plugging in our

43:47.440 --> 43:49.800
laptops, which

43:49.800 --> 43:50.700
the first time

43:50.700 --> 43:51.160
they did it,

43:51.280 --> 43:52.140
the guy gave us

43:52.140 --> 43:52.820
some crap about

43:52.820 --> 43:53.500
using their

43:53.500 --> 43:54.000
electricity.

43:55.000 --> 43:55.480
And come on,

43:55.540 --> 43:56.280
what minuscule

43:56.280 --> 43:56.640
amount of

43:56.640 --> 43:57.320
electricity are we

43:57.320 --> 43:57.600
using?

43:58.680 --> 43:59.460
But the other

43:59.460 --> 44:01.280
time, one of the

44:01.280 --> 44:02.000
other security guards

44:02.000 --> 44:02.520
who was actually

44:02.520 --> 44:03.300
respectful came

44:03.300 --> 44:03.820
by and his

44:03.820 --> 44:04.600
explanation was

44:04.600 --> 44:05.140
that the cords

44:05.140 --> 44:05.860
were going across

44:05.860 --> 44:06.660
between tables

44:06.660 --> 44:07.380
and they didn't

44:07.380 --> 44:07.980
want somebody to

44:07.980 --> 44:08.500
trip and get

44:08.500 --> 44:08.820
sued.

44:09.720 --> 44:10.540
So that, I give

44:10.540 --> 44:11.040
that a valid

44:11.040 --> 44:11.360
reason.

44:11.720 --> 44:12.440
So that I'm

44:12.440 --> 44:12.780
cool with.

44:12.820 --> 44:13.320
So we still

44:13.320 --> 44:13.980
plug in all the

44:13.980 --> 44:14.500
time now.

44:14.760 --> 44:15.240
We just make

44:15.240 --> 44:15.700
sure we move

44:15.700 --> 44:16.300
the table right

44:16.300 --> 44:16.960
above it so that

44:16.960 --> 44:17.520
the cord runs

44:17.520 --> 44:18.080
under the table

44:18.080 --> 44:18.640
and plugs in.

44:18.700 --> 44:19.040
And they haven't

44:19.040 --> 44:19.520
given us any

44:19.520 --> 44:20.140
hassle about that

44:20.140 --> 44:20.580
in a while.

44:21.140 --> 44:21.400
Well, that's

44:21.400 --> 44:21.580
cool.

44:21.840 --> 44:22.020
Yeah.

44:23.120 --> 44:23.880
So yeah, Plan

44:23.880 --> 44:24.540
9 presentation

44:24.540 --> 44:25.280
went really well.

44:25.340 --> 44:25.680
I thought it was

44:25.680 --> 44:26.160
pretty cool.

44:26.360 --> 44:27.180
And he had given

44:27.180 --> 44:28.620
a similar, well,

44:28.700 --> 44:29.280
he didn't give a

44:29.280 --> 44:30.060
demonstration at the

44:30.060 --> 44:30.600
DEF CON meeting

44:30.600 --> 44:31.040
but he brought

44:31.040 --> 44:31.580
it with him

44:31.580 --> 44:32.100
and was setting

44:32.100 --> 44:33.240
it up at the

44:33.240 --> 44:33.840
DEF CON and was

44:33.840 --> 44:34.300
kind of showing

44:34.300 --> 44:34.940
me some things

44:34.940 --> 44:35.420
there.

44:36.200 --> 44:36.920
But he went into

44:36.920 --> 44:37.400
a little bit more

44:37.400 --> 44:38.420
detail at the

44:38.420 --> 44:39.640
meeting, the 2600

44:39.640 --> 44:40.220
meeting this time

44:40.220 --> 44:40.680
which was really

44:40.680 --> 44:40.940
cool.

44:41.660 --> 44:42.440
And we had a

44:42.440 --> 44:43.180
couple new

44:43.180 --> 44:43.880
members or at

44:43.880 --> 44:44.920
least, let's see,

44:45.020 --> 44:45.880
at least one new

44:45.880 --> 44:46.620
member and then

44:46.620 --> 44:48.120
someone who I'd

44:48.120 --> 44:48.840
never seen before.

44:48.920 --> 44:49.500
He said he'd come

44:49.500 --> 44:50.460
years ago and had

44:50.460 --> 44:52.200
returned so he's

44:52.200 --> 44:53.000
new to me as far

44:53.000 --> 44:53.460
as I know.

44:53.820 --> 44:55.060
So had a couple

44:55.060 --> 44:55.920
new people so it's

44:55.920 --> 44:56.480
still growing.

44:56.620 --> 44:57.240
There was probably,

44:58.680 --> 45:00.040
gosh, I didn't

45:00.060 --> 45:00.960
count again but I

45:00.960 --> 45:01.560
would say around a

45:01.560 --> 45:02.360
dozen people which

45:02.360 --> 45:02.960
is pretty cool.

45:04.360 --> 45:05.620
So it was a good

45:05.620 --> 45:05.940
meeting.

45:06.420 --> 45:07.260
I loved getting out

45:07.260 --> 45:08.360
and talking tech

45:08.360 --> 45:09.040
with people so it

45:09.040 --> 45:09.560
went pretty well.

45:10.980 --> 45:12.340
And let's see,

45:13.720 --> 45:14.720
oh, the DDP

45:14.720 --> 45:16.040
Hack Radio coming

45:16.040 --> 45:16.960
along and getting

45:16.960 --> 45:18.120
very close to done.

45:18.800 --> 45:20.220
So we opened up

45:20.220 --> 45:20.880
in the forums for

45:20.880 --> 45:21.920
people to send in

45:21.920 --> 45:22.800
their show submissions,

45:22.980 --> 45:23.560
show ideas.

45:24.680 --> 45:25.840
The information that

45:25.840 --> 45:26.420
we need is all

45:26.420 --> 45:28.100
outlined in the

45:28.100 --> 45:29.300
Hacker Radio TV

45:29.300 --> 45:30.240
Forum at

45:30.240 --> 45:31.100
BinRev.com,

45:31.180 --> 45:32.240
forums.BinRev.com.

45:32.320 --> 45:33.000
So check that out.

45:33.380 --> 45:34.100
Contact us with

45:34.100 --> 45:34.700
your ideas.

45:36.180 --> 45:37.060
And you and I

45:37.060 --> 45:37.900
actually have got a

45:37.900 --> 45:38.700
couple ideas.

45:39.080 --> 45:40.180
One specifically that

45:40.180 --> 45:40.900
I think is going to be

45:40.900 --> 45:42.420
enormously successful.

45:43.080 --> 45:44.280
Yeah, well, I think

45:44.280 --> 45:45.280
that should stay top

45:45.280 --> 45:45.880
secret for a little

45:45.880 --> 45:46.140
while.

45:46.300 --> 45:46.680
But I think it's

45:46.680 --> 45:47.080
going to be a little

45:47.080 --> 45:47.300
bit.

45:47.300 --> 45:48.220
Yeah, so there will

45:48.220 --> 45:49.420
be some other surprises

45:49.420 --> 45:50.300
when we launch Hack

45:50.300 --> 45:51.660
Radio, I think, I hope.

45:52.980 --> 45:53.900
Yeah, I haven't even

45:53.900 --> 45:54.300
asked about Hack

45:54.300 --> 45:54.860
Radio, by the way.

45:54.900 --> 45:55.500
I've been waiting for a

45:55.500 --> 45:55.720
while.

45:55.720 --> 45:56.840
I'm not trying to

45:56.840 --> 45:57.960
say, like, there's

45:57.960 --> 45:58.540
anything wrong with

45:58.540 --> 45:59.460
how long it took, but

45:59.460 --> 46:02.080
I am just all about

46:02.080 --> 46:02.920
this streaming server

46:02.920 --> 46:03.560
being set up.

46:03.640 --> 46:04.380
Yeah, it's going to.

46:04.440 --> 46:05.300
I am, too.

46:05.480 --> 46:06.380
It's really going to be

46:06.380 --> 46:08.240
cool because for a

46:08.240 --> 46:10.080
change, I'm going to

46:10.080 --> 46:11.240
be able to tune in to

46:11.240 --> 46:12.600
a station, to a

46:12.600 --> 46:14.140
streaming station, and

46:14.140 --> 46:15.440
get hacking content

46:15.440 --> 46:17.060
all the time.

46:17.840 --> 46:18.120
Yep.

46:19.080 --> 46:20.160
That's cool.

46:20.720 --> 46:21.760
And it's going to be

46:21.760 --> 46:22.740
one centralized place

46:22.740 --> 46:23.400
that people will

46:23.400 --> 46:24.640
always know that they

46:24.640 --> 46:25.340
can come to.

46:26.160 --> 46:26.800
And at least, you

46:26.800 --> 46:27.560
know what, it'll be

46:27.560 --> 46:28.340
a central, if nothing

46:28.340 --> 46:28.980
else, a launching

46:28.980 --> 46:29.840
off point to link to

46:29.840 --> 46:30.680
everyone's individual

46:30.680 --> 46:31.080
sites.

46:31.500 --> 46:31.720
Right.

46:31.880 --> 46:32.740
You know, come to the

46:32.740 --> 46:33.460
station and then say,

46:33.520 --> 46:34.460
oh, I missed the last

46:34.460 --> 46:36.500
episode of Uberlito, so

46:36.500 --> 46:37.500
link over to Uberlito

46:37.500 --> 46:38.520
and download the old

46:38.520 --> 46:39.100
MP3s.

46:39.140 --> 46:39.940
Link over to Default

46:39.940 --> 46:40.200
Radio.

46:40.340 --> 46:40.960
Link over to Bin

46:40.960 --> 46:41.380
Rev Radio.

46:41.500 --> 46:42.240
Link over to whatever,

46:42.800 --> 46:43.280
you know, the

46:43.280 --> 46:43.740
Droop Show.

46:43.860 --> 46:44.320
Link over to

46:44.320 --> 46:45.060
everybody and get it.

46:45.100 --> 46:46.080
If nothing else, that's

46:46.080 --> 46:47.000
a cool feature of it.

46:47.300 --> 46:48.120
Uh, uh, uh, uh, not

46:48.120 --> 46:48.660
the Droop Show.

46:49.100 --> 46:50.020
Oh, I'm sorry, not the

46:50.020 --> 46:50.460
Droop Show.

46:50.880 --> 46:51.220
The Infonomicon.

46:51.220 --> 46:52.300
The Infonomicon.

46:52.460 --> 46:53.140
The Datonomicon?

46:53.340 --> 46:54.040
The Infonomicon?

46:54.240 --> 46:54.340
Yeah.

46:54.660 --> 46:55.380
Infonomicon, definitely.

46:55.660 --> 46:56.960
Yeah, I actually haven't

46:56.960 --> 46:57.940
listened to the last

46:57.940 --> 46:58.660
version of that.

46:58.800 --> 47:00.260
I guess they called me.

47:00.980 --> 47:01.840
I was asleep.

47:02.840 --> 47:03.980
But I think they called

47:03.980 --> 47:05.180
me, and I wish I could

47:05.180 --> 47:05.900
have answered the phone,

47:05.980 --> 47:06.700
so I haven't heard the

47:06.700 --> 47:08.880
episode yet, but, um, I

47:08.880 --> 47:09.500
have to hear what they

47:09.500 --> 47:10.040
had to say.

47:10.160 --> 47:12.600
I hope, um, well, yeah,

47:12.640 --> 47:13.280
I'll listen to the

47:13.280 --> 47:14.040
episode and see what

47:14.040 --> 47:14.540
happened there.

47:14.860 --> 47:15.520
Yeah, I haven't listened

47:15.520 --> 47:16.240
to that one yet either,

47:16.320 --> 47:17.420
but I gotta say, um,

47:18.000 --> 47:19.160
preemptively, shouts to

47:19.160 --> 47:19.940
Obfuscated Man.

47:20.000 --> 47:21.520
That dude is hilarious.

47:21.680 --> 47:23.400
At least, he's all about

47:23.400 --> 47:24.540
my sense of humor, man.

47:24.840 --> 47:25.580
My sense of humor.

47:25.680 --> 47:26.600
Well, the one that I,

47:26.660 --> 47:26.900
he...

47:26.900 --> 47:27.980
He's sarcastic and, uh,

47:27.980 --> 47:28.460
and rough.

47:28.600 --> 47:30.040
Yeah, I absolutely, oh,

47:30.080 --> 47:30.860
you like it rough, do you?

47:30.860 --> 47:32.260
Oh, I love it rough,

47:32.340 --> 47:32.480
baby.

47:32.660 --> 47:33.560
Um, he did have me

47:33.560 --> 47:33.920
laughing.

47:34.040 --> 47:34.640
He made, what, there

47:34.640 --> 47:35.860
was a joke about, um,

47:36.840 --> 47:37.980
what was it about, uh,

47:38.200 --> 47:39.200
disease tag?

47:40.000 --> 47:41.560
Oh, dude, I was crying.

47:41.900 --> 47:42.420
What are you saying?

47:42.440 --> 47:43.480
He's playing disease tag

47:43.480 --> 47:44.080
with his girlfriend?

47:44.820 --> 47:46.020
I was, I almost pissed

47:46.020 --> 47:46.460
on myself.

47:47.340 --> 47:47.500
Yeah.

47:48.020 --> 47:48.660
All right, who am I

47:48.660 --> 47:48.820
kidding?

47:48.860 --> 47:49.800
I did piss on myself.

47:50.560 --> 47:51.220
Yeah, well, you know,

47:51.260 --> 47:51.820
nothing wrong with that.

47:51.980 --> 47:52.180
Yeah.

47:53.260 --> 47:54.340
So, anyway, that's it

47:54.340 --> 47:54.800
for me.

47:54.920 --> 47:56.080
Now, you, I'm going to

47:56.080 --> 47:56.960
take a breath while you

47:56.960 --> 47:57.620
talk, because I know

47:57.620 --> 47:58.560
you've got, you've got

47:58.560 --> 47:59.420
some stuff to talk

47:59.420 --> 48:00.600
about Bell's Mind, the

48:00.600 --> 48:01.400
growth of Bell's Mind

48:01.400 --> 48:01.940
that's going on.

48:01.980 --> 48:02.620
You've added some new

48:02.620 --> 48:04.180
features to that, um,

48:04.180 --> 48:05.020
some new stuff you put

48:05.020 --> 48:07.040
on the PBX, and if I'm

48:07.040 --> 48:08.900
not mistaken, I think

48:08.900 --> 48:09.860
you've been putting a lot

48:09.860 --> 48:10.820
of time into practicing

48:10.820 --> 48:11.720
the Albatross.

48:11.820 --> 48:12.760
Am I correct on that?

48:12.760 --> 48:14.880
Oh, boy.

48:15.520 --> 48:18.440
Um, I learned about the

48:18.440 --> 48:19.500
Albatross from Stank.

48:19.580 --> 48:20.580
He demonstrated it to me

48:20.580 --> 48:20.980
in Hope.

48:22.720 --> 48:23.900
You were pretty good,

48:23.940 --> 48:24.360
by the way.

48:24.960 --> 48:25.740
Yeah, well, you know,

48:26.180 --> 48:28.000
I was, I was only third

48:28.000 --> 48:30.120
string, but, uh, I helped

48:30.120 --> 48:30.380
out.

48:30.560 --> 48:31.600
I don't even know what

48:31.600 --> 48:33.580
that means, but, oh,

48:33.660 --> 48:34.520
man, you got me crying

48:34.520 --> 48:35.080
again, stop.

48:35.200 --> 48:35.680
Oh, man.

48:35.820 --> 48:37.700
So, um, oh, God, just

48:37.700 --> 48:38.780
don't even bother to look

48:38.780 --> 48:39.400
up the Albatross.

48:39.740 --> 48:40.140
Terrible.

48:40.360 --> 48:41.340
Kids, uh, Stank is

48:41.340 --> 48:42.000
trying to pollute your

48:42.000 --> 48:42.340
mind.

48:42.800 --> 48:43.900
Parents, run away from

48:43.900 --> 48:44.760
this show as fast as

48:44.760 --> 48:44.780
as possible.

48:45.480 --> 48:46.580
No, I'll tell them that

48:46.580 --> 48:48.000
I purposely made that

48:48.000 --> 48:49.560
mean, very mean joke to

48:49.560 --> 48:50.420
not theory here, because

48:50.420 --> 48:52.540
I found that on, uh, what

48:52.540 --> 48:53.620
is it, Urban Dictionary.

48:55.280 --> 48:55.880
UrbanDictionary.com.

48:55.920 --> 48:56.520
Actually, it was, you

48:56.520 --> 48:56.940
know what it was?

48:56.960 --> 48:57.520
It was marked for

48:57.520 --> 48:58.080
deletion.

48:58.340 --> 48:59.500
So it's probably gone.

48:59.580 --> 49:00.280
Nobody will know.

49:00.400 --> 49:00.900
Somebody's going to have

49:00.900 --> 49:02.020
to do some deep research.

49:03.160 --> 49:03.640
I thought you said

49:03.640 --> 49:04.520
that was on your, uh,

49:04.520 --> 49:05.840
M4M trucker site that

49:05.840 --> 49:06.460
you hang out at.

49:07.600 --> 49:07.960
Um.

49:09.300 --> 49:10.120
Oh, should I not

49:10.120 --> 49:10.560
have mentioned that

49:10.560 --> 49:10.860
on the air?

49:10.920 --> 49:11.540
Yeah, I mean,

49:11.620 --> 49:12.500
bookmarks are off

49:12.500 --> 49:13.120
limits, man.

49:14.620 --> 49:15.620
Stuff in the favorites

49:15.620 --> 49:16.840
list, that's not for

49:16.840 --> 49:17.620
public consumption.

49:17.880 --> 49:18.740
Sorry, well, we'll

49:18.740 --> 49:19.380
edit that out.

49:19.460 --> 49:20.180
All right, go ahead.

49:21.380 --> 49:21.700
Anyway.

49:21.920 --> 49:22.440
Turn it out, it's

49:22.440 --> 49:22.840
fair play.

49:23.540 --> 49:25.380
So, uh, let's get

49:25.380 --> 49:26.180
back on track a little

49:26.180 --> 49:26.200
bit.

49:26.200 --> 49:26.780
All right, Bell's

49:26.780 --> 49:27.020
Mine.

49:27.380 --> 49:28.140
Bell's Mine, yes.

49:28.280 --> 49:29.260
Uh, that's the website

49:29.260 --> 49:30.020
that I run, I almost

49:30.020 --> 49:30.280
forgot.

49:30.800 --> 49:32.840
Um, yeah, I've added a

49:32.840 --> 49:33.980
couple new features, uh,

49:33.980 --> 49:34.380
they're not all

49:34.380 --> 49:34.920
complete yet.

49:35.020 --> 49:35.460
People have been

49:35.460 --> 49:36.840
asking for, uh, for

49:36.840 --> 49:38.240
ways to search through

49:38.240 --> 49:38.620
the site.

49:38.620 --> 49:39.520
The search code is

49:39.520 --> 49:40.120
getting there.

49:40.180 --> 49:41.380
It's not done yet, um,

49:41.560 --> 49:42.380
but it's getting there.

49:42.420 --> 49:43.540
But now, um, now you

49:43.540 --> 49:44.340
can see what numbers,

49:44.420 --> 49:44.880
like, a particular

49:44.880 --> 49:45.720
person has submitted.

49:46.260 --> 49:47.000
Uh, you can just click

49:47.000 --> 49:47.800
on their name in that,

49:47.900 --> 49:49.380
in that top, uh, in the

49:49.380 --> 49:50.340
top numbers list, and,

49:50.420 --> 49:51.060
uh, it'll come up with

49:51.060 --> 49:52.660
a huge list of numbers

49:52.660 --> 49:53.280
that some of these guys

49:53.280 --> 49:53.640
have scanned.

49:53.720 --> 49:54.880
Let me tell you, right

49:54.880 --> 49:56.160
now, Bell's Mine has

49:56.160 --> 49:59.040
13,413 numbers in it.

49:59.300 --> 50:00.100
Uh, we haven't been up

50:00.100 --> 50:01.120
that long, and some of

50:01.120 --> 50:01.940
these guys, man, they

50:01.940 --> 50:03.380
are just banging out

50:03.380 --> 50:04.360
stuff like crazy.

50:04.360 --> 50:06.520
Selton X, Gray Area,

50:06.660 --> 50:07.280
I hope that's the way

50:07.280 --> 50:07.920
his name is pronounced,

50:08.040 --> 50:09.400
Selton X, Selton X,

50:10.200 --> 50:12.700
him, or, or her, uh,

50:12.740 --> 50:14.020
and Gray Area, which I

50:14.020 --> 50:15.120
met in, uh, in Vegas.

50:15.240 --> 50:15.960
Gray Area is awesome.

50:16.160 --> 50:17.640
And Test Set, they have

50:17.640 --> 50:19.560
submitted, uh, well over

50:19.560 --> 50:20.540
1,000 numbers each.

50:20.680 --> 50:21.440
Selton X is actually

50:21.440 --> 50:22.600
over 2,000 numbers.

50:22.700 --> 50:23.100
Damn!

50:23.600 --> 50:24.320
Those guys are really

50:24.320 --> 50:26.020
making, making my job

50:26.020 --> 50:26.540
pretty easy.

50:26.920 --> 50:27.780
Um, they're power

50:27.780 --> 50:28.580
washing the numbers.

50:28.960 --> 50:29.800
They are really, they're

50:29.800 --> 50:30.840
fucking rinsing out the

50:30.840 --> 50:31.460
goddamn phones.

50:31.640 --> 50:32.600
No joke, man.

50:32.600 --> 50:35.560
Um, so let me think.

50:35.680 --> 50:36.440
Uh, a couple things

50:36.440 --> 50:37.400
were suggested to me.

50:37.480 --> 50:39.300
I think Ref, that's, uh,

50:39.380 --> 50:41.240
R, capital E, P, H, I

50:41.240 --> 50:42.020
think he was the one

50:42.020 --> 50:42.780
who suggested that I

50:42.780 --> 50:43.520
should start a forum.

50:44.000 --> 50:45.620
Now, don't freak out.

50:45.720 --> 50:46.880
This forum is not, it's

50:46.880 --> 50:47.900
not going to be to, to

50:47.900 --> 50:48.500
discuss anything.

50:48.660 --> 50:49.740
It's only going to be

50:49.740 --> 50:50.660
to discuss freaking,

50:50.900 --> 50:52.320
and specifically, issues

50:52.320 --> 50:53.000
with Bell's Mind,

50:53.120 --> 50:53.960
submission issues, you

50:53.960 --> 50:54.580
know, bug reports,

50:54.680 --> 50:55.260
feature requests.

50:55.800 --> 50:56.720
Uh, we're not trying to,

50:56.860 --> 50:57.320
we're not trying to

50:57.320 --> 50:58.280
replace your forums or

50:58.280 --> 50:58.960
any kind of crap like

50:58.960 --> 50:59.180
that.

50:59.260 --> 51:00.000
I have no interest in

51:00.000 --> 51:00.580
all that kind of

51:00.580 --> 51:00.780
maintenance.

51:01.000 --> 51:01.880
Yeah, dude, I, I, I

51:01.880 --> 51:02.520
mean, if you take away

51:02.520 --> 51:03.300
my forums, I've got

51:03.300 --> 51:03.620
nothing.

51:04.760 --> 51:05.860
No, I just, I just want

51:05.860 --> 51:06.340
to give everybody a

51:06.340 --> 51:07.000
heads up that when we

51:07.000 --> 51:08.080
have forums, they're

51:08.080 --> 51:09.000
going to be specifically

51:09.000 --> 51:10.380
for the stuff on Bell's

51:10.380 --> 51:11.420
Mind and absolutely

51:11.420 --> 51:12.100
nothing else.

51:12.240 --> 51:14.080
So, so, DDP Bell's

51:14.080 --> 51:15.140
Mind, is that what, uh?

51:15.380 --> 51:16.100
Oh, Jesus.

51:18.720 --> 51:19.720
DDP forums already have

51:19.720 --> 51:20.720
so many users that there's

51:20.720 --> 51:21.620
no, no point in trying

51:21.620 --> 51:22.120
to build a little

51:22.120 --> 51:22.860
experience like that.

51:22.860 --> 51:23.780
I, I, I'd much rather

51:23.780 --> 51:24.760
hang out there and talk

51:24.760 --> 51:26.120
about, you know, coding

51:26.120 --> 51:27.040
and stuff like that than

51:27.040 --> 51:27.860
do it on my own

51:27.860 --> 51:28.480
personal site.

51:28.700 --> 51:30.960
So, so, aside from

51:30.960 --> 51:31.720
forums, I've been

51:31.720 --> 51:32.320
looking for forum

51:32.320 --> 51:33.500
software and pretty much

51:33.500 --> 51:34.480
in my mind, every piece

51:34.480 --> 51:35.540
of forum software sucks.

51:36.120 --> 51:37.680
Um, because most of

51:37.680 --> 51:38.940
them use MySQL instead

51:38.940 --> 51:39.420
of Postgres.

51:39.960 --> 51:40.820
And, uh...

51:40.820 --> 51:42.640
I thought, actually, I

51:42.640 --> 51:43.660
hate to pimp the one

51:43.660 --> 51:44.860
that we use, but I

51:44.860 --> 51:46.240
thought Envision was,

51:46.960 --> 51:47.940
I thought with them, one

51:47.940 --> 51:48.440
of the more recent

51:48.440 --> 51:49.280
versions, they offered

51:49.280 --> 51:51.560
one for both MySQL and

51:51.560 --> 51:53.140
Postgres, but I wouldn't

51:53.140 --> 51:54.100
swear to that.

51:54.460 --> 51:56.080
Um, I actually have a,

51:56.120 --> 51:57.860
uh, uh, another

51:57.860 --> 51:59.060
objection to Envision.

51:59.180 --> 52:00.140
The last version I saw

52:00.140 --> 52:01.100
had a pretty serious,

52:01.200 --> 52:02.380
uh, pretty serious

52:02.380 --> 52:03.360
vulnerability that I,

52:03.480 --> 52:04.260
that I came up with.

52:04.320 --> 52:05.540
It's very, very simple,

52:05.740 --> 52:06.960
but, um, I was gonna

52:06.960 --> 52:07.680
write an article about

52:07.680 --> 52:07.780
it.

52:07.800 --> 52:08.540
Maybe I still will.

52:09.680 --> 52:10.720
Well, there was one,

52:10.780 --> 52:11.620
actually, we have not

52:11.620 --> 52:12.760
upgraded because I know

52:12.760 --> 52:13.420
there's a vulnerability

52:13.420 --> 52:14.700
in the later version

52:14.700 --> 52:15.920
than the one that we

52:15.920 --> 52:16.860
have as well.

52:17.440 --> 52:17.840
Yeah.

52:17.940 --> 52:18.540
So...

52:18.540 --> 52:19.820
Yeah, this has, this

52:19.820 --> 52:20.740
particular bug that I'm

52:20.740 --> 52:21.540
talking about has nothing

52:21.540 --> 52:22.660
to do with SQL injection

52:22.660 --> 52:23.360
because that's, that's

52:23.360 --> 52:24.100
what I've seen most of

52:24.100 --> 52:24.840
the Envision bugs are

52:24.840 --> 52:25.780
SQL type stuff.

52:25.880 --> 52:26.160
Right.

52:26.340 --> 52:27.660
Um, you know, nothing

52:27.660 --> 52:28.520
to do with, like,

52:28.660 --> 52:29.940
cookies or any of the

52:29.940 --> 52:30.720
kind of junk like that.

52:30.760 --> 52:31.520
It's, it's kind of like

52:31.520 --> 52:32.840
a different class of, uh...

52:32.840 --> 52:33.840
Cross-site scripting?

52:34.120 --> 52:34.500
Of X.

52:34.580 --> 52:35.420
No, it's not cross-site,

52:35.420 --> 52:36.260
it's cross-site scripting

52:36.260 --> 52:36.460
either.

52:36.600 --> 52:37.260
None of that stuff.

52:37.400 --> 52:38.060
It's, it's kind of,

52:38.060 --> 52:38.620
kind of different.

52:38.740 --> 52:39.480
It's hard to explain.

52:39.780 --> 52:40.700
Um, you know what?

52:40.820 --> 52:41.800
I'll make a promise that

52:41.800 --> 52:43.080
for the next issue of

52:43.080 --> 52:44.080
BinRev, I will have an

52:44.080 --> 52:44.780
article about it.

52:44.940 --> 52:45.220
What?

52:46.320 --> 52:47.980
So, what is it,

52:48.020 --> 52:48.880
2.2, I guess?

52:49.000 --> 52:49.160
Yeah.

52:51.540 --> 52:53.740
Okay, cool, cool.

52:54.280 --> 52:54.400
Um...

52:54.400 --> 52:55.440
Actually, I gotta say,

52:55.500 --> 52:56.140
since you brought it up,

52:56.200 --> 52:57.920
we are, I've gotten some

52:57.920 --> 52:58.740
pretty good article

52:58.740 --> 52:59.160
submissions.

52:59.320 --> 53:00.180
We actually have got a

53:00.180 --> 53:01.020
good head start on this

53:01.020 --> 53:02.100
one for a change, so

53:02.100 --> 53:03.140
that, that's a very good

53:03.140 --> 53:04.380
place to be in instead of

53:04.380 --> 53:05.780
scrambling at the last

53:05.780 --> 53:05.980
minute.

53:06.120 --> 53:07.340
So, so far, we started

53:07.340 --> 53:08.280
off good, but that

53:08.280 --> 53:09.720
doesn't mean for people

53:09.720 --> 53:10.880
to stop sending stuff in.

53:10.940 --> 53:11.660
We still need more.

53:12.300 --> 53:12.680
Right.

53:13.300 --> 53:14.340
Yep, always can use

53:14.340 --> 53:14.620
more.

53:14.800 --> 53:15.000
Yep.

53:16.060 --> 53:17.920
Um, so where was I?

53:18.000 --> 53:18.700
Oh, okay, forum

53:18.700 --> 53:19.140
software.

53:19.520 --> 53:20.200
Looking for forum

53:20.200 --> 53:21.400
software, but it's,

53:21.400 --> 53:22.100
it's hard to,

53:22.100 --> 53:23.260
hard to get going.

53:23.360 --> 53:23.920
I've also been looking

53:23.920 --> 53:24.820
for a content management

53:24.820 --> 53:25.600
software because there

53:25.600 --> 53:27.680
are some things that I

53:27.680 --> 53:28.700
had a long time ago

53:28.700 --> 53:30.660
that, uh, like I had

53:30.660 --> 53:31.460
some, uh, on my old

53:31.460 --> 53:32.780
website, entanglement.net,

53:32.840 --> 53:35.140
I had some, uh, some

53:35.140 --> 53:36.000
phone sounds and stuff

53:36.000 --> 53:36.680
like that that I had

53:36.680 --> 53:37.900
recorded that I put up

53:37.900 --> 53:38.540
so people could listen

53:38.540 --> 53:38.780
to them.

53:38.800 --> 53:39.460
Different types of error

53:39.460 --> 53:40.360
messages and stuff like

53:40.360 --> 53:40.600
that.

53:40.680 --> 53:42.180
I've got a lot more

53:42.180 --> 53:43.220
phones because I have a

53:43.220 --> 53:44.040
bunch of international

53:44.040 --> 53:45.160
stuff, uh, that I

53:45.160 --> 53:46.200
recorded months and

53:46.200 --> 53:46.700
months ago.

53:47.240 --> 53:48.300
Um, so I'm going to

53:48.300 --> 53:48.980
take all those phone

53:48.980 --> 53:49.620
sounds and put them up

53:49.620 --> 53:50.240
on the site somewhere,

53:50.240 --> 53:51.260
but I want some content

53:51.260 --> 53:52.200
management software to

53:52.200 --> 53:52.960
make my life easier.

53:53.080 --> 53:53.740
I don't want to maintain

53:53.740 --> 53:54.840
static webpaces anymore.

53:55.320 --> 53:57.040
So I've almost settled

53:57.040 --> 53:57.960
on that software and

53:57.960 --> 53:58.640
once that's up and

53:58.640 --> 53:59.300
running, there's going to

53:59.300 --> 54:00.900
be way more than just

54:00.900 --> 54:01.900
scanned out numbers on

54:01.900 --> 54:02.380
Bell's Mind.

54:02.800 --> 54:03.440
There's going to be, you

54:03.440 --> 54:04.440
know, some freaking text

54:04.440 --> 54:05.300
files, there's going to be

54:05.300 --> 54:07.180
freak sounds, there's going

54:07.180 --> 54:08.140
to be a lot of cool stuff

54:08.140 --> 54:08.480
on there.

54:08.480 --> 54:10.100
And now that I have

54:10.100 --> 54:11.220
unlimited Western Europe

54:11.220 --> 54:12.380
courtesy of Lingo, which

54:12.380 --> 54:13.440
by the way, Lingo's call

54:13.440 --> 54:14.940
quality on, I'd say every

54:14.940 --> 54:15.840
10th call is really

54:15.840 --> 54:16.200
terrible.

54:17.140 --> 54:19.020
Um, but in any case,

54:19.140 --> 54:20.080
once, uh, now that I've

54:20.080 --> 54:21.020
got their service up and

54:21.020 --> 54:22.320
running, I can, uh, I can

54:22.320 --> 54:23.180
make all kinds of

54:23.180 --> 54:24.840
international calls and,

54:24.960 --> 54:26.440
uh, and get lots and

54:26.440 --> 54:27.240
lots of cool recordings.

54:27.620 --> 54:29.380
So look forward to that

54:29.380 --> 54:29.760
soon.

54:30.280 --> 54:30.960
Let me think.

54:31.220 --> 54:32.120
PBX updates.

54:32.620 --> 54:33.640
Well, and also before,

54:33.760 --> 54:34.860
I guess we can't mention

54:34.860 --> 54:36.780
any specifics, but, um,

54:36.780 --> 54:39.080
in general content for

54:39.080 --> 54:41.560
Bell's Mind, well, I

54:41.560 --> 54:43.000
guess some data

54:43.000 --> 54:44.080
pillaging has been going

54:44.080 --> 54:44.440
on.

54:45.200 --> 54:46.040
Uh, yeah.

54:46.120 --> 54:47.000
Is that safe to say?

54:47.660 --> 54:48.740
I was, I was just going

54:48.740 --> 54:50.540
to mention, uh, something.

54:50.880 --> 54:51.100
Hmm.

54:51.400 --> 54:52.740
Last couple days we've

54:52.740 --> 54:54.000
been on some, uh,

54:54.080 --> 54:54.500
missions.

54:55.500 --> 54:56.300
Yeah, we've been

54:56.300 --> 54:57.640
looking around, um,

54:57.960 --> 54:58.720
should I even mention

54:58.720 --> 54:59.200
what it is?

54:59.340 --> 54:59.640
No.

54:59.800 --> 55:00.900
Well, you know what,

55:00.940 --> 55:01.760
though, it's on, it's on

55:01.760 --> 55:02.420
the main page.

55:02.500 --> 55:02.920
People are going to

55:02.920 --> 55:03.140
know.

55:03.760 --> 55:04.200
Hmm.

55:04.340 --> 55:04.540
Oh.

55:05.280 --> 55:05.540
Well.

55:05.540 --> 55:06.280
Well, anyway.

55:06.780 --> 55:07.640
We've been, we've been

55:07.640 --> 55:08.680
looking around for, uh,

55:08.680 --> 55:10.960
for data on, um, on

55:10.960 --> 55:11.860
other countries and stuff

55:11.860 --> 55:12.600
like that, so.

55:12.880 --> 55:13.660
Yeah, that's all.

55:14.240 --> 55:14.480
Yeah.

55:14.840 --> 55:16.040
Uh, Bell's Mind is going

55:16.040 --> 55:17.640
international, and, uh,

55:17.640 --> 55:18.520
cause, like I said, I've

55:18.520 --> 55:20.000
got unlimited Western

55:20.000 --> 55:20.280
Europe.

55:20.380 --> 55:21.120
I want to start scanning

55:21.120 --> 55:22.680
numbers in Europe, so I'm,

55:22.680 --> 55:23.600
uh, I'm looking for

55:23.600 --> 55:25.120
information on, uh, on

55:25.120 --> 55:25.640
other countries.

55:25.780 --> 55:26.600
Anything you guys got to

55:26.600 --> 55:27.840
submit, feel free to send

55:27.840 --> 55:29.140
it off to me, and, uh,

55:29.140 --> 55:29.700
then I'm going to add

55:29.700 --> 55:30.840
support so people can add

55:30.840 --> 55:32.860
add numbers, uh, for

55:32.860 --> 55:33.440
different countries.

55:33.740 --> 55:34.760
And I think that's, that's

55:34.760 --> 55:35.420
going to be really cool.

55:35.420 --> 55:37.220
Bell's Mind is joining the

55:37.220 --> 55:38.740
global interweb.

55:39.440 --> 55:40.880
I, I like the progress of

55:40.880 --> 55:41.880
Bell's Mind so far, but

55:41.880 --> 55:43.400
the point has been, uh,

55:43.400 --> 55:44.660
brought to me that, you

55:44.660 --> 55:45.540
know, scanning the U.S.

55:45.540 --> 55:46.980
is cool, but, you know,

55:47.060 --> 55:47.940
freaks aren't just in the

55:47.940 --> 55:48.340
U.S.

55:48.340 --> 55:49.780
Most notably, Havoc.

55:49.900 --> 55:51.360
Havoc is like, you know,

55:51.460 --> 55:52.800
he's our man in Poland, or

55:52.800 --> 55:53.880
not our man in Poland, but

55:53.880 --> 55:54.920
he's the guy that everybody

55:54.920 --> 55:55.500
knows in Poland.

55:55.600 --> 55:56.300
He is all about

55:56.300 --> 55:57.640
freaking, and I would love

55:57.640 --> 55:58.920
to see, uh, you know, what

55:58.920 --> 55:59.580
he's got over there.

55:59.660 --> 56:00.340
I'd love to see some scan

56:00.340 --> 56:00.980
numbers he's got.

56:00.980 --> 56:04.220
So, that's the plan for the

56:04.220 --> 56:05.360
next large update for

56:05.360 --> 56:05.820
Bell's Mind.

56:05.980 --> 56:06.580
Very cool.

56:07.140 --> 56:08.780
And the PBX, uh, let me

56:08.780 --> 56:09.500
just throw this in here

56:09.500 --> 56:09.800
quickly.

56:09.880 --> 56:11.780
The PBX, we're adding new

56:11.780 --> 56:14.280
shows to the, uh, to the

56:14.280 --> 56:14.560
menus.

56:14.680 --> 56:15.200
We've got to wait until

56:15.200 --> 56:16.100
somebody records new

56:16.100 --> 56:16.740
menus for us.

56:16.860 --> 56:17.520
If somebody wants to

56:17.520 --> 56:19.120
record menus, definitely

56:19.120 --> 56:21.000
email me, um, mtheory at

56:21.000 --> 56:21.780
bellsmind.net.

56:21.780 --> 56:23.780
Um, we would love to have

56:23.780 --> 56:24.680
any type of menus people

56:24.680 --> 56:25.160
can submit.

56:25.300 --> 56:25.960
You know, I'll send you a

56:25.960 --> 56:27.580
script, get the menus back.

56:27.640 --> 56:28.280
If they're good, I'll throw

56:28.280 --> 56:29.000
them up in the box.

56:29.220 --> 56:30.480
Um, but yeah, we're looking

56:30.480 --> 56:31.540
to add shows to it.

56:31.680 --> 56:34.120
Um, um, I don't want to

56:34.120 --> 56:34.900
list the shows that we've

56:34.900 --> 56:35.740
got already, because I want

56:35.740 --> 56:36.280
to make sure that we've

56:36.280 --> 56:37.880
got everything set up before

56:37.880 --> 56:38.480
they go live.

56:38.620 --> 56:40.620
But new shows are coming

56:40.620 --> 56:41.460
up, and we would like

56:41.460 --> 56:42.920
people to, uh, you know,

56:42.940 --> 56:43.840
if you've got a show and

56:43.840 --> 56:44.560
you want it to be on our

56:44.560 --> 56:46.040
PBX, definitely email me.

56:46.220 --> 56:46.960
Uh, let me know what the

56:46.960 --> 56:47.400
show is.

56:47.440 --> 56:48.740
And the only, the only

56:48.740 --> 56:50.000
stipulation I have on it is

56:50.000 --> 56:51.260
that it's, is that the

56:51.260 --> 56:52.340
recording is good quality.

56:53.060 --> 56:54.540
Um, if you're committed to

56:54.540 --> 56:55.500
making a show, it doesn't

56:55.500 --> 56:56.640
have to be weekly or

56:56.640 --> 56:57.960
bi-weekly or whatever, but

56:57.960 --> 56:59.100
it's gotta, you've gotta

56:59.100 --> 56:59.740
come out with a show every

56:59.740 --> 57:00.080
once in a while.

57:00.140 --> 57:00.700
You can't come out with

57:00.700 --> 57:02.220
two episodes and then, and

57:02.220 --> 57:03.160
then stop, because I don't

57:03.160 --> 57:03.900
want to have to re-record

57:03.900 --> 57:04.820
menus because someone's

57:04.820 --> 57:05.600
not doing their show.

57:06.520 --> 57:08.460
Um, and you've also, out of

57:08.460 --> 57:09.560
courtesy, just when your

57:09.560 --> 57:10.940
show is updated, when

57:10.940 --> 57:12.220
there's a new episode, just

57:12.220 --> 57:13.400
email me so I can download

57:13.400 --> 57:14.540
it, you know, convert it to

57:14.540 --> 57:15.560
the proper format and put it

57:15.560 --> 57:16.200
on the PBX.

57:16.360 --> 57:16.760
That's it.

57:16.840 --> 57:17.540
So if you're willing to do

57:17.540 --> 57:19.140
all those things, we can, uh,

57:19.140 --> 57:19.720
we can get your show

57:19.720 --> 57:20.700
live on the PBX.

57:20.700 --> 57:21.960
Yeah, and actually, we

57:21.960 --> 57:23.160
may be able to work the

57:23.160 --> 57:24.420
whole thing out automated

57:24.420 --> 57:26.280
between DDB Hack Radio

57:26.280 --> 57:28.900
scheduling and get it up

57:28.900 --> 57:30.200
on there as well, so we

57:30.200 --> 57:30.960
may be able to automate

57:30.960 --> 57:31.960
that whole, that whole

57:31.960 --> 57:32.520
process.

57:32.980 --> 57:34.160
It, uh, it requires a

57:34.160 --> 57:34.840
little bit of scripting,

57:34.920 --> 57:36.060
but, um, I'm sure, as the

57:36.060 --> 57:37.540
listeners know, I've, uh, I

57:37.540 --> 57:38.300
started, I started

57:38.300 --> 57:40.100
programming last week, so I

57:40.100 --> 57:41.180
may actually be able to

57:41.180 --> 57:42.000
pull some of that off.

57:42.600 --> 57:42.940
Hmm.

57:44.940 --> 57:46.220
Maybe, but I don't know,

57:46.400 --> 57:47.140
you're a little small.

57:47.140 --> 57:48.400
Yeah, well, you know, I'm

57:48.400 --> 57:49.220
starting out with the

57:49.220 --> 57:50.620
Quick Basic, and once I

57:50.620 --> 57:51.600
get that, uh, you

57:51.600 --> 57:53.700
may be, uh, oh, you'd

57:53.700 --> 57:54.080
kill me.

57:54.700 --> 57:55.740
Oh, man, so let me think,

57:55.760 --> 57:56.600
is there anything else?

57:56.820 --> 57:58.680
Um, oh, Evan Doorbell

57:58.680 --> 57:59.140
recordings.

57:59.320 --> 58:00.340
I, I got a couple of them

58:00.340 --> 58:01.520
up there, but I'm looking

58:01.520 --> 58:02.900
to put everything on

58:02.900 --> 58:04.240
wideweb.com up on the

58:04.240 --> 58:05.720
PBX, because Evan Doorbell,

58:05.840 --> 58:07.720
Mark Bernay, Al Bernay, all

58:07.720 --> 58:08.520
those guys who do phone

58:08.520 --> 58:09.780
recordings, Strom Carlson has

58:09.780 --> 58:10.600
good phone recordings on

58:10.600 --> 58:12.300
his site, I want to put all

58:12.300 --> 58:13.340
that stuff up, because those

58:13.340 --> 58:15.000
guys do so much work, and,

58:15.080 --> 58:16.480
uh, I want everybody to be

58:16.480 --> 58:17.340
able to take advantage of

58:17.340 --> 58:17.500
that.

58:17.620 --> 58:18.500
So, all that stuff is

58:18.500 --> 58:19.540
going up as soon as I have

58:19.540 --> 58:20.560
time to, like I said,

58:20.600 --> 58:21.880
rebuild the menus and

58:21.880 --> 58:22.760
convert the files, it's

58:22.760 --> 58:23.420
going to all be there,

58:23.640 --> 58:24.640
with their permission, of

58:24.640 --> 58:24.820
course.

58:25.440 --> 58:27.040
Yeah, and, uh, also we

58:27.040 --> 58:28.260
discussed, uh, without

58:28.260 --> 58:29.640
going into too much detail

58:29.640 --> 58:31.220
again, only because we want

58:31.220 --> 58:31.920
to make sure we can get

58:31.920 --> 58:33.000
certain things to work or

58:33.000 --> 58:35.000
not, um, we might be able

58:35.000 --> 58:35.700
to offer some other

58:35.700 --> 58:37.840
features with the PBX to

58:37.840 --> 58:39.280
people who have hack radio

58:39.280 --> 58:42.020
shows, like, perhaps,

58:42.220 --> 58:43.800
mailboxes, voicemail boxes,

58:43.800 --> 58:45.540
um, recording, things like

58:45.540 --> 58:47.420
that, if we can get

58:47.420 --> 58:48.480
something, if we can figure

58:48.480 --> 58:49.600
out how to do that easily

58:49.600 --> 58:50.960
without consuming a whole

58:50.960 --> 58:51.960
lot of our time taking away

58:51.960 --> 58:52.980
from other projects, is

58:52.980 --> 58:53.600
that accurate?

58:53.600 --> 58:53.640
Right.

58:54.080 --> 58:55.080
Uh, yeah, there's a lot of

58:55.080 --> 58:55.880
things I would like to offer

58:55.880 --> 58:56.480
the guys who are doing

58:56.480 --> 58:57.360
radio shows, because they're

58:57.360 --> 58:58.420
putting in so much time,

58:58.640 --> 59:00.460
uh, you know, to help

59:00.460 --> 59:01.380
everybody in the scene out,

59:01.500 --> 59:04.120
so, um, yeah, there's,

59:04.180 --> 59:05.080
there's stuff coming for you

59:05.080 --> 59:06.340
guys, anybody, anybody who

59:06.340 --> 59:07.300
I've talked to about their

59:07.300 --> 59:08.800
radio show, uh, you've got

59:08.800 --> 59:09.760
some nice stuff coming to

59:09.760 --> 59:11.960
you, as long as, uh, as

59:11.960 --> 59:12.500
long as my time

59:12.500 --> 59:13.340
constraints work out.

59:13.340 --> 59:14.300
Oh, and by the way, if

59:14.300 --> 59:15.340
anybody's doing a radio show

59:15.340 --> 59:16.220
and you guys need a bridge

59:16.220 --> 59:17.660
to record on, just call up

59:17.660 --> 59:19.720
my PBX and, uh, dial up

59:19.720 --> 59:20.620
any bridge, and feel free

59:20.620 --> 59:21.280
to use it anytime.

59:21.620 --> 59:22.700
You know, we've got tons

59:22.700 --> 59:23.500
and tons of bandwidth,

59:24.000 --> 59:25.200
the machines idle, you

59:25.200 --> 59:26.800
know, pretty much all day,

59:27.240 --> 59:28.260
uh, because the load from

59:28.260 --> 59:29.640
the Astro server is so low.

59:29.760 --> 59:30.360
You know, we get a bunch

59:30.360 --> 59:31.360
of people on at night, but,

59:31.520 --> 59:32.920
you know, if you guys want

59:32.920 --> 59:33.940
to use it during the day or

59:33.940 --> 59:34.680
during the night, whatever,

59:34.820 --> 59:35.700
to record a show on one of

59:35.700 --> 59:37.100
the bridges, please, by all

59:37.100 --> 59:37.760
means, do it.

59:38.320 --> 59:40.500
So, uh, you know, use the

59:40.500 --> 59:41.520
PBX, use my bandwidth,

59:41.720 --> 59:41.940
you know?

59:42.940 --> 59:43.460
Fear.

59:43.720 --> 59:45.200
Or, I fear the

59:45.200 --> 59:45.480
fairness.

59:45.480 --> 59:51.520
Now, um, let's use that

59:51.520 --> 59:53.620
con, that idea of working

59:53.620 --> 59:55.340
on the, um, well, on

59:55.340 --> 59:57.520
Bell's mind, that is, and

59:57.520 --> 59:58.960
kind of transition into what

59:58.960 --> 59:59.800
it was going to be our main

59:59.800 --> 01:00:00.120
topic.

01:00:00.200 --> 01:00:01.580
Let me check our time here.

01:00:01.660 --> 01:00:03.900
We've got about 20 minutes,

01:00:03.960 --> 01:00:04.780
so we've still got some good

01:00:04.780 --> 01:00:05.700
time to talk about this

01:00:05.700 --> 01:00:07.960
stuff, um, and transition

01:00:07.960 --> 01:00:09.620
just to talk about databases

01:00:09.620 --> 01:00:12.620
in general, and then

01:00:12.620 --> 01:00:14.020
specifically, more specifically

01:00:14.020 --> 01:00:15.660
relational databases, because

01:00:15.660 --> 01:00:17.520
this is basically what I do

01:00:17.520 --> 01:00:19.200
for a living, and

01:00:19.200 --> 01:00:20.880
something that you use on

01:00:20.880 --> 01:00:23.340
bellsmind.net regularly, you

01:00:23.340 --> 01:00:24.760
know, it's an important part

01:00:24.760 --> 01:00:25.760
of the, I mean, it is the

01:00:25.760 --> 01:00:26.760
whole thing, it's the back

01:00:26.760 --> 01:00:28.420
end of the whole system, and

01:00:28.420 --> 01:00:30.000
I think we're going to both

01:00:30.000 --> 01:00:31.280
come out, and I think you've

01:00:31.280 --> 01:00:32.340
already done it, come out and

01:00:32.340 --> 01:00:36.800
endorse Postgres as, to me,

01:00:36.960 --> 01:00:39.080
the dominant relational database

01:00:39.080 --> 01:00:40.280
management system out there

01:00:40.280 --> 01:00:40.740
right now.

01:00:41.300 --> 01:00:42.160
Yeah, um.

01:00:42.180 --> 01:00:43.380
But before we talk about the

01:00:43.380 --> 01:00:44.720
specifics of the individual

01:00:44.720 --> 01:00:45.920
ones, let's talk about just

01:00:45.920 --> 01:00:47.760
databases in general, and

01:00:47.760 --> 01:00:49.880
what, what constitutes a

01:00:49.880 --> 01:00:50.220
database.

01:00:51.040 --> 01:00:54.220
For example, in its simplistic,

01:00:54.460 --> 01:00:56.000
in its most simplistic form, a

01:00:56.000 --> 01:00:57.400
database is just a collection

01:00:57.400 --> 01:00:57.980
of data.

01:00:58.340 --> 01:01:00.800
It can be as simple as an Excel

01:01:00.800 --> 01:01:02.660
spreadsheet, or a text file with

01:01:02.660 --> 01:01:04.820
scanned phone numbers, or

01:01:04.820 --> 01:01:05.880
anything like that in it.

01:01:06.660 --> 01:01:06.900
Right.

01:01:06.900 --> 01:01:08.480
By the textbook definition, a

01:01:08.480 --> 01:01:09.800
database can simply be an

01:01:09.800 --> 01:01:10.960
organized collection of, an

01:01:10.960 --> 01:01:12.480
organized gathering of data.

01:01:13.880 --> 01:01:16.080
And over the years, you know,

01:01:16.500 --> 01:01:18.240
they've come up with processes

01:01:18.240 --> 01:01:20.100
and ways to access that data

01:01:20.100 --> 01:01:21.200
and interface it, whether it

01:01:21.200 --> 01:01:24.400
be from, you know, a third,

01:01:24.520 --> 01:01:25.980
fourth generation programming

01:01:25.980 --> 01:01:27.480
language, accessing that data

01:01:27.480 --> 01:01:29.460
file, um, accessing it

01:01:29.460 --> 01:01:31.000
directly within some sort of

01:01:31.000 --> 01:01:32.480
database system with SQL of

01:01:32.480 --> 01:01:32.960
some sort.

01:01:33.600 --> 01:01:35.060
Um, most recently, the

01:01:35.060 --> 01:01:36.460
phenomenon and the trend has

01:01:36.460 --> 01:01:38.740
been to move to something

01:01:38.740 --> 01:01:40.220
called relational databases.

01:01:41.720 --> 01:01:45.560
Now, um, gosh, this is

01:01:45.560 --> 01:01:47.360
really something that would

01:01:47.360 --> 01:01:49.220
lend itself well to charts and

01:01:49.220 --> 01:01:50.680
drawing and demonstrating stuff

01:01:50.680 --> 01:01:52.660
and graphs and, and stuff like

01:01:52.660 --> 01:01:53.080
that.

01:01:53.200 --> 01:01:54.400
But not on the radio.

01:01:54.600 --> 01:01:55.940
But yes, unfortunately, I'm

01:01:55.940 --> 01:01:56.920
going to have to try to do

01:01:56.920 --> 01:01:57.280
this.

01:01:58.040 --> 01:01:59.140
We're going to have to try to do

01:01:59.140 --> 01:01:59.240
this.

01:01:59.240 --> 01:02:00.100
You have to jump in and help me

01:02:00.100 --> 01:02:00.300
here.

01:02:00.920 --> 01:02:03.420
Um, a relational database, what

01:02:03.420 --> 01:02:05.700
makes it different than just a

01:02:05.700 --> 01:02:07.740
collection of data is it's more

01:02:07.740 --> 01:02:09.560
like a collection of, of tables

01:02:09.560 --> 01:02:10.340
is the terminology.

01:02:10.340 --> 01:02:12.140
It's a collection of databases, a

01:02:12.140 --> 01:02:13.260
collection of files.

01:02:13.880 --> 01:02:16.620
And each one of these files has

01:02:16.620 --> 01:02:20.740
been normalized to have very

01:02:20.740 --> 01:02:22.880
precise data in each individual

01:02:22.880 --> 01:02:23.360
table.

01:02:23.360 --> 01:02:26.820
And data normalization is

01:02:26.820 --> 01:02:28.380
something that's a very, very,

01:02:28.480 --> 01:02:30.900
very important term in relational

01:02:30.900 --> 01:02:32.060
databases and absolutely

01:02:32.060 --> 01:02:33.680
something in your computer

01:02:33.680 --> 01:02:34.120
classes.

01:02:34.240 --> 01:02:35.540
I know like this is one of the

01:02:35.540 --> 01:02:36.360
things they teach you in the

01:02:36.360 --> 01:02:37.360
beginning and it sounds real

01:02:37.360 --> 01:02:39.000
boring, but it's the, just the,

01:02:39.000 --> 01:02:41.500
the foundation of relational

01:02:41.500 --> 01:02:42.100
databases.

01:02:43.100 --> 01:02:45.220
And I guess to make up an example

01:02:45.220 --> 01:02:46.620
off the top of my head would be

01:02:46.620 --> 01:02:49.420
imagine that you have a, uh, a

01:02:49.420 --> 01:02:52.600
website, an online storefront and

01:02:52.600 --> 01:02:54.380
you could easily put a bunch of

01:02:54.380 --> 01:02:56.500
data into one big file that has

01:02:56.500 --> 01:02:58.140
name, address, credit card

01:02:58.140 --> 01:03:00.720
number, um, the items that they

01:03:00.720 --> 01:03:02.060
ordered, the price of each item,

01:03:02.160 --> 01:03:02.540
et cetera.

01:03:02.800 --> 01:03:04.360
But that's not the most efficient

01:03:04.360 --> 01:03:06.640
way to store data in a database,

01:03:06.740 --> 01:03:08.040
especially relational database.

01:03:08.560 --> 01:03:10.220
You have duplicate records, you

01:03:10.220 --> 01:03:11.780
have duplicate items, you, one

01:03:11.780 --> 01:03:13.640
person places an order on one day

01:03:13.640 --> 01:03:14.740
and then comes back a week later

01:03:14.740 --> 01:03:15.640
and places another one.

01:03:15.840 --> 01:03:17.400
You've got a whole nother record in

01:03:17.400 --> 01:03:18.500
there with a lot of the same

01:03:18.500 --> 01:03:19.700
information, which is wasted.

01:03:19.700 --> 01:03:23.300
So, normalizing that data is to

01:03:23.300 --> 01:03:25.400
sit down and come up with a

01:03:25.400 --> 01:03:27.160
logical way to break up your data

01:03:27.160 --> 01:03:29.980
into multiple tables so that it

01:03:29.980 --> 01:03:31.320
is efficiently stored and you

01:03:31.320 --> 01:03:33.620
minimize or eliminate, ideally

01:03:33.620 --> 01:03:35.660
eliminate duplicate data of any

01:03:35.660 --> 01:03:36.060
kind.

01:03:36.640 --> 01:03:37.920
And to do that, you'd collapse.

01:03:38.020 --> 01:03:39.420
Instead of having one table with

01:03:39.420 --> 01:03:40.580
all that information and all the

01:03:40.580 --> 01:03:41.700
duplicates and stuff, you break

01:03:41.700 --> 01:03:44.840
that out into logical separations

01:03:44.840 --> 01:03:46.360
of different files or different

01:03:46.360 --> 01:03:46.780
tables.

01:03:46.780 --> 01:03:48.660
For example, you'd make a table

01:03:48.660 --> 01:03:50.860
with customers and customer

01:03:50.860 --> 01:03:51.440
information.

01:03:51.580 --> 01:03:53.780
And that table would contain name,

01:03:53.940 --> 01:03:55.400
address, phone number, things like

01:03:55.400 --> 01:03:55.780
that.

01:03:56.500 --> 01:03:58.000
And a unique ID for each customer.

01:03:58.420 --> 01:03:58.900
Right.

01:03:59.140 --> 01:04:01.820
Well, and they'll have to be tied

01:04:01.820 --> 01:04:02.700
together at some point.

01:04:03.160 --> 01:04:06.920
You make a separate table of items

01:04:06.920 --> 01:04:09.780
and a unique item ID for that item.

01:04:09.780 --> 01:04:13.840
And you could break it down to as

01:04:13.840 --> 01:04:15.900
many tables as you want, right down

01:04:15.900 --> 01:04:17.260
to making, if you really wanted to

01:04:17.260 --> 01:04:19.960
separate out a table for states.

01:04:20.260 --> 01:04:22.180
You can make a table with 50 records

01:04:22.180 --> 01:04:23.340
for all the states and the state

01:04:23.340 --> 01:04:24.800
codes that can be cross-referenced.

01:04:25.040 --> 01:04:26.920
Because technically, two people from

01:04:26.920 --> 01:04:28.100
one state order something, that's

01:04:28.100 --> 01:04:28.780
duplicate data.

01:04:29.220 --> 01:04:30.040
Seems kind of silly.

01:04:30.120 --> 01:04:31.340
It's only a two-character code or

01:04:31.340 --> 01:04:31.620
something.

01:04:31.820 --> 01:04:33.500
But even that can be normalized off to

01:04:33.500 --> 01:04:34.280
a separate table.

01:04:34.280 --> 01:04:39.440
And most database systems and

01:04:39.440 --> 01:04:41.580
programs, like at universities and

01:04:41.580 --> 01:04:43.640
companies and stuff, you will find

01:04:43.640 --> 01:04:46.540
that you don't have a database.

01:04:46.840 --> 01:04:48.340
It's a common misconception to say

01:04:48.340 --> 01:04:49.000
the database.

01:04:49.680 --> 01:04:51.380
Well, it's a database, but it's a

01:04:51.380 --> 01:04:53.240
database that's made up of thousands

01:04:53.240 --> 01:04:55.340
and thousands of individual tables.

01:04:55.800 --> 01:04:57.220
And those tables all have to have

01:04:57.220 --> 01:04:58.860
relationships with each other.

01:04:59.740 --> 01:05:01.920
And if you can take off with that,

01:05:01.920 --> 01:05:04.020
you were just about to say unique

01:05:04.020 --> 01:05:05.500
identifiers, and those are important

01:05:05.500 --> 01:05:07.340
because they'll tie the databases

01:05:07.340 --> 01:05:08.000
together.

01:05:08.180 --> 01:05:08.820
Yeah, exactly.

01:05:09.080 --> 01:05:10.340
Depending on, you know, obviously

01:05:10.340 --> 01:05:11.760
it depends on what your database is.

01:05:11.840 --> 01:05:14.740
But for example, how many different

01:05:14.740 --> 01:05:16.060
tables do you have with your

01:05:16.060 --> 01:05:17.360
BellsMine database?

01:05:18.160 --> 01:05:20.300
Ooh, that's a good question.

01:05:20.900 --> 01:05:22.840
You know, not precisely, but just

01:05:22.840 --> 01:05:24.160
kind of ballpark, I mean.

01:05:24.820 --> 01:05:26.580
Probably about ten, I'd say.

01:05:26.820 --> 01:05:27.620
Not so many.

01:05:27.780 --> 01:05:29.380
It's actually, it's fairly simple

01:05:29.380 --> 01:05:29.880
right now.

01:05:29.880 --> 01:05:33.640
So, like, when somebody submits

01:05:33.640 --> 01:05:36.000
things, do you keep the submitters,

01:05:36.080 --> 01:05:37.360
do you keep the people who submit

01:05:37.360 --> 01:05:39.740
in a table separately that's

01:05:39.740 --> 01:05:41.400
cross-referenced from the main

01:05:41.400 --> 01:05:42.980
collection of numbers, I would

01:05:42.980 --> 01:05:44.020
imagine, in a different table?

01:05:44.160 --> 01:05:44.760
I don't know.

01:05:44.820 --> 01:05:45.820
I'm making this up, of course,

01:05:45.880 --> 01:05:46.780
so please correct me.

01:05:47.160 --> 01:05:47.600
Yeah, yeah, yeah.

01:05:47.600 --> 01:05:47.800
Okay.

01:05:48.320 --> 01:05:50.000
Basically, there's a table that has

01:05:50.000 --> 01:05:51.720
each user in it, right?

01:05:52.220 --> 01:05:53.640
And then there's a table that has

01:05:53.640 --> 01:05:55.300
the scanned numbers in it.

01:05:55.300 --> 01:05:56.380
And the scanned number is, like,

01:05:56.780 --> 01:05:58.680
the area code, the prefix, the

01:05:58.680 --> 01:06:00.360
suffix, the description, the

01:06:00.360 --> 01:06:02.880
number type, and then it has a

01:06:02.880 --> 01:06:05.780
link to the user's table with the

01:06:05.780 --> 01:06:06.320
user ID.

01:06:06.820 --> 01:06:08.480
A unique user ID.

01:06:08.880 --> 01:06:10.000
Yeah, the unique user ID.

01:06:10.120 --> 01:06:11.120
I don't actually store the user

01:06:11.120 --> 01:06:12.760
name in the table of scanned

01:06:12.760 --> 01:06:13.120
numbers.

01:06:13.300 --> 01:06:14.640
Instead, I just store, like, this

01:06:14.640 --> 01:06:17.040
two-byte, or however large the

01:06:17.040 --> 01:06:18.800
database makes it, probably two-byte

01:06:18.800 --> 01:06:20.940
or four-byte number that

01:06:20.940 --> 01:06:22.000
references the user table.

01:06:22.900 --> 01:06:24.540
So none of that information is

01:06:24.540 --> 01:06:25.640
duplicated at any point.

01:06:25.780 --> 01:06:25.980
Right.

01:06:26.060 --> 01:06:28.060
So, for example, StankDog could be

01:06:28.060 --> 01:06:31.760
assigned number one, and let's

01:06:31.760 --> 01:06:33.480
say Strom Carlson assigned number

01:06:33.480 --> 01:06:34.780
two, and G.I.

01:06:34.840 --> 01:06:35.680
Joe, whoever else we want to

01:06:35.680 --> 01:06:36.280
shout out, G.I.

01:06:36.280 --> 01:06:37.220
Joe assigned number three.

01:06:37.860 --> 01:06:39.720
So every time I submit a number,

01:06:39.880 --> 01:06:41.300
instead of duplicating my name

01:06:41.300 --> 01:06:43.560
every time, you simply point to

01:06:43.560 --> 01:06:46.740
that same unique ID of one, so

01:06:46.740 --> 01:06:48.220
you know that no matter how many

01:06:48.220 --> 01:06:49.620
numbers I get, there's only one

01:06:49.620 --> 01:06:51.300
occurrence of StankDog in that

01:06:51.300 --> 01:06:51.660
table.

01:06:52.340 --> 01:06:52.620
Right.

01:06:52.620 --> 01:06:55.500
So thereby, eliminating, if I

01:06:55.500 --> 01:06:57.340
submitted 500 numbers, you don't

01:06:57.340 --> 01:06:59.280
have StankDog written 500 times in

01:06:59.280 --> 01:07:01.960
one table, you have it once in a

01:07:01.960 --> 01:07:03.660
separate table linked to from the

01:07:03.660 --> 01:07:04.220
main table.

01:07:04.660 --> 01:07:04.880
Right.

01:07:04.980 --> 01:07:05.640
And that helps you with

01:07:05.640 --> 01:07:07.860
consistency, too, other than, like,

01:07:07.900 --> 01:07:09.000
making your database smaller.

01:07:09.440 --> 01:07:10.500
Like, you don't have to worry if

01:07:10.500 --> 01:07:11.700
somebody submits something, and,

01:07:11.780 --> 01:07:13.180
like, if you have them type their

01:07:13.180 --> 01:07:14.480
name in when they submit it, but

01:07:14.480 --> 01:07:15.680
they don't type it in two different

01:07:15.680 --> 01:07:17.680
ways, like StankDog or StankDog with

01:07:17.680 --> 01:07:19.260
a space in the middle, you know.

01:07:19.600 --> 01:07:19.940
Right.

01:07:19.940 --> 01:07:21.400
You can keep everything very

01:07:21.400 --> 01:07:22.020
consistently.

01:07:22.320 --> 01:07:23.060
Yeah, yeah, absolutely.

01:07:23.260 --> 01:07:26.340
Data integrity is maintained by the

01:07:26.340 --> 01:07:28.640
sheer logical nature of it.

01:07:29.160 --> 01:07:29.440
Yeah.

01:07:29.960 --> 01:07:32.420
So that is, you know, that's a good

01:07:32.420 --> 01:07:35.080
example, and again, that's one tiny

01:07:35.080 --> 01:07:37.980
example of, I mean, imagine how much

01:07:37.980 --> 01:07:38.720
space is saved.

01:07:38.800 --> 01:07:40.460
All those bytes, instead of, you know,

01:07:40.500 --> 01:07:42.520
nine characters, you use one.

01:07:43.480 --> 01:07:43.840
Right.

01:07:44.480 --> 01:07:47.580
So, 500, do the math, you see you save

01:07:47.580 --> 01:07:49.400
a lot of bytes there, and this, again,

01:07:49.460 --> 01:07:50.280
is a small example.

01:07:50.640 --> 01:07:51.760
Now, when you're working for a

01:07:51.760 --> 01:07:53.240
Fortune 500 company, and you have

01:07:53.240 --> 01:07:55.680
thousands of tables, and lots and

01:07:55.680 --> 01:07:57.060
lots of orders, think Amazon.

01:07:57.920 --> 01:08:00.040
If they didn't have data normalized and

01:08:00.040 --> 01:08:01.860
running efficiently, just imagine the

01:08:01.860 --> 01:08:04.080
space that they would be taking up.

01:08:04.120 --> 01:08:06.000
And they still take up a lot of

01:08:06.000 --> 01:08:07.140
space, don't get me wrong, I'm sure

01:08:07.140 --> 01:08:08.300
their database is huge.

01:08:08.740 --> 01:08:09.000
Yeah.

01:08:09.000 --> 01:08:11.480
But, imagine what it wouldn't be if

01:08:11.480 --> 01:08:12.740
they didn't have normalized data.

01:08:13.380 --> 01:08:15.320
So, that's what a relational database

01:08:15.320 --> 01:08:17.140
is, where all of the individual

01:08:17.140 --> 01:08:19.980
tables have relationships with each

01:08:19.980 --> 01:08:22.560
other through some sort of unique

01:08:22.560 --> 01:08:25.860
key, and it's called, each table has a

01:08:25.860 --> 01:08:27.060
key that you use to read it.

01:08:27.780 --> 01:08:30.640
So, by figuring out the logical keys

01:08:30.640 --> 01:08:32.400
and how you can break this down, you

01:08:32.400 --> 01:08:34.260
form relationships with all of the

01:08:34.260 --> 01:08:34.620
tables.

01:08:35.160 --> 01:08:36.780
For example, I mentioned earlier about

01:08:36.780 --> 01:08:38.560
making a table with the 50 states on

01:08:38.560 --> 01:08:38.680
it.

01:08:39.180 --> 01:08:41.100
This also helps your data integrity

01:08:41.100 --> 01:08:43.080
because you can present a user, for

01:08:43.080 --> 01:08:44.400
example, you can write, this is all

01:08:44.400 --> 01:08:45.720
we're talking back-end stuff of

01:08:45.720 --> 01:08:46.680
database design.

01:08:47.060 --> 01:08:48.600
But on the front end, you can give a

01:08:48.600 --> 01:08:49.820
user a drop-down list.

01:08:50.520 --> 01:08:52.740
That drop-down list is powered by your

01:08:52.740 --> 01:08:54.660
validation table of the 50 states.

01:08:55.040 --> 01:08:56.320
And when they get a drop-down list,

01:08:56.680 --> 01:08:58.120
they can't make up a state.

01:08:58.720 --> 01:08:59.120
Right.

01:08:59.420 --> 01:09:01.160
And I have been, I have worked for

01:09:01.160 --> 01:09:03.660
places that had such garbage data in

01:09:03.660 --> 01:09:06.140
them, that you would just laugh out

01:09:06.140 --> 01:09:07.620
loud at some of the crap that they put

01:09:07.620 --> 01:09:08.000
in there.

01:09:08.620 --> 01:09:11.160
So, by having validation tables, which

01:09:11.160 --> 01:09:13.500
is just kind of a term for a different

01:09:13.500 --> 01:09:15.440
type of table, you can ensure that

01:09:15.440 --> 01:09:17.900
only one of those valid 50 states gets

01:09:17.900 --> 01:09:18.200
input.

01:09:18.320 --> 01:09:20.040
It will not give them the option to put

01:09:20.040 --> 01:09:22.580
something else in from the, if you

01:09:22.580 --> 01:09:23.900
design a nice screen for them.

01:09:24.020 --> 01:09:25.700
Or, even if you yourself as a

01:09:25.700 --> 01:09:27.240
programmer make a mistake and try to

01:09:27.240 --> 01:09:30.860
put in, you know, G-O instead of G-A-E

01:09:30.860 --> 01:09:32.900
and try to put in a state that doesn't

01:09:32.900 --> 01:09:35.220
exist, it will even stop you from

01:09:35.220 --> 01:09:36.320
corrupting your own data.

01:09:37.020 --> 01:09:37.300
Right.

01:09:37.520 --> 01:09:39.900
And an example, I guess, again, relates

01:09:39.900 --> 01:09:40.700
back to Bell's Mind.

01:09:40.860 --> 01:09:42.800
If people are familiar with, you know,

01:09:43.260 --> 01:09:44.440
more familiar with that, I guess.

01:09:45.100 --> 01:09:47.560
They, when you enter a number, you enter

01:09:47.560 --> 01:09:49.360
like an area code and a prefix.

01:09:49.560 --> 01:09:51.500
When you submit that number, I actually

01:09:51.500 --> 01:09:52.940
have the NAMPA, which is the North

01:09:52.940 --> 01:09:54.360
American Numbering Plan Association.

01:09:54.560 --> 01:09:56.620
I have their database of all the area

01:09:56.620 --> 01:09:58.440
codes and exchanges in the U.S. that are

01:09:58.440 --> 01:09:58.700
valid.

01:09:58.700 --> 01:10:00.680
If you enter one that's not valid, it's

01:10:00.680 --> 01:10:01.800
not going to let you submit the number.

01:10:02.420 --> 01:10:03.300
Excellent example.

01:10:03.520 --> 01:10:04.380
Perfect example.

01:10:05.820 --> 01:10:06.260
Perfect example.

01:10:06.260 --> 01:10:09.320
And enter like 914-111, and then, you

01:10:09.320 --> 01:10:11.540
know, it'll tell you that it's valid.

01:10:11.620 --> 01:10:12.520
Or, actually, it should.

01:10:12.620 --> 01:10:13.000
You know what?

01:10:13.040 --> 01:10:14.060
I haven't tested it in a while.

01:10:14.140 --> 01:10:15.160
It's on a bunch of code updates.

01:10:15.360 --> 01:10:16.560
Maybe it does.

01:10:16.660 --> 01:10:17.060
Let's do it.

01:10:17.260 --> 01:10:19.280
Yeah, well, I doubt you undid that.

01:10:19.320 --> 01:10:20.780
If it was working, you know, earlier,

01:10:20.880 --> 01:10:21.900
I'm sure you didn't undo that

01:10:21.900 --> 01:10:22.460
functionality.

01:10:23.100 --> 01:10:23.620
Yeah, we'll see.

01:10:23.700 --> 01:10:24.380
Well, now I know.

01:10:24.600 --> 01:10:25.140
Not intentionally.

01:10:25.260 --> 01:10:26.300
After this show airs, there's going to

01:10:26.300 --> 01:10:28.080
be like 40,000 numbers submitted and

01:10:28.080 --> 01:10:28.420
invalid.

01:10:31.060 --> 01:10:35.820
Well, now, the next question, and

01:10:35.820 --> 01:10:37.760
please, if there's something else you

01:10:37.760 --> 01:10:39.600
think I left out or you want to add,

01:10:39.660 --> 01:10:40.120
go ahead.

01:10:40.980 --> 01:10:43.800
But I was going to move into what is

01:10:43.800 --> 01:10:44.940
database programming?

01:10:45.540 --> 01:10:47.180
Because people hear the term, and, you

01:10:47.180 --> 01:10:48.040
know, well, when people hear

01:10:48.040 --> 01:10:50.580
programming, they immediately think C

01:10:50.580 --> 01:10:52.800
programming, C++, object-oriented,

01:10:52.920 --> 01:10:53.940
visual basic, something.

01:10:54.920 --> 01:10:55.020
Yeah.

01:10:55.020 --> 01:10:56.520
When you say database programming,

01:10:56.640 --> 01:10:59.660
people don't exactly understand what

01:10:59.660 --> 01:11:01.360
you mean unless they've done it before.

01:11:02.840 --> 01:11:03.680
Now, the predominant...

01:11:04.780 --> 01:11:06.020
It's just funny that you bring that

01:11:06.020 --> 01:11:07.780
up, because until, you know, until

01:11:07.780 --> 01:11:09.100
recently, I didn't really have a concept

01:11:09.100 --> 01:11:12.140
of what database programming really was.

01:11:12.260 --> 01:11:14.020
I just, like, I don't know.

01:11:14.180 --> 01:11:16.200
I kind of, you know what, once we get

01:11:16.200 --> 01:11:18.820
into details, I'll explain about all

01:11:18.820 --> 01:11:19.280
that, I guess.

01:11:19.280 --> 01:11:20.800
Yeah, and I'm going to try to speed up

01:11:20.800 --> 01:11:22.440
here, because we're running, we've got

01:11:22.440 --> 01:11:23.800
maybe 12 minutes.

01:11:24.840 --> 01:11:25.840
Yeah, I'll go very...

01:11:25.840 --> 01:11:26.960
Let me try to go quickly here.

01:11:27.020 --> 01:11:28.260
Actually, I don't want to rush this,

01:11:28.340 --> 01:11:32.380
though, but basically, the language that

01:11:32.380 --> 01:11:34.880
most database, relational database

01:11:34.880 --> 01:11:36.960
systems use is SQL.

01:11:37.620 --> 01:11:39.180
And I hate it when people call it SQL.

01:11:39.300 --> 01:11:39.580
It's not.

01:11:39.680 --> 01:11:40.380
It's SQL.

01:11:42.260 --> 01:11:45.100
Microsoft, when people refer to

01:11:45.100 --> 01:11:46.520
Microsoft, they use the word SQL.

01:11:46.520 --> 01:11:49.400
SQL, but I don't call all SQL language,

01:11:49.440 --> 01:11:50.700
all SQL language a SQL.

01:11:50.840 --> 01:11:51.340
I hate that.

01:11:52.640 --> 01:11:56.800
But you write programs in some type

01:11:56.800 --> 01:11:59.780
of SQL language, some type of SQL.

01:11:59.880 --> 01:12:01.720
Now, SQL is a standard.

01:12:01.820 --> 01:12:03.800
There's an ANSI standard for SQL

01:12:03.800 --> 01:12:05.840
that was developed years ago.

01:12:05.940 --> 01:12:06.860
It's nothing new.

01:12:07.600 --> 01:12:10.640
But as technology advanced and as

01:12:10.640 --> 01:12:12.780
databases became more and more complex

01:12:12.780 --> 01:12:16.160
and more and more feature-filled,

01:12:16.520 --> 01:12:19.940
they found the need arose to do things

01:12:19.940 --> 01:12:21.620
with the data and analyze the data.

01:12:21.700 --> 01:12:23.300
With data warehousing as a phenomenon

01:12:23.300 --> 01:12:26.160
lately and deep data analysis,

01:12:26.340 --> 01:12:27.620
they found that they needed to start

01:12:27.620 --> 01:12:29.540
coming up with ways to do something

01:12:29.540 --> 01:12:31.740
more advanced instead of simple...

01:12:31.740 --> 01:12:33.940
You know, people who know basic SQL

01:12:33.940 --> 01:12:36.440
know that the most simple SQL is

01:12:36.440 --> 01:12:40.960
select whatever from whatever table name,

01:12:41.600 --> 01:12:43.500
where, and then whatever criteria.

01:12:44.360 --> 01:12:49.920
Select all numbers from Bell's Mind main table

01:12:49.920 --> 01:12:52.420
where area code equals 914.

01:12:53.100 --> 01:12:53.400
Right.

01:12:53.720 --> 01:12:55.660
So it can be that simple.

01:12:56.100 --> 01:12:57.100
But it's not always.

01:12:57.200 --> 01:12:58.480
Sometimes you need to sort them.

01:12:58.580 --> 01:13:00.340
Sometimes you want to eliminate 914,

01:13:00.340 --> 01:13:02.120
or 111.

01:13:02.180 --> 01:13:03.260
It's not a valid or something.

01:13:03.360 --> 01:13:04.340
Whatever your example you're...

01:13:04.340 --> 01:13:05.820
You can eliminate those if you have

01:13:05.820 --> 01:13:06.700
a little bit more flexibility.

01:13:07.240 --> 01:13:07.640
Right.

01:13:07.640 --> 01:13:10.460
Well, most SQL languages now

01:13:10.460 --> 01:13:11.540
that come with these things

01:13:11.540 --> 01:13:13.000
are, believe it or not,

01:13:13.400 --> 01:13:15.620
object-oriented SQL.

01:13:16.620 --> 01:13:18.700
For example, in Oracle,

01:13:18.960 --> 01:13:20.380
it's called PLSQL.

01:13:21.620 --> 01:13:23.440
In Postgres, it's...

01:13:23.440 --> 01:13:24.320
What is it called again?

01:13:24.860 --> 01:13:25.360
Is it just...

01:13:25.360 --> 01:13:27.560
It's called PLPGSQL.

01:13:27.880 --> 01:13:28.100
Yeah.

01:13:28.100 --> 01:13:32.600
Each different relational database management system

01:13:32.600 --> 01:13:33.780
has their own.

01:13:34.800 --> 01:13:36.660
They still have ANSI standards

01:13:36.660 --> 01:13:37.740
supported in most of them.

01:13:37.840 --> 01:13:39.540
Actually, Microsoft doesn't support all of them,

01:13:39.720 --> 01:13:40.980
which I was going to talk about.

01:13:41.080 --> 01:13:42.220
We might have to save that for another one.

01:13:43.740 --> 01:13:44.580
But basically,

01:13:44.740 --> 01:13:47.640
they all have a query language of some kind

01:13:47.640 --> 01:13:49.620
that's a lot more robust than people think.

01:13:49.620 --> 01:13:53.180
And maybe if we break down...

01:13:53.180 --> 01:13:54.720
Maybe if we go through some of the lists.

01:13:54.880 --> 01:13:57.140
Like, there's four big ones in my mind.

01:13:57.220 --> 01:13:57.760
There are more,

01:13:57.840 --> 01:13:58.720
but there's four big ones.

01:13:58.880 --> 01:13:59.260
Oracle,

01:14:00.060 --> 01:14:01.820
Microsoft SQL Server 2000,

01:14:02.740 --> 01:14:03.320
MySQL,

01:14:04.140 --> 01:14:05.400
and Postgres,

01:14:05.640 --> 01:14:06.520
or PostgresQL.

01:14:07.280 --> 01:14:07.500
Right.

01:14:07.920 --> 01:14:08.720
However that's pronounced.

01:14:10.600 --> 01:14:12.260
Those are the four biggest ones.

01:14:12.380 --> 01:14:13.640
The two latter being

01:14:13.640 --> 01:14:15.980
free, open source,

01:14:17.360 --> 01:14:18.280
publicly available,

01:14:18.280 --> 01:14:20.360
and common stuff you see on the web a lot.

01:14:20.700 --> 01:14:21.960
Oracle being the big boy.

01:14:22.060 --> 01:14:23.320
That's the big expensive one.

01:14:23.460 --> 01:14:25.120
And SQL Server is not exactly cheap.

01:14:25.820 --> 01:14:26.580
And each one of them

01:14:26.580 --> 01:14:28.340
has their own SQL language

01:14:28.340 --> 01:14:29.780
to interface with it.

01:14:30.340 --> 01:14:30.820
So,

01:14:31.540 --> 01:14:33.360
there are certain common functions

01:14:33.360 --> 01:14:34.980
that people want to do to their data.

01:14:35.660 --> 01:14:36.660
Like dates.

01:14:36.940 --> 01:14:38.520
Dates and times is a great example

01:14:38.520 --> 01:14:39.380
because it's universal

01:14:39.380 --> 01:14:41.120
across almost any one of these.

01:14:42.520 --> 01:14:43.380
Date manipulation

01:14:43.380 --> 01:14:44.600
can be really messy

01:14:44.600 --> 01:14:45.340
and really tricky

01:14:45.340 --> 01:14:46.520
when you try to sit there

01:14:46.520 --> 01:14:48.140
and mess with system date

01:14:48.140 --> 01:14:49.040
and system time

01:14:49.040 --> 01:14:49.840
and time stamps

01:14:49.840 --> 01:14:50.660
and breaks down to

01:14:50.660 --> 01:14:52.220
fractions of a second.

01:14:53.080 --> 01:14:54.200
What most of these have done

01:14:54.200 --> 01:14:55.280
is they have functions,

01:14:55.440 --> 01:14:56.340
date time functions,

01:14:57.020 --> 01:14:58.140
that you can manipulate

01:14:58.140 --> 01:14:58.900
that are pre-written

01:14:58.900 --> 01:15:00.880
and you just pass parameters

01:15:00.880 --> 01:15:01.940
to and from them

01:15:01.940 --> 01:15:03.740
to get the format that you want.

01:15:04.620 --> 01:15:05.660
Just like you would do

01:15:05.660 --> 01:15:07.140
in any other object oriented language.

01:15:07.240 --> 01:15:07.820
In C++,

01:15:08.040 --> 01:15:08.680
you can get

01:15:08.680 --> 01:15:10.160
a pre-written function

01:15:10.160 --> 01:15:11.840
that you pass something to it

01:15:11.840 --> 01:15:13.580
and it returns you data

01:15:13.580 --> 01:15:14.300
in that format.

01:15:14.300 --> 01:15:16.640
Same thing with SQL.

01:15:17.220 --> 01:15:18.580
These come in

01:15:18.580 --> 01:15:20.300
two different types generally.

01:15:21.160 --> 01:15:21.980
Stored procedures

01:15:21.980 --> 01:15:22.760
and functions.

01:15:24.440 --> 01:15:24.880
Now,

01:15:25.140 --> 01:15:26.400
you would know more about

01:15:26.400 --> 01:15:26.860
I would

01:15:26.860 --> 01:15:28.420
than the web development part of it.

01:15:28.480 --> 01:15:29.060
Most of mine

01:15:29.060 --> 01:15:30.520
is all back-end programming.

01:15:30.740 --> 01:15:31.360
I don't know

01:15:31.360 --> 01:15:32.640
how often

01:15:32.640 --> 01:15:33.260
or if at all

01:15:33.260 --> 01:15:34.640
you use procedures

01:15:34.640 --> 01:15:35.240
or functions

01:15:35.240 --> 01:15:36.100
with Bell's Mind

01:15:36.100 --> 01:15:37.000
or any other stuff

01:15:37.000 --> 01:15:37.720
you've been developing.

01:15:37.900 --> 01:15:38.300
Is that...

01:15:38.300 --> 01:15:39.520
Well,

01:15:39.520 --> 01:15:40.140
that's what I was going to

01:15:40.140 --> 01:15:40.760
bring up before.

01:15:40.880 --> 01:15:41.660
It's funny that you mentioned

01:15:41.660 --> 01:15:42.700
people aren't really familiar

01:15:42.700 --> 01:15:43.440
what it means

01:15:43.440 --> 01:15:45.720
to do database programming

01:15:45.720 --> 01:15:46.480
and honestly,

01:15:47.040 --> 01:15:47.980
what I had been using

01:15:47.980 --> 01:15:49.300
for the longest time

01:15:49.300 --> 01:15:50.400
because I've done a couple

01:15:50.400 --> 01:15:51.520
of database projects before,

01:15:51.620 --> 01:15:52.560
some fairly large ones

01:15:52.560 --> 01:15:54.660
and I've always just done

01:15:54.660 --> 01:15:55.660
the selects

01:15:55.660 --> 01:15:56.120
and inserts

01:15:56.120 --> 01:15:56.700
and updates

01:15:56.700 --> 01:15:57.160
and deletes

01:15:57.160 --> 01:15:58.220
and stuff like that manually.

01:15:58.420 --> 01:15:59.080
That was just the way

01:15:59.080 --> 01:15:59.860
I was used to it

01:15:59.860 --> 01:16:01.660
because when I started

01:16:01.660 --> 01:16:02.980
with MySQL,

01:16:03.260 --> 01:16:04.240
at least as far as I knew,

01:16:04.580 --> 01:16:05.940
there wasn't any type of

01:16:05.940 --> 01:16:09.300
language for stored procedures.

01:16:09.500 --> 01:16:09.640
I mean,

01:16:09.720 --> 01:16:10.680
I knew I could use SQL

01:16:10.680 --> 01:16:11.680
but I didn't really know

01:16:11.680 --> 01:16:12.620
that SQL had all these

01:16:12.620 --> 01:16:13.280
extra functions

01:16:13.280 --> 01:16:14.440
like you said,

01:16:14.480 --> 01:16:15.320
to handle dates

01:16:15.320 --> 01:16:16.900
and to pad numbers

01:16:16.900 --> 01:16:18.940
and stuff like that.

01:16:19.060 --> 01:16:20.060
I didn't know all that stuff

01:16:20.060 --> 01:16:20.860
and just recently

01:16:20.860 --> 01:16:21.840
I've been finding that out

01:16:21.840 --> 01:16:23.120
so now I've been trying

01:16:23.120 --> 01:16:24.160
to migrate my code

01:16:24.160 --> 01:16:25.420
so that I can put more

01:16:25.420 --> 01:16:26.500
of the code in the database,

01:16:26.660 --> 01:16:27.160
have the database

01:16:27.160 --> 01:16:27.940
do more of the work

01:16:27.940 --> 01:16:29.220
instead of my PHP script

01:16:29.220 --> 01:16:30.420
and that itself

01:16:30.420 --> 01:16:31.460
helps with consistency.

01:16:31.780 --> 01:16:32.300
Like the database

01:16:32.300 --> 01:16:33.900
can do a lot of things

01:16:33.900 --> 01:16:35.000
to keep your data consistent

01:16:35.000 --> 01:16:37.440
when inserts are happening

01:16:37.440 --> 01:16:38.260
at the same time

01:16:38.260 --> 01:16:38.880
and it can make sure

01:16:38.880 --> 01:16:39.360
that they happen

01:16:39.360 --> 01:16:40.100
in a certain order

01:16:40.100 --> 01:16:40.860
and stuff like that.

01:16:41.360 --> 01:16:42.400
So as of right now,

01:16:42.440 --> 01:16:43.120
I don't really use

01:16:43.120 --> 01:16:43.660
stored procedures

01:16:43.660 --> 01:16:44.820
or functions very much

01:16:44.820 --> 01:16:46.060
but I plan on using them

01:16:46.060 --> 01:16:46.760
a lot in the future.

01:16:47.820 --> 01:16:48.180
Yeah,

01:16:48.260 --> 01:16:49.180
and some of them

01:16:49.180 --> 01:16:49.960
can be as simple

01:16:49.960 --> 01:16:50.720
as like you said,

01:16:50.840 --> 01:16:52.360
the LPAD or the RPAD

01:16:52.360 --> 01:16:53.240
is something you and I

01:16:53.240 --> 01:16:54.220
were talking about recently

01:16:54.220 --> 01:16:55.840
that's simply

01:16:55.840 --> 01:16:56.800
a formatting issue.

01:16:57.760 --> 01:16:58.000
You know,

01:16:58.080 --> 01:16:58.880
if you want to change

01:16:58.880 --> 01:17:00.100
a numeric field

01:17:00.100 --> 01:17:01.180
to a character field

01:17:01.180 --> 01:17:01.860
or vice versa

01:17:01.860 --> 01:17:02.940
or you want to,

01:17:02.940 --> 01:17:04.300
let's say,

01:17:04.660 --> 01:17:07.100
right justify a field

01:17:07.100 --> 01:17:08.600
instead of left justify.

01:17:09.340 --> 01:17:09.640
You know,

01:17:09.700 --> 01:17:10.220
you have reason

01:17:10.220 --> 01:17:10.900
to display it

01:17:10.900 --> 01:17:11.680
justified to the right

01:17:11.680 --> 01:17:12.480
for whatever reason.

01:17:12.960 --> 01:17:13.160
Well,

01:17:13.180 --> 01:17:14.080
that's not generally

01:17:14.080 --> 01:17:14.760
easy to do

01:17:14.760 --> 01:17:15.820
with basic SQL.

01:17:16.680 --> 01:17:16.900
Yeah.

01:17:17.520 --> 01:17:18.520
You can write

01:17:18.520 --> 01:17:20.580
SQL code to do it

01:17:20.580 --> 01:17:21.660
but it will take a while.

01:17:21.820 --> 01:17:22.540
It's really messy

01:17:22.540 --> 01:17:23.020
and tricky

01:17:23.020 --> 01:17:24.860
and it's usually customized.

01:17:25.100 --> 01:17:25.360
Well,

01:17:25.960 --> 01:17:26.820
you can write a function

01:17:26.820 --> 01:17:27.360
to do that

01:17:27.360 --> 01:17:28.840
but there are

01:17:28.840 --> 01:17:30.220
pre-written functions

01:17:30.220 --> 01:17:30.740
that ship

01:17:30.740 --> 01:17:31.420
and each one

01:17:31.420 --> 01:17:32.060
comes with,

01:17:32.360 --> 01:17:33.260
they're a little bit different

01:17:33.260 --> 01:17:34.200
but most of them

01:17:34.200 --> 01:17:35.060
are fairly consistent.

01:17:35.660 --> 01:17:36.680
There is an LPAD,

01:17:36.740 --> 01:17:38.040
RPAD in Oracle.

01:17:38.160 --> 01:17:39.040
That's where I've used it

01:17:39.040 --> 01:17:39.660
for in the past

01:17:39.660 --> 01:17:40.280
and apparently

01:17:40.280 --> 01:17:41.260
we looked this weekend

01:17:41.260 --> 01:17:42.720
and there's similar,

01:17:42.900 --> 01:17:43.720
the parameters

01:17:43.720 --> 01:17:44.560
are slightly different

01:17:44.560 --> 01:17:45.220
for Postgres

01:17:45.220 --> 01:17:47.900
but it accomplishes

01:17:47.900 --> 01:17:48.580
the same thing

01:17:48.580 --> 01:17:49.900
and the date functions

01:17:49.900 --> 01:17:51.360
are very similar as well.

01:17:51.460 --> 01:17:52.040
I'm finding,

01:17:52.200 --> 01:17:52.900
I'm now working

01:17:52.900 --> 01:17:53.960
in a SQL Server 2000

01:17:53.960 --> 01:17:54.640
environment

01:17:54.640 --> 01:17:55.680
and I'm finding

01:17:55.680 --> 01:17:56.220
that they,

01:17:56.500 --> 01:17:57.520
I don't like the way

01:17:57.520 --> 01:17:58.880
Microsoft is doing

01:17:58.880 --> 01:17:59.640
their date functions.

01:17:59.640 --> 01:18:00.200
They're really,

01:18:01.280 --> 01:18:02.120
I don't like them

01:18:02.120 --> 01:18:02.860
at all compared

01:18:02.860 --> 01:18:03.220
to Oracle.

01:18:03.340 --> 01:18:04.920
Oracle was so clean

01:18:04.920 --> 01:18:05.500
and nice

01:18:05.500 --> 01:18:06.340
and oh,

01:18:06.620 --> 01:18:07.280
their date functions

01:18:07.280 --> 01:18:08.220
were just beautiful

01:18:08.220 --> 01:18:09.980
and SQL Server 2000

01:18:09.980 --> 01:18:11.460
I am not impressed

01:18:11.460 --> 01:18:12.120
with their date

01:18:12.120 --> 01:18:13.920
formatting features.

01:18:14.060 --> 01:18:14.500
It's just,

01:18:15.500 --> 01:18:15.960
yuck

01:18:15.960 --> 01:18:17.140
and I have to use

01:18:17.140 --> 01:18:17.580
other,

01:18:18.240 --> 01:18:18.680
I have to use

01:18:18.680 --> 01:18:19.780
functions within functions

01:18:19.780 --> 01:18:20.660
to try to clean up

01:18:20.660 --> 01:18:21.540
the date to the format

01:18:21.540 --> 01:18:22.140
that I wanted

01:18:22.140 --> 01:18:23.280
and it's not cool

01:18:23.280 --> 01:18:23.580
at all.

01:18:23.660 --> 01:18:24.760
Using convert functions,

01:18:25.340 --> 01:18:25.940
date functions

01:18:25.940 --> 01:18:27.140
inside of convert functions,

01:18:27.400 --> 01:18:28.900
it's not pretty at all.

01:18:28.900 --> 01:18:30.060
I'm truncating data,

01:18:30.160 --> 01:18:30.840
it's really tacky

01:18:30.840 --> 01:18:31.400
if you ask me

01:18:31.400 --> 01:18:32.260
to get the job done.

01:18:32.880 --> 01:18:33.000
Yeah.

01:18:33.180 --> 01:18:33.480
But,

01:18:34.320 --> 01:18:34.940
these are all

01:18:34.940 --> 01:18:35.920
pre-written functions

01:18:35.920 --> 01:18:36.840
just like,

01:18:37.000 --> 01:18:37.280
again,

01:18:37.380 --> 01:18:37.700
I said,

01:18:37.840 --> 01:18:38.120
you know,

01:18:38.180 --> 01:18:39.240
reusable code with C.

01:18:39.300 --> 01:18:39.780
You can download

01:18:39.780 --> 01:18:40.620
someone else's already

01:18:40.620 --> 01:18:41.460
pre-written function

01:18:41.460 --> 01:18:42.960
that'll right justify

01:18:42.960 --> 01:18:43.400
something.

01:18:43.540 --> 01:18:44.060
You can do the same

01:18:44.060 --> 01:18:44.560
thing as SQL

01:18:44.560 --> 01:18:45.280
that usually ships

01:18:45.280 --> 01:18:46.060
with the database.

01:18:46.740 --> 01:18:47.900
At the same time,

01:18:48.380 --> 01:18:49.480
if it doesn't exist

01:18:49.480 --> 01:18:50.400
within the database

01:18:50.400 --> 01:18:52.220
or if there's something

01:18:52.220 --> 01:18:53.020
that you need to do

01:18:53.020 --> 01:18:53.760
specifically

01:18:53.760 --> 01:18:55.980
for your installation

01:18:55.980 --> 01:18:56.920
or your data

01:18:56.920 --> 01:18:58.320
and it's very important

01:18:58.320 --> 01:18:58.740
that you know

01:18:58.740 --> 01:18:59.200
and understand

01:18:59.200 --> 01:18:59.920
your data

01:18:59.920 --> 01:19:00.680
and the relationships

01:19:00.680 --> 01:19:01.680
between your data,

01:19:02.200 --> 01:19:03.680
understand your primary keys,

01:19:03.800 --> 01:19:04.960
how to build your foreign keys,

01:19:05.060 --> 01:19:05.800
stuff like that.

01:19:06.280 --> 01:19:07.260
It's very important

01:19:07.260 --> 01:19:07.860
that you know

01:19:07.860 --> 01:19:08.460
that kind of stuff

01:19:08.460 --> 01:19:09.080
and you can write

01:19:09.080 --> 01:19:10.000
your own functions

01:19:10.000 --> 01:19:11.760
and then you can in turn

01:19:11.760 --> 01:19:12.320
share them

01:19:12.320 --> 01:19:13.260
with other installations,

01:19:13.440 --> 01:19:13.800
other people

01:19:13.800 --> 01:19:14.780
that use similar software.

01:19:15.500 --> 01:19:16.160
For example,

01:19:16.320 --> 01:19:16.840
let's say,

01:19:17.360 --> 01:19:18.100
let's go back

01:19:18.100 --> 01:19:19.800
to the example

01:19:19.800 --> 01:19:20.540
with the states.

01:19:21.080 --> 01:19:22.440
You have a validation table

01:19:22.440 --> 01:19:23.640
of 50 states on it.

01:19:24.500 --> 01:19:24.720
Well,

01:19:25.040 --> 01:19:26.620
I'm writing a separate program

01:19:26.620 --> 01:19:27.360
over here somewhere

01:19:27.360 --> 01:19:28.120
usually called

01:19:28.120 --> 01:19:28.960
a stored procedure.

01:19:29.080 --> 01:19:29.840
I'm writing a program

01:19:29.840 --> 01:19:30.820
or a procedure over here

01:19:30.820 --> 01:19:32.180
that needs to,

01:19:32.640 --> 01:19:32.680
A,

01:19:33.660 --> 01:19:34.980
read a date from,

01:19:35.760 --> 01:19:36.080
say,

01:19:36.140 --> 01:19:37.480
a comma separated value file

01:19:37.480 --> 01:19:38.340
that someone sends me

01:19:38.340 --> 01:19:40.280
and then insert it

01:19:40.280 --> 01:19:41.040
into our database.

01:19:41.240 --> 01:19:41.360
Well,

01:19:41.400 --> 01:19:42.340
before I do that,

01:19:42.340 --> 01:19:43.600
I want to verify it

01:19:43.600 --> 01:19:44.840
on this validation table.

01:19:45.880 --> 01:19:47.340
I can write a function

01:19:47.340 --> 01:19:49.560
and reuse it

01:19:49.560 --> 01:19:50.500
over and over again

01:19:50.500 --> 01:19:52.120
save it as a name

01:19:52.120 --> 01:19:53.500
and simply call that function

01:19:53.500 --> 01:19:54.760
from within my program

01:19:54.760 --> 01:19:56.860
and since it's always

01:19:56.860 --> 01:19:57.920
the same with our table,

01:19:58.020 --> 01:19:59.440
the keys don't usually change.

01:19:59.540 --> 01:20:00.280
Once you've set a key

01:20:00.280 --> 01:20:00.780
in a database,

01:20:00.920 --> 01:20:01.660
you don't usually start

01:20:01.660 --> 01:20:02.880
moving stuff around very much.

01:20:03.200 --> 01:20:04.180
I can write a procedure

01:20:04.180 --> 01:20:05.100
that automates that

01:20:05.100 --> 01:20:06.320
and I simply tell it,

01:20:06.980 --> 01:20:08.000
go do the date validate

01:20:08.000 --> 01:20:10.040
or go do the state validation procedure

01:20:10.040 --> 01:20:10.840
and then come back

01:20:10.840 --> 01:20:11.620
if it's successful

01:20:11.620 --> 01:20:13.120
and if it's successful,

01:20:13.280 --> 01:20:14.720
I continue writing my program.

01:20:15.580 --> 01:20:15.660
So,

01:20:15.760 --> 01:20:16.480
if you write a lot

01:20:16.480 --> 01:20:17.420
of good procedures,

01:20:17.680 --> 01:20:18.880
your program can be as simple

01:20:18.880 --> 01:20:20.420
as a bunch of function calls

01:20:20.420 --> 01:20:23.680
within basic SQL statements

01:20:23.680 --> 01:20:26.000
and most programs

01:20:26.000 --> 01:20:27.120
in a database environment

01:20:27.120 --> 01:20:28.820
are stored procedures.

01:20:29.280 --> 01:20:30.600
They will do all these steps

01:20:30.600 --> 01:20:32.460
like take a data file

01:20:32.460 --> 01:20:33.000
that I get,

01:20:33.140 --> 01:20:33.640
let's say,

01:20:33.760 --> 01:20:35.300
not theory sends me a data file

01:20:35.300 --> 01:20:36.120
or let's say I send

01:20:36.120 --> 01:20:37.180
not theory a data file

01:20:37.180 --> 01:20:37.920
a better example.

01:20:38.680 --> 01:20:40.280
Let's say I find a text file

01:20:40.280 --> 01:20:41.020
on my hard drive

01:20:41.020 --> 01:20:42.440
of a scan of phone numbers

01:20:42.440 --> 01:20:44.220
that I made a week ago.

01:20:45.260 --> 01:20:46.640
Comma separated values,

01:20:46.640 --> 01:20:47.380
I tell him,

01:20:47.500 --> 01:20:48.580
here's the field names,

01:20:49.140 --> 01:20:50.340
here's the exact data

01:20:50.340 --> 01:20:51.000
that is in here,

01:20:51.260 --> 01:20:52.360
he knows his data

01:20:52.360 --> 01:20:53.120
and his tables,

01:20:53.500 --> 01:20:54.640
he can write a procedure

01:20:54.640 --> 01:20:56.460
that will parse through my file

01:20:56.460 --> 01:20:59.580
if my dates are in a different format

01:20:59.580 --> 01:21:00.860
than the dates in his table,

01:21:01.400 --> 01:21:02.980
he can call the date function

01:21:02.980 --> 01:21:04.340
with the proper parameters

01:21:04.340 --> 01:21:05.800
and it does the conversion work

01:21:05.800 --> 01:21:06.340
for him.

01:21:06.340 --> 01:21:08.180
He just has to tell it

01:21:08.180 --> 01:21:09.920
what format he needs

01:21:09.920 --> 01:21:11.720
and he writes that program

01:21:11.720 --> 01:21:12.320
and then,

01:21:12.780 --> 01:21:13.060
bam,

01:21:13.340 --> 01:21:14.020
execute it,

01:21:14.100 --> 01:21:14.580
it runs,

01:21:14.720 --> 01:21:15.460
it parses through,

01:21:15.580 --> 01:21:16.740
it validates everything

01:21:16.740 --> 01:21:17.960
and the result is

01:21:17.960 --> 01:21:19.120
you just loaded

01:21:19.120 --> 01:21:20.340
a thousand numbers

01:21:20.340 --> 01:21:21.660
or a million numbers

01:21:21.660 --> 01:21:22.520
into your database,

01:21:23.340 --> 01:21:23.860
clean,

01:21:24.460 --> 01:21:25.020
verified,

01:21:25.600 --> 01:21:27.100
data integrity intact

01:21:27.100 --> 01:21:30.160
with no duplicates

01:21:30.160 --> 01:21:32.340
and absolute clean table

01:21:32.960 --> 01:21:34.280
that's just as clean at the end

01:21:34.280 --> 01:21:35.200
as it was at the beginning

01:21:35.200 --> 01:21:37.100
and that is the heart

01:21:37.100 --> 01:21:38.300
of database programming.

01:21:41.760 --> 01:21:42.280
Now,

01:21:42.840 --> 01:21:44.560
I wanted to go through

01:21:44.560 --> 01:21:46.380
some of the specific ones

01:21:46.380 --> 01:21:47.840
but,

01:21:48.280 --> 01:21:49.720
I'm going to skip

01:21:49.720 --> 01:21:50.840
a couple of these,

01:21:50.980 --> 01:21:52.120
I'll do a mini review

01:21:52.120 --> 01:21:53.620
on SQL Server 2000

01:21:53.620 --> 01:21:55.680
on an upcoming show

01:21:55.680 --> 01:21:57.000
because I've been learning that

01:21:57.000 --> 01:21:58.620
and dealing with that recently

01:21:58.620 --> 01:22:00.040
so I'm going to save that

01:22:00.040 --> 01:22:00.880
for another show.

01:22:01.080 --> 01:22:02.400
I also worked in Oracle,

01:22:02.500 --> 01:22:03.480
I was in an Oracle shop

01:22:03.480 --> 01:22:04.060
for a while

01:22:04.060 --> 01:22:05.580
and I'm going to skip

01:22:05.580 --> 01:22:06.000
that one.

01:22:06.060 --> 01:22:06.620
These are the two

01:22:06.620 --> 01:22:07.720
commercial options.

01:22:08.320 --> 01:22:09.080
We've got about

01:22:09.080 --> 01:22:10.360
five or six minutes left

01:22:10.360 --> 01:22:11.160
and the one thing

01:22:11.160 --> 01:22:12.020
that I do want to end

01:22:12.020 --> 01:22:12.460
this show

01:22:12.460 --> 01:22:13.400
and make sure we emphasize

01:22:13.400 --> 01:22:15.400
is the open source

01:22:15.400 --> 01:22:16.260
alternatives that are

01:22:16.260 --> 01:22:16.740
out there,

01:22:18.040 --> 01:22:19.140
the free alternatives

01:22:19.140 --> 01:22:19.960
that are out there

01:22:19.960 --> 01:22:20.680
and that is

01:22:20.680 --> 01:22:21.620
MySQL,

01:22:21.860 --> 01:22:21.960
yeah,

01:22:22.100 --> 01:22:22.860
I corrected myself,

01:22:23.000 --> 01:22:23.620
MySQL

01:22:23.620 --> 01:22:24.900
and Postgres SQL,

01:22:25.040 --> 01:22:25.880
Postgres SQL,

01:22:26.240 --> 01:22:26.860
satellite panacea.

01:22:26.860 --> 01:22:29.420
Now,

01:22:29.840 --> 01:22:31.200
you and I have been

01:22:31.200 --> 01:22:31.820
talking lately

01:22:31.820 --> 01:22:32.400
and I'm becoming,

01:22:32.540 --> 01:22:33.220
you've been convinced

01:22:33.220 --> 01:22:33.800
for a while,

01:22:34.360 --> 01:22:35.620
but I've been becoming

01:22:35.620 --> 01:22:36.460
more and more convinced

01:22:36.460 --> 01:22:37.260
as I do research

01:22:37.260 --> 01:22:38.320
on Postgres

01:22:38.320 --> 01:22:40.160
that it's really,

01:22:40.520 --> 01:22:41.640
really every bit

01:22:41.640 --> 01:22:42.180
as powerful

01:22:42.180 --> 01:22:42.860
as Oracle

01:22:42.860 --> 01:22:44.020
and some of the other options.

01:22:44.120 --> 01:22:44.520
Almost,

01:22:44.760 --> 01:22:45.000
well,

01:22:45.980 --> 01:22:46.840
maybe more so,

01:22:46.960 --> 01:22:47.260
honestly.

01:22:48.000 --> 01:22:48.340
Really?

01:22:48.740 --> 01:22:49.560
I think so.

01:22:49.720 --> 01:22:51.100
Everything that I've been

01:22:51.100 --> 01:22:51.980
able to do in Oracle,

01:22:52.400 --> 01:22:53.560
I've seen an equivalent

01:22:53.560 --> 01:22:54.680
for in Postgres

01:22:54.680 --> 01:22:55.360
so far.

01:22:55.360 --> 01:22:55.800
Now,

01:22:55.860 --> 01:22:56.160
granted,

01:22:56.560 --> 01:22:57.320
you're developing

01:22:57.320 --> 01:22:58.140
more in Postgres

01:22:58.140 --> 01:22:58.700
than I am,

01:22:58.760 --> 01:22:59.160
unfortunately.

01:22:59.660 --> 01:23:00.700
I wish I could do more

01:23:00.700 --> 01:23:01.480
and maybe I can

01:23:01.480 --> 01:23:02.780
help out in the site

01:23:02.780 --> 01:23:03.180
in the future

01:23:03.180 --> 01:23:03.620
with some of that

01:23:03.620 --> 01:23:04.200
when I get time,

01:23:04.340 --> 01:23:05.460
but so far,

01:23:05.540 --> 01:23:06.500
everything I've looked for

01:23:06.500 --> 01:23:07.760
and I've been looking

01:23:07.760 --> 01:23:08.680
lately because I know

01:23:08.680 --> 01:23:09.740
that you think

01:23:09.740 --> 01:23:10.660
very highly of it.

01:23:11.180 --> 01:23:11.540
Yeah.

01:23:11.840 --> 01:23:13.440
It's got everything

01:23:13.440 --> 01:23:14.060
that I've seen

01:23:14.060 --> 01:23:14.780
offered in Oracle

01:23:14.780 --> 01:23:16.380
so far.

01:23:17.360 --> 01:23:17.760
Yeah,

01:23:17.820 --> 01:23:18.200
I actually,

01:23:18.300 --> 01:23:19.520
I used to be a MySQL nut.

01:23:19.600 --> 01:23:20.300
I used to love it,

01:23:20.460 --> 01:23:22.220
but I ran into

01:23:22.220 --> 01:23:23.120
one database project

01:23:23.120 --> 01:23:23.900
that I was working on

01:23:23.900 --> 01:23:24.420
that MySQL

01:23:24.420 --> 01:23:25.340
literally could not

01:23:25.340 --> 01:23:25.960
handle it.

01:23:26.580 --> 01:23:27.380
And if anybody wants

01:23:27.380 --> 01:23:28.340
to look up the data set,

01:23:28.480 --> 01:23:29.800
it's a map data set.

01:23:29.900 --> 01:23:30.720
It's called Tiger

01:23:30.720 --> 01:23:32.260
and it's from the USGS,

01:23:32.380 --> 01:23:33.680
United States Geological Survey.

01:23:33.780 --> 01:23:34.380
They have a database

01:23:34.380 --> 01:23:35.060
called Tiger

01:23:35.060 --> 01:23:37.120
that has every street

01:23:37.120 --> 01:23:38.880
in the entire US

01:23:38.880 --> 01:23:41.180
and you can download it.

01:23:41.260 --> 01:23:42.160
It's like maybe,

01:23:43.100 --> 01:23:43.600
I want to say

01:23:43.600 --> 01:23:44.900
it's like four gigabytes

01:23:44.900 --> 01:23:45.600
of text

01:23:45.600 --> 01:23:46.940
or something,

01:23:47.060 --> 01:23:47.540
maybe five,

01:23:47.660 --> 01:23:47.780
no,

01:23:47.880 --> 01:23:48.320
five giga,

01:23:48.360 --> 01:23:49.320
it's about five gigabytes

01:23:49.320 --> 01:23:50.020
of BZIFs

01:23:50.020 --> 01:23:50.860
or GZIFs.

01:23:51.300 --> 01:23:52.260
So when you expand it,

01:23:52.320 --> 01:23:52.920
it's huge

01:23:52.920 --> 01:23:53.940
and I wanted to turn that

01:23:53.940 --> 01:23:55.000
and I wanted to put that

01:23:55.000 --> 01:23:55.740
into MySQL

01:23:55.740 --> 01:23:57.400
and be able to draw maps.

01:23:57.480 --> 01:23:58.000
Like I could say,

01:23:58.100 --> 01:23:58.200
okay,

01:23:58.260 --> 01:23:58.800
draw a map

01:23:58.800 --> 01:24:01.240
of this region

01:24:01.240 --> 01:24:01.840
and it would draw

01:24:01.840 --> 01:24:02.320
all the streets

01:24:02.320 --> 01:24:02.860
in that area.

01:24:03.620 --> 01:24:04.560
Tried doing it in MySQL,

01:24:05.100 --> 01:24:06.120
MySQL crapped out

01:24:06.120 --> 01:24:06.720
in a big time.

01:24:07.220 --> 01:24:08.060
So I started looking around

01:24:08.060 --> 01:24:08.740
and I found Postgres.

01:24:08.980 --> 01:24:09.500
I put the data

01:24:09.500 --> 01:24:10.100
into Postgres.

01:24:10.560 --> 01:24:11.460
Postgres handled it

01:24:11.460 --> 01:24:12.300
no problem.

01:24:12.860 --> 01:24:13.720
Postgres can deal

01:24:13.720 --> 01:24:14.540
with huge data sets

01:24:14.540 --> 01:24:15.360
and when I was done

01:24:15.360 --> 01:24:17.060
importing all these tables

01:24:17.060 --> 01:24:19.220
and creating all the indexes,

01:24:19.820 --> 01:24:20.840
the database had,

01:24:21.020 --> 01:24:22.760
in just one table,

01:24:22.840 --> 01:24:23.660
it had multiple tables.

01:24:24.240 --> 01:24:25.100
The largest table

01:24:25.100 --> 01:24:27.640
had 147 million records

01:24:27.640 --> 01:24:29.620
and the index

01:24:29.620 --> 01:24:30.740
was two gigabytes.

01:24:32.000 --> 01:24:33.480
So just one index

01:24:33.480 --> 01:24:34.020
was two gigabytes.

01:24:34.220 --> 01:24:35.160
So the whole data set

01:24:35.160 --> 01:24:35.940
was like 36

01:24:35.940 --> 01:24:37.420
or 38 gigabytes total

01:24:37.420 --> 01:24:38.820
and I ran,

01:24:39.060 --> 01:24:39.280
you know,

01:24:39.320 --> 01:24:40.100
I generated maps

01:24:40.100 --> 01:24:40.700
all the time

01:24:40.700 --> 01:24:41.160
and Postgres

01:24:41.160 --> 01:24:42.820
had no problem with it.

01:24:43.540 --> 01:24:44.340
So that to me

01:24:44.340 --> 01:24:45.160
sold me right there

01:24:45.160 --> 01:24:46.140
and ever since

01:24:46.140 --> 01:24:46.820
I've just found out

01:24:46.820 --> 01:24:47.420
more features

01:24:47.420 --> 01:24:50.220
and I'm just even more

01:24:50.220 --> 01:24:50.660
in love with it

01:24:50.660 --> 01:24:52.120
than I was initially.

01:24:52.920 --> 01:24:53.360
Yeah,

01:24:53.520 --> 01:24:55.540
I can't agree more.

01:24:55.660 --> 01:24:56.560
I think when you've got

01:24:56.560 --> 01:24:58.520
a database management system

01:24:58.520 --> 01:24:59.740
that's every bit

01:24:59.740 --> 01:25:01.020
as powerful as Oracle

01:25:01.020 --> 01:25:01.860
and free,

01:25:02.980 --> 01:25:03.220
I mean,

01:25:03.260 --> 01:25:03.920
I think we all know

01:25:03.920 --> 01:25:05.400
Oracle is a gigantic company.

01:25:05.760 --> 01:25:06.900
It's not a cheap product.

01:25:06.900 --> 01:25:08.020
It's not a cheap system

01:25:08.020 --> 01:25:10.100
and you can get something

01:25:10.100 --> 01:25:10.880
with near functionality

01:25:10.880 --> 01:25:11.700
for free.

01:25:12.420 --> 01:25:13.380
That's fantastic.

01:25:13.700 --> 01:25:13.840
Yeah,

01:25:13.840 --> 01:25:14.460
you can't go wrong.

01:25:14.540 --> 01:25:15.080
The last company

01:25:15.080 --> 01:25:15.620
I worked with,

01:25:15.780 --> 01:25:16.620
they had Oracle

01:25:16.620 --> 01:25:17.540
do some work for them

01:25:17.540 --> 01:25:18.120
and the bill

01:25:18.120 --> 01:25:18.740
at the end of it

01:25:18.740 --> 01:25:19.320
ended up being

01:25:19.320 --> 01:25:19.940
somewhere around

01:25:19.940 --> 01:25:20.480
$10 million.

01:25:22.240 --> 01:25:22.640
Yeah.

01:25:23.000 --> 01:25:24.120
It was a huge project.

01:25:24.360 --> 01:25:24.980
Don't get me wrong.

01:25:25.100 --> 01:25:25.320
Oracle,

01:25:25.540 --> 01:25:26.440
I don't know that Oracle

01:25:26.440 --> 01:25:27.400
really ripped them off

01:25:27.400 --> 01:25:28.220
because the project

01:25:28.220 --> 01:25:29.360
was absolutely enormous

01:25:29.360 --> 01:25:30.660
but it was still

01:25:30.660 --> 01:25:31.140
$10 million.

01:25:31.580 --> 01:25:31.960
I don't,

01:25:33.160 --> 01:25:33.980
that's a lot of money.

01:25:34.220 --> 01:25:34.860
You couldn't spend

01:25:34.860 --> 01:25:35.180
that much

01:25:35.180 --> 01:25:35.960
on a Postgres installation,

01:25:35.960 --> 01:25:36.720
I'm sure.

01:25:37.120 --> 01:25:37.440
You know,

01:25:37.480 --> 01:25:38.460
even with considering

01:25:38.460 --> 01:25:39.280
like putting hundreds

01:25:39.280 --> 01:25:40.200
of developers on it,

01:25:41.000 --> 01:25:41.640
you couldn't spend

01:25:41.640 --> 01:25:42.160
that much money.

01:25:42.220 --> 01:25:42.340
Yeah,

01:25:42.380 --> 01:25:43.340
and that's the other thing

01:25:43.340 --> 01:25:44.500
is I was a little bit

01:25:44.500 --> 01:25:45.660
concerned that I'd never

01:25:45.660 --> 01:25:47.120
used Microsoft SQL Server

01:25:47.120 --> 01:25:47.960
2000 before.

01:25:48.420 --> 01:25:49.860
I'm adapting pretty damn well.

01:25:49.960 --> 01:25:50.240
Actually,

01:25:50.340 --> 01:25:51.480
if you can work with one

01:25:51.480 --> 01:25:52.140
and you understand

01:25:52.140 --> 01:25:52.940
your fundamentals

01:25:52.940 --> 01:25:54.560
and the basics

01:25:54.560 --> 01:25:55.260
and some of the stuff

01:25:55.260 --> 01:25:56.040
we talked about tonight,

01:25:56.160 --> 01:25:56.440
I mean,

01:25:56.620 --> 01:25:57.640
listen back to it again

01:25:57.640 --> 01:25:58.160
if you have to,

01:25:58.160 --> 01:26:00.280
but basic database features

01:26:00.280 --> 01:26:01.020
and concepts,

01:26:01.500 --> 01:26:02.860
I had no problems adapting.

01:26:03.260 --> 01:26:03.760
So far,

01:26:03.820 --> 01:26:04.320
so good.

01:26:05.220 --> 01:26:05.340
So,

01:26:05.600 --> 01:26:06.520
and the same thing

01:26:06.520 --> 01:26:07.240
as I'm looking

01:26:07.240 --> 01:26:07.960
into Postgres,

01:26:08.040 --> 01:26:08.740
I'm finding a lot

01:26:08.740 --> 01:26:09.300
of similarities.

01:26:09.780 --> 01:26:09.800
So,

01:26:10.920 --> 01:26:12.360
we're going to have

01:26:12.360 --> 01:26:12.860
to wrap it up

01:26:12.860 --> 01:26:13.240
because we are

01:26:13.240 --> 01:26:14.120
dead out of time.

01:26:14.520 --> 01:26:14.700
Oh.

01:26:15.540 --> 01:26:16.280
But there's,

01:26:16.360 --> 01:26:17.300
we can spend another,

01:26:17.400 --> 01:26:18.100
hold another show

01:26:18.100 --> 01:26:18.420
on this

01:26:18.420 --> 01:26:18.820
and we will

01:26:18.820 --> 01:26:20.220
sometime in the future

01:26:20.220 --> 01:26:21.840
coming back

01:26:21.840 --> 01:26:22.400
and looking at

01:26:22.400 --> 01:26:22.980
some specifics

01:26:22.980 --> 01:26:23.600
of each one

01:26:23.600 --> 01:26:24.240
and comparing them.

01:26:24.240 --> 01:26:25.040
because there's

01:26:25.040 --> 01:26:25.420
nothing wrong

01:26:25.420 --> 01:26:25.860
with Oracle.

01:26:26.320 --> 01:26:27.020
I'm just saying

01:26:27.020 --> 01:26:27.860
it's pricey,

01:26:27.900 --> 01:26:28.140
you know.

01:26:28.260 --> 01:26:29.020
It's a good product

01:26:29.020 --> 01:26:29.860
but it's pricey.

01:26:30.300 --> 01:26:30.460
Yeah,

01:26:30.500 --> 01:26:30.720
I think,

01:26:30.800 --> 01:26:31.320
I guess in a couple

01:26:31.320 --> 01:26:31.920
weeks when we have

01:26:31.920 --> 01:26:32.680
more time to do this

01:26:32.680 --> 01:26:32.880
again,

01:26:32.960 --> 01:26:33.400
I'll have a lot

01:26:33.400 --> 01:26:34.020
more experience

01:26:34.020 --> 01:26:34.680
because my,

01:26:34.820 --> 01:26:35.300
my actually,

01:26:36.060 --> 01:26:36.660
I'm using,

01:26:36.780 --> 01:26:37.900
I'm using Postgres

01:26:37.900 --> 01:26:38.740
stuff for my business

01:26:38.740 --> 01:26:39.800
now and I'm going

01:26:39.800 --> 01:26:40.260
to have to learn

01:26:40.260 --> 01:26:41.080
a lot of store

01:26:41.080 --> 01:26:41.440
procedures,

01:26:41.580 --> 01:26:42.040
a lot of functions,

01:26:42.140 --> 01:26:42.700
all that stuff.

01:26:43.260 --> 01:26:43.780
I'm going to be

01:26:43.780 --> 01:26:45.500
doing it 24 hours a day.

01:26:45.860 --> 01:26:45.880
So,

01:26:46.220 --> 01:26:46.880
you'll know a lot

01:26:46.880 --> 01:26:47.340
more in a couple

01:26:47.340 --> 01:26:47.660
of weeks.

01:26:47.820 --> 01:26:48.900
My instant messenger

01:26:48.900 --> 01:26:49.840
is up all day,

01:26:49.960 --> 01:26:50.200
so,

01:26:50.940 --> 01:26:51.860
I've got the numbers.

01:26:51.860 --> 01:26:54.100
By all means,

01:26:54.200 --> 01:26:54.640
feel free.

01:26:55.360 --> 01:26:55.720
Now,

01:26:55.800 --> 01:26:56.640
let's wrap up here.

01:26:56.720 --> 01:26:57.140
I've got a couple

01:26:57.140 --> 01:26:57.920
quick shouts.

01:26:58.580 --> 01:26:59.480
I'm not sure if I

01:26:59.480 --> 01:27:00.100
mentioned this on the

01:27:00.100 --> 01:27:00.540
show before,

01:27:00.640 --> 01:27:01.560
but I just wanted

01:27:01.560 --> 01:27:02.140
to give one more

01:27:02.140 --> 01:27:03.340
shout to Rax

01:27:03.340 --> 01:27:04.920
and the rest,

01:27:05.060 --> 01:27:05.660
many of the others.

01:27:05.760 --> 01:27:06.400
I single out Rax

01:27:06.400 --> 01:27:06.860
because he's my

01:27:06.860 --> 01:27:07.200
homeboy,

01:27:07.620 --> 01:27:08.720
but all the guys

01:27:08.720 --> 01:27:09.160
that were working

01:27:09.160 --> 01:27:10.020
on the AV stuff

01:27:10.020 --> 01:27:10.320
at Hope.

01:27:10.540 --> 01:27:10.980
At Hope,

01:27:10.980 --> 01:27:11.460
when I put on

01:27:11.460 --> 01:27:12.200
my presentation,

01:27:13.080 --> 01:27:14.620
I walked up there,

01:27:14.700 --> 01:27:15.400
they had everything

01:27:15.400 --> 01:27:15.860
ready,

01:27:16.260 --> 01:27:17.240
they had it all set,

01:27:17.420 --> 01:27:18.680
easy to go,

01:27:18.800 --> 01:27:19.820
it took 30 seconds,

01:27:19.920 --> 01:27:20.420
I was plugged in,

01:27:20.460 --> 01:27:20.960
ready to give my

01:27:20.960 --> 01:27:21.340
presentation.

01:27:21.860 --> 01:27:22.680
These guys were

01:27:22.680 --> 01:27:23.320
sitting up behind

01:27:23.320 --> 01:27:24.660
the cameras the

01:27:24.660 --> 01:27:25.360
whole time,

01:27:25.440 --> 01:27:26.020
making sure the

01:27:26.020 --> 01:27:26.660
sound was right,

01:27:26.740 --> 01:27:27.140
making sure the

01:27:27.140 --> 01:27:27.740
video was right,

01:27:28.200 --> 01:27:30.000
and I,

01:27:30.120 --> 01:27:30.360
for one,

01:27:30.420 --> 01:27:31.060
appreciated that

01:27:31.060 --> 01:27:31.340
because,

01:27:31.480 --> 01:27:31.740
to me,

01:27:32.140 --> 01:27:32.980
that was probably

01:27:32.980 --> 01:27:33.600
really boring.

01:27:34.460 --> 01:27:34.620
I mean,

01:27:34.660 --> 01:27:34.780
yeah,

01:27:34.800 --> 01:27:35.240
I guess they got

01:27:35.240 --> 01:27:36.660
to watch the

01:27:36.660 --> 01:27:37.400
presentations and

01:27:37.400 --> 01:27:37.620
stuff,

01:27:37.760 --> 01:27:38.840
but that was

01:27:38.840 --> 01:27:39.400
really cool of

01:27:39.400 --> 01:27:39.540
them,

01:27:39.580 --> 01:27:40.020
and I don't know

01:27:40.020 --> 01:27:40.960
if they got any

01:27:40.960 --> 01:27:41.320
credit.

01:27:41.580 --> 01:27:42.320
I really wish

01:27:42.320 --> 01:27:44.780
people appreciated

01:27:44.780 --> 01:27:45.200
that more,

01:27:45.320 --> 01:27:45.940
so I just wanted

01:27:45.940 --> 01:27:46.420
to give a shout

01:27:46.420 --> 01:27:47.000
out to them,

01:27:47.840 --> 01:27:48.140
and,

01:27:48.220 --> 01:27:48.680
of course,

01:27:48.780 --> 01:27:49.020
Rax,

01:27:49.080 --> 01:27:49.480
because he's

01:27:49.480 --> 01:27:50.460
just awesome.

01:27:50.460 --> 01:27:51.680
Yeah,

01:27:51.720 --> 01:27:52.220
I will second

01:27:52.220 --> 01:27:52.580
the shout

01:27:52.580 --> 01:27:53.160
to Rax.

01:27:53.700 --> 01:27:54.360
Rax is the

01:27:54.360 --> 01:27:54.540
man.

01:27:56.880 --> 01:27:57.140
Hmm,

01:27:57.280 --> 01:27:57.760
let me think,

01:27:57.780 --> 01:27:58.100
who do I want

01:27:58.100 --> 01:27:58.460
to shout out?

01:27:58.500 --> 01:27:58.980
The guys I met

01:27:58.980 --> 01:27:59.520
at DEFCON,

01:27:59.660 --> 01:28:00.440
some people are

01:28:00.440 --> 01:28:01.280
particularly media

01:28:01.280 --> 01:28:01.520
shy,

01:28:01.640 --> 01:28:02.140
so I will not

01:28:02.140 --> 01:28:02.580
mention their

01:28:02.580 --> 01:28:02.860
names,

01:28:03.420 --> 01:28:03.540
but,

01:28:03.620 --> 01:28:04.640
yeah,

01:28:04.740 --> 01:28:05.200
shouts to them,

01:28:05.260 --> 01:28:05.520
definitely,

01:28:05.740 --> 01:28:06.400
they were awesome,

01:28:06.500 --> 01:28:06.860
I had a great

01:28:06.860 --> 01:28:07.600
time at DEFCON.

01:28:08.980 --> 01:28:09.280
Thanks,

01:28:09.360 --> 01:28:09.920
shouts to

01:28:09.920 --> 01:28:11.000
CodeMonkey,

01:28:11.160 --> 01:28:12.080
next month I

01:28:12.080 --> 01:28:12.600
will be at the

01:28:12.600 --> 01:28:13.420
2600 meeting,

01:28:13.500 --> 01:28:14.080
unless something

01:28:14.080 --> 01:28:14.860
really terrible

01:28:14.860 --> 01:28:15.200
happens.

01:28:15.520 --> 01:28:15.840
Awesome.

01:28:17.120 --> 01:28:17.480
Yeah,

01:28:17.600 --> 01:28:17.740
yeah,

01:28:17.760 --> 01:28:18.120
I wanted to

01:28:18.120 --> 01:28:18.380
go this

01:28:18.380 --> 01:28:18.620
month,

01:28:18.740 --> 01:28:18.900
but,

01:28:19.420 --> 01:28:19.640
you know,

01:28:19.680 --> 01:28:20.020
it's a long

01:28:20.020 --> 01:28:20.320
story,

01:28:20.440 --> 01:28:20.660
and I don't

01:28:20.660 --> 01:28:21.240
think CodeMonkey

01:28:21.240 --> 01:28:21.580
went this

01:28:21.580 --> 01:28:22.020
month anyway,

01:28:22.200 --> 01:28:22.680
so it doesn't

01:28:22.680 --> 01:28:23.040
really matter.

01:28:23.160 --> 01:28:23.760
Awesome is my

01:28:23.760 --> 01:28:24.160
word of the

01:28:24.160 --> 01:28:24.360
show.

01:28:25.080 --> 01:28:25.440
Awesome.

01:28:26.500 --> 01:28:27.000
I think,

01:28:27.120 --> 01:28:27.680
shout out to

01:28:27.680 --> 01:28:28.060
everybody who

01:28:28.060 --> 01:28:29.040
submitted numbers,

01:28:29.640 --> 01:28:29.880
I mean,

01:28:29.920 --> 01:28:30.500
not just the top

01:28:30.500 --> 01:28:30.760
guys,

01:28:30.880 --> 01:28:31.020
like,

01:28:31.200 --> 01:28:31.700
everybody who

01:28:31.700 --> 01:28:32.300
submitted numbers,

01:28:32.720 --> 01:28:33.460
I really appreciate

01:28:33.460 --> 01:28:33.680
it,

01:28:34.300 --> 01:28:34.900
keep the emails

01:28:34.900 --> 01:28:35.220
coming,

01:28:35.680 --> 01:28:35.920
you know,

01:28:36.020 --> 01:28:36.740
give me suggestions,

01:28:37.700 --> 01:28:38.160
and,

01:28:38.240 --> 01:28:39.680
damn,

01:28:39.740 --> 01:28:40.320
that's all I can

01:28:40.320 --> 01:28:40.880
think of right

01:28:40.880 --> 01:28:41.080
now,

01:28:41.140 --> 01:28:41.580
I know there's

01:28:41.580 --> 01:28:42.040
somebody that I'm

01:28:42.040 --> 01:28:42.280
missing,

01:28:42.420 --> 01:28:42.560
but.

01:28:42.560 --> 01:28:43.720
I'll also

01:28:43.720 --> 01:28:44.220
add a shout

01:28:44.220 --> 01:28:45.580
out to one

01:28:45.580 --> 01:28:45.980
of the guys

01:28:45.980 --> 01:28:46.460
down here in

01:28:46.460 --> 01:28:46.800
Miami,

01:28:47.060 --> 01:28:47.680
a guy I met

01:28:47.680 --> 01:28:47.980
recently,

01:28:48.060 --> 01:28:48.320
he's really

01:28:48.320 --> 01:28:48.620
cool,

01:28:48.760 --> 01:28:49.000
and that's

01:28:49.000 --> 01:28:49.580
El Diablo,

01:28:50.320 --> 01:28:50.880
shout out to

01:28:50.880 --> 01:28:51.040
him,

01:28:51.080 --> 01:28:51.300
I'm going to

01:28:51.300 --> 01:28:51.600
be working

01:28:51.600 --> 01:28:52.140
with him on

01:28:52.140 --> 01:28:53.300
some upcoming

01:28:53.300 --> 01:28:54.060
projects and

01:28:54.060 --> 01:28:54.540
some upcoming

01:28:54.540 --> 01:28:54.920
things,

01:28:55.020 --> 01:28:55.520
so shouts to

01:28:55.520 --> 01:28:55.700
him.

01:28:57.040 --> 01:28:57.440
And,

01:28:57.540 --> 01:28:59.160
email us at

01:28:59.160 --> 01:28:59.460
radio at

01:28:59.460 --> 01:29:00.440
binrev.com,

01:29:00.660 --> 01:29:01.600
article submissions

01:29:01.600 --> 01:29:02.000
come to

01:29:02.000 --> 01:29:02.500
articles at

01:29:02.500 --> 01:29:03.520
binrev.com,

01:29:04.120 --> 01:29:05.380
and we're

01:29:05.380 --> 01:29:05.760
going to close

01:29:05.760 --> 01:29:06.080
out with

01:29:06.080 --> 01:29:06.620
another track

01:29:06.620 --> 01:29:07.200
from MC

01:29:07.200 --> 01:29:07.800
Chris,

01:29:08.400 --> 01:29:08.940
and that's

01:29:08.940 --> 01:29:09.180
going to do

01:29:09.180 --> 01:29:09.480
it for the

01:29:09.480 --> 01:29:09.900
show.

01:29:11.320 --> 01:29:12.220
Once again,

01:29:12.560 --> 01:29:14.240
thank you,

01:29:14.640 --> 01:29:15.220
not theory,

01:29:15.360 --> 01:29:15.820
for being on

01:29:15.820 --> 01:29:16.140
the show.

01:29:16.800 --> 01:29:17.420
Thank you for

01:29:17.420 --> 01:29:17.700
having me.

01:29:17.700 --> 01:29:18.500
Always a

01:29:18.500 --> 01:29:18.760
pleasure,

01:29:18.920 --> 01:29:19.320
even though we

01:29:19.320 --> 01:29:19.980
joke around a

01:29:19.980 --> 01:29:20.200
lot.

01:29:21.120 --> 01:29:21.620
That's what's

01:29:21.620 --> 01:29:21.960
great about

01:29:21.960 --> 01:29:22.360
having you on

01:29:22.360 --> 01:29:22.680
the show.

01:29:22.960 --> 01:29:23.420
You and I,

01:29:23.500 --> 01:29:24.000
I think we've

01:29:24.000 --> 01:29:24.600
got that sense

01:29:24.600 --> 01:29:25.100
of humor thing

01:29:25.100 --> 01:29:25.580
where we know

01:29:25.580 --> 01:29:26.260
how far we can

01:29:26.260 --> 01:29:26.880
push each other

01:29:26.880 --> 01:29:27.760
and make each

01:29:27.760 --> 01:29:28.240
other laugh,

01:29:28.340 --> 01:29:28.940
so I think that

01:29:28.940 --> 01:29:29.460
works out really

01:29:29.460 --> 01:29:29.760
cool.

01:29:30.400 --> 01:29:30.920
Speaking of that

01:29:30.920 --> 01:29:31.520
sense of humor,

01:29:31.720 --> 01:29:32.040
shout out to

01:29:32.040 --> 01:29:32.820
Obfuscated again,

01:29:32.900 --> 01:29:33.320
he's the man.

01:29:33.460 --> 01:29:33.680
Yeah,

01:29:33.860 --> 01:29:34.100
yeah,

01:29:34.220 --> 01:29:34.680
he had me

01:29:34.680 --> 01:29:35.380
rolling on that,

01:29:35.560 --> 01:29:37.320
and I guess

01:29:37.320 --> 01:29:38.940
until we master

01:29:38.940 --> 01:29:39.660
the albatross,

01:29:39.760 --> 01:29:40.080
that's going to

01:29:40.080 --> 01:29:40.440
have to do it

01:29:40.440 --> 01:29:40.900
for the show,

01:29:40.900 --> 01:29:42.760
so I think

01:29:42.760 --> 01:29:43.340
we should tell

01:29:43.340 --> 01:29:44.100
everybody that

01:29:44.100 --> 01:29:44.780
we'll see them

01:29:44.780 --> 01:29:45.880
next week,

01:29:46.000 --> 01:29:46.900
same hack time.

01:29:47.440 --> 01:29:48.460
Same hack channel.

01:30:05.140 --> 01:30:06.120
This one goes

01:30:06.120 --> 01:30:06.700
out to all the

01:30:06.700 --> 01:30:07.200
cuties in the

01:30:07.200 --> 01:30:07.400
crowd,

01:30:07.480 --> 01:30:07.920
walk the kitty

01:30:07.920 --> 01:30:08.200
corner,

01:30:08.460 --> 01:30:09.000
with the itty

01:30:09.000 --> 01:30:09.500
bitty box,

01:30:09.580 --> 01:30:10.300
scoping out the

01:30:10.300 --> 01:30:10.520
window,

01:30:10.520 --> 01:30:11.060
waxing wise

01:30:11.060 --> 01:30:11.580
while you walk

01:30:11.580 --> 01:30:11.960
I stalk

01:30:11.960 --> 01:30:12.620
the fox box

01:30:12.620 --> 01:30:13.160
to the party

01:30:13.160 --> 01:30:13.580
I'm lying,

01:30:13.680 --> 01:30:14.180
security checks

01:30:14.180 --> 01:30:14.620
to my eye

01:30:14.620 --> 01:30:15.320
disinfected,

01:30:15.440 --> 01:30:16.200
in the elevator

01:30:16.200 --> 01:30:16.880
waiting to get

01:30:16.880 --> 01:30:17.280
rested,

01:30:17.580 --> 01:30:18.240
open the doors

01:30:18.240 --> 01:30:18.680
to the floor

01:30:18.680 --> 01:30:19.360
by the heat,

01:30:19.540 --> 01:30:20.280
and you pass a J

01:30:20.280 --> 01:30:20.800
will they play

01:30:20.800 --> 01:30:21.420
pause with me,

01:30:21.480 --> 01:30:21.900
get a pass

01:30:21.900 --> 01:30:22.420
a couple nice

01:30:22.420 --> 01:30:22.980
unless you like

01:30:22.980 --> 01:30:23.440
it neat,

01:30:23.540 --> 01:30:24.000
all the guys

01:30:24.000 --> 01:30:24.500
step up,

01:30:24.600 --> 01:30:25.040
all the guys

01:30:25.040 --> 01:30:25.540
take teeth,

01:30:25.660 --> 01:30:25.840
poke,

01:30:25.900 --> 01:30:26.520
feds the air,

01:30:26.760 --> 01:30:27.140
you're feeling

01:30:27.140 --> 01:30:27.520
Denise,

01:30:27.700 --> 01:30:28.180
on your mansion,

01:30:28.260 --> 01:30:28.660
on your minor,

01:30:28.740 --> 01:30:29.280
on the middle

01:30:29.280 --> 01:30:29.660
east,

01:30:29.720 --> 01:30:30.320
the Fashita,

01:30:30.780 --> 01:30:31.220
hop a dress

01:30:31.220 --> 01:30:31.780
to the Syrola

01:30:31.780 --> 01:30:32.260
with a sister

01:30:32.260 --> 01:30:33.080
liquor belt loop,

01:30:33.160 --> 01:30:33.840
bleep to the liquor

01:30:33.840 --> 01:30:34.280
with lips,

01:30:34.420 --> 01:30:34.880
smelling best

01:30:34.880 --> 01:30:35.620
and the bubblegum

01:30:35.620 --> 01:30:36.240
scratch the shifts

01:30:36.240 --> 01:30:36.880
take your lips

01:30:36.880 --> 01:30:37.100
shoot,

01:30:37.220 --> 01:30:37.980
suck the deck out

01:30:37.980 --> 01:30:39.100
and cook all my dash

01:30:39.100 --> 01:30:39.600
to a crib,

01:30:39.800 --> 01:30:40.640
the roomie is a geek

01:30:40.640 --> 01:30:41.680
he's playing God's keys

01:30:41.680 --> 01:30:42.120
making friends

01:30:42.120 --> 01:30:42.740
I'm down to end

01:30:42.740 --> 01:30:43.440
so I'm climbing up

01:30:43.440 --> 01:30:43.740
a tree,

01:30:43.820 --> 01:30:44.800
beers clinging to my teeth

01:30:44.800 --> 01:30:45.660
Mr. Wendell edge

01:30:45.660 --> 01:30:46.120
hit the hedge

01:30:46.120 --> 01:30:46.880
land upon my teeth

01:30:46.880 --> 01:30:48.060
I'm a dome rack

01:30:48.060 --> 01:30:49.140
that is a fact jack

01:30:49.140 --> 01:30:50.120
look at it instead

01:30:50.120 --> 01:30:51.200
playing with warm wax

01:30:51.200 --> 01:30:52.100
hitting all the hundreds

01:30:52.100 --> 01:30:52.960
at the vendor machine

01:30:52.960 --> 01:30:53.660
the one hitter

01:30:53.660 --> 01:30:54.120
trade dinner

01:30:54.120 --> 01:30:55.020
all you need's an ID

01:30:55.020 --> 01:30:56.380
I said I'm a dome rack

01:30:56.380 --> 01:30:57.460
that is a fact jack

01:30:57.460 --> 01:30:58.460
looking at it instead

01:30:58.460 --> 01:30:59.540
playing with warm wax

01:30:59.540 --> 01:31:00.420
hitting all the hundreds

01:31:00.420 --> 01:31:01.280
at the vendor machine

01:31:01.280 --> 01:31:02.000
the one hitter

01:31:02.000 --> 01:31:02.440
trade dinner

01:31:02.440 --> 01:31:03.360
all you need's an ID

01:31:03.360 --> 01:31:04.580
grab a bottle

01:31:04.580 --> 01:31:05.100
though I'm plaid

01:31:05.100 --> 01:31:05.380
please

01:31:05.380 --> 01:31:06.620
everything you girls wear

01:31:06.620 --> 01:31:07.520
make me stare at the dirt

01:31:07.520 --> 01:31:08.220
the five balls

01:31:08.220 --> 01:31:08.960
I flirt with y'all

01:31:08.960 --> 01:31:09.520
study hall

01:31:09.520 --> 01:31:10.260
do the geek talk

01:31:10.260 --> 01:31:10.780
turn your idol

01:31:10.780 --> 01:31:11.560
back into your skull

01:31:11.560 --> 01:31:12.260
but I'm a freak

01:31:12.260 --> 01:31:13.800
spell F-O-Double-3-K

01:31:13.800 --> 01:31:14.920
when you walk on my way

01:31:14.920 --> 01:31:15.820
put my pockets in play

01:31:15.820 --> 01:31:17.020
I can't say what's your name

01:31:17.020 --> 01:31:17.920
care to chat for a bit

01:31:17.920 --> 01:31:18.600
it's me, Brian

01:31:18.600 --> 01:31:19.560
the guy from the class

01:31:19.560 --> 01:31:20.180
rushing it

01:31:20.180 --> 01:31:20.660
care to sit

01:31:20.660 --> 01:31:21.180
have a trip

01:31:21.180 --> 01:31:22.220
can't force some fun dip

01:31:22.220 --> 01:31:23.320
trust the S.P. doesn't impress me

01:31:23.320 --> 01:31:24.160
what you think of that shit

01:31:24.160 --> 01:31:24.740
but I don't

01:31:24.740 --> 01:31:25.380
I just switch

01:31:25.380 --> 01:31:26.380
and I itch in my pants

01:31:26.380 --> 01:31:27.320
play my Game Boy Advance

01:31:27.320 --> 01:31:28.400
until she finally walked past

01:31:28.400 --> 01:31:29.040
I'm at dash

01:31:29.040 --> 01:31:29.520
in my crib

01:31:29.520 --> 01:31:30.440
what I get on my blog

01:31:30.440 --> 01:31:31.560
at trickyspot.com

01:31:31.560 --> 01:31:32.540
check it out if you want

01:31:32.540 --> 01:31:33.660
that's a steam-blowing team

01:31:33.660 --> 01:31:34.700
where I reign supreme

01:31:34.700 --> 01:31:35.500
westerns my friends

01:31:35.500 --> 01:31:36.220
that I run the message

01:31:36.220 --> 01:31:36.940
watch when we need

01:31:36.940 --> 01:31:37.800
to mess them off a team

01:31:37.800 --> 01:31:38.820
it's a paradise and earth

01:31:38.820 --> 01:31:39.880
but in a way it's like a curse

01:31:39.880 --> 01:31:40.900
faster than a google search

01:31:40.900 --> 01:31:41.920
just sit here and drink

01:31:41.920 --> 01:31:42.900
while my roommate flirts

01:31:42.900 --> 01:31:44.080
at some party with some hotties

01:31:44.080 --> 01:31:45.040
who's all into Fred Durst

01:31:45.040 --> 01:31:45.900
it makes my heart burst

01:31:45.900 --> 01:31:47.220
and yet I do nothing

01:31:47.220 --> 01:31:48.100
just get on the web

01:31:48.100 --> 01:31:49.200
and start bitching and fun

01:31:49.200 --> 01:31:49.840
nut.com

01:31:49.840 --> 01:31:50.300
commotion

01:31:50.300 --> 01:31:51.400
whose love life is suffering

01:31:51.400 --> 01:31:52.360
it's the rope of the oven

01:31:52.360 --> 01:31:53.440
or the hope of our loving

01:31:53.440 --> 01:31:54.600
that I'm a light rat

01:31:54.600 --> 01:31:55.680
that is a sad fact

01:31:55.680 --> 01:31:56.700
shining my tech tubes

01:31:56.700 --> 01:31:57.740
crying in red shoes

01:31:57.740 --> 01:31:58.540
storm light broke

01:31:58.540 --> 01:31:59.500
if you got nowhere to go

01:31:59.500 --> 01:32:00.640
I call my mother every day

01:32:00.640 --> 01:32:01.700
I say I wanna go home

01:32:01.700 --> 01:32:02.900
I am a light rat

01:32:02.900 --> 01:32:03.960
that is a sad fact

01:32:03.960 --> 01:32:04.980
shining my tech tubes

01:32:04.980 --> 01:32:06.000
crying in red shoes

01:32:06.000 --> 01:32:06.860
storm light broke

01:32:06.860 --> 01:32:07.800
if you got nowhere to go

01:32:07.800 --> 01:32:08.960
I call my mother every day

01:32:08.960 --> 01:32:10.080
I say I wanna come home