It's clearly a lot of Claude though:
> Neither is a URL fetch, so the allowlist never saw them. > No code ran; this vector is purely a file disclosure, and it is the one the agent used first.
etc
1,303 karma · joined August 14, 2020
It's clearly a lot of Claude though:
> Neither is a URL fetch, so the allowlist never saw them. > No code ran; this vector is purely a file disclosure, and it is the one the agent used first.
etc
CFAA doesn't just mean the feds kick down your door, you actually have to get reported and sued over it.
Are we all having this idea?
A big worry was always "why does workers sit in front of my cache? that's a waste of an invocation if i'm returning a cached result"
this is the wrong direction
(jk i read the readme)
Sure, Ceph isn't "S3-backed", but when you're talking about an actual filesystem or block device (the thing that does lots of small-IO), you care more about io-perf than sequential.
Large sequential jobs that everyone is targeting now (ie AI workloads) can use s3 directly just fine, because they don't have decades of code built on top of the filesystem.
Congrats iroh team!
Easier for them to adopt AI than AI companies to rebuild the networks
Gemini models clearly gaslight the user and hallucinate, they're also SUPER verbose, as shown in the demos from the keynote.
Plus, if they're not charging a subscription for this, you know we're getting the dumbest models...
Biggest deal imo
You see this at least once a year. Never heard of this from AWS or Azure.
In all seriousness, this is why we don't use them. They have the most ergonomic cloud of the big three, then absolutely murder it by having this kind of reputation.
> Rippling
> Parker Conrad's redemption arc after Zenefits hit a plot twist when Rippling sued competitor Deel for planting an undercover spy inside Rippling who was paid €5,000/month by Deel's CEO to steal trade secrets. The DOJ opened a criminal investigation. Deel allegedly ran the same playbook at crypto HR startup Toku. YC uses Rippling for their own HR — awkward.
Per this description Rippling did nothing wrong here, all about Deel...
In seriousness, looking at their scale, this is an insane engineering challenge.
Especially if they’re moving databases, not easy ever, and certainly not at that scale
Works on these psuedo links all over github
Tune in for the next episode: Word