Thank you for verifying 🙂

Hm, my guess would be either “cube control” or “cube C-T-L”.

EDIT (2025-02-28T09:02Z): Hm, actually, given that it’s for Kubernetes ^[1], maybe it’s “koob control” or “koob C-T-L”… ^[2]?

Do you mean /ɲiɲks/?

Here are the sounds for each:

• ɲ ^[1]
• ŋ ^[2]

…it’s not “curl”?

EDIT (2025-02-27T04:15Z):

cURL (pronounced like “curl”, /kɜːrl/) […] [1]

🤔

A likely comparatively barebones (but sufficient for my needs) solution that I use is Obsidian with Synching.

What specific features are you looking for?

Neat!

Can you ping the Jellyfish server from the laptop? Can any other device access the Jellyfish server?

At least with Windows, most people know what its normally like at home, but thats less true for Linux.

Yeah, that’s a fair point that they wouldn’t have a comparison, so they wouldn’t know if it’s always like that. One could perhaps make an educated guess, depending on circumstance, but, without any first-hand experience or exposure, it would be just that: a guess.

Hm, but I’m not sure people would attribute that to the design of the underlying OS itself rather than just the employer. Like do those people with restrictions on Windows blame Microsoft? It’d be the same as someone blaming the Linux maintainers for employer placed restrictions on an OS running Linux. Don’t get me wrong, I’m sure someone would still do that, but I’m not convinced that the majority would think that way — I think most people would be able to make the distinction.

I still expect it to be done in the open, one of the things Munich got right was upstreaming all their changes, which meant that even when it was cancelled, nothing was lost. Maintaining out of tree changes is just way to much work

Would you be able to cite a source for this Munich program? I’d like to read more about it.

Only the end-users would have rights to the source under GPL, and its unlikely that someone is going to risk their job by releasing the code.

Fair point. So I suppose that would be the employees using the distribution rather than the entire populace.

Edit: on the GPL front, GPL doesn’t require that you publish your code to everyone, just to the recipients of your binaries. And you only have to give it upon request. So they definitely could keep it somewhat under wraps if they wanted to.

When I said “hidden from the public”, I was meaning refusing to disclose the source code even when asked. I do wonder how the laws would apply to government organizations violating copyright 🤔. Like what if it was the OS for some defense system? I’m not sure a government would be too keen on disclosing that — even if it was requested though some sort of freedom of information request (if the respective country has that) — and would rather classify it and refuse to disclose regardless of the license. I’m not aware of any precedent of this.

[…] but its never a nice experience […]

Why’s that?

Based.

a really locked down/limited system might not be a step forward at all

Depends what you mean. Locked down as in hidden from the public (I don’t think that’s legal anyways because of the GPL) would be bad. But locked down/limited from employees so that they can’t bork the system is good, imo.

I will preface by saying that I am not casting doubt on your claim, I’m simply curious: What is the rationale behind why it would be so unlikely for such an exploit to occur? What rationale causes you to be so confident?

Looks like a Fractal Node 304?

Yep! I’ve found that the case is possibly a little too cramped for my liking — I’m not overly fond of the placement of the drive bay hangars — but overall it’s been alright. It’s definitely a nice form factor.

It wasn’t a deliberate choice. It was simply hardware that I already had available at the time. I have had no performance issues of note as a result of the hardware’s age, so I’ve seen no reason to upgrade it just yet.

Main Server

Services

• Jellyfin
• FreshRSS
• Borg
• Immich
• Nextcloud AIO
• RSS-Bridge

Hardware

• CPU: Intel Core i5-4460
• GPU: Nvidia GeForce GTX 760
• Memory: Kingston KHX1600C10D3/8G (8GB DDR3-1600)
• Motherboard: ASUS H81I-PLUS

OS

• Ubuntu 22.04.5 LTS

Reverse Proxy

Services

• Caddy

Hardware

• Rasbperry Pi 4 Model B Rev 1.5 (2GB)

OS

• Debian 12

Router

Hardware

• TP-Link Archer C7 AC1750

OS

• OpenWRT 23.05.5