A free option worth checking out: https://github.com/0xCUB3/wBlock . I have been using it on my mac and my mobile devices and it syncs up nicely and seems to perform well :)
A backend for an open source bbq thermometer firmware that a mate and I wrote last year for a product that was discontinued (https://github.com/epiecs/free-grilly).
The github repo for the backend is still private atm but we are planning to release soon once we have a gui ready for that new backend. The plan after that is to learn pcb design and electronics and maybe design our own bbq thermometer :)
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 :(
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 :)
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.
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 :)
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 :)
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.
You can also just setup a pihole adblocker on a vm. It has a local dns feature as well (that is nothing more that a textfile containing all your local records). Super easy to setup and maintain :)
Because the pi-hole is a dns server. So it doesn't need to filter all traffic. It just replies to dns requests. And you need a LOT of traffic to completely saturate a 100Mbit link with dns requests :)