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!

Not to mention mortgage interest.

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!

Add to that photo editing (as much as GIMP is great…). I would guess DAW and video editing would fall under that category, too…and good luck finding many AAA open source games.

You can roll your own saline nasal rinse, but it takes a little care to get the salinity just right. And best to boil the water first in case of brain eating amoebas (seriously — not common, but very, very bad).

We have one kid, one one the way, and then it’s time for a Balls Voyage party (or snipped but still equipped, if you prefer).

I would be very surprised if such a fork would diverge from Linux. I would guess that this would be little more than a branch with (most likely) support for Russian hardware. Just my hunch.

A legitimate hard fork doesn’t seem particularly smart to me, but what do I know…

My headcanon for The Matrix’s “humans are batteries” is that it’s the machines’ perverse interpretation of this — killing the humans is off the table, and for whatever reason letting them live with no purpose to serve the machines is also disallowed. But giving their lives “meaning” in the form of a shitty (and thermodynamically dubious) “battery” somehow satisfies the rules.

It’s a very big stretch, I’ll admit…

https://en.m.wikipedia.org/wiki/867-5309/Jenny

Duh, just read it back from /dev/random

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

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.

If you have a TV, you likely already have the receiving device. Antenna can cost, or you can play around with wire length and orientation.

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.

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.

The one I’ve heard replaces “brains” with “money.”

It can be daunting to get into the hobby, there are a ton of niches.

To start: where are you? I’m in the USA, so that’s where my experience is.

License: required to transmit on the ham bands; you can listen without a license.

Range: are you looking to talk to people in your city/region? If so, a cheap “walkie-talkie” style (called “HT” in the biz — best avoid “walkie-talkie”) is a good place to start. These VHF/UHF (very/ultra high frequency) radios are affordable — something from Baofeng(~$30) or similar will work just fine, though they are often looked down on (I have one — for the price, it’s great). You will have the most luck if there is an active ham scene in your area, in large part because they may have a repeater, which can greatly extend your range. Many regions will have scheduled “nets” where you just go around and chat.

If you’re looking for the ability to chat with folks on the other side of the world, you’ll want to look into HF (high frequency). This is much lower frequency, thus longer wavelength, than the handheld VHF/UHF HTs. So…the antennas take up a lot of space. Mine is 52 feet long, in the attic. And the radios are much more expensive (more like $1k new). ICOM 7300, Yaesu FT710 are popular entry level units (but you also need power supply, cables, and antenna).

That said: if you just want to listen to HF, the antenna doesn’t matter as much at all, and you can use an SDR (RTL-SDR probably works?) for listening. You can probably also find a used shortwave radio that covers some of the HF ham bands.