My favorite French borrowings are gentle, genteel and jaunty. All borrowed from gentil (kind, pleasant, nice), but at different times (13th century, late 16th, and 17th, respectively).

The French word is from Latin gentilis, meaning “of the Roman clan.” English borrowed that from Latin as gentile.

So we have 4 English words, all from the same Latin origin. Of them, genteel is probably closest to the Old French pronunciation (but the vowels are still a little bit different).

put the phone to my ear

Clearly you would look more normal if you blast it on the speaker while holding the phone in front of you, like everyone else. /s

It’s funny that there are two unambiguous alternatives to bimonthly, but they both mean 2x/month: fortnightly and semimonthly.

Both German and Dutch distinguish their equivalent words with clear prefixes meaning half- and two-. The English word was unclear after 1066 since the French word bimensuel would have been used by the new bosses. And that means 2x/month. English used bimensual for a while before developing a new, worse word with the Latin origin bi- and the Germanic origin -monthly. And it seems to have been ambiguous from the start. So this has probably been messed up for almost 1050 years.

Maybe we should resurrect the Old English prefix twi- to make a new(old) 1x/2months word twimonthly or more intuitively, twomonthly that we can use in opposition with halfmonthly.

That and the shrinking ability to grant access to device storage. If that becomes an option only on rooted phones (which seems like the directly Google is heading) it will make the audience for such an app much smaller.

If you’re buying new cameras they’ll be 802.3af PoE. Passive is becoming much less common. So that model router I linked would work great.

I think if you’re a moderately technically inclined person you would be happy with that solution. If you are intimidated at the idea of writing or adapting some scripts, I would probably recommend a router on one of the other platforms plus a PoE switch.

The easiest part of your requirements are the custom DNS records. All of the platforms recommended so far can do this. OpenWRT has the advantage of WiFi capabilities. If you want the router to also be your WiFi access point then it may be your best option. But it sounds like you only need it to be a wired router, which is good.

As far as the ad blocking, I have done this with pi-hole, and with the built-in DNS and block capabilities of OpenWRT, Mikrotik and OPNSense. They are all fine. The router ones don’t have the fancy web UI like pi-hole. So if you use that a lot you will be disappointed. Mikrotik’s is the most basic and a new feature for them, but they are actively developing it. Plus their current routers can run containers, so you can run pi-hole on the router as a container if you want.

PoE ports as a requirement is what narrows your options considerably I think. You could get that from a separate switch. If you want that in the router itself then you have very few options.

Mikrotik has a lot of routers with PoE out. Their newest model in the RB5009 series can do either passive or 802.3af/at PoE out. Many of their older routers have passive PoE only. Make sure you know what your cameras need.

I had similar requirements as you and got this: https://mikrotik.com/product/rb5009upr_s_in

It has PoE out available on all 8 Ethernet ports. The default 48v power supply works with 802.3af/at PoE. It is a 96 watt supply, and can support ~76 watts of PoE downstream. If you need passive PoE then you would need to change to a 24v power supply.

Mikrotik RouterOS requires some learning to use its advanced features, but their quick setup defaults are good. And the platform is super reliable and flexible.

For DNS you would use their Adlist functionality along with a script similar to the one from BartoszP in this thread to enable DNS name resolution for lan hosts: https://forum.mikrotik.com/viewtopic.php?t=181640. That script is added to the DHCP server config to run when each client gets an address lease. And then you would add static name records in IP / DNS / Static for the other host.domain names you want your lan devices to connect to by name which can’t be resolved via your upstream DNS server.

I will gladly die on this hill.

Obviously! Well done. Your definition is delusional and at odds with science and common language use, yet you won’t back down. That takes commitment. It also has me questioning whether you believe in light outside human perception (since it’s also measured as a wave). You are the embodiment of this fun thread! And I genuinely enjoy thinking about both positions.

But I think I’ll stick with the Wikipedia and dictionary editors, and the likes of Britannica which states:

Sound, a mechanical disturbance from a state of equilibrium that propagates through an elastic material medium. A purely subjective definition of sound is also possible, as that which is perceived by the ear, but such a definition is not particularly illuminating and is unduly restrictive, for it is useful to speak of sounds that cannot be heard by the human ear, such as those that are produced by dog whistles or by sonar equipment.

I appreciate your hill. But several sources disagree with you.

Wikipedia: “In physics, sound is a vibration that propagates as an acoustic wave through a transmission medium such as a gas, liquid or solid.”

Oxford: “1. vibrations that travel through the air or another medium and can be heard when they reach a person’s or animal’s ear.”

Webster: “1.c: mechanical radiant energy that is transmitted by longitudinal pressure waves in a material medium (such as air) and is the objective cause of hearing”

Cambridge: “something that you can hear or that can be heard”

These don’t seem to require the ear for the vibrations to be sounds in and of themselves. Only that it would be detectable by an ear if an ear were present.

Upon what do you base your assertion that it is the hearing of the thing that is the most essential requirement? (And given the thread I think it’s perfectly reasonably for the answer to be something like “because it’s my hill dammit!”)

Neat. It has a wikipedia article as well.

It makes sense. But as a US speaker it just makes me want to stick to my guns and generalize our second syllable stress on these units. I’m team kilogram now. And centimeter.

Found a new hill!

It’s amazing that they can measure the speed of sound at all given this. They must need to line up a bunch of eardrums.

That’s my take too. Short for “this requires you to follow a steep learning curve, even if it is not easy to do so.”

Ha! Well I was just having a laugh. Expecting that you would prefer “you should damp your expectations” and that my construction should mean “make your expectations wet.” And it turns out dampen is ambiguous. It means both moisten and dull, deaden, make weak.

Not only that, but most every form carries both meanings, and the “weaken” sense for the word damp predates the “humid” sense. Because the noun came first and it was specific to suffocating fumes in a mine that would extinguish candles, and people.

So my take now is that dampening means both “making weak” and “humidifying, moistening.” Only damping is specific to motion/energy. And I can’t recall encountering anyone using damping to mean “making wet.”

That’s a great point. Water heaters heat hot water much more often than cold water. Maintaining the already elevated temperature.

You should probably dampen your expectations on this one.

I tasted the rainbow 🌈

Nice, I’ll check it out! I remember LMS and Squeezebox. Didn’t know it would sync between rooms, and I didn’t know it had been open sourced, that’s excellent.

At the time we started in the Sonos ecosystem we wanted easy, and it provided that. Now I’ve got multiple servers running, self-hosting services for the family, slowly working on removing our cloud service dependencies. So this would fit right in.

Yeah, I get what you’re saying. Definitely. It’s not complicated for one pair of speakers in one room. For one music source. For one person controlling it.

There just haven’t been any better cost-effective solutions with multi-room, control from your any phone convenience. And that’s a big plus for how we listen to music. Today there are a few contenders, but many of them are also cloud dependent. Really the small number of good options in this space is proof of how good Sonos was for a long time. Well and also of Spotify causing people ditch the idea of a offline digital music library.

Edit: And to be clear, aside from the “any computer networks” part, this is what the original Sonos device did. It could work without a home network, but worked best with a shared music library on a PC. Didn’t need cloud anything, internet connection, account, etc. You just hooked your normal speakers to it and it played music.

That SATA port is what you need. You can use that to connect an external eSATA drive enclosure (external jbod).

For a clean install, get a SATA to eSATA adapter - the kind with an expansion slot plate. Something like a STCESATAPLT1LP. Unscrew the eSATA end from the plate, cut a matching hole in the PC case and mount the port to the hole. This is better than going straight from the internal port in my opinion.

It looks like you have a mini-PCIe slot as well, probably intended for WiFi. That may work with an mSATA to SATA adapter to give you a second port. Or it may work with an mSATA SSD. I would test with something cheap or get confirmation it works from other users of this PC before investing in an expensive SSD.

VPN + DDNS is what I do. You may be thinking about the perf hit of putting all your home connections through a VPN. That’s not the idea here. For self hosted services you would set up a wireguard “server” at your house. Then you connect your phone back to it to access your services.

With Wireguard it’s pretty easy to do a split tunnel, so that the VPN connection is only used for traffic to your home servers. Nothing else is affected, and you have access to your house all the time.

This is better for security than DDNS + open ports, because you only need a single open UDP port. Port scanners won’t see that you are hosting services and you wouldn’t need to build mitigations for service-specific attacks.

As far as podman, I am migrating to it from a mix of native and docker services. I agree with others that getting things set up with Docker first will be easier. But having podman as an end goal is good. Daemonless and rootless are big benefits. As are being able to manage it as systemd units via quadlets.