What would be the point? How would you prevent malware from being signed? Currently, code signatures are used as a signal for trustworthiness of the code.

Misplaced trustworthiness?

Has anyone figured out a good way to use (neo)vim with devcontainers?

haven't tried it but amitds1997/remote-nvim.nvim

I need something like that though that's one of the thing that pains me the most while trying to use vim/nvim for dev

And:

> their flight plan was not communicated in advance to the Italian air force general staff, nor had the American aircraft received authorization to land,

Sounds like they might have gotten authorization if they had just told them in advance.

Aren't their databases behemoths that satisfy requirements (especially of regulatory nature) of large banks and such? I don't think they have much in common with the needs of your run-of-the-mill startup.

> I don't think they have much in common with the needs of your run-of-the-mill startup.

that's right, Oracle's databases are for things like Visa and Mastercard transactions and maybe the US IRS and Social Security systems of record.

The Feynman method of solving problems puts a similar emphasis on writing:

1. Write down the problem

2. Think really hard

3. Write down the solution

It's a bit tongue-in-cheek, but there is also truth to it. Step 1 is not optional and actually very important.

What do you mean? By default, Claude asks for permission for every file read, every edit, every command. It gets exhausting, so many people run it with `--dangerously-skip-permissions`.

It does not ask for permission for every file read, only those outside the project and not explicitly allowed. You can bypass project edit permission requests with “allow edits”, no need for “dangerously skip permissions”. Bash commands are harder, but you can allow-list them up to a point.

> so many people run it with `--dangerously-skip-permissions`

It's on the people then, not the "agent". But why doesn't Claude come with a decent allow list, or at least remember what the user allows, so the spam is reduced?

You have the option to "always allow command `x.*`", but even then. The more control you hand over to these things, the more powerful and useful (and dangerous) they become. It's a real dilemma and yet to be solved.

You can write it as 10.1 though

You could, sure. You shouldn't, because not only is it nonstandard, roughly noone writes it that way.

Without consulting documentation or otherwise querying external memory, tell me what is 10.1.1?

A site-to-site VPN of two previously unrelated local networks is a pure gamble with IPv4. It would be almost straight forward with IPv6.

Yes but these days overlay networks are a way more common practice for that, with their own benefits (overlay IPs are always encrypted)

GPG keys are typically guarded much better than emails, that's the whole point. Accessing e-mails can be done by guessing a password, to get to the key you basically need command execution on the target's client system.

> When solar OVERproduces you have to literally pay someone to consume that energy,

Can't we just throttle the solar panel? In a worst case, you just pull the plug. It's not like a nuclear power plant which needs to be shut down carefully, or am I misunderstanding something?

Yes that's exactly how it works, it's called curtailment.

You can limit amount you feed back into network.

Not sure how is situation with home installations, factory i work for runs 150kw plant for our own consumption and don't bother with selling, but i know that we can set up how much we want/are allowed to feed back.

You don't have to use net metering in residential either. Grid-supported hybrid inverters that won't export power can be installed. Bonus is that they run when the grid is down. It's effectively like having an automatic transfer switch where the grid is the backup generator when your batteries are drained. The profit margin for the pro installers is reduced so they don't promote them, but it is a viable route to save money and avoid hassles with the power company on a self-install.