![](https://lemmy.keychat.org/pictrs/image/1f08ce6b-6c40-4066-b51c-7abb6cdc5ad6.jpeg)
![](https://sh.itjust.works/pictrs/image/045a2049-eb61-4960-88ba-97e7f1ffbf31.jpeg)
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.
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.
I wonder if you applied inflation from the time that idiom was first popularized what the modern price would be.
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.
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 I could drop 2024
No
You could hire a team of security experts to audit it for you
I love the concept. I hate many of the language design choices.
The demo was so fucking creepy. Would rather be in a dark room surrounded by victorian dolls that sometimes seem to turn their head towards you and blink.
I guess their advertising campaign wasn’t very effective!
It’s popcorn not salad dressing.
Not what I was expecting. “Diminishing” made me think that the new effect of the beacons would cover a larger area but diminish as distance to the building increases
I’ve been using it the last month. It’s autocomplete and does what autocomplete should. It doesn’t guess utterly insane shit like certain other tools.
Simple: make friends with someone with high speed internet who’s not very savvy, keep up the charade until they allow you to borrow their computer. Then you install a headless vpn server with logging disabled. Boom, high speed local VPN that doesn’t point to you. Just buy them a $2.50 beer once a month to keep up pretenses in case you need to do maintenance.
I just barely managed to cancel the update and apply hacks to prevent it completing. I
was one of the many people who got hit in the nostalgia from the show and decided to replay. Of course that meant grabbing a mod list which took a couple days to get downloaded and working. Then a couple days later they release an update that breaks all the mods. Would have been much better timing if they released the update ahead of the show so modders had time to fix things before the rush.
It’s in there
I’ve been meaning to finish the first one. Is there combat in that game? I just remember picking flowers for hours.
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.