the8472

30 ms·

601.
by the8472 3y ago
Predicting the next word is hard. To do this more efficiently than a dumb lookup table (the chinese room thought experiment) or a markov chain you basically need to build a world model. This model sits in the deeper layers of the LLMs (the
602.
by the8472 3y ago
They won't have any. We already have footage from similar interventions from 2026 https://twitter.com/PatrickJBlum/status/1706354581989626323
603.
by the8472 3y ago
linux has pressure stall information[0] which tracks the time where some processes couldn't be run because they were waiting for contended resources (cpu/io/memory). An N-parallel compute-bound job on an M-thread CPU will sta
604.
by the8472 3y ago
I don't see what that has anything to do with unix or stdio? The read/write syscalls will happily transfer much larger buffers. If an application invokes the syscalls directly with 1-byte chunks it's on the application. users
605.
by the8472 3y ago
TCP can coalesce acks for multiple packets, can't SCTP do the same?
606.
by the8472 3y ago
> But why bother with UDP? Why can’t you do this with a TCP connection? Just measure the time deltas and throttle yourself if it spikes, right? Good question, and I don’t have a good answer. Perhaps one of you can give a persuasive one,
607.
by the8472 3y ago
> Rejecting a valid packet because the order got shuffled is wasteful, This is not what happens. The data isn't dropped as long as there are only a few reordered segments. And with SACK the receiver can also acknowledge them. It&#x2
608.
by the8472 3y ago
The issue isn't that this behavior is the default. The issue is that there isn't a portable way to also duplicate the file description. One has to open() the file multiple times or use platfom-specific things such as procfs.
609.
by the8472 3y ago
The question is also whether those cloud providers are much better proportionally. They may put somewhat more effort into security but they're also a much bigger target. Then there also is the question of cascading effects. E.g. if som
610.
by the8472 3y ago
Everyone using a one of a few cloud providers means lots of golden eggs in very big baskets. Sure, everyone deploying things on-prem will mean attackers will focus on the software instead of the cloud vendor. But that's A∨B vs. only B.
611.
by the8472 3y ago
secure boot + virtualized memory encryption is supposed to prevent that, you'll have to trust intel/amd though.
612.
by the8472 3y ago
Depends on your processes. Digital ones should handle them fine. In person you could use those good old business cards (each card now with its own number!). Over a phone call... well, the other side should already have that number on the ph
613.
by the8472 3y ago
If it were structured in fashion closer along the protocol startup process or how a real client is structured more people might end up with a functional client rather than a "bittorrent leecher". Up to "peer handshake" m
614.
by the8472 3y ago
5 years ago you could have bought a Zen2 threadripper (non-pro).
615.
by the8472 3y ago
You can use them for servers, but they're meant for workstations with resource-hungry applications. There even are companies that make a threadripper-box-with-a-handle-and-wheels when you need that oomph to be deployable to locations.
616.
by the8472 3y ago
Nice! In that case yeah, price is another differentiator.
617.
by the8472 3y ago
Bittorrent is most useful as a long-running application or background service to make data available. To get any use out of it in short-running contexts (e.g. updaters) you need lots of machines jumping on the content simultanously.
618.
by the8472 3y ago
If they actually paid in advance for the whole production run for those months how is that any different compared to the product being released but shelves being empty?
619.
by the8472 3y ago
Higher boost clocks. And the cheap EPYCs are single-socket too. The real issue is that there are no non-Pro threadrippers anymore. Those were even cheaper.
620.
by the8472 3y ago
Oddly the uploading part is missing. To be a peer, an equal, things have to flow both ways. Bittorrent wouldn't work otherwise.
621.
by the8472 3y ago
It's a mix of many different things. At work we have very beefy workstations that just aren't available in those hardware specs from cloud vendors. They use workstation grade hardware (A6000 GPU, threadrippers) that offer better p
622.
by the8472 3y ago
have another one: replace short phone numbers with ipv6 addresses. prefix owned by telco, customers can generate random suffixes. hand out random numbers every time you need to provide a number and delete them if you no longer need to recei
623.
by the8472 3y ago
Those samples don't look like 4k to me.
624.
by the8472 3y ago
It's not the law that's the problem (well, ok, it is perhaps poorly structured to even allow these things to happen...) but in the end it's malicious compliance of all those sites that put up the banners. The law doesn't
625.
by the8472 3y ago
Disabling a built-in, non-networked feature and then replacing it with a cloud-linked, self-updating 3rd-party one doesn't seem like it would improve security.
626.
by the8472 3y ago
JIRA already had attachments. Win+G, drag & drop
627.
by the8472 3y ago
> engineers will soon be able to visually log issues in Jira I already use windows game mode for screen captures. Why would I need a separate application for that?
628.
by the8472 3y ago
> since the division between attribute vs child doesn't match most in-memory data structures. vtables are attributes for pointers. hypergraphs (as used in some tagging systems) have attributes on everything, including attributes. CB
629.
by the8472 3y ago
> It’s not a competition. But it is in the context of the 3-way tradeoff we're talking about here. complexity of the site vs. load time vs. protocol complexity > You just need a few images. On the HTTP level those can be deferre
630.
by the8472 3y ago
Most businesses are not in a position to push through a new network protocol for the entire planet! So if we lived in a world with fewer monopolies then protocols might have evolved more incrementally. Though we'd presumably still have

More ›