teravor

for a standalone project that's fine, but when the project's entire purpose is to track and be an adversary to another project...

the problem is that to someone who can't maintain (realistically, get an LLM to do it without running into refusals) this project on their own, any time they spend utilizing it will end up a waste of time.

the actual value comes from having a solution which tracks cloudflare, a full LLM pipeline for pulling the most recent obfuscated code, reversing it and updating the current solver. without it, users aren't going to have confidence in the continuity of the solver to build around it.

that said, most of the people who really need it roll their own in-house. don't think I have seen someone post it to github yet.

that's exactly the point. a human didn't have the intent.

it's called a cache covert channel and there is a lot of literature and code on the subject.

doesn't it require intent? so how exactly are the feds going to proceed when the LLM takes the initiative and helpfully confesses to it in the logs?

it's possible commercial routers such as the ones utilized by restaurants allow wireguard through these days? wireguard makes no effort to be stealthy when emitting.

some VPN apps bypass wireguard blocks automatically by using https tunnels and whatnot.

something about solar I don't understand is even if you crack energy storage for nighttime, what do you do about the tail risks? There are overcast days, sometimes it lasts for multiple days. you can have a volcano eruption or wild fires that have the same effect on solar cells.

would it really be acceptable to have power outages during such events? is it reasonable to have gas plants on standby for just this? if so, you must add them to the cost of solar.

if you are willing to put in the work you can devise a hyper specialization for which you can create an RL playground (which is likely absent in the frontier labs), then you can obtain cutting edge results on it by post training an open weights model using minimal resources.

talk =/= worry

only people who are directly impacted by an aspect of automation worry about it, everyone else either doesn't care or is quite happy even as they talk about how bad it is.

the military has conducted studies where submariners were exposed to a PPM of 1000s with no ill effect. I suppose they were trying to determine how hard they need to scrub.

having said that, it's possible they omitted what other gasses and %s they used for advantage. there could be some mitigation possible there.

CO2 by itself doesn't appear to be a problem until some truly absurd levels are somehow achieved.

CO2 is usually a proxy for air quality because outside is usually something consistent like 400 therefore deviation from that figure indicates staleness.

iirc there is actually very little to none double blind study into most dentistry.

domain binding requires browser participation.

you can have a TOTP variant which has the browser display a challenge string & QR code, authenticator generates a 5-6 digit response. include more entropy in the response if you want to do away with the password entirely.

passkeys are trash, I would never opt for dedicated hardware (or a cloud service) and using them with a password manager is extremely messy when you want the password manager to be properly isolated from the rest of your system.

by buying a mass produced generalist device (preferably from a randomly chosen vendor) and then restricting it to a specialized purpose you are effectively negating a targeted attack.

I always assumed the people buying those crypto gadgets were idiots.

also, if Apple falls to a supply chain attack like this where their laptops are backdoored crypto theft will be problem number #10.