HN user

muti

318 karma
Posts10
Comments120
View on HN

Thank you for prompting me to try with my own obscure question, Fable was able to find something from a poor description. I've been looking manually and over many sessions with different models as they improve, none have been able to find what I was after. Fable 5 just one-shot the answer.

Podman v6.0.0 20 days ago

Cool, been running my home server on podman + quadlets for about two years now and picked up a couple of things in the release notes

  podman quadlet list
Added in v5.6.0, lists quadlets and their containers
  podman system migrate --migrate-db
Flag added in v5.8.0. I remember seeing the bolt db deprecation warnings in the past but there was no tool to do the migration to sqlite, now there is (or just upgrade to podman 6.0.0 and it will do it automatically)

See the image and caption at the top of the article

  Images printed with structural colour ink can be made both highly transparent to transmitted light (top) and at the same time reflect light from above in vivid colours (bottom) – two properties that are typically considered mutually exclusive
The printing on the phone is not visible when the phone display is on as the structural printing is highly transparent. When the display is off, the printing is visible because of the reflected light.

Doesn't seem like a very insightful result. Kimi won with the naive strategy. Other models didn't slide tiles at all or didn't demonstrate understanding of the rules, claiming words that lost points. A strategy that did nothing would beat them.

We know these models can solve much more difficult problems, something isn't right.

GitHub Stacked PRs 3 months ago

+1 on this, I also switched to jj when working with any git repo.

What's funny is how much better I understand git now, and despite using jj full time, I have been explaining concepts like rebasing, squashing, and stacked PRs to colleagues who exclusively use git tooling

PGLite Evangelism 3 months ago

Unfortunate name furthers the SQLite is "lite" association i.e. underpowered or incapable somehow.

IIRC it is intended to be read as SQL-ite, as having some relationship to SQL.

PG Lite probably makes sense here though, and PGite is not appealing

Suboptimal - likely. There is some utility: a green letter is more useful than a yellow. Checking for a in two locations when a is a very commonly used letter is __useful__. Still likely much more useful to check for the presence of a fifth letter than a chance at knowing more precisely the location of an a.

Pay someone to sharpen them for petes sake. I can't fathom why you would suggest that seemingly off hand, secondary to throwing away and buying new knives.

Active bookshelf speakers with HDMI Arc input are getting more common. Kanto Ren, Kef LSX II, Klipsch The Fives, Elac Debut ConneX

There's also the compact, simple alternatives to bulky receivers that are becoming available: Wiim amp, Sonos amp, Eversolo play, and the cheaper chinese makers like SMSL and Fosi. Each of those brands has a small device the size of an apple tv that will take an HDMI Arc input, and output an amplified signal to power some passive bookshelf speakers.

Knots and construction with poles and rope lashing was always my favourite part of scouts. The sketches of the knot looks cool on the surface but don't tell me much about how they are tied or what other lashings they are similar to. Not much detail and the second image has three running ends?

The specifics of how the keys are backed against different failure modes/attacks is orthogonal to the splitting of data/key.

Yes you would need to carefully design the system that allows deletion of keys while minimizing chances of data loss, but it can be done, and it's going to be cheaper and less complex to do so on a tiny subset of the data.

Latency considerations are also down to design, it's not a given that there will be significant overhead imposed.

I wanted to try something different when I reset my self host set up several years ago, and went with openSUSE MicroOS. Ultimately it has led to podman containers running under systemd/quadlet and I'm quite happy with the current set up.

Containers auto update with built in podman tooling, getting at logs and monitoring is through the usual systemd tools. When I need to change something, it's easy to work out where the config files are if I have forgotten and they are easy to read and change. Rootless and daemonless is nice too.

I tried a few things along the way, podman compose felt clunky so I'm glad it is deprecated and it's clear quadlets are the way to go.

There was a learning curve and there's less information out there than with docker, so keep that in mind. I would still lean towards docker and docker compose for local dev to bring a stack of services up and down.

Too bad it makes the whole thing laggy enough that I didn't get past the first few paragraphs on my phone, and there's no obvious way to disable it

Apple VPs Greg Jozwiak and John Ternus explained in an interview to a Chinese content creator on Billibilli (spotted and machine-translated by ITHome) that the main reason the power button is on the bottom of the 2024 Mac Mini is because of the computer’s size. Since it was nearly half the size of the previous generation, the underside was “kind of the optimal stop” for a power button. They also say most users “never use the power button” on a Mac, anyway.

Apple isn’t wrong here. The Mac mini measures 5 x 5 x 2 inches, compared to 7.75 x 7.75 x 1.4 inches from the last generation; it takes up much less space on your desk, which is great. The trade-off is that you run out of space for some important things, like a power button.

GnuCash 5.9 2 years ago

There are many levels in between tracking at the "Amazon" level vs the "Meat:Pork" level. For example I currently track all unprepared food shopping as "Groceries", and would break down "Amazon" shopping into categories such as "Electronics" or "Books".

Ultimately it comes down to how much effort you want to spend categorising spending, but there are many levels of granularity and orthogonal dimensions to slice against

From the article

  Intel said Thursday that the company will lay off more than 15 percent of its workforce  
and
  Intel will cut roughly 15,000 of its 131,000-employee headcount, most by the end of the year
15% of 131,000 is ~20,000, so are there more to come or is workforce =/= headcount?