It can only accommodate 58ft wide ships but it can accomodate a 74 ft wide ship?
It can only accommodate 58ft wide ships but it can accomodate a 74 ft wide ship?
Because it makes my pee taste funny
The worst is when they just won’t leave afterwards. So clingy.
Who’s melroy?
Yeajulothiissithmadpoijuloiwimovlinmiany
I don’t get it
Oh wow I didn’t realize nearly any of that detail about the current system. That explains why my fluid systems would always be unbalanced crap and sometimes require inexplicable pumps be added.
FTS? fuck that
I wonder if you applied inflation from the time that idiom was first popularized what the modern price would be.
NAAAAAaaaants ingonyamaaaaaa bagithi Babaaa
deleted by creator
No, pipes don’t really store it unless they’re blocked a long time and even then they don’t hold much. They facilitate the pee’s transfer to your cat in a child
Sunburnt Clitoris. Sounds itchy.
They probably have a bunch of 1 hour ‘books’ that mess with the average as shorter is cheaper to help pad out their numbers.
Looking at my personal library, the median length audiobook is The Last Wish at a tad over 10 hours. So it’d be equal to 1.5 books going by that, not the worst marketing exaggeration I’ve ever seen.
Oh wow that looks fucking awesome. Major Legends & Lattes vibes but with a dark undercurrent.
You could say finding the Trans Server is their TransMission
Data size and user expectations is the main difference. It’s possible but there’d be a lot of latency and overhead for just scrolling down a page with a bunch of images. Maybe there’s fancy stuff you could do by batching images together and reusing connection pools but it feels sisyphean.
Mastodon and lemmy handle this in slightly different ways. Mastodon (according to the link) replicates media on every instance while lemmy (mostly) only replicates thumbnails. That means a popular post doesn’t cause load for one server on mastodon but does on lemmy. But Mastodon has a higher aggregate cost due to all the replicated data, which is what the linked proposal solves by making it sublinear.
If the torrent is instance to instance I don’t see any real benefit (and instance to client is infeasible). On Mastodon side you still have data duplication driving storage costs and bandwidth usage regardless of whether it’s delivered via direct http or torrent. On the lemmy side it wouldn’t gain much (asymmetric load is based on subscription count and so not very bursty) but would add a lot of non-determinism and complexity to the already fragile federation process.
Conventional solutions like cache/CDN/Object Storage or switching to a shared hosting solution (decoupled from instances like your link proposes) seems like a more feasible way to address things.
I wish it were real. Pepsi-milk just doesn’t hit the same.
I’d usually do the former because by build number I usually mean pipeline or job id in a build server. You could build 4.0.4 and then 3.4.18 and so 4.0.4 could be build number 1026 while 3.4.18 is 1027.
You can also just use a special number to keep your version number unique when doing dev builds so your version number comes through like 3.5.2-48 and some might call the 48 a build number, in which case that would make sense to reset with each version number.