torarnv

My experiments with output styles have not been sufficient to keep the model in check. It still spits out incomprehensible gibberish and load-bearing-isms.

Does anyone have an output style nailed down that actually works? If so, please share!

This twist often involves loosely related or even unrelated bugs or even non-issues, and Claude bringing those into the conversation at that point breaks my mental processing of the response.

Any tips on how to avoid that would be highly appreciated!

Those are awesome features! The one missing for me is bridge networking. Any idea why orbstack doesn’t have that?

https://github.com/orbstack/orbstack/issues/342

I’m using https://github.com/torarnv/claude-remote-shell for this, which runs Claude’s Bash tool on a remote machine but leaves Claude running locally otherwise.

I’ve found it to be a good balance for letting Claude loose in a VM running the commands it wants while having all my local MCPs and tools still available.

> Lume automates the macOS Setup Assistant via VNC and OCR, creating ready-to-use VMs without manual clicking. Tart relies on Packer plugins for automation.

This feels disingenuous. Tart has unattended setup support as well, and it's based on the same VNC + OCR technique as Lume. In fact Tart had it first, and your approach seems to be heavily inspired by it. In addition the boot command instructions you're using came from https://github.com/cirruslabs/macos-image-templates/

The only material difference is whether it's built-in or integrated via Packer.

Excellent, thanks!

Awesome! Thanks for posting, I've been looking for exactly this kind of project that takes end to end pristine restoration seriously.

The FAQ states you back up the originals as plain images files in YYYY/MM/DD format, which is great for integration with other tools. What about metadata? Is it in a format that lends to integration with other tools, say if you stop developing/supporting your app for some reason?

Qt for macOS maintainer here.

We've tweaked our styles to take the new design metrics into account, and fixed or worked around issues where we've seen them. We don't integrate with NSGlassEffectView and friends yet. If you find any issues in recently released version of Qt 6.10, 6.8 or 6.5, please report them upstream, thanks!

See also https://www.qt.io/blog/qt-on-macos-26-tahoe

In my case, both.

I've flown twice with my new AirPods Pro 3, and both times I had this exact experience; high pitched and loud feedback. They were properly cleaned, and had a "good seal" according to the settings wizard.

Glad to see I'm not the only one at least, and hopefully this will be possible to fix as a software update, rather than having to replace the AirPods.

This seems like a good initiative, but makes me wonder, isn't there a risk these cats will end up overeating when endless Internet-people click the feed-button?

Another vote for Infuse. In my experience Infuse 8 handles HDR and color management correctly (1:1 with Safari or QuickTime), while IINA does not (too dark).

Awesome!! Are you planning to open source this? I’ve been working on something similar and would love to join forces!

Could you describe the tweak you did, and possibly the general setup you have with zed working with LM Studio? Do you use a custom system prompt? What context size do you use? Temperature? Thanks!

Does anyone have suggestions for tools similar to this/Screen Studio that works as a webcam on macOS? I'd like to share 2-3 windows, with those fancy backgrounds, and a camera overlay, in a 16:9 or 4:3 aspect ratio, without needing to change the resolution of my ultra wide monitor or move/close all other windows etc.

Agreed! The CMake Xcode generator is extremely slow because not only is it running the configure tests sequentially, but it generates a new Xcode project for each of them.

CMake also does sequential configuration AFAIK. Is there any work to improve on that somewhere?

Amazing summary of the mental model of the interdiff review style, and the problems with GitHub's approach to code review. Thank you!

One thing you don't touch upon (yet) is that the diff soup may lead people to prefer the squash merge strategy, to get rid of the "noise" of the fixup commits, which throws away the "good" initial 3 atomic commits as well.

With interdiff review style you're left with the initial 3 commits, and the choice of whether to land them individually or squash them is based entirely on the commits themselves and how atomic they really are.

As far as I know, splitting the series into individual PRs only works if you have commit rights to the repository, so you can base one PR on a different branch (in the main repository) than main.

As an outside contributor, with a fork of the repository, your three PRs will incrementally contain change A, A+B, and A+B+C, making the review of the last two PRs harder, because you need to review diffs for code you're already reviewed in another PR.

I remember seeing a similar layout used for an article or blog post about reverse engineering a binary format. I’ve tried finding it later, but couldn’t. Anyone know of such a tool that lets you describe the various headers, fields, etc of a binary format with a similar visualization?

$ clang++ foo.cpp -o foo -framework Foundation

-lswift_Backtracing also works, but dunno if that's "public API"

$ codesign --force --sign - --entitlements entitlements.plist foo

https://github.com/apple/swift/blob/main/docs/Backtracing.rs...

$ SWIFT_BACKTRACE="enable=yes" ./foo

Very cool!

6.0.0 was released 08.12.2020, with 6.0.4 released at 04.05.2021 as the last patch release in that minor series. That's more than 5 days of support for the 6.0 minor series.

If Debian supports its releases for longer than the upstream projects do, then that's a (perfectly valid) choice of Debian, but I'm assuming that involves maintaining those projects as well, to the standards of Debian's support policies.

Qt absolutely releases updates

https://wiki.qt.io/QtReleasing

(Disclaimer: I work for the Qt company)

How do these distributed build tools work across the Internet, i.e. outside of a local LAN office setting? Does the increased latency and slower bandwidth become a bottleneck?

The communication with the author (Bogdan) has unfortunately been lacking, taking very long to reply (months) and at best confirming the issues but without any plans to fix them.

See https://news.ycombinator.com/item?id=25434191 for prior discussion about my experience.

I wish I could use Zeal to browse the Apple documentation as well, but unfortunately that’s exclusive to Dash.

I’ve even paid for Dash to get that feature, but no longer use it due to some UI changes in the latest version that add extra clicks for each search query, making the UI inefficient.

Zeal seems to have be inspired by the old and efficient Dash UI, but I can’t have both that and the Apple docs from what I can tell.

What are the differences? Do you have a link to the original?

FUSE (Filesystem in Userspace) is an interface for userspace programs to export a filesystem to the Linux kernel. The FUSE project consists of two components: the fuse kernel module (maintained in the regular kernel repositories) and the libfuse userspace library (maintained in this repository). libfuse provides the reference implementation for communicating with the FUSE kernel module.

https://github.com/libfuse/libfuse

Nor is this related to Qt in any way. As far as I know Qt has never shipped .cire files as a way to sign the libraries. This is something the vendor of the software token library (stauto32) has done when embedding Qt.

Don't know how Syncthing works, of it it would even work, but what if Syncthing would detect that it recurses into a .git folder, and then use git push to push all refs to the remote .git repo? That should give a transparent "sync" of the entire git repo and workdir for the user, but via the safety of git's own sync mechanism.