00:01:17<thuban>i'm sorry, but i promised myself not to discuss this anymore
00:05:33<SootBector>has the bot ever announced the content of tweets? I noticed that https://publish.twitter.com/oembed?url=...&omit_script=True still works (limnoria's spiffytitles plugin) - unsure if it ends up ratelimited though
00:07:44<@OrIdow6>That's actually a nice idea
00:11:23<qwertyasdfuiopghjkl>thuban: That's fine, just wanted to point out some stuff :)
00:16:13<qwertyasdfuiopghjkl>(getting rather tired of discussing it myself too)
00:21:22qw3rty__ quits [Ping timeout: 255 seconds]
00:25:35<SootBector>it was a lovely surprise to see a link pasted on another channel didn't need clicking to read
00:29:03qw3rty__ joins
00:33:01shgaqnyrjp_ (shgaqnyrjp) joins
00:34:51shgaqnyrjp quits [Ping timeout: 260 seconds]
01:02:01hexa- quits [Quit: WeeChat 4.2.2]
01:03:09hexa- (hexa-) joins
01:04:07nepeat quits [Ping timeout: 255 seconds]
01:08:45<fireonlive>hi! wow!
01:10:03<fireonlive>many words i could say perhaps. however in the interest of peace i've switched the auto-replace domain to xcancel.com
01:13:38nepeat (nepeat) joins
01:13:45mgrytbak quits [Quit: Ping timeout (120 seconds)]
01:13:53mgrytbak joins
01:26:08shgaqnyrjp_ is now known as shgaqnyrjp
01:57:12icedice (icedice) joins
02:35:31etnguyen03 quits [Client Quit]
03:01:14seadog007_ joins
03:18:46<pabs>anarcat: I see python-internetarchive has a new upstream not in Debian yet, would you be able to update it? hoping that will fix the errors I've been seeing recently
03:20:42<steering>JAA: I do wonder if eventually we will see SSD take over for HDDs in capacity/$, especially for extremely-low-overwriting uses like IA
03:21:18<steering>I feel like we could see Moore's Law take over there at some point, for a while more anyway
03:22:13<@OrIdow6>Tape's still the king of the barrel, isn't it?
03:23:51<@OrIdow6>Hacker News style clueless guess, it feels like HDDs have less complexity per bit than SSDs, just a cell on a platter or whatever versus... however it is that SSDs work
03:27:58<pabs>fireonlive: twiit.com redirects to https://nitter.lucabased.xyz/ sometimes, looks like a good alternative
03:31:30<steering>qwertyasdfuiopghjkl: I feel like you haven't actually tried using other instances for any length of time. I haven't tried in a while but ~a year ago it was literally a weekly or even daily maintenance burden to go find a new instance that actually worked. Except poast, which has basically always worked.
03:32:01<steering>For a while I was using farside.link but even that kept breaking.
03:32:59<steering>Maybe twi{2,3}t is better.
03:34:49<steering>lucabased seems snappy to me, hopefully it's also stable.
03:39:46<steering>OrIdow6: an SSD is just a bunch of logic gates wired together at the most basic, but my thoughts are more around demand and 'node size'. I'm not sure how small you can make bits on a HDD, though, tbh.
04:03:23<fireonlive>,, source scripts/twitter2nitter.tcl
04:03:23<eggdrop>ok: (no output) -3ms-
04:03:26<fireonlive>swapped to nitter.lucabased.xyz
04:03:52<fireonlive>!seen that_lurker
04:03:53<eggdrop>[seen] that_lurker (~that_lurk@irc.kuhaon.fun) was last seen quitting from #urlteamwasright 12 hours 27 minutes 35 seconds ago (2024-07-22T15:36:17Z), stating "Ping timeout: 272 seconds"
04:03:56<fireonlive>hmmmm
04:04:17<@OrIdow6>!seen eggdrop
04:04:17<eggdrop>[seen] You found me, OrIdow6!
04:12:19Barto quits [Remote host closed the connection]
04:31:07atphoenix__ quits [Ping timeout: 255 seconds]
04:47:22DogsRNice quits [Read error: Connection reset by peer]
05:16:08that_lurker joins
05:22:52that_lurker quits [Remote host closed the connection]
05:25:38that_lurker joins
05:28:21Barto (Barto) joins
05:31:00that_lurker adds a self note to setup server monitoring for disk space usage -_-
05:31:50that_lurker swept the underlying issue under the rug by scaling to CX32
05:49:51<fireonlive>i wondered where you went!
05:57:13fuzzy8021 (fuzzy80211) joins
06:00:09fuzzy80211 quits [Ping timeout: 272 seconds]
06:15:58Sluggs quits [Ping timeout: 255 seconds]
06:34:48BlueMaxima quits [Read error: Connection reset by peer]
07:37:41Ryz quits [Ping timeout: 272 seconds]
07:38:19kiska5 quits [Ping timeout: 272 seconds]
07:41:25kiska5 joins
07:41:54Ryz (Ryz) joins
07:42:49HP_Archivist quits [Ping timeout: 255 seconds]
07:44:14HP_Archivist (HP_Archivist) joins
09:58:12fangfufu joins
10:26:14le0n_ quits [Quit: see you later, alligator]
10:27:39le0n (le0n) joins
10:44:47HackMii quits [Ping timeout: 260 seconds]
10:55:13HackMii (hacktheplanet) joins
11:00:05Bleo1826007227196 quits [Client Quit]
11:01:23Bleo1826007227196 joins
11:09:51Juest quits [Ping timeout: 272 seconds]
11:19:40Juest (Juest) joins
11:23:19Harzilein quits [Quit: ircII EPIC5-2.1.7 -- Are we there yet?]
12:30:17that_lurker quits [Ping timeout: 272 seconds]
13:00:55tek_dmn quits [Quit: ZNC - https://znc.in]
13:01:35c3manu quits [Remote host closed the connection]
13:01:50c3manu (c3manu) joins
13:12:49midou joins
13:14:05yarr0w joins
13:15:53yarrow quits [Ping timeout: 272 seconds]
14:22:52d10n quits [Ping timeout: 255 seconds]
14:23:03<qwertyasdfuiopghjkl>steering: I haven't (wasn't previously aware there was reason to), but I switched my redirect extension to https://nitter.lucabased.xyz/ yesterday and it seems to be fine so far. Occasionally there's a "tweet not found" error that goes away after refreshing, but that was happening on nitter.poast[.]org too so I'm guessing that's an issue with
14:23:04<qwertyasdfuiopghjkl>twitter or the nitter software itself. Looks like https://nitter.lucabased.xyz/ also doesn't require you to wait while it verifies your browser, so I'd consider it an improvement.
14:33:19that_lurker joins
15:05:20yarr0w_ joins
15:09:15yarr0w quits [Ping timeout: 272 seconds]
15:27:13G4te_Keep3r34924 quits [Quit: Ping timeout (120 seconds)]
15:27:32G4te_Keep3r34924 joins
15:28:53qw3rty__ quits [Ping timeout: 272 seconds]
15:33:33qw3rty__ joins
15:36:40katocala quits [Ping timeout: 255 seconds]
15:36:56katocala joins
15:48:02magmaus3 quits [Quit: :3]
15:48:31magmaus3 (magmaus3) joins
15:50:05tek_dmn (tek_dmn) joins
15:57:37Meli quits [Remote host closed the connection]
16:15:49katocala quits [Ping timeout: 255 seconds]
16:15:57katocala joins
16:17:01qw3rty__ quits [Ping timeout: 272 seconds]
16:20:37qw3rty__ joins
16:33:05pixel leaves
16:38:00<nulldata>https://letsencrypt.org/2024/07/23/replacing-ocsp-with-crls.html
16:48:35<fireonlive>neat
17:13:44<fireonlive>the lounge: your connection attempt to the irc server timed out. this is a fatal error. i won't try again.
17:13:48<fireonlive>🙄
17:28:39<nulldata>https://www.tomshardware.com/pc-components/cpus/intel-finally-announces-a-solution-for-cpu-crashing-errors-claims-elevated-voltages-are-the-root-cause-fix-coming-by-mid-august
17:29:18eghythhhyg joins
17:36:51pixel (pixel) joins
17:39:31eghythhhyg quits [Ping timeout: 255 seconds]
17:41:28eghythhhyg joins
17:50:46eghythhhyg quits [Ping timeout: 255 seconds]
17:56:24<nukke>CPUs are degrading by the minute
17:56:35<nukke>3+ weeks before a fix lol
17:57:45magmaus3 quits [Client Quit]
17:58:49magmaus3 (magmaus3) joins
17:59:00<@JAA>I've seen claims that they intentionally delayed everything because the new microcode will affect performance, but now the old microcode will still be used for comparison benchmarks with Zen 5.
18:20:20<nukke>it's so stupid. their new CPUs will release in september/october, and I don't think the performance difference is worth how much they are and will be losing with RMAs
18:20:44<nukke>even their Sapphire Rapids server Xeons are impacted apparently
18:36:21that_lurker quits [Ping timeout: 272 seconds]
18:47:55that_lurker joins
19:03:37<fireonlive>jeez
19:08:30icedice quits [Client Quit]
19:08:32<fireonlive>new from MSCHF: https://mschfscoutcookies.com/
19:31:50Panasonic quits [Remote host closed the connection]
19:38:34<imer>“Alternatively, you can eat them all yourself, we would respect that.” tempting
19:38:43<fireonlive>x3
20:47:37Dango360 quits [Ping timeout: 255 seconds]
20:47:52Dango360 (Dango360) joins
20:51:25Dango360_ (Dango360) joins
20:53:47Dango360 quits [Ping timeout: 272 seconds]
21:24:41IRC2DC joins
21:40:39_Dango360 (Dango360) joins
21:45:05Dango360_ quits [Ping timeout: 272 seconds]
21:51:19<yarrow_irccloud>I am impatiently waiting for something like Microsoft Silica (quartz glass) or ceramic storage or DNA data storage or piql film or anything that can rival hard drives as a storage medium for digital data
21:51:48<yarrow_irccloud>*rival hard drives and magnetic tape, I should say
21:53:55<yarrow_irccloud>Not for hot or warm storage, but just for cold storage
21:57:59etnguyen03 (etnguyen03) joins
22:11:24icedice (icedice) joins
22:17:35<yarrow_irccloud>Someone claiming to work at the Internet Archive commented on Reddit that the IA previously tried backing stuff up to magnetic tape, but every time they tried to load the tapes, there would be data loss due to bit rot that was undetectable until they tried to load the tapes
22:33:09<fireonlive>hmm
22:33:11<fireonlive>link?
22:39:21<yarrow_irccloud>https://www.reddit.com/r/DataHoarder/s/18IkHuKDMf
22:40:34<yarrow_irccloud>https://www.irccloud.com/pastebin/Y8RSVton
22:47:08<yarrow_irccloud>It would be so nice if exabytes of important data could be backed up on quartz glass slabs that last 1,000+ years and can’t be damaged by heat, humidity, or electromagnetic radiation
22:50:07Hackerpcs quits [Quit: Hackerpcs]
22:52:28<fireonlive>hmm interesting
22:53:11Hackerpcs (Hackerpcs) joins
22:53:20<f_>fireonlive: I thought your thelounge -> znc -> soju -> znc -> thelounge -> znc -> irccloud -> znc -> znc -> psybnc -> znc -> znc -> soju -> thelounge -> znc -> irc.hackint.org setup was foolproof
22:53:50<fireonlive>don't forget sbnc!
22:54:03<fireonlive>this one was another TL instance to another server :p
22:54:23<f_>fireonlive: I thought your thelounge -> znc -> sbnc -> soju -> znc -> thelounge -> znc -> sbnc -> sbnc -> sbnc -> sbnc -> irccloud -> znc -> sbnc -> znc -> psybnc -> znc -> znc -> soju -> thelounge -> znc -> irc.hackint.org setup was foolproof
22:54:29<fireonlive>:P
22:55:04<f_>stacking bouncers since 1999™
22:56:50<f_>JAA: did I mention your channel names are just funny
23:13:12BlueMaxima joins
23:36:44<fireonlive>>I Will Fucking Dropkick You If You Use That Spreadsheet
23:36:47<fireonlive>https://ludic.mataroa.blog/blog/i-will-fucking-dropkick-you-if-you-use-that-spreadsheet/
23:49:12Medowar quits [Quit: Ping timeout (120 seconds)]
23:51:36Medowar joins