Hacker Newsnew | past | comments | ask | show | jobs | submit | whs's commentslogin

In Thailand the first TP-Link distributor offered "lifetime forever" warranty. Even if it get lightning surge you can get a replacement. For that I believe they charged twice for the product. Many people think it was a really good deal for an unknown Chinese brand at the time.

Later on TP-Link themselves added more distributor and were not happy that they cannot dictate the pricing, and also the distributor did get undercut by the newer distributors who only offer standard warranty, so they part ways.

Even now almost 10 years after that they probably will honor my TP-Link warranty but I'll get a Totolink instead


Now I wonder when will people find how Carmack found 0x5F3759DF


It's the same thing. Seems like the major version bump is to advertise WSLc, which is like Apple containers - an SDK for launching Linux containers as part of a Windows app.


I guess windows containers where dead on arrival?


Windows Containers, owing to how NT itself is put together, are incredibly awkward to use. Container images have to go all the way down to smss.exe (the NT equivalent to init), which ties you to a particular kernel patch level.

Upgrade the container host? Re-bake your container images. It's a massive pain in the ass.


Yeah, I wasn't familiar with that (being all day working with Linux containers), and past week I found you cannot build images nor run Windows containers unless the host and the image match on the major Windows release. No backwards compatibility either.

So, for example, you cannot run a Windows 2019 container in a Windows 2025 host (nor the other way around). So, upgrading a base image means upgrading all the containers running in that host, and also the host itself.


Exactly, and there isn't really any backwards compatibility possible. Below csrss.exe on the stack, you really are wedded to a particular kernel patch level.

Linus found religion in a stable system call interface somewhere in the 2.4 series, and it's made the Linux container experience rather nice. Windows moves that particular kind of interface stability much, much further into userspace, and it makes the Windows Containers situation untenable.


Not dead on arrival, just extremely expensive on arrival for commercial/production use-cases, unless you're using Windows Containers on Azure.

They're missing things like winget as well, but that's mostly an inconvenience rather than a blocker.


Not dead, but they are ridiculously buggy. Much like WSL.


I wonder if API is affected by this issue, especially Claude on public clouds? Would that means the subsidized rate just means they use cheaper quantized models and it's not comparable to API spending.


I've always used Enterprise per-token billing for Claude Code and I've never understood these nerf complaints. I've never noticed any slow downs at certain times of day, or a gradual decline in quality.


There’s probably contractual guarantees in the enterprise plans. My understanding of the subscriptions is they can swap the models out if any of them is getting too heavily loaded for a period of time


Open AI aims to have a stable API and admits to meddling with effort levels and such for subscriptions here: https://news.ycombinator.com/item?id=49804316#49809266


I’m also often not affected by Claude outages on the API; but Claude.ai is down.


Tell that to AWS Lambda and Google Compute Engine?


Seems clear from their website?

1. Their API server provide an attestation JWT. This JWT is signed by Google's private key. 2. The attestation has details on the running container. I suppose the container host is a Google-provided distro and Google's signer will verify that the OS is theirs and up-to-date. 3. They could've proxy the attestation. To prove this is not the case, the field eat_nonce include the TLS certificate fingerprint, which should match the API server you're connecting to. I suppose you will need to pull their container and verify from the source that the container itself generate the private key, it never leaves the container, and the container has no way to run arbitrary code such as SSH or vulnerabilities.


I had one.

The only two reasons it was worth it is my company paid for it, and you can get a lounge space and some swag at reinvent. I never get to use it professionally


I've been looking for similar distributed computing style LLM, and I found AI Horde and a few other smaller efforts like one from Aphrodite people and distributed training from Nous Research.

AI Horde seems to be the biggest of them all. Their API speaks KoboldCPP text completion (not even chat completion). It seems that the community (or at least the active people) strongly prefer it this way because the API exposes more tunables than chat completions, which for roleplay use seems to result in better result. I don't know what else you can use AI Horde for anyway since all other use cases likely will require tool use. Just this week I was set out to improve their OpenAI bridge to support chat templates and response parsing. We'll see if I could get it deployed officially then you might be able to use it to code, although you'll have to use RP models.

I think Horde do have a lot more abuse prevention. Workers needs to have 1 week of cumulative uptime to be considered trusted to prevent brigading - users can opt into trusted workers only. Running a worker give you kudos which is required for >512 max tokens generations and also free requests get bumped to last.


I wonder how security is done in this engine, since it's accepting input from anyone. llama.cpp's RPC layer seems to says that you shouldn't run it in public (I assume because it is lower level and may result in RCE on your GPU)


Sounds like the same problem as condom. Nobody want to buy the "mini" size.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: