Ginden

Now we have new ways to solve this problem: send Haiku or Luna to do task using computer use, but without access to code. If it can't complete it, or takes too long, docs are bad.

This requires keeping history if, at the time, Buckmaster's account had a certain flag set, because just because the account has the flag now doesn't mean it had the flag at a certain moment in the past. And even if they had such history, it's not obvious whether they just load all data as-is into training.

A totally reasonable pipeline may be unauditable for this purpose.

And, of course, you can train a model to start with repeating prompt in chain of thought!

My employer bought me a Claude Max subscription. On heavy weeks I use 80% of the subscription. And among software engineers that I know, I'm a relatively heavy user.

Why? Because in my experience, the bottleneck is in shareholders approving new features, not my ability to dish out code.

"Age-restriction laws push platforms toward intrusive verification systems that often directly conflict with modern data-privacy law" - when you make rules contradictory, someone always violate these laws, and you can use selective persecution to "convince" companies to favor you, the incumbent politician. You don't even have to use such power, just a "joke" may be enough to send have any rational CEO licking your shoes.

European proponents of "anti-big-tech action" make it pretty explicit - broad discretionary power should be given to executive branch, because otherwise "international corporations" will use "loopholes" (and these "loopholes" are, in practice, explicitly written laws used as intended).

You need only a device on network to spam DHCP messages with malware DNS. So you don't need "shady hotspot", only compromised device within network.

> easily solved

Asynchronous (you don't know when and where you will get Internet/local network connectivity) mesh (there is no gov infrastructure to be trusted) networking in presence of malicious (gov operated) and unreliable (destroyed by gov) nodes is probably among hardest problems known to computer science.

Mining in Arctic is a technical nightmare. Typical alloys become brittle in these temperatures, darkness severely limits operations and/or workplace accidents, transport requires ice-breakers, permafrost is fundamentally unstable (heat from buildings melts it, causing sinking), and you need to pay people a lot to work there.

There are multiple tech companies with quadrillion-deep pockets.

Because almost everyone involved in AI race grew up in "winner takes it all" environments, typical for software, and they try really hard to make it reality. This means your model should do everything to just take 90% of market share, or at least 90% of specific niche.

The problem is, they can't find the moat, despite searching very hard, whatever you bake into your AI, your competitors will be able to replicate in few months. This is why OpenAI is striking deal with Disney, because copyright provides such moat.

Oh, you mean specifically GPL v3 license, not any GPL license.

Yeah, broad tivoisation and patent clauses make it a problem, because making any patent litigation on unrelated grounds has potential to lose ability to ship the entire OS.

So what? Standalone binaries don't infect other things with copyleft anyway.

> given support to these fake public interest groups in attempts to sue wind projects out of existence.

Remember - that's the core issue. Development of housing or green energy projects or industries with low externalities should be by-right.

Electricity is not really an expensive resource for communications. You need like a single rooftop to provide WiFi for the entire village.

This is merely an engineering problem.

The hardest part of building nukes is acquiring weapon-grade enriched uranium, because it's controlled as hell and you will get bombed if you try to make your own.

If you spend hundreds of millions of dollars on enriched uranium, paying salaries for team of engineers is the easy part.

Conflict of interests is a real thing to worry about. I wouldn't trust scientist working in tobacco company on cigarette harm, even if I have no evidence of wrongdoing.

This, but unironically. Humans have the best daylight eyesight in mammals, and only birds of prey come close.

Asymmetric cryptography isn't a rocket science. Airline keeps encrypted recording and public key, certain government institution keeps private key, you need both to decrypt.

Title "People cough more during classical concerts" implies that people are more likely to cough during classical concerts than non-classical concerts. Article implies that people cough more in classical concerts than at home.

There are numerous biological, physical and neurological factors that can affect cough rate, and implication "it's voluntary" seems to be rather ridi... far-fetched.

Paper link BTW: https://ideas.repec.org/p/cue/wpaper/awp-05-2012.html

I was already running home server, so for me, setting up smart home was relatively simple:

- Buy Zigbee USB dongle - Install Home Assistant and Zigbee2MQTT in Docker on server - Initial configuration

It requires basic technical knowledge, but after initial configuration it just works.

There were three major pains:

- Configuring camera (ONVIF is pure pain) - it works initially, but I physically plug-in cameras only when I'm going on holiday - Configuring voice assistant - Finding good ZigBee remotes - Price of Hue Wall Switch (DIY approach is possible by gutting cheap button)

Cameras and voice assistant troubles were arguably result of my "keep as much as possible within local network" approach.

Minor pains:

- Binding remotes to light bulbs, so they work even if server is down - Finding instructions how to bind certain ZigBee accessories (they have "just open our proprietary app and it will explain what to do" manual)

Incremented serial numbers can leak things like eg. volume of sales in your shop.

> length prefixing is annoying when streaming

This can be avoided by magic number. If length is 0, then message length isn't known.

History as social science was basically invented between 19th and 20th century. Ancient writers generally had agenda and they happily filled missing pieces with ideologically-fueled speculation.

> Mentally I felt like I needed more food and more junk food than I ever did before using the drug

This is consistent with hungry brain hypothesis. Your hypothalamus detects that you have less body fat than amount set on "lipostat" and it tries to get fat content back to this set amount.

> If it was the case then insurers would already be adding the drugs to their formularies.

American healthcare system has perverse incentivizes. Most unhealthy groups are generally least likely to be privately insured, so insurers are incentivized to prioritize health issues affecting working-age adults, while neglecting those which will be someone's else concern in future.

> This is opposed to coming up with long term solutions that involve re-evaluating daily decisions that lead to some of these diseases in the first place.

Medicine tried this. It's extremely hard to actually to do it in practice. Obviously, it's better solution, but we are living in real world, where we have to choose "good enough" solutions over those deemed "better, but infeasible for 90% of patients".

> At that time, Gophers leaped to defend it, going so far as to say that it's better because it's simple.

I'm not sure why certain things generate such fanatical community.

Eg. I remember arguing with iOS developer in my first work that smartphones bigger than 4.7" are useful. He claimed they aren't and Apple, as company focused on best experience of user, will never ever produce bigger smartphone, because it's totally useless.

I think that inflation isn't exactly comparable over that large periods of time. No amount of money could buy computing power equivalent to smartphone in Dickensian times. Our expectations also rises - no one wants to live in Dickensian standard of living. ;)

Also, Cratchit wasn't doing minimum wage job - AFAIR he was accountant or someone like that.

Yes, it made me wary - design choice with different tradeoffs is portrayed as "better".

> these dev dependencies will never be pulled into your project,

Please, don't ruin "JS bad" thread with facts. It's rude.