guptaneil
Joined 16 years ago
Joined 16 years ago
I’d love to see somebody nail the UX of distributed compute in your home that you own. A box I can buy that is similar UX to managing a SaaS account after plugging it into my router, with automatic management, updates, encrypted backup across cloud providers, and an App Store for services I can install on this appliance that gives self-hosted apps a means to monetize. Then scale that foundation up to business needs and really profit.
These ideas have existed before but IMO nobody nailed the UX and most people didn’t believe we’d light our own basket on fire for fun back then, so the market wasn’t there.
All this is to say despite net neutrality technically not being federally required between 2018 - 2024, it wasn't feasibly for ISP's to roll out metered plans that would go unchallenged. I suspect most were stuck in a "wait and see" stage, and likely expected this eventual rollback anyway given the landscape is still so rapidly changing.
So the protests and constant pushing back against NN did have a positive impact on our eventual outcome, even if it's not obvious or a direct line from reddit blackouts. Like most things, the truth is complex.
Correct. The sortable nature of UUIDv7 improves database performance and index locality by helping the index be more efficient since rows are inserted in a predictable order instead of scattered randomly.
The biggest question will be if it’s too much of a pain that I don’t want to use it at all.
Oh sorry, that's from CNET's review of the first iPhone in 2007: https://www.cnet.com/tech/mobile/original-iphone-review/
It's way too early to tell if this product line will succeed in the long term. Will the first gen Vision Pro be a runaway success? Of course not! Will later generations look as obvious as the iPhone does now? I sure hope so!
For comparison, Apple sold 1.4 million iPhones in 2007. Supposedly Apple is expecting to sell around 500k Vision Pro units this year. Given the 3x price difference (in 2024 dollars), that effectively means the first gen Vision Pro is expected to bring the same revenue as the first gen iPhone.
We all have rosy retrospection about how great and obvious the first iPhone or first iPod was, but honestly nobody had any idea if Apple's crazy bet would pay off. We all agreed it was magical tech, but it was expensive, had tons of limitations, and nobody really needed it. Sound familiar?
All I know is betting against Apple has rarely paid off. They do have failures too though and this is clearly technologically more ambitious than any other launch, so who knows! And honestly that's what makes this launch most exciting.
It's been so long since I've had child-like wonder about some new technology that I'm just glad Apple took a chance on launching such a crazy device, even if I don't know what to do with it... yet.
It's a completely local energy monitor that you can install into your home's circuit breaker panel, and then view dashboards or read data via an API from a local web server running on-device. You choose how many sensors you want, but you can monitor your whole home as well as individual circuits.
For example, I track and trigger automations when my various appliances (laundry, dishwasher, microwave, etc) start/stop. It's very cool. Just be warned that it does require some research, basic understanding of electricity, and comfort working with high voltage mains connections if you plan to DIY it but I found it approachable and easy to setup.
What it looks like: https://i.ibb.co/qBVmBD1/IMG-1595.jpg
What if I make a 3rd party client that actively records my users' iMessages and sells them to Facebook? Should Apple be required to support my app too? If not, are they expected to audit and vouch for every third party client? If yes, how is Apple supposed to make any claims about the security of iMessage if I have no control over the client my recipient might be using?
The whole interoperable API argument comes from the same place as "encryption where the good guys have keys," yet somehow demands for interoperability seem to be much more popular on HN. The E2E in E2E encryption stands for end-to-end, which inherently requires trusting both ends. Otherwise you might as well not have encryption.
Note that whether or not companies should be required to support third party clients is a different debate than whether or not Apple should be required to support Android, even if the end result happens to be similar in this case. I think most people defending Beeper are interested in the latter and are willing to burn down encryption to get it via the former. As a user, sure I'd love for my Android friends to use iMessage too. But this is not the way.
(To be clear, I don't think we should regulate that Apple has to support Android either. If I develop a new OS, would every company be required to build a client for their service for my new OS too? But at least I understand the merits of that debate.)
One idea I’d love to see somebody implement: weight content that a user spent longer typing + editing higher as a proxy for thoughtfulness. Unfortunately this specific client-side metric can realistically only work on a native-only service with device attestation and no API, so that the metric can be trusted, but would be cool to think about other solutions to surfacing higher quality content (like TikTok did), as well as solving the inevitable authenticity problem as more and more online content will be astroturfed by LLM’s.