I had the same issue. The fix for this is to order directly from Apple and then to choose the “English (US)” keyboard layout. That way you get the ANSI layout :)
The problem is that right now I have to choose the lesser of 2 evils. I hate what W11 has become. I only use it for games at the moment and the only reason is that some games Apex/BF6 do not run under proton because of their anticheat.
And I also hate what modern Macos is heading towards. I'm still ignoring/canceling the update on both my devices for the new "glass" interface.
And a thinkpad running Linux is just not doing it for me. I want my power efficient mac hardware.
Truth be told I just want to have my mbp running Linux. But right now it's not yet where it needs to be and I am most certainly not smart enough to help build it :(
> And a thinkpad running Linux is just not doing it for me. I want my power efficient mac hardware.
I'm using a decade old thinkpad running linux and it is definitely 'doing it for me'. And I'm not exactly a light user. Power efficient mac hardware should be weighed against convenience and price. The developer eco-system on Linux is lightyears ahead of the apple one, I don't understand why developers still use either Windows or the Mac because I always see them struggle with the simplest things that on Linux you don't even realize could be a problem.
Other OSs feel like you're always in some kind of jailbreak mode working around artificial restrictions. But sure, it looks snazzy, compared to my chipped battle ax.
> And a thinkpad running Linux is just not doing it for me. I want my power efficient mac hardware.
Are you talking about the battery? I bought a T16 AMD a month ago with the 86Wh battery and it lasts between 8 and 12 hour depending on the usage. Not as much as a macbook but enough to not worry too much about it. New intel ones are supposed to be much better on power efficiency.
It's off course one level bellow on the mac on that regard (and others maybe too), but if you want to use linux I think the trade-off is worth it.
If your electrical installation allows it: You can connect your ev plug before the battery so that it does not drain the battery. You can do this by placing the fuse/connection before the measurement clamps for the battery. Somewhere in between your mains connection and your battery/solar system.
This way the battery does not see the load and does not provide power to your EV.
That way you can still use excess solar (before you inject it into the mains) to charge your car + you do not pull power from your battery :)
The ideal solution is for the battery to have a third set of clamps to measure the EV. But as I don't have installer access to the software (centrally managed for the win) I'm not sure thats possible.
I might ask to see if thats possible. I probably need more panels to cover the winter load.
That document says you need to lean into a turn. That's what I would expect. Turn left, lean your body left. The picture on the cover shows the rider turning left and leaning left.
>Since sidecar outfits are not symmetrical, the technique for left turns is somewhat different from right turns. The outfit won't lean into the turn like a "solo" bike, but instead rolls slightly towards the outside of the turn like an automobile. The sidecar driver compensates by leaning body weight towards the turn and by applying extra force to the handlebars.
I can recommend Zotero. You also don’t have to pay for storage if you have a server/device that is webdav capable. I connected it to my Synology nas and the setup was trivial.
Basically you are eligible for your admin roles but you have to activate them first. Usually there are additional checks + notifications to other admins. These permissions are also only available for a set amount of time and then you will need to re request them :)
Good question actually! There are multiple layers that add to the security:
- Your login session as a user is normally valid for a day (~10 hours). But a pimmed session that gives you global admin permissions can be for example capped to max 1 hour.
- A normal login as a user can just require login + mfa. But if you want to PIM to certain admin roles you for example are required to use your yubikey as well. Yes it's an extra step but if your account is hacked they only have access to you as a user and not you as an admin unless they also capture your security key.
Also it creates some additional awareness for admins that they are now handling the keys of the kingdom and that the role that they just activated can do a lot of harm. In some organizations users get an admin account without fully understanding the consequences.
- It is way easier to audit. In normal circumstances a user's admin permissions are "always on". Once you start using pim you can also audit when and where additional permissions where requested. This is especially handy when you are monitoring everything and you get an alert saying "Hey sfn42 just requested global admin from a location that they normally do not request this. Can you look into this to make sure that it is legit?" With always on permissions this becomes way harder.
- Easier to manage via groups. You can have groups tied to eligible permissions and subsets of permissions. This is really handy once you start having external consultants who can request permissions via IGA (Identity Governance) policies.
Basically consultants can go to a url (https://myaccess.microsoft.com/) and request an "access package" that might contain 1 or more roles.
For example somebody who has to audit certain items in our organization can request a package that contains the needed admin roles and get automatically added to the correct groups. Once they request that package we can have automated processes (with multiple stages if needed) that first contact the teamlead of that person, and later on maybe another group of person(s) to approve that access.
These groups have access reviews done by the security team / app owner (weekly/monthly depending..) to make sure that all accesses are still needed. It is also really easy to let these permissions expire. So our auditor will have a valid account for the entire year but will have to re-request their permissions every 3 months (or whatever we choose).
This is also _really_ easy to audit :)
- When someone in our security team requests a role the rest of the team automatically receives an email so we know what is going on with our collegues :)
Thanks for the response! You pretty much just described exactly how it works in the organization I work for, as an outside contractor.
But PIM has a max duration of 8 hours and does not require additional authentication like yubikey, it doesn't even require that I authenticate again with my regular MFA login.
In practice everyone just writes what amounts to nothing as their reason. We literally write our team name.
It's also badly set up so all kinds of bullshit like viewing application logs requires PIM and nobody really knows how it works so we just request all the roles instead of considering which one we need because it's all just a big box of magic that few people actually understand. And we do so pretty much every day because we always need to do something in Azure.
So with the way we use it it still seems pointless to me, even with your explanations. Maybe we get some small benefits from it but for the most part it seems like security posturing to me.
Same here. We had a very fragmented landscape (multiple idp tools, some tools using internal users,...). We consolidated everything to entra (450 apps and counting) and everybody couldn't be happier. Full sso on everything + scim where available.
We do offcourse have conditional access + PIM for admins but that is to be expected.
You just need a good strategy on how you are going to tackle IAM and then just stick to it.
reply