Bears, beets, battlestar galactica

It’s been a bit since I saw the original behind the scenes vid or whatever it was, what was the context?

“The bypass uses a CXH (cloud experience host) URI (Uniform Resource Identifier) string during the OOBE to invoke the hidden local account setup screen.” this had to be data mined or something yeah.

one of these creepy bastards got inside of my soap dispenser brush thing for doing the dishes. just threw the entire brush away D=

the one with the biiig built in “leather” wrist rest? loved that thing!

I’m pretty sure that’s corporate speak for “we need to drive plex pass subscriptions more so we need to lock more feature behind it.”

deleted by creator

lmfao right?

LineageOS Android TV looks like an interesting solution but having SELinux in permissive mode is a bit scary. Maybe someone with more in-depth Linux knowledge can chime in here but my understanding is that would mean that the Android kernel’s security system would basically be turned off. Permissive Mode logs security access violations within the OS but does nothing to prevent them so I would be wary of connecting it to the internet.

I can’t speak for other countries, the EU banned it a while ago, but up until very recently a lot of citrus drinks over here in the U.S. used a chemical called Brominated Vegetable Oil as a stabilizer/emulsifier I think? So at least in the U.S. there can be fats in some sodas. Maybe enough for the THC?

If you’re particularly lazy and want to check how a plant is doing you can even just microwave to activate it. put it in a glass cup with a damp paper towl under it, cover with a second damp paper towl, cover in plastic wrap except a small gap like you’re making a microwave dinner. Cook for a minute at a time on 20-30% power and let the steam release between cooks. Do that 2-3 times then remove nug from container and let it sit a few minutes on a plate or something.

this here is the real issue.

The update was meant to fix a situation where an attacker would somehow get grub onto a machine that was SINGLE booting windows and use grub to tamper with secureboot. this fix was meant to only apply in single boot situations where it should be entirely unexpected to see grub. as they said, something went seriously wrong.