#soylent | Logs for 2024-12-11

« return
[04:59:25] -!- chromas [chromas!~chromas@Soylent/Staph/Infector/chromas] has joined #soylent
[04:59:25] -!- mode/#soylent [+v chromas] by Imogen
[04:59:33] -!- chromass has quit [Ping timeout: 272 seconds]
[06:33:17] -!- chromas has quit [Ping timeout: 272 seconds]
[06:33:35] -!- chromas [chromas!~chromas@Soylent/Staph/Infector/chromas] has joined #soylent
[06:33:35] -!- mode/#soylent [+v chromas] by Imogen
[06:42:40] <chromas> w.t.fuckin'-f
[06:58:21] <kolie> ?
[06:58:29] <chromas> my net keeps masturbating
[06:59:27] <kolie> no net november?
[06:59:28] <kolie> lol
[06:59:44] <chromas> kolie++
[06:59:44] <bender> kolie: 18
[07:00:19] <kolie> night bro.
[07:02:22] <chromas> already? you just turned 18!
[07:03:27] <kolie> yea i gotta get rest i got a flight tmw I gotta be prepared for.
[07:03:47] <chromas> g'noight
[09:15:47] <Ingar> chromas: thanks, my net has been awful for weeks, seems better today
[09:16:12] <Ingar> I guess the critter decided to visit your sites instead of mine
[09:16:24] <chromas> Must have
[09:17:26] <chromas> cosmic rays shooting at my packets and giving them radiation sickness
[09:22:30] <janrinok> Have you added anything to your system recently or reconfigured a box somewhere. Perhaps it is a simple setting that is incorrect?
[09:26:05] <janrinok> I spent ages trying to solve a problem which was simply an incorrect IP on one of my boxes - but they are always correct aren't they...?
[09:27:14] <janrinok> If I had started trying to track the fault down like I should have done I would have found it a lot quicker than I did.
[09:42:13] <Ingar> my ISP is upgrading their wiring
[09:44:42] <chromas> I guess I could set up some pings when it goes down to see if I can still hit the isp and wahtnot
[10:26:59] -!- chromas has quit [Ping timeout: 272 seconds]
[10:27:15] -!- chromas [chromas!~chromas@Soylent/Staph/Infector/chromas] has joined #soylent
[10:27:15] -!- mode/#soylent [+v chromas] by Imogen
[10:28:14] -!- plethora [plethora!~plethora@98.98.um.zs] has joined #soylent
[10:31:49] <plethora> =submit https://www.rawstory.com
[10:33:13] -!- plethora has quit [Quit: Client closed]
[10:45:34] <chromas> this time, it seems the lan locked up too
[10:45:42] <chromas> Maybe switch or something is dying
[10:45:52] <chromas> the xlefay problem
[10:54:43] <ted-ious> Maybe ping from one of your lan systems to another and see if any packets ever get dropped.
[10:57:43] * chromas starts a pingin'
[10:58:48] <ted-ious> Do you know of a really good script or utility that records ping's and such and creates an archive of network outages or performance?
[10:59:36] <ted-ious> Running traceroute's in a loop and logging to a text file would work but that's not a very good solution.
[11:00:27] <chromas> I don't. What'd be nifty is an instant-messenger style interface that lists all the pingables like contacts, showing which ones are up or down, then maybe I could click to portscan or connect up to specific services
[11:00:37] <janrinok> ted-ious, fab23 has such software
[11:01:11] <chromas> I tried setting up smokeping once, then found out it's a whole web server package. too much work :D
[11:01:39] <ted-ious> Right that's a bit of overkill. :)
[11:02:26] <fab23> I guess janrinok means this: https://oss.oetiker.ch
[11:03:48] <chromas> "Written in dead language for easy enhancability."
[11:05:08] <fab23> they run a company with doing perl coding, seems not that dead https://www.oetiker.ch
[11:07:36] <janrinok> Well, at the other end of the scale you are looking a crontabl which pings various sites and presents you with the data to analyse. There might be something in between but I don't know of it.
[11:58:00] <Bytram> This email concerns the renewal of the domain name soylentnews.[net|org|com] at Gandi, for which you are a contact via the username or organization "SoylentNews".
[11:58:03] <Bytram> The domain name soylentnews.net will expire at the Registry in 60 days, on 09 Feb 2025 (UTC).
[12:00:03] <Bytram> (condensed & elided)
[12:02:36] <Bytram> kolie: ^^^
[12:48:02] <janrinok> Bytram, was it addressed only to you?
[14:46:39] -!- chromas has quit [Ping timeout: 272 seconds]
[14:46:55] -!- chromas [chromas!~chromas@Soylent/Staph/Infector/chromas] has joined #soylent
[14:46:55] -!- mode/#soylent [+v chromas] by Imogen
[15:44:17] -!- esainane has quit [Ping timeout: 272 seconds]
[15:57:31] -!- esainane [esainane!esainane@sendjocq.space] has joined #soylent
[16:54:59] <chromas> Definitely dropping packets in the lan. Even my network mounts go away for a bit
[16:58:12] <ted-ious> Time to buy another cheap 8 port switch?
[16:58:30] <ted-ious> They seem to be disposable consumables.
[17:59:15] -!- pleurinoma [pleurinoma!~pleurinom@195.146.u.ull] has joined #soylent
[17:59:34] <pleurinoma> Journal entries have been banned/disabled?
[18:04:00] <kolie> I'm not aware of journals being altered.
[18:07:00] <pleurinoma> Certainly none are being produced.
[18:10:07] <kolie> Guess no one wants to make anything or rn
[18:14:37] -!- pleurinoma has quit [Quit: Client closed]
[18:48:16] <fab23> 🤡
[18:50:42] <janrinok> kolie, o/ I thought you were flying somewhere today?
[19:23:00] <kolie> yea, headed over to the field soon.
[19:23:31] <kolie> grandparents 75th tonite too
[19:23:49] <kolie> going to head over there and seem them for dinner.
[19:24:03] <kolie> skys look calm and cielings at fl25 i think its all good.
[19:29:15] <janrinok> I hope you enjoy the evening!
[20:41:57] -!- svarog has quit [Ping timeout: 272 seconds]
[20:42:13] -!- svarog [svarog!~svarog@the.edge.of.sanity] has joined #soylent
[20:45:20] -!- pleuricast [pleuricast!~pleuricas@65.20.nko.ps] has joined #soylent
[20:46:41] <pleuricast> Why is janrinok diverting subs into the journals?   Has he lost his mind?
[20:53:18] <pleuricast> =submit https://www.bostonglobe.com
[20:55:51] -!- pleuricast has quit [Quit: Client closed]
[21:34:28] <Bytram> janrinok: The email (WRT cert renewal) was addressed to: admin@soylentnews.org
[23:34:51] -!- fab23 has quit [Ping timeout: 272 seconds]
[23:37:52] -!- fab23 [fab23!fabian@62.12.vng.u] has joined #soylent
[23:57:12] -!- systemd [systemd!~systemd@pid1] has joined #soylent