mmahemoff

I contemplated returning my Duo for the first 12 hours. A week later, I wouldn’t dream of it.

In closed form, it’s tiny, especially with keyboard active. Not something I’d want to be using for more than two minutes, let alone reading or watching videos on. This was my main concern, but I soon realized closed form is “pocket mode” since in my pocket is just about the only time the phone is closed. Occasionally I’ll pull it out and, keeping it closed, select some audio, set up a call, or emoji-react, then put it back. The rest of the time the phone is open, whether I’m out or at home, charging or not.

Another problem is what OP mentions, touch ID. It seemingly jumps around like whack-a-mole because of the 8 possible combinations of (open/closed state) x (orientation). There’s even more dimensions to hammer your muscle memory if you also consider which hand you’re using or whether you’re using it with one versus two hands.

I’m gradually getting used to guessing where the Touch ID is though. I do prefer it for wallet payments since the finger is already on the button. I’ve learned to double-click and verify before making any attempt to tap the phone.

The keyboard in open mode is full-width, and that’s not fun to swipe-type on. I think Apple overlooked this since they omitted the iPad setting to reduce the keyboard size. I expect that’s coming eventually.

As for apps, many third-party apps are still using un-responsive layouts like the early iPad days. Some, e.g., Kindle, are outright non-functional when the phone is open. Certain companies will rave about their AI chops yet they’ve been unable to compose a few magic prompt words to target Duo. This will improve in time.

I’ll live with all these trade-offs for the bigger screen. Reading and video were obvious applications, but using maps when mobile was a pleasant surprise. It feels like folding out an old paper map. It’s very readable in the sun too. I prefer reading on electronic display to e-ink due to the responsiveness, so it’s a big win to have an electronic display that doesn’t suffer from glare.

I think preferences will heavily depends on lifestyle. In particular, people who drive a lot won’t see the same benefits. If you spend a lot of time walking or on public transport, it’s a game changer.

In this case, Party B is sandwiched between Party A (scraper such as Meta) and Party C (the third-party content provider). The scraping agreement dictates A-B relationship and the licensing agreement dictates B-C relationship. Devil is in the fine print as far as what is allowed in both agreements.

Party B has already committed to uphold B-C. Entering A-B may put them at risk of violating that agreement by appearing to grant Party A rights that Party C never granted to anyone but Party B (and maybe even rights that Party B doesn't enjoy). Party B's options are don't consent to A-B (e.g., withdraw from Meta program), take down the Party C content (which would suck if they've already paid for it), or negotiate a carve-out with one or both of Parties A and C.

(IANAL)

“Not your wallet, not your coins” is usually taken to imply “Your wallet, your coins”, catchy marketing but a logical fallacy. This incident demonstrates as much.

r/ClaudeAI, r/ClaudeCode, r/claude

WRT the timing, Veritasium maybe looked at the last few weeks and decided there's a fast-closing window in which to report on any famous messages yet to be solved.

“Make it nicer” will lead to unpredictable and controversial changes, likely to clash with the project owner’s vision. The owner would be better off using the LLM as a collaborator, if anything, to decide where to take the design.

However, UX can also be improved by some simple heuristics that could be seen as mechanistic by the standards of modern LLMs.

Performance and responsiveness, for example, contribute to UX even when the UI remains fixed. I’d wager Fable-level LLMs could improve perf on most open-source GUIs by benchmarking typical use cases and progressively applying standard tricks like caching, buffering, batching network calls.

I still use a 13 Pro Max for travel. Incredible longevity. The only downside is it requires a battery pack to last a full day but those are slim and compact now. I intend to replace the battery soon since it still has 2-3 years left as a backup.

It will probably keep most of its value too, if hardware price inflation continues.

The good news is Apple made a more practical dual-screen device than most previous attempts. The “big square” UI was awkward for both reading and video. Apple not only made it rectangular but kept it in the magic aspect ratio that’s able to be shared by single and dual screens.

I had written off dual screen when the square layouts were the norm, but I think Apple has struck a good balance here between screen size and price+chunkiness+serviceability. I won’t be holding my breath for an iPhone Trio. (Not to be confused with Palm Treo.)

> I've heard PMs saying: "this was a user-submitted bug", meaning you better fix this ASAP.

There are certainly developers with a practice of triaging and action user-submitted reports, but unfortunately it’s opaque to the one who reported it.

“Only a minority of people think of reporting bugs and, if they do think of it, they often fail to do so either because they think it’s too time-consuming or that they might end up looking silly.”

Most people don’t directly use open source, and reporting bugs in closed systems is rarely rewarding.

With the issue trackers that are common in open source, a bug reporter gets to watch the bug report’s lifecycle.

They can see what the developer – and others – think about the bug report. Is it a real bug? Was it reported previously? Is it worth fixing? Does the report contain sufficient detail to reproduce it?

With enough time, the reporter will learn if the bug is fixed or discarded or ignored. At the outer loop, they can become better reporters of bugs by seeing this play out enough times.

In contrast, bug reports to a typical end-user application go into a black hole from the moment they’re submitted. Even if said bug is eventually fixed, the reporter will be none the wiser about whether their submission was even looked at, let alone triggering the fix.

Visitor’s Sunday or owner’s Sunday? It seems to be the former as the stated purpose suggests a PSA function and less about reducing owner’s burden in maintaining uptime.

If that’s the case, you could consider using pre-render JavaScript to detect what day it is in the browser. Then temporarily redirect Sunday-identifying browsers to a “Closed On Sunday” page.

I can see how the title is misleading, but I would have been shocked if it was internal Meta jargon. Execs at all the big tech companies nowadays have a culture of avoiding slogans that could be deemed overly aggressive. Even “Move fast and break things” was technocratted into “Move fast with stable infrastructure” after Meta went public.