Not really. The cords are all the same inside, the colors are just for convenient matching of the ends.
If both ports are the same color, and wire has the same color on both ends, you’re fine. You can send yellow through a red cable. I’ve definitely had a few times where all I had were a couple of loose cable pairs and it works fine.
You could a little with the later component cables where there were separate ones for the different colors, but the “original” composite cables (yellow, red, and white) only had one video cable and the other two were left and right sound. You could get odd patterns in the static with the sound plugged into the video port, but that was about it. Before that was the single coaxial cable that carried video and sound together, so there wasn’t easily available messing with that without damaging the cable or doing magnetic or RF shenanigans against an unshielded cable.
That said, if you get into messing with some of the old hardware in different ways, you can get some real wild effects from those old analog media standards/hardware/cables.
There’s small communities online doing stuff with it. Search for analog glitch art, analog data moshing, and circuit bending (although that last one is more abusing where digital circuits and hardware are susceptible to analog style weirdness due to basic physics of how electric signals work “analogly” between components).
If you saw anyone else hanging around a garden or forest you might say they’re gardening, foraging, vibing, touching grass, or waiting until their mortal body is reclaimed by nature. But when it’s a gnome they have to be plotting?
If you treat them like you would any other magical creature, spent some time to get to know them, you’d see just how wrong you were. Spend a little less time pondering your orb and little more time out in the real world.
Besides, if you examine the statistics, you’d see that skinwalkers are the real problem. Despite making up only… But I can tell you aren’t ready to be red potioned on that yet.
Good job putting to words one of the core issues I’ve had with using LLM chat for work. Stop trying to design an entire fucking system or solution and just answer the damn question I actually asked, by using natural language to search documentation and existing implementations.
I would tell it to only answer exactly what I asked, but sometimes I do get value from it “exploring” on occasion. It’s just so much damn worse with it than my newest junior co-worker who is known on our team for getting hours deep into tangential rabbit holes before coming up for air and asking seemingly nonsequiteur questions.
Doesn’t help the conversation that some LLM chat systems call minor customization of the prompt making an agent.
Under duress I use CoPilot Chat at work. No, the basic sad customization I did along the lines of “don’t be sycophantic, always cite sources, use these specific official documentation sites as sources before searching outside of them and clearly call out when you search outside them” that customization isn’t making a damn agent, it’s adjusting the prompt and saving those changes you disingenuous marketing fucks!
Dating just about forever
Smartest might be a stretch
Looks to me like an out of focus shot of Joey, the guy that wrote the “a softer world” comics, sitting on the ground.
It’s more of an artsy webcomic than necessarily a comedic one, although there are plenty of funny ones. Some of them are more musings about the world than anything else, as I feel this one is.
This is a particular message that stuck with me in the more than a decade since I first read it, and it’s damn good advice.
Fair enough. I work in IT but endpoint config and group policy isn’t my area at work, so most of my experience is with my personal computers at home. I at least usually hear the latest bullshit Microsoft is pulling from our endpoint management/config guy.
I should also bear in mind that I stripped down and customized the hell out of the install media before I last installed Windows on any of my devices, and I’ve run a shit ton of other customization/privacy/debloat tools afterwards as well. Usually by examining the policy and registry edits or PowerShell code they run and just picking and choosing parts for myself. Lots of good tools out there, but none I trust to do exactly what I want with no oversight or investigation.
I’d still say that Group Policy is usually the best option for configuration shit sticking though, due to it being Microsoft’s “business side” solution for endpoint config for quite a while now.
Except that these are group policy settings. The stuff they provide to allow businesses to manage their endpoints. Businesses that actually have enough size and money for Microsoft to care. Businesses that can have strict audit and data security requirements relating to things like not allowing data to even brush against something like OneDrive.
To be more direct, the only reason I can’t count the number of times they’ve broken a Group Policy is because I legitimately don’t recall it happening in the past decade.
If you work at a company where all of its offices are in the same time zone and you’re time-stamping logs, then it’s more expedient for understanding and placing an event in time against other things to use local time.
Unless everything is already standardized as GMT with offset I guess, but I feel like down that route lies madness.
“I got your email at 20:37:45-7:00” is a few more steps than “I got your email at 1:37PM”.
It’s not a big hurdle, but I try to design for the newest member on the team scrambling in panic rather than a calm cool professional already familiar with conventions.
Now, as soon as we do start dealing with multiple time zones I would just cut my custom time formatting string down to the shorthand to have the scripting language output in the full ISO 8601 format. But until then, being able to easily sort the the date properly and having the time be more human readable is a more “workable” compromise.
Except I can’t get behind the time part of it, personally. I can see the point of doing GMT with the offset if you’re working across multiple timezones, but it’s overkill for situations where you aren’t.
It was originally a shitposty way to drown out/protest the overwhelming flood of every goddamn post in the shitposting and meme communities being about American politics.
They need to do way instain mothers
No, if you knock it over it holds nothing you useless prat! God dammit this is why we can never have anyone over! Ten years. Ten. Years! I kept thinking, maybe this is the time you’d be able to- to- fuck it. It’s not worth it anymore. I’m done. I think I’ve been over this for a while now, but it’s real now. You can be here, with your cans and your beans and your fucking shit mess everywhere! Without me.
No, it’s fine. It’s fine! You just go do exactly what you want. What you’ve always done. Just without me now. It’ll be even easier for you. Goodbye.
Sure, and that’s just as valid points against them as well. For my part at least, none of this is meant as some sort of death knell, or direct damning evidence that some software is some sort of terrible piece of garbage.
I just refuse to believe that someone would literally be entirely incapable of comprehending any of the reasons people dislike systems to only be capable of engaging with the criticisms in bad faith.
That only has impact on the security risk surface exposed for your own install and for troubleshooting on your own machine. The maintainers and other coders on the project still have far more space, complexity, and features to cover.
It’s not a death knell by any means, but still a valid cause for concern.
As someone who designs systems as part of his job, “it violates Linux philosophy” is a perfectly valid reason to hate something as critical and low level as an init system.
I think “hate” is a strong word, mind, but following consistent design patterns and constraining scope matters. The problem is that it’s one of those things that doesn’t tend to matter until shit hits the fan.
The scope creep exponentially raises the efforts needed to properly test, troubleshoot, secure, and just generally work with the project code. The unique design creates rough edges for integrations with other pre-existing systems and tools, while also raising the effort needed for troubleshooting when something goes wrong.
There’s also the whole “Chesterton’s Fence” aspect to a lot of it, where the project runner’s overall attitude has been dismissive of existing conventions and separation of functionality.
There’s a lot of perfectly valid reasons to dislike it. That said, I think full on hate is extreme for an aspect of the overall Linux “system” and “user experience” that most users never interact with. Like having an opinion on the order your BIOS handles things in.
Yeah, I think that’s the running theory of the corporate backup plan if/when AI falls through and they need to find a use for all the data center resources.