TheIPW

joined 2 days ago
[–] TheIPW@lemmy.ml 3 points 1 day ago

I get it. I spend more time in the CLI than writing, so I've been using tools to help structure my posts. Clearly, that 'polished' look just comes across as robotic slop here. I'll stick to the raw technical details from now on. Thanks for the feedback.

[–] TheIPW@lemmy.ml 2 points 1 day ago

Depends! Bazzite on ROG Ally X, Debian for servers, CachyOS for my desktop and laptop and Fedora for my sons PC

[–] TheIPW@lemmy.ml 5 points 1 day ago (3 children)

Fair play, you’ve done a proper deep dive there. I’ll hold my hands up—I’m a sysadmin, not a journalist. I use tools to help structure my thoughts because my natural writing style is about as readable as a kernel panic. As for the 'social media' bit, the share buttons are a default plugin I haven't stripped out yet, and Mastodon is the only place I actually hang out because it's federated. I'm just a guy in a home lab trying to share some tech stories; sorry if the 'robotic' prose put you off

[–] TheIPW@lemmy.ml 23 points 1 day ago (8 children)

That is a fair point. 'Sideloading' is definitely a corporate term designed to make basic ownership of our devices feel like a 'workaround' rather than a right. I used it here because it's the language Google is currently using to justify their crackdown, but you're absolutely right—it's just installing software. We shouldn't let them control the vocabulary of our digital freedom.

 

Google is tightening control over Android under the guise of 'security,' but this crackdown on sideloading is a direct hit to digital sovereignty and FOSS. I've written about why this matters for our privacy and the future of open platforms. What do you think—is this the end of Android's 'open' era?