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

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.

reply


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.


Because people refuse to sharpen their knifes, no matter what you do. So it's better for them to throw away old blunt knifes and buy new ones. That they will do. And buy a real cutting board at the same time.


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.


Are you looking for solutions within git or jj?

In my experience with jj when resolving a conflict, as long as I do it in the earliest change, I will only have to do it once.

Git has the rerere setting [0] which reduces the need to resolve the same conflict over and over

0: https://git-scm.com/book/en/v2/Git-Tools-Rerere


  if (!same) {
    return;
  }

  if (!number) {
    return;
  }

  if (!of_braces) {
    return;
  }

  println("but easier to read")


Yes, you should definitely unnest functions and exit early. But the null-coalesced version is shorter still.


Require the intent to include ticket holder names/id and check it on entry to the venue, multiple intents for the same group can be deduplicated


The article addresses that:

> Of course it also harms real buyers who want to go to a concert with a +1 but do not yet know who they will bring.


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?


Much less data to back up so it can be stored in a way that is replicated for redundancy but still mutable. Separating the key and data is what allows for sending data to tape backup etc


If your (backup-via-redundancy) keys are mutable, you do not have a backup. What happens in the case of a ransomware attack, for example?

You've also added (possibly substantial) latency to every single operation that operates on user data.


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.


One simple way is to keep only a few days / weeks of (immutable) keys backups. You can always stop the deletion of you have a big issue. If the law says you have 14 days to delete all data, you keep only that much backups.


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.


I'm using fedora coreos to run nextcloud on a cheap old workstation. It took some work to get the configuration right, but I'm very impressed by how little maintenance I need to do (so far none at all).

If anyone is interested in doing the same, my configuration can be found here for inspiration: https://github.com/jeppester/coreos-nextcloud


The quadlet + MicroOS (or any other Atomic distro i.e. Fedora CoreOS) is a very powerful combo; I've been on the slow process of migrating all my nodes over to MicroOS and pushing for it or something similar at work. The combo of automatic rollbacks for base OS and declarative container configs+auto-updates feels lock they just slot together.


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


Alas :( my phone is fine scrolling at 120hz with the effect (iPhone 15 pro max)


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

Search: