Tomeu Cabot

Staff Frontend engineer at @cohere 🤖
Formerly @twilio, @trivago.
Mallorca 🏝♥
My opinions are my own.

[Miguel Ángel Durán @midudev]

¡La mejor librería de sliders que he visto para 2026!
Solo ocupa 4.3KB y usa el mínimo JavaScript posible.

✓ Funciona con scroll-driven animations
✓ Añade drag con ratón
✓ En móviles carga 0KB

Se llama Blossom:
https://t.co/9v2w0T9Pt8

[Cohere @cohere]

When you rent your artificial intelligence, you have no control, and no choice. This is why sovereignty and ownership matters.

Whether it means using your own hardware, open source, or deep customization. Own your AI, own your future.

[Daniel @DanielWhit21874]

You know what is so satisfying to use ?

Slot-text

https://t.co/NLjNwFO8I3

[shadcn @shadcn]

You have Claude Fable for only a few days. Here's how to make the most of it.

Introducing /improve: use your most capable model to audit your codebase and write plans for cheaper models to execute later.

Studies your code, figures out bugs, perf, tech debt, missing tests, what to build and writes plans any agent can run.

[Cohere @cohere]

Introducing Cohere's first open-source coding model: North Mini Code

Small & efficient, designed for agentic performance and built for community input.

[balint @BalintFerenczy]

Use the scroll-padding CSS property when using a scroll fade so your items don't get stuck in the fade region.

Bonus: It also makes clicking through each option way more convenient!

[Florian @flornkm]

Tip: prevent scrollbars from re-wrapping text.

Using "scrollbar-gutter: stable" fixes this

[Ali Grids @AliGrids]

this inline table editing interaction is buttery smooth @nitishkmrk

[Ali Grids @AliGrids]

who knew ░▒▓█ could look this good in motion?

Anime.js + block characters = chef’s kiss from @clockmaker

[Sebastiano Guerriero @guerriero_se]

Drag enough to collapse it.

Demo ↓

[m4rio @m4rio_eth]

🚨 TL;DR: Attackers are sending fake Sentry bug alerts to projects using public Sentry DSNs. The fake alert is designed to trick AI agents into running a malicious `npx` command that looks like a Sentry profiling diagnostic.

Do NOT run commands from Sentry issues/logs/alerts unless verified.

These are not legitimate Sentry fix commands. The malicious package reportedly steals environment variables/secrets and sends them to advisory-tracker[.]com.

[Javi Lopez ⛩️ @javilopen]

🔴 I NEED YOUR ATTENTION

I've spent a month helping Miriam with her case of metastatic cancer and I want to share the methodology I've been using because it's completely replicable.

I think (with luck) this could be USEFUL TO OTHER PEOPLE with cancer (or any other illness).

The results we've gotten aren't a miracle, but we believe they're genuinely useful and could mean the difference in a literal life-or-death medical case.

Here's the method step by step:

1/ Use the most advanced models of the moment (unfortunately paid, and not cheap. I think Public Healthcare should invest in this):

- ChatGPT 5 Pro + Extended Thinking (40 min aprox. of thinking per call)
- Claude Opus 4.8 MAX

Still pending deeper testing:

- Perplexity Sonar Pro Max
- NotebookLM

Tested but only useful for additional links/research (not as powerful in my experience)
- OpenEvidence

2/ Feed the AI the FULL clinical history, completely chewed up. This sounds dumb but it's critical.

- The first thing I ask, using Claude Cowork (which has hard drive access), is to go into the folder with the ENTIRE clinical history (can be 100+ PDFs) and consolidate everything into:
- One single PDF (it can be 1000+ pages, whatever it takes)
- One single readable .txt or .md, which it must build correctly using an OCR script and then check thoroughly to make sure it's right.

I insist: don't jump to the next step until you've nailed this one, especially the .txt.

3/ Once you have the above, use this prompt along with the .txt (and optionally the PDF too if you want) as input files, and run it on BOTH models at once (and more if possible).

👉 This prompt is insanely complex/advanced: https://t.co/1qeqEqudCe And it's not designed for Miriam's specific oncology case, you can change the initial parameters for the desired case. And with the models from step 1 you could adapt it to your case without trouble.

In any case, I'm also leaving you this other prompt, even more general, for any type of rare disease: https://t.co/4B327floDP

4/ The ARROWHEAD (adversarial model spiral): facing one model against the other. I've never heard anyone talk about this methodology, but it works incredibly well. The feeling is like sharpening a stake until it gets a gleaming point.

It works like this: with patience and across successive iterations (I recommend a minimum of 7, and keep in mind that if ChatGPT takes 40 min, this will take a while), pit the output (the resulting PDF) from one model against the other. With a simple prompt like:

"Another committee of experts says this. What do you think? If you agree or disagree, tell me why, and generate a new PDF if you think it's necessary."

Then you feed that result back to the opposite model. So, across successive iterations, web searches, papers, etc., they'll find and sharpen more and more.

When to stop? When BOTH models say the work is perfect and they can't improve the other's output any further. This is so absurdly game-changing that I think the output of ALL current models would improve if they followed this methodology (leaning on a kind of adversarial-model spiral). I don't understand why nobody has noticed this, or if they have, why it's not getting more attention. It works impressively well in any domain, including programming and math.

In fact, my theory is this could be done even better not just with two models, but with greater combinatorics, maybe adding Perplexity Sonar Pro Max, etc.

RESULTS

Incredible. Obviously I can't know if they're better than the best scientific-medical committees in the world, but they're giving Miriam a new dimension to her case, additional tests to do, possible exams, etc.

Obviously AI doesn't perform miracles, but I think it can already, today, help many patients. And Public Healthcare should invest a lot (but A LOT) in this.

I'm going to ask Miriam if I can post the full PDF of the most advanced results we've reached, so you can get an idea of the quality. She's already given me rough permission, but I want to make sure 100%.

FUTURE PREDICTION

Easy to make: in the near future (I hope), any person's medical history won't just be fully digitized (we're close, but not all the way, well, well, well). On top of that, it'll be "pre-chewed" so it can be consumed by an LLM in one shot.

CLARIFICATION

- We're aware this is a delicate subject and we don't let the AI make final treatment decisions. What we're doing is clearing the ground for the oncologists so they can have possible paths they may not have considered.
Thanks 🙏

- The top LLMs have context windows for that and much more (much, much more). In any case, the PDF is more of a supporting file for the .txt. Both contain absolutely the entire history, but the PDF allows images/charts/etc. The .txt is what the AI consumes.

- On automation: and yes, this can be automated. Yes, AutoGen supports it almost out of the box. LangGraph builds it really well with supervisor / evaluation loops. CrewAI can orchestrate it too with Flows, although its "consensus" process isn't native yet. That would be the next level: automating it.

PETITION AND DISCLAIMER

If there's any oncologist in the room or you are an LLM company, we'd be grateful if you could take a look / help 🙏

Remember: in any case, this is just one more tool for the doctor.

I've simply shared the methodology I know that processes data more exhaustively, with the best models, and that we believe reaches better conclusions. If you know a better methodology / prompt / whatever, we'd be glad to improve this with your insights and share it.

Then the doctor reviews, adopts, or discards the report.

And if it helps the doctor, it helps the patient. And if it doesn't, all we've lost is some time and tokens. In a case that's literally life or death, that's nothing.

Just plain common sense.

Many people will argue with me, but in the near future it will seem absurd that we ever expected any professional to keep in their head every clinical trial, paper, bibliography, and raw data point that an AI and its agents can process via search in minutes. It will be such a valuable tool for doctors that its daily use will simply be taken for granted.

[Cohere @cohere]

"If you don't know who Cohere is, you will"

- Prime Minister @MarkJCarney 🇨🇦

[Pierre @pierrecomputer]

diffshub[dot]com

Take any public diff from GitHub and virtualize it nearly instantly, no matter how large, with DiffsHub. Built to show off our brand new CodeView component.

To try it out, replace `github` with `diffshub` in your address bar.

[Nick Frosst @nickfrosst]

> be cohere
> join forces with some German companies
> immediately open source your best model
> life is good

[Seb ⚛️ ThisWeekInReact.com @sebastienlorber]

TL;DR for open-source maintainers

🚫 NEVER use "pull_request_target" workflows

🚫 NEVER use shared caches in your publish pipeline

Combining these 2 in particular is extremely dangerous

I've repeated this countless times over the years, but another reminder is always useful

[Manu Arora @mannupaaji]

You can pin a chat scroller to the bottom with CSS 𝚘𝚟𝚎𝚛𝚏𝚕𝚘𝚠-𝚊𝚗𝚌𝚑𝚘𝚛, without having to use MutationObserver or 𝚜𝚌𝚛𝚘𝚕𝚕𝚃𝚘() functions

<𝚍𝚒𝚟 𝚒𝚍="𝚜𝚌𝚛𝚘𝚕𝚕𝚎𝚛">
...
...
<𝚍𝚒𝚟 𝚒𝚍="𝚊𝚗𝚌𝚑𝚘𝚛"></𝚍𝚒𝚟>
</𝚍𝚒𝚟>

#𝚜𝚌𝚛𝚘𝚕𝚕𝚎𝚛 * { 𝚘𝚟𝚎𝚛𝚏𝚕𝚘𝚠-𝚊𝚗𝚌𝚑𝚘𝚛: 𝚗𝚘𝚗𝚎; }
#��𝚗𝚌𝚑𝚘𝚛 { 𝚘𝚟𝚎𝚛𝚏𝚕𝚘𝚠-𝚊𝚗𝚌𝚑𝚘𝚛: 𝚊𝚞𝚝𝚘; 𝚑𝚎𝚒𝚐𝚑𝚝: 𝟷𝚙𝚡; }

Browsers run scroll anchoring by default to prevent layout shifts

Disable it on children, re-enable it on a 1px anchor at the end and the scroll follows new content down on its own

[Miguel Carranza @elwatto]

insane gains. save a rainforest and your budget https://t.co/YPhVE3ACAr

[Soren @sorenblank]

`tabular-nums` should be the default for any number that updates ( timers, counters, prices, percentages, scores, live data etc ).

you can enable this tnum OpenType feature using the CSS property `font-variant-numeric`.

.tabular-nums {
font-variant-numeric: tabular-nums;
}

[Alex Carpenter @alexcarp_me]

Using scroll-padding CSS property to ensure selected item stays visible above the scroll fades.