ezekg

This is the clearest explanation of why I never really liked Stephenson.

Haskell always hurts my brain, but in a good way. I want to understand it, but haven't been bothered thus far.

or look at your phone or whatever

have a means to get it ... in tv broadcasting etc

I think you're missing the point of wearing an analog watch, which is fine, but still missing the point nonetheless. :)

As an avid watch wearer, all analog, I built the game so I could improve my skills, because under pressure when somebody asks "what time is it?", I want to be able to tell them exactly, because I should be able to read it! I think it's good to want to improve your skills, whatever that may be. You shouldn't bar people from that because you disagree.

That works great until somebody sees your watch and asks you for the exact time!

I may have missed numpad support because I have a 60% keeb! Normal number keys work fine for me. Will investigate.

Ha! Very true. I embarrass myself regularly with this little game. :)

Thanks for the report! Will try and fix this in the next release.

Ha! It's quite embarrassing isn't it? Practice makes perfect!

Interesting! There is no am/pm, but I could definitely add it!

I was thinking 10:30.

Are you sure you weren't "close" on something else, e.g. hour/min?

Appreciate the feedback! It cares, yeah, but being off-by-a-minute doesn't really dock your overall score very much. I figured without that, a "perfect" would be much less meaningful.

Good idea! I'll see if I can add into the next release.

Thanks for playing. It's been a fun little game I play to make sure I don't embarrass myself when somebody asks me what time it is, since I wear a lot of watches. I'd love to add a global leaderboard, but right now it's all client-side! A server-authoritative leaderboard seemed a bit too complex, especially i.r.t. preventing cheating, but I might tackle it at some point.

I don't understand how the agent's own authz doesn't match the prompter's authz -- in fact, the agent shouldn't even have its own authz at all! it should always use the prompter's authz, even if that means 'layered' authz (i.e. AND'd) across prompts. Almost all of these prompt-injection attacks crop up because companies decide an agent should be trusted, able to decide its own authz, or that authz for one prompter is the authz of another prompter, which is quite frankly, retarded.

It's even worse if you're SOC2 because then you actually have to go through and mark them as "not exploitable." The noise is insane right now.

Thankfully, most devs aren't the one making purchasing decisions in B2B. I haven't seen any change in the build vs buy equation for real businesses tbqh, and in B2B, those are the customers you want to target anyways, not the indie devs who think they can build Dropbox in a weekend. In B2C, I can definitely see this being true, but I have very little experience there so anything I say here is more on gut-feeling than anything else. But I have over 10 years of experience in B2B, and I've never seen businesses more eager to buy, to free teams up to work on the things they're experts at -- myself included.

Build a good product and they will come.

I did this exact thing this year. I moved about >5 TB of event and log data into Clickhouse. I went from having to increase Postgres storage capacity every few months ($$$) to never thinking about it. Migrating to Clickhouse took me from constant timeouts on analytics queries to all queries returning in well under 100ms, and automated data retention using TTLs going from nightly pruning jobs that failed constantly (Postgres hates DELETEs on large tables) to again, never thinking about it. Because of this, I was able to increase retention per-account from a mere 30 days like I had -- just to keep performance and storage costs under control -- to much, much longer. Huge fan.

Our philosophy through this transition is to bring existing projects along, not to force a hard break. Studios shipping on UE5 today should expect a manageable, and clear path forward when UE6 is ready for them. To allow for this, Actors and Blueprints will be in early versions of UE6. Eventually, these will be deprecated when the new framework is sufficiently mature, and you’ll have conversion tools to move projects from one framework to the other.

Very interesting to see them deprecating Blueprints. The proliferation of Blueprints is actually why I chose Unity DOTS over Unreal. I wanted to code (especially with LLMs), and from who I talked to, the industry seemed to use Blueprints more than code for gameplay scripting, which didn't appeal to me at all.

Gitlawb is very close to Gitlab. Good luck.

I also wrote a huge chunk of my game by hand 8 years ago, but I wouldn't lead with 'it's built without AI' now because that would be disingenuous.

Wow, I also wrote a game 8 years ago and have been using AI to rebuild upon it. I'm excited to tell people that I wrote it from scratch without AI! Love these new rules!

If you ask it for a cute picture of you and somebody else it has no way of telling if you’re trying to improve your relations with your spouse or be a delusional creepazoid stalker. The chatbots which can make images are programmed to assume the latter, which is more than a little bit offensive.

I've seen the same behavior increasing as well, across the board with AI. I was hitting these types of issues just using ChatGPT to make funny pictures with my kids, of me and my kids. It got to the point where all of my kids asks were rejected due to its "guidelines" when in reality all they were asking was to be turned into Elsa or be chased by a trex. Silly kid things, yet it assumed I was being a creep, or attempting to break copyright law. I used to be able to use Grok for these things, as it was largely less "censored" but that seems to no longer be the case. It feels like infantilization, and I absolutely hate it.

Or they're trying to hype up an investment...

Thanks for sharing. Funny enough, I was just asking GPT to chart this for me a few days ago. And people say postmillennialism is a pipe dream...

Not talking about the generated clients, I'm talking about the spec itself. If the majority of API services don't even have an OpenAPI spec, they can't use tools like Stainless even if they wanted to. A lot is being left on the table by not working on that first issue: companies don't have an OpenAPI spec. Been on my mind to explore that issue, because I run one of those API services that don't have an OpenAPI spec, but I have other priorities pulling my attention away from that. I just wish it was all handled.

Now if only we had a service that could generate OpenAPI specs automatically...

Just say no. Serious.

Yes and no: https://www.anthropic.com/news/anthropic-acquires-bun-as-cla...

Unpublish was unavailable for nearly all affected packages because of npm's "no unpublish if dependents exist" policy. We have to rely on npm security to pull tarballs server-side, which adds hours of delay during which malicious tarballs remain installable

Per https://docs.npmjs.com/policies/unpublish:

If your package does not meet the unpublish policy criteria, we recommend deprecating the package. This allows the package to be downloaded but publishes a clear warning message (that you get to write) every time the package is downloaded, and on the package's npmjs.com page. Users will know that you do not recommend they use the package, but if they are depending on it their builds will not break. We consider this a good compromise between reliability and author control.

I don't even know what to say here, npm.