aLake™ retweeted
I have a particularly nasty case of cancer. When I was hospitalized again at my lowest point last year, I told Jensen. He immediately reached out to contacts at Stanford, who were able to cut through red tape, and get me into a clinical trial for which I've turned out to be a perfect fit. I think everyone can have their own views about recent events. But any claims that Jensen did not really care about his staff is simply inaccurate. I, personally, owe him more than I can express.
I think the best tribute we can pay to Jensen's legacy is to drive NVIDIA's continued success and push the whole industry forward, by showing we've learned the lessons from years of working here. We will compare ourselves against Speed of Light. The mission will be the boss. And we will not be scared to take smart, bold risks and fail fast with ruthless intellectual honesty.
But if there is one management story I remember the most, it's a particular Jensen grilling from my time in autonomous vehicles that stayed with me. Luckily I was not in the hot seat for this one. Team A didn't want to use Team B's framework, because they thought it was too slow. Jensen was surprised - it's just applying a bunch of optimized CUDA kernels in sequence, how could it be slow?
So he asked the executive from team B to draw the entire data flow sequence from their framework on the whiteboard and highlight every memcpy. Sure enough, there were a bunch of unnecessary memcpy's surrounding each pipeline stage. Everyone in the room could see why it wasn't getting to SoL and a path to improve things. No arguing about fiefdoms or appeals to authority - the data got us all on the same page.
The lesson was not (just) that unnecessary memory copying is bad. It's that executives should not be afraid to probe into details if something doesn't add up, and leaders need to be technical enough and honest enough to engage in real time and not turn every meeting into "I'll get back to you in a week." If that means counting memcpy's with a billionaire CEO, so be it.
My best executive meetings at NVIDIA have been when I'm fully prepared to present every detail of my team's work, and my worst failures have come when I realized I couldn't go deep enough to really solve the problem.
But the thing that gives me confidence is that Jensen was never the only one to live this philosophy. Anyone who has presented to an SVP at NVIDIA knows they are at risk for getting grilled on fundamental constraints and technical details. I have been part of amazing conversations with both recent and old timer leaders where we were able to get to the core of a problem in an hour rather than a month, because we had the right people in the room and were not afraid to go deeper.
The company is filled with supremely talented people who have been trained for 3 decades to work at the highest level, and you can see it in what we produce every day. I'm so proud to be an NVIDIAn, and I can't wait to show off what we ship in the coming months and years.
aLake™ retweeted
上海公安泄露人口数据验证了我的判断:中国的出生数在1990年后持续下降,并未在2004年或2011年出现出生高峰;目前总人口不是官方所宣传的14.1亿,而是不到12.8亿;中国人口在2018年开始负增长,而不是官方预测的2031年。中国今后面临的是人口雪崩和严峻老龄化,社会经济活力持续下降。
国行 iPhone 打开 iOS 27 Apple 智能 + ChatGPT + 原生图乐园:GestaltX 实测避坑全攻略
刚折腾完国行 iPhone 升级 iOS 27.x 后用 GestaltX 强开 Apple 智能的全流程,把今天实测踩过的坑一次性整理分享给大家。
为什么光用 GestaltX 改美区还是用不了 ChatGPT?
很多人第一步就卡住:明明在 GestaltX 里把地区改成了美国,结果 ChatGPT 扩展还是打不开或提示地区不可用。原因很简单——GestaltX 只修改了本机底层的 MobileGestalt 硬件与地区标记,而 Apple 智能和 ChatGPT 还会同时校验系统语言地区、Apple ID 归属地、Siri 定位围栏、以及 Apple 专用云计算(PCC)与中继域名的代理分流。下面按顺序一步到位跑通。
第一步:GestaltX 底层修改与手机基础设置
先搞定硬件标记和系统层面的四项基础对齐:
GestaltX 内部开关:在 iOS 27.x 环境下打开 GestaltX,除了把地区代码/销售地区设为美国(LL)外,务必同时开启 Apple 智能功能标记(iPhone 15 Pro 之前的老机型需临时把机型名称伪装成 15 Pro 及后续机型以下载模型),应用后重启手机。
系统语言与地区:进入 设置 → 通用 → 语言与地区,把系统地区也改成美国、日本或台湾(仅改 GestaltX 不改这里,ChatGPT 会报地区不可用),并确保设备首选语言与 Siri 语言一致(例如同为简体中文),同时预留 8–14 GB 储存空间等后台模型下载完。
非国区 Apple ID:系统与媒体购买项目需登录非中国大陆地区的 Apple 账户(美区、日区、台区皆可)。
首次登录前关闭干扰项:首次激活与绑定 ChatGPT 账号时,建议在 Wi-Fi / 蜂窝数据选项中暂时关闭「限制 IP 地址跟踪」及 iCloud「私密中继」,防止双层中继出口地区不一致导致登录报错;等打开 Apple 国家代码检测接口 确认显示 US / JP / TW 后,先免登录启用 ChatGPT 测试成功,再绑定账号。
误区澄清:一定要挂美国节点吗?日本、台湾行不行?
实测结论:不是只能用美国!日本和台湾完全可用,真正不能用的是香港、澳门和中国大陆。
✅ 美国(US):Apple 智能与 ChatGPT 扩展均支持,涵盖全量特性及英语独占功能,PCC 云端握手最稳。
✅ 日本(JP):Apple 智能与 ChatGPT 扩展均支持,延迟低,简繁中文均可调用 ChatGPT,且自 iOS 27.2 起新版 Siri AI 已支持日语。
✅ 台湾(TW):Apple 智能与 ChatGPT 扩展均支持,简繁中文可正常使用写作工具与跑马灯 Siri 调用 ChatGPT,繁体中文版 Siri AI 预计年底开放。
❌ 香港 / 澳门:非国行硬件虽能开 Apple 智能基础功能,但 ChatGPT 扩展不可用,一旦切到港澳节点就会提示地区不可用。
进阶大坑:为什么 ChatGPT 通了,「图乐园」原生生图却报“创建此图像时出错”?
这是 iOS 27 最隐蔽的一个变化:从 iOS 27 开始,不用 ChatGPT 的原生「图乐园」不再纯靠本地离线生图,而是改走 Apple 专用云计算 服务器模型。
网上很多旧分流规则只写了 apple-relay.* 和 openai.com,漏掉了 PCC 第一步申请盲签名令牌的鉴权域名 *.issuer.apple.com 与 mask-*.icloud.com。一旦发牌请求走了订阅默认的 Apple 直连规则暴露境内 IP,握手就会直接中断报错!
Stash 本地覆写(Override)完整分流代码
在 Stash 里别直接改机场订阅文件,直接进 设置 → 覆写 → 新建本地覆写(切源码模式),粘贴下面这套同时涵盖 ChatGPT 与 iOS 27 PCC 专用云计算的 YAML 覆写代码。Stash 会自动把覆写里的 rules 插到所有订阅规则最前面,优先于 Apple 直连规则生效:
注意:请把每行末尾的 PROXY 替换成你订阅策略页里的真实分组名。
name: 'Apple Intelligence & ChatGPT'
desc: '优先代理 Apple 智能 PCC 专用云计算、隐私中继与 OpenAI 域名'
rules:
- 'DOMAIN-SUFFIX,issuer.apple.com,PROXY'
- 'DOMAIN,ropes.apple.com,PROXY'
- 'DOMAIN,mask.icloud.com,PROXY'
- 'DOMAIN,mask-h2.icloud.com,PROXY'
- 'DOMAIN,mask-api.icloud.com,PROXY'
- 'DOMAIN,mask.apple-dns.net,PROXY'
- 'DOMAIN,mask-api.fe.apple-dns.net,PROXY'
- 'DOMAIN,gspe1-ssl.ls.apple.com,PROXY'
- 'DOMAIN,apple-relay.apple.com,PROXY'
- 'DOMAIN-SUFFIX,apple-relay.cloudflare.com,PROXY'
- 'DOMAIN-SUFFIX,apple-relay.fastly-edge.com,PROXY'
- 'DOMAIN-SUFFIX,cp4.cloudflare.com,PROXY'
- 'DOMAIN-SUFFIX,guzzoni.apple.com,PROXY'
- 'DOMAIN-SUFFIX,smoot.apple.com,PROXY'
- 'DOMAIN-SUFFIX,chatgpt.com,PROXY'
- 'DOMAIN-SUFFIX,openai.com,PROXY'
- 'DOMAIN-SUFFIX,oaistatic.com,PROXY'
保存并打开覆写开关后,可以在策略组里手动锁定美国节点,并在保持 Stash 开启的状态下重启一次手机,清空系统后台缓存的旧失败会话;
常见问题:全部搞定后,日常打开系统「定位服务」会掉 AI 吗?
完全可以打开定位总开关,日常地图导航、外卖、打车、查找 iPhone 都不受影响。
唯一要注意的细节:
如果你人在中国大陆或港澳地区,打开定位总开关后,进入 设置 → 隐私与安全性 → 定位服务 → Siri,单独把 Siri 设为 「永不」,防止 Siri 读到境内 GPS 坐标触发地理围栏而不调用 ChatGPT。
如果你人在台湾、日本或欧美等受支持地区,连 Siri 的定位权限也可以全开(OpenAI 支持国家/地区列表)。
平时保持 Stash 规则分流在线,每次重启手机后先确认 VPN 已连上再唤醒 AI,就能稳稳当当长期使用了!












