How does this differ from Hermes / Openclaw / Vellum?

I didnt think about it this way, but it would be helpful to have infra around reputation in the same way email has them.

And, it would be nice to have unsubscribe lists in the uBlock Origin style.

NX again??

This isn't the first time their plugin has led to RCE...

How are you able to get to $300/hr productively? (I’m assuming this isn’t fast mode tax).

not hard, massive elo stuff. every decision point needs to think up and implement 25 ideas and then rank them.

Works perfectly installed as part of a server and at mentioning you there. Direct DMs are finicky in my experience.

Except for pro and plus users in the EU eh…

I still use it.

We have it as a data analyst that’s been trained via exemplar queries and MD about the underlying databases.

It also does ad creatives analysis and overall paid marketing spend analysis, including delivering briefs and conversing with stakeholders about things such as cross-ad-platform deduplicated cost of customer acquisition.

In general it is used to lower the technical bar required for cross-domain collab.

Interesting, another case of removing HT improving performance. Reminds me of doing that on Intel CPUs of a few gens ago.

It's quite logical that by saturating your CPU it can only decrease performance.

In this case the CPU wasn’t really saturated with work but with contention on global locks. The contention is lessened by removing the amount of concurrent mounts that are being done.

I wonder if simply setting a maximum number of concurrent mounts in the code or by letting containerd think there are only half the amount of cores, would have solved the contention to the same amount.

There were also really good financing deals during Covid. Net for me after all costs after resale was $1k for the years I owned the car (the 2nd gen).

But I got in near the bottom and got out before the market for it dumped.

Even in a product as technically wonderful as Temporal, we can have relatively simple oversights like this that lead to cross tenant leakage.

If anyone is more familiar with Temporal, is there a way clients could have had internal defense in depth that guards against tenant leakage at the provider (Temporal) level?

Don't use namespaces. Wire up multi-tenant at the RBAC level. Need stronger isolation? Run another cluster.

Encrypting tenant data with per tenant keys is a good defense against this kind of thing.

Things like this are inevitable, especially these days.