Embed Notice

@kaia@brotka.st since nobody would be dumb enough to call their company that. 💀

So my experience is a little limited but know this is an issue I ran into with sharkey but from what I understand it is a security feature on the browser level if the webserver/reverse proxy does explicitly not signify that subdomain as trusted

Even though my files are files.oshi.social and my instance is oshi.social it was failing a CORS origin request for my instance icon

The PROPER solution was to add the subdomain into my headers to authorize that subdomain

The lazy solution I went with was using my primary instance URL to proxy the image on the subdomain lol

I hope I am close enough to the correct answer here, but again still new