Especially as the nice response is “we’ve had feedback about that app from too few users to support it, unless you’d like to try”.

Or, pretty much any other response.

I trialled both a while ago, chose ummich asits face recognition was superior.

There were other reasons, but I’ve forgotten them.

I bought a refurbished SFF PC and put a PCIe NIC in it. Installed opnSense.

Cheap as chips. Supremely powerful.

I still double-check my CIDR’s/netmasks and expected ranges with a tool (some online one or other). Easier to avoid silly mistakes or typo’s

TL;DR: it depends entirely on the DHCP server software.

Generally the safe/reliable policy is to assign a smaller DHCP range (or ranges) and allocate static assignments outside of the DHCP range(s).

Assume your network is 192.168.1.0/24.

Specify 192.168.1.128/25 for DHCP, which means all DHCP addresses will be above 192.168.1.128.

This leaves you everything below 192.168.1.127 for static assignments.

Amazing. I get there’s some atlassian bullshittery behind that.

There’s also a draw.io (diagrams.net) plugin for intellij and probably eclipse.

I’ve used coreos happily on homelab bare metal.

PXE booting it with cloudinit/ignition automation for provisioning.

It’s make for an excellent VPS.

They do!

See their Era, Mood, Ridge, Terra cases.

I, for one, welcome our new AI overlords.

Had a similar incident with my son’s hand-me-down laptop. It just sits on a desk with a monitor and what-not plugged into it. It’s now a wide flat desktop.

Don’t set the static IP within the DHCP range (well you can, but it then depends on how smart your dhcp server is, just avoid the situation).

You run a risk of the same IP being assigned to another device.

Didn’t know about them!

I personally use GitHub pages for mine, now.

Static website? Upload to S3 via CI and serve it from there.

It’ll cost cents per month.

K8s is obscene overkill.

I assume all the cloud vendors have an S3 equivalent.

Service guarantees citizenship!