This is the separate entry so it can be ignored as pretty much irrelevant to the specific topic.
To make my sysadm life tolerable, I map every interaction based on a device organisation person role service model which works more or less with most traditional ways of modelling corporate designs.
I’ve done some things with the my model though, to allow me to rejig relationships between each of those basic constructs top down or bottom up without breaking stuff. Well hopefully not too badly, it’s still a WIP.
So they all exist as a
a = construct[rand()]
b = one to many
c = a||b
d = many to one
e = construct[rand()!=a]
a b c d e
Yup, I do have a soft spot for temporal 6NF database design.
There’s no rules to say any relationship can’t exist, but IRL folx only see some of the rules as reasonable, mainly due to the way language implements restrictions in our thinking. In my case English caused a lot of problems initially. In my albeit very limited experience, native thinkers of dialects that have a written expression in 漢語 similarly with עִבְרִית and I suspect the endonymically فارسی connected dialects, tend to have a different view of what consitutes a sensible relationship or one that’s absurd.
All this came about from the group of, tiny by international standards, SME’s who are my clients, who continually have hare-brained notions about restructuring their businesses, starting new ones, and spinning off potentially sellable parts, and moving staff between the business units on a part time during the day basis and providing adequate accounting of the costs.
A total administrative nightmare from the deeper regions of hell.
This led me to a layered administrative ownership of every business unit construct, which worked fine with a Personal, Local, Systems, Domain, Forest concept. I eventually needed a Goddess layer above Forest, read that as above Federated if you prefer, level which surprisingly fitted very well into the model, even when looped back to the extant structures to allow one meatbag to express multiple social instances without breaking any legal strictures. Being trans helps a lot with understanding this.
My tentative solution to the Tailscale IP for a device, before IP for a deviceperson, (machine, machineuser in your argot I think) becomes available, is to define a conceptual mesh network local administrator role on every device which is a, login once to set up the “Run unattended” thingy, then can be ignored from then on. Except it has to stay there forever on the login screen, and I’ll get continually pestered about why it exists and why it can’t be removed.
Will try to keep a close watch on yor forum, Github, and Twitter PointsOfPresence (?!) for where this goes. I get that’s it’s not a specific problem that I can file a bug report for, more a general, this is pretty much how we can make the cross-OS thing work.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐