holgersson

Fair enough. Im in devops and the first thing I thought about was Jenkins, where “server” and “agent” fit quite well.

I dont think master/slave is that good of a naming scheme for fault tolerance either, since the “slave” doesnt do work so that the master doesnt have to, but it’s rather an active/reserve kind of thing.

But I also admit that using different terms that fit best for every usecase would only cause more confusion than good.

We’re using server and agent, but im also a proponent of “captain” and “crew”

It’s simple: Either the project management team keeps the customer away from my time tracking or I’ll keep my time away from that customer

Chinese companies steal your data

Try Pixel

lol

Putting GrapheneOS on the Pixel is good advice though

Something marketing and having your service not appear dysfunctional or buggy to the stupid, stupid enduser