there's a special kind of horror where you're trying to use a website and it won't work and you can just glimpse the tip of the iceberg of how they've managed to fuck up their network
these fuckers have multiple domains and some of them are blocked in some countries and they're using cloudflare tunnels to make some of the domains appear to be other domains to some of those users and they haven't gotten their CORS headers 100% in line with this very complicated setup and it means I can't watch a 1970s horror film with my friend from another continent because the Join Watch Party API call is getting rejected by the browser
@foone Might I suggest that you both just download the movie and use https://syncplay.pl/ to manage watching together? That's what I settled on during COVID to continue my movie nights.
(Well, admittedly I ripped my own discs / digitized my tapes and shared those files - but it worked really well!)
because the page I'm on thinks its called foobar.egg in my browser, but when it originally was emitted the server thought it was serving api.barbazz.egg but cloudflare rewrote that and the CORS headers are all wrong for that shit to work
and I tried VPNing to the same country as my friend so that we'd both in theory be on the same domain but noooo something is getting cached or geolocated wrong along the way so I'm still ending up on questionable domains that can't talk to the right server.
to fix this I'd need to set up a mitmproxy and rewrite some of the URLs to get the hostnames to match the headers and mitmproxy has a problem with big streaming content and this is a VIDEO SITE that BARELY LOADS IN THE FIRST PLACE
@foone I can smell the technical debt from here
@foone like that bit where you pry apart the plastic case of some broken electronic device and catch a glimpse of black soot, charred wires, and several stacked circuit boards before the plastic snaps shut pinching your fingers.