●● IRC: #techbytes @ Techrights IRC Network: Wednesday, February 19, 2025 ●● ● Feb 19 [00:12] *jacobk has quit (Ping timeout: 2m30s) [00:14] *jacobk (~quassel@syp65ggum2ibk.irc) has joined #techbytes [00:19] *jacobk has quit (Ping timeout: 2m30s) [00:21] *jacobk (~quassel@syp65ggum2ibk.irc) has joined #techbytes [00:24] *jacobk has quit (Ping timeout: 2m30s) [00:27] *jacobk (~quassel@syp65ggum2ibk.irc) has joined #techbytes [00:36] *jacobk has quit (Ping timeout: 2m30s) [00:40] *jacobk (~quassel@syp65ggum2ibk.irc) has joined #techbytes [00:49] *jacobk has quit (Ping timeout: 2m30s) [00:52] *jacobk (~quassel@syp65ggum2ibk.irc) has joined #techbytes [00:54] *jacobk has quit (Ping timeout: 2m30s) [00:56] *jacobk (~quassel@syp65ggum2ibk.irc) has joined #techbytes ● Feb 19 [01:00] *jacobk has quit (Ping timeout: 2m30s) [01:04] *jacobk (~quassel@syp65ggum2ibk.irc) has joined #techbytes [01:07] *jacobk has quit (Ping timeout: 2m30s) [01:09] *jacobk (~quassel@syp65ggum2ibk.irc) has joined #techbytes [01:14] *jacobk has quit (Ping timeout: 2m30s) [01:17] *jacobk (~quassel@syp65ggum2ibk.irc) has joined #techbytes [01:26] *jacobk has quit (Ping timeout: 2m30s) [01:28] *jacobk (~quassel@syp65ggum2ibk.irc) has joined #techbytes [01:31] *jacobk has quit (Ping timeout: 2m30s) [01:44] *jacobk (~quassel@syp65ggum2ibk.irc) has joined #techbytes [01:55] *jacobk has quit (Ping timeout: 2m30s) [01:55] *jacobk (~quassel@syp65ggum2ibk.irc) has joined #techbytes ● Feb 19 [02:05] *jacobk has quit (Ping timeout: 2m30s) [02:07] *jacobk (~quassel@syp65ggum2ibk.irc) has joined #techbytes [02:11] *jacobk has quit (Quit: No Ping reply in 180 seconds.) [02:19] *jacobk (~quassel@syp65ggum2ibk.irc) has joined #techbytes [02:36] *jacobk has quit (Ping timeout: 2m30s) [02:36] *jacobk (~quassel@syp65ggum2ibk.irc) has joined #techbytes [02:39] *jacobk has quit (Ping timeout: 2m30s) [02:44] *jacobk (~quassel@syp65ggum2ibk.irc) has joined #techbytes [02:47] *jacobk has quit (Ping timeout: 2m30s) [02:47] *x-amarsh04 has quit (Quit: Konversation terminated!) [02:51] *jacobk (~quassel@syp65ggum2ibk.irc) has joined #techbytes [02:53] *x-amarsh04 (~amarsh04@h5zkbfemmwig6.irc) has joined #techbytes ● Feb 19 [03:56] *x-amarsh04 has quit (Quit: Konversation terminated!) [03:57] *x-amarsh04 (~amarsh04@h5zkbfemmwig6.irc) has joined #techbytes ● Feb 19 [05:03] pi_ db [05:43] *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #techbytes ● Feb 19 [07:40] schestowitz[TR2] "Hackers use sophisticated macOS malware to steal cryptocurrency, Microsoft says | The Record from Recorded Future News" [07:40] schestowitz[TR2] x https://therecord.media/hackers-use-macos-malware-to-steal-crypto [07:40] schestowitz[TR2] # misrepresents m$ as an authority on anything [07:40] -TechBytesBot/#techbytes-therecord.media | Hackers use sophisticated macOS malware to steal cryptocurrency, Microsoft says | The Record from Recorded Future News [07:56] schestowitz[TR2] * #soylent :Cannot join channel (+r) - you need to be logged into your NickServ account [07:56] schestowitz[TR2] * #soylent :Cannot join channel (+r) - you need to be logged into your NickServ account [07:56] schestowitz[TR2] * Disconnected (Connection timed out). [07:56] schestowitz[TR2] * Looking up chat.soylentnews.org [07:56] schestowitz[TR2] * Connecting to chat.soylentnews.org (2602:fd63:12::2) port 6667... [07:56] schestowitz[TR2] * Connection failed. Error: Connection timed out [07:56] schestowitz[TR2] Cycling to next server in SN... [07:56] schestowitz[TR2] * Disconnected (). [07:56] schestowitz[TR2] * Looking up chat.soylentnews.org [07:56] schestowitz[TR2] * Connecting to chat.soylentnews.org (2602:fd63:12::2) port 6667... ● Feb 19 [09:01] *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #techbytes [09:02] *jacobk has quit (Ping timeout: 2m30s) [09:05] *jacobk (~quassel@syp65ggum2ibk.irc) has joined #techbytes ● Feb 19 [11:32] schestowitz[TR2]
[11:32] schestowitz[TR2][11:32] schestowitz[TR2]In this update, users will notice that the Unicorn Desktop now behaves much more reliably. Configuration files no longer get overwritten when you update the desktop package, and the global menus tendency to push the end of the panel off the screen has finally been resolved.
[11:32] schestowitz[TR2]Moreover, the wallpaper properly scales to different screen sizes, and the audio issues that previously caused some devices to lack out-of-the-box sound have been addressed, ensuring a more consistent multimedia experience across various setups.
[11:32] schestowitz[TR2]
[11:33] schestowitz[TR2][11:33] schestowitz[TR2]With that said, the Breeze theme no longer causes occasional crashes in non-KDE apps, KScreen Doctor now handles DPMS mode outputs more reliably, and Info Center no longer struggles with page flickering on its energy panel.
[11:33] schestowitz[TR2]Moreover, KWin, KDEs window manager, reduces graphical glitches and polishes advanced display features like night light and offloading for HDR. Among these changes, one of the more important is a fix that ensures brightness does not ramp up unexpectedly when you enable night light.
[11:33] schestowitz[TR2]
[11:37] schestowitz[TR2][11:37] schestowitz[TR2]This has been one of the longest-running debates in the Linux community, going back many years. Both brands have their loyal supporters, and discussions can get pretty heated. But in this article, were leaving bias at the door. I aim to give you a well-reasoned answer to help you navigate this not-so-simple decision.
[11:37] schestowitz[TR2]Lets cut straight to itif youre looking for a quick and simple answer, go with AMD. But that recommendation comes with a few important caveats. Keep reading if you want to make a truly informed decision based on your particular requirements. As always, the right choice depends on what you need from your GPU.
[11:37] schestowitz[TR2]