ezekg

I had a feeling this wasn't a vulnerability in GitLab as much as it was for Ruby!

Why? Is/was Ruby vulnerable?

Is this a bug in GitLab or in Ruby? It's hard to tell from the report and the patch...

Liability. Compliance. Chain-of-responsibility. Risk. This has always been the case in business, and it will continue to be the case (at least until artificial intelligence actually replaces that need).

> I guess Turso hosting was not making enough revenue?

I would guess it's more that the founders want to exit before AI replaces them. (Based on the doom-and-gloom narrative in tech right now...)

Studying and writing about my conclusions, or just writing in general, is one way that I am still able to enter flow state outside of programming.

I assume it's already on your radar, but look into fair source: https://fair.io.

The context is i.r.t. the monthly cost and the cost of one's time, which has a monetary value, as well as the cost of tokens. So I think it's rightful to assume the topic is of a monetary pay off.

I promise you something like this will never monetarily "pay off."

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.