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.
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.
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.
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.
8 hasn’t been getting the essential security updates since march 2022.
That’s not really true despite what Oracle claims. Even without dropping money for Oracle’s 2030 support, there’s been 9 releases to OpenJDK 8 so far in 2024. Amazon has guaranteed OpenJDK 8 LTS through 2026 as “corretto” for justifying it to corporate compliance teams.
Everyone really should upgrade but it’s going to be several years yet before it’s an actual security risk.
Remove the quotation marks and the first result is https://kottke.org/19/05/grace-hopper-explains-a-nanosecond
More accurate is “electricity has a speed limit”
Where can I get a prescription for this “poverty”?
There were several years when it would be the top result whenever you searched for a tech problem. Back then usenet was already largely dead, was more about mailing lists and IRC if you couldn’t find a blog or forum post that covered the issue.
Enjoy installing fake dependencies squatted by malware
The industry has too long neglected the true threat posed to information security by the platypi.
The manual talks about some of the older alternatives that influenced it. Doesn’t directly compare them though https://difftastic.wilfred.me.uk/tree_diffing.html
They mention that in the first paragraph and repeatedly through the announcement. How does that mean they’re not really sunsetting the original product?
A lot of the classic “pastebin”-type solutions get overrun by phishers and other scammers if they don’t require registration.
Seems kinda trash tbh. Like the concept I love, I would love a cross-language “by examples” learning resource and snippet repository beyond SO. But looking through there most of the function options are trivial problems. The ones that aren’t one or two lines mostly have broken code that passes very few tests. The weird Z naming of function and variable makes it totally unreadable. The “composition” option is barely comprehendable and beyond that I only see two language options so it can’t even serve as a “rosetta stone”.