I think there’s a bias in the US against this sort of thing that doesn’t exist (or not to the same extent) in Europe due to the age of the cities/buildings.

In the US, a building from the 1700s is a historic artifact to be cherished, while in parts of Europe a building from the 1500s is just the local pub.

So, the US is often hesitant to modify these old buildings, but Europe seems to have more of a perspective of “it’s a building, not a museum, let’s give it new life by modifying it.”

This is just from the perspective of me, from the US — and I think these old/new buildings are really neat!

Anybody want a peanut?

Janeway’s toilet would just be full of coffee that’s had the caffeine extracted. So…decaf. Blech!

IIRC that was the release that cleaned up the make output substantially.

Ok so it is fully qualified then? I’m just confused because it sounded like you were saying I wasn’t using the term correctly in your other comment.

Hmm, my understanding was that FQDN means that anyone will resolve the domain to e.g. the same IP address? Which is the case here (unless DNS rebinding mitigations or similar are employed) — but it doesn’t resolve to the same physical host in this case since it’s a private IP. Wikipedia:

A fully qualified domain name is distinguished by its lack of ambiguity in terms of DNS zone location in the hierarchy of DNS labels: it can be interpreted only in one way.

In my example, I can run nslookup jellyfin.myexample.com 8.8.8.8 and it resolves to what I expect (a local IP address).

But IANA network professional by any means, so maybe I’m misusing the term?

TIL, thanks. I use namecheap and haven’t had any problems (mikrorik router).

If you have your own domain name+control over the DNS entries, a cute trick you can use for Jellyfin is to set up a fully qualified DNS entry to point to your local (private) IP address.

So, you can have jellyfin.example.com point to 192.168.0.100 or similar. Inaccessible to the outside world (assuming you have your servers set up securely, no port forwarding), but local devices can access.

This is useful if you want to play on e.g. Chromecast/Google TV dongle but don’t want your traffic going over the Internet.

It’s a silly trick to work around the fact that these devices don’t always query the local DNS server (e.g., your router), so you need something fully qualified — but a private IP on a public DNS record works just fine!

Debian (i3 on laptop, headless on homelab).

But apparently my coffee is Arch.

Open to discussion, but since 2008, the Democrats have won every election where the leadership didn’t “put their finger on the scale” in the primaries/picking the candidate. Obama, Obama; Clinton arguably shouldn’t have been the nominee and Sanders should have; Biden was (?) properly primaries; Harris was picked — obvious pick, but still, not primaried.

Or the other reason, that the US is too sexist to elect a woman. It’s depressing either way of course.

The Democrats, in hindsight, fucked up with the economy and/or the messaging.

Did inflation happen because of the groundwork that Trump laid down in his term (not to mention global pandemic)? Sure — but did inflation get really bad under Biden? Yes, absolutely. That doesn’t make it his fault, but it makes it a problem that the Democrats probably needed to address more aggressively, an all-out attack on rising cost of living.

At the start of the pandemic, for me to carry $100 of normal weekly groceries home from the supermarket was a real challenge, but I could do it. Now, I carry $100 no problem, with a toddler on my shoulders. The money doesn’t really matter to me, but from what I’ve been reading, it really mattered to a lot of voters. Again: I think his will be worse under Trump (if it does get better, it’ll be due to some shady tax rebates to supermarkets or big ag or something, IMHO).

So while the Dems are talking about first time home credits and whatnot, Vance is out there lying about the price of eggs — but it’s a lie that “feels” right to a lot of people, and anecdotally, has some truth to it in that inflation/cost of living increase is real. Nevermind that the R policy is…what, exactly? But they say they’ll fix it, and they point out that Dems are currently in power, and that’s enough for a lot of people.

Duh, just read it back from /dev/random

You will recover the data, you just need to wait long enough.

Perhaps microwaving for significantly longer, at a low power level, would be safer and result in higher success/yield?

That’s how I started using Linux — big book with CD, I think it was “RedHat Linux Secrets 5.4” or something. 2.0 or 2.2 kernel.

Honestly, it was fantastic. And almost all of it is still relevant today. (Some of the stuff on xfree86 and the chap/pap stuff not so much.)

But it gave a really solid (IMHO) intro to a Linux/*NIX system, a solid overview of coreutils, etc. And while LILO has been long replaced, and afaik /sys didn’t exist at the time, it formed a good foundation.

I’ll refrain from commenting on any init system changes that have taken place since then.

You can also take a fairly selfish view and come to the same conclusion. Like, I don’t want to see homeless encampments, or really sick and untreated people, or panhandlers, or (…) while I’m walking around in my city. I can solve this problem by 1) moving to a nice suburb, or 2) having my tax dollars go to fix a problem that affects me. 1) is off the table because I want to live in the city, and 2) — while it helps the greater good — also helps me directly. (2 can also be addressed in a draconian fashion, which is not what I’m advocating at all.)

I think one problem is looking at things as zero sum. It’s not. If you are healthy and housed and fed then you’re not — to be very crass — an eyesore, you’re adding to the fabric of the city. I want street musicians who are playing for fun, not because they’re trying to make enough to afford dinner.

It’s mostly so that I can have SSL handled by nginx (and not per-service), and also for ease of hosting multiple services accessible via subdomains. So every service is its own subdomain.

Additionally, my internal network (as in, my physical LAN) does not have any port forwarding enabled — everything is over WireGuard to my VPS.

For a while I thought the Google AI result had a pretty logical, well thought out, practical solution — use glue.

I am devastated that I got rid of my 2000s HP LaserJet (with Ethernet). Only flaw it had was that it didn’t have a duplexer.

My method:

VPS with reverse proxy to my public facing services. This holds SSL certs, and communicates with home network through WireGuard link configured on my router.

Local computer with reverse proxy for all services. This also has SSL certs, and handles the same services as the VPS, so I can have local/LAN speeds. Additionally, it serves as a reverse proxy for all my private services, such as my router/switches/access point config pages, Jellyfin, etc.

No complaints, it mostly just works. I also have my router override DNS entries for my FQDN to resolve locally, so I use the same URL for accessing public services on my LAN.

As a long-time Debian user, I’d have to throw my vote behind Slackware for the title of most UNIX-y, which is I guess a bit different from most Linux-y.

Debian got me through grad school, but Slack got me through undergrad on a hopelessly underpowered old ThinkPad — Volkerding is a legend, and Slack will always be dear to my heart.