HomeSearchPrevious dayNext day

00:00:40<fireonlive>
00:00:51<fireonlive>blankpost!
00:07:30<fireonlive>05:06:08 PM -ChanServ- #🔥 is now registered to fireonlive.
00:07:37<fireonlive>my fellow americans, the future of IRC
00:30:36Naruyoko quits [Remote host closed the connection]
00:30:58Naruyoko joins
00:31:01<@JAA>jasonswohl: The manufacturer has nothing to do with it, this is a random webshop selling the lock. And I think it's just the first couple search results for the lock's name on YouTube. LPL shows up at the top there as well.
00:32:26<fireonlive>does he open it up on 0.5s
00:32:28<fireonlive>lol
00:32:31<fireonlive>son/in/
00:34:11<@JAA>Nope, it actually holds up fairly well considering it's pretty much the worst lock ABUS even makes: https://www.youtube.com/watch?v=pnzMCCqzu14
00:41:21<nicolas17>JAA: https://notnow.dev/notice/AVmlOyqBbHtaqFFqFM
00:41:40<fireonlive>ah!
00:41:59<@JAA>> To use Pleroma, please enable JavaScript.
00:42:02<@JAA>Nah, I'm good. :-)
00:42:23<nicolas17>pfft
00:42:28<nicolas17>> This is the LockPickingLawyer, and what I have for you today is a Python "Global Interpreter Lock"
00:42:39<@JAA>Heh
00:43:37<fireonlive>yeah not bad as some i've seen lol
00:43:59@JAA calls PyGILState_Release.
00:44:15<@JAA>And to make it more interesting: via ctypes :-P
00:50:24<fireonlive>JAA: Your call has been forwarded to the automated voice messaging system, PyGILState_Release is unavailable. After the tone, please record your message. When you are finished recording please hang up.
00:50:28<fireonlive>*beep*
00:51:16@JAA sends a SIGSEGV.
00:54:36<fireonlive>x_x
01:02:14h3ndr1k (h3ndr1k) joins
01:05:51h3ndr1k_ quits [Ping timeout: 265 seconds]
01:06:44<fireonlive>apcupsd → h2i → real-time power alerts!
01:07:59<@JAA>:-)
01:08:58<fireonlive>=]
01:19:52katocala quits [Ping timeout: 265 seconds]
01:20:24katocala joins
01:51:49sonick quits [Client Quit]
02:05:58<jasonswohl>@a query anyone work ISP level fiber provider?!
02:06:52justmolamola joins
02:10:42<jasonswohl>reason i ask............. been having packet loss issues on frontier fiber for nearly a week, more than a dozen convos with tech support, still no resolution. As far as i know, should be a passive network to the "head office" and IMO other than latency and upload why i signed up. So, with 5-25% packet loss for ~a week now, and now only packet loss
02:10:43<jasonswohl>under bandwidth tests/heavy WAN network load. Anyone have any insights. as to what might reasonably explain this?
02:52:11BearFortress quits [Ping timeout: 265 seconds]
03:11:00<pabs>perhaps something on the network path is oversubscribed?
03:11:58BearFortress joins
03:25:00<jasonswohl>pabs i mean sure, i'd get that. Prob being that, a: no issues for a month of vaguely heavy usage (generally not compared to this "lot") and b: from what i noticed no latency difference regardless of usage, C: after a week of ~20% wan packet loss now my only issue is that I only get packet loss during BW tests, or heavy load. WTF is goin on? like i
03:25:00<jasonswohl>thought the whole promis of fiber was that is was more reliable?! I know there are opicts on the "head end" that do some magic or something or other with wavelengths or something or other and that is a part of the reason of my recent issues, but for them to say it's resolved then get continued issues.......... tf
03:26:12<jasonswohl>also pabs it has been a month but according to the tech who did my install, i was 1st on my street/splice box. although that doesnt discredit your theory for sure
03:27:00<imer>could be anything tbh, A year ago I had a flakey connection randomly for a few weeks before it just died, tech came out (business connection so next day thankfully), ended up finding the cable loose in the cabinet down the street, how that even happened he did not know either
03:28:53<imer>if it happens with the isp provided speed test site it's probably something on their end unless your router is just dying (which might be their problem too if it's an isp provided one)
03:31:04<jasonswohl>imer im quite simpathetic, however i dealt with intermittent packet loss with "cox" for ~4 years on a resi/busi conn had ~1 year of trouble free service w/ comcast at new address, thought frontier would be better because of better u/l or synchronous and have had far more probs then are warranted IMHO
03:31:37<imer>just gotta play dumb sometimes with tech support I find, especially the first level people will just be following their protocol and won't really be able to do anything outside what their protocol says (ymmv of course)
03:33:00<jasonswohl>imer 2 days ago onsite tech stated that there was an issue at head office w/ a "card" causing ~200+ tickets issue was resolved re: packet loss, then i try and have my son DL a game, get ~5-25% loss on wan (using pFsense on a R510 esxi 6.5U3)
03:34:08<jasonswohl>imer my almost entire experience w/ Frontier support either personally, or for a busi acct for a MSP client when that was something i used to have to deal w/ has been lackluster at best
03:35:38<imer>can't really say anything about specific companies in the us, only had the misfortune of dealing with a few over in europe, current one (small fiber one) has been pain-free so far thankfully
03:36:07<pabs>have you got mtr up looking at where in the traceroute the packet loss is happening?
03:37:05<jasonswohl>mtr? @ pabs ?
03:37:38<jasonswohl>im basing packet loss on pFsense graphing (and my own pings) to its own default GW
03:44:26<pabs>jasonswohl: https://www.bitwizard.nl/mtr/ - packages in all the Linux distros
03:44:33<pabs>probably in BSD distros too
03:46:32<jasonswohl>good shout pabs i'll check it out but. quite confident this is an issue of frontier being........... incompetent which is me putting it nicely (have bookmarked though)
03:47:24<pabs>wouldn't be surprising. mtr is great, a cross between traceroute and ping
03:47:57<jasonswohl>pabs /s but what about the glory that is pathping?! :)
03:52:56<pabs>hadn't heard of it :)
03:53:30<pabs>ah, windows thing that sounds similar to mtr
03:53:42<jasonswohl>pabs almost like we've never hear of sarcasm :)
03:53:51<pabs>:)
04:01:51<jasonswohl>this now does conclude my activity for teh night :( as i used to say to my children: nuh night time :) lol night y'all
04:08:21BigBrain quits [Ping timeout: 245 seconds]
04:10:29BigBrain (bigbrain) joins
04:18:49<fireonlive>night!
04:18:50<fireonlive>=]
04:22:27hitgrr8 joins
04:38:31fishingforsoup_ quits [Ping timeout: 265 seconds]
04:39:02fishingforsoup joins
05:14:27<fireonlive>https://twitter.com/titanicsub
05:14:35<fireonlive>omg
05:39:01BlueMaxima quits [Read error: Connection reset by peer]
06:47:14le0n_ (le0n) joins
06:47:23le0n quits [Ping timeout: 252 seconds]
06:51:55le0n_ quits [Ping timeout: 265 seconds]
06:53:26le0n (le0n) joins
07:09:29Arcorann (Arcorann) joins
07:54:16AlbertLarsan68 (AlbertLarsan68) joins
08:27:48AlbertLarsan681 (AlbertLarsan68) joins
08:30:31AlbertLarsan68 quits [Ping timeout: 265 seconds]
09:14:48AlbertLarsan68 (AlbertLarsan68) joins
09:16:55AlbertLarsan681 quits [Ping timeout: 265 seconds]
09:49:11Meli quits [Quit: After some time of wasteful lurking, 's brain 63gf4u1ted! X_x]
11:03:48AlbertLarsan681 (AlbertLarsan68) joins
11:06:09AlbertLarsan68 quits [Ping timeout: 265 seconds]
11:40:32AlbertLarsan681 quits [Client Quit]
11:43:22lk quits [Ping timeout: 265 seconds]
11:44:11lk (lk) joins
12:12:00justmolamola quits [Remote host closed the connection]
12:14:03justmolamola joins
12:16:33justmolamola_ joins
12:19:44justmolamola quits [Ping timeout: 258 seconds]
12:19:54justmolamola_ quits [Remote host closed the connection]
12:26:37albertlarsan68 (AlbertLarsan68) joins
12:58:46AmAnd0A quits [Ping timeout: 265 seconds]
12:59:00AmAnd0A joins
12:59:36cdub joins
13:12:23asie2 quits [Quit: WeeChat 3.0]
13:26:08Arcorann quits [Ping timeout: 252 seconds]
13:33:46BigBrain quits [Ping timeout: 245 seconds]
13:37:32BigBrain (bigbrain) joins
13:57:03<Hans5958>https://old.reddit.com/r/sbubby/comments/1470dp8/the_developers_dream_app/ lol
14:03:12SF quits [Remote host closed the connection]
14:15:17SF joins
14:54:37Sluggs quits [Excess Flood]
14:54:56Sluggs joins
15:41:39ThreeHM quits [Ping timeout: 265 seconds]
15:43:20ThreeHM (ThreeHeadedMonkey) joins
15:54:13Dango360 quits [Ping timeout: 265 seconds]
16:01:49Dango360 (Dango360) joins
17:39:08lk quits [Ping timeout: 252 seconds]
17:39:30lk (lk) joins
17:57:47PredatorIWD quits [Read error: Connection reset by peer]
18:50:44TheTechRobo quits [Ping timeout: 258 seconds]
18:51:02TheTechRobo (TheTechRobo) joins
19:57:11lk quits [Ping timeout: 252 seconds]
19:57:26lk (lk) joins
20:04:20<fireonlive>"Dear Red Hat: Are you dumb?" https://www.jeffgeerling.com/blog/2023/dear-red-hat-are-you-dumb , https://news.ycombinator.com/item?id=36436786
20:28:18sarayalth_ (sarayalth) joins
20:32:08sarayalth quits [Ping timeout: 265 seconds]
20:32:08sarayalth_ is now known as sarayalth
20:46:09lk quits [Ping timeout: 265 seconds]
20:47:08lk (lk) joins
21:08:16<fireonlive>^ from Rocky Linux's etherpad/mad scramble; one of their possible options lmao: https://i.postimg.cc/BvmPZF4r/image.png
21:08:50<fireonlive>(https://etherpad.opendev.org/p/r.24fab14385c0aa2db6fa7340a8b2aae7)
21:51:03icedice (icedice) joins
21:57:34AmAnd0A quits [Read error: Connection reset by peer]
21:57:56AmAnd0A joins
22:13:31cdub quits [Ping timeout: 258 seconds]
22:38:46AmAnd0A quits [Ping timeout: 265 seconds]
22:39:18AmAnd0A joins
23:11:14AmAnd0A quits [Read error: Connection reset by peer]
23:11:34AmAnd0A joins
23:30:35AmAnd0A quits [Read error: Connection reset by peer]
23:31:42h3ndr1k_ (h3ndr1k) joins
23:31:50AmAnd0A joins
23:32:54h3ndr1k quits [Ping timeout: 265 seconds]
23:34:10hitgrr8 quits [Client Quit]
23:39:12Arcorann (Arcorann) joins
23:45:47sec^nd quits [Remote host closed the connection]
23:46:00sec^nd (second) joins

HomeSearchPrevious dayNext day