04:35 <nyanpasu64> dumb idea: if you're trying to trigger speaker burnout on stock apple hardware, try playing out-of-phase audio in the left and right channels, since apple amplifies out-of-phase sound in this dumb stereo widening filter you can't turn off

10:37 <bluetail> nyanpasu64 why would you want to destroy speakers?

11:29 <chadmed[m]> For science

11:37 <mps> chadmed[m]: does count my washing mbp as science :)

11:39 <bluetail> how do u wash it? 100% alcohol? :D

11:40 <mps> pipe water

11:41 <bluetail> oh no

11:42 <mps> though serviceman told that he saved few of them 'washed with beer'

11:50 <bluetail> sure that wasnt a joke?

12:01 <mps> well, I have no reason to not trust him, though I didn't saw with my eyes

12:04 <bluetail> I'd rather not have beer smell in my pc

16:34 <nyanpasu64> bluetail: Marcan was testing destroying speakers in asahi on Twitter, and mentioned it was possible in macos too

16:34 <bluetail> nyanpasu64 thanks for explaining. I appreciate

16:35 <GllmR[m]> `:: Remplacer kdesdk-kioslaves par extra/kdesdk-kio ? [O/n]` After a pacman -Syu, is it normal ?

16:36 <GllmR[m]> Can i update asahi with pacman without breaking my installation ?

16:41 <j`ey> GllmR[m]: yes

16:41 <j`ey> I mean, there's not a guarantee that, but that is the aim

18:07 <doootard[m]> anyone running sway? I have a weird issue witch scaling on 2020 m1 air. Integer scaling looks awful even on native wayland apps, but it seems to be working well in gnome.

18:12 <bluetail> I'm fine with sway, actually it looks better for me... confused

18:12 <bluetail> there shouldnt be diff

18:12 <bluetail> right?

18:12 <bluetail> perhaps all in my head

18:14 <doootard[m]> could be something on my end, but it's really weird. it works perfectly on my thinkpad, but on the mac scale 1.75 makes fonts unreadable almost, but really sharp with scale 1 or 2

18:43 <j`ey> I ran sway with scaling, fractional scaling looked bad but 2scale was fine

18:45 <bluetail> some apps require to run in wayland mode

18:45 <bluetail> did u pass wayland args for firefox?

18:45 <doootard[m]> so I managed to fix firefox by setting widget.wayland.fractional_buffer_scale to match my scaling in sway. Not sure how to fix it systemwide though

18:46 <doootard[m]> yeah these are all native wayland apps. Even the fonts in waybar are ugly

18:47 <waldi> doootard[m]: wayland fractional scaling is weird. if i understand it correctly, it renders a larger version and scales it. this can't provide proper font rendering. afaik the only solution is to use integer scaling and change the font size

18:49 <bluetail> fractional scaling works like a svg if setup properly

18:51 <bluetail> even 1.25...

18:51 <doootard[m]> waldi: I don't see the same issue on my pc/thinkpad with fractional scaling though, both running sway.

18:51 <doootard[m]> https://imgur.com/a/3Umpdmv

18:51 <doootard[m]> scale 2 vs scale 1.75 on the mac

18:53 <bluetail> u run firefox right?

18:54 <doootard[m]> I do. Firefox is working now after setting widget.wayland.fractional_buffer_scale to 1.75 in about:config to match my scaling. But other apps are still ugy, waybar,tilix, gedit. None of them are on xwayland

19:03 <bluetail> whats your environment variables set to?

19:03 <bluetail> upload it

19:07 <doootard[m]> bluetail: https://pastebin.com/EgEFD7Xf

19:07 <bluetail> cant access

19:07 <bluetail> use termbin or so

19:09 <doootard[m]> sorry about that, https://termbin.com/c6eok

19:10 <bluetail> why dont u have QT_QPA_PLATFORM="wayland" for instance

19:10 <bluetail> take a look at mine... https://termbin.com/fuyc

19:11 <bluetail> before saying wayland doesnt work, make sure its not your cause

19:11 <doootard[m]> I don't have any QT vars cause I didn't install anything QT yet :)

19:11 <bluetail> what about mozilla tho

19:13 <doootard[m]> export MOZ_ENABLE_WAYLAND="1" is the default on wayland sessions on fedora, so it doesn't need to be set explicitly. If I go to about:support it's listed as set to 1

19:15 <bluetail> Having those values not in one file is not good...

19:21 <doootard[m]> as a test I set up the vars, no difference

19:23 <bluetail> idk then mate

19:24 <compassion> i wonder if I can get this to be a daily driver. almost.

19:33 <bluetail> I use it as my daily slave

19:33 <bluetail> doesnt have enough display outs anyways

20:25 <compassion> true. it's one HDMI out and no extra screens on the M1 MBP?

20:28 <j`ey> currently yes

22:14 <bread_crumb[m]> >"In the meantime, we recommend that users concerned about physical security enable FileVault in macOS. This will implicitly add a log-in requirement to recovery mode, which will prevent an attacker with physical access from being able to compromise your OS that way. m1n1 does not yet have a secureboot mode, but it also doesn’t have any local access features as long as it is installed properly. Locking down U-Boot and GRUB and the rest

22:14 <bread_crumb[m]> of Linux is left as an exercise for the user."

22:15 <bread_crumb[m]> I am not very technical when it comes to boot processes etc. but I would like to ask, if FV is set up then is locking down UBoot/GRUB necessary to have full security?

22:18 <bread_crumb[m]> Also I suppose GPU acceleration isn't fully implemented yet, could this have potential negative impacts on my CPU lifetime if it is being used to also handle graphics?

22:18 <bread_crumb[m]> * handle graphics? I mean I guess it has to definitely have _some_ wear impact.

22:25 <bluetail> I doubt this is measurable

22:30 <bluetail> Especially since electron migration is probably still super low since those m1 rigs are not particularly under a increased load like you would have with an overclock + increased voltage. What often happens in cpus that were overclocked with a specific setting, is that it wont hold up for many years with that specific setting. Thats when electron

22:30 <bluetail> migration had taken place and same would now need a higher voltage...

22:49 <bread_crumb[m]> <nyanpasu64> "bluetail: Marcan was testing..." <- https://github.com/AsahiLinux/linux/issues/53 just posting this issue. Funny how they found some limits after breaking the microspeakers. I wonder how that paper which was referenced had similar values, must be a coincidence right considering that seemingly the paper isn't at all related to the actual hardware components they are talking about?

22:57 <bluetail> such an interesting read. thanks for linking

23:01 <bread_crumb[m]> <bluetail> "Especially since electron..." <- I searXed quickly, you are meaning electromigration or electron migration (or both same)? Nevertheless I get your point, thanks.

23:02 <bluetail> I dont know :>