#soylent | Logs for 2024-06-12
« return
[01:23:06] <Runaway> Silly chromas - expecting things to work when you buy them.
[01:23:25] <Runaway> You think this is the 1960s or something?
[01:24:19] <Runaway> Well, actually, *some things* worked when you bought them in the 1960s
[04:47:09] <chromas> Silly Runaway, Trix are for chicks
[05:00:20] <Bytram> Anyone else having trouble loading our site?
[05:04:51] <Bytram> chromas: Runaway: Anyone here? I am heading for bed.
[05:05:39] <Bytram> laters
[05:12:41] <chromas> yep internal server error
[05:13:08] <chromas> the sylvester bot reports the same
[06:19:58] -!- soylentil1 [soylentil1!~soylentil@qnxp45-393-428-316.range95-893.btcentralplus.com] has joined #soylent
[06:29:43] -!- soylentil1 has quit [Ping timeout: 258 seconds]
[06:41:06] <janrinok> I am seeing comments that the site is down. I checked it about 2 hours ago it was OK, and it is working now. I'm not sure what that problem was but it seems to be OK now. I do not know who fixed it.
[06:41:32] <chromas> site working confirmed
[06:50:01] <janrinok> Thank you to ever sorted that problem out....
[06:50:07] <janrinok> *whoever
[07:43:53] -!- _dx3bydt3 [_dx3bydt3!~|dx3bydt3@129.224.zsu.s] has joined #soylent
[07:47:46] -!- dx3bydt3 has quit [Ping timeout: 252 seconds]
[07:48:40] -!- dx3bydt3 [dx3bydt3!~|dx3bydt3@129.224.tgq.ugw] has joined #soylent
[07:48:52] -!- _dx3bydt3 has quit [Ping timeout: 252 seconds]
[08:10:19] -!- drussell has quit [Ping timeout: 252 seconds]
[08:37:15] -!- drussell [drussell!~drussell@2604:3d08:a77f:tzmr:pwil:gmis:ohkg:owgz] has joined #soylent
[11:08:14] -!- systemd has quit [Remote host closed the connection]
[11:11:46] <Ingar> chromas isn't that what 3D printers are for? to print parts for your printer?
[11:12:20] <Ingar> tbh all this tinkering is what is keeping me from getting one
[11:12:21] <chromas> true. I should build a voron while they're still trandy
[11:12:56] -!- systemd [systemd!~systemd@pid1] has joined #soylent
[11:13:47] <chromas> well I got it all up and running, then started a print, but the nozzle's a wee too high
[11:13:55] <Bytram> systemd: Wb!
[11:14:07] <chromas> go to adjust it with rotary encoder know and it started seizing up. fpos
[11:14:11] <chromas> knob
[11:14:11] <janrinok> Bytram, mornin'
[11:16:05] <Bytram> hi! got dr appt in 15 min
[11:16:56] <Bytram> TTYL!
[11:45:23] <chromas> actually now that you mention it, it wouldn't even be a real printer if it just worked
[12:44:11] -!- Runaway has quit [Read error: Connection reset by peer]
[13:16:24] -!- Runaway1956 [Runaway1956!~OldGuy@the.abyss.stares.back] has joined #soylent
[14:19:44] -!- Runaway [Runaway!~OldGuy@the.abyss.stares.back] has joined #soylent
[14:23:46] -!- Runaway1956 has quit [Ping timeout: 252 seconds]
[14:26:54] <janrinok> Runaway, are you having connection problems?
[14:51:33] -!- Runaway1956 [Runaway1956!~OldGuy@the.abyss.stares.back] has joined #soylent
[14:54:34] -!- Runaway has quit [Ping timeout: 252 seconds]
[17:12:42] <Runaway1956> janrinok, my connection problems were self induced this time. I had a problem in another application with geofencind, so I swapped a couple times between VPN servers. Task completed, I'm back to my normal server.
[17:13:01] <Runaway1956> *geofencing
[17:14:04] <Runaway1956> Had a site that simply refused to accept $US for my transaction, had to log out, switch servers, log back in, then everything worked.
[17:15:06] <janrinok> Ah OK, thanks for that. We have had a couple of other unexplained issues today. I was wondering if there was a connection (excuse the pun)
[19:16:42] <Ingar> it's earthrays
[20:49:51] -!- Ox0000 [Ox0000!~Ox0000@ysig-694-71-0-819.washdc.fios.verizon.net] has joined #soylent
[20:49:59] <Ox0000> You guys know about the 500 error?
[20:51:18] <drussell> It is a 500 Error for me here, aswell...
[20:54:14] <Ox0000> Oh, it no longer 500's now
[20:56:45] -!- Ox0000 has quit [Quit: Client closed]
[22:10:35] -!- pTamok [pTamok!~pTamok@82.148.lts.sjg] has joined #soylent
[22:14:33] <pTamok> Yes, the site had a few wobbles for me earlier on today, but seems to be OK now. Thank you to whoever reset the frangible confabulator and restored normal service.
[22:16:15] <pTamok> Of course, I am doing my clueless end-user impression today, so I didn't make note of the (differing) error messages I was getting, even though I have a reasonable camera in my phone. The days of writing down hexadecimal code from BSODs are long gone.
[22:17:37] <pTamok> I'm looking forward to the sunny uplands of the new order, so I can throw some money at SN.
[22:20:34] <pTamok> I shall sidle off-stage looking embarrassed now. Tschüß!
[22:20:53] -!- pTamok [pTamok!~pTamok@82.148.lts.sjg] has parted #soylent