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

Also, "ssh -A" is your friend. Keep your ssh key on your yubikey where you control it. Let Claude play on it's own VM and in its own clone of your repo. Only when you choose to add the -A, do you temporarily, for that one ssh connection, have the possibility to push Claude's work to your repo, where you can review it.

Treat it as a colleague, making PRs that you review.


Soundtrack for this post: https://youtu.be/3qF95ANVHSg

Kursk, by The Vad Vuc


This is about urban Switzerland. Way out in the country, we still have crap copper up on poles, which maxes out at 25 Mbits.

But yes, Swisscom (owners if the old crap copper) do have to let the competitors use it.


Yes, that is sadly still the case but the expansion of the fiber build out is now rapidly moving forward. By 2030 +90% will have fiber

https://www.swisscom.ch/en/about/news/2024/02/08-weniger-kup...


That's actually terrible. The UK (which has been a laggard in FTTH in Europe until very recently) is at 84% FTTH coverage already.

Swisscom has to do better, as regulated by the government. One can get 80/8 Mbit/s for CHF 65/month: https://www.swisscom.ch/en/residential/landline-subscription...

> 80/8 Mbit/s for CHF 65/month

This is a terrible value, and good luck uploading anything at 8Mbps...


Currently also have copper and Sunrise cable. Just got the cables to the house two weeks ago. I’m now waiting for the local electricity company to get in-house installation. Everything at no costs. So yes, it’s progressing fast.

When I watch how little influence I have on my children from my spoken advice, and recall how many lessons people tried to teach me which I had to learn myself, I laugh at the eternal pointlessness of writing like this.

Carry on, world, carry on.


I don't want to pile on this poor guy, but video conferencing software in browser works, and does not require software installation.

Use the browser sandbox to protect yourself.


...which is exactly the same way backdoored Cisco hardware got to China.

It's a big if because the threat model normally includes "bad guys can forge messages". Which means that the input is untrusted and you want to generate your own domain separation bytes for the hash function, not let your attacker choose them.

It is definitely not transmitted.

Domain separation happens in the input to the hash function, not on the wire. Because what arrives off the wire is UNTRUSTED input.


This is a nice explanation of an obvious idea. Both domain separation, and putting the domain signifier into the IDL are fine, but not novel.

Crypto is hard. Do it right. Get help from your tools. 'Nuff said.

Jeeze, I'm getting too old for this crap.


Bring back John Insprucker.

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

Search: