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


If it would be, then a fake explosion after start as climax before revealing it, would be quite a joke. Probably will yield mixed reception, though.

Erm no. If it goes a round and gets passed without spinning, the chances change of course. It is 1/6, 1/5, 1/4, 1/3, 1/2, .. 1

I didn't think of the gun getting passed around. To me, "one round" is pulling the trigger once after spinning the cylinder with one bullet. 1-in-6 chance of dying, you'll probably live. That's how I feel about this mission, I think they'll probably live, but man I'm nervous.

... 1/0

It is great to advance of what is humanly possible. Sending a robot? Great! Good data. If it dies, who cares, it does not live anyway. All abstract.

But sending a human? That feels more real. If we have the power to go alive to the moon, we also have the power to go even further. And we lost it, now we are reclaiming it.

And it doesn't matter to me what I think of the US government - this is progress for all of humanity. Also the comment section on the youtube stream is interesting - lot's of different flags are posted, sending good wishes from all around the world, low effort comments otherwise of course, but largely positive. (Very rare I think)

So, more rockets into space please and less on earth.


Is that a real fact?

(I misremembered it slightly, so sue me)

From "Apollo The Race to the Moon" pg 102:

The joke that made the rounds of NASA was that the Saturn V had a reliability rating of .9999. In the story, a group from headquarters goes down to Marshall and asks Wernher von Braun how reliable the Saturn is going to be. Von Braun turns to four of his lieutenants and asks, "Is there any reason why it won't work?" to which they answer: "Nein." "Nein." "Nein." "Nein." Von Braun then says to the men from headquarters, "Gentlemen, I have a reliability of four nines."


Reliability of 4 neins to be precise

You know why you chose 6 9s.

The date checks

"The market for local models is always gonna be a small niche, primarily for the paranoid."

Have you ever heard of industrial espionage? Pr privacy regulations? Or military applications?

(Also the US military runs claude as a local model)


" - it’s not like it’s something special (Claude is, this cli thingy isn’t)"

How do you know? Have you checked the source?

Do you know how exactly context is created, memory files, skills? Subagents created with tasks?

I don't, but am checking right now. Then I will judge.


bc I build stuff like this myself - it doesn’t take anything to build a wrapper client around a good llm, including using another llm.

So .. the stuff you build yourself, you point it to claude then it runs just as productive as Claude CLI? Did you try?


Neat. Coincidently recently I asked Claude about Claude CLI, if it is possible to patch some annoying things (like not being able to expand Ctrl + O more than once, so never be able to see some lines and in general have more control over the context) and it happily proclaimed it is open source and it can do it ... and started doing something. Then I checked a bit and saw, nope, not open source. And by the wording of the TOS, it might brake some sources. But claude said, "no worries", it only break the TOS technically. So by saving that conversation I would have some defense if I would start messing with it, but felt a bit uneasy and stopped the experiment. Also claude came into a loop, but if I would point it at this, it might work I suppose.

I think that you do not need to feel uneasy at all. It is your computer and your memory space that the data is stored and operating in you can do whatever you like to the bits in that space. I would encourage you to continue that experiment.

Well, the thing is, I do not just use my computer, but connect to their computers and I do not like to get banned. I suppose simple UI things like expanding source files won't change a thing, but the more interesting things, editing the context etc. do have that risk, but no idea if they look for it or enforce it. Their side is, if I want to have full control, I need to use the API directly(way more expensive) and what I want to do is basically circumventing it.

It doesn't matter what defence you can think of, if they want to ban you, they'll ban you.

They won't even read your defence.


I know. All I could do in that case is a blogpost "Claude banned me, for following claude's instructions!" and hope it gets viral.

> I do not like to get banned

This is why I do such experiments on ChatGPT and not Claude.

I don't want to get banned by Claude but I couldn't care less if ChatGPT bans me.


You are not allowed to use the assistance of Claude to manufacture hacks and bombs on your computer

This is neither.

The trick isn't to patch it once, but to create a system that can reproduce your patches against each release as they come in. Then, when code changes make fixes non-trivial calling in a headless session to heal your fixes.

The first trick will be avoiding getting flagged for running an unofficial build.

Well, when I am doing rather thinking work, so not type in commands as fast as possible - I very much do like my laptop to have a touchscreen. It is way more ergonomic and comfortable, but yes, slower. But when the real work happens in my head, I like to be rather comfortable.

(Also I can immediately test touch features of the apps I develope)


Well, google for "DIY cloud chamber" did result in quite some entries. Apart from youtube channels, with the first entry a guide from CERN:

https://home.cern/news/news/experiments/how-make-your-own-cl...


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

Search: