In Brief
Shape-sensing sheet digitally tracks its own movement as it bends and twists
Why this matters now: MIT’s shape-sensing sheet could enable better wearable motion tracking for physical therapy, VR skins, and soft-robot sensing without bulky external rigs.
Researchers at MIT built a stretchable sheet woven with zig-zag optical fibers that changes the light that travels through it as the surface bends and folds; an algorithm then reconstructs the sheet’s 3D shape in near real time. The team showed the system tolerates some fiber damage and still produces a usable virtual twin, which makes it promising for real-world, wear-and-tear applications such as therapy mats or soft robot skins. As the researchers note, this isn’t just lab trickery — the approach could replace heavier sensor setups with a low-profile, damage‑tolerant surface sensor. Read the full release from MIT News for the demo and technical highlights.
Deep Dive
NYC’s “Click to Cancel” rule is now in effect
Why this matters now: New York City’s rule forces subscription services that sell to New Yorkers to provide cancellation flows as easy as signup, changing UX, billing notices, and potentially how companies run automatic renewals.
New York City has started enforcing what many consumers have wanted for years: cancellation must be no harder than sign-up. According to the city’s announcement, companies that sell recurring services to New Yorkers must offer an easy, online cancellation flow (a single click or equivalent), clear disclosures about renewal timing and pricing, and must avoid manipulative retention patterns often labeled “dark patterns.” The change is part of a broader push against hidden junk fees and deceptive practices, and municipal agencies will have enforcement power to investigate violations. See the official Click to Cancel page from NYC for the rule text and guidance.
This is a practical UX- and billing-level mandate, not just a consumer-rights slogan. Product teams that rely on automatic renewals will need to audit their flows: are cancellations buried behind multiple pages, forced into phone calls, or hidden in obscure menus? Those patterns are now squarely targeted. Expect quick product changes (clearer pop-ups, dedicated cancel buttons, straight‑forward refund policies) plus some strategic responses: companies could geofence features, limit offers outside New York, or pivot to phone-only offers where legally allowed. Either way, this raises a predictable question — will stronger local rules nudge national product norms? Historically, large jurisdictions acting first tend to set de facto standards when the user experience becomes simpler and cheaper to apply everywhere.
Enforcement will determine the rule’s teeth. Cities can issue fines and penalties, but proving “undue friction” in a UX flow can be subtle. Consumer complaints will be the easiest trigger for investigations, and firms that ignore the spirit of the rule risk not just fines but public blowback. For product managers, the practical checklist is short: surface cancellation options; make renewal timing and price explicit at signup and in renewal notices; and remove manipulative design that obscures quitting. Those are straightforward changes — and importantly, they align UX with customer respect rather than trickery.
“Cancellation must be as simple as sign-up,” says the city guidance, summarizing the rule’s central aim.
Key takeaway: If your product uses recurring billing and serves New Yorkers, you should already be mapping your cancellation journey, clarifying renewal language, and preparing for possible enforcement inquiries.
Total Annihilation, rebuilt for modern computers
Why this matters now: A community-built, MIT-licensed engine lets players run the original Total Annihilation on current OSes while giving developers a clean, permissively-licensed codebase to learn from and mod.
A small team of preservation-minded developers launched a modern, open-source engine that runs the 1997 RTS Total Annihilation using the original game assets. The project modernizes rendering with GPU support, documents file formats, and is licensed under MIT — explicitly aiming to be a platform for learning and modding while preserving original game behavior. As the project puts it, they want you to "Play the classic through a modern, MIT-licensed engine you can study, modify and build on." The project homepage showcases cross-platform builds (Windows, macOS, Linux, mobile) and an emphasis on fidelity over reinterpretation; you still need your original game files to play.
This is a clean example of software archaeology combined with pragmatic licensing. Ports and reimplementations often reintroduce bugs or license constraints; an MIT-licensed engine gives modders and researchers freedom to experiment without copyleft entanglements. Practically, that means faster iteration on custom maps, modern graphics fixes, or academic work probing the game's AI and simulation. The project also documents formats and behaviors, which helps people reconstruct historical design decisions rather than poke blindly at binary blobs.
IP remains a corner to watch. The engine itself is permissively licensed, but playing the game requires the original assets — a common preservation compromise that respects rights holders while enabling community-driven modernization. For hobbyist developers, the clean codebase is a learning resource: you can study real-time simulation logic, consider how legacy CPU-bound systems map to modern GPU pipelines, and craft mods that extend the original’s systems without fighting outdated engine constraints.
“Play the classic through a modern, MIT-licensed engine you can study, modify and build on,” the project states, framing this as both preservation and an open playground.
Key takeaway: If you care about game preservation or want a hands-on, permissively-licensed codebase to learn RTS internals, this rebuild is a rare, practical resource.
Closing Thought
Regulation and community engineering are both forms of stewardship — one protects users by changing incentives and the other preserves cultural tech artifacts by making them inspectable and reusable. This morning’s stories show both levers in action: a city rewriting product incentives for fairness, and a community rewriting a game engine to keep a cultural artifact alive and teachable. For product teams, the lesson is straightforward: make quitting simple, and document your systems so others can build on what you leave behind.