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.

So what printer should I be looking for when I rob graves?

I got one of those desks with a vertical pneumatic lift so I can stack the computers vertically in a rack and just raise/lower it so the right one is at eye height

FTS? fuck that

I wonder if you applied inflation from the time that idiom was first popularized what the modern price would be.

MAAAN would be a much better acronym though

That’s when you update your sig with your address and a link to a local delivery venue

Alternatively all 504 Gateway Timeout

deleted by creator

That joke was constant in the early 00s.

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.

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 was not expecting that. Trump continues to shock.

No

Wasabi Pea no peeing inside!

You could hire a team of security experts to audit it for you

Carefully timed explosives placed in the middle of the moon causing it to split in half, one half going away from Earth and the other half going right into the Atlantic coast. Problem solved.

I love the concept. I hate many of the language design choices.