Decrypt

112 posts

Decrypt banner
Decrypt

Decrypt

@DecryptTV

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

🪐 Katılım Nisan 2020
96 Takip Edilen290 Takipçiler
Decrypt retweetledi
DefiLlama.com
DefiLlama.com@DefiLlama·
DefiLlama 2025 Wrapped Let’s begin.
DefiLlama.com tweet media
English
60
25
163
37.2K
Decrypt
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. github.com/Decryptu/zigdex
Decrypt tweet media
English
1
1
22
3.5K
Decrypt
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: github.com/Decryptu/claud… Or build it yourself here: github.com/Decryptu/claud… Fully open source. Feel free to contribute.
Decrypt tweet media
English
0
1
8
314
JV 🟪
JV 🟪@John_Vance·
@0xngmi not true but thanks for subscribing
English
3
0
5
1.7K
0xngmi
0xngmi@0xngmi·
> blockworks becoming a data first org that's cool, you guys could start by not reselling our free data for 4.5k/yr against our ToS, even after telling us you had removed all our data when we asked screenshot from blockworks paid platform, 1 min ago
0xngmi tweet media
Yano 🟪@JasonYanowitz

Update on our next phase of growth (long post) TL/DR: Blockworks is becoming a software/data first org When Mike and I started Blockworks in 2017, we wanted to solve "the information problem." Crypto was growing up fast and the new entrants deserved better information. We've built everything from events to podcasts, research, data, and news. As we’ve scaled, we’ve experienced massive growth across all business units: we've had record revenues in 2025 and we'll have another record year in 2026. Over the past two years, we have seen particularly rapid growth in our data business. The market is telling us that our combo of data + distribution is extremely valuable. Every day, we hear from both investors and protocols that Blockworks data is critical to their daily workflow. And so, we're going all in on what Mike and I believe is the greatest opportunity we’ve seen since launching Blockworks in 2017. More on this soon :) Now, to talk about news... Mike and I launched news in 2021 as an extension of our events, podcasts, and newsletter businesses. At the time, crypto media couldn't speak fluently to tradfi, and trad media couldn't understand crypto. Since then, Blockworks has broken big stories, published thousands of stories, been cited by nearly every major publication, and helped shape the industry conversation every day. I am very proud of the work that the team has done. But the landscape is changing and the same problems don’t exist today. There are many strong crypto media publications. Great journalists combined with new tools have raised the bar in reporting, and traditional outlets have also improved. Meanwhile, users are increasingly looking toward data as a primary information source. So we’ve decided to sharpen our focus on software and data and exit our news business. To our incredible news team: a huge, heartfelt thank you. You built something that helped shape the industry and fueled the growth of Blockworks. I have a deep amount of respect for all that you do. To anyone hiring crypto journalists, please reach out – everyone is incredible. To the broader Blockworks community: over the coming months, you’ll see Blockworks evolve into a data-first intelligence platform. Our website will become a true data destination. Our main newsletters and podcasts will continue to set the pace for conversations that drive the industry. Our events will continue to grow (DAS is coming to Abu Dhabi next year). And we’re rolling out more category-defining software and data products soon. Love you all, onwards.

English
113
153
2.2K
244.1K
Decrypt retweetledi
Name: Less
Name: Less@Name_is_Less·
Promise stays Find her
Name: Less tweet media
English
22
1.9K
14.7K
131.9K
Decrypt
Decrypt@DecryptTV·
@saltyAom got an outage with them yesterday, broke 2 of my servers
English
0
0
0
1.4K
SaltyAom
SaltyAom@saltyAom·
Hetzner CX32 4 vCPU, 8GB RAM, 80GB storage, 20TB bandwidth Slap Coolify on top Add Cloudflare Tunnel, and Origin Certificate Setup GitHub webhook to deploys automatically You can deploys several projects, and database there $6.99/month or double the specs for $9.99
SaltyAom tweet media
English
82
36
1.2K
108.4K
Alsie 🇦🇪
Alsie 🇦🇪@AlsieLC·
@shilllin @Dune We don’t create narratives. The narrative will manifest itself through data. 🌊
English
30
17
77
28K
Alex 🥷
Alex 🥷@Shilllin·
Dune >>> DefiLlama Open dashboards >>> Hidden data Community analytics >>> VC filters Decentralization >>> Centralization Transparency >>> Secrecy After tweets made by the DefiLlama cofounder this morning I will only be using Dune as a trusted analytics source
Alex 🥷 tweet mediaAlex 🥷 tweet media
English
53
63
291
44.6K
Decrypt
Decrypt@DecryptTV·
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

QME
0
0
2
30
Decrypt
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 tweet media
English
28
15
417
45.7K
Decrypt
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
English
1
0
0
91
Sam Selikoff
Sam Selikoff@samselikoff·
@DecryptTV @reactjs Exactly. It also deprioritizes rerenders (which you can't do in userland). Hm not sure what you mean by inline it? How would that work?
English
1
0
1
78
React
React@reactjs·
React 19.2 is now available! This release includes Activity, useEffectEvent, React Performance Tracks, partial pre-rendering, and more!
React tweet media
English
49
485
2.7K
318K
Decrypt
Decrypt@DecryptTV·
@samselikoff @reactjs ok ok, so <Activity /> gives semantics that aren't possible with just userland patterns (CSS hide / conditional render). makes sense. do you see the compiler eventually being able to inline/optimize <Activity />, or will it always stay an explicit primitive?
English
1
0
0
145
Sam Selikoff
Sam Selikoff@samselikoff·
@DecryptTV @reactjs It keeps the component rendered but destroys any Effects. So can't quite be done in userland.
English
1
0
1
146
Decrypt
Decrypt@DecryptTV·
@adamwathan Been using the Tailwind extension in @raycast for a while, even faster than AI
Decrypt tweet media
English
1
0
2
505
Adam Wathan
Adam Wathan@adamwathan·
The AI effect is wild — this is traffic to tailwindcss.com compared with monthly downloads of the tailwindcss package. Interesting times navigating this and figuring out what to do with it for sure!
Adam Wathan tweet media
English
70
18
600
66.9K
Laravel
Laravel@laravelphp·
This is the biggest update to server management since 2014. ◆ Instant Laravel VPS servers ◆ Zero downtime deployments ◆ Team terminal sessions ◆ Free on-forge domains ◆ Health checks, Heartbeats, & real-time metrics
English
31
82
418
143.7K
Decrypt
Decrypt@DecryptTV·
Close, but slight correction: Initial page load = 1 request → HTML Client-side navigation = 1 request → RSC payload Without Vary support, Cloudflare caches whichever response it sees FIRST for /page, then serves that same cached response for both HTML and RSC requests. So: - User A loads page (HTML) → CF caches HTML - User B navigates there (needs RSC) → CF serves cached HTML breaks OR: - User A navigates there (RSC) → CF caches RSC - User B loads page (needs HTML) → CF serves cached RSC shows raw data Query param workaround (?__cf_rsc=1) makes CF see them as different URLs: - /page → caches HTML - /page?__cf_rsc=1 → caches RSC Both get cached, just separately. This is what the Vary header SHOULD do automatically but CF ignores it.
English
0
0
1
50
joe
joe@joe622724616854·
@DecryptTV @BraydenWilmoth so even though page loading is 2 requests, cloudflare is caching them together instead of only caching the html, meaning then you have to specifically add query params to rsc isnt cached with the original page?
English
1
0
0
37
Brayden
Brayden@BraydenWilmoth·
Migrating from Vercel to Cloudflare is easy. - Run 2 commands - Add 2 files - Modify your package.json - npm run dev Need help? DM me and will spend time this week helping out if you need it. This also allows me to make our process better.
Brayden tweet media
English
51
240
2.3K
171.1K