吳冠廷tinger wu retweeted
指原莉乃プロデュース【≒JOY】
11月25日(水)発売💿
≒JOY 6thシングル
『ロックスター様』
アートワーク👑˖°
➤ nearly-equal-joy.jp/news/det…
#ロックスター様
#ニアジョイ
吳冠廷tinger wu retweeted
[SPOILER DE ABSOLUTE GREEN ARROW]
Confirmando minhas suspeitas, Arqueiro Verde Absolute é CONNOR HAWKE, filho de Oliver Queen!
A partir do segundo arco da HQ (começando na edição 7 em fevereiro) Connor vai assumir o protagonismo de AGA.
吳冠廷tinger wu retweeted
サムネで腹よじれるくらい笑った
結局って、なんでさも議論したことあるような言い草やねん笑笑
youtu.be/mpNFckOljG0?si=Ghto…
pstack v0.15.27 ships with a new skill /create-formal-verification-skill!
it's still in beta, and similar to /create-verification-skill, this is a meta-skill that creates a new skill and formal verification suite based on the characteristics you want to verify. for example, you may want to model state machines and systems with concurrency using TLA+, or use kani in rust to check for undefined behavior.
if you're new to formal verification, think of it as mathematically proving properties and invariants (something that must always be true) or "laws" of your system. usually, this means modeling your programs in a separate language like with TLA+ and then running the solver on that spec. newer approaches like with kani and @bendlang take a different approach where there is no separate language: you write kani in rust, and bend in bend (it's also a programming language, and the proofs are written as laws and expressed in its type system).
historically formal verification never reached mainstream status because of the difficulty in modeling and writing proofs. it's quite difficult to model your business requirements and keep them in sync! but i expect that we will see more innovation in formal verification in the future as being able to formally verifiy that the code does what you intended gives your agents superpowers in writing correct software.
in the meantime though, i've been experimenting with modeling our code with TLA+ and have already found several bugs with the skill created by /create-formal-verification-skill.
try it out and let me know how it goes!
吳冠廷tinger wu retweeted
Claude Code 刚刚通过逆向工程,在 90 秒内破解了我酒店房间的门锁。2014 年的加密技术。右上角的烟雾探测器也使用同一套协议——那个红色小灯不是电池指示灯。我启动扫描时,它闪了两次。
我现在躺在一个每晚 85 美元的酒店房间里。我打开 Claude Code,输入:「扫描范围内的每一台蓝牙和无线设备。告诉我哪些设备在与哪些设备通信。」
它找到了 19 台无线设备。其中 18 台是正常的。
设备 19:一个 BLE 控制器,使用着自 2014 年以来就没有修复过的固件。它控制着电子门锁、烟雾探测器、恒温器和房间里的保险箱。四台设备共用一个控制器。同一种协议。10 年没有任何更新。
我让 Claude Code 分析这套协议。整个过程用了 90 秒。
门锁使用一个 4 字节的滚动密钥,没有会话令牌。Claude Code 在第三次尝试时生成了一个有效的主密钥。我躺在床上,听见房间的门锁咔哒一声打开了。
接着,它发现烟雾探测器也连接在同一条总线上。照片里的红色小灯?那是控制器状态指示灯。它并不监测烟雾。它每隔 8 秒就会确认一次与门锁系统之间的 BLE 握手。
这意味着,任何处于蓝牙覆盖范围内的人——走廊、隔壁房间、停车场——只需要一条提示词和 90 秒,就可以:
打开你的房门
关闭房间内的警报
打开你的保险箱
而烟雾探测器会通过那个小小的红色闪烁,确认连接状态
检查只需要 2 分钟:
步骤 1 → 打开 Claude Code → 粘贴第一条评论中的提示词
步骤 2 → 它会扫描覆盖范围内的每一台 BLE 设备,并标记存在未修复固件的设备
步骤 3 → 如果发现问题 → 要求更换房间 → 要求换到配有机械门闩的房间 → 然后使用那个房间
每一家使用 2018 年之前生产的 ASSA ABLOY 或 Onity 门锁的酒店连锁都存在这个问题。这大约占全球酒店的 30%。
我本周测试了 3 家酒店。3 家全部存在漏洞。
看看照片。右上角。那个每隔 8 秒闪烁一次的红点。那就是握手信号。
保存这条提示词。下次入住酒店时 → 先运行它,再打开行李。
吳冠廷tinger wu retweeted
イベントの受付がスタートしました❣️
♡対面お話会
fortunemusic.jp/joy_202611_t…
♡ツーショット撮影会
fortunemusic.jp/joy_202611_2…
♡オンラインお話会
fortunemusic.jp/joy_202611_o…
いっぱい好きにさせちゃうぞ〜😈
愛伝えさせてねっ
対面イベントどんなお洋服着ようかな💭
待ってるね!!
吳冠廷tinger wu retweeted
Whats happening right now is probably way worse than the Hugging Face incident.
AI-powered attacks are hitting real organizations while major platforms disclose breaches and critical flaws.
- Microsoft reports AI agents targeting hundreds of organizations, reaching privileged cloud access in under three hours in multiple cases. It attributes the ConnectWise compromise to the same group.
- CrowdStrike documented four operators running successful AI-agent campaigns. One compromised at least 15 Argentine healthcare organizations.
- PHP2Shell: AI helped turn longstanding PHP flaws into working exploits. Cloudflare’s CEO reports millions of exploitation attempts. Their AI involvement is unknown.
- Railway disclosed possible access to customer secrets. LiteLLM shipped a backdoored release. Zeabur confirmed another breach and is shutting down.
- GitLab patched a maximum-severity flaw affecting 12 years of releases. Node.js patched a serious code-execution vulnerability, with Vercel deploying firewall protections.
Feels like a turningpoint.
吳冠廷tinger wu retweeted
【スクープ!】
超人気声優の小野賢章(37)×美人声優のM・A・O(34)が「極秘誕生日会デート」
↓独占スクープ写真はこちら
friday.gold/article/448422
小野の誕生日前夜にマーベル映画を見て、しゃぶしゃぶを堪能した二人。日付が変わる瞬間まで一緒にいた二人は小野の離婚前から“親密”だったというが……

























































