mmahemoff

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.)

Gell-Mann Amnesia https://en.wikipedia.org/wiki/Gell-Mann_amnesia_effect

As tech became more pervasive in the past couple of decades, it became commonplace for pundits to spout nonsense on the topic. Those takes should give anyone in tech pause about how everything else is reported.

> 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.

Dwarkesh subsequently interviewed one of the authors, published yesterday.

https://www.dwarkesh.com/p/ajeya-cotra

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.

Wayback shows #6 as "By 2010, more than 50 percent of books sold worldwide will be printed on demand at the point of sale in the form of library-quality paperbacks."

It was removed early 2011. Is this what happens when they can't decide on who won?

Aphantasia doesn’t preclude having dreams or internal dialogue/thought.

Great idea for any kind of ambient display. Could use it to CI or server stats.

Why now though? Based on the sharp decline since 2022 (according to Ferris’s numbers), s/books/chatbots seems like the Occam’s Razor explanation here.

> The linked hacks blog

https://hacks.mozilla.org/2026/05/behind-the-scenes-hardenin...

Claude's vim bindings don't support ESC mapping, unfortunately for muscle memory. https://github.com/anthropics/claude-code/issues/25306

Nice work but please consider fixing the cursor styling. It doesn't change to `pointer` when hovering over the books, which is what you'd expect as they are clickable. Then, when you click on a book to open the modal, the cursor does mysteriously change to `pointer` - and stays that way wherever the cursor is.

Sure, if the bot is actually committing fraud, but there's perfectly valid use cases that don't involve fraud, e.g., buying groceries, booking travel. And some banks provide APIs, so it's allowed for a bot to use them. However, any of that can easily lead to flagging by overzealous systems. Having a separate account flagged would give the user a better chance of keeping their regular payments system around while the issue is resolved.

There's also a massive selection bias when the cohort is early adopters.

Another thing about early users is they are also longer-term users (assuming they are still on the platform) and have seen the platform evolve, which gives them a richer understanding of how everything fits together and what role certain features are meant to serve.

Giving access to "my bank account", which I take to mean one's primary account, feels like high risk for relatively low upside. It's easy to open a new bank (or pseudo-bank) account, so you can isolate the spend and set a budget or daily allowance (by sending it funds daily). Some newer payment platforms will let you setup multiple cards and set a separate policy on each one.

An additional benefit of isolating the account is it would help to limit damage if it gets frozen and cancelled. There's a non-zero chance your bot-controlled account gets flagged for "unusual activity".

I can appreciate there's also very high risk in giving your bot access to services like email, but I can at least see the high upside to thrillseeking Claw users. Creating a separate, dedicated, mail account would ruin many automation use cases. It matters when a contact receives an email from an account they've never seen before. In contrast, Amazon will happily accept money from a new bank account as long as it can go through the verification process. Bank accounts are basically fungible commodities, can easily be switched as long as you have a mechanism to keep working capital available.

I’ve tried many e-readers since early Kindle but I keep coming back to two fundamental problems with e-ink, both relevant to education.

First, extremely cumbersome and error-prone to type compared to swipe-typing on a soft keyboard. Even highlighting a few sentences can be problematic when spanning across a page boundary.

Second, navigation is also painful compared to a physical book. When reading non-fiction, it’s vital to be able to jump around quickly, backtrack, and cross-reference material. Amazon has done some good work on the UX for this, but nothing is as simple as flipping through a physical book.

Android e-readers are better insofar as open to third-party software, but still have the same hardware shortcomings.

My compromise has been to settle on medium-sized (~Kindle or iPad Mini size) tablets and treat them just as an e-reader. (Similar to the “kale phone” concept ie minimal software installed on it … no distractions.) They are much more responsive, hence fairly easy to navigate and type on.

The current top HN post is for moltbook.com seven hours ago, this present thread being just below it and posted two hours hence

We conclude this week has been a prosperous one for domain name registrars (even if we set aside all the new domains that Clawdbot/Moltbot/OpenClaw has registered autonomously).

Very cool idea since ffmpeg is one of those tools that has a few common tasks but most users would need to look up the syntax every time to implement them (or make an alias). In line with the ease of use motivation, you might consider supporting tab completion.

Correct. Fortunately a number of streaming services are available in many regions nowadays, e.g., Netflix, Apple TV, Disney, HBO Max or whatever it’s called now.

The content may vary between regions though, e.g., you open Netflix in another country and no longer see a show you’re watching while see other ones appear. This can sometimes feel like a feature more than a bug.

Yes and combine with a travel router so you don’t have to endure logging into a wifi portal with a soft keyboard on the TV, if the stick OS even allows it. Then having to repeat the process daily due to expiration times, or as soon as you remove the key card from the hotel room slot, causing the router to power down and the TV stick to time out.

> of course 1/2 of the appeal is just the accent

Deflating is the moment when Arnie's autobiography audio switches from his own voice to a random American-accent narrator. (After chapter 1 or so?)

I guess time-constrained celebrities are, or soon will be, using AI to read their books in full.

A major advantage of pure models is testability. If your conception of a "model" is perversely a user-facing widget, congratulations, you'll need to write UI tests that simulate button presses and other such user actions, and maybe even inspecting pixels to check resulting state. Tests like that are a pain to compose and are fragile since the UI tends to evolve quickly and may also be vulnerable to A-B experiments. Juice ain't worth the squeeze in most cases.

In contrast, pure model components tend to evolve slowly, which justifies the investment of a comprehensive test suite which verifies things like data constraints, business logic, persistence. If automated testing were seen as a priority, this would be a no-brainer for any serious app. However, testing tends to be underappreciated in app development. This goes some way to explaining why frameworks carelessly fold in M, V, C to the same component.

Or do ZZZZZZZZZZ

This is especially true for sleep since we can be pretty good at incorporating external sounds into our dreams. It's been shown in controlled experiments. Seems likely that certain noises are generically easier to integrate into dreams than other noises, which could just cause you to wake up or have your sleep otherwise impaired.