RE: https://chaos.social/@sleepyowl/116126002122086149

A must read thread from @sleepyowl, particularly for anyone laughing off the "oh they're trying to enforce age verification at an OS level, well I'll just change my open source operating system settings"

Y'all, this is the game where we get LOCKED OUT of having ANY real FOSS operating system we control AT ALL

The steps have been being put in place for this for over a decade now. And who controls the supply chain?

We have to fight this stuff tooth and nail.

I advocate for getting hackable open hardware stuff, and @sleepyowl is completely right that even the best options there still rely on supply chains we don't have enough control over, AND once those "resisting" become a small enough group, resisting becomes a lot more dangerous.

That said, I think we should be taking a multi-pronged attack *now*, in every way imagineable:

- Try to use *the most hackable hardware you can get* and contribute to making it a better experience
- Support open firmware, hackable devices
- Maybe it's time for the return of the install fest I dunno
- Absolutely DO NOT run a proprietary operating system under any circumstances
- FIGHT BACK ON THESE POLICIES! Contact your representatives, write articles, do whatever you gotta

@cwebber @sleepyowl do you happen to know if Google could decide to lock the bootloader of a Pixel phone with a software update?
@dain @cwebber this isn't Pixel, but Samsung seems to have pushed updates to stop people from installing custom ROMs https://manganiello.eu/objects/efc723df-04cf-440d-8404-e9a5f21b2f4c
Fabio Manganiello (@[email protected])

#Samsung devices from today can no longer install custom ROMs.Odin is gone and the Download Mode is also gone, which makes life hard also for repair services that want to restore a device.This is y...

@sleepyowl @cwebber oh no, that's pretty terrible and does directly answer the question that any Android OS vendor (not just Google) can decide to end the custom firmware party at any moment