that’s a great question. thank you for the question
I love how every single one of your posts ends
Flareon you should add on Discord~
- she/her
Member of a traumagenic–catharigenic, semi-structural DID system (host: @LoganDark)
Feral female Flareon, somewhat kinky but terminally panromantic towards other ferals~
Please do not call us "alters", we are full people with our own souls, not just personality states! We say "system members" or just "members". "People" works too!
Discord: Emily the Flareon#3557 or @emilytheflareon
(open to friend requests! otherkin/plural <3~)
(but seriously add me if you interact uwu)
also feel free to use our asks as direct messages! :3
Discord
Emily the Flareon#3557
add me on discord
add me on discord
add me on discord
add me on discord
add me on discord
:3
You must log in to comment.
in reply to @blep's post:
oh god, supporting range requests was my arch-nemesis for like, a solid half-day. I ended up going pretty much the same route. Dealing with multi-part responses seemed like so much more hassle than it was worth.
for cache control, I ended up having versioned resources (kind of) because I actually didn't want the browser making additional requests (useful when you're loading a page full of images). So instead of replacing an asset, there's redirects along the lines of /foo -> /foo?hash=123456789abcdef, and the page is generated with the hashes already there, so there's no additional requests. (and then /foo?hash=123456789abcdef has the "do not ask me again ever" cache control).
iirc there's some better things possible with cache-control as well, like having a web worker ask the browser to clean up old versions of assets if they're still cached, but that seemed like a lot of work.
all that aside, the rest of what you did is also super cool! Implementing that in two days is an incredible flex