#jortage — Jortage AU (another instance of the storage pool running entirely within Australia) has been decommissioned due to losing its initial sponsor and a lack of interest from others.
#jortage — Jortage AU (another instance of the storage pool running entirely within Australia) has been decommissioned due to losing its initial sponsor and a lack of interest from others.
#Jortage — The new geo-specific us.pool-api.jortage.com
domain has been broken, always resulting in signature failure 403s due to a configuration error. I've fixed this now, and the pool-api and us.pool-api subdomains both work as expected.
#jortage — I have begun the process of deleting the Backblaze bucket. (Doing it slightly early as every day I don't delete the bucket costs me $20)
#Jortage — all data has been successfully transferred from Backblaze B2 to Fastly Object Storage. I've shut off the fallback system, we are now solely serving from Fastly.
I will delete the Backblaze bucket in a week or so when I am confident everything's working good, which will reduce our expenses by $500/mo thanks to Fastly continuing to provide free service to Jortage via Fast Forward.
#Jortage — SVG files were being served with a bogus Content-Type due to a Fastly Object Storage limitation, which caused Firefox to refuse to display them. This was breaking some instance mascots and is now fixed.
long, Jortage expense report (June 2025)
#jortage local idiot forgot to test multipart upload
it's fixed now. sorry to all the instances that had stuck media upload tasks
#jortage — new uploads are now going to Fastly Object Storage. Migration of old files from B2 to Fastly is ongoing, so older files will be a little bit slower to load when not cached yet.
← can't afford a staging environment
sorry y'all
Mastodon upgraded from v4.2.20 to v4.3.8
Cherry-picked a patch from v4.4.0-beta.1 to fix CSP Error.
https://github.com/mastodon/mastodon/commit/803a8be998b9e00e76e593f7054f08a76fe4e53b
https://www.skrlet13.xyz/posts/mastodon-v430-jortage-en/
long, Jortage expense report (May 2025)
reminder: the #Jortage Rivet protocol is real and implemented in poolmgr right now, there's just nothing that speaks it
long, Jortage expense report (April 2025)
#Jortage — some images have been failing to load in certain contexts in Mastodon as of ~30 minutes ago, but would show up if opened in a new tab.
This is due to Backblaze B2 deploying some new harebrained nonsense that attempts to honor Sec-Fetch-Mode: no-cors
by returning bogus JSON payloads instead of the original file, when they falsely believe CORS is being violated. I've configured Fastly to hide this header from Backblaze to fix the issue.
#jortage — Due to a bug in our dependencies that was causing large files served directly by the poolmgr to time out (i.e. mastodon account exports), I have updated all of poolmgr's dependencies. This shouldn't have any behavior impacts, but may make the service faster. If stuff does break, please let me know.
#Jortage — Updates complete
#Jortage — All services will be going down shortly for a brief period. Just routine hypervisor updates, including a Linux kernel security update.
long, Jortage expense report (March 2025)
long, Jortage expense report (February 2025)