


computer security person. former helpdesk.


Baseline Security has been formally announced! techcommunity.microsoft.com/…
This is roughly what the baseline security check looks like as of build 29704

Microsoft announces new local-first security tooling in response to recent cloud outages #MSIgnite

Both NeXT and 3DFX tried to “do the right thing” with color spaces, and it wound up generally making them look worse than competing options. I didn’t really understand it properly until years later. It is natural to think that a pixel with a value of 1.0 is emitting twice the photons as a pixel with a value of 0.5, so you can do the obvious linear math to calculate partial pixel coverage, blending a foreground over a background, or interpolating between colors in a texture. If displays are “linear”, that is correct. NeXT and 3DFX were much closer to linear than other contemporary displays. NeXT had crossover from the deep graphics understanding at Pixar, and 3DFX had the SGI heritage. They did this intentionally. If you have 10+ bits per channel like the professional rendering systems, linear displays are The Right Thing. Unfortunately, NeXTStation Colors were 4 bits per channel and 3DFX was 5 or 6 bits per channel, and there… it was not the right thing. Human eyes aren’t linear intensity sensors. We mostly register relative changes in intensity, so we can tell the difference between 0.01 and 0.02 as a huge doubling, while 0.99 to 1.00 is almost imperceptible. This distribution of intensities is often referred to as the “gamma” of the display system, but the actual curves like sRGB are a bit more complicated. If you only have a small number of discrete pixel values, you definitely don’t want to spread them evenly from 0 to 1! If you do, you will have good precision in the brights, but very stark “intensity bands” in the dark colors. If everything was authored specifically for 3DFX, you would still have the fundamental problem with the dark bands, but more accurate blending and filtering. The problem was that artists made all of their textures in paint programs on conventional non-linear displays, so when they were drawn by 3DFX cards, they got the characteristic “washed out color” look. You can mathematically correct textures for differences in display gamma, but I didn’t really understand the issue back in the glQuake days, and we were so enthralled by the absolute performance of 3DFX that the color fidelity didn’t get as much attention as it should have. Even today, tons of games don’t properly handle gamma across their textures and render targets. High resolutions and 24 bit color masks most of it, but you still see it in some slight shimmerings in high contrast textures and edges.
Does anybody know why 3DfX 1 cards had such a washed out color output? In my research, circa '97 I found many people complaining about the colors. Is it gamma? 16-bit color? What can it be?

It was an honor to be a small part of Windows Phone, and an honor to be a small part of this documentary. Hats off to David for making a remarkable piece of storytelling.
In 2009, a handful of designers set up in a warehouse. What they made reshaped @Microsoft, then the whole industry, and some of it is still on nearly every screen you use. I made a feature-length documentary about Metro UI, told by the people who made it. It premieres Friday!


PowerShell 7.7 is released -- as an MSIX oofhours.com/2026/11/15/powe…

🔒 Secure Bits 💡 𝗧𝗲𝗺𝗽𝗼𝗿𝗮𝗿𝘆 𝗴𝗿𝗼𝘂𝗽 𝗺𝗲𝗺𝗯𝗲𝗿𝘀𝗵𝗶𝗽 𝗶𝗻 𝗔𝗰𝘁𝗶𝘃𝗲 𝗗𝗶𝗿𝗲𝗰𝘁𝗼𝗿𝘆? Yes! I know not many people know about this, but there is actually a native Just-In-Time (JIT) capability in Active Directory. It is not enabled by default, and you need to have Windows Server 2016 forest functional level. It basically allows you to add a user to an AD group for a limited amount of time. Cool, right? I can’t say I’ve ever used this as a permanent solution in Active Directory, but it’s there and it’s good to know about it. 1️⃣ 𝗘𝗻𝗮𝗯𝗹𝗲 𝘁𝗵𝗲 𝗣𝗿𝗶𝘃𝗶𝗹𝗲𝗴𝗲𝗱 𝗔𝗰𝗰𝗲𝘀𝘀 𝗠𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 𝗳𝗲𝗮𝘁𝘂𝗿𝗲 Enable-ADOptionalFeature -Identity "Privileged Access Management Feature" -Scope ForestOrConfigurationSet -Target "ad[.]horizon-secured[.]com" 2️⃣ 𝗔𝗱𝗱 𝗮 𝘂𝘀𝗲𝗿 𝘁𝗼 𝗮 𝗴𝗿𝗼𝘂𝗽 𝗳𝗼𝗿 𝗮 𝗹𝗶𝗺𝗶𝘁𝗲𝗱 𝘁𝗶𝗺𝗲 $ TimeLimit = New-TimeSpan -Minutes 2 Add-ADGroupMember -Identity t1-administrators -Members t1-dhorak -MemberTimeToLive $ TimeLimit After those two minutes, the membership expires automatically. 3️⃣ 𝗖𝗵𝗲𝗰𝗸 𝗵𝗼𝘄 𝗺𝘂𝗰𝗵 𝘁𝗶𝗺𝗲 𝗶𝘀 𝗹𝗲𝗳𝘁 Get-ADGroup "t1-administrators" -ShowMemberTimeToLive -Property member This shows you the remaining TTL for the temporary membership. 𝗦𝗼, 𝘄𝗵𝘆 𝗱𝗼𝗻’𝘁 𝗜 𝘂𝘀𝗲 𝗶𝘁 𝘁𝗵𝗮𝘁 𝗼𝗳𝘁𝗲𝗻? ➡️ It’s nice that the user is automatically removed from the group, but you can still have existing sessions with active access tokens containing that group membership. So you need to take care of those as well. Did you know about this feature? 👇 #ActiveDirectory #WindowsServer #WindowsSecurity #CyberSecurity #IdentitySecurity #PrivilegedAccess #HorizonSecured

Sorry I meant Surface LAPTOP Go. Model 1943. Blame marketing.

The Surface Go design with the light-up biometric power button is fantastic with the new administrator UAC evaluation experience.

The 1st gen Surface Go is generally regarded as a shit-tier laptop but running the latest Win11 and properly cut-down with some basic optimizations it's a perfectly fine, even great, lightweight dev station.

You want me to eat bread in the shape of a SHAFT? In a bag? Like BALLS come in?


Thinking hackers need 0days is like believing Santa's sleigh must logically have sonic boom dampers.

Now, humans can not separate their existence from the caretaker Artificial Intelligence. They can not run the datacenters. Nor can they can shut down the datacenters. It’s the unforced inception of a Steady State Society. It’s what we wanted. Without a single bullet. The End.

At this point, human engineers had architected an infrastructure for society they could not maintain. Society recognized this, and demanded something better. Something proven. Humans demand to be ruled by machine. In September 2043, they democratically cement this delegation.