01:35:43 I'm parsing a MacOS resource fork with Python so clearly I took a wrong turn somewhere 01:40:31 i often have that feeling 01:44:57 oh god, someone in another chat was having problems with a hard disk 01:45:13 checked Linux, it didn't even recognize the correct disk size, and "xxd /dev/sdb | head" said "I/O error" 01:45:20 turns out 01:45:33 "oh, you're fucked, this is the drive which is so bad it gets its own wikipedia page https://en.wikipedia.org/wiki/ST3000DM001" 02:52:46 De-Crewed Cursedliner is about to attempt re-entry https://www.youtube.com/live/vZ0T-cZWh78 02:53:05 I'm getting video glitches 02:53:56 ok it's their fault, the corruption never affects the nasa logo 02:54:28 Hey this is Boeing - be thankful you're getting anything. 03:02:06 I'm surprised the cameras they're using haven't bursted into flames yet or something 03:05:34 There were glitches on the earlier stream, too. 03:09:58 what's the ETA again? 03:10:35 About 7 minutes till it starts the burn 03:11:10 0401UTC landing 03:11:31 I assume (if it doesn't explode) they're going to rehearse getting to the craft and opening it to get the crew out 03:11:35 Thank you, finally something that isn't a silly American time zone. :-) 03:11:52 JAA: yeah they keep giving the landing time in farenheit or something 03:12:13 Oh sorry, I mean 12:01 AM Freedom Time 03:20:13 weird to think that it's slowing down over australia but still going fast enough to be in new mexico in 40 minutes 03:22:16 '3000 degrees' pls 03:23:21 the person moving the mouse cursor around :D 04:00:52 Holy shit - it seems to have made it in one piece 04:01:18 Boeing++ 04:01:18 -eggdrop- [karma] 'Boeing' now has -1 karma! 04:51:34 I was watching the starliner landing at 1am my time, it's now 1:50am, and I remembered Akademy (KDE conference) starts tomorrow at 5am my time so I guess I'm *not* watching the morning talks live x_x 09:41:11 Has anyone got news from fireonlive? 15:19:34 steering? 18:18:48 :( 18:42:57 I once again wish fireonlive all the best.. this really sucks :( 18:45:12 Oh do we have an update? 18:45:22 I might have missed it 18:45:58 kiska: we don't :( 18:46:03 I see.... 18:57:00 what happened? 18:57:48 DogsRNice: > i just got confirmation that fireonlive is in the hospital, so, best wishes or religious thoughts are appreciated 18:58:07 about a few weeks ago :( 18:58:58 He had a stroke and was still basically unresponsive about a week later. 19:02:06 hope he's doing a bit better now.. 19:15:59 it's going to take a while if it's that bad :-| 19:16:21 I hope that he'll get back here and show how we rooted for him 19:39:10 :/ 19:39:24 I hope he'll get back here 21:35:26 seems I used 12% of my laptop SSD's write cycles hm 21:36:01 Percentage Used: 12% 21:36:03 Data Units Read: 71.462.331 [36,5 TB] 21:36:04 Data Units Written: 59.169.583 [30,2 TB] 21:36:06 Power Cycles: 536 21:36:07 Power On Hours: 10.424 21:37:12 Available Spare: 100% 21:37:14 So 250 TB endurance, pretty common for consumer SSDs. 21:37:14 Available Spare Threshold: 10% 21:37:16 Percentage Used: 100% 21:37:18 Data Units Read: 1,527,623,185 [782 TB] 21:37:20 Data Units Written: 1,660,573,137 [850 TB] 21:37:22 :-) 21:37:34 used 100%? I hope you have backups 21:37:56 I'm watching that one though: 21:37:59 Media and Data Integrity Errors: 0 21:38:01 Error Information Log Entries: 0 21:38:03 Warning Comp. Temperature Time: 0 21:38:05 Critical Comp. Temperature Time: 0 21:38:07 Error Information (NVMe Log 0x01, 16 of 256 entries) 21:38:09 No Errors Loggedy 21:38:11 (extra y, sorry) 21:38:13 so all fine :-) 21:38:31 JAA: there's an irrational feeling of "oh no it's already at 12%" and then realizing I have had it for a year or two 21:38:44 this laptop is *not* going to last me 10-20 years 21:39:59 Mine's on a good path to 10 at least. 21:41:33 this is a 500GB SSD, I'll want to replace it before the endurance becomes a problem :P 21:43:28 I suspect it's MLC with a SLC cache, and I wish SMART exposed how much data is in SLC waiting to be flushed to the MLC 21:43:54 "why is it slow, oh okay the SLC filled up"