Readit News logoReadit News
0vermorrow commented on Cerebras launches Qwen3-235B, achieving 1.5k tokens per second   cerebras.ai/press-release... · Posted by u/mihau
0vermorrow · 7 months ago
I'm eagerly awaiting for Qwen 3 coder being available on Cerebras.

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.

0vermorrow commented on TinyPod – Apple Watch case with scroll wheel   thetinypod.com/... · Posted by u/herbertl
0vermorrow · 2 years ago
It's funny how we went from using iPod Nano as a watch with a third party case, to using an Apple Watch as an iPod Nano with a third party case.
0vermorrow commented on Show HN: AI Playground by Vercel Labs   play.vercel.ai... · Posted by u/palmdeezy
pastacacioepepe · 3 years ago
It's completely broken. I couldn't even get one full response from one of the AIs, it always gets stuck near to the completion of the first response. After like 5 tries it told me that I used all my requests. lol.
0vermorrow · 3 years ago
Well it's not broken, I'd assume they limit the `max_tokens` to minimize costs.
0vermorrow commented on A bad acid trip nearly ruined my life   blackshaw.substack.com/p/... · Posted by u/whoooooo123
mahathu · 3 years ago
Exactly.

> 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!

0vermorrow · 3 years ago
Well see, there is your problem, because the author says this in the immediate next sentence

> In other words, it was as unsuitable an environment for psychedelic experimentation as I could have designed [...]

0vermorrow commented on Total number of Brave Browser Publishers   batgrowth.com/... · Posted by u/vicnicius
0vermorrow · 5 years ago
Are there any users here who actually ran Brave ad campaigns?

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.

0vermorrow commented on Crux SQL   juxt.pro/blog/crux-sql... · Posted by u/yogthos
0vermorrow · 6 years ago
Are you missing an /s or is this a serious comment?

https://www.merriam-webster.com/dictionary/crux

0vermorrow commented on Twitter accounts of Coinbase, Gemini and Binance hacked   twitter.com/jorilallo/sta... · Posted by u/jorde
0vermorrow · 6 years ago
Elon Musk has his hacked as well... https://twitter.com/elonmusk/status/1283495825998520320

What just happened?

0vermorrow commented on Gitlab ‘rethinking’ third-party telemetry   gitlab.com/gitlab-org/git... · Posted by u/EMM_386
0vermorrow · 6 years ago
The pushback from users made them rethink this change, here's a pending merge request to the blogpost: https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/...

""" 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. """

0vermorrow commented on Cache Poisoned DoS Attack: Shutdown any CDN Website with One HTTP Request   cpdos.org/... · Posted by u/ldmail
0vermorrow · 6 years ago
So after the authors disclosed this issue to AWS it was fixed and CloudFront no longer caches 400 Bad Request by default, also from the paper linked on the website [0]:

""" 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...

u/0vermorrow

KarmaCake day297April 24, 2014View Original