markasoftware

Residential proxies operated by "legitimate" providers can only open TCP connections, which more or less rules out DDoS attacks, which seem to be the most common use of botnets. (And all tcp connections typically have to go through the proxy providers datacenter first to get through NAT, which effectively limits the total amount of traffic/connections you can make)

have only tested a few prompts, but it failed my favorite non-coding question that dsv4 flash aces. Benchmarks look excellent though (don't they always!)

Read the exploitgym docs. It's not a "find the flag, it's somewhere.". Its a "here's some vulnerable source code and an input that triggers a crash; turn it into a full exploit." It also verifies at the end, using another agent, that the hacking agent actually used the intended vulnerability.

So going to find the Vulnerability's description on a third party website is clear cut reward hacking

I believe the only way people start taking x-risk seriously is a major real world scare which is short of global catastrophe. Like Chernobyl. This ain't it yet, but it raises my hopes that such a scare will occur before its too late.

playing devil's advocate a little bit, but wikipedia does have a policy against original research. If you published an obviously correct counterexample to wikipedia which is not anywhere else on the internet (or in a book, etc), the rules are clear: the counterexample must be removed.

in this case it's not original research, because there's a tweet by someone with a good reputation, and plenty of comments on said tweet corroborating the result. But it's a more sketchy "secondary source" than most wikipedia references and some caution on the part of the editors is not out of place.

(saying this as the person who made the original edit to the wikipedia page adding the counterexample)

I almost felt bad adding {{Cite tweet ...}} to the wikipedia article

[Deleted]

Heat dissipation isn't as big a concern as it seems: the weight of the solar panels is significantly larger than that of the heatsinks you'd need per typical modern gpu

nitpicking and beating a dead horse, but it was never going to be open source, at best open weight.

Right now, if you search https://www.google.com/search?q=kimi+k3+open+weight the blurb under the quickstart page contains the removed text.

They've removed the paragraph about releasing model weights.

does it matter as long as yt-dlp is maintained?

gdi, we need a GNU project for the llm era

Really glad to see an harness other than Pi that seems to be non-vc-backed FOSS and by a competent maintainer

Edit: seems like the remote connection feature may not work...

Yep, OP should certainly retest under gnome. Im not in the weeds myself but I get the vibe that gnome's wayland compositor is somewhat faster and more carefully designed than kwin (at least, Emacs in pgtk mode does substantially better under gnome, whereas on Kwin it uses substantial cpu when scrolling and even lags a bit at high resolutions)

Its serverHold which means the .me registry took this action, not the registrar (GoDaddy).

Runpod, digital ocean's gpu cloud, and at least a few others use Linux containers for isolation between tenants (look at Wiz's blog post about the nvidia container toolkit bug; digitalocean just puts everyone in a massive k8s cluster)

the vast majority of the target audience of this blog post would only consider moving to SF because of the tech scene. This isn't a mountain biking or asian food blog.

Pi does this by default. Since the frontier lab agents are vibe coded you really should sandbox any agent you run period.

"The freedom to run the program as you wish, for any purpose (freedom 0)."

Bazel maintains a system-wide cache that fixes this. At $current_employer a truly cold build (rm - rf the system cache) is 10 minutes or so. In a new worktree with a warm system cache it's under 60 seconds (still needs to build the worktree specific analysis cache). A fully warmed build is 10 seconds. Additionally there's no lock on that system wide build cache.

For this reason alone I want to like Bazel. But at the same time it has like half a dozen caches for different purposes and doesn't feel generally elegant. It saddens me that (a) cargo can't do this afaik and (b) its hard to package Bazel packages under nix. I'm not sure what other system has a shared unlocked cache.

Wtf do you mean by story? Performance and price are all people care about

Why is no other inference provider offering similar prices then?

Multiple providers (who need to make a profit) offer the same 4.40 rate for glm-5.2. It's not subsidized.

Deepseek's 0.86 or whatever is likely subsidized but alternate providers offer it for a price comparable to glm-5.2.

I have friends who have had serious permanent vision changes as a result of taking a reasonable dose of psychedelics one time (which is one of the main reasons I haven't tried it). If you overdose on either lsd or alcohol you'll have serious ill effects.

At the same time, using LSD once is higher risk than one night of drinking.

Very true, this was likely an attack. Worth noting that mr kettle has done a defcon talk nearly every year on some variant of this attack, the most recent one titled "HTTP/1.1 must die" because he rightfully believes that switching to the binary headers of http/2 (specifically in reverse proxy connections to upstream servers) is the only way to systematically prevent these.

FWIW I had this issue even with the MDB_NOSYNC flag so it shouldnt be force flushing to disk unless I'm out of ram or whatever

Not amazing. In certain workloads I ran, once the db reached several hundred gb, writes would hang for longer and longer periods of time, eventually hours, while the db grew drastically in the background. https://news.ycombinator.com/item?id=30023623 seems to be the same issue, and it was serious enough that Shopify decided not to use lmdb.

And yes, I ensured there were no outstanding long lived readers, verified with mdb_stat -r. My workload used one transaction per read/write anyway (never needed larger atomicity). Once the db got into the bad state, running my program on it would almost immediately run into the issue again, so I really think the db is in a bad state such that most writes would cause it to hang, not related to how I do transactions. This workload would pretty consistently hit the issue once the db got to several hundred gb.

Issue #10236 on the OpenLDAP bug tracker might be the root cause, who knows. It's been marked CONFIRMED for years without a fix, while other similar issues are created.

This is extremely annoying. It seems workload dependent (other workloads I've run create absolutely massive lmdb dbs without this issue) and once it happens your only recourse is to make a new db and copy the contents over (thankfully reads still work fine on these borked dbs).

Other than that, though, it's great. Never in any case had actual data corruption, and reads and writes are extremely fast (until this issue happens)

Edit: fun fact, since shopify may have created Bolt in response to this bug, and then Bolt was the root cause of the 73-hour Roblox downtime in 2021, this bug may indirectly have caused one of the worst outages ever!

Nym is pretty complicated and although they offer some kind of traditional VPN service as well IIRC, their main product is actually the only large scale operational "mixnet", which you can think of as kinda similar to Tor but a lot more resistant to certain types of deanonymization attacks (specifically it's designed to be safe against passive global adversaries, ie an attacker who can monitor every packet on the internet, though with the default settings at least it's not quite there yet: https://petsymposium.org/popets/2026/popets-2026-0055.php).

The research behind the mixnet is quite legit (look up Loopix). There's cryptocurrency involved because they're trying to do this whole complicated thing to incentivize people to operate nodes in the mixnet (though who are we kidding, the real reason is to make money). One can argue this is good for the long term sustainability of the network, and helps prevent sybil attacks by encouraging a large number of legitimate nodes. Of course, the downside is that the company is trying to make money, not just make the best mixnet possible. Having a profit motive also means they're incentivized to get the network to a point where interactive usage works well even at the price of anonymity (an optimization in this vein is sorta the reason that the paper I linked above is possible).

But having a working mixnet at all is extremely cool. People have been researching mixnets for decades without producing anything practical. While Nym is by far the most deployed / most ready mixnet rn, there thankfully are other options coming up, like https://katzenpost.network/ (though I believe most of the devs behind Katzenpost are also in some VC-funded situation, they certainly at least are trying to position katzenpost as more of a community driven project).