
Well, that’s unfortunate re: Jeff, but it’s still weird to me that the other commenter would be aware of that about him (which you mention having to dig through a decade of blog posts and old tweets to find), without at some point also finding out that he’s ‘the Raspberry Pi guy.’
It’s like knowing that Hitler was a vegetarian but somehow not knowing that he was the dictator of Germany who started WWII – it just doesn’t make sense for a fact to be that isolated from its context.

…wat.
I think you must be thinking of some other Jeff Geerling. The one I’m talking about is probably the #1 guy on Youtube for content about ARM stuff, and AFAIK isn’t a homophobe.
Your comment doesn’t make any sense because, even if you were talking about the right person and your accusation were accurate, why would you know some obscure thing about him while being unaware of the thing he’s famous for?

Unlocking the phone voids the warranty?
No, it doesn’t. Motorola apparently claims it does, but they’re lying. The Magnusson-Moss Warranty Act requires them to honor the warranty no matter how you modify your property unless they can prove your modification caused the fault you’re trying to claim the warranty for. They don’t just get to presume it because you flashed the firmware.

I mean, at the time when turbo buttons were a thing (and I was a kid who didn’t know much about computers yet), I incorrectly thought that too. My own computers never had one though, and I’d like to think that if one had, I would’ve eventually figured out that it worked opposite to how the label implied.

Turbo was on by default. Pressing the button to turn it off made the computer run slower to emulate an 8086, so that software coded to calculate time based on instruction cycles rather then using a proper real time clock function wouldn’t run faster than the intended speed.
An 8088 wouldn’t have a turbo button since it ran at the same speed as an 8086 to begin with.
(Also, SimCity 2000 required at least a 386.)

It’s not about preventing sideloading installing software in the normal way1 by someone determined to do it.
It’s about spreading FUD and propaganda demonizing the idea of device owners actually having control over their property instead of abdicating their rights and ceding their privacy to technofeudal overlords like Google.
1 because “sideloading” is itself already a propaganda term
I also have GrapheneOS, but have been noticing that it would (for example) annoyingly kill Voyager when I’m in the middle of writing a comment and task switch to Firefox to copy a URL or something. I switch back and it’s back on the home feed with a message that it “recovered” my comment text, but of course I have no hope of finding the thing I wanted to reply to again…
This is on a Pixel 7 that should have plenty of RAM, BTW.

Okay, but having normal lighting (matching the way light works in the real world) is obviously normal. Realism has always been the main goal of 3D rendering. If you want something different than that, it’s because you’re making a deliberate stylistic choice.
It should be easy to delete the normal lighting, but a new project should absolutely, obviously, start out with normal lighting.

STFU, ghost of Dallas executive producer Leonard Katzman!
The mere phasing of it as them “letting” users do it shows that they fundamentally Do Not Get It and are still failing to respect device owners’ property rights.