#jortage — Public Fediverse posts

#jortage — downtime was caused by some form of memory leak, and lasted longer than it should have due to sleeping and a proxmox issue related to the cluster filesystem getting stuck preventing me from rebooting the container

#Jortage — we're back

#Jortage — Hypervisor going down for routine updates.

#Jortage — we now have scraper detection and blocking. If you get a noisy blue image with barely-legible red text on it and are not an AI scraper, please let me know and include details about your request (browser version / etc)

#jortage — The hypervisor suddenly rebooted for no obvious reason at 7:55 EDT. The disk is encrypted, so reboots require manual intervention. I was asleep, as usual. No information in any logs.

#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.

#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

#jortage

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/

#csp #jortage #mastodon

reminder: the #Jortage Rivet protocol is real and implemented in poolmgr right now, there's just nothing that speaks it

#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.

Endlessly grateful to #Fastly for providing free CDN service to #Jortage

Hey...
what happens to images uploaded to #jortage or rather Wet-Dry World, that get removed from a post.

Are the images deleted after a certain amount of time? Or do they persist forever?

#MastoAdmin

If you use #Jortage and you upgraded to Mastodon v4.3.0, your multimedia could stop working, because of this commit: https://github.com/mastodon/mastodon/commit/a496aeabcb28b7cc7d8a9e69bf47543c2be038c2

The redirection from pool-api.jortage.com to blob.jortage.com messes things up.

So, if you need a solution (at least for now):
1. replace "app/lib/content_security_policy.rb" with Glitchsoc's
2. add:
EXTRA_DATA_HOSTS=https://blob.jortage.com
to your .env.production
3. restart mastodon processes

(At least that worked for me)

Cheers!

#Jortage is a shared media hosting that a lot of different mastodon instances rely on. It's maintained by a single person paying a substantial amount out of pocket.

I make a small donation every month to help them cover the bills. Look at any image url in your instance's web UI. If you see jortage in there then consider becoming a supporter too!

https://sleeping.town/@unascribed/111818772892716334

@unascribed hi Una! I just learnt about #Jortage thanks to this post which was boosted.

I suggest you add the link to the website of the project in such toots, so people like me have an easier time getting to know what it’s about. 🙂

I'm super excited to share a conversation I had recently with #FastForward program member @unascribed.

Una is the creator of #Jortage, a communal storage pool for #Fediverse instances. The project helps admins here on #Mastodon and beyond keep costs down by pooling resources and de-duplicating content storage across the 70+ #instances that use it.

So let's get into it: https://dev.to/fastly/community-spotlight-una-thompson-is-making-the-fediverse-more-manageable-with-jortage-34gk

@david I'm sure you're getting way too many suggestions (and might already be aware of these suggestions), but you might want to look at #Jortage (https://jortage.com). They're running a communal deduplicated pool of storage for different Mastodon instances and Fastly is providing free bandwidth.

Other thoughts:

It looks like you're using Storj at a list price of $4/TB and bandwidth at $7/TB. Backblaze's B2 is $5/TB for storage and Bunny.net offers $5/TB CDN (with free egress from Backblaze to Bunny.net). Backblaze does have some request costs, but they should be minimal with Bunny.net caching things.

There's also Cloudflare's R2 which has no bandwidth costs and is $0.36 per million reads. If your average image size is above 76KB, Cloudflare's R2 is cheaper than $5/TB. R2 does cost $15/TB for storage, though (but bandwidth might be more an issue). I also understand if you want to avoid CF.

I've heard good things about Fastly helping people out with bandwidth if you get in touch.

jortage is a communal cloud designed for #fediverse instances.

Content duplication across instances is an expected behavior, but it can mean high costs for admins. Jortage helps solve this by deduplicating content for members. Their #storage pool is currently storing 13.40TiB across 60.35 million objects — without deduplication, it would be storing 27.02TiB across 123.37 million objects.

Today, we welcome #jortage to #FastForward ⏩

https://jortage.com/ #instance #hosting #admin

Apparently #Jortage is doing some kind of migration on their service, so images are sometimes coming through with a bad cert, which in turn causes them to show up blank on the web. Hopefully this will resolve itself soon...

#TootCat @news

@poag it's a good question, and I honestly don't know the underlying reason why. However, I did run across #jortage yesterday which is trying to solve essentially that problem: https://jortage.com/

I haven't really been paying attention to the #Jortage statistics, but (perhaps unsurprisingly), our usage increased 5.6× in November compared to October and September — from 16M requests to 90M.

Didn't even notice, which I suppose is a testament to how the Storage Pool is constructed. If anything, Jortage has felt faster the past month — media uploads have been quite snappy.

#mastoAdmin

https://jortage.com/ takes the "duplicate every image across every fedi server" model and deduplicates as possible at the media storage level

self-hosting an instance and outsourcing media storage has been for me a nice balance

i just upped my contribution a bit

thought you should all know about #jortage

New #Jortage service

Inspired by the fact my site is getting absolutely hammered by remote requests as a result of a popular post I've made, I've created a new service — https://jort.link

It's a URL redirector shield for posting links on the fediverse — fedi software receives a cached page copy, and normal browsers/etc receive a redirect.

@woozle Gah!!!

This one's my fault.

I just checked my uMatrix settings. I hadn't permitted "media" for "jortage.com".

Toggled that, saved the config. All's now good.

If anyone else runs into this issue, point them to this thread.

#TootCat #uMatrix #Jortage.Com