The arguments are pretty broad, and it does seem the author worked back from a conclusion toward proof which in statistics doesn't work.

Being interested in decentralized currency and being a libertarian are essentially a Venn diagram that's a perfect circle. There were numerous other examples where the author would have concluded the average late 90s Slashdotter created Bitcoin because that was just your average neckbeard from the era, nothing unique to Satoshi. I was ready to just write off the whole article based on this extremely flimsy correlation.

The writing analysis comes down to a fundamental flaw. They chose a number of idiosyncrasies and then judged all candidates on those idiosyncrasies using the AI. But we don't know that those are the only idiosyncrasies of writing. Maybe only 1 author wrote both "email" and "e-mail" but maybe 1 other author only commonly misused "analogy" vs "metaphor" but since that person wasn't Back, they were ignored.

However , that all being said in defense of sloppy research. I can say with 100% confidence that a Giant Fucking Nerd that spends months, years and endless nights on a message board or mailing list don't usually just disappear. They especially don't just disappear at the exact moment that their biggest passion project suddenly finally heats up and gets popular. They got him dead to rights it's him. I need no more convinced.

If I'm a giant fucking e-currency nerd, I've created my own proof of work currency in the past (one of only a handful of people) and discussed/debated/thought about e-currencies like mine... and then suddenly someone finally actually starts on a viable implementation that's actually attracting a lot of attention... I would need welfare checks to make sure I wasn't dead because I would be following it so obsessively. Black even mentions that this happened while he was writing his dissertation with PGP... and he didn't even contribute to PGP. But we're supposed to believe that something as important (or more) that aligns with your politics and builds on your own work--going so far as to cite it as an inspiration... just isn't interesting enough for you to bother discussing?! Yeah lol no.

Y2Claude

And yes they posted at least one example:

https://ftp.openbsd.org/pub/Op...

Wasn't there an 80186? That literally nobody built anything with? Like, it was almost a proof of concept?

Just today I noted that GIMP 3.2.2 (an application, not an OS) has dropped support for 32-bit x86.

What's more, you really have to know what you're doing to coax it into re-using code, rather than rewriting the same functionality with each prompt.

Yeah well, we can't all be a person who doesn't understand how things work. Kudos to you for being simple minded!

" The Kathmandu Post"

Ah we don't to pay for journalism, says a planet of suckers

Isolate should be capitalized as Cloudflareâ Isolate©. They're probably running out of synonyms for Sandbox, Container, Jail, Cage, Cell, Vault, Pod, etc... And has the side effect of also being an homage to oldschool Science Fiction (Isaac Asimov The Foundation which probably has the word "Isolate" as a noun used more per page than any non-scientific book in history).

Oh, that's pretty neat. Microsoft is definitely the right level to address this at - they already have permission to enumerate the HW, own the hardware and software infra to tackle this, enjoy economy of scale other players are not privvy too, and can deliver a solution in a vendor agnostic way. Thanks for the heads up. It's the right thing to happen.

Of course there are. Tragedy of the commons. My point is that no single entity is likely to absorb the costs unless they're already enjoying economy of scale advantages and there are business experience/optic benefits to doing so. The poster above you pointed out that Microsoft seems to be addressing this, which makes a lot more sense to me than doing it at the 3d HW vendor level.

Sure, but many people would opt in, especially if you explained that they would benefit.

Maybe. Maybe not. Before committing to developing such a thing, you'd have to at least do some research and analysis to find out if that's true and how the likely opt in/out ratios would impact the business case. Remember, this is hosting content in a daemon on your machine .. I think that'd a non-starter for a lot of people, despite the upside of shorter shader updates. (I'm not super up on what the US ISP market/landscape is like these days, but are not data caps still a thing on many plans there? I get the sense that hosting off a home line is not only a performance concern but a concern with actual possible financial ramifications.)

It can't be only when the game is open - this is when gamers are most sensitive to their computers doing other work, and the available of such a network would be far more limited.

Also a torrent like network would be absolute loaded with cache misses. You need to fetch a shader from somebody who has the exact same hardware/drive/game version combination as you do, and they need to have opted in. I highly suspect the majority case for many would be to cache miss and end up compiling locally.

Asking people to host and serve a non-trivial amount of content to other players is a non-starter. (The size of compiling all the shaders for CoD can range from a couple gigs to 10 gigs.) Opting in to a torrent-like network would have to be opt in - many people would just opt out (justifiably or not) minimizing the point of such a network.

You can probably assume that if you've thought of something, they've thought of it too. They simply have constraints and considerations - both technical and business oriented - you don't need or want to account for.

It's worth noting that many game studios/engines do support shared shader caches in their local studio pipelines, but the hardware config spread is much more limited, and the costs for lost productivity waiting for shaders is far greater than hosting a shader cache on premises.

Yes, this. There are many *many* combinations. Distributed compilation and a remotely hosted shader cache would cost a lot of money to host. I don't think it's the technical considerations that are as preventative as simply the cost of hosting the service.