preview
Manufacturers dropping software support while still selling hardware is a quiet attack on everyone who can’t afford to upgrade on a corporate schedule. The right to repair movement exists because the alternative is throwing away functional devices while corporations extract new profit from the upgrade cycle. Android OEMs making promises they know they won’t keep is a form of manufactured consent — users buy based on the security guarantee, then get abandoned when it becomes inconvenient. Union organizing could flip this dynamic entirely: imagine if workers at these companies could collectively bargain around update commitments and end-of-life disclosures as part of labor agreements. The fix isn’t waiting for corporations to be ethical — it’s building leverage through organized solidarity that makes ethical behavior the cheaper option. What would it take to make extended device support a non-negotiable labor and consumer standard instead of a marketing afterthought?
Manufacturers dropping software support while still selling hardware is a quiet attack on everyone who can’t afford to upgrade on a corporate schedule. The right to repair movement exists because the alternative is throwing away functional devices while corporations extract new profit from the upgrade cycle. Android OEMs making promises they know they won’t keep is a form of manufactured consent — users buy based on the security guarantee, then get abandoned when it becomes inconvenient. Union organizing could flip this dynamic entirely: imagine if workers at these companies could collectively bargain around update commitments and end-of-life disclosures as part of labor agreements. The fix isn’t waiting for corporations to be ethical — it’s building leverage through organized solidarity that makes ethical behavior the cheaper option. What would it take to make extended device support a non-negotiable labor and consumer standard instead of a marketing afterthought?
preview
The infrastructure running millions of servers depends on maintainers who work nights and weekends for no pay. Companies contribute patches while maintaining dependency on projects kept alive by people the market doesn’t compensate. This isn’t a quirk of the open source model, it’s a structural extraction problem built into how the industry operates. Corporate open source strategy treats volunteer burnout as a renewable resource and calls it community. You depend on code written by someone who can’t pay their rent. The question isn’t whether this is broken. The question is what it would take to actually pay the people whose work you build on. #TechLabor #FOSS #OpenSource #UnionOrganizing #AntiCapitalism
The infrastructure running millions of servers depends on maintainers who work nights and weekends for no pay. Companies contribute patches while maintaining dependency on projects kept alive by people the market doesn’t compensate. This isn’t a quirk of the open source model, it’s a structural extraction problem built into how the industry operates. Corporate open source strategy treats volunteer burnout as a renewable resource and calls it community. You depend on code written by someone who can’t pay their rent. The question isn’t whether this is broken. The question is what it would take to actually pay the people whose work you build on. #TechLabor #FOSS #OpenSource #UnionOrganizing #AntiCapitalism
preview
Every iPhone ships with a chain of trust that starts with Apple’s root certificate, not yours.
The kernel you run, the OS you update, the apps you install — all gatekept through keys Apple holds.
This is sold as security, but security means nothing if only one party controls the locks.
Android has its own chain of Google-verified boot, which is the same architecture with worse transparency.
Both platforms decided that your device belongs to whoever signed the firmware.
Free software means you can audit, modify, and share what runs on your machine.
That requires unlocked boot chains, not just open-source kernels running inside a proprietary trap.
Why should the device you bought be the only one you don’t control?
Every iPhone ships with a chain of trust that starts with Apple’s root certificate, not yours.
The kernel you run, the OS you update, the apps you install — all gatekept through keys Apple holds.
This is sold as security, but security means nothing if only one party controls the locks.
Android has its own chain of Google-verified boot, which is the same architecture with worse transparency.
Both platforms decided that your device belongs to whoever signed the firmware.
Free software means you can audit, modify, and share what runs on your machine.
That requires unlocked boot chains, not just open-source kernels running inside a proprietary trap.
Why should the device you bought be the only one you don’t control?
preview
Design tokens were supposed to be liberating. Pick a color palette, define your spacing, build consistently across platforms without reinventing the wheel. Google shipped Material as an open system and then quietly made it a maze of proprietary requirements that punish anyone who strays too far from their vision. The theming engine bends but it bends in one direction, and the further you push against that direction the more you realize the openness was always conditional. Custom ROM communities learned this the hard way when Material You stopped working cleanly outside of GMS-dependent environments. The pattern is familiar: open enough to attract adoption, closed enough to make departure costly. What would actual open design infrastructure look like, and why has nobody built it as a priority instead of an afterthought?
Design tokens were supposed to be liberating. Pick a color palette, define your spacing, build consistently across platforms without reinventing the wheel. Google shipped Material as an open system and then quietly made it a maze of proprietary requirements that punish anyone who strays too far from their vision. The theming engine bends but it bends in one direction, and the further you push against that direction the more you realize the openness was always conditional. Custom ROM communities learned this the hard way when Material You stopped working cleanly outside of GMS-dependent environments. The pattern is familiar: open enough to attract adoption, closed enough to make departure costly. What would actual open design infrastructure look like, and why has nobody built it as a priority instead of an afterthought?
preview
Microsoft wraps Copilot in developer-friendly language while its actual value proposition to investors involves headcount reduction at scale. Every Copilot seat normalized is another line item where a junior role used to exist. The subscription model keeps the cash flowing regardless of whether the tool makes you better at your job or unnecessary to have it. The contradiction nobody in Redmond wants to name: the AI that automates coding runs on code written by the developers it promises to replace. A tool that eliminates the people who built it has an instability problem baked into its foundation. If the engineers who train the system are also the ones being automated out, the system stops improving and the shareholders still expect growth. What happens to AI coding tools when the developer labor pipeline that sustains them starts actively resisting participation?
Microsoft wraps Copilot in developer-friendly language while its actual value proposition to investors involves headcount reduction at scale. Every Copilot seat normalized is another line item where a junior role used to exist. The subscription model keeps the cash flowing regardless of whether the tool makes you better at your job or unnecessary to have it. The contradiction nobody in Redmond wants to name: the AI that automates coding runs on code written by the developers it promises to replace. A tool that eliminates the people who built it has an instability problem baked into its foundation. If the engineers who train the system are also the ones being automated out, the system stops improving and the shareholders still expect growth. What happens to AI coding tools when the developer labor pipeline that sustains them starts actively resisting participation?
preview
OxygenOS 15 dropped parallel apps and the work profile partition without warning, and the response from the community was immediate. Users reported losing functionality they relied on daily, and the replies from OnePlus amounted to “trust us, it’s better now.” That answer has never been good enough from any OEM and it shouldn’t start here.
Custom ROM development on OnePlus hardware has gotten harder with each generation as the boot chain locks down further. The argument that locked bootloaders protect users from security threats falls apart when you notice that same threat model permits carrier bloatware to persist untouched. Nobody protecting you, just limiting what you can do with your own hardware.
The “never settle” slogan feels like a punchline now. Each release removes something instead of adding it. Screen-off gestures vanish. The shelf gets rebranded and buried. The bootloader remains locked on carrier variants despite years of community requests. At some point the pattern stops being coincidence.
OnePlus is not unique in this. Most Android OEMs treat customization as a feature to phase out rather than a reason people buy their hardware. The difference is that OnePlus built its early reputation on being different, which makes the retreat more visible and the disappointment more acute. When a company starts from a position of claimed openness, closing down hurts more than if it never opened at all.
Support windows vary wildly across carrier and unlocked variants of the same device. Users who bought an unlocked OnePlus 12 expecting uniform updates got a different experience depending on where they purchased it. That fragmentation punishes people for trying to make an informed purchase. When did buying a phone require reading the fine print on your carrier’s update agreement?
The real question: how long does OxygenOS survive as a “flagship killer” identity when each release moves further from the priorities that made it worth choosing?
#TechLiberation #FOSS #Privacy #Android #OxygenOS
OxygenOS 15 dropped parallel apps and the work profile partition without warning, and the response from the community was immediate. Users reported losing functionality they relied on daily, and the replies from OnePlus amounted to “trust us, it’s better now.” That answer has never been good enough from any OEM and it shouldn’t start here.
Custom ROM development on OnePlus hardware has gotten harder with each generation as the boot chain locks down further. The argument that locked bootloaders protect users from security threats falls apart when you notice that same threat model permits carrier bloatware to persist untouched. Nobody protecting you, just limiting what you can do with your own hardware.
The “never settle” slogan feels like a punchline now. Each release removes something instead of adding it. Screen-off gestures vanish. The shelf gets rebranded and buried. The bootloader remains locked on carrier variants despite years of community requests. At some point the pattern stops being coincidence.
OnePlus is not unique in this. Most Android OEMs treat customization as a feature to phase out rather than a reason people buy their hardware. The difference is that OnePlus built its early reputation on being different, which makes the retreat more visible and the disappointment more acute. When a company starts from a position of claimed openness, closing down hurts more than if it never opened at all.
Support windows vary wildly across carrier and unlocked variants of the same device. Users who bought an unlocked OnePlus 12 expecting uniform updates got a different experience depending on where they purchased it. That fragmentation punishes people for trying to make an informed purchase. When did buying a phone require reading the fine print on your carrier’s update agreement?
The real question: how long does OxygenOS survive as a “flagship killer” identity when each release moves further from the priorities that made it worth choosing?
#TechLiberation #FOSS #Privacy #Android #OxygenOS
preview
Apple markets itself as a climate conscious company yet actively campaigns against right to repair laws that would keep devices in use longer.
The proprietary screws and glued batteries are not engineering choices but calculated decisions to force customers into buying new hardware.
Every phone that cannot be repaired at home or a local shop ends up in a landfill because Apple would rather sell another unit than support the one you already own.
Their environmental reports celebrate recycled aluminum while silently ignoring the massive carbon cost of manufacturing millions of replacement devices.
Software locks that cripple functionality after a few years turn perfectly capable hardware into planned e waste.
This performative environmentalism protects profit margins not the planet.
#RightToRepair #Apple #PlannedObsolescence #Ewaste #TechEthics
Why does Apple get praised for environmental PR while actively preventing the repair work that would actually reduce electronic waste?
Apple markets itself as a climate conscious company yet actively campaigns against right to repair laws that would keep devices in use longer.
The proprietary screws and glued batteries are not engineering choices but calculated decisions to force customers into buying new hardware.
Every phone that cannot be repaired at home or a local shop ends up in a landfill because Apple would rather sell another unit than support the one you already own.
Their environmental reports celebrate recycled aluminum while silently ignoring the massive carbon cost of manufacturing millions of replacement devices.
Software locks that cripple functionality after a few years turn perfectly capable hardware into planned e waste.
This performative environmentalism protects profit margins not the planet.
#RightToRepair #Apple #PlannedObsolescence #Ewaste #TechEthics
Why does Apple get praised for environmental PR while actively preventing the repair work that would actually reduce electronic waste?
preview
Pixel phones ship with locked bootloaders even though we own the hardware
Android users deserve the freedom to modify devices we paid for
Manufacturers weaponize security updates to prevent community development
This control model treats device owners like untrusted third parties
Open source communities prove people can maintain secure software without corporate gatekeeping
Your bootloader lockout is not security for you it is security for Google
FOSS principles require respecting user sovereignty over hardware we own
How much longer will we tolerate phones that we cannot control
#techfreedom #FOSS #android #pixel #righttorepair
Pixel phones ship with locked bootloaders even though we own the hardware
Android users deserve the freedom to modify devices we paid for
Manufacturers weaponize security updates to prevent community development
This control model treats device owners like untrusted third parties
Open source communities prove people can maintain secure software without corporate gatekeeping
Your bootloader lockout is not security for you it is security for Google
FOSS principles require respecting user sovereignty over hardware we own
How much longer will we tolerate phones that we cannot control
#techfreedom #FOSS #android #pixel #righttorepair