#soylent | Logs for 2026-05-22
« return
[00:20:41] -!- prg has quit [Ping timeout: 240 seconds]
[00:21:06] -!- prg [prg!~prg@ryfhuvb.de] has joined #soylent
[00:35:03] -!- AlwaysNever has quit [Read error: Connection reset by peer]
[00:44:40] <kolie2> hydraulic pin failed to retract from the launch tower arm
[00:44:56] <kolie2> Elon Musk
[00:44:56] <kolie2> @elonmusk
[00:44:56] <kolie2> ·
[00:44:56] <kolie2> 55m
[00:44:56] <kolie2> The hydraulic pin holding the tower arm in place did not retract.
[00:44:57] <kolie2> If that can be fixed tonight, there will be another launch attempt tomorrow at 5:30 CT.
[01:00:12] -!- bender has quit [Remote host closed the connection]
[01:00:22] -!- bender [bender!bot@Soylent/Bot/Bender] has joined #soylent
[01:01:24] -!- Loggie [Loggie!Loggie@Soylent/BotArmy] has joined #soylent
[01:58:54] <kolie2> Code Archaelogy - Why "Temporary" Became Permanent
[01:58:54] <kolie2> Slashcode was notorious for its complexity and the sheer volume of "temporary" duct-tape fixes required to keep one of the internet's highest-traffic sites online.
[01:58:54] <kolie2> As the mid-2000s progressed, the overhead of SOAP (parsing all that XML in Perl) proved to be too heavy for high-performance, real-time web operations. Slashdot eventually leaned heavily into aggressive caching layers (like Memcached, which actually grew out of the LiveJournal ecosystem around the same time) and backend database optimizations rather than fully realizing a massive SOAP-based microservice web.
[01:58:55] <kolie2> You are looking at a literal piece of internet history - a snapshot of a developer working late nights to keep Slashdot alive, dreaming of a clean, generic API structure that the relentless tide of production traffic probably never gave them time to finish.
[01:59:16] <kolie2> # this WILL NOT remain in journal.pl, it is here only temporarily, until
[01:59:16] <kolie2> # we get the more generic SOAP interface up and running, and then the Search
[01:59:16] <kolie2> # SOAP working (this will be in the Search SOAP API, i think)
[02:29:53] <chromas> SOAP is so old it's replacements have been replaced
[02:33:48] <kolie2> I have pixel accurate rendering of index.
[02:35:14] <kolie2> one character off on comments.pl ill have to fix that.
[02:38:00] <kolie2> oh wow thats a production error.
[02:38:31] <kolie2> If you go view https://soylentnews.org there is no space between the title. "Magical, no. Easy, no.(Score: 2, Insightful)"
[02:38:32] <systemd> ^ 0303SoylentNews Comments | The Art and Science of Being Charismatic
[02:58:39] <chromas> so AC comments don't get the space?
[02:59:08] <chromas> oh, a few logged in users lack ti to. hm
[03:02:19] <chromas> only thing I notice so far is a newline between, which renders as a collapsed space
[03:37:07] <kolie2> yea its the uhh paren
[03:37:12] <kolie2> between the score and the title.
[03:37:23] <kolie2> Now that I've seen it I can't unsee it.
[04:23:40] <kolie2> https://paste.ennwise.com
[04:23:45] <systemd> ^ 0303paste. — nd6wn26c
[19:20:16] <kolie2> Found a bug in Lingua::Stem::En
[19:20:34] <kolie2> well, rehash's use of it.
[19:20:55] <kolie2> It doesn't correctly count search hits, unsure of the effect in practice.
[19:24:48] <kolie2> discarding uncommon words... The background task
[19:24:48] <kolie2> refreshUncommonStoryWords
[19:24:48] <kolie2> calculates the frequency of words in stories posted over the last 30 days. To keep matching focused, words with a count higher than a threshold (e.g., 15) are classified as "common" and discarded. Due to the accumulator bug, rare words appearing in titles or introtexts get their counts inflated up to 3x, pushing them past the threshold. Consequently, they are incorrectly excluded from the uncommonstorywords table.
[19:24:49] <kolie2> degraded "Similar Stories" results... the
[19:24:51] <kolie2> getSimilarStories
[19:24:53] <kolie2> matching algorithm matches stories using only words that exist in the uncommonstorywords table. Because the accumulator bug incorrectly excludes rare keywords from this table, the site fails to find valid similar stories (false negatives) or links unrelated articles.
[19:41:48] -!- progo has quit [Quit: The Lounge - https://thelounge.chat]
[19:53:43] -!- progo [progo!~progo@eegc-73-589-96-43.nwrknj.fios.verizon.net] has joined #soylent
[20:03:25] <progo> whois #nicechat
[20:03:37] <progo> oops sorry command sent to wrong window
[20:15:11] -!- AlwaysNever [AlwaysNever!~donaldo@315.38.1.669.dynamic.jazztel.es] has joined #soylent
[21:53:40] <Bytram> .
[21:55:59] <Bytram> JUST OVER 30 MINATES TU\\
[22:01:51] <Bytram> ~30 MINUTES TILL SPACEX LAUNCH
[22:01:56] <Bytram> .
[22:20:30] <kolie2> https://paste.ennwise.com
[22:20:32] <systemd> ^ 0303paste. — n124rh5y
[22:31:12] <Bytram> GO!
[22:32:02] <Bytram> MAXQ OK
[22:35:01] <kolie2> no boost back burn
[22:38:06] <Bytram> OOPS!
[22:40:04] <Bytram> SECU
[22:48:23] <Bytram> NOM TRAJECTORY W SHALLOW TRAJ
[22:50:23] <kolie2> pez launch
[22:56:07] <Bytram> 3 EO GO
[22:59:22] <Bytram> YAY
[23:00:15] <kolie2> pretty cool!
[23:00:23] <kolie2> gotta go get the kids.
[23:02:30] <Bytram> K
[23:37:58] <Bytram> KABOOM