incredibly dumb

police

that makes it extra sus tho

not gonna get fully into the weeds here but ‘have no leadership to revoke’ is an odd point to try and make when the covid disinfo campaign absolutely had leadership.

this martin guy is the same one who made the asahi linux drama a thing and brigaded torvalds?

yeah. fuck that guy. i don’t care what he has to say about some 20 year old code that nobody cares if it was decompiled from ninty’s sdk or not. nintendo isn’t even making a fuss about it! this is all just martin scrambling for more attention, again.

daily reminder that luddites weren’t against new tech out of fear or misunderstanding, they were against the owner class hoarding all extra productivity as wealth instead of reducing workload and/or increasing pay for the workers alongside tech advancements.

yet

it seems pretty obvious to me on word meanings alone that ‘color management protocol’ isn’t only for relatively new hdr tech, but instead everything to do with color management, like how color profiles are under ‘color management’ in the system settings you’re telling me to use that the wiki says isn’t ready yet…

from https://wiki.archlinux.org/title/ICC_profiles

"Wayland

Wayland supports color management through color profiles, but the user interface for managing these profiles is currently not implemented properly. However, you can manually add a color profile through the following steps: Firstly, copy your .icc color profile file to the /usr/share/color/icc/colord/ directory. Run colormgr get-profiles to obtain the available color profiles, and colormgr get-devices to obtain the IDs of the attached devices. To assign a color profile to a device, use the command colormgr device-add-profile Device_ID Profile_ID. The device ID is obtained from the output of colormgr get-devices and the profile ID from colormgr get-profiles. For example, if your device ID is “DP-3” and the profile ID is “icc-5fb87663ba378cadf463ba64d92dced3”, the command would look like: $ colormgr device-add-profile DP-3 icc-5fb87663ba378cadf463ba64d92dced3 With these steps, you can manually manage your color profiles in Wayland until the user interface is fully implemented. Once the ICC profile is added with this method, it will show up and work as expected in system settings like Color Manager in the KDE Plasma settings. "

copy to colord folder, eh?

the part i have trouble with is colormgr shows no devices and nothing happens trying commands to load an icc profile. it’s no big deal, i’ll just use x11 until this gets fixed but others on arch forums and reddit threads has this same issue with kde wayland, and judging by the ‘user interface isn’t ready yet’ i’m guessing it’s just not ready yet.

but sure, colord has nothing to do with it and color management protocol is ONLY for hdr tech.

am i taking crazy pills?

i’m using kde on endeavouros. when using wayland the color profiles section in settings does nothing. you can go pick a profile and click ok but it just doesn’t load it. colord is the daemon that handles color profiles entirely and that’s what this is about.

not just hdr stuff, it’s all color profiling. my old monitor is dark af with wayland because it’s not loading its color profile and i can’t adjust gamma or apply color profiles in settings or with colord like you can in x. i really need this to be able to switch to wayland.

this is a concept i’ve been trying to put into concrete terms for myself and you just, like, fuckin nailed it right down. thank you so much.

mint is good, pop!os is also good, i use and recommend endeavouros as arch-but-easy. tbh just about any popular distro these days is prolly gonna do fine for the average user.

pop!os reportedly packs in and handles the proprietary nvidia drivers for you, which can be a pain to handle yourself. i haven’t tried it nor do i have nvidia but i see it highly recommended a lot.

deleted by creator

yt android has been buggy as fuck for me. randomly disconnecting while casting, captions stopping halfway thru a video and the button for them greyed out until i disconnect and restart the app, no tab buttons at the bottom when i first open and it goes straight into shorts instead of homepage until i back out then restart the app, sometimes when trying to watch a video on the app and not casting it just straight up refuses to play not even showing a buffering symbol just the play button like a static image. it’s gotten ridiculously bad.

deleted by creator

sodium. gravity. carbon capacitors. lead acid. molten salt. air pressure. flywheel.

there’s alllll kinds of battery storage solutions, and for grid storage just about anything other than lithium can be used because lithium is really only useful for power density applications where weight and size of the battery matters like cars and planes.

nuclear fission is dead. fusion is the only nuclear worth talking about and that’s still years, probably decades away from being actually useful.

so then: solar, wind, wave, hydro, geothermal, and all kinds of batteries is what we have now and can do cheaply and do everywhere and do it now.

why do nuclear diehards always pretend it’s nuclear or fossil fuels only, like renewables are nonexistant? it smells bad faith as fuck. nobody arguing against nuclear fission power plants are arguing for fossil fuels. absolutely nobody.

don’t know why you’d want to? you may trust your dns server but without dns over https the dns requests themselves are sent plaintext and are vulnerable to man-in-the-middle attack. with dns over https the dns requests are encrypted and that encryption would have to be broken for a MITM attacker to see your requests. more security is better and dns over https costs virtually nothing to use in terms of cpu resources.

edit: oh do you mean whole system mullvad VPN? if so, then yeah dns over https doesn’t really help much but it’s also still a case of why bother turning it off when there’s no benefit to it.

linux typically won’t hard freeze on errors like that no matter the distro. it can, but rarely. being an all amd build i suspect there’s some cpu bios feature auto scaling core clock or voltage and in my experience ryzen cpus need to have a manually set stable clock and voltage to perform properly no matter the os. try checking your bios and disabling any powersaving or auto-scaling features for your cpu and manually set it for stock clock and voltage. you may need to look up what these values are as the bios might not have a default value for you. this might not be your issue but it’s worth trying. good luck!