今日已更新 184 条资讯 | 累计 37433 条内容
关于我们

标签:#t

找到 17788 篇相关文章

开发者

Apple announces iOS 27

Apple announced its next major iOS update, iOS 27, at WWDC 2026 on Monday. Apple is highlighting performance and design improvements, trust and safety upgrades like a Screen Time redesign, and major upgrades to Siri and Apple Intelligence. The update will be supported all the way back to the iPhone 11. A big change is […]

2026-06-09 原文 →
AI 资讯

Critical Zcash Vulnerability Found and Fixed

If you’re a user—owner?—of this cryptocurrency, this is important: On May 29, the security researcher Taylor Hornby found a critical vulnerability in Zcash Orchard privacy pool using Claude Opus 4.8. The Zcash team hired Hornby specifically to look for this kind of issue. He found one fast enough to be embarrassing. The Orchard pool is the newest and most advanced shielded transaction system in the cryptocurrency Zcash. Introduced in 2022, it allows users to send and receive ZEC while keeping transaction details private. It uses zero-knowledge proofs to validate transactions without revealing amounts or participants. The bug: a specific check that was supposed to validate transaction inputs wasn’t actually enforcing the rules it appeared to enforce. An attacker could have exploited the flaw to feed false inputs into that check and generate ZEC from nothing, with the zero-knowledge proof system blessing the fraudulent transaction as valid...

2026-06-09 原文 →
AI 资讯

AWS Releases Next Generation of Amazon OpenSearch Serverless

Amazon Web Services has recently announced the general availability of the next generation of Amazon OpenSearch Serverless, with a redesigned architecture that enables 20 times faster resource provisioning than the previous serverless architecture, true scale-to-zero capability, and up to 60% lower cost than a provisioned cluster for peak loads. By Gianmarco Nalin

2026-06-09 原文 →
AI 资讯

I wanted an AI assistant. Most of them turned me into the assistant.

TL;DR: Future archaeologists will discover this post and conclude I traded a referral link for free AI credits. They will be correct. 500 free credits: https://manus.im/invitation/L722LISUH3EMDS?utm\_source=invitation&utm\_medium=social&utm\_campaign=system\_share Anyway... You know how in every sci-fi movie they promise us AI assistants? Yeah. Somehow we ended up with AI that needs constant supervision. Me: "Research this topic." AI: "Certainly. Before I begin, please provide your goals, audience, format, timeline, preferred writing style, risk tolerance, blood type, and your mother's maiden name." Thirty minutes later I'm managing the AI instead of the AI helping me. I've been messing around with Manus and the thing I like is that it behaves more like an actual assistant. I tell it what I need, and it goes off and fills in a lot of the blanks itself. I don't use it as my main model for everything. I use it like a second opinion. Research. Project planning. Finding blind spots. Comparing options. Figuring out what I'm forgetting. Basically all the stuff that happens before the actual work starts. For pure coding, there are better tools. For "here's the thing I'm trying to do, help me think through it from start to finish," it's been surprisingly useful. Full disclosure: if you use the link, I get some credits too. You get free credits. I get free credits. The robots get stronger. Honestly that's the healthiest relationship I've had with technology in years. submitted by /u/Mstep85 [link] [留言]

2026-06-09 原文 →
AI 资讯

ai agents make the web feel weird now

maybe i am overthinking this but the more i look at AI agents using the web, the more the current web starts to feel kind of awkward. like websites are still built assuming a human is sitting there, reading the page, ignoring the cookie popup, guessing which button matters, understanding which part is marketing and which part is actually useful. but an agent does not really do that naturally. it has to parse the page, figure out what is clickable, understand the form state, avoid random modals, compare options, maybe call tools, maybe retry when something fails, then somehow verify it actually did the right thing. that sounds less like “browsing” and more like forcing software to cosplay as a human user. which is probably fine for demos but idk how well that scales. this is why all these things that seem separate to me are starting to feel connected. MCP, A2A, WebMCP, AI search, browser agents, bot traffic, agent security, all of it. not saying they are the same thing obviously. but they all point to the same pressure: software is becoming a real user of the web, not just humans. and if that keeps happening then maybe websites need something beyond normal UI. not just better HTML or better accessibility, but some kind of agent-readable/action-readable layer. basically not “AI kills websites” or anything dramatic like that. more like websites keep existing for humans, but also need to expose themselves properly to machines. kind of like SEO but instead of optimizing for search crawlers reading your content, you optimize for agents actually doing stuff. not sure if this is a real architecture shift or just people putting new names on APIs again. wrote a longer version in the attached medium post if anyone wants to read it. submitted by /u/Old_Cap4710 [link] [留言]

2026-06-09 原文 →
AI 资讯

I bundled a fully local LLM inside my Unity game. No internet, no cloud, no API key. The conversation is the gameplay.

My game 'Simulation Simulator' is a campfire conversation game about DMT, simulation theory, and a friend with a computer monitor for a head. The game is bundled with a local LLM and every conversation is unique. 5 endings you can reach totally based on how you interact naturally with the AI. One is a romance ending! Everything in the clip is totally organic and unscripted. Trying to use AI for good. Honestly haven't seen the use of LLM tech inside games to this extent yet. I'm sure people much smarter than me must be trying though. For NPCs & world building, this seems like a logical next step. I even wanted to do text to speech audio and automatic translation. The only thing really preventing it right now is processing time on local machines. Those extra layers would add like 10-20 seconds of calls per exchange so it just breaks the game. If processing gets faster/better, I can imagine whole towns of NPCs with memories, that have no scripted dialogue at all and change over time. In my game here, you argue with an LLM and can attempt to prove that reality itself is a simulation. It's really a philosophical experiment more than a game. It can get trippy trying to prove you do or don't exist. Anyway, demo for Simulation Simulator is out on steam if you want to try for yourself. Let's talk using AI for good in games! submitted by /u/MorphLand [link] [留言]

2026-06-09 原文 →
AI 资讯

IM SCARED this is the story mode off the fucking chains right?

Prerequisites (what you need before starting) Account and tokens : user:MODDER credentials and access to the proposal inbox. Local tools installed : qemu-system-x86_64 , libfuzzer or afl++ , boofuzz (optional), openssl , jq , base64 . Artifact store access : S3 or equivalent with write permissions. HSM access for owner : owner HSM is required only for final autonomy=1 apply; Modder does not sign. Test harness : test-harness CLI that runs vectors (provided by platform). If not present, use the included run-vectors.sh wrappers. Network : ability to reach staging Overcrest endpoint and Zclarity3D collector. Basic skills : copy/paste, editing JSON, running shell commands. submitted by /u/GabenHood [link] [留言]

2026-06-09 原文 →
产品设计

The Verge’s Father’s Day 2026 gift guide

With Father's Day on the horizon, happening June 21st, it's time to start thinking about what kind of gifts you want to buy for the fathers you care about. You know your dad best - he may be a man of simple pleasures who wants nothing more than to share a meal or drinks with […]

2026-06-09 原文 →
开发者

WWDC 2026: All the news from Apple’s developers conference

Apple’s annual WWDC event is kicking off on June 8th with a keynote presentation starting at 1PM ET / 10AM PT, where Apple will announce major updates to iOS, macOS, and its other operating systems. Among those updates could be Apple’s delayed Siri overhaul, which has faced setbacks since it was initially announced at WWDC […]

2026-06-09 原文 →
AI 资讯

Safe Operating Throughput (SOT) as a First-Class SRE Metric: Derivation and Operationalization

In the summer of 2016, Pokémon GO launched to a user base roughly fifty times larger than its capacity planning had anticipated. The engineering team had done load testing. They had throughput thresholds. They had autoscaling configured. Within hours of launch, the service was degraded globally — not because the infrastructure could not scale, but because it scaled too slowly against an arrival rate that exceeded every modelled scenario, and because the metric that was driving scaling decisions (CPU utilisation) lagged behind the actual saturation signal by several minutes. By the time CPU registered critical, the request queue had already grown to the point where p99 latency had crossed into the range where users were abandoning sessions faster than new sessions were being created. The engineering post-mortem identified the same root cause that appears in the post-mortems of most capacity-related incidents: the organisation's operational metrics were measuring how hard the infrastructure was working, not how much work the service could safely accept. CPU percentage is a resource utilisation metric. Memory percentage is a resource utilisation metric. IOPS is a resource utilisation metric. None of them is a service throughput metric. None of them tells you, with precision, at what arrival rate your SLO begins to degrade. Safe Operating Throughput is that metric. It is not a new concept in queueing theory or systems engineering — the idea of a safe operating ceiling predates modern distributed systems. What is new is its treatment as a first-class SRE metric: formally derived from load test data and SLO targets, continuously monitored for drift, and operationally enforced as a constraint in autoscaling configuration, capacity planning decisions, and deployment pipeline gates. Why Existing Capacity Metrics Are Insufficient The canonical capacity management approach in most organisations works like this: observe CPU or memory utilisation, set an autoscaling threshold (t

2026-06-09 原文 →