HN user

caeruleus

87 karma
Posts1
Comments34
View on HN

Prefixing commands solves the namespace problem and discoverability (at least partly). I use a slightly more sophisticated method, which helps me remember which custom utilities are available and how to use them: sd [1], a light wrapper written for zsh that, in addition to namespaces, provides autocompletion, custom help texts + some other QoL enhancements. Can definitely recommend if you're looking for something a bit more fancy.

[1] https://github.com/ianthehenry/sd

I recognize that my initial statement comes off as too broad in light of theoretical computability, when I was mostly weighing in terms of current/near-term technology. Given what we know today, I would (still cautiously) agree with your statement. There hasn't been any evidence to the contrary (only some highly contested speculation, most prominently by Roger Penrose).

You're raising some intriguing points, and I agree with your assertion about the epigenome. I still feel like your response misses the point I was making.

followed by examples of things that are encoded by DNA

... given its natural environment. A nucleobase sequence is not a symbolic language, it relies on physical laws in general and a defined chemical environment in particular (that it helps to create and maintain) to mean something. It's similar to the point about Othello vs. the physical world in the article: The language itself does not encode every bit of information about the world it describes. For instance, in 3D space, regions of DNA that are far apart in the sequence can physically interact and influence each other’s expression.

TLDR: I think my point is that a base sequence requires a particular context (~ interpreter/knowledge about the physical world) to encode mostly everything about life. Treating it as just a language in the context of LLMs abstracts away the complex substrate that makes it work.

I don't believe the concept of DNA can be reduced to a sequence of quaternary numerals, which is what gene sequence data would represent. Similar to proteins, DNA forms higher-level structures on top of the primary one [1], and (in a biological context, inside the nucleus) exhibits somewhat self-modifying [2] and self-regulating [3] behavior as well as meta-modification [4]. Analogous to the article, if one defines the language of DNA by its nucleobase sequence, this language can only represent a subset of the world of DNA.

Somewhat related, the way the adaptive immune system works has similarities with some concepts in machine learning. In this process, sections of nuclear DNA serve as randomly initialized weights in precursor cells [5] as well as final weights in memory cells. There's even fine-tuning of the weights. [6]

[1] https://en.wikipedia.org/wiki/Nucleic_acid_structure [2] https://en.wikipedia.org/wiki/Transposable_element [3] https://en.wikipedia.org/wiki/Transcriptional_regulation [4] https://en.wikipedia.org/wiki/Epigenetics [5] https://en.wikipedia.org/wiki/V(D)J_recombination [6] https://en.wikipedia.org/wiki/Affinity_maturation

The stew style, which seems to have been recalled as well, is my favorite instant ramen since it's very rich in flavor and has thick noodles. I usually add a couple of fresh Thai chilies (Prik Kee Noo) into the broth, it's not that spicy - though it's usually too much for people who can't handle capsaicin at all. Can't speak for the other ones though.

This feels like an overreaction by some bureaucrats which could have been handled with a warning sticker instead.

Edit: Per https://www.koreatimes.co.kr/www/nation/2024/06/281_376457.h..., the 3x has 13000 SHU, the 2x 10000, stew type was not mentioned, but a quick search claims ~4700.

This should have been pretty obvious for more technical people, but it's a nice introduction into networking and VPNs. I have configured a Linux VPN gateway VM a couple of times now and the reliance on the routing table only always felt brittle, especially when paired with running on the same machine that uses the connection.

In addition to network namespaces and physical VPN gateway routers, an architecture based on VMs can thus also solve this. In my homelab, the firewall blocks any unexpected traffic from the VPN gateway VM (devices in the VPN VLAN are not allowed any outgoing connections, the gateway VM has a separate VLAN for outgoing ones). As a personal solution, QubesOS makes configuring a similar setup quite friction-less, but once again requires more technical knowledge than a regular OS.

There's a nuance to this that I haven't seen mentioned so far:

With this law, Cannabis will be removed from the list of scheduled drugs and turned into a simple prescription drug. It will be a lot less complicated to prescribe medical Cannabis.

Looking forward! Thanks for maintaining such an awesome library btw, most of my internal PKI (X.509 and OpenSSH) is managed with it. It's a bliss to work with, even more so compared to other crypto libs. :)

Prefixing these utility scripts is a nice tip, I used to do that as well.

Some time ago I found sd [1] though. It's a light wrapper around your own scripts which provides namespaces, autocompletion, custom help texts + some other QoL enhancements around that. It improves discoverability and usability a lot, very happy with it.

[1] https://github.com/ianthehenry/sd

I have been using Yabai for two years now and am very happy. For me, it's stable and you can script almost anything by using event reactors.

Yabai also makes working with a 15" display much more productive imho. For example, I can effortlessly and nearly instantaneously switch between browser and coding spaces by pressing hyper + w / hyper + c (I'm using Karabiner Elements to map capslock to hyper).

Since it's a common misconception, you do NOT need to disable SIP if you don't care about some features (noticeably, disabling those nasty space switch animations). For an overview of features that require SIP to be partially disabled:

https://github.com/koekeishiya/yabai/issues/1863

Also in general, the wiki on GitHub is very well-written.

GitHub was down 3 years ago

Notice that there were issues with Slack notifications only before:

The delayed Slack notifications should be fully processed in about 30 minutes (Nov 03, 2023 - 18:25 UTC)

Exactly 30 min after:

(Git Operations|Issues|Pull Requests|Actions|API Requests|Codespaces|Packages|Actions|Pages) is experiencing degraded performance. We are continuing to investigate. (Nov 03, 2023 - 18:55 UTC)

Might be coincidence, might not be...

Yup, Firefox for me as well. Chromium-based browsers seem to sanitize the title.

I'm frankly a bit surprised that at least Linux and MacOS allow control characters in window titles and wonder if there is any reason to do so.

Imagine someone pwning your OS via an HTML tag.

Opening this site actually crashes my Yabai status bar widget on MacOS. What an unexpected and nice troll. Lol.

It contains the raw byte of 0x1b (ESC) in the title (before [31m), which colors the following text red in the context of a terminal. The browser title is reported to Übersicht, which apparently fails to serialize it to proper JSON and thus crashes simple-bar with a JSON decode error, removing the overview of my spaces. Everything is back to normal once I change my browser tab.

It was mentioned they were receiving footage continuously. I think when all monitors are shown, in the middle you can discern pictures being rendered.

Edit: They called this out now, it seems those are live pictures.

This is called Taarof and can be at times quite extreme: https://en.wikipedia.org/wiki/Taarof.

I have a good friend whose parents are from Persia/Iran. He told me about this culture after we knew each other for quite some time. Even though he has never lived there, he often still has a hard time not to do this, which has resulted in some funny (at least for his friends) or uncomfortable situations over time. Knowing this, many things I ascribed to his character alone suddenly made a bit more sense.

This succinct style of reporting reminds me of how surgeons are taught to report on a patient (to colleagues):

  1. name/age/gender
  2. current problem (+ potentially relevant preexisting condition)
  3. relevant clinical/laboratory findings
  4. suspected cause
  5. recommended actions
  6. If an operation is planned: general health assessment (ASA)/allergies
  7. prognosis/miscellaneous notes
As a rule of thumb, non-surgical medical professionals have a similar framework, but will report more in-depth and less focused on a singular logical path.

Peep, anyone there?

Wow, for me it looked like the world had gone mad. This is a reminder to not only rely on 1.1.1.1 for DNS resolution in PiHole.

I host most of my services locally, but ironically could not connect to my own homelab. I use a dedicated domain with DynDNS and did not configure the network and DNS without reliance on external DNS. Surely it's infinitely more likely for me to make a mistake, right?

Last year, I started setting up a Qubes OS workstation. Doing all the intricate little steps manually seemed like such a waste of time that I started learning SaltStack, which is built into the Qubes management stack, to be able to automate and replicate the setup. This small itch exploded in such a way that I wrote a formula for almost every program on every system and server I use. For all other small programs, I just use one formula that syncs the appropriate dotfiles (I can also template them with Jinja).

In hindsight, going with Nix would have been the most efficient way to reach most of that, apart from the Qubes-specific stuff. This will probably be the next step on my (ironic) odyssey of going all-in on configuration to finally stop worrying about it and reap the benefits of the beauty that is computing without its nasty warts.

In essence, I would love a proper integration between Nix and Qubes OS.

Edit: For anyone interested in an example of my current process, see https://github.com/lkubb/salt-tool-chromium-formula, https://github.com/lkubb/salt-tool-gpg-formula or https://github.com/lkubb/salt-tool-macos-formula.

Afaik, it is specific to this provider. I'm not entirely sure why exactly tbh, probably to require some kind of associated identity (the policy is likely targeted to larger providers). It was a manual process and I never had to do anything similar for a different one.

They require that

a) the sending IP address has a PTR record b) from a domain that you own c) that resolves to the same IP address.

This is also very important for general deliverability (https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS).

They furthermore recommend d) that your host name should clearly mark it as a mail server and e) to make sure the domain leads to a web page that contains provider details and contact information.