beardsciences

self hosted forgejo is easy/great

There's no way this wasn't meant to coincide with Anthropic's release today.

I am very interested in why it was able to overthink that much. In the 20-30mins of Max reasoning I've had so far, I'm not having the same issues (yet).

I made something that tries to highlight the humor regarding this:

https://news.ycombinator.com/item?id=48950534

Can confirm, just now.

I wanted to make something topical that highlights the humor surrounding the AWS billing issue. Please don't hesitate to let me know what you think.

I love Forgejo!

I am somewhere in the middle, where I want something with more than 48GB/$2k of VRAM, but less than 384GB/$40k.

I'm curious if GMKtec's EVO-X2, with ~96GB of usable VRAM, is still a good solution for something like this for $3,399.

I literally said "Oh, of course" out loud.

My average eventually made it to about 3900, and then stagnated between 3600-3900. I'm curious if this is universal behavior or not. I'm up to about 5k steps.

The repository now appears to be disabled.

https://github.com/DO-SAY-GO/ghostbox-releases

https://github.com/crisdosaygo/ghostbox-home-reveal

This idea is great in concept, and I think it's important to state that, but the GitHub Actions stuff is against TOS iirc + they will need to address that pretty quickly.

I believe this has the same issue as the last article that had these claims.

We can assume that Mythos was given a much less pointed prompt/was able to come up with these vulnerabilities without specificity, while smaller models like Opus/GPT 5.4 had to be given a specific area or hints about where the vulnerability lives.

Please correct me if I'm wrong/misunderstanding.

I'm glad that Atari was willing to compromise at all. I'm happy with the updated response, and hope that it helps others understand the nuance of the situation. Anyone can still go download the main release from the official site.

This is looking pretty good. Going to run some sample data runs + might try this out.

I was coming to look for a comment like this.

It may say more about me than the person writing these type of README's, but if I see more than one or two emojis in a README, I immediately assume it was fully generated rather than written.

Very interesting. I would be curious to understand how granular these updates are being applied to CC + what might be causing things like this. I feel like I can notice a very small degradation but have compensated with more detailed prompts (which I think, perhaps naively, is offsetting this issue).

Simply Amazing. I'd love to know more about this.

appears to be hugged to death for now.

That makes sense, thanks for clarifying. Great writeup.

If I understand this correctly, upcoming Ca-derivations will fix this by making these situations expected, properly-handled cases rather than a weird bug? https://nixos.wiki/wiki/Ca-derivations

Whether it's something like this, or ladybird's engine, I'm happy there is work being made in this space.

This is really incredible. I love easter eggs/hidden things in spectrograms. The implications of this are really cool, regardless of whether is it lossy or not.

I really like the design of this - including the number row.