It would be extremely barebones, but you can do something like this with Pandoc.

That I agree with. Microsoft drafted the recommendation to use it for local networks, and Apple ignored it or co-opted it for mDNS.

Macs aren’t the only thing that use mDNS, either. I have a host monitoring solution that I wrote that uses it.

Yeah, that’s why I started using .lan.

I was using .local, but it ran into too many conflicts with an mDNS service I host and vice versa. I switched to .lan, but I’m certainly not going to switch to .internal unless another conflict surfaces.

I’ve also developed a host-monitoring solution that uses mDNS, so I’m not about to break my own software. 😅

Coincidentally, I just found this other thread that mentions EasyEffects: https://programming.dev/post/17612973

You might be able to use a virtual device to get it working for your use case.

It depends on the model you run. Mistral, Gemma, or Phi are great for a majority of devices, even with CPU or integrated graphics inference.

Show me a music store I can purchase music from on my phone through an app, and I’ll purchase it.

My go-to solution for this is the Android FolderSync app with an SFTP connection.

Correction: migrated to GitLab, but I don’t expect they’ll want to keep it there.

The Nuzu repository is already wiped.

I was going to recommend Ansible as well - documentation as code can never be out of date if you continue using it.

I wonder the same thing, to be honest.

It doesn’t quite say that, but I think the meaning is essentially the same: “Don’t choose a name after a project unique to that machine.” - RFC 1178

For my homelab, I think that’s fine to do. I’m unlikely to have multiple Plex servers locally, for example, and if so, numerically naming them is fine - I provision with Ansible, and if I’m at the point where I’m having sequentially numbered hosts, they’ll be configured as cattle anyway. Also, having the names reflect the services a host provides makes it easier to match in my playbooks.

I think it’s a better scheme than turning to mythology, fiction, or animal species, which oddly enough RFC 1178 does encourage you to do.

I use significant hardware component or model:

• Z390
• AERO15

…or sometimes intended purpose:

• USERV - Ubuntu SERVer
• PlexBox - Plex Server
• NAS - NAS
• Runner - GitLab Runner
• MDEV - Mobile DEVelopment
• MDEV2 - Mobile DEVelopment, Version 2

I also have a Kubernetes cluster that ranges from K8S_0 to K8S_5.

I’m still using the old docker-compose executable - my Docker role is still installing it until the Ansible module catches up.

I’ve done something similar, but I’m using compose files orchestrated by Ansible instead.