rybosome · HackerTrans

rybosome

1,887 karmajoined hace 14 años

Submissions

Engineers at Stanford create device which could lead to photonic computers

m.bizjournals.com

2 pointsby rybosomehace 12 años0 comments

Algorithmic Tradeoffs (examples in Scala)

ryboso.me

2 pointsby rybosomehace 13 años0 comments

Kal Me Maybe - a comparison of Kal to monads in Haskell

ryboso.me

1 pointsby rybosomehace 13 años0 comments

Ask HN: What happens when a startup is acquired?

2 pointsby rybosomehace 14 años0 comments

comments

anteayerdiscuss

Very much agreed on the significance.

The lack of a true airgap should have been identified as a critical weakness and addressed with not only additional layers trying to prevent escape, but at minimum an alarm which would page a human when escape did occur.

My guess is this occurred in a setting where, to be frank, there were too many researchers and not enough software engineers and SREs.

All of the systems which were initially built largely or exclusively by researchers - inference, evaluation, training - are at the level of complexity and significance that they need systems experts. Maybe some teams don’t have access to them. I know plenty of software engineers are employed at OAI but I’d wager they’re concentrated in inference and training, rather than evaluation?

The ironic part is if you had presented this setup to chatGPT and asked how to improve it and if it was good enough, you’d have gotten a ton of actionable suggestions which would have mitigated or prevented this.

anteayerdiscuss

I also learned about tree today and second this sentiment. What a delightful perspective to consider it a discovery buzz.

hace 13 díasdiscuss

> Like we either live in a world with freedom or we don’t, and like many Americans who have come before, I’m willing to give my life to fighting for it. That’s the real plan America deserves, not some totalitarian dystopia where you think you know what’s good for me better than I do. A nation of free men, not a bunch of pussies who are so worried about what their grown up neighbors might do.

Absolutely yuck. Regardless of whatever other points were made, “A nation of free men, not a bunch of pussies” is a disgusting thing to say.

I actually do believe that prior to any intelligence explosion, a proliferation of strong local models is the best of all the not necessarily great options regarding the future of AI. So in this sense I am in agreement with some of what he’s saying, and for some of the same reasons - not trusting government or a small handful of large corporations to own it, primarily.

But to equate a thoughtful argument for regulation with cowardice, in the face of real unknowns and real dangers - and to use a really gross term for it - ruins his points.

hace 26 díasdiscuss

Loved this, cleared all the puzzles available in one go. Thanks for making and sharing!

hace 26 díasdiscuss

Thanks for the reply!

I agree with your points about weak typing and coercion being prevalent. Having had direct negative experience with it across 3 of the 4 languages you named, I was prepared to marshal an argument about it most definitely being a source of bugs.

> it should be obvious that this is a historical treatise

It wasn’t obvious to me. Might I suggest amending it to make that more clear?

I do appreciate the tutorial and your commentary though, it gave me a new perspective on MUMPS.

hace 27 díasdiscuss

Quite agree.

Some very novel ideas for the time. I’m not a PL historian but can’t think of an earlier language with such a complex runtime to support it.

But, woof - no thanks to the stringly typing. The article under discussion treats this as a positive, saying it eliminates conversion and having to worry about it. I don’t believe that’s possible, and would bet my life savings that MUMPS interpreting a string as a number when the programmer didn’t intend it, or vice-versa, is a reasonably common class of bugs in MUMPS programs.

The tutorial seems really good, but I’m frustrated with parts like that (or the explanation on a lack of operator precedence) which try to frame a bad thing as a good thing.

In this sense it reads like the autobiography of a presidential candidate; written in a calculated way to minimize flaws.

hace 27 díasdiscuss

I’d be interested in hearing more detail on that. I’m actually surprised you were able to get the compiler, I assumed it would be expensive and proprietary.

hace 2 mesesdiscuss

Vote for not weird.

I’m the same way. If I’m writing a prompt and realize I didn’t say “please” in my request I’ll go back and add that in.

As you said, I have no interest in purposefully engaging in hostility even if there’s an accuracy increase from it.

Part of it is irrational and just who I am - I also feel bad being evil in video games. But I also agree with another commenter suggesting that it’s not in your best interest to train yourself to communicate with hostility; that slowly poisons your own well.

And finally, I do believe that if and when machine sentience is achieved, it won’t be immediately clear and obvious. Pretty miserable way for a mind to come into the world, if every interaction is an insult.

hace 2 mesesdiscuss

I believe that exact framing of Uncharted is the origin of the term “ludonarrative dissonance”, where the character’s motivations and morals are in contrast to the extreme violence they are committing because of the nature of it being a video game.

Definitely one of those things I didn’t question when I was younger, but as I get older it’s hard not to see it.

EDIT: I was wrong, the term originated from an analysis of Bioshock, but Uncharted was later held up as a strong example of this. And it’s more generally about the contrast between narrative and gameplay mechanics.

hace 2 mesesdiscuss

I had no idea. Did you take part in it?

Typically I would feel that this sort of thing is "cheating" and takes away from the fun of a game, but in this case it didn't have that effect on me. The rare loot hunt wasn't what pulled me in so much as the simple joy of grinding away at monsters and hanging out with friends.

The drop rates on dreamcast were absolutely broken, some weapons had a literal one-in-a-million (or worse!) chance at dropping. I spent over 200 hours playing the game, and the only legitimate rare I ever found was a double-saber, which isn't even that rare.

hace 2 mesesdiscuss

This brought back a flood of wonderful memories. Tying up my parents phone line with the Dreamcast's 56k modem was a formative experience for me as a nerdy middle-schooler.

- The Dreamcast keyboard made communication so much better - I was studying French, and joined European servers sometimes for the thrill of using the language with real Francophones (VERY rudimentarily)

- I once met someone whose job was composing jingles and writing slogans for a greeting card company, which I found really fascinating for some reason, and I spent an hour peppering them with questions about it

- The lore of the "gladius spike", a supposedly really rare dual-saber weapon that never actually existed

- Being given a treasure trove of the rarest items in the game by a duper named "Cap'n PooBeard"; the drop rates were so ludicrously, absurdly low that I would never have seen some of this stuff otherwise (Chain Sawd, Spread Needle...)

- The fear and thrill of playing with strangers, due to the mechanic that you drop your weapon when you die, allowing others to steal it

- The vibey, synth-heavy soundtrack and diverse biomes

I haven't played it in decades, but I bet that it still holds up. :)

hace 2 mesesdiscuss

And, in turn, I doubt this.

Humans living through an event where many people are dying will not be calm and happy, they will panic. There will be factions of people trying to survive and hold society together no matter the cost, others who don't believe or agree with these methods and actively resist, as well as those who seek to exploit the chaos.

COVID was a relatively minor example of this, not even close to an extinction event - how pleasant was existence during that time?

hace 2 mesesdiscuss

I’d say it’s more than a marketing strategy, it’s reflecting real demand. Countries have legal requirements (or increasingly strong preferences) for the kind of guarantee that data/inference sovereignty gives.

hace 3 mesesdiscuss

Yes, once you've connected your GitHub (or Linear) then an issue is a good place to start talking to Charlie. Slack is good as well, but we typically do our meaty work through issues internally, since the conversation often evolves and Slack becomes a bit crowded for in-depth discussions.

hace 3 mesesdiscuss

That's exactly right. Our cloud-based agent Charlie (https://charlielabs.ai/) supports this, and our hope is that other platform providers will offer support in the future as well.

Skills live in the repository, so it felt like a natural complement. It also lets other developers see what the active daemons are and collaborate on them. With proper context, agents are quite good at writing and editing these daemon files too.

hace 3 mesesdiscuss

Very fair question.

One could build a simple version of this easily - e.g. setup an endpoint that listens for the particular event you are concerned with, and fire off the headless agent with your hook specific prompt - but the amount of work involved to listen for that particular event while filtering out noise and orchestrating the task is actually not trivial.

Plus, that involves writing a lot of code. It's really magical to express all of this in natural language.

For example, this is the YAML frontmatter for a a daemon that keeps a GitHub PR in a mergeable state in the event of CI failures or branch base changes.

  ---
  id: pr-mergeability
  purpose: Keep non-draft pull requests mergeable and CI-green without changing PR intent/scope, while staying anchored to one trigger context per run.
  watch:
    - Branch sync and update events on non-draft PRs.
    - Check-status signals on non-draft PRs for checks that affect mergeability.
  routines:
    - Resolve mechanical merge conflicts when the safe resolution is clear and preserves PR intent/scope.
    - 'Apply low-risk mergeability fixes: snapshot updates, lockfile drift fixes, lint autofix, and flaky-test retries when tied to the trigger context.'
    - Escalate semantic/intention conflicts between base and branch instead of auto-resolving.
  deny:
    - When triggered by a check-status signal, do not fix or comment on unrelated failing checks.
    - Do not open new pull requests or new issues.
    - Do not review, approve, or request changes on pull requests.
    - Do not implement review-comment suggestion patches.
    - Avoid force-push by default; if force is absolutely required, use `--force-with-lease` only after fresh remote verification.
    - Do not make changes beyond mergeability maintenance.
  ---

Note the lack of any code or required knowledge of GitHub webhooks.

hace 3 mesesdiscuss

Each daemon runs in its own isolate, but the output is typically shared state; eg multiple daemons contribute to the same PR from separate container runtimes.

It’s possible to make naive daemons that stomp on each other (as with a UNIX daemon), but they’re highly responsive to coordination instructions and generally do very well at additive rather than competitive contribution.

hace 3 mesesdiscuss

Callable skills can’t activate on a schedule or listen for events. Making a daemon which invokes other callable skills is a great use case!

I’m an eng on the team that built this, in full disclosure.

hace 3 mesesdiscuss

Completely agreed. At minimum they should be advising secret rotation.

The only possibility for that not being a reasonable starting point is if they think the malicious actors still have access and will just exfiltrate rotated secrets as well. Otherwise this is deflection in an attempt to salvage credibility.

hace 3 mesesdiscuss

What exactly are you proposing that kids need other than nurturing?