code logs -> 2024 -> Fri, 29 Mar 2024< code.20240328.log - code.20240330.log >
--- Log opened Fri Mar 29 00:00:04 2024
00:00
<&[R]>
I remember using pulseaudio back in the KDE 3 days, I was trying out KDE 3 for the first time. Didn'
00:01
<&[R]>
Didn't know that error messages had an accompanying error sound that was glass breaking
00:01
<&[R]>
Error would pop up, no sound. Hear glass break *15 seconds* later, go around the house for 30 minutes trying to find what the cat just destroyed
00:22 Vornicus [Vorn@Nightstar-ivektl.res.spectrum.com] has quit [Connection closed]
00:41
<@macdjord>
[R]: lol
01:53 Degi [Degi@Nightstar-kaliqh.pool.telefonica.de] has quit [Ping timeout: 121 seconds]
01:55 Degi [Degi@Nightstar-a6alpe.pool.telefonica.de] has joined #code
07:14 ToxicFrog [ToxicFrog@ServerAdministrator.Nightstar.Net] has quit [Ping timeout: 121 seconds]
08:23
< NSGuest22977>
Hahaha.
12:11
< NSGuest22977>
...
12:11
< NSGuest22977>
I'm trying to log into my energy provider's online service.
12:11
< NSGuest22977>
It's taking too long, so I click the button again.
12:12
< NSGuest22977>
I get a popup that the data was already sent and it's waiting for the server to respond.
12:12
< NSGuest22977>
I have concerns.
12:12
< NSGuest22977>
1. The server is slow.
12:12
< NSGuest22977>
2. The dev team knows it's slow.
12:13
< NSGuest22977>
3. It's been slow consistently and durably enough that they implemented a system to tell the user to enhance their calm.
12:27
< NSGuest22977>
It takes literally 5-10 minutes to process a request.
12:27
< NSGuest22977>
I am actually impressed that there's no actual timeouts yet.
13:12 ToxicFrog [ToxicFrog@ServerAdministrator.Nightstar.Net] has joined #code
13:12 mode/#code [+ao ToxicFrog ToxicFrog] by ChanServ
13:13
<&[R]>
Might also be a result of them knowin they occasionally get a massive spike in requests to process
13:32
< NSGuest22977>
Theoretically, I suppose, but I'm not hearing of a massive outage right now.
13:33
< NSGuest22977>
Not that outages are their responsibility. That's the distributor's, but I expect many consumers don't know.
13:55 Vornicus [Vorn@Nightstar-ivektl.res.spectrum.com] has joined #code
13:55 mode/#code [+qo Vornicus Vornicus] by ChanServ
13:55 Vornotron [Vorn@Nightstar-ivektl.res.spectrum.com] has joined #code
15:09 Vornotron [Vorn@Nightstar-ivektl.res.spectrum.com] has quit [Connection closed]
15:10 Vornicus [Vorn@Nightstar-ivektl.res.spectrum.com] has quit [Connection closed]
17:44 Emmy [Emmy@Nightstar-qo29c7.fixed.kpn.net] has joined #code
19:01
< bluefoxx>
Apparently a backdoor vuln has just been found in the 5.6 release of xz, fwiw if you're running debian or a rolling release like arch you might wanna version check and rollback...
19:01
< bluefoxx>
sounds like it tries to attack SSH
19:02
<@Tamber>
https://nvd.nist.gov/vuln/detail/CVE-2024-3094
19:15
< bluefoxx>
Yup, that's the one
19:17
< bluefoxx>
Apparently I installed 5.6 on my system last month, easy enough to revert back at least - and thankfully this isn't a system I run an SSH server on
20:32 Vornicus [Vorn@Nightstar-ivektl.res.spectrum.com] has joined #code
20:32 mode/#code [+qo Vornicus Vornicus] by ChanServ
21:12
<&McMartin>
Yeah, it looks like Fedora and Debian's stable releases didn't take it, but Fedora's beta did briefly, and both their unstables did
--- Log closed Sat Mar 30 00:00:05 2024
code logs -> 2024 -> Fri, 29 Mar 2024< code.20240328.log - code.20240330.log >

[ Latest log file ]