[00:29] Kind of surprised the public interest hasn't resulted in unnecessary arguments/wiki edits on github. Also a good thing. [01:07] Oh yeah, winr4r, you stopped working on screenshots? [01:53] once again... [02:38] maybe ill go find something to do, bros [02:38] good luch [02:38] luck [02:38] .. [02:40] good luchadore [02:42] mmm [02:42] my first "waiting for admin" task [03:39] bros, when do you think it is gonna all go to shit [03:46] vagrant is pretty sweet [03:46] too bad it requires virtualbox (for now) [03:47] SOMEONE MAKE A NEW THREADDDD , good way to get shot [03:47] mistym: I've noticed that public exposure to Github doesn't seem to attract a lot of stupid [03:47] yipdw: Vagrant? [03:47] mistym: http://vagrantup.com/ [03:47] Thanks! [03:47] it generates VMs [03:47] yipdw: It's true! I remember seeing one or two places where things started to degenerate, but in general it's pretty good. [03:47] Travis CI uses it to provision VMs for builsd [03:47] builds [03:47] Well, very good. [03:48] mistym: I think people see "omg code" and leave [03:48] Hehe. I guess the bar to entry is higher. [03:48] github is the world's worst dating site [03:49] It does have lots of forking, though. [03:49] Aw. The infamous bumblebee commit is no more. The commit comments were hilarious. [03:50] It's gone? [03:50] That thing was hilarious [03:51] it's still around [03:51] I think [03:52] lol [03:53] http://www.google.com/search?q=a047be85247755cdbe0acce6f1dafc8beb84f2ac [03:53] MOST FAMOUS SHA1 EVER [03:53] Hah! [03:53] mistym: https://github.com/MrMEEE/bumblebee-Old-and-abbandoned/commit/a047be85247755cdbe0acce6f1dafc8beb84f2ac [03:53] You're right, project changed names. It's still there! :D [03:57] I found it weird that the Chinese started getting in on that [03:57] maybe I should github-backup that repo [03:58] I'm already wget-backup'ing the page :P [03:58] ...and done. [03:59] yipdw: Backing up the repo won't get you the comments ;) [03:59] oh [03:59] or starbucks to pick up some new music [03:59] damn [04:01] is belgravia a chatbot? [04:01] ???, yipdw [04:01] Maybe they just like bros a lot. [04:02] 21:02:34 [EFNet] -!- belgravia [Surbiton@c-69-143-107-126.hsd1.va.comcast.net] [04:02] 21:02:34 [EFNet] -!- ircname : belgravia [04:02] 21:02:34 [EFNet] -!- channels : +#Famous #ircbar #hinduism #herpederpo #heroin #hardware #gearsbeta #gearsales #g #fw #free60 #football #fiber-hosting #efnut #efnet #dvdr #dust #diablo3 #dc-chat #darknet #crazyirc #computer #catface #business #buddhism #buddha #bud #botinc #bluray #blunt #bluejays [04:03] #blackhats #batu #battleield3 #archiveteam #apple #antisec #YouTube #XTV #ShadowCore #RGH #Python r#olsentwins #Live247 #HamRadio #Dupecheck #Divalicious #Cyberspace #CRAIGSLIST [04:03] 21:02:34 [EFNet] -!- channels : #Beastys-Typo-Class-101 #Beastyboyz #B1G #50.channels.1.cup #49ers #3DS #360news #360banned #2600 #testing50608 [04:03] 21:02:34 [EFNet] -!- server : irc.servercentral.net [Server Central Network] [04:03] 21:02:34 [EFNet] -!- : 69.143.107.126 :actually using host [04:05] All aboard the chatboat [04:05] hehe [04:08] belgravia was #famous [04:11] That's one of the least effective chatbots I've seen. I wonder what it was for. [04:12] hmmm [04:13] At least it made an effort; I still get hit by script ones sometimes [04:13] I dunno, did it make an effort? People spoke to it directly by name and it didn't try to shill or get personal info or anything. [04:14] True [04:14] It acted confused. Not sure what that is meant to prove. [04:14] it was more coherent than most Youtube comments [04:14] that's a pretty big AI advance [04:14] Now I'm tempted to join one of its other billion channels and see what it does [04:31] i have every episode of dl.tv now :-D [04:32] yipdw: that's clearly an insult to AI [04:32] AI hasn't done so well [04:33] well, natural language generation at least [04:33] but youtube comments? [04:33] well [04:33] we can write a bot that posts youtube comments [04:33] especially on videos from VEVO [05:08] apparently belgravia isn't a bot [05:08] according to the other channels [05:08] which may be all bots :p [05:22] who cares [05:22] NOT I [05:25] my feelings, you've hurt them [05:26] i demand a refund [05:27] * chronomex gladly refunds Zod_ 100% of payments received [07:07] hmm -- I'm running VirtualBox VMs in a KVM VM [07:07] well, going to try, anyway [08:25] If I have any assigned work on MeMac, please clear it out [08:27] alard: ^ [08:32] willwill: Does that also hold for anything you've already completed? [08:32] Or are you just using seesaw? [08:34] mmmm [08:34] https://www.youtube.com/watch?v=LIIBRr31DIU [08:58] alard: I use seesaw so everything marked completed should be OK [09:26] willwill: Good, thanks. [09:50] hmmm [09:50] i did appently 40gb traffic on the network yesterday [09:51] :/ [09:51] I think most of htatm ust of been internal [11:52] SmileyG: I may have done that in the last day too [11:53] trying to backup dl.tv episodes was a pain [11:53] i had to figure out the unique url for each episode [12:05] Wyatt: re what you said 11 hours ago: for now [12:54] is there any way to make a running wget, that is caught in infinite links not visit any more links in that specific directory? [12:55] http://domain.com/files/about.php/about.php/about.php/archive.php/archive.php/archive.php/files/about.php/files/ etc [12:56] i would like to make it stop doing any more in /files/ [13:17] You could try to rm -rf /files/ [13:54] nope, it continues (i backgrounded it earlier, mved the directory, resumed) [14:52] i chmod -w the dir now, lets see [15:19] so far it is still trying hard [16:23] Schbirid: AFAIK, the only method wget has for this is a recursion limit [17:04] or --exclude [17:04] but also requires stop-restart [17:16] good afternoon [17:16] hi [18:29] Wow, Q-audio being hosted on Dreamhost, I wanted to look at their pricing, etc. Yup, you get unlimited disk/bw. And they say they have a 100% uptime guarantee, round-the-clock support, your site will never miss a beat. [18:30] I assume the guy who runs Q-audio would beg to differ. [18:31] i think jason would differ, too, given that he moved a whole bunch of sites off dreamhost [18:31] they're hacked to shit, apparently [18:31] I was also looking at their VPS plans and there's a pretty convenient (for them!) catch there. You get prices for ram, etc. and a signup button. *Later* they tell you those prices are plus a shared hosting fee of as little as $8.95 per month. [18:31] yeah, that's kind of weak [18:33] yeah, Jaybird11, he doesn't recommend Dreamhost anymore [18:33] at all! [18:33] My VPS is on Linode. I've had no problems with them. [18:37] dreamhost was storing passwords in plaintxt for over a decade [18:38] of course they eventually got hacked [18:38] I still have my account, but I will probably move off when it comes up for renewal [18:38] *sigh* I have so much crap on there. [18:38] Oh well, it will make me automate the process [18:39] sethish: people still do that? [18:39] in 2012? [18:39] christ on a bike [18:47] uh, yeah? Duh [18:47] there's been like a bazillion exposures 2011/2012 [18:48] dreamhost gets hacked continually [18:51] my dreamhost experience http://spirit.enjoys.it/stuff/dreamhost.txt [18:52] written 2009 i think [18:55] I even knew that they had my password in cleartext, because they would email it to me *facepalm* [19:04] I've been doing a little mobileme seesaw on my Linode. I ran it with an & at the end to background it last time, and rsync seems to be stuck. No idea what's going on. If I kill rsync, will seasaw try again, delete those files, or what? [19:05] Jaybird11: you'll need to run upload-finished.sh to complete the upload; running seesaw again will start a new download [19:05] If it's uploading, seesaw will leave those files as-is and download something else [19:06] I've noticed rsync get stuck occasionally (it constantly does a select() system call which times out every 60 seconds), no idea what's up with that [19:11] Is anything wrong with fos? [19:16] Seems to be a problem between probably the Dallas Linode datacenter and Fos. I have an rsync job going to Fos from my home net connection and it's going fine. I even stopped/restarted it. [19:16] My uploads seem to be progressing fine currently, but the ones where rsync got stuck got lost; they were all partial uploads continued with upload-finished.sh, if that could make a difference [19:16] Ah, it's up again now. [19:17] Is it possible that fos is just being very slow, if you couldn't connect to it moments ago? [19:18] Yes, maybe it was very busy. [19:19] I've now modified my script to check the rsync result, was too lazy to do that before. (The seesaw/memac scripts are safe, by the way, they retry.) [19:42] I just checked my uploads (from Atlanta & France) - both are uploading to fos at an extremely slow rate [20:11] sethish: http://www.bash.org/?17392 [20:19] Hm. Just checked my two uploads and they're hosed. I can ping FOS but rsync won't respond. [21:32] You'd think that there was also something wrong on batcave: http://ia700000.us.archive.org:8088/mrtg/networkv2.html [21:55] "archive team members, please investigate fortress." [21:55] wat? [21:55] jason just tweeted that [21:56] Probably unrelated: "a seagull just pooped on me! Remember this at oscar time" [21:56] hi mistym [21:56] Hey winr4r [22:00] https://twitter.com/#!/textfiles/status/192718538564308994 [22:07] Fortress? [22:08] fos.textfiles.com [22:08] Oh; thought a site was dying [22:11] same, heh [22:21] anyone remember what IA host fos is on? [22:26] teamarchive-1.us.archive.org [22:36] winr4r: that's the vm. I want the host [22:37] Coderjoe: not sure what you mean [22:38] batcave and fos are virtual machines. in batcave's case, it is running on the host named ia700000.us.archive.org [22:38] oh, gotcha [22:39] most of IA's newer infrastructure is set up with baremetal hosts for the main storage pool and VMs on those hosts doing various work [22:39] (my observation, at least) [22:41] and ia700000.us happens to be aisle 70, rack 00, system 00 in the us cluster [22:41] (again, my observations from various photos and stuff I have seen over the years) [22:41] the ailse part may be a little off [22:41] ah :) [22:54] found it [22:54] http://ia700108.us.archive.org:8088/mrtg/ [22:59] Well, I guess we have a better idea where the issue is at now... that's a painful graph [22:59] yes