I wasn’t around much before GitHub so. I believe I tried submitting patches to the XFCE project but I didn’t get anything accepted to FOSS before GitHub.

In this type of system, if I am competent and can contribute how to do I? By reviewing the maintainers PRs, helping fill out more info for bug reports / root causing?

There had to be some way for a competent user to get involved enough to become a familiar handle to the maintainers and be seen as a possible future maintainer/ expert contributor right?

That’s all well and good, but making that dataset also means it will be leaked

how does my spiritual wellness affect the mechanical structure of my lower back?

Ignoring the spiritual part, emotional state does have a well-known feedback loop with physical state. There’s a (largely incorrect) idea in pop psychology that just as happiness leads to smiling, smiling leads to happiness. It’s not nearly that simple, but there are some more straightforward examples: lots of tense emotional states (anger, anxiety) lead to tense muscles (jaw being the classic example). Relaxing your jaw can lead to a (temporary) relaxation of your emotional tenseness. I’ve never heard of a similar result for the lower back, but it’s not hard to imagine. If nothing else, they must be correlated through sedentary lifestyle.

> (largely incorrect) ... just as happiness leads to smiling, smiling leads to happiness.

I don't have a citation to hand and it's really old but there was academic research supporting that at some point. IIRC they used some clever request to get people to move their facial muscles in various ways without tipping them off about what was really going on and then asked them lots of questions that touch on emotional state.

Functional disorders are a thing, and placebo surgery for osteoarthritis of the knee works just as well as real surgery: https://www.nejm.org/doi/full/10.1056/NEJMoa013259

I have heard psychedelics be described as the most effective placebo of all placebos.

By directing your attention towards, or away from, physical phenomena that mechanically affect your lower back: overexertion, underexertion, posture, nutrient intake, crowd...

Setting the woo aside, there is a lot of data on disorders like central sensitization syndrome that show our psychological state has a very strong modulating effect on our perception of pain.

I mean tons of back pain is medically unexplained. It's not like physiology has a perfect record here that can be used to dismiss alternative theories.

Thankfully, you don't need a perfect record to dismiss theories like "a wizard did it."

There's a really neat book called Gift of the Raven about an athlete with chronic knee pain that doctors couldn't figure out any plan to stop. He rowed from Alaska to Siberia and the book goes on about a shaman that performs a healing ritual (psychedelic mushrooms were involved) and he finds himself cured. So, there are times I suppose when the pain is all in your head, and maybe has a feedback loop since pain will also cause muscle contraction which can pull bones out of alignment. Relax enough and the pain stops.

Relieved to learn that my small peen is merely a projection of my energetic spiritual being.

I feel like you missed a turn somewhere.

You can disable extensions and download them in advance and load those from file path. This is how I’m pinning extensions for a self hosted version of duckdb I setup at work.

Keep your friends close and your enemies closer

Yet the Linux kernel is a monorepo

The Linux kernel is pretty small

Try google3

Yeah, but no needs to pay for software SaaS anymore so no-one is going to be getting a lucky 100MRR business off pure vibecoded software as anyone can just make that in house.

You can ack based on groups, and you can out users into groups. So if you auth a node, it’s now your node and the ACL for your user / group will apply.

But yes I don’t think you can ACL based o the hostname

Hi there, I work at Tailscale.

Part of the reason that we don't (currently) let you do this is that a hostname is a user-reported field, and can change over time; it's not a durable form of identity that you can write ACLs on. One could imagine, for example:

1. Creating an ACL rule that allows hostname "webserver" to hostname "db".

2. (time passes)

3. Hostname "webserver" is deleted/changed to "web"/etc.

4. Someone can now register a user device with the system hostname set to "webserver"

Should they be allowed to inherit the pre-existing ACL rule?

However, you can accomplish something very close to what you're asking for, I think, by defining a "host" in the policy file (https://tailscale.com/docs/reference/syntax/policy-file#host...) that points to a single Tailscale IP. Since we don't allow non-admins to change their Tailscale IP, this uniquely identifies a single device even if the hostname changes, and thus you can write a policy similar to:

  "hosts": {
    "myhost": "100.64.1.2",
  },
  "grants": [
    {
      "src": ["myhost"],
      "dst": ["tag:db"],
    },
  ]

Yes I noticed that when designing our ACL usage. I didn’t find it all that useful unless we were inheriting some non tailscale systems with static IPs that we were going to subnet proxy to w/ tailscale.

Tags are just a better way to do this for tailscale only nodes, as now the ACL doesn’t require any change during a device key rotation.

That's why my next instinct was to try specifying a node key, which does not change unless the device is re-registered, but that does not work either.

We run nomad at work. I’m very happy with it from an administrative standpoint.

I believe you can disable this and it isn’t really required for TS to work