https://support.claude.com/en/articles/14604842-real-time-cy...
If you work in security (which I assume the OP does), they should be able to get in easily. I think most people just don't know this is a thing.
2,309 karma · joined June 12, 2023
https://support.claude.com/en/articles/14604842-real-time-cy...
If you work in security (which I assume the OP does), they should be able to get in easily. I think most people just don't know this is a thing.
Despite all the evidence that we are in fact just biological machines, people still persist the theory of our own uniqueness from other creatures, which we ourselves often treat as biological machines.
This adaptation is wonderful to me specifically because I think it shows that our shifted goalposts of, "well we're not just animals, we can think and reason" was never more than a convenient excuse for many people (and as evidence of animal intelligence continues to mount, denialism still attempts to preserve this distinction by claiming human thought and reason is different than 'animal' thought and reason, sans evidence).
It's not about who created it or why, it's about how people still haven't actually internalized the point, because the subject changing from human to LLM doesn't intrinsically change the message about consciousness, but the reaction being a 180 shows how hostile people are to that message, still.
Do you eat at the cheapest restaurant every day? Do you think that every Michelin Star restaurant immediately fails and shutters? Do you think everyone buys the $80 prepaid flip phones, and no one actually buys the $700+ iPhones?
Most people don't gravitate towards the cheapest option (in fact, many people find the cheapest option automatically suspect and won't buy it), but rather want a balance of affordable and desirable. No one living in NYC is doing it because they're gravitating towards the cheapest option in the first place, they're there because it has a high level of desirability comparative to its cost, even as expensive as it is.
We can't solve the intentional sabotage of our educational system by keeping kids in it for longer via remedial classes, which are supposed to be focused on kids who have personal barriers to learning, not systemically-imposed ones.
1) https://fiscalpolicy.org/wp-content/uploads/2025/10/20251009...
> As we get more data on the post-pandemic period, we increase our knowledge of the major upheavals that took place in New York between 2020 and 2022. Despite the state suffering a deep recession and massive out-migration during the pandemic, data show that New York’s tax base remains resilient. When taxes on millionaire earners were raised in 2021, tax revenue to the state increased by an estimated $3.6 billion and there was no detectable increase in high earner out-migration.
Actual studies [1] show that the rich are not moving in response to wealth taxes, and in fact when they do move, it's almost never due to taxes.
> As we get more data on the post-pandemic period, we increase our knowledge of the major upheavals that took place in New York between 2020 and 2022. Despite the state suffering a deep recession and massive out-migration during the pandemic, data show that New York’s tax base remains resilient. When taxes on millionaire earners were raised in 2021, tax revenue to the state increased by an estimated $3.6 billion and there was no detectable increase in high earner out-migration.
1: https://fiscalpolicy.org/wp-content/uploads/2025/10/20251009...
There are so many games (like Hitman: WoA, which I love btw) that "require" online access in order to provide the same functions that previous games by the same devs provided fully offline (e.g. keeping track of your weapon unlocks).
This is just clawing back some of the consumer protections that the "we're not selling you a product, we're selling you a temporary and arbitrary license that we reserve all rights over" BS snuck around.
Both the latter 2 are big choices for a university administration to make, so it's much easier to ask the professors to make up the difference. That's why it's the faculty and not the admin demanding this; they know what the admins are asking them to do is impossible.
Are LLMs really going to fall off in significance, or will it just be the nth newest incarnation of LLMs?
The function of what an LLM does (generative language) is what people seem to take issue with, but the function is here to stay, even if the next iteration has a different name or method.
It's always surprising to me when people mention these google services I've never heard of. What do you mean a Google IDE? Haven't you heard of Vim, bro?
Mostly-jokes aside; don't trust Google! Google is asshole.
Castles still exist as well, you just aren't invited to them (which was true for us peasants back in the day, too). Trump is still trying to get one built under the ruins of the East Wing, in fact.
But I hear everyday, non-IT-sector people talking constantly about how they're using it, and that means there's a demand for it, and someone is going to supply it. I think a lot of anti-AI people think it's still equivalent to the PDA, and don't realize it's a smartphone already.
The other side is that "AI" is of course very very broad and isn't new, and e.g. medical vision models are making advancements that are having huge impacts on patient care already, especially around early cancer detection. Those aren't going away (and shouldn't), so there's still going to be a demand for the underlying technology and infrastructure to support it, even if LLMs stop being spammed everywhere.
The other thing which people seem not to understand is that you don't need a whole datacenter to RUN individual LLMs, you need it to train them, or to run them at scale for thousands of customers. A lot of the upper-mid-tier models that exist now can be run on a single (beefy) 4U server in your closet if you've got the GPUs to put in it. And people are running e.g. Deepseek V4 Pro FP4 locally. If you've got an actual server room, like at a university, you can run the full, un-quantized versions with ~2-4 servers.
Technology that is living in peoples' homes and businesses already is not going to just disappear. It's a lot less centralized than the market prevalence of OpenAI and Anthropic would lead you to believe.
To save you a click: It's harder to monetize desktop apps than webapps.
Lol. LMAO, even.
We still haven't found and agreed upon the 'best' way for AI to work in a given environment, and the experts in this area aren't working at Apple. Once there is a clear path forwards to use AI best, it makes sense for Apple to jump in.
Edit: literally just saw this article afterwards:
https://www.lbc.co.uk/article/dubai-police-spied-private-wha...
UAE government getting access to private WhatsApp messages (presumably in conjunction with Meta).
I wonder if my formal university python training predated this change (~2010), or if the professors were themselves unaware of this.
Side note, there actually isn't one shinkansen from Kagoshima to Hakodate, that route would take you on 5 different shinkansen lines: Kyushu, Sanyo, Tokaido, Tohoku, and Hokkaido. But I get your point.
If you're thinking there is some magical line where LOC < n gets properly reviewed, but LOC > n doesn't, I assure you that's not the case.
And no one is turning off their approval gates in their build pipeline just to accommodate AI code.
What this fails to take into account is that unless the codebase is changed, there are a finite amount of actual (and even fewer actionable) bugs in a piece of code, but an infinite amount of potential attacker spend; nothing stops you running mythos against it, whether it finds anything or not, and because each run is atomic by nature, you just have to play the numbers out and see when the average vuln discovery rate is dropping. You could spend a billion dollars and not find anything, without the defender spending a cent.
Generally speaking, the advantage goes to whoever can spend more time or money on security research (this has always been true, which is why the NSA was able to find Windows exploits that M$ did not). But eventually the fount of bugs in a piece of software will dry up, and attackers have no way of knowing if that's the case or not before dumping money at it (especially since attackers do not generally coordinate unless they're just branches of the same 'entity', e.g. nation-state).
Fully agree about phone calls though.
I have bad news for you about the executives and salespeople who manage and sell fully-human-coded enterprise software (and about the actual quality of much of that software)...
I think people who aren't working in IT get very hung up on the bugs (which are very real), but don't understand that 99% of companies are not and never have met their patching and bugfix SLAs, are not operating according to their security policies, are not disclosing the vulns they do know, etc etc.
All the testing that does need to happen to AI code, also needs to happen to human code. The companies that yolo AI code out there, would be doing the same with human code. They don't suddenly stop (or start) applying proper code review and quality gating controls based on who coded something.
> The only way I felt comfortable using Claude Code was holding its hand through every step, doing test driven changes and manually reviewing the code afterwards.
This is also how we code 'real' software.
> I can't help but think that massive code bases that have moved to vibe coding are going to spend inordinate amounts of time testing and auditing code
This is the correct expectation, not a mistake. The code should be being reviewed and audited. It's not a failure if you're getting the same final quality through a different time allocation during the process, simply a different process.
The danger is Capitalism incentivizing not doing the proper reviews, but once again, this is not remotely unique to AI code; this is what 99% of companies are already doing.
Because they can afford to buy the 'right' to do what they want, and you can't, and what they want is cheaper labor who they have more control over, and H1B workers will never rock the boat because the visa is a sword hanging over their heads.
Downvote all you want, it's the truth.
When bubbles burst, investors change tack, and when investors pull back, companies turtle and do layoffs.
After Y2K, investment moved on to real estate. In 2008, that bubble burst. It moved on to social media next.
I would argue that bubble burst somewhat silently during COVID with the quiet deaths of Xitter and Facebook (from a standpoint of cultural relevance), and investment transitioned towards and into its current AI bubble.
Investors are always going to move on once the lustre of a field has waned, and I'd hazard that we'll see investment move somewhere other than software tech next (if I had to prognosticate, I'd say it's moving into robotics/ drones).
In all seriousness though, it scares me that a lot of security-focused people seemingly haven't learned how LLMs work best for this stuff already.
You should always be breaking your code down into testable chunks, with sets of directions about how to chunk them and what to do with those chunks. Anyone just vaguely gesturing at their entire repo going, "find the security vulns" is not a serious dev/tester; we wouldn't accept that approach in manual secure coding processes/ SSDLCs.
They actually will need oil changes starting anywhere from the 50k to 100k mile mark.
Here's the maintenance guide with pictures walking through changing the oil and filter for the Rear Drive Unit (RDU) in a Tesla Model S:
https://service.tesla.com/docs/ModelS/ServiceManual/Palladiu...
Legacy app compat is actually an argument for moving to Linux.
I'd really recommend separating prototyping work like that out into a pre-design phase. Do the prototypes and figure out the direction for the actual project, but then come back in with a clean repo and design docs built off the prototypes, for claude to work from. I started out using claude to refactor my old projects (or even my codex ones) before I realized it worked better starting fresh.
I think sometimes it silently decides that certain pieces of code or design are absolute constraints, and won't actually remove or change them unless you explicitly tell it to. Usually I run into this towards the end of implementation, when I'll see something I don't expect to and have to tell it to rip it out.
One example recently was an entire messaging queue (nats jetstream) docker image definition that was sitting in the deploy files unused, but claude didn't ever mention or care about it as it worked on those files; it just silently left it sitting there.
Another example was an auth-bypass setting I built in for local testing during prototyping, being not just left alone by Claude but actually propagated into other areas of the application (e.g. API) without asking.