4,603 karma · joined December 16, 2017
But actually a lot don't, and when you try to pay, even contactless, with a non-Girocard, it won't work.
Visa and Mastercard don't magically let you on their network because you have a card machine.
Bad example, since the krbtgt password needs to be rotated twice, since the old one is stored as well, precisely to avoid outages.
Directory server could be Samba4, but I guess if they aim for Linux on the desktop, FreeIPA would probably be the better bet.
Though the choice of email software is interesting; Grommunio from Austria is literally a drop-in Exchange server with support for MAPI, MAPI over HTTP, RPC over HTTP, ActiveSync etc. But again, I guess with a move to Linux you just need something support Cal/CardDAV and IMAP.
Is your passport number then linked to the visa? What happens if you get a new passport? Does it work for non-biometric passports?
Or is there some kind of stable "citizen" identifier in the passport that the visa is linked to? I can't imagine it being a simple name + DoB lookup.
Ehh, in German we talk about Rindfleisch, which comes from a Kuh.
It's almost what I imagine client-server Open Banking could have been.
There's also the EBICS protocol, but that is more for B2B, server-server communication I believe.
Go to the Drivers page on Brother's website, and for any recent macOS version, the answer is, "just use AirPrint".
Whilst clever for the people who don't have Google Authenticator installed, it's just bizarre to ignore it when it's there.
Another example, the default routing rules page in the admin console defaults to only showing 10 rules. Every time you add a rule, the pagination is reset, so you get lost where you are and can't even see the rule you literally just added.
And as an identity platform, Google is nothing compared to Okta or AAD. Whilst it's wonderful that Google login is everywhere now, I can't for example, request the user do 2FA for particular apps.
Even the admin console only requires 2FA once a month, it's ridiculous.
And don't get me started on "groups" still being attached to distribution lists out of the 60s [1]. Or the inability to have shared mailboxes.
No one should ever choose Google Workspace over Office 365.
I don't follow your reasoning. So you have the ability to block QUIC, but declare QUIC to be a "bad actor" trying to bypass your network management?
They switched from TCP to QUIC base, what can be done over HTTP3 can also be done over HTTP2.
IMHO the Phoronix title is more descriptive: "Ubuntu Flavors/Spins Will No Longer Be Able To Install Flatpak By Default" and the HN title should be changed.