No. POWER and PPC are decidedly not the same. the closest they ever came together was the G5's 970.
4xx and 75x were OK for embedded a decade ago, but today they're hot and power hungry. You can use them in devices where you can burn 10+ watts to maintain backwards compact with existing PPC code, but they're way the fuck too hot for a phone.
There are differences in details about uncommon instructions, irrelevant assembly language changes, some instructions privileged for one arch and not the other, that kind of things.
But for the bulk of the ISA, it's the same. You probably can create a single userspace binary compatible with both? Not sure but seems doable.
The microarch is likely different but then it is also different between several members of each category, so the word does not really designates the micro-arch, but really the ISA. And then you have other brand names using that, and they are so similar that e.g. Freescale switched from PowerPC to Power while incrementing PowerQUICC II to III. I remember Linux has an eieio macro that just emits the aforesaid instruction for PPC, and actually the opcode does something similar on Power (mbar) and IIRC the assembler is happy to emit it regardless of the ISA.
So it was kind of messy when you reached the differences, but everything was quickly workable and you got use to it. The reference manuals of Freescale are very good and the "[...]Programmer’s Reference Manual for Freescale Power Architecture Processors" EREF_RM often directly points at the few differences with PowerPC.
POWER and Power (formerly PowerPC) are similar but quite different. PPC has been in embedded (but generally not mobile) for quite a long time, but even then, the cores are still hot, power hungry, and poorly suited for mobile.
Because the designs predate the big push into extremely high efficiency processors. Like the big "server class" processors, the investment required to create a truly high efficiency processor is quite large. Small in-order cores with limited functional units, and lacking much of what makes a modern processor fast (vector units, specialty instructions/etc) can fool people into thinking that minimal clock domains/gating is sufficient to create a high efficiency design.
regular "app based" is just OATH-TOTP in most cases. This uses a shared secret and the time to generate one time codes.
The Yubikey explicitly supports TOTP, and will happily store your secret on the key. You can then use Yubioath to pull codes from the Yubikey as needed.
I'm a huge fan of the ability to use either U2F or TOTP with the same hardware token.
What benefit do you provide over the Indian place down the block with similar or even cheaper pricing? These prices are absurdly expensive even for us overpaid tech folk.
Our main differentiator is specifying the macronutrients and allowing you to pick between different macronutrient profiles. You're not likely to get that at your local Indian place.
For a spinach curry (saag or saag paneer), yes, $12 is very expensive.
In my local asian grocery store, they stock a lot of vacuum packed Indian meals, all of which have nothing "dodgy" in the list of ingredients, and all of which are actually really good - they cost the equivelant of around $2.5 each.
My local Indian takeaway restaurants sell saag paneer for around $4 USD.
I mean... that's my point. I can plan ahead and pay $12 to have something delivered and then heat it up myself, or I can pay $12 to pick it up already hot and ready to eat, on demand.
Like it or not, vernacular changes. Today, in most contexts, "sysadmin" suggests (at worst) a Windows pusher armed with a mouse and (at best) a heads-down computer toucher (which is also what this "devops consultant" document seems to outline, really, so you're not wrong!).
You're totally right in that sysadmins can certainly practice (part of) devops, but anywhere I've ever gone it's less the rule then the exception and "sysadmin" is a career-limiting classification, akin to calling oneself a programmer [0]. Ends, not means, etc.
certainly won't disagree that it can be limiting to folks of some perspectives, but as someone who publicly has applied the sysadmin label for the duration of their career (starting in the early 00's), I've yet to see a downside.
I've been obscenely compensated for working on interesting projects for much of my career. then again, part of it may be due to the confidence that comes with focusing on my work instead of fluffing my title.
You also, candidly, may be experienced enough and have enough time-served to get away with it. ;) There's definitely an effect--I kinda want to call it a thermocline?--above which your actual achievements can speak for themselves, particularly if you've built a solid network.
Today, if I had a notion to, I could probably call myself a "sysadmin" and not have trouble finding well-compensated work. But when I was freelancing, as well as when I was earlier in my career, I can tell you a lot of doors would have slammed right shut had I used the term regardless of my capacity. I do not particularly love the term "devops", but at this point its umbrella at least encompasses what we (like, you and I, not the general we) think about when we're doing this stuff, and it has a certain amount of loaned--or stolen--credibility.
As I said in a top-level comment, I'm more twitchy at this description of being a consultant than I am at the devops part.
e2ee can be turned off client side (and is off by default until ux improves), and while I don't think it's possible with the stock home server, it seems entirely possible to patch the home server to reject encrypt requests, and only federate unencrypted rooms
for directory service, LDAP and web SSO are both supported
We weren't actually using Slack. There are self-hosted alternatives.
You can also add a TOTP code to the command to get 2FA if you're really worried about limiting the attack vector - I actually gave a conference talk about that years ago.
2) Drugs. This has been my number one use for cannabis. If I need to go to sleep early for what ever reason, I smoke a bowl, lie down, and am out in no time.
It's all about shoving a ton of hot power hungry multithread cores as close together as you can and running them at full bore.