gorgonzolachz

I assume the chief reasoning behind this decision twofold. First, it's a crapshoot to get alternative stores working on my steam deck (I wouldn't expect my less technical gamer friends to feel confident installing a game from Epic/EA/Ubisoft). It's also a financial decision, as Valve presumably isn't charging the OEMs a licensing fee.

In a market that's getting more crowded by the day, where so many of their competitors are using the same SoC and come in at roughly the same price point, it's a rational decision to control costs as much as possible. Not to mention, they also need to compete against the Deck itself, which Valve is subsidizing to hit its pricepoint. The alternative would be to innovate and differentiate your product offering from your competitors (like the original Legion Go, which had detachable controllers and a fancy pseudo-mouse). The fact that this machine didn't carry those features forward is a strong signal that the bottom of the market is where the early wins will be.

Keep in mind also that Microsoft is planning their own handheld xbox experience. Speculation: MS' effort will look a lot like Valve's, with Xbox games coming day-and-date to OEM-built handhelds, as well as a first party reference implementation that's intended as a benchmark for devs. I imagine that most OEMs are using the cheaper steamOS pricing as a hedge against future gouging from MS; if there's an "Xbox certification process" that proves to be too cumbersome, a vendor that's already shipping cheap(er) devices en masse with SteamOS has the option of simply dropping windows support altogether.

I'm cautiously excited/optimistic for this.

That said, I wonder if this feature will end up seeing all that much usage? Once your inputs are sanitized/bounded in a Golang application, it's pretty hard to get the language to do things it wasn't meant to do - and if the fuzzing system is built like the unit testing system, the number of useful fuzzing cases you can run won't be that large.

I've always thought that fuzzing primarily benefits E2E/integration testing, and that with modern languages' type systems and lack of pointer arithmetic the usage of fuzz testing is useful for niche cases (embedded programming and cryptography come to mind). The examples in the article (integer overflows, truncated input, invalid unicode) may be issues, but they won't break the integrity of the program or cause catastrophic failure (assuming there are no panic() calls in the code) due to Go's type system.

Sorry, I made a couple of points in that post, and you're conflating two of them. Ben Shapiro isn't radicalizing anyone, but he's definitely a hack who regularly says controversial things to get into the public eye. In a principled political party he would live on the fringes, like Hasan Piker does for liberals (although that might be a reach, I'm not super familiar with either figure).

I think this hits at the heart of the issue though - you don't get to, as a public figure, decide whether or not you are "the voice of a movement". In mass media today, influencers and other people of note who don't have advanced degrees should be doing their research - from credible sources - so they're not spouting inaccuracies and falsehoods to their followers.

Joe Rogan doesn't need to do these things if he's just "hanging out with his buddies smoke'n" but he also doesn't have an obligation to have provocateurs and hacks like robert malone or ben shapiro on his show. He does it because he knows his fanbase will listen to it, ingest the information, and then speak it as fact to their friends and family - and THAT is where the danger comes in. Furthermore, he also knows that parts of his fanbase will go wild to see their fringe views espoused by a guest on their favorite podcast, without Joe challenging them to back their claims up with facts. I'm sure he also knows that his listeners skew young and male, and impressionable young men have been radicalized to a dangerous degree on the internet. Having the same views on his podcast as conspiracy theory sites, for example, will undoubtedly make it easier for the bad actors running these sites to radicalize JRE listeners (who will then, of course, become a part of the fanbase that loves when their theories are given time on his show in some perverse feedback loop).

He has also inked a deal with the largest music streaming service in the world for more money than any of us will see in our entire lives - at that point I don't think you can even say he's just "hanging out" any more. It's facetious at best, and wilfully negligent at worst, to assume that no one thinks of him as an authority figure, because even if he's playing the everyman character his guests profess to be authority figures in their fields. If he doesn't seriously challenge their false claims or ask for evidence from credible sources, he's doing his listeners a disservice.

I thought based on how pilots were paid, longer routes were more desirable? And shorter routes would be in lower demand, since airlines don't typically pay for time spent on the ground?

2 and 3 are great points, but honestly - and especially if you're working in multiple repos, or multiple subdirectories in a monorepo - VS code's folder search is better than grep. It'll find you the exact place in the file, and a click will take you there, nice and easy. I've more or less forgotten the quirks/flags of grep, because I haven't needed to use it in a while.

And this is where the NIMBYs come in; people who bought in years or even decades ago, who want to see prices rise to astronomical levels so they can retire off of their home's equity. Any proposal to do this will absolutely be shot down, until the voting public outnumbers the homeowners - which may never happen, given current voting trends.

To What, though?

This is the problem I'm currently struggling with.

I could go to Android, which is relatively good but still run by Google (one of the most data-hungry corporations around). I kind of want the Z Flip 3, but not if it's running the kind of operating system that thinks of me as a data source and not a customer.

I could go to linux phones, execpt no, they have absolutely no concept of competence in any form, and frequently die with less than two hours of battery life under their belts.

I might decide to root/jailbreak, but that's the kind of resistance that invites malicious intruders to take advantage of the broken security models of our duopolist platform economics to sell my data to the highest bidder.

This isn't a rhetorical position: what do I do in this scenario? I want to leave Apple, but I can't find a good alternative and iMessage might be the dollar-store adhesive keeping me to the lesser of two evils.

I'm on the other side of this; I don't use my phone for anything more than messaging, light browsing/videos, and social feeds, so what I really want is more battery life.

Last I checked, both purism and pine64 are struggling with this.

Facetious as this is, I can't imagine this is anything other than Apple's endgame here.

The best of both worlds: keep advertising their privacy chops to the masses, while also allowing any and every government agency a programmatic way to hash-verify the data passing through their systems in real-time.

Yeah, I've worked with HSMs in the past and to say that it's a challenge to get key material out of them is an understatement. That said, a lot of this depends on the architecture surrounding the HSM - if the key material leaves the HSM at any point, you've basically increased your attack surface from an incredibly secure box to whatever your surrounding interfaces are. At Apple's scale, I have to imagine it's more economical to have some kind of envelope encryption - maybe this is the right attack vector for a malicious actor to hit?

I would disagree here. AWS has to be strong out of the gate to push opensearch as more than just "elasticsearch, but on AWS". Elastic has proven its worth, or this fight wouldn't even be happening. AWS is simultaneously David and Goliath in this fight - they obviously won't have ES' newest, coolest features immediately, but companies will sign up with them instead of Elastic if it means they get good-enough software at a reasonable pace.

Elastic's playbook is almost diametrically opposed to this: they need to prove that they're worth paying a premium for, over AWS' offering. The repo activity clearly shows that they're working on more stuff, building faster, whatever signals you want to glean from that. Change is happening, and if it's good change I can see the gambit AWS is pushing turn into a losing proposition.

The endgame for Elastic is a partnership on AWS, on "equal" terms; license fees, a cut of the profits, the whole shebang. The endgame for AWS is an end to Elastic as a company, but not heavily increased profits one way or another - AWS still gets its cut if Elastic succeeds.

The incentive models aren't equal here, and that's what kills AWS' agenda. I'm not affiliated with either company, so I don't have any inside info, but I have to imagine that Elastic will succeed here in carving out a niche for themselves - unless there's been a silent exodus from the company I understand that these are smart folks building software under, shall we say, extrenuous motivational circumstances. A little stress is good for productivity :)

This is the right answer - HN is absolutely not representative of web users at large. If we were, I'm sure there would be much stricter anti-adblock/ad protection systems on large sites.

KYC only helps to an extent, right? My understanding of crypto is minimal, but if you run your own miner I assume you don't need to verify anything to anyone. You should be able to send out transactions to the network and have them be accepted anonymously, which is what most people who would be interested in money laundering would do.