Month: March 2026

My Toyota Sienna Van is Now a Lemon Due to an Unaddressed Recall..

Back in December, I shared information regarding a recall affecting my 2025 Toyota Sienna. As of today, March 5 2026, the vehicle has been sitting at the dealership without a resolution. The van has been out of service for almost 90 days, having been at the dealer since December 12th. I’m about to take Toyota to Lemon Law Court here in Connecticut.

See more in my latest video!

The recall addresses an issue where the second-row seats rails have a risk of losing their structural integrity and pose a risk of injury due to defective welds. The manufacturer’s notice explicitly stated no one should sit in these seats until a remedy is performed. While the manufacturer instructed dealers to pull the vehicles from lots on October 7th, 2025, my notice did not arrive until 66 days later. To date, no remedy or timeline for a fix has been communicated.

This situation impacts approximately 50,000 Sienna vans. Faced with a vehicle that cannot be safely used as intended, I researched the lemon law in my home state of Connecticut.

Connecticut requires that a vehicle be a new vehicle under two years old, have less than 24,000 miles, and exhibit a condition that substantially impairs its use, safety, or value. Given that I purchased a seven-passenger van and two of the middle seats cannot be used, the impairment is clear. Furthermore, Connecticut law provides eligibility if a vehicle has been out of service for repair for a cumulative total of 30 days or more.

I have filed a lemon law complaint with the state, and it has been accepted for a hearing. At the hearing, I will make my arguments for either a replacement or a refund. For other owners dealing with this extended recall, researching state-specific lemon laws is a practical step. Resources like Justia provide a 50-state survey of lemon laws across the United States, detailing varying procedures.

While the process in Connecticut is designed so consumers can file without an attorney, legal counsel may be consulted if the hearing process is intimidating. Following my hearing, I will share my presentation and arguments so other owners have something they can use in their own hearings. Stay tuned!

California Law to Require Age Verification on All Operating Systems (Including Linux)

Recently, a new California law signed by Governor Gavin Newsom caught my attention due to its potential impact on the open-source community, specifically Linux users. The legislation mandates that operating systems for PCs and other general computing devices like tablets and phones must implement a form of age verification during the initial account setup process.

I take a look at the implications of this law in my latest video.

While California is not the only state pursuing such measures—Texas recently faced legal hurdles over a similar law—this development raises questions about how open-source organizations, rather than traditional corporate entities, will comply.

The text of the California bill, which was signed on October 13, 2025, and takes effect on January 1, 2027, calls for an interface that requires the account holder to provide their birth date or age. This information generates a signal regarding the user’s age bracket—categorized as under 13, 13 to 16, 16 to 18, or over 18—to be read and enforced by applications within a covered app store.

The legislation defines an operating system provider broadly enough to include independent developers creating Linux distributions. Furthermore, a covered application store is defined as a publicly available online service, which could encompass command-line package managers used daily by Linux administrators.

From a practical standpoint, the current requirement relies entirely on self-reporting. Users are asked to volunteer their age, meaning anyone could input inaccurate information to bypass restrictions. Despite this, the penalties for non-compliance are clearly defined. Operating system makers face civil penalties ranging from $2,500 for negligent violations to $7,500 for intentional violations per “affected child.” If a developer has internal data showing a user’s actual age differs from the self-reported signal, they are legally obligated to act on that information or face action from the California Attorney General.

The implications for Linux distributions are notable. Commercial entities with a business nexus in California, such as the organizations behind Ubuntu and Fedora, will likely implement the necessary prompts to comply.

However, smaller projects face a different reality. Many distributions are maintained by volunteer groups without the financial resources or organizational structures to shield them from liability. Midnight BSD has already modified its software license to exclude California residents, but this legal maneuver may not satisfy California regulators if the software remains accessible for download within the state’s borders.

This legislative push is not confined to the West Coast. My home state of Connecticut is currently evaluating controls for minors on the internet, and Colorado is exploring operating system-level age verification. Texas attempted to regulate app stores before a federal court blocked the law, citing First Amendment concerns regarding its broad application. The absence of a unified federal privacy law has resulted in a fragmented regulatory landscape across different regions.

Historically, some internet users have responded to localized regulations by migrating to decentralized platforms. When Discord faced scrutiny over its age verification methods that included video selfies and government IDs, users began exploring open-source alternatives like Revolt and Matrix. These self-hosted and federated platforms demonstrate how technical communities can circumvent centralized data collection and restrictive legal mandates.

As the 2027 deadline approaches, it is likely that many Linux distributions will simply integrate a birth date or age prompt into their installation screens to mitigate legal risks. The technical challenge of passing that age signal consistently to various package managers and standalone applications remains a logistical hurdle. The coming months will test how far state authorities are willing to go in enforcing these mandates on the broader open-source software ecosystem.

DOS Games in a Browser? DOS.ZONE Review

For my annual Christmas retro video, I explored the Exodos project, a method for downloading and playing a vast library of classic DOS games. While functional, it requires significant disk space, BitTorrent downloads and some complexity. It also lacks native compatibility with MacOS and Linux. Following a recommendation from my friend Adam of TechOdyssey, I recently tested an alternative approach called DOS.zone.

Check it out in my latest video!

DOS.zone is a web-based emulation platform designed to run legacy DOS and Windows 95 games directly within a browser. During my testing on an M2 MacBook Air using the Brave browser, games like Doom booted quickly and ran at standard speeds without requiring any software installation or command-line management. The platform currently hosts approximately 2,000 titles, which is a smaller library compared to the Exodos project, but it focuses on immediate accessibility.

The service operates primarily as a free service, downloading and executing the game files locally in the browser rather than streaming them from a server. The DOS games run in DosBox or DosBox-X which has been ported to Javascript (more on that later).

Game progress can be saved to the browser’s local storage, provided the user clicks the designated save icon before exiting. Because local browser data can be cleared or lost, DOS.zone offers an optional subscription for a few dollars a month that enables cloud synchronization for save files. The save files can be synced across devices too.

The emulation includes various adjustable settings to tailor the experience. Users can modify the DOSBox performance by toggling the auto-adjust feature and manually setting CPU cycles, which I found necessary to stabilize the frame rate in titles like Wing Commander. Other options include mouse capture, on-screen control scaling, and an image smoothing toggle for those who prefer altered graphics over the original pixelated rendering. Notably, the platform currently lacks native game controller support, relying instead on keyboard controls or external software mapping.

Technically, DOS.zone distinguishes itself from other in-browser solutions by supporting Windows 95 environments and 3dfx hardware acceleration. Loading a game like Road Rash prompts a brief Windows 95 boot sequence before launching the application. While this specific browser port lacks the original full-screen video and music, it runs consistently at 60 frames per second. The 3dfx support extends to titles like the original Grand Theft Auto and various hardware demos, rendering hardware-accelerated graphics entirely within the browser window.

The platform also integrates a multiplayer hub where users can join active network sessions for games like Quake or Half-Life Deathmatch. In my experience, some visual assets load dynamically during the initial session, which can cause minor stuttering, but the performance stabilizes once the caching is complete.

Because the underlying technology utilizes the open-source JS-DOS API, the emulation extends to mobile devices. Testing Need for Speed on a smartphone demonstrated that the platform automatically maps necessary game controls to the touchscreen, enabling mobile gameplay without requiring a dedicated app installation.

For users seeking a broader library, the Internet Archive remains a viable alternative with over 8,800 browser-playable DOS titles. However, DOS.zone provides a more specialized technical implementation with its inclusion of 3dfx, Windows 95 support, and built-in multiplayer routing, offering a highly accessible route to revisiting legacy software without the need to manually configure local emulators.

See more retro here!