No insider info but this seems like two teams combined and one of their (redundant) products got shuttered. Not a typical "shutdown" announcement for a service since it was (AFAIK) just a different interface for the same underlying feature, accessible elsewhere.
Hard to find the signal in the noise and know what stories I should even read to get a sense of baseline quality; partially because that's just a hard problem inherent to floods of any content, but also because the recommendation system seems to lack enough data (and also might be weighting the wrong things, e.g. the rank #1 story is also the lowest-rated...).
A very cool idea in theory and something very hard to pull off, but I think in order to get the data you need on how readable each story is you'll need to work on presentation and recommendation so those don't distract from what you're actually testing.
Thanks for the feedback - looking at the rest of the comments, I definitely agree it seems to be a common theme. Will do better to fix those issues so there's less noise.
Right now I paste screenshots of AWS/Azure/GCP into Claude and ask it questions on how to navigate around / what to do / how to set things up. This seems like a much better experience solely to not have to deal with the weird mac screenshot UX.
Too fast. It's already coding too fast for us to follow, and from what I hear, it's doing incredible work in drug discovery. I don't see any barrier to it getting faster and faster, and with proper testing and tooling, getting more and more reliable, until the role that humans play in scientific advancement becomes at best akin to that of managers of sports teams.
I'm not sure this is true... we heavily use Gemini for text and image generation in constrained life simulation games and even then we've seen a pretty consistent ~10-15% rejection rate, typically on innocuous stuff like characters flirting, dying, doing science (images of mixing chemicals are particularly notorious!), touching grass (presumably because of the "touching" keyword...?), etc. For the more adult stuff we technically support (violence, closed-door hookups, etc) the rejection rate may as well be 100%.
Would be very happy to see a source proving otherwise though; this has been a struggle to solve!
Why would you buy a 5-year-old iPhone for the same price you can get a new Android with comparable specs though? If I'm gonna spend 2-3 hundred on a phone, I'd like it to last at least a couple more years. Regardless of OS, you're more likely to get that on a new phone vs any phone 5+ years old.
If Apple's still selling it, they'll almost certainly support it at least as long as an above-average Android manufacturer.
The current iOS supports things back to iPhone 11 and the SE2, so you can expect the SE3 and iPhone 13 to get at least two more years of support (no real guarantees, but they're still selling new stock of both, and they have a reputation to protect).
>
> Bitwarden volunteered for this research and already fixed the vulnerabilities a year ago
reply