Wasn't Fennec a couple of major revisions behind due to build issues, and one of said major revisions was a zero-day fix, so yeah, Fennec would be vulnerable.
(I dumped it about two weeks ago once I noticed that it was behind the security patch curve.)
I like this method of shaming corpos making piles of money on free labor much more than what a certain other open source CEO is currently trying.
I'm just waiting for the 'but we can't afford it!' lines to start coming out of these companies as their next excuse as to why they couldn't possibly contribute back to the software that makes their entire business work.
And, well, okay, but if your business doesn't work unless you have the unpaid labor of thousands of volunteers, perhaps we don't need you?
I'm shocked I didn't get downvoted to shit myself.
It's just that it was VERY clearly either sanctions or a NSL, since the Linux Foundation is in the US and the two things that result in a public entity like that making silent, un-explained changes are, well, sanctions and NSLs and you don't say shit because your lawyer told you not to.
I don't necessarily agree that tossing contributors off an open-source project is in the spirit of the OFAC list, but the problem almost certainly is that they're employed by some giant tech company in Russia.
And, in Russia, like in the US, and Israel, and China, and anywhere else you care to mention, tech companies are almost always involved in military supply chains, since shit don't work without computers at this point.
Which leads to a cycle of being unable to work with Weapons, Inc. and someone works for Weapons, Inc. so now that person can't be worked with either and so your choices are.... comply with the OFAC list, or take a stupid amount of legal risk up to and including angry people with guns showing up to talk to you.
We really don't know the whole story and immediately jumping to "Imperialists bad!" is how certain chunks of Lemmy roll these days.
I think they'd be much happier if they all moved to North Korea and helped achieve the goal of Juche by becoming dirt farmers.
but what the hell will be in my next flagship phone I’m planning to buy next summer
Probably a Snapdragon X Elite Extreme Ultra Mega Pro XxxxX or whatever their naming scheme is now.
The odds that ARM will get an injunction preventing Qualcomm from selling chips is basically zero. The courts are rarely going to torpedo an entire company over a dispute like this when the facts are very much in dispute and very... subjective.
This is a scenario where nothing changes until the case ends and then either ARM has to build another moneybin to store their settlement, or literally nothing happens.
If it was Chris Roberts, it'd just be a JPEG of a dinosaur and a promise that the mount is in the pipeline for early pre-production to be added to the next major quarterly alpha release once it's ready.
Because I stuck a 1TB sd card in my phone and don't have to deal with transcoding or dealing with, well, anything, but copying new files over and listening to things.
I've developed quite the liking for stupidly simple solutions, and 'copy the files to a sd card' is about as simple as it gets.
I'm going to go another route here: do you need streaming?
Like, I've simply gone with a giant pile of FLACs that I put on a SD card for my phone, and use over the NAS for when I'm at home and don't currently use any fancy-pants streaming stuff.
So like, depending on how you're using your music library, you might not even need to drop deep into the giant self-hosting rabbithole for this.
I hate to be that guy, but uh, what do the logs say?
The container logs would probably be most useful since you should (probably) be able to tell if they're having issues starting and/or simply not attempting to launch at all.
That's probably because they built a protocol specifically for a usecase, rather than building a protocol and hoping that someone will come along with a usecase.
Which is exactly what anyone who wasn't wanting to just snort some concentrated outrage knew was the case.
And you can argue as to if OFAC list should apply to things like this or not, but the problem is that the enforcement options for OFAC violations include 'stomp you into the ground until you're powder', most people are just going to comply.
Well I went to look because that option has always been there as far back as I can recall, so I assumed the exact opposite: it's something they had recently broken.
But, as far as I can tell, once you get to the check out step you can pick pay in full or apple card installments, so I'm just confused as to who this didn't work for, and why it didn't. (I'm not doubting that apple is perfectly willing to do this kind of fuckery, just that it doesn't look like it applies to everyone everywhere all the time.)
Wasn't Fennec a couple of major revisions behind due to build issues, and one of said major revisions was a zero-day fix, so yeah, Fennec would be vulnerable.
(I dumped it about two weeks ago once I noticed that it was behind the security patch curve.)