Hacker Newsnew | past | comments | ask | show | jobs | submit | fghorow's commentslogin

Check out proxmox. Debian base with Debian apt repos available for standard stuff, with ZFS built into their kernels. Easy to install. And, if you insist on running TrueNAS (or whatever) just stash it in a container or KVM box.

(Edited to add: I forgot! ZFS on root available from the installer -- encrypted even if that's your jam.)


Nice! Ta.

I've been using Claude Code Extension in VSCode (no phone-home configured), backed by DwarfStar on a LAN local MBPro 128GB M5. The context bloat is horrendous, leading to 5-10 minute prefills.

I've recently been exploring tools like headroom to help manage context, with some limited "success" (for some definition of success). What do others with similar setups do?

(I kind of hate to abandon Claude Code, as it seems to be the most capable coding assistant of the limited set of tools I've tried. But that horrendous context bloat is really painful!)


OMP. Opinionated but completely configurable. Probably the beat to have a lot of batteries and let you uninstall what you don’t want. Sadly Anthropic forbids its use on their subscriptions.

Thanks. I'll kick the tires on OMP a little harder...

Isn't OMP sort of Claude in Pi's clothing? I tried it and it seemed like I was using Claude. But if tweaking is needed there then why not stick to Pi and add/strip as needed?

> Anthropic forbids its use on their subscriptions

This! How are these companies even allowed to do this while they anyway charge for either API access or limit usage in the generic plans. It's blatantly just "I don't want you to spend less per generic task!".


It's getting harder and harder to tell these days when El Reg is being serious. I think this is a case when that is so, but I'm not sure...

Written by "A worried Belgian researcher".

Perhaps this approach should be known as "The Method of MOOments"?


I'm interested in your eclipse experience. I tried capturing totality with a seestar S50 back in the 2024 eclipse. What I found is that at the very moment of totality, I had not removed the solar filter fast enough, and the bloody thing lost lock on tracking the Sun. Rather than fiddling with the equipment, I immediately started to ignore the 'scope and just experienced the eclipse.

That was the right thing to do!

But removing the solar filter right at the moment of totality is such an edge case (both for the software and my wetware which was kind of overwhelmed) that I wonder how others dealt with it?


I was capturing video and removed the magnetic solar filter as quick and carefully as I could. It worked but didn’t love the results. Hard to not move the telescope a bit that causes realignment and then obviously it has to readjust exposure that takes a moment. Same when putting it back after totality. I’m also looking for advice. We have another chance next year in Spain!


Yes indeed! Spain, next year! (And Australia, the year after that! ;-) )

I'm also wondering about the feasibility of taking these gizmos on airplanes, what with the Lithium battery packs, etc.

What we really need (for some definition of need) is a robot-filter-remover, timed to deal with the two critical times (first and last instant of totality; 2nd and 3rd contacts from memory). Anybody out there interested in building something like that? It would be purely a passion project, because it could only be used a few times a decade...


I’ve flown with it a handful of times without issue. Both in cabin luggage and checked in but I guess I’m risking it in the latter.

Not sure how a robot filter remover would work on the DWARF 3 that is reliable and works around loss of alignment and the exposure adjustment. I would love to find a solution for next year. Also wonder how can one test it out beforehand. I don’t want to burn the sensor ha ha


Agreed!

Also, I just found this (total hack, but cool)! [1]

[1] https://github.com/nsuan/TelescopeFilter


On a related note, there is a reasonably well known commentary on an adjacent technology by Ruth Schwartz Cowan (1985) titled "How The Refrigerator Got Its Hum". It describes a 1930s market battle between heat-driven ad/absorption chiller technology ("Kelvinator") and work-driven compressor chiller technology ("GE"). Tl;DR GE won.

The ab-chiller is likely best known these days as the "propane fridge" in RVs.

Sadly, the only online resources for Cowan's work I can find are either Scribd paywalled [1], the entire book in which Cowan's piece is a chapter on the Internet Archive [2] or a pointer-to-a-pointer from a piece in the Guardian [3] to a boingboing piece [4] that seems to be offline.

(Background: I work in Direct-Use geothermal. Such ad/absorption chillers are one major tool in the toolbox for low-T cases where it is uneconomical to turn geothermal heat into electrical energy -- mostly due to Carnot's Law considerations.)

[1] https://www.scribd.com/document/527479452/Cowan-How-the-refr...

[2] https://archive.org/details/socialshapingoft0000unse_g5b0

[3] https://www.theguardian.com/science/political-science/2014/f...

[4] https://boingboing.net/2012/08/20/how-the-refrigerator-got-i...


It's not exactly straight out of one of the labs -- it's heavily quantized -- but have a look at [1].

[1] https://github.com/antirez/ds4


...or a station wagon full of magtapes.


Testing:

The union of a lot of necessary conditions is not a sufficient condition. But it might be good enough for software.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: