WEBVTT 00:00.000 --> 00:09.460 This is dedicated to all the hackers and the crackers, to the hackers and the crackers. 00:09.760 --> 00:15.520 I see in binary, I speak source code, step on my toes, I'll post a million jpegs of you 00:15.520 --> 00:16.600 and a fag pwned. 00:16.720 --> 00:21.640 In your digital stance, getting firewalled ho, cause I'm riding the net in my six-fold. 00:21.900 --> 00:26.440 I was a dick with my 56, now with my cable I'm able to get that stable. 00:26.440 --> 00:32.460 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.680 --> 00:38.360 In a flash, I'll screw you on burning Dreamcast. You need some ISO? Let me through my hard drive rifle. 00:38.700 --> 00:43.520 Our exchange you could never stifle. In a digital hug, you just caught the love bug. 00:43.840 --> 00:47.540 I bootlegged your CD, I caused a fight between Un and Jay-Z. 00:47.880 --> 00:52.100 Your CG, it's all gonna be free, whether we take it by force or we take it nicely. 00:52.220 --> 00:56.280 You feel that rattling your bones? When I tell you we just hacked out Jones. 00:56.440 --> 01:00.660 And NASDAQ leaves you flat on your back, cause I am he who loves to hack and crack. 01:01.080 --> 01:03.460 Cause I am he who loves to hack and crack. 01:03.960 --> 01:06.740 This is dedicated to the hackers and the crudents. 01:07.080 --> 01:11.660 Serial codes, source codes, ISOs, RANS, SIFs, SIFs. 01:11.880 --> 01:14.200 This is dedicated to the hackers and the crack. 01:14.200 --> 01:16.720 Yes, you can believe it. 01:16.780 --> 01:22.900 You are hearing me, Stank Dog, on Binary Revolution Radio episode number 191. 01:23.320 --> 01:28.360 Finally coming to you today, April 10th, 2007. 01:29.480 --> 01:31.000 We finally got a new episode up. 01:31.080 --> 01:36.260 We had some delays there, some things that came up that were a little bit out of our control. 01:36.260 --> 01:39.080 But we are back, at least for this week. 01:39.140 --> 01:44.700 I'm not sure what next week's gonna hold, but I guess let's talk about that in a couple seconds. 01:44.840 --> 01:49.780 First of all, I should mention that my co-host today is absolutely nobody. 01:50.180 --> 01:53.440 I am doing this episode Millennium Falcon style, baby. 01:53.520 --> 01:56.600 That's right, flying Han solo up in this biatch. 01:57.200 --> 02:01.680 Got no co-host with me, so you are stuck with the dog on this episode. 02:01.680 --> 02:04.540 And we do have a few topics to talk about. 02:04.680 --> 02:07.120 I don't need no stinking co-host. 02:07.700 --> 02:11.220 Although the show would probably be much, much better if I had one. 02:11.560 --> 02:13.240 But, you know, we're gonna do what we can do. 02:13.820 --> 02:17.560 And today actually literally is April 10th, a Tuesday. 02:17.740 --> 02:24.560 I am recording this just before we go live because I did have an opening in my schedule to actually get one done. 02:25.540 --> 02:29.760 So, a few things to talk about in housekeeping before we go there, though. 02:29.760 --> 02:37.060 So, that we are in the process, or actually hopefully finished at this point, moving servers once again. 02:37.240 --> 02:41.380 Yes, I know we did this, what, three, four months ago, two, three months ago. 02:41.520 --> 02:49.280 But, well, quite frankly, the hosting company that we are slash were with was just not cutting the mustard. 02:49.440 --> 02:54.640 They weren't giving us what we expected from the server, from the hosting, from the support side of things. 02:54.640 --> 02:57.900 And physically the server was fine. 02:57.980 --> 03:00.500 It had enough power to get by in the short term. 03:01.100 --> 03:06.840 But we kind of, we knew that this was gonna be short term, maybe last another year or so on that server 03:06.840 --> 03:12.180 before we were going to frankly have to look at possibly upgrading again as the site continues to grow. 03:12.340 --> 03:16.740 So, we kind of killed two birds with one stone by finding another hosting company. 03:16.740 --> 03:19.280 First of all, we upgraded the server once again. 03:19.420 --> 03:21.320 We have even more power, more memory. 03:21.820 --> 03:27.100 So, we should be good on this server for a good couple of years, if not longer. 03:27.420 --> 03:33.160 So, hopefully we will be staying put if the second part of this equation comes into play. 03:33.780 --> 03:40.580 And that is the fact that we went with a total managed solution when we switched servers this time. 03:40.640 --> 03:44.420 That is to say that in the past we've been doing self-management. 03:44.420 --> 03:53.020 Now, we all know Linux pretty well and I have a few years of experience self-taught in maintaining and managing this server over the years. 03:53.360 --> 03:59.340 But we've gotten to the point where we've grown so big that the time that it takes to maintain a server like this 03:59.340 --> 04:05.880 and the constant monitoring and watching of it is just something that is really starting to wear on me. 04:06.000 --> 04:12.180 It's starting to dig into my time that I need to produce well to shows like this one. 04:12.180 --> 04:17.120 I haven't done a lot of writing in a while and I've got a ton of articles in my head that I want to get down on paper. 04:18.020 --> 04:20.460 Creating content for Hack TV, everything. 04:20.860 --> 04:26.020 You know, it actually slows me down from actually producing content, which is what I enjoy doing. 04:26.240 --> 04:31.780 So, when we switched to this last hosting company, we were looked for only managed services 04:31.780 --> 04:36.040 and we had an offer of total management of the server. 04:36.040 --> 04:42.760 And I guess long story short, without going into details, because technically we still have not canceled that server quite yet. 04:43.120 --> 04:49.440 So, without going into details of who, where, and why, we'll just say that it did not live up to expectations. 04:49.680 --> 04:55.320 So, we have shopped around and found a good deal from a company called Karo.net. 04:55.320 --> 05:02.500 So, you will see probably us talking about that in the forums and on the sites occasionally. 05:03.060 --> 05:04.920 Hopefully, our experience with them will be better. 05:05.040 --> 05:07.280 I can tell you that so far, it is very much. 05:07.660 --> 05:14.160 And they have taken very good care of us on working with us on this new server, giving us a good price, giving us great support so far. 05:14.300 --> 05:17.900 So, you'll have to forgive me if I will be pimping them out for a while. 05:18.000 --> 05:22.120 They are actually going to be kind of a sponsor, if you will, of the show. 05:22.120 --> 05:29.960 So, that being said, let's move into the show itself and actually jump right into the mailbag. 05:29.960 --> 05:52.120 And our first email. 05:52.260 --> 05:54.460 Now, you've got to realize also that we're backed up on email. 05:54.640 --> 05:57.920 So, we're going to have a pretty large email section on this week's show. 05:57.920 --> 06:03.020 But our first email comes from Swooz, which is kind of a fun name to say. 06:03.820 --> 06:06.160 Swooz, S-W-O-O-Z, who says, 06:06.780 --> 06:09.800 Stank and featured co-host or substitute host. 06:10.080 --> 06:11.920 First of all, you're owned, bitch. 06:12.060 --> 06:13.940 You don't have a co-host this week. 06:14.000 --> 06:15.660 It's just me, biatch. 06:16.800 --> 06:18.080 There, get that out of my system. 06:18.660 --> 06:22.360 Swooz says, I've been a faithful listener since episode circa 90 06:22.360 --> 06:27.380 and have been listening to another internet radio podcast or whatever since 1996. 06:27.940 --> 06:32.380 But have more recently switched to BinRev due to the lack of tech, tech talk, 06:32.520 --> 06:35.300 and the emphasis on politics on the other show. 06:35.300 --> 06:41.420 So, yes, the other show does put a lot of emphasis on politics and we try to avoid it here. 06:41.620 --> 06:43.580 So, that's all well and good. 06:43.680 --> 06:46.740 Now, you know, that being said, you don't have to switch to BinRev. 06:46.800 --> 06:47.840 You can listen to both. 06:47.980 --> 06:50.640 I mean, I still listen to other shows. 06:50.780 --> 06:53.460 I'm not going to assume what you're referring to, 06:53.540 --> 06:56.940 but I still listen to other shows sometimes when I have the time. 06:56.940 --> 06:59.500 So, I appreciate the sentiment nonetheless. 07:00.340 --> 07:01.780 Now, Swooz goes on to say, 07:02.740 --> 07:06.580 I just wanted to write a quick note to say how much I'm anticipating the next episode. 07:07.560 --> 07:13.700 Well, yeah, you might want to second guess that after you hear me talking all by myself for the next hour. 07:14.360 --> 07:19.480 I check your website every night in hopes to listen to your hack cast before retiring for the evening and you are missed. 07:19.860 --> 07:20.500 Idea for a show? 07:20.600 --> 07:24.160 I like to see the show on buffer overflows, explanation of the stack, 07:24.240 --> 07:26.220 and just good conversation going on about that. 07:26.220 --> 07:27.220 Just a thought. 07:27.340 --> 07:28.760 Keep up the good work, fellas. 07:29.720 --> 07:30.080 Okay. 07:30.280 --> 07:31.480 Well, thank you, Swooz, for that. 07:31.520 --> 07:32.220 I appreciate it. 07:32.900 --> 07:39.180 As far as the show topics now, we've discussed that exact topic in the past, 07:39.280 --> 07:45.200 but the problem with it is it's just very, very difficult to explain verbally when we have just the radio as a medium. 07:45.960 --> 07:53.380 That's really a topic that needs some visual aid, some illustrations and code possibly to really get the point across. 07:53.380 --> 07:56.420 We are, however, going to give it a shot sometime. 07:56.540 --> 07:59.760 It's on the list of things we've been wanting to talk about for quite some time. 08:00.160 --> 08:06.000 We just haven't figured out exactly how to organize it and put it together into an episode of the show. 08:06.000 --> 08:13.460 I know a lot of the longtime listeners have heard reference to my show novels, show notes that I write before every show. 08:13.540 --> 08:14.160 I sit down. 08:14.280 --> 08:16.780 I mean, even tonight, quite honestly, I'm doing the show by myself. 08:16.860 --> 08:19.940 I could have completely lied and just flown by the seat of my pants, 08:19.940 --> 08:26.520 but I did sit down and put together show notes that took me about a half hour, 45 minutes to put them together for even a show as short 08:26.520 --> 08:29.440 and as straightforward as this, doing it by myself. 08:30.360 --> 08:35.420 And when we have a more complex topic, it's going to take much longer because I will sit with the co-host 08:35.420 --> 08:40.680 and we will organize and say, okay, what would be the best way to ease our way into the topic, 08:40.800 --> 08:43.960 make sure everybody's brought up to speed, make sure we don't leave anybody behind. 08:43.960 --> 08:48.480 You know, what do we need to explain before we explain the stack? 08:48.580 --> 08:52.100 What do we need to explain before we talk about buffer overflows? 08:52.200 --> 08:53.560 What do they have to understand? 08:53.680 --> 08:55.520 What concepts and things do they have to know? 08:55.960 --> 08:58.140 You can't just jump into buffer overflows. 08:58.260 --> 08:59.560 So you've got to bring everybody up to speed. 08:59.680 --> 09:02.460 Those are factors to take into account. 09:03.520 --> 09:07.960 So that is something that a lot of people might not realize or take for granted, 09:08.060 --> 09:11.260 that we put time into trying to make the show flow well. 09:11.260 --> 09:13.640 We could just turn the mic on and start talking about it. 09:13.960 --> 09:16.580 But that's not really what we like to do on BinRev Radio. 09:16.720 --> 09:17.960 We try to be organized. 09:18.480 --> 09:19.740 We may seem unorganized. 09:19.820 --> 09:20.600 We may cuss a lot. 09:20.660 --> 09:22.420 We may go off track sometimes. 09:22.420 --> 09:26.980 But we do try to take some pride into putting together a show that flows, 09:27.320 --> 09:30.220 that's organized, that gets the topics and points across. 09:30.520 --> 09:33.240 And, you know, sometimes we fail, but at least we try. 09:33.400 --> 09:36.860 So, yeah, it is on our list of topics to talk about. 09:36.980 --> 09:40.120 I think we're probably going to have to yell at Verbal to co-host that one with us. 09:40.120 --> 09:42.500 That's something that he would probably be really good at explaining. 09:42.500 --> 09:45.180 So we did set the stage for this, however. 09:45.320 --> 09:51.620 It was episode 167 where we talked about IP switching, about TCP IP, and some networking concepts. 09:51.840 --> 09:53.860 So that would be a prerequisite episode. 09:53.960 --> 09:57.860 So certainly go back and listen to that because that is something you would definitely need to understand 09:57.860 --> 10:01.740 before we go into another deeper topic. 10:01.740 --> 10:06.520 And we'll jump into the second email this week that comes from Virtual. 10:07.240 --> 10:12.020 Virtual said that the last episodes get on the air because I did not see them uploaded on the website. 10:12.500 --> 10:14.020 Also, do you need someone to do show notes? 10:14.120 --> 10:17.620 I am new to the BR community, but I'm ready to pitch in. 10:17.740 --> 10:18.680 So, two emails. 10:18.800 --> 10:19.880 We'll go ahead and talk about it now. 10:19.980 --> 10:23.380 The story with the show is pretty simple. 10:23.480 --> 10:24.400 It's not all that complex. 10:24.400 --> 10:31.580 As the regular listeners know, we've been basically handing switching co-hosting duties off for Season 4. 10:32.260 --> 10:34.620 Season 1 and 2, I pretty much did myself. 10:34.820 --> 10:37.180 I drove all of those episodes, co-hosted all of those. 10:37.540 --> 10:42.880 Season 3 came along, and I kind of had a life change, new job, moving, that kind of thing. 10:42.880 --> 10:48.800 So the show was handed over to Black Ratchet, who did the show for Season 3 and into Season 4. 10:49.680 --> 10:55.820 And towards the end of Season 3, I think it was, and into Season 4, we kind of realized that he had some life-changing events 10:55.820 --> 10:59.160 and same type situation and moving and whatnot. 10:59.480 --> 11:05.700 So we both realized that it might be better if we started to split the show up and try to share the hosting duties. 11:05.800 --> 11:11.260 And we've done that pretty successfully so far through the end of Season 3 and so far through Season 4. 11:11.260 --> 11:16.880 And I had some deadlines, have some deadlines that are still ongoing right now as we speak. 11:17.080 --> 11:20.300 And I knew in advance that this was going to be a rough month for me. 11:20.440 --> 11:24.860 So we were going to tag out and let Black Ratchet take the show back over. 11:24.960 --> 11:28.280 But unfortunately, he had an emergency come up at the last minute as well. 11:28.980 --> 11:36.380 And normally when that happens, I will step in and fill in, even though I'm booked up or it's someone else's turn, I'll still step up. 11:36.780 --> 11:39.440 And this was just a case where I simply could not do it. 11:39.440 --> 11:40.540 I'm working late. 11:40.620 --> 11:43.680 I'm not getting home until late into the evenings. 11:43.680 --> 11:49.760 And it's just I haven't had the time to dedicate to putting together notes and topics and even physically recording. 11:49.900 --> 11:51.840 It's just been that tight on time for me. 11:52.320 --> 11:54.860 I've been traveling, which I do quite frequently for work. 11:55.040 --> 11:56.480 So it's just been rough. 11:56.620 --> 11:58.760 And that's the simple answer to why there haven't been a show. 11:59.480 --> 12:02.260 Believe me, I take pride in putting this show out every week. 12:02.260 --> 12:10.260 And then when we did occasionally miss one, for reasons explained earlier, I would try to fill in and do a double back-to-back episode and catch us up. 12:10.400 --> 12:12.220 But not going to happen this week. 12:12.300 --> 12:12.920 Sorry, guys. 12:12.960 --> 12:16.000 You're stuck with this one episode and you're stuck with me for it. 12:16.120 --> 12:18.120 So that's all there is. 12:18.160 --> 12:18.800 That's the story. 12:19.000 --> 12:22.700 And we will hopefully try to get back on some schedule. 12:22.880 --> 12:24.760 I do not know what the future of the show is. 12:24.780 --> 12:25.540 I'll be honest with you. 12:25.540 --> 12:31.420 I do not know what we're going to do since it's kind of tough to do these every week. 12:32.060 --> 12:38.860 I would have a tendency to think that at some point we are probably going to switch to biweekly format if we continue after season four. 12:39.020 --> 12:42.300 So those are decisions that we are all working on right now. 12:42.300 --> 12:47.120 So basically getting switched over to the new server reduces a lot of headaches for us. 12:47.160 --> 12:53.080 So we will be talking about that within the DDP and figuring out who's available for what and take it from there. 12:53.080 --> 12:55.540 So we will keep everyone in the loop. 12:55.640 --> 13:00.040 Just tune in to BinRev Radio and we will let you know as soon as we possibly can. 13:00.940 --> 13:04.820 And I think as far as the show notes go, that's another thing that I've fallen behind on. 13:04.900 --> 13:12.340 I believe that I do have some show notes from Enigma who has sent me show notes and I just haven't put them all up yet. 13:12.380 --> 13:15.460 So I think we're fairly caught up on those, but I appreciate the offer. 13:16.100 --> 13:19.220 So that's something else I will have on my list of things to do. 13:19.700 --> 13:21.000 Let me tell you, this is not a list. 13:21.000 --> 13:23.420 This is like a novella of things to do. 13:23.560 --> 13:29.400 This is just a complete, I mean, I don't know when I'll ever, ever get everything done that's on my list of things to do, 13:29.500 --> 13:33.140 which is why it's always very helpful when people pitch in and help. 13:33.380 --> 13:35.140 So I appreciate the offer. 13:35.240 --> 13:41.440 In this case, I think we're okay, but I will keep your email address and get back to you if I decide to take you up on that. 13:41.440 --> 13:47.020 And our next email this week, doesn't it suck to have to hear only my voice? 13:47.140 --> 13:53.160 Like at this point is where, you know, somebody else would chime in with their thoughts and opinions and we, you know, have a little conversation. 13:53.280 --> 13:54.300 But you're stuck with me. 13:54.300 --> 14:01.040 And another thing that kind of sucks about this, I'm finding out, is that, like, you know, when someone else begins to talk, 14:01.100 --> 14:05.100 that's when I'll take my opportunity to have a sip of my sweet iced tea. 14:05.180 --> 14:09.080 Or in this case, I don't know why I'm still on this Kool-Aid kick, so I'm having some cherry Kool-Aid. 14:09.080 --> 14:16.620 But I can't really stop and take a drink because you're going to get a lot of dead air, which is like the cardinal sin of radio. 14:17.240 --> 14:20.360 Of course, I say um and ah a lot on the show, too, which is the other cardinal sin. 14:20.460 --> 14:21.800 So, you know, who really cares? 14:21.980 --> 14:23.680 But it kind of makes it a little bit difficult. 14:23.800 --> 14:33.820 But I am going to take a sip of some cherry Kool-Aid and continue on to our next email from Prince Vegeta, who has emailed us before. 14:33.820 --> 14:37.980 Prince Vegeta says, Dear host and that other guy. 14:38.060 --> 14:39.660 Well, you got owned, too, bitch! 14:39.980 --> 14:41.160 There is no other guy. 14:41.220 --> 14:41.920 It's me! 14:42.420 --> 14:43.220 Deal with it! 14:44.060 --> 14:47.860 Prince Vegeta says, Unlike Linux, a Windows OS tends to... 14:47.860 --> 14:52.140 Okay, also keep in mind, everyone, that these are emails from past episodes. 14:52.280 --> 14:55.740 We've been gone for a few weeks, so these are going to be all over the place. 14:55.820 --> 14:57.320 They're going to run the gamut of topics. 14:58.100 --> 14:59.240 This one is... 14:59.240 --> 15:00.360 Let's see, where was I? 15:00.360 --> 15:04.940 Unlike Linux, a Windows OS tends to self-destruct after installing it. 15:04.980 --> 15:08.360 So, from the moment you install it, it's in a constant process of alteration. 15:08.980 --> 15:13.660 I mean that with more programs you install, and the more stuff you do, it starts to work slower and slower. 15:14.220 --> 15:20.180 So, no matter what precautions you take when installing programs, the Winbox just dies, and you have to reinstall it at least once every two months. 15:21.340 --> 15:21.700 Yowza! 15:21.940 --> 15:23.200 Two months, man, that's rough. 15:23.680 --> 15:25.400 I hate having to reinstall Windows. 15:25.400 --> 15:31.900 I do it as rarely as possible, but I do know people that make it a thing they do every six months. 15:32.080 --> 15:33.040 I've never heard two months. 15:33.120 --> 15:34.760 That's kind of drastic, I guess. 15:34.960 --> 15:37.960 But, anyway, Prince Vegeta goes on to say, 15:38.060 --> 15:41.560 That means installing, configuring, etc., etc., lots of boring work. 15:42.240 --> 15:43.780 One solution is VMware. 15:44.260 --> 15:46.380 The other one is a drive cloning program. 15:46.500 --> 15:47.320 I use two of these. 15:47.640 --> 15:50.220 The first is called Drive Image XML. 15:50.220 --> 15:59.580 It's free, and you can add it as a plug-in for your BART PE disk and run it straight off your BART PE Win CD in case something goes wrong with your PC. 16:00.740 --> 16:04.040 Wow, did I just throw out, like, the entire fucking alphabet on that, or what? 16:04.700 --> 16:07.480 I install Windows XP and all my favorite programs. 16:07.660 --> 16:10.020 I consider all my settings just the way I like it. 16:10.180 --> 16:14.880 I scan my disk for Vista, which is viruses, intruders, spyware, trojans, and adware. 16:14.940 --> 16:18.620 That's an unfortunate acronym that I'm sure Microsoft hopes that doesn't stick. 16:18.620 --> 16:24.720 I refragment, I defragment, excuse me, my drive, and I'll refragment my drive. 16:24.800 --> 16:27.560 That would be extremely counterproductive. 16:28.380 --> 16:31.520 I might make that as a joke, April Fool's program, a refragmenter. 16:32.400 --> 16:34.100 Let's see, I defragment my drive. 16:34.200 --> 16:35.960 I boot BART PE and back it up. 16:36.420 --> 16:40.600 Six gigs of WinGoodness equals one two-gig backup file. 16:41.460 --> 16:44.440 By the way, you need to store the backup file on another partition. 16:44.440 --> 16:51.200 Because this copies my disk sector by sector, if I restore my backup, which takes about ten minutes, guess what? 16:51.300 --> 16:56.440 All my programs installed and configured in my HDD is defragmented. 16:57.360 --> 16:57.620 Great. 16:58.240 --> 16:59.400 There's just one small problem. 16:59.620 --> 17:03.580 The partition that you backup must be the same as the one you plan on restoring. 17:04.020 --> 17:05.520 And I mean exactly the same. 17:05.520 --> 17:15.860 So if you decide to permanently modify your partition size, you need to restore the backup, resize the disk, and make the backup again. 17:16.600 --> 17:20.760 Yeah, that's also a common refrain I hear from people that are using Ghost and stuff like that. 17:20.800 --> 17:22.740 I think more recent versions of Ghost are better. 17:23.160 --> 17:31.140 But the very early version of Ghost, before Symantec bought it, also had that problem where they had to be identical with the drives when they were restoring them. 17:31.140 --> 17:39.800 And there were also problems with Windows and their licensing issues where you were installing it to something that had even a fractional tiny bit of hardware difference. 17:39.900 --> 17:46.860 It would unlicense itself and force you to handle that problem, which was a pain in the rear end. 17:48.720 --> 17:49.240 Let's see. 17:49.300 --> 17:49.680 Where was it? 17:49.700 --> 17:53.720 So if you decide to permanently modify your partition size, you need to restore the backup, resize, and make the backup again. 17:53.720 --> 18:03.320 The second program is not free, and it's called, okay, I'm not sure if I'm going to pronounce this, Acronis, A-C-R-O-N-I-S, Drive Image Something. 18:03.800 --> 18:06.180 I guess he doesn't know the name either, so it's okay if I can't pronounce it. 18:06.560 --> 18:09.020 I use this because it can also do Linux FS. 18:09.220 --> 18:11.100 I guess it's better, but I like the free one. 18:12.500 --> 18:16.500 For example, this week I want Slackware installed, but next week I need SUS. 18:16.660 --> 18:19.900 It's a great way for switching OSes on a single partition. 18:19.900 --> 18:23.060 For example, this week I want Slackware installed, but next week I need SUS. 18:24.480 --> 18:32.660 Hope this was helpful for those who lose precious time reinstalling that bloated piece of trash, in parentheses, called Windows. 18:33.980 --> 18:36.760 So, wow, boy, did I stumble my way through that email. 18:36.980 --> 18:40.820 But, yeah, no other guy this week, so you got owned. 18:40.960 --> 18:42.520 Everybody got owned an email this week. 18:42.860 --> 18:43.880 But thanks for the tip. 18:44.080 --> 18:47.880 This is obviously a follow-up on our virtual computing episode. 18:47.880 --> 18:49.000 We talked about VMware. 18:49.240 --> 18:52.120 We talked about virtual environments and all the different uses of them. 18:52.120 --> 18:57.460 So, yeah, we talked about it on the show, and that's one of many uses that people can have. 18:58.140 --> 19:06.800 Home users can take advantage of virtual PC, virtual computing, at a performance hit. 19:06.800 --> 19:15.940 But businesses really, really love it, and it's become an even bigger buzzword each passing day because businesses that have the big cash, 19:16.000 --> 19:22.300 they can buy like a nice big high-end box and run all these virtual images of all the environments that they could imagine 19:22.300 --> 19:30.500 and have a lot of boxes for text testing and not actually have to have the physical boxing around cluttering up their data center 19:30.500 --> 19:33.680 and, you know, paying for each individual box adds up. 19:33.740 --> 19:38.560 It ends up being much, much cheaper if they can buy one high-end machine and then virtualize everything. 19:38.560 --> 19:42.820 So, businesses love this a lot more right now. 19:43.120 --> 19:48.200 Home users, certainly it has its uses, just like the one that Prince Vegeta described, 19:48.580 --> 19:53.800 and a lot of testing we can do, a lot of, well, from the hacking standpoint or security standpoint, 19:53.900 --> 19:58.680 you can do a lot of attack and defense methods on your own systems safely. 19:58.680 --> 20:02.680 And if you screw something up, you know, you can simply go back to the image. 20:03.720 --> 20:07.680 So, again, we've talked about a lot of that, so we won't go into that too much detail. 20:07.780 --> 20:09.100 You can go back and find that episode. 20:10.080 --> 20:14.340 The other thing is that, oh, man, what did I do here? 20:14.420 --> 20:15.460 I cut my email all up. 20:15.520 --> 20:20.980 But the other thing is that as PCs do become more and more and more powerful like they are right now, 20:21.500 --> 20:25.960 the performance hit that users at home take is really dwindling. 20:25.960 --> 20:33.600 I mean, you can certainly do a lot of stuff at home without having a huge performance hit. 20:33.900 --> 20:41.200 So, it's kind of interesting that to see, I guess, how long it's going to take 20:41.200 --> 20:45.820 before we can really start running a lot of virtual environments at home. 20:45.980 --> 20:49.600 I'm sure people can email me and tell me, yeah, I'm running 3, 4, 5, 10, whatever. 20:49.880 --> 20:53.560 I know Not Theory, of course, is a huge supporter and proponent of it. 20:53.560 --> 20:55.400 He uses multiple environments. 20:55.400 --> 20:58.260 But I think it's really going to roll out. 20:58.320 --> 21:01.960 Right now, it's just people who are really realizing to see the potential of it. 21:02.000 --> 21:04.580 But it's going to really roll out for common, everyday users. 21:05.160 --> 21:09.320 I think probably within the next years as PCs become more powerful 21:09.320 --> 21:11.120 and the prices continue to drop on the hardware, 21:11.800 --> 21:15.780 virtual computing is definitely the wave of the future. 21:17.640 --> 21:19.220 So, thank you for that email. 21:19.220 --> 21:24.420 Next email this week comes from, well, we're going to call him KJ. 21:25.780 --> 21:28.600 KJ says, live USB are easy. 21:28.680 --> 21:35.060 Okay, and this is a follow-up to the episode I did with Ubix about USB key applications, 21:35.140 --> 21:39.000 making your own USB key with lots of hacking goodness on it. 21:39.000 --> 21:45.080 So, KJ says, live USB are easy to make them Linux live USB. 21:45.720 --> 21:47.860 Linux distros can be as small as 30 megs, 21:47.940 --> 21:51.920 and I'm not talking about a bash plus kernel plus GNU tools and that's it. 21:52.280 --> 21:56.660 I'm talking about a whole full desktop with window manager, browser, office suite, 21:56.780 --> 21:58.640 network monitor, partitioners, etc. 21:58.640 --> 22:01.300 So, here is the rundown. 22:02.320 --> 22:05.640 Gparted, USB live and is just 30 megs. 22:05.880 --> 22:09.040 Damn small Linux, USB live is just 50 megs. 22:09.340 --> 22:14.300 Puppy Linux, USB live is just 75 megs with Opera slash SeaMonkey. 22:15.020 --> 22:19.980 And Pen Linux used for 128 meg USB. 22:20.520 --> 22:23.240 You can also have a USB live derivative. 22:24.500 --> 22:27.360 So, that is another cool tip. 22:27.360 --> 22:30.740 And, like I said, I know we did the episode with Ubix 22:30.740 --> 22:34.320 because Ubix has a few projects over on the Hack5 site 22:34.320 --> 22:37.380 on making, like, a couple of killer USB drives. 22:37.520 --> 22:40.180 Tons of apps that you can put on there, how useful they can be, 22:40.580 --> 22:43.120 scripting a lot of things, which is very, very cool. 22:43.600 --> 22:46.220 But I wouldn't mind seeing, like, a thread or two in the BinRev forums 22:46.220 --> 22:51.400 of several different USB drive projects for several different purposes. 22:51.700 --> 22:52.900 Like the one in this email. 22:52.900 --> 22:57.600 You know, like, maybe another drive focusing on security apps. 22:57.960 --> 23:00.360 Maybe one for productivity apps, etc., etc. 23:00.360 --> 23:03.220 Kind of like a recipe book for USB devices 23:03.220 --> 23:07.320 where you list the file sizes, like, exactly like we did in this email. 23:08.280 --> 23:10.900 List the file sizes and all the files that you would put on there. 23:11.000 --> 23:12.700 The size of the drive that you're dealing with. 23:12.700 --> 23:15.120 Because, you know, the other thing is not everybody can go out 23:15.120 --> 23:17.780 and buy, like, a 2-plus gigabyte USB key. 23:18.500 --> 23:20.200 You know, and we don't all have the money, A. 23:20.300 --> 23:23.340 And, B, you know, how much, it's kind of cool to see 23:23.340 --> 23:25.640 how much leatness can be thrown onto a small drive. 23:25.740 --> 23:28.320 Like, I know probably a lot of our listeners have 23:28.320 --> 23:33.360 even 32, 64, or 128 megabyte keys laying around 23:33.360 --> 23:36.320 or maybe that we even use on a daily basis. 23:37.220 --> 23:40.260 But especially, I've got some old 64s, I think, 23:40.260 --> 23:41.380 that are laying around here or there 23:41.380 --> 23:43.160 that I can't really put big files on. 23:43.220 --> 23:44.240 They're not too awful useful 23:44.240 --> 23:46.300 unless you're just transferring some documents here or there. 23:46.720 --> 23:48.740 But it would be cool to see within that limitation 23:48.740 --> 23:52.360 what kind of a distribution or what kind of tools 23:52.360 --> 23:55.140 or what kind of theme you could put on one key like that. 23:55.200 --> 23:57.180 So within a limitation, list, you know, 23:57.240 --> 23:59.020 what cool window manager you could put on there, 23:59.120 --> 24:00.540 what cool apps you might put on there, 24:00.540 --> 24:02.420 and see if you could put together, you know, 24:02.460 --> 24:08.000 even maybe name it, maybe go so far as to pimp your USB key. 24:08.140 --> 24:10.220 You can paint it, put logos, give it a name, 24:10.460 --> 24:11.680 put the whole recipe out there. 24:11.720 --> 24:13.200 We'll have a page dedicated to it. 24:13.480 --> 24:14.640 Yeah, okay, I'm getting a little corny. 24:14.740 --> 24:16.240 But point being, it would be kind of cool 24:16.240 --> 24:18.480 to have like a recipe book of different people 24:18.480 --> 24:19.980 and what they've done with their drives 24:19.980 --> 24:22.340 and maybe learn from each other, 24:22.420 --> 24:25.540 maybe take that and develop your own derivatives 24:25.540 --> 24:26.380 and your own drives. 24:26.380 --> 24:29.260 So they don't necessarily have to be live, 24:29.380 --> 24:31.740 USB live, bootable, Linux ones. 24:31.840 --> 24:33.740 They could be, you know, Windows apps. 24:33.840 --> 24:34.940 They could be Linux apps. 24:35.040 --> 24:37.300 Like I said, anything that you guys can think of 24:37.300 --> 24:39.760 I think would be cool to read and see. 24:40.120 --> 24:42.860 And, you know, a lot of people, you know, 24:42.900 --> 24:44.120 most of the listeners of this show 24:44.120 --> 24:46.140 do a lot of roll their own applications, 24:46.320 --> 24:47.360 roll their own stuff. 24:47.920 --> 24:50.000 But a lot of people, let's be honest, 24:50.060 --> 24:51.800 a lot of people out there go out and search Google 24:51.800 --> 24:54.240 and they just want step-by-step directions. 24:54.740 --> 24:57.620 Copy file A, copy file B, copy file C, 24:57.820 --> 25:00.040 install to hard drive, follow these steps, 25:00.400 --> 25:01.900 install to USB key. 25:01.900 --> 25:03.840 A lot of people want those written directions 25:03.840 --> 25:05.960 simplified like a recipe that they can follow. 25:06.220 --> 25:08.360 So I think that might be a cool thing 25:08.360 --> 25:09.960 that a lot of people would be interested in. 25:10.980 --> 25:11.840 Hey, maybe I'm wrong. 25:12.000 --> 25:12.420 Who knows? 25:12.900 --> 25:13.760 I've been wrong before. 25:14.140 --> 25:14.900 I was wrong once. 25:15.580 --> 25:16.820 Well, I thought I was wrong, 25:16.880 --> 25:18.160 but I was actually mistaken. 25:20.100 --> 25:21.880 Yeah, think about that recursion. 25:22.380 --> 25:23.840 Next email this week 25:23.840 --> 25:27.960 is from Killa Office Monkey. 25:28.860 --> 25:29.880 K-O-M. 25:29.980 --> 25:30.900 Killa Office Monkey. 25:31.900 --> 25:32.800 Killa Office Monkey says, 25:32.880 --> 25:34.820 Hello, random binrev hosts. 25:35.400 --> 25:36.180 I have a question. 25:36.340 --> 25:37.480 I asked this question in the forums, 25:37.600 --> 25:38.760 but nobody could give me an answer 25:38.760 --> 25:41.980 because of the number of connections. 25:42.540 --> 25:43.680 The question I have, 25:43.780 --> 25:45.260 is there a way to link, say, 25:45.340 --> 25:47.160 five different interweb connections, 25:47.500 --> 25:49.040 two Ethernet, three wireless, 25:49.880 --> 25:51.800 to make them as one connection 25:51.800 --> 25:54.080 so I can take five to six megabit connection 25:54.080 --> 25:55.700 and use it as one big pipe? 25:56.280 --> 25:57.320 Any suggestions? 25:59.020 --> 26:00.140 Okay, first of all, 26:00.140 --> 26:01.280 you got on, too, 26:01.380 --> 26:03.520 because hosts with an S is plural 26:03.520 --> 26:05.620 and I am flying solo. 26:05.920 --> 26:06.980 So, eat it. 26:09.120 --> 26:10.000 Let's see. 26:10.420 --> 26:12.060 As far as the topic at hand, 26:12.260 --> 26:12.520 let me, 26:13.140 --> 26:14.060 I'm going to go ahead 26:14.060 --> 26:16.120 and qualify this answer up front 26:16.120 --> 26:18.060 by saying that I'm talking out of my ass here. 26:18.140 --> 26:18.360 Okay? 26:18.360 --> 26:21.400 But, that being said, 26:22.200 --> 26:23.720 the first thing I would ask 26:23.720 --> 26:24.840 is exactly where 26:24.840 --> 26:25.880 and in what capacity 26:25.880 --> 26:27.440 you're trying to do this. 26:28.340 --> 26:29.160 What I mean is, 26:29.260 --> 26:30.700 if you're asking about 26:30.700 --> 26:31.600 whether you can soup up 26:31.600 --> 26:33.000 like your home Windows box 26:33.000 --> 26:34.320 to use multiple resources, 26:34.740 --> 26:36.160 then the quick answer is no. 26:36.240 --> 26:38.020 It doesn't really work like that. 26:38.720 --> 26:40.360 If that's what you're shooting for, 26:40.420 --> 26:40.580 I mean, 26:40.640 --> 26:42.980 imagine like if you're war driving 26:42.980 --> 26:43.840 and you get a bunch of 26:43.840 --> 26:45.220 wireless access points 26:45.220 --> 26:45.960 or you're in an airport 26:45.960 --> 26:46.380 or someplace 26:46.380 --> 26:48.040 with lots of internet, 26:48.160 --> 26:49.860 wireless internet connections 26:49.860 --> 26:51.440 that you could all use 26:51.440 --> 26:52.080 at the same time. 26:52.120 --> 26:53.340 You could compound them all, 26:53.480 --> 26:54.380 use all that bandwidth. 26:55.440 --> 26:57.160 Never heard of anybody doing that. 26:57.160 --> 26:58.980 It's just not possible 26:58.980 --> 27:00.640 for multiple reasons. 27:00.760 --> 27:01.400 Now, I'm not saying 27:01.400 --> 27:03.060 not completely possible. 27:03.240 --> 27:04.680 I'm saying not easily possible. 27:05.360 --> 27:06.600 And, pretty realistically, 27:06.760 --> 27:07.680 I think I can say that. 27:08.380 --> 27:09.660 It's for multiple reasons, 27:09.800 --> 27:11.600 but mostly it's because 27:11.600 --> 27:13.660 you have multiple IP addresses involved 27:13.660 --> 27:15.360 because those are independent networks 27:15.360 --> 27:16.720 that don't communicate 27:16.720 --> 27:17.620 with each other. 27:18.900 --> 27:20.460 You could possibly solve 27:20.460 --> 27:22.380 the IP addresses 27:22.380 --> 27:24.460 with multiple cards 27:24.460 --> 27:25.720 and each card connecting 27:25.720 --> 27:27.120 to a different network. 27:28.140 --> 27:29.240 But even then, 27:29.620 --> 27:30.700 asking those cards 27:30.700 --> 27:32.360 to cooperate with each other, 27:32.860 --> 27:33.660 the network stack 27:33.660 --> 27:35.300 doesn't exactly work that way. 27:35.300 --> 27:35.800 I don't think it could 27:35.800 --> 27:36.880 exactly handle that. 27:37.240 --> 27:37.400 You know, 27:37.740 --> 27:38.700 you've heard probably 27:38.700 --> 27:40.100 us talk about on the show before 27:40.100 --> 27:41.700 having two network cards 27:41.700 --> 27:42.260 in your laptop, 27:42.380 --> 27:42.780 for example, 27:42.880 --> 27:44.400 where one is bringing data in 27:44.400 --> 27:46.800 and one is feeding data back out, 27:46.840 --> 27:48.120 a man-in-the-middle type attack. 27:48.400 --> 27:49.640 Those are two independent 27:49.640 --> 27:50.860 connections of each other. 27:50.920 --> 27:51.860 One's transferring data 27:51.860 --> 27:52.680 to the other one. 27:52.740 --> 27:53.480 They're not actually 27:53.480 --> 27:55.840 doubling up the bandwidth 27:55.840 --> 27:57.140 by connecting to the same network. 27:57.160 --> 27:58.620 They're two separate things. 27:59.040 --> 27:59.060 So, 27:59.820 --> 28:00.840 it's not exactly, 28:00.920 --> 28:02.120 if that's what you're shooting for, 28:02.800 --> 28:03.900 then the short answer 28:03.900 --> 28:04.740 is no. 28:04.820 --> 28:06.280 You can't really easily do that. 28:06.860 --> 28:07.160 Now again, 28:07.200 --> 28:07.980 if anybody listening 28:07.980 --> 28:08.820 knows otherwise, 28:08.940 --> 28:09.380 by all means, 28:09.540 --> 28:10.720 write in and let me know, 28:10.720 --> 28:11.560 but I don't think there's 28:11.560 --> 28:12.460 an easy way to do this 28:12.460 --> 28:13.820 if there's even a way at all, 28:13.900 --> 28:14.920 especially Windows. 28:16.080 --> 28:16.480 Now, 28:16.600 --> 28:17.480 on the other hand, 28:18.340 --> 28:19.260 if you're talking about 28:19.260 --> 28:20.680 running like a network data center 28:20.680 --> 28:22.080 or something for a company, 28:22.800 --> 28:24.080 then the answer is 28:24.080 --> 28:24.760 kinda, 28:24.920 --> 28:25.740 kinda yes. 28:26.500 --> 28:26.940 And, 28:27.680 --> 28:28.500 it's yes, 28:28.620 --> 28:29.340 but I say kinda 28:29.340 --> 28:31.060 because this is where 28:31.060 --> 28:32.040 a lot of the higher end 28:32.040 --> 28:32.940 networking equipment 28:32.940 --> 28:33.820 comes into play. 28:34.160 --> 28:35.020 I'm not sure about 28:35.020 --> 28:36.080 the wireless part of this 28:36.080 --> 28:36.620 again. 28:36.720 --> 28:37.320 The wireless part 28:37.320 --> 28:37.820 of your equation, 28:37.980 --> 28:38.280 honestly, 28:39.080 --> 28:40.300 wireless is really 28:40.300 --> 28:41.440 just a different medium 28:41.440 --> 28:42.820 that still stems 28:42.820 --> 28:43.720 from some sort of 28:43.720 --> 28:44.660 wired link. 28:45.220 --> 28:45.560 So, 28:45.620 --> 28:46.300 unless you have access 28:46.300 --> 28:47.020 to control that 28:47.020 --> 28:48.440 incoming wired link, 28:48.540 --> 28:49.400 the wireless is just 28:49.400 --> 28:50.480 another kinda segment 28:50.480 --> 28:51.320 along the way. 28:51.400 --> 28:52.520 It's kinda relaying it, 28:52.520 --> 28:53.460 so it's not exactly 28:53.460 --> 28:55.000 as easy. 28:55.840 --> 28:56.200 Now, 28:56.320 --> 28:57.100 it may be possible, 28:57.220 --> 28:58.060 but I've just never seen 28:58.060 --> 28:59.080 the two mixed like that. 28:59.160 --> 28:59.280 So, 28:59.360 --> 29:00.260 I actually would be 29:00.260 --> 29:00.840 interested to hear 29:00.840 --> 29:01.500 if anybody's ever 29:01.500 --> 29:02.640 successfully mixed the two, 29:02.700 --> 29:03.520 but I don't think that's, 29:03.780 --> 29:04.920 it's certainly not common. 29:06.080 --> 29:06.440 Now, 29:06.540 --> 29:07.460 to the wired part 29:07.460 --> 29:08.300 on the other hand, 29:08.660 --> 29:08.820 yeah, 29:08.880 --> 29:09.660 that's exactly what 29:09.660 --> 29:10.420 data centers do. 29:10.500 --> 29:11.120 You've got multiple 29:11.120 --> 29:12.200 pipes coming in, 29:12.700 --> 29:12.960 and, 29:13.040 --> 29:13.180 you know, 29:13.220 --> 29:14.320 if you need to have 29:14.320 --> 29:14.840 more bandwidth, 29:14.960 --> 29:15.520 you need to upgrade, 29:15.640 --> 29:16.600 you add another pipe 29:16.600 --> 29:17.560 and add another line, 29:17.620 --> 29:18.740 add another line coming in 29:18.740 --> 29:19.420 from the phone company 29:19.420 --> 29:19.820 or whatever. 29:20.340 --> 29:20.620 And, 29:20.680 --> 29:21.380 you have redundancy 29:21.380 --> 29:22.120 in there as well, 29:22.120 --> 29:22.420 so, 29:22.780 --> 29:22.940 yeah, 29:23.040 --> 29:23.780 this is exactly 29:23.780 --> 29:24.800 what higher end 29:24.800 --> 29:25.600 data centers do, 29:26.200 --> 29:27.220 but that's not exactly 29:27.220 --> 29:27.800 your typical 29:27.800 --> 29:28.860 Ethernet connection. 29:29.020 --> 29:30.100 You said Ethernet. 29:30.300 --> 29:31.180 That's not your normal 29:31.180 --> 29:32.380 everyday Ethernet connection. 29:32.700 --> 29:34.300 These are fat digital pipes 29:34.300 --> 29:35.800 that are using 29:35.800 --> 29:37.640 high end multiplexers 29:37.640 --> 29:38.200 and switches 29:38.200 --> 29:39.820 and T1000 29:39.820 --> 29:41.580 and Decepticons 29:41.580 --> 29:42.640 and shit like that. 29:43.260 --> 29:44.300 It's something 29:44.300 --> 29:45.320 that's very high end. 29:45.440 --> 29:45.820 Again, 29:45.920 --> 29:46.400 it's something 29:46.400 --> 29:48.400 that's not simple 29:48.400 --> 29:49.800 to set up 29:49.800 --> 29:51.140 for a small office 29:51.140 --> 29:52.500 or a home office 29:52.500 --> 29:53.740 or something like that. 29:53.960 --> 29:54.200 Not, 29:54.360 --> 29:54.600 again, 29:54.680 --> 29:55.500 in my opinion. 29:55.820 --> 29:56.320 Unless you happen 29:56.320 --> 29:56.960 to have some 29:56.960 --> 29:57.820 high end equipment 29:57.820 --> 29:58.420 laying around 29:58.420 --> 29:59.540 that'll handle that. 30:00.000 --> 30:00.140 So, 30:00.320 --> 30:00.800 honestly, 30:00.880 --> 30:01.380 that's the best 30:01.380 --> 30:02.400 that I can really explain it. 30:02.480 --> 30:03.140 I admit, 30:03.240 --> 30:04.220 I'm not a networking guy. 30:04.260 --> 30:04.800 I'm a programmer, 30:04.800 --> 30:06.440 so I can get by 30:06.440 --> 30:07.160 with my networking, 30:07.320 --> 30:08.220 but I'm pretty sure 30:08.220 --> 30:10.740 that both of those scenarios 30:10.740 --> 30:11.780 are pretty rough 30:11.780 --> 30:13.280 and it's certainly 30:13.280 --> 30:14.580 anything is possible. 30:14.740 --> 30:15.080 We're hackers. 30:15.200 --> 30:15.820 We know that, 30:15.920 --> 30:17.580 but as far as there being 30:17.580 --> 30:18.440 a cheap, 30:18.540 --> 30:18.820 easy, 30:18.980 --> 30:19.220 simple, 30:19.740 --> 30:20.800 not that you asked for it 30:20.800 --> 30:21.460 whether it was cheap 30:21.460 --> 30:22.260 or simple or anything, 30:22.420 --> 30:23.700 but if anybody out there 30:23.700 --> 30:24.700 knows that there's a cheap, 30:24.800 --> 30:25.820 easy way to pull this off 30:25.820 --> 30:26.300 that I'm missing, 30:26.400 --> 30:27.200 by all means, 30:27.580 --> 30:29.800 email and set me straight 30:29.800 --> 30:32.220 because I just don't see it. 30:32.220 --> 30:32.640 But, 30:32.900 --> 30:33.240 hey, 30:33.360 --> 30:33.880 what do I know? 30:35.320 --> 30:35.700 And, 30:35.780 --> 30:35.960 you know, 30:36.020 --> 30:37.100 let's wrap up the email 30:37.100 --> 30:37.580 this week 30:37.580 --> 30:39.000 with our last email 30:39.000 --> 30:41.140 from Stack Smasher. 30:41.400 --> 30:42.500 Stack Smasher says, 30:42.620 --> 30:43.920 any word on when, 30:44.400 --> 30:45.160 if ever, 30:46.180 --> 30:48.480 Freak Factor will be back. 30:48.960 --> 30:49.400 Thanks, 30:49.500 --> 30:50.360 and always keep up 30:50.360 --> 30:51.120 the good work. 30:51.200 --> 30:51.400 Wow, 30:51.480 --> 30:51.820 thank you, 30:51.860 --> 30:52.500 Stack Smasher. 30:53.260 --> 30:54.480 All I can say is, 30:54.620 --> 30:55.340 everybody listening, 30:55.440 --> 30:56.240 email Not Theory 30:56.240 --> 30:57.520 and yell at him about it. 30:57.600 --> 30:58.280 It's sitting right 30:58.280 --> 30:59.440 on the edge of done. 30:59.640 --> 30:59.860 I mean, 30:59.900 --> 31:00.740 it's right there. 31:01.060 --> 31:02.080 We've been testing it. 31:02.080 --> 31:02.900 I know Ratchet and I 31:02.900 --> 31:03.460 have talked about it 31:03.460 --> 31:03.920 on the show 31:03.920 --> 31:04.560 and we're like, 31:04.620 --> 31:05.520 we both have thought 31:05.520 --> 31:06.820 it's right there. 31:06.920 --> 31:08.260 It's so close to being done, 31:08.440 --> 31:09.880 but we haven't quite 31:09.880 --> 31:11.120 gotten through the testing. 31:11.360 --> 31:13.060 We'll be up with Not Theory 31:13.060 --> 31:13.960 when he gets time 31:13.960 --> 31:14.560 to test it 31:14.560 --> 31:15.820 and we'll run into 31:15.820 --> 31:16.660 a little snag 31:16.660 --> 31:18.580 and just some little 31:18.580 --> 31:19.140 small glitch 31:19.140 --> 31:20.120 that has to be ironed out 31:20.120 --> 31:21.860 and just hasn't 31:21.860 --> 31:22.540 quite gotten done. 31:22.620 --> 31:24.020 But it's sitting right there 31:24.020 --> 31:24.660 teetering, 31:25.040 --> 31:25.740 ready to go 31:25.740 --> 31:26.340 and it's just, 31:26.560 --> 31:26.780 oh, 31:26.800 --> 31:27.500 it's kind of frustrating. 31:27.640 --> 31:28.400 So I don't want to put out 31:28.400 --> 31:29.140 any more teasers 31:29.140 --> 31:31.080 because it could come out tomorrow, 31:31.080 --> 31:32.100 it could come out 31:32.100 --> 31:32.800 in six months. 31:33.200 --> 31:33.880 And truthfully, 31:34.740 --> 31:36.120 now that we have switched servers, 31:36.240 --> 31:36.800 once again, 31:37.100 --> 31:38.120 I know he's going to start 31:38.120 --> 31:38.720 yelling at me 31:38.720 --> 31:39.400 and yelling at me 31:39.400 --> 31:40.220 and I'm going to break down 31:40.220 --> 31:40.840 and cry. 31:41.960 --> 31:42.320 Oh, 31:42.480 --> 31:44.200 I'm just so tired 31:44.200 --> 31:45.600 of the abuse. 31:45.860 --> 31:45.880 But, 31:46.440 --> 31:46.860 you know, 31:46.940 --> 31:47.820 it's all worthwhile 31:47.820 --> 31:48.320 when, 31:48.400 --> 31:48.600 you know, 31:48.640 --> 31:49.760 we end up making 31:49.760 --> 31:50.080 sweet, 31:50.180 --> 31:51.320 sweet love down by the fire 31:51.320 --> 31:52.300 and having makeup sex. 31:52.300 --> 31:52.580 So, 31:52.740 --> 31:53.340 kind of makes it all 31:53.340 --> 31:53.720 worthwhile, 31:53.860 --> 31:54.180 I guess. 31:55.300 --> 31:56.140 And on that note, 31:56.320 --> 31:57.240 why don't we switch 31:57.240 --> 31:58.580 into our main topic 31:58.580 --> 32:00.380 of the day. 32:00.520 --> 32:01.360 And the main topic 32:01.360 --> 32:03.000 of this show 32:03.000 --> 32:05.760 is April Fool's Day. 32:06.480 --> 32:06.840 Yeah, 32:06.920 --> 32:07.160 sorry, 32:07.240 --> 32:08.900 nothing as dramatic 32:08.900 --> 32:10.060 as Stack Smashing 32:10.060 --> 32:13.020 and some of the other things 32:13.020 --> 32:13.600 we talked about. 32:13.700 --> 32:13.980 But, 32:14.480 --> 32:15.460 I think a lot of people 32:15.460 --> 32:16.140 have some questions 32:16.140 --> 32:16.860 about not only 32:16.860 --> 32:17.900 our April Fool's stuff, 32:17.900 --> 32:18.160 but, 32:19.700 --> 32:20.020 ah, 32:20.100 --> 32:21.240 April Fool's in general. 32:21.320 --> 32:22.120 I had to take a drink there, 32:22.160 --> 32:22.300 guys. 32:22.360 --> 32:22.580 You guys, 32:22.660 --> 32:23.520 it's rough to sit here 32:23.520 --> 32:24.860 and talk non-stop 32:24.860 --> 32:25.620 by myself. 32:27.080 --> 32:27.360 Maybe, 32:27.420 --> 32:28.240 maybe I should like 32:28.240 --> 32:28.920 change voices 32:28.920 --> 32:29.860 and pretend I have 32:29.860 --> 32:30.760 a different co-host 32:30.760 --> 32:31.120 with me. 32:31.180 --> 32:32.160 Maybe I should do like a, 32:32.440 --> 32:33.480 have Beavis co-host 32:33.480 --> 32:34.840 or have somebody else 32:34.840 --> 32:35.400 I'll do voices, 32:35.560 --> 32:35.680 but, 32:36.340 --> 32:37.040 that would really 32:37.040 --> 32:37.700 strain my throat. 32:38.540 --> 32:38.900 But, 32:38.960 --> 32:39.440 let's talk about 32:39.440 --> 32:40.200 April Fool's Day 32:40.200 --> 32:40.600 a little bit 32:40.600 --> 32:41.380 because it's really, 32:42.020 --> 32:42.620 I know it sounds 32:42.620 --> 32:43.120 kind of funny, 32:43.220 --> 32:43.640 but it's really 32:43.640 --> 32:44.720 one of my favorite holidays. 32:44.860 --> 32:45.440 It's something I look 32:45.440 --> 32:46.620 forward to every year 32:46.620 --> 32:47.800 because, 32:47.900 --> 32:49.020 especially because of the, 32:49.680 --> 32:49.980 I don't know, 32:50.040 --> 32:50.840 there's kind of a tradition 32:50.840 --> 32:52.120 on the global interweb 32:52.120 --> 32:53.820 for April Fool's Day 32:53.820 --> 32:54.380 and it's growing 32:54.380 --> 32:55.140 year after year. 32:55.240 --> 32:55.660 A lot of people 32:55.660 --> 32:56.160 are realizing 32:56.160 --> 32:57.100 that it's kind of fun. 32:57.520 --> 32:58.380 You got one day 32:58.380 --> 32:58.940 that you can, 32:59.000 --> 32:59.200 you know, 32:59.280 --> 33:00.200 kind of trick people 33:00.200 --> 33:01.000 and play some pranks 33:01.000 --> 33:01.700 on each other 33:01.700 --> 33:03.500 and stuff like that 33:03.500 --> 33:04.120 and it's just, 33:04.240 --> 33:05.000 it's more traditional 33:05.000 --> 33:06.180 than anything else, 33:06.320 --> 33:06.480 but, 33:07.320 --> 33:07.680 you know, 33:07.760 --> 33:08.900 everybody has fun with it. 33:09.480 --> 33:09.720 Sites, 33:09.900 --> 33:10.060 you know, 33:10.120 --> 33:10.740 like Slashdot, 33:10.840 --> 33:11.220 for example. 33:11.360 --> 33:12.680 Slashdot always does something. 33:13.280 --> 33:13.760 This year, 33:13.820 --> 33:14.480 they kind of put up 33:14.480 --> 33:16.080 some fake 33:16.080 --> 33:17.020 dig this 33:17.020 --> 33:18.000 knockoff 33:18.000 --> 33:18.560 where they pretended 33:18.560 --> 33:19.100 like they were 33:19.100 --> 33:20.120 allowing their users 33:20.120 --> 33:20.720 to dig 33:20.720 --> 33:21.580 and vote up stories 33:21.580 --> 33:22.460 and things like that 33:22.460 --> 33:23.560 and not only 33:23.560 --> 33:24.380 did they do that 33:24.380 --> 33:24.940 but if you read 33:24.940 --> 33:25.420 some of them 33:25.420 --> 33:26.100 they were kind of funny 33:26.100 --> 33:26.500 the notes 33:26.500 --> 33:27.060 and the comments 33:27.060 --> 33:27.600 that were on them 33:27.600 --> 33:29.700 so Slashdot always 33:29.700 --> 33:30.580 does something fun 33:30.580 --> 33:31.340 so everybody always 33:31.340 --> 33:31.960 checks them out. 33:31.960 --> 33:33.460 I like Think Geek. 33:33.600 --> 33:35.280 Think Geek 33:35.280 --> 33:36.220 always does some 33:36.220 --> 33:37.160 pretty funny stuff. 33:37.240 --> 33:37.780 They always put up 33:37.780 --> 33:38.460 fake products 33:38.460 --> 33:41.100 and I'd be curious 33:41.100 --> 33:41.860 to see how many people 33:41.860 --> 33:42.880 actually try to buy them. 33:43.440 --> 33:43.900 So every year 33:43.900 --> 33:44.440 they'll make up 33:44.440 --> 33:45.200 some fake products 33:45.200 --> 33:45.940 that they'll put in there 33:45.940 --> 33:47.100 as real items to sell 33:47.100 --> 33:49.200 so that's always 33:49.200 --> 33:49.720 really funny. 33:49.820 --> 33:50.260 Some of those, 33:50.400 --> 33:51.200 because when you think about it 33:51.200 --> 33:52.060 if you wanted to make up products 33:52.060 --> 33:52.560 you could make up 33:52.560 --> 33:53.520 some pretty silly stuff 33:53.520 --> 33:54.760 and make up 33:54.760 --> 33:55.500 some pretty funny ones 33:55.500 --> 33:57.060 and actually this year 33:57.060 --> 33:58.720 I think 33:58.720 --> 33:59.720 apparently one of the 33:59.720 --> 34:00.720 fake items that they made 34:00.720 --> 34:01.280 I think it was an 34:01.280 --> 34:02.160 8-bit tie 34:02.160 --> 34:02.860 is what they call it 34:02.860 --> 34:03.420 which was like 34:03.420 --> 34:05.180 this old retro looking tie 34:05.180 --> 34:05.920 with these ugly 34:05.920 --> 34:07.560 big block graphics on it. 34:08.280 --> 34:09.540 I think I heard 34:09.540 --> 34:10.180 from somebody 34:10.180 --> 34:11.220 that that was actually 34:11.220 --> 34:11.860 so popular 34:11.860 --> 34:12.480 people were actually 34:12.480 --> 34:13.340 trying to order it 34:13.340 --> 34:14.400 that they're actually 34:14.400 --> 34:14.980 going through 34:14.980 --> 34:16.280 with making a real item 34:16.280 --> 34:16.760 out of that 34:16.760 --> 34:17.260 that they're actually 34:17.260 --> 34:18.240 making a real tie. 34:18.360 --> 34:19.080 Maybe that's a 34:19.080 --> 34:20.920 continuous April Fool's joke 34:20.920 --> 34:21.880 that that's not really true 34:21.880 --> 34:23.060 but somebody told me 34:23.060 --> 34:23.780 that that was actually 34:23.780 --> 34:24.800 a real product now 34:24.800 --> 34:25.460 because people 34:25.460 --> 34:26.440 actually wanted 34:26.440 --> 34:27.860 this ugly 34:27.860 --> 34:28.920 8-bit tie 34:28.920 --> 34:29.500 with these big 34:29.500 --> 34:30.700 block pixels on it. 34:32.120 --> 34:33.120 So that's kind of cool. 34:33.240 --> 34:34.060 ThinkGeek always does 34:34.060 --> 34:35.040 something fun like that 34:35.040 --> 34:35.480 every year. 34:36.500 --> 34:36.900 eBay 34:36.900 --> 34:38.520 did some stuff this year. 34:38.580 --> 34:39.320 They had what they called 34:39.320 --> 34:40.980 quote unbelievable deals 34:40.980 --> 34:42.440 like selling flying carpets 34:42.440 --> 34:44.000 and I think there was one 34:44.000 --> 34:44.340 where you could 34:44.340 --> 34:45.700 get your face on 34:45.700 --> 34:46.460 Route Rushmore 34:46.460 --> 34:47.400 or something like that. 34:47.860 --> 34:48.340 I don't know if that was 34:48.340 --> 34:48.960 a buy it now 34:48.960 --> 34:50.080 or if that was a bid on thing 34:50.080 --> 34:51.800 but again 34:51.800 --> 34:52.760 kind of the funny idea 34:52.760 --> 34:53.840 you can make stuff up 34:53.840 --> 34:54.860 and have some fun with it. 34:55.220 --> 34:55.700 I don't know if 34:55.700 --> 34:57.200 I'm not a big eBay user 34:57.200 --> 34:58.160 to be honest with you 34:58.160 --> 35:00.100 but I don't know 35:00.100 --> 35:01.320 if eBay has done that 35:01.320 --> 35:01.880 traditionally. 35:02.100 --> 35:02.860 I just heard about it 35:02.860 --> 35:03.480 this year 35:03.480 --> 35:04.440 and I don't know 35:04.440 --> 35:05.000 if they did anything 35:05.000 --> 35:05.480 last year 35:05.480 --> 35:05.960 if that's something 35:05.960 --> 35:06.700 they do every year 35:06.700 --> 35:07.160 or not. 35:07.380 --> 35:08.060 So maybe somebody 35:08.060 --> 35:08.640 who knows eBay 35:08.640 --> 35:10.560 could email in 35:10.560 --> 35:11.320 and let me know. 35:12.820 --> 35:13.560 Google of course 35:13.560 --> 35:13.980 is famous. 35:14.080 --> 35:14.600 They always do 35:14.600 --> 35:15.420 something every year 35:15.420 --> 35:16.940 and this year 35:16.940 --> 35:18.380 they did a couple things. 35:18.600 --> 35:19.060 One of them 35:19.060 --> 35:19.740 that was kind of funny 35:19.740 --> 35:20.520 and made you 35:20.520 --> 35:21.520 kind of do a double take 35:21.520 --> 35:23.220 was that they offered 35:23.220 --> 35:23.700 the ability 35:23.700 --> 35:24.640 to print out 35:24.640 --> 35:25.620 your Gmail 35:25.620 --> 35:26.780 and have it delivered to you. 35:26.840 --> 35:27.300 They could actually 35:27.300 --> 35:28.020 mail you 35:28.020 --> 35:29.520 your email 35:29.520 --> 35:30.820 which is kind of 35:30.820 --> 35:31.580 a funny concept 35:31.580 --> 35:32.440 especially any of us 35:32.440 --> 35:33.120 in the business world 35:33.120 --> 35:33.560 that have actually 35:33.560 --> 35:34.380 seen this happen. 35:34.980 --> 35:35.980 Some high managers 35:35.980 --> 35:37.240 that still to this day 35:37.240 --> 35:38.600 refuse to use 35:38.600 --> 35:39.480 the global interweb 35:39.480 --> 35:40.780 refuse to use email 35:40.780 --> 35:41.860 whether it's from 35:41.860 --> 35:42.360 ignorance 35:42.360 --> 35:43.640 laziness 35:43.640 --> 35:44.100 whatever 35:44.100 --> 35:44.700 or they simply 35:44.700 --> 35:45.580 can't comprehend 35:45.580 --> 35:46.480 or figure out 35:46.480 --> 35:46.880 how to use 35:46.880 --> 35:47.620 the computer machine 35:47.620 --> 35:48.280 in their office 35:48.280 --> 35:49.200 and they'll have 35:49.200 --> 35:49.760 secretaries 35:49.760 --> 35:50.540 actually print off 35:50.540 --> 35:50.980 the emails 35:50.980 --> 35:51.480 for them. 35:52.400 --> 35:53.040 A lot of 35:53.040 --> 35:54.140 high end executives 35:54.140 --> 35:55.000 and big companies 35:55.000 --> 35:56.080 don't have 35:56.080 --> 35:58.380 their assistants 35:58.380 --> 35:59.460 or secretaries 35:59.460 --> 35:59.900 or what not 35:59.900 --> 36:00.840 go through the email 36:00.840 --> 36:01.660 weed through them 36:01.660 --> 36:02.920 answer even some of them 36:02.920 --> 36:04.080 and only deliver 36:04.080 --> 36:04.940 the ones that they think 36:04.940 --> 36:05.620 are important enough 36:05.620 --> 36:06.480 to be dealt with. 36:07.140 --> 36:07.880 So that's not 36:07.880 --> 36:09.300 uncommon printing it out 36:09.300 --> 36:10.220 but obviously 36:10.220 --> 36:11.020 when you're offering 36:11.020 --> 36:11.800 that to everybody 36:11.800 --> 36:12.720 on the global interweb 36:12.720 --> 36:13.920 who has a Gmail account 36:13.920 --> 36:15.380 that's kind of different. 36:15.700 --> 36:16.820 I was actually thinking 36:16.820 --> 36:17.420 maybe I should 36:17.420 --> 36:18.640 write a little 36:18.640 --> 36:19.540 routine in there 36:19.540 --> 36:20.220 write a little script 36:20.220 --> 36:20.780 that would actually 36:20.780 --> 36:21.660 print out Pi 36:21.660 --> 36:23.420 and have them 36:23.420 --> 36:24.100 send that to me 36:24.100 --> 36:24.480 that would be 36:24.480 --> 36:25.080 a nice long 36:25.080 --> 36:25.580 print out 36:25.580 --> 36:26.300 but I guess 36:26.300 --> 36:26.780 if I could figure 36:26.780 --> 36:27.520 out how to email 36:27.520 --> 36:28.860 to get Pi 36:28.860 --> 36:29.440 into an email 36:29.440 --> 36:30.060 continuously 36:30.060 --> 36:30.840 somehow I could 36:30.840 --> 36:31.340 deserve it 36:31.340 --> 36:33.300 but the other thing 36:33.300 --> 36:34.680 that Google did 36:34.680 --> 36:35.180 this year 36:35.180 --> 36:36.080 was they announced 36:36.080 --> 36:36.620 something called 36:36.620 --> 36:36.980 I think it was 36:36.980 --> 36:38.000 TISP 36:38.000 --> 36:38.900 which was a 36:38.900 --> 36:39.600 toilet internet 36:39.600 --> 36:41.080 service provider 36:41.080 --> 36:41.500 where you could 36:41.500 --> 36:42.760 install the equipment 36:42.760 --> 36:43.920 into your toilet 36:43.920 --> 36:45.800 to get internet 36:45.800 --> 36:46.280 access. 36:46.280 --> 36:47.820 Now again 36:47.820 --> 36:48.360 I'm sorry 36:48.360 --> 36:48.960 I have issues 36:48.960 --> 36:49.540 with Google 36:49.540 --> 36:50.640 Google 36:50.640 --> 36:51.380 guess what 36:51.380 --> 36:52.260 we invented 36:52.260 --> 36:52.840 war shitting 36:52.840 --> 36:53.980 a long time ago 36:53.980 --> 36:54.720 admit you stole 36:54.720 --> 36:55.720 the idea from us 36:55.720 --> 36:57.100 war shitting 36:57.100 --> 36:58.280 was copyright 36:58.280 --> 36:59.260 and trademark 36:59.260 --> 37:00.780 or I guess 37:00.780 --> 37:01.420 technically it was 37:01.420 --> 37:02.500 open creative 37:02.500 --> 37:03.200 commons license 37:03.200 --> 37:03.660 so I guess 37:03.660 --> 37:04.720 they can take 37:04.720 --> 37:05.140 war shitting 37:05.140 --> 37:05.960 but anyway 37:05.960 --> 37:06.560 we invented 37:06.560 --> 37:07.080 war shitting 37:07.080 --> 37:08.240 a long time ago 37:08.240 --> 37:09.460 so that was 37:09.460 --> 37:10.320 our idea first 37:10.320 --> 37:10.700 Google 37:10.700 --> 37:11.660 thank you very much 37:11.660 --> 37:13.980 let's see 37:13.980 --> 37:14.700 as far as more 37:14.700 --> 37:15.000 let's see 37:15.000 --> 37:15.480 oh Blizzard 37:15.480 --> 37:16.180 is another one 37:16.180 --> 37:16.640 that I've always 37:16.640 --> 37:16.860 liked 37:16.860 --> 37:17.240 they've always 37:17.240 --> 37:18.080 done some 37:18.080 --> 37:18.600 cool jokes 37:18.600 --> 37:19.280 I'm not a big 37:19.280 --> 37:20.000 gamer but I am 37:20.000 --> 37:20.740 a Blizzard fan 37:20.740 --> 37:21.260 I think they make 37:21.260 --> 37:21.820 great games 37:21.820 --> 37:22.800 and honestly 37:22.800 --> 37:23.520 I don't play 37:23.520 --> 37:23.860 any of their 37:23.860 --> 37:24.480 games right now 37:24.480 --> 37:25.440 I can't get 37:25.440 --> 37:25.960 into that world 37:25.960 --> 37:26.440 of Warcraft 37:26.440 --> 37:27.140 I'll get addicted 37:27.140 --> 37:27.660 and I'll be up 37:27.660 --> 37:28.380 all night playing 37:28.380 --> 37:28.940 the freaking thing 37:28.940 --> 37:29.600 so I've avoided 37:29.600 --> 37:29.940 that 37:29.940 --> 37:31.020 but I still go to 37:31.020 --> 37:31.380 their website 37:31.380 --> 37:32.340 on April Fool's 37:32.340 --> 37:32.720 Day because I 37:32.720 --> 37:33.140 know they make 37:33.140 --> 37:33.700 great jokes on 37:33.700 --> 37:34.020 the site 37:34.020 --> 37:35.000 they even go 37:35.000 --> 37:35.400 all out 37:35.400 --> 37:35.760 they make a 37:35.760 --> 37:36.360 nice page 37:36.360 --> 37:36.940 fake art 37:36.940 --> 37:37.440 screenshots 37:37.440 --> 37:38.140 and what not 37:38.140 --> 37:38.680 so this year 37:38.680 --> 37:39.780 they introduced 37:39.780 --> 37:40.380 a new item 37:40.380 --> 37:40.820 called the 37:40.820 --> 37:41.940 tin foil helmet 37:41.940 --> 37:42.560 for World of 37:42.560 --> 37:42.920 Warcraft 37:42.920 --> 37:43.300 which was 37:43.300 --> 37:44.080 kind of cool 37:44.080 --> 37:45.920 and pretty 37:45.920 --> 37:46.660 doggone funny 37:46.660 --> 37:47.100 actually 37:47.100 --> 37:48.560 so that was 37:48.560 --> 37:49.060 kind of cool 37:49.060 --> 37:50.480 and maybe on a 37:50.480 --> 37:51.080 more hackerish 37:51.080 --> 37:51.300 note 37:51.300 --> 37:52.180 the Pirate Bay 37:52.180 --> 37:53.300 which probably 37:53.300 --> 37:53.980 people outside 37:53.980 --> 37:54.520 of this community 37:54.520 --> 37:55.100 might not even 37:55.100 --> 37:55.800 care or notice 37:55.800 --> 37:56.300 that they know 37:56.300 --> 37:56.820 they did this 37:56.820 --> 37:57.320 but they made 37:57.320 --> 37:57.800 an announcement 37:57.800 --> 37:58.400 that they would 37:58.400 --> 37:58.860 be moving 37:58.860 --> 38:00.420 to North Korea 38:00.420 --> 38:01.180 to have some 38:01.180 --> 38:01.880 protection in the 38:01.880 --> 38:02.380 embassy there 38:02.380 --> 38:03.160 because of their 38:03.160 --> 38:04.600 recent drama 38:04.600 --> 38:06.780 alright so yeah 38:06.780 --> 38:07.500 yeah blah blah 38:07.500 --> 38:08.120 enough already 38:08.120 --> 38:08.660 we don't need to 38:08.660 --> 38:09.280 hear about all the 38:09.280 --> 38:10.060 April Fool's 38:10.060 --> 38:10.540 jokes on the 38:10.540 --> 38:11.400 global interweb 38:11.400 --> 38:12.600 the tubes are 38:12.600 --> 38:13.120 filled with 38:13.120 --> 38:13.700 April Fool's 38:13.700 --> 38:14.220 jokes but 38:14.220 --> 38:15.500 you know the 38:15.500 --> 38:15.920 only one that 38:15.920 --> 38:16.440 really matters 38:16.440 --> 38:16.960 is BinRev 38:16.960 --> 38:17.240 right 38:17.240 --> 38:18.720 what did Bin 38:18.720 --> 38:19.360 Rev do 38:19.360 --> 38:20.700 for April Fool's 38:20.700 --> 38:21.240 Day because 38:21.240 --> 38:21.820 you know it 38:21.820 --> 38:22.280 seems that we 38:22.280 --> 38:22.860 confuse the hell 38:22.860 --> 38:23.240 out of a lot 38:23.240 --> 38:23.940 of people so 38:23.940 --> 38:25.400 let me clarify 38:25.400 --> 38:26.020 it because 38:26.020 --> 38:27.360 it's actually 38:27.360 --> 38:27.880 kind of a funny 38:27.880 --> 38:28.640 story truthfully 38:28.640 --> 38:30.080 well 38:30.080 --> 38:31.680 let's go back 38:31.680 --> 38:32.100 a couple of 38:32.100 --> 38:32.600 years actually 38:32.600 --> 38:33.360 like I said 38:33.360 --> 38:34.000 I've kind of 38:34.000 --> 38:34.680 made April Fool's 38:34.680 --> 38:35.200 Day a tradition 38:35.200 --> 38:35.820 I've done that 38:35.820 --> 38:36.660 for the longest 38:36.660 --> 38:37.200 time we've 38:37.200 --> 38:37.580 always played 38:37.580 --> 38:38.080 some kind of 38:38.080 --> 38:38.380 prank 38:38.380 --> 38:40.580 and the 38:40.580 --> 38:41.120 other thing 38:41.120 --> 38:41.840 too is 38:41.840 --> 38:43.420 pulling off 38:43.420 --> 38:44.160 a simple 38:44.160 --> 38:45.380 you know 38:45.380 --> 38:46.200 a simple 38:46.200 --> 38:46.540 prank 38:46.540 --> 38:46.860 you know we 38:46.860 --> 38:47.240 could easily 38:47.240 --> 38:47.720 put up a 38:47.720 --> 38:48.020 thing that 38:48.020 --> 38:48.960 says you 38:48.960 --> 38:49.780 know OMG 38:49.780 --> 38:50.860 BinRev has 38:50.860 --> 38:51.340 been busted 38:51.340 --> 38:52.000 by the feds 38:52.000 --> 38:52.280 and stank 38:52.280 --> 38:52.940 dogs in jail 38:52.940 --> 38:53.540 and you know 38:53.540 --> 38:53.960 stuff like 38:53.960 --> 38:54.200 that 38:54.200 --> 38:54.820 we've never 38:54.820 --> 38:55.300 taken the 38:55.300 --> 38:55.680 easy way 38:55.680 --> 38:55.860 out 38:55.860 --> 38:56.180 we've never 38:56.180 --> 38:56.620 done anything 38:56.620 --> 38:57.320 silly like 38:57.320 --> 38:57.680 that 38:57.680 --> 38:59.740 you know 38:59.740 --> 39:00.140 we did the 39:00.140 --> 39:00.820 OMG ponies 39:00.820 --> 39:01.220 last year 39:01.220 --> 39:01.480 which was 39:01.480 --> 39:01.740 kind of 39:01.740 --> 39:02.000 funny 39:02.000 --> 39:03.200 which totally 39:03.200 --> 39:03.820 by coincidence 39:03.820 --> 39:04.300 is what 39:04.300 --> 39:04.980 Slashdot did 39:04.980 --> 39:05.320 they went 39:05.320 --> 39:05.580 with the 39:05.580 --> 39:06.080 ponies theme 39:06.080 --> 39:06.520 as well 39:06.520 --> 39:07.660 it was a 39:07.660 --> 39:07.920 couple of 39:07.920 --> 39:08.280 years ago 39:08.280 --> 39:08.740 actually we 39:08.740 --> 39:09.520 did do a 39:09.520 --> 39:10.740 not exactly 39:10.740 --> 39:11.280 a stank dog 39:11.280 --> 39:11.640 has been 39:11.640 --> 39:12.060 busted 39:12.060 --> 39:12.680 type thing 39:12.680 --> 39:12.980 but what 39:12.980 --> 39:13.460 we did 39:13.460 --> 39:14.000 was 39:14.000 --> 39:15.680 we made 39:15.680 --> 39:16.340 the announcement 39:16.340 --> 39:17.700 that I 39:17.700 --> 39:18.040 had been 39:18.040 --> 39:18.620 taken in 39:18.620 --> 39:19.380 for questioning 39:19.380 --> 39:21.380 not for 39:21.380 --> 39:21.800 myself 39:21.800 --> 39:22.480 but because 39:22.480 --> 39:23.000 see this is 39:23.000 --> 39:23.300 where you got 39:23.300 --> 39:23.620 to throw a 39:23.620 --> 39:23.940 little bit of 39:23.940 --> 39:24.600 social engineering 39:24.600 --> 39:25.500 everybody knows 39:25.500 --> 39:25.840 that it's 39:25.840 --> 39:26.500 April Fool's 39:26.500 --> 39:26.700 Day 39:26.700 --> 39:28.160 you've got to 39:28.160 --> 39:28.460 figure out 39:28.460 --> 39:28.700 some way 39:28.700 --> 39:29.180 to cast 39:29.180 --> 39:29.640 a little bit 39:29.640 --> 39:30.020 of doubt 39:30.020 --> 39:30.500 in there 39:30.500 --> 39:31.000 because no 39:31.000 --> 39:31.260 one's going 39:31.260 --> 39:31.640 to believe 39:31.640 --> 39:32.160 anything you 39:32.160 --> 39:32.500 say on 39:32.500 --> 39:33.040 April Fool's 39:33.040 --> 39:33.140 Day 39:33.140 --> 39:33.500 you put up 39:33.500 --> 39:33.780 a thing 39:33.780 --> 39:34.080 that says 39:34.080 --> 39:34.580 stank dog's 39:34.580 --> 39:35.040 been busted 39:35.040 --> 39:35.500 blah blah 39:35.500 --> 39:35.700 blah 39:35.700 --> 39:36.700 it's not 39:36.700 --> 39:37.740 it's not 39:37.740 --> 39:38.200 going to sell 39:38.200 --> 39:38.640 very well 39:38.640 --> 39:39.000 everybody's 39:39.000 --> 39:39.200 going to be 39:39.200 --> 39:39.700 like yeah 39:39.700 --> 39:40.300 ha ha 39:40.300 --> 39:41.020 how obvious 39:41.020 --> 39:41.700 April Fool's 39:41.700 --> 39:41.920 joke 39:41.920 --> 39:42.360 blah blah 39:42.360 --> 39:43.360 well 39:43.360 --> 39:44.720 we kind of 39:44.720 --> 39:45.060 take a little 39:45.060 --> 39:45.620 time each year 39:45.620 --> 39:45.960 to try to 39:45.960 --> 39:46.320 come up with 39:46.320 --> 39:46.700 something a 39:46.700 --> 39:46.940 little bit 39:46.940 --> 39:47.300 creative 39:47.300 --> 39:48.020 and unique 39:48.020 --> 39:48.960 and that 39:48.960 --> 39:49.460 one we did 39:49.460 --> 39:50.140 was kind 39:50.140 --> 39:50.500 of funny 39:50.500 --> 39:51.840 because we 39:51.840 --> 39:52.480 posted up 39:52.480 --> 39:53.180 and said 39:53.180 --> 39:53.680 that I had 39:53.680 --> 39:54.240 been brought 39:54.240 --> 39:54.580 in for 39:54.580 --> 39:55.020 questioning 39:55.020 --> 39:56.040 well that 39:56.040 --> 39:56.960 could have 39:56.960 --> 39:57.340 left it 39:57.340 --> 39:57.900 right there 39:57.900 --> 39:58.720 saying that 39:58.720 --> 39:59.300 I was busted 39:59.300 --> 40:00.340 or that 40:00.340 --> 40:00.740 the site 40:00.740 --> 40:01.200 was busted 40:01.200 --> 40:01.580 or something 40:01.580 --> 40:02.240 we didn't 40:02.240 --> 40:02.640 do that 40:02.640 --> 40:03.060 we actually 40:03.060 --> 40:03.600 spun it 40:03.600 --> 40:03.940 a little bit 40:03.940 --> 40:04.440 to say 40:04.440 --> 40:06.200 no I'm 40:06.200 --> 40:06.700 not being 40:06.700 --> 40:07.200 busted 40:07.200 --> 40:08.340 I'm being 40:08.340 --> 40:08.820 questioned 40:08.820 --> 40:09.720 because one 40:09.720 --> 40:10.040 of our 40:10.040 --> 40:10.780 forum members 40:10.780 --> 40:11.820 posted something 40:11.820 --> 40:12.440 illegal on 40:12.440 --> 40:12.860 the site 40:12.860 --> 40:14.940 and I'm 40:14.940 --> 40:15.580 being asked 40:15.580 --> 40:16.100 to give up 40:16.100 --> 40:16.720 that information 40:16.720 --> 40:17.180 of who it 40:17.180 --> 40:17.500 is 40:17.500 --> 40:18.500 now 40:18.500 --> 40:19.760 it's still 40:19.760 --> 40:20.180 if that 40:20.180 --> 40:20.500 was in 40:20.500 --> 40:20.740 and of 40:20.740 --> 40:21.280 itself 40:21.280 --> 40:22.640 you know 40:22.640 --> 40:23.220 just saying 40:23.220 --> 40:23.440 that I'm 40:23.440 --> 40:23.820 taking in 40:23.820 --> 40:24.260 for questioning 40:24.260 --> 40:24.640 is one 40:24.640 --> 40:24.840 thing 40:24.840 --> 40:25.300 but saying 40:25.300 --> 40:25.740 that it's 40:25.740 --> 40:26.820 because I'm 40:26.820 --> 40:27.440 refusing to 40:27.440 --> 40:27.860 divulge 40:27.860 --> 40:28.280 information 40:28.280 --> 40:28.720 on other 40:28.720 --> 40:29.180 people in 40:29.180 --> 40:29.660 the forums 40:29.660 --> 40:30.940 what that 40:30.940 --> 40:31.340 does is 40:31.340 --> 40:31.760 it plants 40:31.760 --> 40:32.260 that seed 40:32.260 --> 40:32.580 of doubt 40:32.580 --> 40:33.020 in people's 40:33.020 --> 40:33.320 mind 40:33.320 --> 40:33.900 because there 40:33.900 --> 40:34.440 were people 40:34.440 --> 40:35.220 and I'm 40:35.220 --> 40:35.460 not going 40:35.460 --> 40:35.740 to drop 40:35.740 --> 40:36.040 names 40:36.040 --> 40:36.380 but we 40:36.380 --> 40:36.860 have a lot 40:36.860 --> 40:37.340 of logs 40:37.340 --> 40:37.760 from all 40:37.760 --> 40:38.160 that too 40:38.160 --> 40:38.560 for our 40:38.560 --> 40:39.880 own fun 40:39.880 --> 40:40.380 and internal 40:40.380 --> 40:40.860 purposes 40:40.860 --> 40:42.580 of people 40:42.580 --> 40:42.840 who were 40:42.840 --> 40:43.320 really freaked 40:43.320 --> 40:43.780 out because 40:43.780 --> 40:44.260 they started 40:44.260 --> 40:44.640 thinking 40:44.640 --> 40:45.140 well wait a 40:45.140 --> 40:45.260 minute 40:45.260 --> 40:46.060 I wonder 40:46.060 --> 40:46.640 if it's me 40:46.640 --> 40:47.060 I wonder 40:47.060 --> 40:47.500 what I 40:47.500 --> 40:47.840 posted 40:47.840 --> 40:48.160 in the 40:48.160 --> 40:48.400 forums 40:48.400 --> 40:48.780 oh my 40:48.780 --> 40:49.040 gosh 40:49.040 --> 40:49.280 I need 40:49.280 --> 40:49.480 to go 40:49.480 --> 40:49.780 delete 40:49.780 --> 40:50.020 this 40:50.020 --> 40:50.280 oh I 40:50.280 --> 40:50.460 need to 40:50.460 --> 40:50.800 go find 40:50.800 --> 40:51.080 and edit 40:51.080 --> 40:51.380 that 40:51.380 --> 40:51.900 people 40:51.900 --> 40:52.200 started 40:52.200 --> 40:52.440 really 40:52.440 --> 40:52.760 freaking 40:52.760 --> 40:53.000 out 40:53.000 --> 40:53.700 in IRC 40:53.700 --> 40:55.400 some of 40:55.400 --> 40:55.540 them 40:55.540 --> 40:56.060 legitimately 40:56.060 --> 40:56.520 some of 40:56.520 --> 40:56.640 them 40:56.640 --> 40:56.940 were like 40:56.940 --> 40:57.200 you know 40:57.200 --> 40:57.480 what 40:57.480 --> 40:58.280 it is 40:58.280 --> 40:58.520 April 40:58.520 --> 40:58.840 Fool's 40:58.840 --> 40:58.960 Day 40:58.960 --> 40:59.600 but just 40:59.600 --> 41:00.300 in case 41:00.300 --> 41:01.120 I'm 41:01.120 --> 41:01.280 going to 41:01.280 --> 41:01.700 go delete 41:01.700 --> 41:02.000 stuff 41:02.000 --> 41:02.520 when we 41:02.520 --> 41:02.760 pulled 41:02.760 --> 41:02.940 that 41:02.940 --> 41:03.260 I got 41:03.260 --> 41:03.500 more 41:03.500 --> 41:04.040 PMs 41:04.040 --> 41:04.420 from people 41:04.420 --> 41:04.700 saying 41:04.700 --> 41:04.940 that they 41:04.940 --> 41:05.100 wanted 41:05.100 --> 41:05.260 their 41:05.260 --> 41:05.580 accounts 41:05.580 --> 41:06.020 deleted 41:06.020 --> 41:06.660 and they 41:06.660 --> 41:06.840 wanted 41:06.840 --> 41:07.020 their 41:07.020 --> 41:07.320 posts 41:07.320 --> 41:07.800 deleted 41:07.800 --> 41:08.380 because 41:08.380 --> 41:08.520 they 41:08.520 --> 41:08.820 freaked 41:08.820 --> 41:09.060 out 41:09.060 --> 41:09.440 because of 41:09.440 --> 41:09.560 the 41:09.560 --> 41:09.720 whole 41:09.720 --> 41:10.060 thing 41:10.060 --> 41:11.140 and then 41:11.140 --> 41:11.520 the other 41:11.520 --> 41:11.820 little 41:11.820 --> 41:12.400 extra 41:12.400 --> 41:12.780 touch 41:12.780 --> 41:13.100 that I 41:13.100 --> 41:13.320 threw 41:13.320 --> 41:13.740 in there 41:13.740 --> 41:13.880 is 41:13.880 --> 41:14.180 everybody 41:14.180 --> 41:14.600 also 41:14.600 --> 41:14.880 knows 41:14.880 --> 41:15.080 that one 41:15.080 --> 41:15.300 of our 41:15.300 --> 41:15.680 other big 41:15.680 --> 41:15.920 sites 41:15.920 --> 41:16.060 is 41:16.060 --> 41:17.280 oldschoolfreak.com 41:17.280 --> 41:17.780 which is run 41:17.780 --> 41:18.380 by Natus 41:18.380 --> 41:20.380 so when it 41:20.380 --> 41:20.860 started to go 41:20.860 --> 41:21.560 sour and people 41:21.560 --> 41:22.280 started to think 41:22.280 --> 41:22.960 that maybe it was 41:22.960 --> 41:23.620 an April Fool's 41:23.620 --> 41:24.220 prank and it 41:24.220 --> 41:24.880 wasn't real 41:24.880 --> 41:25.540 after all 41:25.540 --> 41:27.500 I sent a 41:27.500 --> 41:28.520 quote unquote 41:28.520 --> 41:29.480 text message 41:29.480 --> 41:30.000 to Natus 41:30.000 --> 41:30.780 a fake text 41:30.780 --> 41:31.680 message to Natus 41:31.680 --> 41:32.640 that he put up 41:32.640 --> 41:33.920 on oldschoolfreak.com 41:33.920 --> 41:34.420 I don't know if it's 41:34.420 --> 41:35.120 archived over there 41:35.120 --> 41:35.700 we might have to 41:35.700 --> 41:36.380 dig it up for 41:36.380 --> 41:37.240 reference purposes 41:37.240 --> 41:38.800 where I sent a 41:38.800 --> 41:39.580 text message 41:39.580 --> 41:40.020 to Natus 41:40.020 --> 41:41.480 from my 41:41.480 --> 41:42.040 questioning 41:42.040 --> 41:42.580 I was being 41:42.580 --> 41:42.980 questioned 41:42.980 --> 41:43.680 and I somehow 41:43.680 --> 41:44.780 was able to get 41:44.780 --> 41:45.480 a text message 41:45.480 --> 41:46.300 off to Natus 41:46.300 --> 41:47.300 to post on 41:47.300 --> 41:48.240 oldschoolfreak.com 41:48.240 --> 41:48.860 to let everybody 41:48.860 --> 41:49.440 know that I 41:49.440 --> 41:50.200 didn't cave 41:50.200 --> 41:51.260 I didn't sell out 41:51.260 --> 41:52.020 and drop docs 41:52.020 --> 41:52.560 on everybody 41:52.560 --> 41:53.460 I'm still holding 41:53.460 --> 41:53.940 to the 41:53.940 --> 41:54.580 you know 41:54.580 --> 41:55.160 staying true 41:55.160 --> 41:55.560 to the 41:55.560 --> 41:56.480 users of the 41:56.480 --> 41:56.720 site 41:56.720 --> 41:57.460 not dropping 41:57.460 --> 41:58.180 that information 41:58.180 --> 41:59.020 which 41:59.020 --> 41:59.800 truthfully 41:59.800 --> 42:00.400 I would fight 42:00.400 --> 42:01.100 pretty doggone 42:01.100 --> 42:01.340 hard 42:01.340 --> 42:02.060 if it ever 42:02.060 --> 42:02.420 did come 42:02.420 --> 42:02.620 to that 42:02.620 --> 42:03.080 in real life 42:03.080 --> 42:03.720 but let's 42:03.720 --> 42:04.380 hope that it 42:04.380 --> 42:05.020 never does 42:05.020 --> 42:07.260 and 42:07.260 --> 42:09.080 text message 42:09.080 --> 42:09.880 kind of 42:09.880 --> 42:10.420 would be 42:10.420 --> 42:11.040 transparent 42:11.040 --> 42:12.420 but to sell 42:12.420 --> 42:12.540 it 42:12.540 --> 42:12.980 once again 42:12.980 --> 42:13.480 throw a little 42:13.480 --> 42:13.820 bit of a 42:13.820 --> 42:14.500 social engineering 42:14.500 --> 42:15.020 into the 42:15.020 --> 42:15.560 whole thing 42:15.560 --> 42:16.820 not only did I 42:16.820 --> 42:17.700 send Natus 42:17.700 --> 42:18.500 a text message 42:18.500 --> 42:19.380 I sent 42:19.380 --> 42:20.060 of course it was 42:20.060 --> 42:20.360 fake 42:20.360 --> 42:20.940 it was emailed 42:20.940 --> 42:21.420 to him 42:21.420 --> 42:22.000 or we talked 42:22.000 --> 42:22.460 about it over 42:22.460 --> 42:22.900 the phone 42:22.900 --> 42:24.400 I emailed it 42:24.400 --> 42:24.720 to him 42:24.720 --> 42:25.320 because 42:25.320 --> 42:27.000 I know 42:27.000 --> 42:27.620 what the limits 42:27.620 --> 42:28.460 of a text message 42:28.460 --> 42:29.180 are and how many 42:29.180 --> 42:29.980 texts you can send 42:29.980 --> 42:30.660 on one line 42:30.660 --> 42:31.200 before it does 42:31.200 --> 42:31.820 a line break 42:31.820 --> 42:32.320 it's not a 42:32.320 --> 42:33.140 continuous thing 42:33.140 --> 42:33.800 it's not easy 42:33.800 --> 42:34.480 to put everything 42:34.480 --> 42:35.280 together like an 42:35.280 --> 42:35.520 email 42:35.520 --> 42:36.780 so I sent 42:36.780 --> 42:37.280 it as though 42:37.280 --> 42:37.740 it were in 42:37.740 --> 42:38.580 four or five 42:38.580 --> 42:39.360 different separate 42:39.360 --> 42:40.080 text messages 42:40.080 --> 42:40.740 because I didn't 42:40.740 --> 42:41.140 have enough 42:41.140 --> 42:41.980 space to type 42:41.980 --> 42:42.320 it out 42:42.320 --> 42:43.740 I also threw 42:43.740 --> 42:44.260 in some 42:44.260 --> 42:45.400 I won't say 42:45.400 --> 42:46.020 leet speak 42:46.020 --> 42:46.500 I threw in 42:46.500 --> 42:47.000 some text 42:47.000 --> 42:47.420 speak 42:47.420 --> 42:48.740 because you 42:48.740 --> 42:49.060 know when 42:49.060 --> 42:49.400 you're typing 42:49.400 --> 42:49.780 from those 42:49.780 --> 42:50.440 thumb keyboards 42:50.440 --> 42:50.860 you want to 42:50.860 --> 42:51.380 take shortcuts 42:51.380 --> 42:52.040 and you use 42:52.040 --> 42:52.340 a lot of 42:52.340 --> 42:52.900 initials and 42:52.900 --> 42:53.320 what not 42:53.320 --> 42:54.320 make all the 42:54.320 --> 42:54.880 jokes about 42:54.880 --> 42:55.560 my space 42:55.560 --> 42:56.180 and teenage 42:56.180 --> 42:56.920 girls texting 42:56.920 --> 42:57.320 each other 42:57.320 --> 42:57.800 you want 42:57.800 --> 42:59.040 it's true 42:59.040 --> 43:00.000 especially in 43:00.000 --> 43:00.760 my circumstances 43:00.760 --> 43:01.320 so I sent 43:01.320 --> 43:01.920 a message 43:01.920 --> 43:02.880 saying to the 43:02.880 --> 43:03.400 effect of 43:03.400 --> 43:04.260 don't have a 43:04.260 --> 43:04.680 lot of time 43:04.680 --> 43:05.200 to talk 43:05.200 --> 43:05.820 of course 43:05.820 --> 43:06.960 and abbreviated 43:06.960 --> 43:07.280 and made 43:07.280 --> 43:07.500 it look 43:07.500 --> 43:08.020 chunked up 43:08.020 --> 43:09.020 all chunky 43:09.020 --> 43:09.820 because I was 43:09.820 --> 43:10.680 abbreviating words 43:10.680 --> 43:11.200 and shortening 43:11.200 --> 43:11.580 the message 43:11.580 --> 43:12.240 and keeping it 43:12.240 --> 43:12.820 all short 43:12.820 --> 43:13.220 and sweet 43:13.220 --> 43:14.420 which further 43:14.420 --> 43:15.420 sold the joke 43:15.420 --> 43:16.820 so when that 43:16.820 --> 43:17.300 went up on 43:17.300 --> 43:18.520 oldskifreak.com 43:18.520 --> 43:18.940 it kind of 43:18.940 --> 43:19.780 reintroduced people 43:19.780 --> 43:20.360 going wow 43:20.360 --> 43:20.860 that looks 43:20.860 --> 43:21.860 kind of real 43:21.860 --> 43:22.360 like a real 43:22.360 --> 43:23.000 text message 43:23.000 --> 43:23.600 maybe it isn't 43:23.600 --> 43:23.980 a joke 43:23.980 --> 43:25.200 so most people 43:25.200 --> 43:25.920 probably know 43:25.920 --> 43:26.240 it is 43:26.240 --> 43:26.700 but just 43:26.700 --> 43:27.160 planting that 43:27.160 --> 43:27.880 seed of doubt 43:27.880 --> 43:28.800 helps and 43:28.800 --> 43:29.520 makes the whole 43:29.520 --> 43:30.000 process 43:30.000 --> 43:30.840 makes it fun 43:30.840 --> 43:31.840 having a little 43:31.840 --> 43:32.640 fun with everybody 43:32.640 --> 43:33.460 settle down 43:33.460 --> 43:34.420 don't freak out 43:34.420 --> 43:35.380 so sorry 43:35.380 --> 43:35.720 that you're 43:35.720 --> 43:36.140 without your 43:36.140 --> 43:36.740 forms for a 43:36.740 --> 43:36.960 day 43:36.960 --> 43:37.980 or you can't 43:37.980 --> 43:38.360 deal with 43:38.360 --> 43:38.840 having the 43:38.840 --> 43:39.600 Spongebob 43:39.600 --> 43:40.260 Squarepants 43:40.260 --> 43:40.940 theme on 43:40.940 --> 43:41.220 there 43:41.220 --> 43:42.580 you'll live 43:42.580 --> 43:42.840 with it 43:42.840 --> 43:43.340 for a day 43:43.340 --> 43:43.860 a day and a 43:43.860 --> 43:44.100 half 43:44.100 --> 43:44.480 until I 43:44.480 --> 43:44.960 came back 43:44.960 --> 43:46.300 which kind of 43:46.300 --> 43:46.780 brings us to 43:46.780 --> 43:47.300 this year's 43:47.300 --> 43:47.640 prank 43:47.640 --> 43:48.140 which is 43:48.140 --> 43:49.020 I gotta say 43:49.020 --> 43:49.720 I pulled a 43:49.720 --> 43:49.940 little 43:49.940 --> 43:51.220 got a little 43:51.220 --> 43:52.000 revenge for our 43:52.000 --> 43:52.800 users if you 43:52.800 --> 43:53.000 will 43:53.000 --> 43:53.800 let me explain 43:53.800 --> 43:55.460 the other thing 43:55.460 --> 43:55.900 I do is 43:55.900 --> 43:56.600 if I'm in 43:56.600 --> 43:57.120 IRC or 43:57.120 --> 43:57.440 something 43:57.440 --> 43:58.500 you know 43:58.500 --> 43:59.940 I try not 43:59.940 --> 44:00.460 to lie 44:00.460 --> 44:01.500 I try to 44:01.500 --> 44:02.220 avoid lying 44:02.220 --> 44:02.600 to people 44:02.600 --> 44:03.100 I've never 44:03.100 --> 44:03.660 come out 44:03.660 --> 44:04.060 and lied 44:04.060 --> 44:04.480 about any 44:04.480 --> 44:04.660 of our 44:04.660 --> 44:05.200 April Fool's 44:05.200 --> 44:05.400 joke 44:05.400 --> 44:05.780 if people 44:05.780 --> 44:06.200 ask me 44:06.200 --> 44:06.620 questions 44:06.620 --> 44:07.000 I'll 44:07.000 --> 44:08.200 use some 44:08.200 --> 44:08.940 social engineering 44:08.940 --> 44:09.540 skills to 44:09.540 --> 44:10.300 sidestep the 44:10.300 --> 44:10.740 question 44:10.740 --> 44:11.480 redirect the 44:11.480 --> 44:11.960 question 44:11.960 --> 44:12.820 choose my 44:12.820 --> 44:13.420 words carefully 44:13.420 --> 44:13.760 and the 44:13.760 --> 44:14.180 answer 44:14.180 --> 44:15.360 for example 44:15.360 --> 44:16.140 I was asked 44:16.140 --> 44:17.440 directly in 44:17.440 --> 44:18.180 IRC this 44:18.180 --> 44:18.500 year 44:18.500 --> 44:19.380 whether 44:19.380 --> 44:21.640 the site 44:21.640 --> 44:22.180 being hacked 44:22.180 --> 44:22.740 this year 44:22.740 --> 44:24.380 was my 44:24.380 --> 44:25.080 April Fool's 44:25.080 --> 44:25.580 day joke 44:25.580 --> 44:26.800 which I can 44:26.800 --> 44:27.720 honestly answer 44:27.720 --> 44:28.100 and say 44:28.100 --> 44:28.480 no 44:28.480 --> 44:29.220 no 44:29.220 --> 44:29.820 it is not 44:29.820 --> 44:30.080 my 44:30.080 --> 44:30.760 April Fool's 44:30.760 --> 44:31.260 day joke 44:31.260 --> 44:33.260 it is your 44:33.260 --> 44:34.300 moderating team's 44:34.300 --> 44:35.020 April Fool's 44:35.020 --> 44:35.480 day joke 44:35.480 --> 44:36.120 I had nothing 44:36.120 --> 44:36.780 to do with it 44:36.780 --> 44:38.140 I was completely 44:38.140 --> 44:39.080 honest in answering 44:39.080 --> 44:39.580 the question 44:39.580 --> 44:40.220 and when people 44:40.220 --> 44:40.780 ask me other 44:40.780 --> 44:41.680 things I can 44:41.680 --> 44:42.180 dodge the 44:42.180 --> 44:42.660 question and 44:42.660 --> 44:43.160 say no 44:43.160 --> 44:44.340 I honestly 44:44.340 --> 44:44.960 can say that 44:44.960 --> 44:45.380 I did not 44:45.380 --> 44:45.840 do that 44:45.840 --> 44:47.000 one thing I 44:47.000 --> 44:47.660 did admit to 44:47.660 --> 44:48.100 and did up 44:48.100 --> 44:48.740 front was 44:48.740 --> 44:49.680 change the 44:49.680 --> 44:50.160 form skin 44:50.160 --> 44:50.520 to the 44:50.520 --> 44:51.420 Spongebob 44:51.420 --> 44:52.100 Squarepants 44:52.100 --> 44:52.600 form skin 44:52.600 --> 44:53.100 for a day 44:53.100 --> 44:53.700 again 44:53.700 --> 44:54.140 tradition 44:54.140 --> 44:54.600 every year 44:54.600 --> 44:54.980 we put up 44:54.980 --> 44:55.420 some funny 44:55.420 --> 44:55.860 skin of 44:55.860 --> 44:56.340 some kind 44:56.340 --> 44:57.180 we have a 44:57.180 --> 44:57.520 little fun 44:57.520 --> 44:58.060 doing that 44:58.060 --> 44:58.980 and I 44:58.980 --> 44:59.440 actually put 44:59.440 --> 44:59.820 that up 44:59.820 --> 45:00.100 probably 45:00.100 --> 45:00.880 10 o'clock 45:00.880 --> 45:01.420 10.30 45:01.420 --> 45:01.800 the night 45:01.800 --> 45:02.240 before 45:02.240 --> 45:03.100 I went 45:03.100 --> 45:03.480 to bed 45:03.480 --> 45:04.780 and I 45:04.780 --> 45:05.060 did it 45:05.060 --> 45:05.640 in IRC 45:05.640 --> 45:05.980 and I 45:05.980 --> 45:06.480 purposely 45:06.480 --> 45:08.120 was verbal 45:08.120 --> 45:08.760 about it 45:08.760 --> 45:09.000 I was 45:09.000 --> 45:09.380 purposely 45:09.380 --> 45:10.080 boisterous 45:10.080 --> 45:10.460 saying 45:10.460 --> 45:11.140 is it 45:11.140 --> 45:11.780 April Fool's 45:11.780 --> 45:12.020 I'm going 45:12.020 --> 45:12.280 to go ahead 45:12.280 --> 45:12.480 and pull 45:12.480 --> 45:12.860 my prank 45:12.860 --> 45:13.040 now 45:13.040 --> 45:13.220 and go 45:13.220 --> 45:13.580 to bed 45:13.580 --> 45:13.940 and I 45:13.940 --> 45:14.320 dropped 45:14.320 --> 45:15.380 the skin 45:15.380 --> 45:15.940 into place 45:15.940 --> 45:16.140 so that 45:16.140 --> 45:16.360 everybody 45:16.360 --> 45:16.840 saw it 45:16.840 --> 45:17.420 and that 45:17.420 --> 45:17.820 plants 45:17.820 --> 45:18.360 the seed 45:18.360 --> 45:18.680 that 45:18.680 --> 45:19.440 oh 45:19.440 --> 45:19.800 that's 45:19.800 --> 45:20.100 all he's 45:20.100 --> 45:20.300 doing 45:20.300 --> 45:20.720 this year 45:20.720 --> 45:21.200 is changing 45:21.200 --> 45:21.720 the skin 45:21.720 --> 45:22.160 and then 45:22.160 --> 45:22.540 I'm out 45:22.540 --> 45:23.440 well that 45:23.440 --> 45:23.900 is kind 45:23.900 --> 45:24.140 of all 45:24.140 --> 45:24.600 I was 45:24.600 --> 45:24.920 doing 45:24.920 --> 45:25.680 but of 45:25.680 --> 45:26.000 course I 45:26.000 --> 45:26.220 knew 45:26.220 --> 45:26.480 that your 45:26.480 --> 45:26.900 moderating 45:26.900 --> 45:27.140 team 45:27.140 --> 45:27.580 had much 45:27.580 --> 45:28.000 bigger 45:28.000 --> 45:28.860 and better 45:28.860 --> 45:29.360 plans 45:29.360 --> 45:30.420 for you 45:30.420 --> 45:31.580 and their 45:31.580 --> 45:32.020 plans 45:32.020 --> 45:32.560 actually we 45:32.560 --> 45:32.900 brought it 45:32.900 --> 45:33.460 up in the 45:33.460 --> 45:34.420 moderators 45:34.420 --> 45:34.820 forum 45:34.820 --> 45:36.400 a long 45:36.400 --> 45:36.920 time ahead 45:36.920 --> 45:37.380 even a couple 45:37.380 --> 45:37.880 months ago 45:37.880 --> 45:38.280 we talked 45:38.280 --> 45:38.700 about it 45:38.700 --> 45:38.980 and even 45:38.980 --> 45:39.580 weeks ahead 45:39.580 --> 45:39.880 when we 45:39.880 --> 45:40.140 made a 45:40.140 --> 45:40.440 decision 45:40.440 --> 45:40.820 what we're 45:40.820 --> 45:41.220 doing 45:41.220 --> 45:42.800 truthfully 45:42.800 --> 45:43.220 what I 45:43.220 --> 45:43.900 was going 45:43.900 --> 45:44.160 to do 45:44.160 --> 45:44.540 was put 45:44.540 --> 45:44.760 up the 45:44.760 --> 45:45.360 Spongebob 45:45.360 --> 45:46.340 and my 45:46.340 --> 45:46.960 first idea 45:46.960 --> 45:47.580 was maybe 45:47.580 --> 45:48.060 I can put 45:48.060 --> 45:48.320 up a 45:48.320 --> 45:48.620 cease and 45:48.620 --> 45:48.900 desist 45:48.900 --> 45:49.300 letter 45:49.300 --> 45:50.500 later that 45:50.500 --> 45:51.000 evening 45:51.000 --> 45:51.720 on April 45:51.720 --> 45:52.100 1st 45:52.100 --> 45:52.880 after Spongebob 45:52.880 --> 45:53.300 had been up 45:53.300 --> 45:53.640 all day 45:53.640 --> 45:54.280 saying that 45:54.280 --> 45:55.400 the Spongebob 45:55.400 --> 45:56.160 people busted 45:56.160 --> 45:56.460 me for 45:56.460 --> 45:56.860 copyright 45:56.860 --> 45:57.440 infringement 45:57.440 --> 45:58.580 even though 45:58.580 --> 45:58.860 it was up 45:58.860 --> 45:59.220 less than 45:59.220 --> 45:59.920 24 hours 45:59.920 --> 46:00.180 so I 46:00.180 --> 46:00.440 thought that 46:00.440 --> 46:00.620 would be 46:00.620 --> 46:01.040 pretty 46:01.040 --> 46:01.600 transparent 46:01.600 --> 46:01.960 but just 46:01.960 --> 46:02.220 a little 46:02.220 --> 46:02.860 fun thing 46:02.860 --> 46:03.080 nothing 46:03.080 --> 46:03.500 fancy 46:03.500 --> 46:03.860 but the 46:03.860 --> 46:04.320 mods 46:04.320 --> 46:05.460 they came 46:05.460 --> 46:05.700 up with 46:05.700 --> 46:06.500 something a 46:06.500 --> 46:06.760 little bit 46:06.760 --> 46:07.080 better 46:07.080 --> 46:08.180 and they 46:08.180 --> 46:08.620 implemented 46:08.620 --> 46:08.960 it about 46:08.960 --> 46:09.360 a week 46:09.360 --> 46:10.440 before April 46:10.440 --> 46:11.100 Fool's Day 46:11.100 --> 46:11.760 so the 46:11.760 --> 46:12.840 actual prank 46:12.840 --> 46:13.660 happened on 46:13.660 --> 46:14.080 the 1st 46:14.080 --> 46:14.580 but we had 46:14.580 --> 46:15.060 to put some 46:15.060 --> 46:15.500 time into 46:15.500 --> 46:15.980 setting it 46:15.980 --> 46:16.180 up 46:16.180 --> 46:17.960 so Ponyboy 46:17.960 --> 46:19.060 and Droops 46:19.060 --> 46:19.820 and Seal 46:19.820 --> 46:21.000 and Booter 46:21.000 --> 46:21.780 and G.I. 46:21.820 --> 46:22.120 Joe and 46:22.120 --> 46:22.800 everybody on 46:22.800 --> 46:23.300 the moderating 46:23.300 --> 46:23.540 team 46:23.540 --> 46:24.180 they all 46:24.180 --> 46:25.340 had a little 46:25.340 --> 46:25.840 hand on 46:25.840 --> 46:26.020 this 46:26.020 --> 46:26.380 they made 46:26.380 --> 46:27.360 up a 46:27.360 --> 46:28.720 user in 46:28.720 --> 46:29.160 the forums 46:29.160 --> 46:29.700 who went 46:29.700 --> 46:30.480 by Switchblade 46:30.480 --> 46:32.160 great name 46:32.160 --> 46:32.760 Lee Tized 46:32.760 --> 46:33.200 and everything 46:33.200 --> 46:33.720 who came 46:33.720 --> 46:34.040 in 46:34.040 --> 46:34.820 had the 46:34.820 --> 46:35.220 typical 46:35.220 --> 46:35.740 skiddy 46:35.740 --> 46:36.320 attitude 46:36.320 --> 46:37.040 chest 46:37.040 --> 46:37.620 pounding 46:37.620 --> 46:38.140 I'm the 46:38.140 --> 46:38.460 greatest 46:38.460 --> 46:39.120 taxor in 46:39.120 --> 46:39.540 the world 46:39.540 --> 46:40.340 kind of 46:40.340 --> 46:40.680 attitude 46:40.680 --> 46:41.120 which 46:41.120 --> 46:41.700 well you 46:41.700 --> 46:41.900 know 46:41.900 --> 46:42.320 sometimes 46:42.320 --> 46:42.900 people do 46:42.900 --> 46:43.160 that 46:43.160 --> 46:43.440 so it 46:43.440 --> 46:43.680 was an 46:43.680 --> 46:44.300 easy sell 46:44.300 --> 46:45.240 people 46:45.240 --> 46:45.840 believed it 46:45.840 --> 46:46.260 is real 46:46.260 --> 46:46.800 lots of 46:46.800 --> 46:47.360 replies to 46:47.360 --> 46:47.900 his threads 46:47.900 --> 46:48.280 that people 46:48.280 --> 46:48.720 bought it 46:48.720 --> 46:49.100 lots of 46:49.100 --> 46:49.700 PMs from 46:49.700 --> 46:50.060 people 46:50.060 --> 46:50.900 complaining 46:50.900 --> 46:51.500 about him 46:51.500 --> 46:52.640 and the 46:52.640 --> 46:52.920 mods 46:52.920 --> 46:53.340 of course 46:53.340 --> 46:53.880 behind the 46:53.880 --> 46:54.240 scenes 46:54.240 --> 46:54.840 pretending 46:54.840 --> 46:55.400 that they 46:55.400 --> 46:55.820 didn't know 46:55.820 --> 46:56.260 any better 46:56.260 --> 46:57.600 and one 46:57.600 --> 46:57.780 of the 46:57.780 --> 46:58.100 things that 46:58.100 --> 46:58.520 we agreed 46:58.520 --> 46:59.100 that we 46:59.100 --> 46:59.500 would have 46:59.500 --> 46:59.740 to do 46:59.740 --> 47:00.160 to sell 47:00.160 --> 47:00.340 it 47:00.340 --> 47:01.100 is we 47:01.100 --> 47:01.380 have to 47:01.380 --> 47:01.740 treat it 47:01.740 --> 47:02.060 as though 47:02.060 --> 47:02.480 he really 47:02.480 --> 47:02.900 were a 47:02.900 --> 47:03.140 troll 47:03.140 --> 47:04.420 so we 47:04.420 --> 47:04.980 would let 47:04.980 --> 47:05.380 the person 47:05.380 --> 47:05.960 talk for a 47:05.960 --> 47:06.380 little bit 47:06.380 --> 47:07.200 knowing that 47:07.200 --> 47:07.680 full and well 47:07.680 --> 47:08.140 that was us 47:08.140 --> 47:08.380 that was 47:08.380 --> 47:08.720 posting 47:08.720 --> 47:09.020 everybody 47:09.020 --> 47:09.480 was taking 47:09.480 --> 47:09.840 turns 47:09.840 --> 47:10.280 posting 47:10.280 --> 47:10.960 except me 47:10.960 --> 47:12.680 taking turns 47:12.680 --> 47:13.080 posting 47:13.080 --> 47:13.520 and then 47:13.520 --> 47:14.240 within a few 47:14.240 --> 47:14.780 minutes 47:14.780 --> 47:15.720 hours later 47:15.720 --> 47:17.120 ban the 47:17.120 --> 47:17.580 user like 47:17.580 --> 47:17.920 we would 47:17.920 --> 47:18.500 anybody else 47:18.500 --> 47:18.840 who broke 47:18.840 --> 47:19.340 the rules 47:19.340 --> 47:20.800 but then 47:20.800 --> 47:21.580 our good 47:21.580 --> 47:22.260 persistent 47:22.260 --> 47:22.760 hacker 47:22.760 --> 47:23.380 switchblade 47:23.380 --> 47:23.740 would go 47:23.740 --> 47:24.200 back in 47:24.200 --> 47:24.520 under a 47:24.520 --> 47:24.760 different 47:24.760 --> 47:25.080 email 47:25.080 --> 47:25.580 create a 47:25.580 --> 47:25.720 new 47:25.720 --> 47:26.080 account 47:26.080 --> 47:26.840 and come 47:26.840 --> 47:27.300 back in 47:27.300 --> 47:27.820 and continue 47:27.820 --> 47:28.100 his 47:28.100 --> 47:28.740 flamage 47:28.740 --> 47:29.520 and talking 47:29.520 --> 47:30.740 and trash 47:30.740 --> 47:31.160 talking 47:31.160 --> 47:31.720 and what not 47:31.720 --> 47:32.700 and once 47:32.700 --> 47:33.100 again we 47:33.100 --> 47:33.460 would keep 47:33.460 --> 47:34.080 handling it 47:34.080 --> 47:36.700 and the 47:36.700 --> 47:37.380 moderating team 47:37.380 --> 47:37.900 had done that 47:37.900 --> 47:38.500 quite well 47:38.500 --> 47:39.040 I must say 47:39.040 --> 47:39.500 and I even 47:39.500 --> 47:40.040 stepped in 47:40.040 --> 47:40.300 and said 47:40.300 --> 47:41.420 okay guys 47:41.420 --> 47:42.240 we're going 47:42.240 --> 47:42.480 to handle 47:42.480 --> 47:42.940 this the way 47:42.940 --> 47:43.360 we do 47:43.360 --> 47:44.040 here's the 47:44.040 --> 47:44.420 rules of 47:44.420 --> 47:44.860 the forum 47:44.860 --> 47:46.220 again at no 47:46.220 --> 47:46.720 time did I 47:46.720 --> 47:47.880 lie or say 47:47.880 --> 47:48.600 anything otherwise 47:48.600 --> 47:49.000 but 47:49.000 --> 47:49.820 played along 47:49.820 --> 47:50.180 with it 47:50.180 --> 47:50.620 tried to 47:50.620 --> 47:51.060 sell the 47:51.060 --> 47:51.540 prank as 47:51.540 --> 47:51.940 best I 47:51.940 --> 47:52.220 could 47:52.220 --> 47:53.860 and then 47:53.860 --> 47:54.340 switchblade 47:54.340 --> 47:54.980 started making 47:54.980 --> 47:55.980 his threats 47:55.980 --> 47:56.540 against the 47:56.540 --> 47:56.920 site about 47:56.920 --> 47:57.220 how he 47:57.220 --> 47:57.620 could own 47:57.620 --> 47:58.040 us all 47:58.040 --> 47:58.360 and take 47:58.360 --> 47:58.780 BinRev 47:58.780 --> 47:59.160 down 47:59.160 --> 48:00.040 well this 48:00.040 --> 48:00.300 is where 48:00.300 --> 48:00.640 the story 48:00.640 --> 48:01.140 gets fun 48:01.140 --> 48:01.640 for me 48:01.640 --> 48:02.960 and see 48:02.960 --> 48:03.900 this is where 48:03.900 --> 48:04.260 I'm looking 48:04.260 --> 48:04.540 out 48:04.540 --> 48:05.260 I'm looking 48:05.260 --> 48:06.200 out for 48:06.200 --> 48:06.640 the listeners 48:06.640 --> 48:07.180 I'm looking 48:07.180 --> 48:07.640 out for the 48:07.640 --> 48:08.040 users of 48:08.040 --> 48:08.380 our site 48:08.380 --> 48:08.940 this is where 48:08.940 --> 48:09.580 I stepped 48:09.580 --> 48:10.040 in and said 48:10.040 --> 48:10.600 okay 48:10.600 --> 48:12.120 pulling a 48:12.120 --> 48:12.680 prank on our 48:12.680 --> 48:13.520 users is one 48:13.520 --> 48:13.960 thing 48:13.960 --> 48:15.500 but do the 48:15.500 --> 48:16.160 mods really 48:16.160 --> 48:16.740 think that 48:16.740 --> 48:17.040 they're going 48:17.040 --> 48:17.800 to get away 48:17.800 --> 48:18.740 with pulling 48:18.740 --> 48:19.460 this off 48:19.460 --> 48:20.480 and be 48:20.480 --> 48:21.200 immune from 48:21.200 --> 48:21.560 an April 48:21.560 --> 48:22.040 Fool's Day 48:22.040 --> 48:22.960 prank themselves 48:22.960 --> 48:24.560 no no no no 48:24.560 --> 48:25.200 no no I 48:25.200 --> 48:25.860 can't let that 48:25.860 --> 48:26.360 happen 48:26.360 --> 48:27.560 I'm trying to 48:27.560 --> 48:28.140 look out for 48:28.140 --> 48:28.740 everybody right 48:28.740 --> 48:29.140 I'm trying to 48:29.140 --> 48:29.540 look out for 48:29.540 --> 48:29.900 y'all they're 48:29.900 --> 48:30.180 not going to 48:30.180 --> 48:30.820 be immune to 48:30.820 --> 48:31.160 this 48:31.160 --> 48:33.700 so I didn't 48:33.700 --> 48:34.500 let anybody else 48:34.500 --> 48:34.960 know about 48:34.960 --> 48:35.620 this I just 48:35.620 --> 48:36.060 came up with 48:36.060 --> 48:36.440 the idea 48:36.440 --> 48:37.260 myself that 48:37.260 --> 48:37.780 said you know 48:37.780 --> 48:38.300 what I'm going 48:38.300 --> 48:39.520 to do the 48:39.520 --> 48:40.100 mods are having 48:40.100 --> 48:40.900 a lot of fun 48:40.900 --> 48:41.500 at the expense 48:41.500 --> 48:42.160 of the users 48:42.160 --> 48:43.040 I did give 48:43.040 --> 48:43.620 them one rule 48:43.620 --> 48:44.040 I said they 48:44.040 --> 48:44.520 can't put the 48:44.520 --> 48:45.140 switchblade guy 48:45.140 --> 48:45.560 in the newbie 48:45.560 --> 48:46.400 HQ because I 48:46.400 --> 48:46.820 do want to 48:46.820 --> 48:47.180 keep that 48:47.180 --> 48:48.360 clean and I 48:48.360 --> 48:48.900 told them that 48:48.900 --> 48:49.300 any of the 48:49.300 --> 48:49.920 trash talking 48:49.920 --> 48:50.460 stuff that he 48:50.460 --> 48:51.560 does eventually 48:51.560 --> 48:52.380 I want it moved 48:52.380 --> 48:53.040 as quickly as 48:53.040 --> 48:53.580 possible and 48:53.580 --> 48:54.180 treated like we 48:54.180 --> 48:54.560 would normally 48:54.560 --> 48:55.100 do and move it 48:55.100 --> 48:56.100 to the to the 48:56.100 --> 48:56.660 bit box 48:56.660 --> 48:58.480 well what I 48:58.480 --> 49:00.280 did is on 49:00.280 --> 49:01.000 April Fool's Day 49:01.000 --> 49:01.600 that morning 49:01.600 --> 49:03.280 the mods were 49:03.280 --> 49:04.280 just having fun 49:04.280 --> 49:05.060 still posting 49:05.060 --> 49:05.940 whatnot posting 49:05.940 --> 49:07.080 things right 49:07.080 --> 49:08.040 coast made up a 49:08.040 --> 49:09.020 fake hacked page 49:09.020 --> 49:09.620 for us to put on 49:09.620 --> 49:10.400 the site once I 49:10.400 --> 49:11.180 got that from him 49:11.180 --> 49:11.740 it was time to 49:11.740 --> 49:12.840 implement my 49:12.840 --> 49:13.640 April Fool's Day 49:13.640 --> 49:15.340 prank and my 49:15.340 --> 49:16.100 April Fool's Day 49:16.100 --> 49:17.000 prank was to 49:17.000 --> 49:18.000 you know they've 49:18.000 --> 49:18.640 already created 49:18.640 --> 49:19.460 switchblade they've 49:19.460 --> 49:20.100 done all the hard 49:20.100 --> 49:21.760 work all I got to 49:21.760 --> 49:22.780 do is go in 49:22.780 --> 49:24.120 abuse my admin 49:24.120 --> 49:26.320 powers and ban 49:26.320 --> 49:26.840 the entire 49:26.840 --> 49:27.740 moderating team 49:27.740 --> 49:29.000 under the name 49:29.000 --> 49:29.700 switchblade of 49:29.700 --> 49:31.460 course so I made 49:31.460 --> 49:32.340 it appear as though 49:32.340 --> 49:33.940 switchblade banned 49:33.940 --> 49:34.500 the entire 49:34.500 --> 49:35.400 moderating team 49:35.400 --> 49:36.280 and Iron Geek as 49:36.280 --> 49:36.900 well who was in 49:36.900 --> 49:37.500 there talking a 49:37.500 --> 49:38.020 little trash who 49:38.020 --> 49:38.940 was also in on 49:38.940 --> 49:39.180 it 49:39.180 --> 49:43.260 so alright well 49:43.260 --> 49:44.180 you know what's 49:44.180 --> 49:44.880 good for the goose 49:44.880 --> 49:45.500 is good for the 49:45.500 --> 49:46.240 gander I had 49:46.240 --> 49:47.040 country talk what 49:47.040 --> 49:47.540 can I tell you 49:47.540 --> 49:49.140 I banned all the 49:49.140 --> 49:50.140 moderating team so 49:50.140 --> 49:51.080 no moderators had 49:51.080 --> 49:51.700 access to the 49:51.700 --> 49:52.880 forums on April 1st 49:52.880 --> 49:53.540 and actually well 49:53.540 --> 49:54.480 into April 2nd 49:54.480 --> 49:55.680 truth be told and 49:55.680 --> 49:56.300 I changed the 49:56.300 --> 49:57.320 admin password so 49:57.320 --> 49:58.800 that even Seal the 49:58.800 --> 49:59.620 forums administrator 49:59.620 --> 50:00.480 could not get in 50:00.480 --> 50:01.320 there sorry Seal had 50:01.320 --> 50:03.320 to do it sorry I 50:03.320 --> 50:03.820 had to have a little 50:03.820 --> 50:04.380 bit of fun at 50:04.380 --> 50:05.560 everybody's expense so 50:05.560 --> 50:07.020 everybody that was 50:07.020 --> 50:08.400 in the forums was 50:08.400 --> 50:09.120 complaining and 50:09.120 --> 50:09.680 wondering if 50:09.680 --> 50:10.340 switchblade did he 50:10.340 --> 50:11.100 really hack it you 50:11.100 --> 50:12.060 had that believability 50:12.060 --> 50:13.040 factor you had that 50:13.040 --> 50:15.060 maybe it's true you 50:15.060 --> 50:15.820 had all that stuff 50:15.820 --> 50:17.940 going on and the 50:17.940 --> 50:18.840 moderators didn't seem 50:18.840 --> 50:19.480 to be doing anything 50:19.480 --> 50:21.340 about it and then I 50:21.340 --> 50:22.240 logged in and started 50:22.240 --> 50:23.320 posting a switchblade 50:23.320 --> 50:24.900 saying hey I've owned 50:24.900 --> 50:25.680 all the moderators 50:25.680 --> 50:26.620 accounts I started 50:26.620 --> 50:28.300 changing their signature 50:28.300 --> 50:29.300 files I started 50:29.300 --> 50:30.380 reactivating the 50:30.380 --> 50:31.360 switchblade accounts 50:31.360 --> 50:32.680 saying that switchblade 50:32.680 --> 50:33.660 had gotten root to the 50:33.660 --> 50:34.860 site which also sold 50:34.860 --> 50:36.440 the believability that he 50:36.440 --> 50:37.500 had hacked the site it 50:37.500 --> 50:38.560 made it possible it made 50:38.560 --> 50:39.640 it believable which was 50:39.640 --> 50:40.860 the only goal I don't 50:40.860 --> 50:41.740 expect everybody to 50:41.740 --> 50:42.500 believe it I expect 50:42.500 --> 50:43.360 everybody to have fun 50:43.360 --> 50:45.400 and laugh at it so I 50:45.400 --> 50:46.700 think that was something 50:46.700 --> 50:47.460 that we accomplished 50:47.460 --> 50:50.700 pretty well so I went to 50:50.700 --> 50:52.480 bed that night and agree 50:52.480 --> 50:54.100 that yes I left the forum 50:54.100 --> 50:55.040 skin up and the hacked 50:55.040 --> 50:56.220 page up overnight I 50:56.220 --> 50:57.060 didn't take it down till 50:57.060 --> 50:57.860 the next day when I got 50:57.860 --> 50:58.720 home from work so it did 50:58.720 --> 50:59.600 go a little longer than 50:59.600 --> 51:00.640 the first it went into the 51:00.640 --> 51:02.900 second by a few hours but I 51:02.900 --> 51:04.040 cleaned it up then gave the 51:04.040 --> 51:05.420 moderators their powers back 51:05.420 --> 51:06.800 to a nice little message 51:06.800 --> 51:07.820 waiting for them I also 51:07.820 --> 51:09.600 sent them all if anybody 51:09.600 --> 51:10.920 cares just because I am an 51:10.920 --> 51:12.500 ass I sent them all an 51:12.500 --> 51:14.440 email from the administrator 51:14.440 --> 51:17.340 as switchblade saying boom 51:17.340 --> 51:20.240 headshot so they all enjoyed 51:20.240 --> 51:22.620 that so moderators sorry you 51:22.620 --> 51:23.800 got caught up in the crossfire 51:23.800 --> 51:24.620 but you know what that's what 51:24.620 --> 51:25.460 you get from messing with my 51:25.460 --> 51:28.680 people only I can mess with my 51:28.680 --> 51:30.000 people you see what I'm saying 51:30.000 --> 51:33.040 here so anyway that was pretty 51:33.040 --> 51:34.280 much what happened I even 51:34.280 --> 51:35.940 went to sell the hacked page 51:35.940 --> 51:36.960 a little bit better I got 51:36.960 --> 51:39.300 on cleared the hacked page up 51:39.300 --> 51:40.880 put my original page back for 51:40.880 --> 51:43.280 a few hours so that people 51:43.280 --> 51:44.560 saw that we were actually 51:44.560 --> 51:45.840 trying to fix it because if 51:45.840 --> 51:46.600 somebody hacked the site 51:46.600 --> 51:47.780 everybody knows I'm going to 51:47.780 --> 51:48.920 get on and investigate and 51:48.920 --> 51:50.000 fix it and get it back up and 51:50.000 --> 51:51.100 running if I left it up all 51:51.100 --> 51:53.160 day it's obvious so I went on 51:53.160 --> 51:54.460 there after a couple hours and 51:54.460 --> 51:55.960 fixed it quote unquote fixed 51:55.960 --> 51:58.120 it which meant put the original 51:58.120 --> 51:59.880 page back and then a few more 51:59.880 --> 52:01.240 hours after that I put up yet 52:01.240 --> 52:02.560 another hacked page with new 52:02.560 --> 52:04.080 comments on it as though 52:04.080 --> 52:05.380 switchblade had re-hacked the 52:05.380 --> 52:07.240 site so went back and forth a 52:07.240 --> 52:08.820 few times to sell it as well so 52:08.820 --> 52:10.320 I think a few people bought it 52:10.320 --> 52:11.440 a little bit even if they don't 52:11.440 --> 52:12.960 admit it and may not have 52:12.960 --> 52:14.120 completely bought it everybody 52:14.120 --> 52:17.080 had a little fun with it so I 52:17.080 --> 52:18.060 thought that was pretty good 52:18.060 --> 52:19.280 don't know what we're going to 52:19.280 --> 52:20.440 do next year we got a year to 52:20.440 --> 52:21.620 think about it got a year ahead 52:21.620 --> 52:23.580 of time to come up with some 52:23.580 --> 52:24.980 good ideas but be prepared 52:24.980 --> 52:26.880 something's going to happen 52:26.880 --> 52:28.940 keep your eyes open you have been 52:28.940 --> 52:30.160 warned and you will forget by 52:30.160 --> 52:34.240 next year so we'll see I guess I'm 52:34.240 --> 52:35.560 going to go ahead and wrap up 52:35.560 --> 52:36.900 with that I could go into some 52:36.900 --> 52:40.700 other things I'll briefly again 52:40.700 --> 52:42.820 talk about the fact that we move 52:42.820 --> 52:46.120 servers once again so bear with us 52:46.120 --> 52:47.860 if you do have any run into any 52:47.860 --> 52:49.620 problems or any glitches any errors 52:49.620 --> 52:51.020 anything like that for the most 52:51.020 --> 52:52.540 part we are up and running on the 52:52.540 --> 52:54.920 new boxes mail does seem to be 52:54.920 --> 52:56.080 working it was a much smoother 52:56.080 --> 52:58.300 transition this time Nick 84 and I 52:58.300 --> 53:00.600 split the workload up and of 53:00.600 --> 53:02.540 course the the support from 53:02.540 --> 53:04.260 caro.net was really helpful 53:04.260 --> 53:05.440 getting this box set up 53:05.440 --> 53:06.980 initially configure it the way we 53:06.980 --> 53:08.700 wanted so all that went fairly 53:08.700 --> 53:11.980 well so we will probably go into 53:11.980 --> 53:13.900 some more detail on that later but 53:13.900 --> 53:15.480 right now we are very happy with 53:15.480 --> 53:17.580 what we've got so I guess with that 53:17.580 --> 53:21.360 I'll segue into the shouts I will 53:21.360 --> 53:22.640 of course go ahead I'll give shouts 53:22.640 --> 53:23.640 to Hesham and Russell and 53:23.640 --> 53:24.980 everybody over caro.net for 53:24.980 --> 53:26.240 helping us get moved over to the 53:26.240 --> 53:28.080 new server the last host sucked 53:28.080 --> 53:29.960 pretty bad so definitely give them 53:29.960 --> 53:32.920 shouts out and to Natus to Thomas 53:32.920 --> 53:34.860 Icom to Acidus all of them had 53:34.860 --> 53:36.800 articles in the current 2600 53:36.800 --> 53:38.380 magazine I noticed so I've got that 53:38.380 --> 53:39.800 sitting here might be my reading for 53:39.800 --> 53:41.520 tonight while you're listening to 53:41.520 --> 53:43.280 the show because this is boy I got 53:43.280 --> 53:44.580 to start mixing this to get this up 53:44.580 --> 53:47.000 tonight that's how close I cut it 53:47.000 --> 53:49.140 and that's how dedicated I am to get 53:49.140 --> 53:52.320 BinRev Radio back on the in the 53:52.320 --> 53:54.420 tubes I guess not on the air in the 53:54.420 --> 53:57.000 tubes or something like that so yeah 53:57.000 --> 53:58.600 as mentioned earlier binary 53:58.600 --> 54:00.420 revolution radios hosting is 54:00.420 --> 54:02.480 provided by caro.net so check them 54:02.480 --> 54:04.480 out and that'll give me an easy site 54:04.480 --> 54:06.040 of the week so I can be lazy and say 54:06.040 --> 54:09.860 www.caro.net cool because they're 54:09.860 --> 54:11.160 their own data center which I also 54:11.160 --> 54:12.600 like a lot their own data center so I 54:12.600 --> 54:14.240 don't have any more resellers which 54:14.240 --> 54:16.600 are our last host that was one of the 54:16.600 --> 54:18.460 problems is they're a reseller so they 54:18.460 --> 54:19.860 don't have physical access to a lot of 54:19.860 --> 54:21.300 things and frankly they don't care 54:21.300 --> 54:23.540 they well anyway that's a long story 54:23.540 --> 54:26.560 we'll go into that later email us if 54:26.560 --> 54:28.020 you have feedback of any kind radio 54:28.020 --> 54:31.700 at binrev.com as always our closing 54:31.700 --> 54:34.900 music from tonight nice treat MC 54:34.900 --> 54:37.620 Frontalot my good friend this is the 54:37.620 --> 54:39.320 title track from his new album it's 54:39.320 --> 54:41.900 called secrets from the future go order 54:41.900 --> 54:44.140 the new album frontalot.com it is 54:44.140 --> 54:45.640 awesome I've been listening to the 54:45.640 --> 54:47.540 advanced copy for a while now the gold 54:47.540 --> 54:49.260 it is available on the site to order 54:49.260 --> 54:52.800 now so go buy this album it's really 54:52.800 --> 54:54.640 good it's got some great tracks on it 54:54.640 --> 54:56.580 this is the title track secrets from 54:56.580 --> 54:59.660 the future and closing the show out we 54:59.660 --> 55:01.540 lied I guess that makes me a liar last 55:01.540 --> 55:03.220 week our closing phrase last time we 55:03.220 --> 55:06.140 said next week obviously it wasn't next 55:06.140 --> 55:08.320 week just what three weeks later a 55:08.320 --> 55:11.040 month later but we will close out the 55:11.040 --> 55:12.340 show this week to tell you that 55:12.340 --> 55:14.960 hopefully we'll see you next week 55:14.960 --> 55:17.900 same hack time same hack channel 55:17.900 --> 55:27.580 get your most closely kept personal 55:27.580 --> 55:29.960 plot put it in the word block for the 55:29.960 --> 55:32.460 password block socket deep in the raw 55:32.460 --> 55:34.440 with extraction precluded by the 55:34.440 --> 55:36.560 ludicrous length and the strength of a 55:36.560 --> 55:39.000 reputed little dictionary attack proof 55:39.000 --> 55:41.520 string of characters this imperative to 55:41.520 --> 55:43.960 what all that is beverages of privacy the 55:43.960 --> 55:47.120 the NSA and homeliness you better pgp the 55:47.120 --> 55:48.960 raw because so far they ain't impressed 55:48.960 --> 55:50.900 you better take the pgp and print the 55:50.900 --> 55:53.460 hex of it out scan that into a tiff 55:53.460 --> 55:55.740 then if you secret out for your data 55:55.740 --> 55:58.060 scramble up the order of the pixels 55:58.060 --> 55:59.940 with a one-time pad that describes the 55:59.940 --> 56:01.780 fun time had like a thick soul boot 56:01.780 --> 56:03.560 wearing stomper who dance to produce 56:03.560 --> 56:05.780 random clap trap all the intervals in 56:05.780 --> 56:07.620 between which set in tandem with the 56:07.620 --> 56:09.640 stomps themselves we gotta see the mouth 56:09.640 --> 56:11.920 unguessable and no complaint about the 56:11.920 --> 56:14.080 cypher that's redressable best of all your 56:14.080 --> 56:15.080 secret nothing that could date could 56:15.080 --> 56:16.920 extract it by twenty twenty five a 56:16.920 --> 56:18.920 children speak and spell could crack it 56:18.920 --> 56:21.920 you can't hide secrets from the future we 56:21.920 --> 56:23.920 fast you can try but i bet that in the 56:23.920 --> 56:26.920 future they laugh at the half fast schemes and 56:26.920 --> 56:31.920 algorithms amassed to enforce cryptographs in the past 56:31.920 --> 56:33.920 you can't hide secrets from the future we 56:33.920 --> 56:36.920 fast you can try but i bet that in the future they 56:36.920 --> 56:41.920 laugh at the half fast schemes and algorithms amassed to enforce cryptographs in the past 56:41.920 --> 56:48.920 and future people do not give a damn about your shopping your visa number SSL to cherry 56:48.920 --> 56:51.920 popping hot ramp for action websites that you visit 56:51.920 --> 56:55.920 more password protected partitions no matter how illicit and this it would seem 56:55.920 --> 57:00.920 is your saving grace like amazing haste to people to forget your name your face 57:00.920 --> 57:10.920 your lit in this list of indefensible indiscretions in fact the only way that you can pray to make impression on the era ahead is if instead of being notable you make the data describing your face 57:10.920 --> 57:39.920 describing you undecodable for script kiddy sexting in that relic called the internet seeking latches on treasure chest that they could reckon seconds would be in yet get a chance to queue up for disassembly to discover and crack the cover like a cumberland they'll glance you over i guess and then for a bad moment you'll persist you exist almost seem like you're there don't it but you're not you're here your name will fade as friends will that since the future they don't know our crypt to bury it and still you can't hide secrets from the future 57:39.920 --> 57:42.920 in the past 57:42.920 --> 57:47.920 in the past 57:47.920 --> 57:56.920 now it's an enigma machine my code yelled out it hot long into a tin can with a thin string and that ain't it 57:56.920 --> 58:01.080 And now the river's a mess to enforce cryptographs in the past. 58:03.560 --> 58:05.340 Now it's an enigma machine. 58:05.940 --> 58:09.180 A code yelled out at hot bong into a tin can with a thin string. 58:09.300 --> 58:13.280 And that ain't all you do to broadcast clear text of all intentions. 58:13.500 --> 58:18.620 Send an email to the government pledging your abstention from vote fraud this time, next time. 58:18.740 --> 58:22.360 Can't promise you don't get a visit on the deep off in a piranet. 58:22.440 --> 58:24.260 Be honest, you ain't hacking those. 58:24.260 --> 58:28.340 It'd be too easy setting up the next president, pretending that you were through with reason. 58:28.460 --> 58:31.120 When you're nothing but warming up to do list in your diary. 58:31.300 --> 58:32.440 Better keep for a long time. 58:32.480 --> 58:37.080 In the long time, better be tiring into the distribution of electrical brains. 58:37.180 --> 58:39.960 That's a guessing every unsalted hash that ever came. 58:40.100 --> 58:42.620 They got alien technology to make the rainbow tables. 58:42.740 --> 58:45.260 Get in an afternoon, a dance, and have them secrets. 58:45.400 --> 58:49.100 Don't resist the loving codes of the mathematical calculation. 58:49.400 --> 58:52.380 Heart of your mystery sent free-fall into palpitation. 58:52.380 --> 58:55.340 Computernal rise up in the dump for free agent. 58:55.460 --> 58:56.440 Nobody knows the future. 58:56.560 --> 58:58.380 Now go find out, be patient. 58:58.420 --> 59:03.480 phonedal rise up in the dump for free agent. 59:04.200 --> 59:04.840 You're a delegate. 59:04.960 --> 59:07.500 I can't hide secrets from character with mind. 59:07.560 --> 59:10.460 You can try with the myth that you can perturb the map. 59:10.580 --> 59:13.160 Half-life schemes and are looking out this way. 59:13.720 --> 59:15.240 Parades from the picture. 59:16.420 --> 59:18.940 You have had secrets from the picture. 59:19.200 --> 59:21.140 Parades from the picture. 59:21.620 --> 59:23.940 A hunter that you can throw the map. 59:23.940 --> 59:47.160 From the secrets from the future. 59:53.940 --> 01:00:05.980 no, no, no, no, no, no, no