00:33:43<pabs>https://www.tomshardware.com/pc-components/storage/unpowered-ssd-endurance-investigation-finds-severe-data-loss-and-performance-issues-reminds-us-of-the-importance-of-refreshing-backups https://news.ycombinator.com/item?id=43739028
01:11:16sludge quits [Ping timeout: 260 seconds]
01:16:37jasons76 (jasons) joins
01:18:51jasons7 quits [Ping timeout: 260 seconds]
01:18:51jasons76 is now known as jasons7
01:20:42<chrismrtn>I just used Twitter's user archive request. All of the images within the archive were rescaled to a maximum 1200px, and the README.txt file still calls the place "Twitter" in all but two instances.
01:24:30<BlankEclair>why are they downscaled to max 1200px... that seems to nerf a part of the reason for the archive
01:24:35<BlankEclair>but hey, twitter is still funny lol
01:28:01<BlankEclair>our wiki proudly deadnames twitter
01:43:15ericgallager quits [Quit: This computer has gone to sleep]
02:18:44DogsRNice_ joins
02:22:47DogsRNice quits [Ping timeout: 258 seconds]
02:32:59ericgallager joins
02:35:36<@JAA>> As a reminder, an SSD's endurance rating is calculated based on how long it can store data if left unplugged after a certain amount of data has been written, hence the importance of this testing.
02:35:40<@JAA>Huh, first time I hear this.
02:36:25<@JAA>I thought it was just expected total data writes over the lifetime of the drive.
02:36:58<@JAA>As a proxy for how many cycles the flash cells are capable of.
02:38:55GNU_world joins
03:00:25sec^nd quits [Ping timeout: 240 seconds]
03:02:22sec^nd (second) joins
03:09:13sec^nd quits [Ping timeout: 240 seconds]
03:27:28sec^nd (second) joins
03:41:55etnguyen03 (etnguyen03) joins
03:44:18<steering>the funny thing is, they say that, and then later they use endurance in the traditional way: "the 'Worn' drives have been subjected to 280 terabytes of written data churn, much more than their rated 60 Terabytes Written (TBW) endurance rating"
04:08:15etnguyen03 quits [Remote host closed the connection]
04:09:34Webuser054456 joins
04:18:00<nicolas17>yeahhh I think those are two different metrics that the article is conflating horribly
04:33:44DogsRNice__ joins
04:33:58DogsRNice__ quits [Read error: Connection reset by peer]
04:37:46DogsRNice_ quits [Ping timeout: 260 seconds]
04:44:03ericgallager quits [Client Quit]
05:08:01sec^nd quits [Ping timeout: 240 seconds]
05:13:54sec^nd (second) joins
05:19:25ericgallager joins
05:51:08BornOn420 quits [Remote host closed the connection]
05:51:45BornOn420 (BornOn420) joins
05:52:01sec^nd quits [Ping timeout: 240 seconds]
05:52:21sec^nd (second) joins
05:56:49sec^nd quits [Ping timeout: 240 seconds]
05:57:22sec^nd (second) joins
06:16:01sec^nd quits [Ping timeout: 240 seconds]
06:16:24sec^nd (second) joins
06:38:15ericgallager quits [Client Quit]
06:53:41programmerq quits [Ping timeout: 260 seconds]
06:54:01programmerq (programmerq) joins
07:01:37sec^nd quits [Ping timeout: 240 seconds]
07:01:56sec^nd (second) joins
07:49:37Meli (Meli) joins
08:48:54<Barto>yeah, and 60 TBW is awfully low
08:49:55<Barto>for me they showed correlation between reaching TBW and drives rotting unpowered, that's all.
08:53:12<Barto>but it's worth more digging for sure: more samples, more reproduction, etc.
09:31:21<steering>once you've written 4x the TBW to it, I wouldn't expect it to be reliable whether powered or not
09:50:37<Barto>_exactly_
10:35:43ducky_ (ducky) joins
10:35:56ducky quits [Ping timeout: 260 seconds]
10:36:28ducky_ is now known as ducky
11:00:02Bleo18260072271962345 quits [Quit: The Lounge - https://thelounge.chat]
11:02:47Bleo18260072271962345 joins
11:12:26arch quits [Remote host closed the connection]
11:54:06IDK (IDK) joins
12:35:05FiTheArchiver joins
12:58:51ducky quits [Ping timeout: 260 seconds]
13:00:01Matthww quits [Ping timeout: 260 seconds]
13:04:39Matthww joins
13:18:44ducky (ducky) joins
13:48:13etnguyen03 (etnguyen03) joins
13:58:27ericgallager joins
14:12:37IDK quits [Client Quit]
14:22:05IDK (IDK) joins
14:55:45FiTheArchiver1 joins
14:57:16FiTheArchiver3 joins
14:58:43FiTheArchiver quits [Ping timeout: 258 seconds]
15:00:00FiTheArchiver joins
15:01:21FiTheArchiver1 quits [Ping timeout: 260 seconds]
15:02:31FiTheArchiver3 quits [Ping timeout: 260 seconds]
15:05:26Juest quits [Ping timeout: 260 seconds]
15:15:10grill (grill) joins
15:28:25Juest (Juest) joins
16:44:52hexa_ is now known as hexa-
16:50:05ericgallager quits [Client Quit]
17:07:45arch joins
18:00:25grill quits [Ping timeout: 258 seconds]
18:01:47grill (grill) joins
18:07:37HackMii quits [Remote host closed the connection]
18:08:08HackMii (hacktheplanet) joins
18:12:56SootBector quits [Remote host closed the connection]
18:14:09SootBector (SootBector) joins
18:41:40arch quits [Remote host closed the connection]
18:41:56arch joins
18:45:32sec^nd quits [Remote host closed the connection]
18:45:56sec^nd (second) joins
19:06:56grill quits [Ping timeout: 260 seconds]
19:52:43ericgallager joins
20:52:55DogsRNice joins
22:00:33BornOn420 quits [Remote host closed the connection]
22:01:06BornOn420 (BornOn420) joins
22:33:33<nicolas17>"I can't find how to UNinstall KDE from my Samsung Galaxy 24+ phone. Help please."
22:33:46<nicolas17>email sent to KDE's contact address for the Windows Store... how does this level of confusion even happen
23:16:35Hackerpcs quits [Quit: Hackerpcs]
23:57:58rohvani joins