I worked at an IT consultancy and one of the things it did was support the SharePoint system for a chemical company. One interesting thing they did was use Javascript in the Material Safety Data Sheets to automatically add the current date when one was printed. Most people don't know that PDF readers have a full javascript interpreter.

This must be for Cowork. I don't have Hyper-V enabled because I prefer to use VMWare workstation so I can't use Cowork.

Why would AWS have any say in what someone does in their own time?

You are 100% correct and if uBlock Origin didn't exist I would dedicate my life to creating it.

Google Maps is the modern globe.

I own a domain I use for email and I have it configured to deliver ANY address that ends with @mydomain. This works like + addressing on steroids. I can have website@mydomain or recipient@mydomainand it makes filtering much easier.

The original Google search that used inverted indexes and page rank and respected boolean operators was very good and let you actually find obscure information. Call this Google Search 1.0

Then in order to increase revenue Google dumbed down search very badly and made it very hard to find obscure information. Whoever decided to delete random search terms is someone I want to punch in the face really hard. Call this Google Search 2.0

But the way Google has integrated Gemini Flash into search is actually pretty good and is definitely an improvement over Google Search 2.0

If the US is shit, then the CCP is shit that has been eaten and puked back up.

Anthropic knows it refuses too much, they want to be very cautious to avoid any scandals. I think this is why they want to store all Fable and Mythos chats for 30 days so they can use the data to improve.

They want to be very cautious to honour the important doctrine at least until IPO launches: we are so good we are nerf our products.

I’m a point where I expect everything I do will be retained indefinitely.

I’m having a really hard time believing some weak reason for a 30 day retention policy.

"Performance guarantees are stochastic rather than deterministic. The worst case performance (for metrics such as number of hops and oversubscription) is known, but for RNG our models are stochastic (i.e., the worst case performance is known with high probability). This is a weaker limitation than it might appear. Fat-tree guarantees are also effectively stochastic once you account for real-world failures, which are frequent at scale. RNG simply makes the stochastic nature explicit and designs for it from the start."

Well I guess I'd like to see those guarantees, but more specifically, the variance of them.

I think Section 9, and Figures 13/14 in the Arxiv preprint sort of address this, but it doesn't mention anything about accounting for real-world failures in fat trees. I haven't had a chance to read it all, though...