> Suffice to say that I was far from home in an unfamiliar (and public) environment with people I didn’t know very well and had little reason to trust.
Stopped reading after this part -- Taking psychedelics in such circumstances is a horrible idea!
> In other words, it was as unsuitable an environment for psychedelic experimentation as I could have designed [...]
I'm wondering what is your overall experience, how much of your ad campaign traffic were bots and how did it fare compared to other ad platforms.
What just happened?
""" UPDATE: Thanks for the feedback. There were many more concerns than we expected. We’re going to process the feedback and rethink our plan. We will not activate product usage tracking on GitLab.com or GitLab self-managed for now. We'll make sure to communicate in advance on our blog when we do have a new plan. """
""" Amazon Web Services (AWS). We reported this issue to the AWSSecurity team. They confirmed the vulnerabilities on CloudFront. The AWS-Security team stopped caching error pages with the status code 400 Bad Request by default. However, they took over three months to fix our CPDoS reportings. Unfortunately, the overall disclosure process was characterized by a one-way communication. We periodically asked for the current state, without getting much information back from the AWS-Security team. They never contacted us to keep us up to date with the current process.
"""
[0] - https://cpdos.org/paper/Your_Cache_Has_Fallen__Cache_Poisone...
I run plenty of agent loops and the speed makes a somewhat interesting difference in time "compression". Having a Claude 4 Sonnet-level model running at 1000-1500 tok/s would be extremely impressive.
To FEEL THE SPEED, you can either try it yourself on Cerebras Inference page, through their API, or for example on Mistral / Le Chat with their "Flash Answers" (powered by Cerebras). Iterating on code with 1000 tok/s makes it feel even more magical.