Comments URL: https://news.ycombinator.com/item?id=49938845

Points: 6

# Comments: 0

It's baffling you people are in control of such a strong product when you are obsessed with this intellectual pornography; wow - look at how smart it made my thoughts look (n.b. look, not read). Don't look too close. And certainly don't ask me what it means.

We just want to ban the competition guys! Very different.

--

The ridiculous anthropic/openai strategy of selling shovels at a loss in a gold rush isn't going to play out, and the hilarious thing is that these AI companies are going to create tons of value and _capture none of it_.

Their only path to profitability is if they get to capture it and they're going to do everything to do so. Put it this way: *all the blog posts that Anthropic and OpenAI are putting out are DESIGNED to scare you so that you let them capture the market*.

...and "distillation attacks" (hilarious framing of "saving the output of our models")... Whatever.

Where is the support thread?

I have ticket T-D95851 at the moment, if you could get someone to resolve it. I do not want to use cloud agents.

Thanks

zk

I've been on `Privacy Mode (Legacy)` for a long time, which is the "Do not store my code" setting. A year or so ago they marked this as "Legacy" and hid it under a "Extra options" menu. They added a new Privacy Mode which is significantly more wishy-washy about what it might store - it includes a clause of "Code may be stored for Background Agents or Other Features", so I've never touched it or wanted to enable it.

pic: https://us1.discourse-cdn.com/cursor1/optimized/3X/0/9/09412f800cb07a713d13c034f40eaf28e165e8f4_2_1032x1000.jpeg

Upon installing and logging in to the iOS app, my account was changed to the softer Privacy Mode and the previous setting I was on has disappeared from all menus. I contacted support and they've said:

> Really sorry about this. When you set up the mobile app, the prompt to turn on Cloud Agents switched you from Privacy Mode (Legacy) to our current Privacy Mode,

> without making clear what that meant or that it's hard to undo. That wasn't right, and we're working on making that prompt clearer.

>

> To be straight with you: I'm not able to switch your account back to Privacy Mode (Legacy). The option to move back isn't available in the app today.

So just a PSA I guess; do not install or set up the app if you want to keep your privacy settings.

I honestly don't understand how it's legal to make logging into the iOS app change your privacy settings at all. Making the option then disappear from all menus so you can't get it back is doubly ridiculous.

Comments URL: https://news.ycombinator.com/item?id=48737226

Points: 249

# Comments: 34

Also, $500/mo for 64GiB of RAM and 16 mystery meat CPUs. LOL! You guys are all being ripped off and you don't even know it.

"Provably Correct Axiom" is nonsense. An axiom is unprovable.

Just "provably correct" would've been fine. This chess stuff is hilariously pretentious.

The article doesn't dig too deep into this sadly, rather just accepts that it's slow and uses a different tool.

But seriously, this is responding to a request with the content of a file. How can it be 100,000x slower than the naive solution. What can it possibly be doing, and why is it maxxing out the CPU?

If no-one else looks into this, I might get around to it.

If you wrote your app in NextJS 2 years ago, you would already have to rewrite chunks of it to get it to compile today. These tools are NOT solidified, they are releasing breaking changes at least once a year.

In the netflix blog post they're complaining about increasing latency over time because they have a function that *reloads all express routes in-memory* that didn't properly remove all the previous routes, so the routes array got bigger and bigger. That's not a fundamental problem with express[1], that's an obscure (ab)use case implemented wrong. Hardly a damning indictment of express.

> This turned out be caused by a periodic (10/hour) function in our code. The main purpose of this was to refresh our route handlers from an external source. This was implemented by deleting old handlers and adding new ones to the array. Unfortunately, it was also inadvertently adding a static route handler with the same path each time it ran.

[1]: Admittedly an array is not the "best" data structure for routing, but that absolutely wasn't the performance issue they were having. Below a couple thousand routes it barely matters.

The software in question is the winning entry in a hackathon from 2020: https://github.com/DevrathIyer/ballotproof

Inside that repo they have a script called `generate.py` which generates ballot test data.

Look at it for yourself: https://github.com/DevrathIyer/ballotproof/blob/master/gener...

It's a ~100 line python script that generates some test data. The last commit on is as naive as "hope this works".

What a horrendously misleading title. It's just some kids making something with OpenCV to scan images. Ridiculous.

Comments URL: https://news.ycombinator.com/item?id=42232040

Points: 815

# Comments: 211

Make on its own is great but most of the time I've worked with C projects it's been cmake/autotools + global pkg installs, which you Do have to frequently look up.