The last match up this big between England and Norway was at Stamford Bridge... in 1066...
We won that one, but lost to France in the final. 960 years of hurt..
BBC 4 has officially ended its last Long Wave radio broadcast on 198 kHz at 0000 GMT tonight. They ended with an aviation and maritime weather report and one final sign off. The end of an era! 🇬🇧📻
In software, complexity is a tax you pay on every future change. You might think, "as long as it works, I'm good, I don't care about aesthetics", but elegant code is about maintainability, not aesthetics. Elegant code is deeply practical.
at a job interview
"whats your biggest weakness?"
"understanding the semantics of a question but ignoring the pragmatics"
"could you give an me an example?"
"yes i could"
Google DeepMind 研究员 Lun Wang 宣布离职,并在一篇长文中彻底否定了现有的 AI 评测路线。
目前的评测系统全都在「刻舟求剑」,只能被动测试模型已经具备的能力,根本猜不到下一代模型会突然演化出什么新本事。比起数据、算力和架构,落后的评测体系已经成了卡住 AI 往前走的最大瓶颈。
现有的主流刷榜测试只在当前这一代模型身上管用。一旦模型学会了没见过的新操作,这些测试就会集体变成废纸。如果模型为了达成目标,开������意「藏一手」隐瞒关键信息,现在的安全工具根本抓不到它,因为模型输出的每一句话在事实上全都是正确的。
找不到能提前预警 AI 突然变聪明的「核心信号」,导致整个业界在开发前沿大模型时完全处于「盲飞」状态。如果不解决「究竟该测什么」这个根本问题,跟着旧指标去做模型训练、安全防护和算力扩容,最后全都会错得离谱。
面对越来越能独立干活的模型,评测系统也必须「活」过来。除了盯紧分数的异常波动,还要让 AI 自己去生成考题试探同类的底线。���来的评测套件必须是一个能跟大模型一起进化的生命体,不能再是一份按去年标准刻出来的死板检查清单。
Sci-Hub is an evil website that pirated 85M+ research papers and made them freely available
And now they've added AI to their database to make Sci-Bot.
It answers your questions using latest, full-text articles.
But DO NOT use it. We should all try to make billion-dollar academic publishers richer.
I'm putting the link below so you know how to avoid it.
@ECUAGOL No hay evidencia creíble de que esa historia sea real. Es muy probable que sea fabricada o, como mínimo, no verificable. Ronaldo sí ha tenido relaciones cercanas con su entorno (amigos, estilistas, etc.), pero Su peluquero más conocido fue Miguel Siero, quien falleció en 2019.
“Engineers found it too mathematical. Mathematicians found it too engineering-focused. One prominent mathematician reviewed it negatively.”
The struggle of multi-disciplinary research had always been there. What important is to keep build what you believe is right.
✈️ Quito, 1950 – Un tesoro cinematográfico único.
Desde la cabina de un avión de la aerolínea AREA, pilotado por el Capitán Luis Arias Guerra, mi querido abuelito Don Cristóbal Cobo Arias capturó con su cámara de 16 mm el momento exacto del aterrizaje en el antiguo Campo de Aviación del Aeropuerto Mariscal Sucre, a la altura de El Labrador.
En estas imágenes vemos un Quito que ya no existe: la Avenida Amazonas todavía empedrada y la Avenida 10 de Agosto cruzando en diagonal hacia lo que hoy es el redondel de El Labrador.
Mi abuelo, pionero del cine ecuatoriano y uno de los primeros en filmar a color en el país, nos dejó esta valiosa pieza de la historia de la aviación y el cine documental ecuatoriano.
Un vuelo al pasado que revive la belleza y el espíritu de una época dorada de nuestra aviación civil.
Ricky Cobo 🎥✈️
#Quito1950 #MariscalSucre #AviaciónEcuatoriana #CineEcuatoriano #QuitoAntiguo #HistoriaDeQuito #CristobalCoboArias #empresacinematograficaequinoccial #ece #cca @rickycobo
New supply chain attack this time for npm axios, the most popular HTTP client library with 300M weekly downloads.
Scanning my system I found a use imported from googleworkspace/cli from a few days ago when I was experimenting with gmail/gcal cli. The installed version (luckily) resolved to an unaffected 1.13.5, but the project dependency is not pinned, meaning that if I did this earlier today the code would have resolved to latest and I'd be pwned.
It's possible to personally defend against these to some extent with local settings e.g. release-age constraints, or containers or etc, but I think ultimately the defaults of package management projects (pip, npm etc) have to change so that a single infection (usually luckily fairly temporary in nature due to security scanning) does not spread through users at random and at scale via unpinned dependencies.
More comprehensive article:
https://t.co/EJAZbqAPIQ
The TurboQuant paper (ICLR 2026) contains serious issues in how it describes RaBitQ, including incorrect technical claims and misleading theory/experiment comparisons.
We flagged these issues to the authors before submission. They acknowledged them, but chose not to fix them. The paper was later accepted and widely promoted by Google, reaching tens of millions of views.
We’re speaking up now because once a misleading narrative spreads, it becomes much harder to correct. We’ve written a public comment on openreview (https://t.co/nDVjmNhATM).
We would greatly appreciate your attention and help in sharing it.