[01:30] I'm making eggs [01:30] Ha, that's what I made as well.. but mine look much better [01:32] I am domesticly challenged. My wife is impressed! [02:07] https://www.reddup.co/ [02:08] stupid stupid: http://gadgets.ndtv.com/mobiles/news/oneplus-5-fingerprint-sensor-front-panel-ceo-pete-lau-1697339 [02:09] I like it on the back and feel that it makes more sense but others disagree with me on that (Apple and older Samsung phones for example) [02:10] it makes sense to me to be on the back [02:10] as well [03:01] decided to stop being lazy & irresponsible and use a password manager over the browser [03:02] @SivaMachina, I do still use browser autofill for a few sites [03:03] Might still keep a few for Google Smartlock. But for the most part I will be using pass [03:05] But Ido think the Android client for Pass has autofill capabilities [03:06] Not sure how how well it works [03:09] I know my password manager autofill works well (enpass) [03:19] Yeah. Decided to go with a more Open source option. That and if Pass stops being a thing I should be able to just use gpg to decrypt my passwords [03:20] "auto-confirm@amazon.com " [03:20] that's new [03:20] ? [03:21] it's a fake address [03:21] I go tho my spam every so ofter just for fun [03:22] @SivaMachina, Enpass is not open source but there are a few mitigating factors that ensure I can access my stuff if they go under. The password bank is self hosted. [03:27] https://www.xfinity.com/mobile/plan [03:34] I plan to switch to keep ass once Android o comes out [03:34] Keepass.. stupid voice recognition [03:35] @ahoneybun, I will pass [03:36] @AdamOutler, Sure.... [03:37] I'm super cereal. It translated it to what was written. [03:38] But keepass is open source and once Android has auto fill API, I think it's a good time to switch. [03:57] @AdamOutler [03:58] @SivaMachina, Android O has deeper integration. The current autofill that some password managers use are essentially a hack [03:59] Ah [04:00] @SivaMachina, The current ones use the Android Accessibility API. Technically this could be abused and cause password leakage. The O implementation actually uses a much more secure method [04:19] So it's a thing kind of. But crappy and prone to being insecure [04:22] @SivaMachina, For the record, I am not aware of any actual attacks, just theoritical attacks [04:24] Probably not something out want risk with passwords [10:51] and I don't have service on my phone anymore [11:18] The heck [12:53] The O integration with password maangers is one of my favorite new features. I use KeePass for all my credentials. Streamlining and securing that pipeline is a big win. [12:56] I completely agree. Although I do not use keepass [13:45] Damn, Google actually got "keepass" correct... that was using Voice to Text on my Android Auto while driving to work. [13:45] Now @AdamOutler has some explaining to do [13:45] Its my Accent [13:48] Sometimes I ask Google something and he just say que [15:00] Have I ever said how much I love "screen" [15:02] Aren't there mux wars like vim vs emacs but for screen, tmux byobu, etc? [15:02] Wow, you all love to talk [15:02] Curse you @Abrerr [15:02] @Ivoriesablaze - sometimes [15:03] I know I missed out on that tmux talk @ Fossetcon [15:03] kekekeke [15:04] Whatcha love about "screen", @KMyers ? [15:04] The fact that it just works [15:05] can confirm, screen /dev/ttyUSB0 just works [15:15] Not doing that, just have a long running script on a server [15:15] (Re-indexing my NextCloud filesystem) [15:35] I just like I don't have to specify baud rate, etc if I'm consoling into a device. [15:35] :D [15:36] I use Byobu, which is wrapper for both tmux and screen. It makes using either much easier. [15:37] And apparently my power went out at 11:01 today, since that's the time my usual handle disconnected. :( [15:41] dun dun dunnn [15:42] And FWIW, I use my maxolasersquad handle through byobu on my home server. [15:42] I have a small reference guide to screen because it's on some boxes @ work. [15:42] otherwise it's tmux @ home when needed [15:43] Byobu looks like. [15:43] nice* === JollyRgrs is now known as fe1da === fe1da is now known as JollyRgrs [20:35] Yas [20:43] Almost 100 days up [20:47] Pix or it didn't happen. [20:48] There is the pic [20:48] 98d21h [20:49] Oh, there it is! It has officially happened. [20:50] I reboot my closet server often. Thanks to control.adamoutler.com, it's an easy way to reset inbound connections. [20:52] Its a raspi hooked to a pigtail controlled by this. https://github.com/adamoutler/RaspberryPiGPIOControl/blob/master/README.md. I should get pix up. [20:52] I have three power outlets hooked to a raspi web interface. [22:49] Lovely twitter [22:52] @ahoneybun, That's nothing [22:53] well yea [22:56] damnnn [22:57] That one has the highest uptime [23:24] @KMyers [23:24] any idea what's with this? [23:25] What app? [23:25] no app [23:25] it's just the whole thing [23:25] I honestly disabled that check on mine [23:25] That is a web app or something. [23:25] Is that nextcloud? [23:25] where is that? [23:26] yea @AdamOutler [23:26] Package maintainers screwed up. [23:26] You can search the logs for more info. [23:28] https://aaron.rack1.net/index.php/settings/integrity/failed [23:29] ahhh [23:30] I'm stuck on 12.0.0 RC2 [23:30] can't update [23:33] I can't see that error without login. [23:33] fixed it [23:33] was direct men [23:33] which I don't need with 12 anymore [23:33] Direct men? [23:34] *direct menu [23:34] Ok. I saw that once with a Ubuntu package. I guess that one slipped by @mhall119 [23:35] That was OC9 and it was a package maintainer sticking his credits into the folder. [23:40] To login you need to provide the unhashed value of "updater.secret" in your config file. [23:40] I got the secret but it's not taking it [23:44] and did it with the CLI