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.
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.
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.
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.
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.
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.
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
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.
You might consider reading up on reproducible builds. The majority of Debian packages can now be bit-for-bit rebuilt to verify the maintainer actually ships what they say they are.
users with totp tokens can kinit using their password+totp in the password field. better still, if you use PAM for all your services, you you can define hbac rules allowing users access to specific services on specific hosts.
the caveat is that the freeipa servers must be available to provide authorization even once the ticket is issued. with x509, the authenticating host doesn't need to rely on a server for anything but CRL checks
nobody uses analog audio out in an HTPC use case. You send digital audio streams out the HDMI port.
Even a low end external ADC is going to greatly outperform anything RPi could ship onboard for a reasonable cost, and even if they did ship something onboard, at this point it would almost certainly just be a USB ADC, but onboard.
the entire reason the devices get public a public IP is because the firewall effectively isn't there. from the time u-boot inits the topaz chip, until linux controls the chip, it behaves like a dumb ethernet switch.
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.