PS: they did release technical details once the mitigations had been released etc. And these were released to tech researchers earlier, and proof of concepts were shown etc. https://youtu.be/QuqefIZrRWc?t=1005
And, like, the fact that AMD released an urgent patch for it should kind of speak to the severity of the issue in the first place. AMD doesn't patch "sudo lets you do root things", obviously, so it necessarily must have been more than that, and this was obvious even at the time. But we have to go through this dance with literally every single AMD exploit.
AMD has a unpatched exploit in all Zen3 and below processors that leaks data from kernel at a faster rate than meltdown did. It was discovered by the same researchers that discovered meltdown. AMD has chosen to leave that unpatched, and put out a weaselly deflection about "it doesn't cross address boundaries" but they also still refuse to turn KPTI on by default because it would hurt their benchmarks. And without KPTI there is no address boundary to cross, that's the weaselly part. AMD very craftily made it sound like they're saying there's not an issue, but in fact they are fully confirming the finding from the researcher, including the suggested mitigation (enabling KPTI), they just don't recommend that you do it. The statement is deliberately short to avoid inclusion of too many details that might dispel these misleading impressions.
This follows that same researcher (who previously discovered meltdown) uncovering a prior series of vulnerabilities in the cache ways predictor that also nullify KASLR... which AMD refused to patch because it "didn't leak actual data, only metadata"... the metadata being the page-table layouts. That one is still unpatched too - as the researchers note, AMD never actually mitigated this either, just more weasel words.
(this one literally doesn't even seem to have a security bulletin page for itself so I guess they have fully shoved this one down the memory hole now, but here's the news item from wayback) http://web.archive.org/web/20200325045817/https://www.amd.co...
After 6+ years of watching the community defend this behavior, downplay exploits from their favorite megacorporation, etc, it just gets old. Not liking how CTS labs did it or whatever is fine. It doesn't mean there's not a serious exploit, and so often that is where people end up with these AMD exploits, they like AMD so much that they argue against the existence or significance of the exploit, attack the researchers or whine about research grants, etc.
"Does this really deserve this CVE score" is a constant refrain in AMD vuln threads and it just gets so old. As tptacek noted... intel ME vulns are frontpage news and have people asking where they can buy a processor without ME in it. Literally nobody cares that AMD has had these vulnerabilities left open and unmitigated for years and years even though they're actually worse (as judged by the researcher who found both these issues and meltdown).
People would have flipped the fuck out if Intel left meltdown unpatched and released misleading statements implying that it wasn't an issue etc. It is wild just how much AMD is playing on story-mode difficulty with the average enthusiast, and honestly most people don't even realize they're doing it. And that drives me nuts - just decide if security issues are a problem or not, and if the answer is "not" then let's just turn all the mitigations off and see how long they remain un-exploited. If we want to have the security version of the drug-assisted olympics then fine, there is value in having dragsters that just do the thing as quickly as possible, right? But the double-standard people apply to anything AMD is crazy. Talk about your "tyranny of low expectations".
the radio literally has a squelch knob on it, and turning the knob is required if you want to not hear static constantly or if you want to hear your traffic when they call you, so if you somehow manage to own a radio without knowing what squelch is it’s kinda on you.
let’s give users at least a little bit of agency here
it's funny that they have to debunk the "root is root, why would AMD patch this" that goes around every time there's a serious issue that allows guest-root escape from virtualized containers.
the same thing happened with the ryzenfall/masterkey exploit, where people were just in utter denial there was an actual exploit there, because root is root! People literally spent more time talking about who released it and their background image than the actual exploit. AMD obvious cannot have exploits, that's only an intel thing. /s
OK? Well, the iphone mini series did not sell fine, objectively so. It was a bad seller even with the bump from the novelty of apple releasing a mini, and it declined even further the next generation. Probably at minimum it's not worth doing more than one every couple generations.
idk why you guys are continuing to rage at the messenger here, I'm not the one who canceled it and the reason it was canceled is widely acknowledged. Your refusal to accept reality does not constitute a problem on my part.
"squelch codes" probably conveys the meaning more correctly.
people understand the idiom that just because your radio has squelch set (too high, perhaps) that it doesn't mean someone else can't hear it.
otherwise, CTCSS codes works fine, that's the technical description of what it is. and actually they call them "squelch tones" there. it's only motorola that branded them as "private lines", that's their trademark for an adequately-described term. Much like Tesla "Full Self Driving"/"Autopilot", it's kind of a misnomer and definitely breeds (deserved) confusion.
> To bring this point home, for years there was hubub in the industry that Nintendo would bring out some kind of Switch Pro with 4k output and faster guts, rumors swirled around and around until Nintendo finally brought out? The Switch Light.
Switch Lite is not the console people were referring to in that context. And oddly enough, Nintendo themselves have pseudo-confirmed the launch will occur in Q1 next year via various official statements:
(and then they later confirmed that they won't discuss it this year... so it's going to be Q1 next year.)
And again, to underline this point: the hardware itself has literally been ready to go since 2022 or before (prominently, there was an enormous amount of stuff in the hacked nvidia data dump and it's all essentially confirmed accurate at this point) and the delay has frankly baffled industry-watchers. It’s not even just Nintendo being nintendo and favoring older cheaper hardware, they seem to have internally had some pullback or change of heart back a year or two ago such that they decided not to release it.
And obviously at some point the hardware will be relatively weaker than the original switch was at its launch, so at this point they may have to update the hardware again.
But yeah switch is a bad example of “see, rumors are sometimes wrong!” when Nintendo literally had a console generation ready to go, as confirmed by multiple sources, and then just inexplicably decided to pull the plug or delay it for 2 years for inscrutable Nintendo reasons. That’s the Nintendo being Nintendo part - and we have their confirmed-in-financials timeline for release now.
I don't disagree, but the market placement of the iphone has nothing to do with the continued poor sales of the mini series every time it's been tried.
And the mini ran for multiple generations and none of them sold well.
Much like the 3.5mm jack, people just cannot admit that it's not a very popular idea. Extremely popular among a very small niche, incredibly unpopular if not actively dispreferred outside of it.
Microsoft was upfront that they didn’t think a mid-gen price cut was in the cards, so here’s the series s, it’s what we can do and we’ll do it right now, etc.
They were right and not only have prices not really come down, but in some ways they’ve increased.
The unfortunate consequences of a post-Moores law reality. Like yeah nothing is getting 2x better for the same price even every 3-4 years anymore. Your expectations based on past history will no longer hold true, and this has been clear for a number of years now.
You can’t make a gamer understand something when his wallet depends on him not understanding it. People have been in active denial for years, in ways that have crossed into objective denial of reality. The "AMD is just choosing to join NVIDIA and gouge!" stuff has been joined by "and sony is in on it too!" etc. Yes, corporations suck but the margins are not actually very fat here, this is just what it costs now.
iphone 8 plus, bought refurb in early 2019. replaced the battery once (and got a replacement since the battery wouldn't pair). it's getting to be time.
usb-c is a big feature increment for me, and I need to finish the leap away from google voice, since I absolutely know they are not going to bother implementing RCS and will just shutter the service instead. LiDAR also seems extremely useful/cool. On the other hand, I was kinda hoping for thunderbolt support on the pro models eventually. Not sure if I will buy a refurb 15 Pro or a new 16 Pro Max or wait for the next cycle.
that's how you avoid e-waste for real and not as a fashion statement. simply consume less - and that includes not consuming a $300 android phone every 18 months, not just apple - and have it repaired when it needs it. with OEM parts that will last the long-haul and not something off amazon that will need to be changed again in 6 months.
swapping on an m4 with a midrange pcie 4.0 SSD is quite different from swapping on a celeron with a low-end SATA SSD or spinning rust, plus linux/unix/macos is generally much better with swapping sensibly than windows.
believe it or not, an 8GB macos device is generally quite usable even if it's swapping, as long as it's apple silicon family. yes, it's not going to save if you if your working set is more than 8GB and you need everything in the set, but chrome/firefox do not actually need the 32gb you are probably giving them.
> When a battery goes bad, I toss it in the recycle bucket, and buy a new one. I currently have 10 of them and they're on rotation.
not to pick on you but it’s baffling the way some people clothe themselves in right to repair and then bust out some shit like this. this is absolutely insane from an e-waste and frankly just regular-waste perspective.
I’m sure it’s very convenient and granted everyone needs batteries, but still, “they fail and I throw them away and buy new ones, I currently have 10” is objectively insane and I have to think that buying shitty non-oem batteries is a major part of why you churn batteries so much.
“I said it sounds like he’s just feeding e-waste to landfills and hackernews started crying”
maybe think about buying some 18650 batteries and a power bank or something, idk. You can get cold-weather 18650 cells which improve outdoors performance a lot, and good quality 18650s last a half decade or more.
Really disappointing how right to repair just turned out to be a fashion accessory for most people, and the actual boots-on-the-ground aspects like oem parts availability and not using disposable junk batteries didn’t sink in, people are literally happy to have a backpack full of 10 Amazon batteries they change out every 6 months if it means they get to bash apple and feel smug about it. The discussion around usb-c vs lightning went much the same way - people were exuberant at the prospect of filling the landfills full of discarded cables (on a port that's been around for a decade), as long as they were the right cables. People bashed the self-service/OEM parts availability for being some kind of plot or conspiracy. People bashed it because the OEM factory repair tools apple will rent or sell you are too big and clunky.
There really, really ought to be a real attempt to account and attribute some of these total lifecycles, independently of some of the fandom and some of the actors involved with R2R with their own personal foibles and financial interests. Specifically thinking of component-level repair as not being in the interest of certain major backers of R2R, for example. There should be an accounting of what the actual cost is for that decision, vs the aspects of R2R increasing the churn on these essentially-disposable amazon batteries and other junk and so on. Those things need to be attributed in the total lifecycle cost too, if bunches of people keep doing the same thing you are that's a real social problem. Ten batteries, and I just swap them out when they fail and buy new ones to throw away. One of the most polluting and dangerous and toxic parts of the phone. Good lord.
I hope you are at least sending them for proper disposal, but even that is not currently even close to full recycling efficiency iirc.
I’ve never seen a literal “this product sucks because I refuse to learn about it” given as an explicit argument before, usually it’s just implicit, thank you for this
A single 3090 won’t even fit the model. OP is talking about running a 405B model, it needs close to 200gb of memory just to open it which is why we’re talking about mac studio and it’s 192gb unified memory.
This is exactly like when the AMD fanboys got a burr up their ass about the “$50k Mac Pro” with 2tb of memory… when you could the same thing with a threadripper with 256gb of memory for $5k, and it’s just as fast in Cinebench!