Readit NewsIn my case, stupid use cases for a folding phone: unfolding the screen helped it render in desktop layout...
Picking the 'desktop site' / request desktop site button in the ... menu also works though!
In many threads, those comments can be just as annoying and distracting as the ones being replied to.
I say this as someone who to my recollection has never had anyone reply with a rule correction to me -- but I've seen so many of them over the years and I feel like we would fill up the screen even more with a rule like this.
I know they mentioned that they thought of making this just a watch app, but didn't like the two-handed button press or raise to wake gesture. Why not just optimize for removing the gesture entirely? The microphone has to be better on a full size watch on your wrist vs the tiny ring further away on your finger.
This hits the same nerve in me as those single-use vapes with screens, except you can't harvest the battery out of this one.
https://www.kickstarter.com/projects/getpebble/pebble-2-time...
It was one of the devices I was most excited about way back when, and I'd still love to see it – button, headphone jack, running Android. I would love a headless (and thus longer-charge-for-smaller-device) Android device like that again.
This is the case even on high-end devices. Our 12-month-old Galaxy Tab is slower than a 7-year-old Pixel. Hard to understand.
Plus, they make really odd tweaks to the UI, such as adding a permanent button overlay that clashes with most hamburger icons in websites and apps. This drives novice users insane.
If you wanna ship a custom Android, at least get it right. Otherwise, just stick to stock. Sony does this really well: https://developerworld.wpp.developer.sony.com/open-source
it's really really terrible at agentic stuff
Also notable: they're claiming SOTA prompt injection resistance. The industry has largely given up on solving this problem through training alone, so if the numbers in the system card hold up under adversarial testing, that's legitimately significant for anyone deploying agents with tool access.
The "most aligned model" framing is doing a lot of heavy lifting though. Would love to see third-party red team results.
> For Claude and Claude Code users with access to Opus 4.5, we’ve removed Opus-specific caps. For Max and Team Premium users, we’ve increased overall usage limits, meaning you’ll have roughly the same number of Opus tokens as you previously had with Sonnet. We’re updating usage limits to make sure you’re able to use Opus 4.5 for daily work.
> Don’t make your prospects wait–ever again
> [...] where prospects receive personalized demos, in a video call, instantly.
> We are preparing the demo for you...
> Setting up your experience...
> We are experiencing very high demand
> Almost there...
I'm not super sure what architecture is in use that means that 16 minutes of being on the HN frontpage leaves it stalling out and unable to respond to requests after 60 seconds, but... it doesn't feel connected with the homepage messaging.
I absolutely appreciate (and have been subject to!) the HN traffic influx before, but for the nature of the product, when doing an _intentional_ Launch HN (not posted by someone else), it's fairly confidence-eroding to see the architecture fail to handle it in this way.
Really hoping that it's something transient and one-time that can be fixed – but surprised that there exist loading screens for this situation.
I know that from time to time people have argued that jailbreaking should have resulted in more creativity if it were going to, but with that tiny, tiny market, it's hard to believe that many developers, relatively speaking, would have been able to go hard at building something custom and impressive. With this larger market, hopefully folks will get the chance to do that now.