Decrypt

✦ Web Designer & Web Dev ✦
Working with @DefiLlama, @OAK_Res, @CryptoastMedia & @adan_asso

[Decrypt @DecryptTV]

https://t.co/0Kqkwho5C4

[Decrypt @DecryptTV]

@J0se @levelsio

[Decrypt @DecryptTV]

@peduarte and yes this color picker

[Decrypt @DecryptTV]

@peduarte I shared everything and my logs on slack if needed, I use cmd+space by default, it worked for a week. Theb it was only workin to open but not to close. Had to press escape. Then it also stopped working to open it. In settings, the raycast shortcut changer was not detecting space

[Decrypt @DecryptTV]

@peduarte Ran into those issues :
- space bar no longer recognised after a week, could no longer open / close raycast, or change shortcuts
- color picker not working
- pasting color hex code not giving details
- search field inside settings not displaying all results

[Decrypt @DecryptTV]

@bstaples GitLab UI is so terrible that I wouldn’t switch even if I were paid

[Decrypt @DecryptTV]

@BTChip @mpfeth That doesn’t make sense. If your bathtub has multiple leaks and someone is stealing your water, fixing one hole doesn’t solve anything. They’ll just use another one.

[DefiLlama.com @DefiLlama]

DefiLlama 2025 Wrapped

Let’s begin.

[Decrypt @DecryptTV]

Rewrote pokeget in Zig: zigdex. Single binary, embeds 1010+ sprites for offline use, 1/128 shiny odds, and it's stupid fast, optimized for shell scripts.

Benchmark (hyperfine):

▓░░░░░░░░░ 0.75ms zigdex
▓▓░░░░░░░░ 1.28ms pokeget
▓▓▓▓▓▓▓▓░░ 3.95ms krabby

Hook it to fastfetch in .zshrc for a random mon on every terminal launch. No I/O, no excuses. And feel free to contribute, it's fully open source.

https://t.co/A143mc756O

[Decrypt @DecryptTV]

Just created ClaudeMeter, a little macOS menu bar app that shows your @claudeai usage like a battery.

Pulls straight from the desktop app or browser session, updates every minute. Tells you when the next reset is. All local. (Not for the Claude API usage, but feel free to create a PR if you want to add support)

Wrote it in SwiftUI, runs on MacOS 26, lightweight.

App file ready: https://t.co/xSiYfulcnK

Or build it yourself here: https://t.co/fy4n8DWp1h

Fully open source. Feel free to contribute.

[Decrypt @DecryptTV]

@John_Vance @0xngmi You’re not the cool kid you think you are

[0xngmi @0xngmi]

@smyyguy the chart i mentioned had data from this month (october 2025)

[Name: Less @Name_is_Less]

Promise stays
Find her

[Decrypt @DecryptTV]

@Hetzner_Online yes, tell me ?

[Decrypt @DecryptTV]

@saltyAom got an outage with them yesterday, broke 2 of my servers

[Decrypt @DecryptTV]

@arno39 Bozo

[Marusha @maruushae]

Nah you don't get to delete that dune, you are a brand, you did retarded thing, now it's for all to see, you want to attack lama by retweeting a know scammer, while using Defillama? you don't get to just delete and that shit getting away, open your mouth so i can spit inside it

[Decrypt @DecryptTV]

@AlsieLC @shilllin @Dune

[Decrypt @DecryptTV]

@dok2001 @heyandras https://t.co/VTkUHMJLLz

[Decrypt @DecryptTV]

So @Cloudflare is making you pay to fix their bug.

Here’s the situation:

Modern frameworks like @nextjs App Router use the HTTP Vary header (defined in RFC 7231) to tell CDNs:

“Cache HTML and RSC payloads separately, based on request headers.”
Example:

/page with no RSC header → returns HTML (text/html)
/page with RSC header → returns RSC payload (text/x-component)Next.js sets:Vary: RSC, Next-Router-State-Tree, Next-Url, ...

Every major CDN (@fastly , @cloudfront , @Akamai ) respects this, so they cache and serve HTML vs RSC correctly.

Cloudflare does not.

They completely ignore Vary (except Accept-Encoding).

Result:

If HTML is cached first, client navigations break (RSC request gets HTML).
If RSC is cached first, page reloads show raw RSC payload as text instead of HTML.

I opened a support ticket. Their answer?
They admitted Cloudflare is non-compliant by design and told me if I want correct behavior, I need to upgrade to Enterprise.

In other words:

@CloudflareDev is deliberately ignoring a core part of the HTTP spec… and charging you extra to patch around the fallout.

Workarounds exist (Workers, query params), but they shouldn’t be necessary. This isn’t a “feature request”, it’s a standards compliance bug that breaks Next.js and any framework relying on Vary.

Other CDNs respect the spec. Cloudflare does not.
cc @vercel @rauchg

[Decrypt @DecryptTV]

Shawww from #SilkSong

[Decrypt @DecryptTV]

@AvgDatabaseCEO @Cloudflare @nextjs my goal is getting Cloudflare to fix a spec-breaking bug. if that makes ppl mad, so be it

[Decrypt @DecryptTV]

So @Cloudflare is making you pay to fix their bug.

Here’s the situation:

Modern frameworks like @nextjs App Router use the HTTP Vary header (defined in RFC 7231) to tell CDNs:

“Cache HTML and RSC payloads separately, based on request headers.”
Example:

/page with no RSC header → returns HTML (text/html)
/page with RSC header → returns RSC payload (text/x-component)Next.js sets:Vary: RSC, Next-Router-State-Tree, Next-Url, ...

Every major CDN (@fastly , @cloudfront , @Akamai ) respects this, so they cache and serve HTML vs RSC correctly.

Cloudflare does not.

They completely ignore Vary (except Accept-Encoding).

Result:

If HTML is cached first, client navigations break (RSC request gets HTML).
If RSC is cached first, page reloads show raw RSC payload as text instead of HTML.

I opened a support ticket. Their answer?
They admitted Cloudflare is non-compliant by design and told me if I want correct behavior, I need to upgrade to Enterprise.

In other words:

@CloudflareDev is deliberately ignoring a core part of the HTTP spec… and charging you extra to patch around the fallout.

Workarounds exist (Workers, query params), but they shouldn’t be necessary. This isn’t a “feature request”, it’s a standards compliance bug that breaks Next.js and any framework relying on Vary.

Other CDNs respect the spec. Cloudflare does not.
cc @vercel @rauchg

[Decrypt @DecryptTV]

@samselikoff @reactjs ok thank you I see, I was thinking whether the compiler could eventually recognize common "hidden but keep state" patterns and rewrite them to <Activity /> under the hood. but I get that keeping it explicit is safer since intent matters