// #eevblog — 2019-03-04
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
05:43:06 Nick: EEVBlog1 is now known as EEVBlog
05:43:09 Quit: EEVBlog ([email protected]) Changing hosts
05:43:09 Join: EEVBlog ([email protected]) to #EEVblog
05:59:49 Mode: (by Ampera) +v EEVBlog
06:15:06 Join: Bluenote ([email protected]) to #EEVblog
09:15:35 <ServalSpots> And what a stable server it looks to be
10:05:56 <EEVBlog> New EEVBlog Tweet: Anyone know if there will be any place in Sydney to watch #Apollo11 in 70mm?
10:24:56 <Ampera> That's not my server, that's AustNet
10:40:27 <ServalSpots> :/
10:40:40 <ServalSpots> Wasn't AustNet touted as being more stable than afternet?
10:40:52 <Ampera> it was
10:41:10 <Ampera> but the stability is half the problem, I'd actually give them that, when they aren't being DoS'd, they are slightly more stable than AfterNET
10:41:39 <Ampera> the issue is I cannot authenticate my bot automatically, so it will just randomly decide to kick it off the EEVBlog username, and then I have to go in and manually re-auth
10:42:05 <ServalSpots> tbf if you remove afternet's major cause of douwntime it's really stable as well
10:43:07 <ServalSpots> Why can't it auto-auth?
10:43:07 <Ampera> tbf if you remove the tumors, pain, weakness, and death, cancer is really a benign illness
10:43:14 <Ampera> because there's no such thing on this server
10:43:18 <ServalSpots> hehe, aye
10:43:21 <Ampera> no SASL no AustNET style AoC
10:43:23 <Ampera> *AfterNET
10:44:58 <ServalSpots> Aye, I was thinking more having the bot "manually" auth on its own
10:45:59 <Ampera> because the IRC library for whatever reason will not read the auth messages notifying me to
10:46:16 <ServalSpots> balls :/
10:46:18 <Ampera> It's also not a great idea to store plaintext public passwords in a bot
10:46:31 <Ampera> but apparently "if my system is secure" that shouldn't be a problem
10:46:52 <Ampera> so I'll have to figure out how to make my system secure then I won't have to worry about passwords
10:46:59 <ServalSpots> :P
10:47:55 <ServalSpots> though in this context it's never bothered me. Hell, I don't go strip them out of my logs or anything
10:48:43 <Ampera> yeah, but this isn't /my/ password, and I tend to be very paranoid about what I do with other people's accounts
10:48:54 <Ampera> even if it's IRC, it's just good practice
10:50:54 <Ampera> If I were to redo the bot, I'd make my own IRC library, since I now know how easy it is, and my IRC library doesn't work with SSL/TLS anyways
10:51:00 <Ampera> but effort
10:51:31 <Ampera> I'd also have to split the program into C/C++ and Java, since all of the Twitter code is Java, and not easily portable to C/C++
11:01:46 <ServalSpots> Ah, I assumed it was yours
11:01:59 <Ampera> No, it's KittehIRC for Java
11:02:38 <ServalSpots> (the password I meant. I've never been sure of how much of the bot was prebuilt, cobbled, or custom)
11:02:52 <Ampera> Halcyon made the accounts and stuff
11:05:52 <ServalSpots> makes sense really
11:37:09 Join: seaner ([email protected]) to #EEVblog
13:53:34 <EEVBlog> New EEVBlog Tweet: NEW Video on EEVblog2! The EEVblog Lab VIBRATES! https://t.co/Yh24t5yBET
14:35:52 <EEVBlog> New EEVBlog Tweet: RT @TheAmpHour: This week @eevblog and @Chris_Gammell discuss designing hardware without specifications, upcoming conferences, working with…
15:46:10 Topic Is: Official IRC channel of the EEVBlog - www.eevblog.com
15:46:10 Set By: (ChanOP) on: Tue Jan 22 08:34:08 2019
15:57:52 Quit: Bluenote ([email protected]) Quit: Leaving
17:53:18 <EEVBlog> New EEVBlog Tweet: 34min, bugger, maybe another go-through might get it down to 29:xx https://t.co/HeYEIA5hIf
17:56:19 <EEVBlog> New EEVBlog Tweet: RT @chr1sa: Another weekend, another ho-hum VR experience. We've tried every VR/AR device made for the past 10 years--every version of Ocul…
17:57:20 <EEVBlog> New EEVBlog Tweet: RT @nascom1: The 70M is a bit like a Swiss army knife when it comes to working on it. Cranes and hoists pop out to allow transporting of ha…
19:46:05 <EEVBlog> New EEVBlog Tweet: Nope, no chance. I added an extra thing :-> Rendering now.
19:53:07 <EEVBlog> New EEVBlog Tweet: Solus just keep digging their own technical grave. https://t.co/2Xa8JZT13I
20:47:35 Quit: Ampera ([email protected]) Quit: Quick! Someone tell Ampera his server has caught fire!
20:47:35 Quit: EEVBlog ([email protected]) Quit: The bot went SPROING!
20:51:44 Join: EEVBlog ([email protected]) to #EEVblog
20:52:47 Join: Ampera ([email protected]) to #EEVblog
20:52:51 Mode: (by ChanOP) +o Ampera
20:53:38 Quit: Ampera ([email protected]) Quit: Quick! Someone tell Ampera his server has caught fire!
20:53:47 Nick: EEVBlog is now known as EEVBlog1
21:18:16 <K> hello
21:23:49 <ibiza> gday
21:36:26 Join: Ampera ([email protected]) to #EEVblog
21:36:36 Mode: (by ChanOP) +o Ampera
21:36:39 <Ampera> oh how nice of the bot to be on before me
21:37:13 Nick: EEVBlog1 is now known as EEVBlog
21:37:16 Quit: EEVBlog ([email protected]) Changing hosts
21:37:16 Join: EEVBlog ([email protected]) to #EEVblog
21:38:14 <Ampera> EEVBlog Status
21:38:14 <EEVBlog> EEVBlog's Latest Tweet: Solus just keep digging their own technical grave. https://t.co/2Xa8JZT13I
21:38:30 <Ampera> EEVBlog Help
21:57:20 <Ampera> me and the bot are going down because I need to reinstall FreeBSD because I did a shit job of it when I did, and I want to switch drives, bbl
21:57:28 Quit: Ampera ([email protected]) Quit: Quick! Someone tell Ampera his server has caught fire!
21:57:28 Quit: EEVBlog ([email protected]) Quit: The bot went SPROING!
22:27:13 Join: EEVBlog ([email protected]) to #EEVblog
22:27:43 Join: Ampera ([email protected]) to #EEVblog
22:27:47 Mode: (by ChanOP) +o Ampera
22:29:27 Nick: EEVBlog is now known as EEVBlog1
Search this day's buffer: