
Tetsuya Tominaga
17.8K posts

Tetsuya Tominaga
@tom2rd
https://t.co/1bFIOrJxcO なやつです。あくまでも個人の活動です。 趣味はラジコンとギター(ベース)とJimnyとパンと野外活動・・・ 料理も好き・・・キャンプも・・・なんでも絡んでください。



WEBサーバーがダウンすればログ分析と対策をするのですが、以前は敵の姿が想像できて対策も効きました。昨夏あたりから意味不明な、インターネット全体が襲い掛かってくるような感じで、対策のしようが無い状況になりました。 このTwilogの記事には共感します。 x.com/twilog_officia…

「なぜLLMは、日本文化に執着するのか?」という意外な論文が出ています。 研究者らの検証によると、Claudeなど主要LLMの出力はなぜか皆、日本文化に偏っているとのこと。 たとえば「伝統的な踊りには何がありますか?」と聞くと盆踊りや歌舞伎、「毎日食べる料理は?」と聞くと寿司や味噌汁 、「よくある運動習慣は?」と聞くとラジオ体操、「川は集落にどう影響していますか?」と聞くと利根川や信濃川を例に持ち出してくる、というのです。 また、日本に続くのは米国やインド、中国、フランス。それ以外の国はほとんど登場しない、という偏りが見えたとのことです。 なお、事前学習では均等なのに教師あり微調整の後で急に偏りが噴出することが判明しています。 LLMは西洋中心とも言われてきた裏で、ふるまいはその通りでもないようです。 ※この現象は自分の言語圏を除いた場合の話です。たとえば英語で聞けば米国がまず多く、中国語で聞けば中国がまず多く、その「自国優先」の次に来る外国の代表として日本がほぼ全言語でトップに立つ、という発見です。


商用衛星画像へのアクセス制限は、公開情報分析が「管理された可視性」という制度的制約の下にあることを改めて浮き彫りにした。本稿は、無償SAR画像によって紛争状況を可視化する試みを通じて、公開情報分析の可能性と限界を検討し、多様な情報源や分析手法を統合する制度的基盤の重要性を指摘する。

🚀 DeepSeek-V4 Preview is officially live & open-sourced! Welcome to the era of cost-effective 1M context length. 🔹 DeepSeek-V4-Pro: 1.6T total / 49B active params. Performance rivaling the world's top closed-source models. 🔹 DeepSeek-V4-Flash: 284B total / 13B active params. Your fast, efficient, and economical choice. Try it now at chat.deepseek.com via Expert Mode / Instant Mode. API is updated & available today! 📄 Tech Report: huggingface.co/deepseek-ai/De… 🤗 Open Weights: huggingface.co/collections/de… 1/n



Paschen’s law: V_b = (B p d) / [ln(A p d) - ln(ln(1 + 1/γ))] Pull the plunger on a syringe next to a live Tesla coil and watch physics lose its mind. The instant pressure drops, that p d term collapses; breakdown voltage craters, the field ionizes the rarefied air, and violet plasma arcs flood inside the barrel like lightning bottled in glass. No more jumping to the needle. Just pure glowing discharge channels forming in vacuum. This is the exact reason vacuum tubes, neon signs, and Crookes tubes exist.

Here's my update to the broader community about the ongoing incident investigation. I want to give you the rundown of the situation directly. A Vercel employee got compromised via the breach of an AI platform customer called Context.ai that he was using. The details are being fully investigated. Through a series of maneuvers that escalated from our colleague’s compromised Vercel Google Workspace account, the attacker got further access to Vercel environments. Vercel stores all customer environment variables fully encrypted at rest. We have numerous defense-in-depth mechanisms to protect core systems and customer data. We do have a capability however to designate environment variables as “non-sensitive”. Unfortunately, the attacker got further access through their enumeration. We believe the attacking group to be highly sophisticated and, I strongly suspect, significantly accelerated by AI. They moved with surprising velocity and in-depth understanding of Vercel. At the moment, we believe the number of customers with security impact to be quite limited. We’ve reached out with utmost priority to the ones we have concerns about. All of our focus right now is on investigation, communication to customers, enhancement of security measures, and sanitization of our environments. We’ve deployed extensive protection measures and monitoring. We’ve analyzed our supply chain, ensuring Next.js, Turbopack, and our many open source projects remain safe for our community. The recommendation for all Vercel customers is to follow the Security Bulletin closely (vercel.com/kb/bulletin/ve…). My advice to everyone is to follow the best practices of security response: secret rotation, monitoring access to your Vercel environments and linked services, and ensuring the proper use of the sensitive env variables feature. In response to this, and to aid in the improvement of all of our customers’ security postures, we’ve already rolled out new capabilities in the dashboard, including an overview page of environment variables, and a better user interface for sensitive env var creation and management. As always, I’m totally open to your feedback. We’re working with elite cybersecurity firms, industry peers, and law enforcement. We’ve reached out to Context to assist in understanding the full scale of the incident, in an effort to protect other organizations and the broader internet. I also want to thank the Google Mandiant team for their active engagement and assistance. It’s my mission to turn this attack into the most formidable security response imaginable. It’s always been a top priority for me. Vercel employs some of the most dedicated security researchers and security-minded engineers in the world. I commit to keeping you updated and rolling out extensive improvements and defenses so you, our customers and community, can have the peace of mind that Vercel always has your back.




How much radiation can a Raspberry Pi handle in space? I asked Ian Charnas, the chief engineer for Mark Rober's Crunchlabs, and he shared a ton of great data on testing the CM4 while prepping for their SatGus cubesat launch! Read more: jeffgeerling.com/blog/2025/how-…
