Content
@
https://warpcast.com/~/channel/degentokenbase
0 reply
0 recast
0 reaction
Ryan J. Shaw
@rjs
Countdown to the end of season 5 / start of season 6! This is an experimental frame. The idea is this countdown should be accurate whenever you see the frame, without needing to press a reresh button. Let's see if it works! 🤞 https://degen-countdown.heox.org/
47 replies
9 recasts
68 reactions
memes4airdrop
@wake
It renders dynamically on view?
1 reply
0 recast
1 reaction
Ryan J. Shaw
@rjs
Almost... the illusion is created with a fixed 180 seconds* of counting down, which would be too expensive to generate on every single request (as we speak, it's chowing 40% of 4 server-quality CPU cores non-stop to generate just a single 180 second GIF). So what I do is generate the GIF every second in the background, and the image referenced in the frame changes every second to force Warpcast to show you the latest if you happen to revisit the frame. * I thought about putting a prize at the end of the 180 seconds but figured somebody would get there by accident too quickly, and @ds8 proved me right https://warpcast.com/ds8/0xdf96deb2
6 replies
0 recast
4 reactions
onten.eth | Ⓜ️🍖🎩
@rezaisgoat.eth
Do you create the frames on the fly for the next 180 frames? How would it make the performance if you create all the frames needed for a countdown beforehand and only stick them together when creating the gif? For proxy[.]wrpcd[.]net to not cache the image you used the "public, max-age=1" header value, right?
1 reply
0 recast
0 reaction
Ryan J. Shaw
@rjs
It's about 2KB/frame, so 3*24*60*60 ~= 500MB of storage but about 3*24*60*60*0.4/360 ~= 288 seconds of CPU time. So I'd have to store it to disk, but that's 260K files which is a nuisance to dev & test with when fine tuning the clock algorithm... not 100% sure if it's worthwhile pursuing, but not a bad idea 1000 $degen And yeah I'm sending `public, max-age=1`, but CF doesn't pass that through even though I've set "Respect existing headers" in the cache config... This is literally the entire frame server, using my Netcaster library:
3 replies
0 recast
2 reactions
onten.eth | Ⓜ️🍖🎩
@rezaisgoat.eth
I think I have the solution to your CF issue, because I had literally the same think happening to me :D The fix is to have a new rule under Caching -> Cache Rules for the subdomain. & set the rules like this (I also turned on sorting query params):
2 replies
0 recast
0 reaction
onten.eth | Ⓜ️🍖🎩
@rezaisgoat.eth
It happens because CF sets the Cf-Cache-Status to Dynamic by default and this is what dynamic does:
1 reply
0 recast
0 reaction
Ryan J. Shaw
@rjs
OOoh nice, I'm going to play around with this! 1000 $degen
1 reply
0 recast
0 reaction
