How the Web Was Hardened: Inside the Internet's Critical 1996-1998 Transition

·1 views

Between 1996 and 1998, the internet underwent a fundamental shift from an academic research network into a commercial utility, forcing engineers to redesign its core infrastructure under pressure. Legacy assumptions inherited from the old Network Control Program haunted the transition, as outdated connection-oriented logic clashed with the realities of large-scale packet-switching. To prevent network-wide congestion collapses triggered by surging browser traffic, engineers at the IETF and companies like Cisco refined TCP/IP congestion control algorithms, including TCP Tahoe and Reno. Sliding window mechanisms were tightened and hardware-level packet inspection via ASICs was introduced to push processing logic closer to the silicon. This period represented a decisive 'hardening' of the internet, burying direct network control beneath the graphical browser while laying the structural foundation for modern global commerce.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

StreamCart Pitches Open-Source Shoppable Video Engine Built on Medusa v2 and MeiliSearch

A developer on DEV Community has detailed StreamCart, a self-hosted shoppable video commerce system built on the Medusa v2 e-commerce framework and MeiliSearch. The system is designed to automatically link YouTube video content to product catalog listings, allowing viewers to add items to a cart without leaving the merchant's own domain. It uses a daily automated pipeline that ingests YouTube uploads, extracts product mentions from titles and descriptions, and matches them to inventory via semantic search. The project is positioned as an alternative to platform-native solutions like TikTok Shop or Instagram Shopping, which the author argues charge transaction fees of up to 15% and limit merchant data ownership. The post claims the architecture can save merchants over 45 minutes of manual work per week and cites a 2.3x increase in average order value from video-driven traffic, though these figures appear to be projections rather than independently verified results.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Two-Stage Workflow Helps Developers Catch Data Leakage Before Model Deployment

Data leakage is a common but often overlooked problem in machine learning, where information from outside the training set artificially inflates model accuracy during development but causes failure in production. A developer has proposed a standardized two-stage workflow to pinpoint the exact columns responsible for leakage before any hyperparameter tuning begins. The first stage uses Pearson correlation and single-feature R² scores to flag any feature that linearly explains more than 10% of the target variable's variance on its own. The second stage employs a shallow decision tree to detect non-linear leakage patterns that linear correlation alone would miss, such as categorical IDs that cleanly separate target classes. Together, the two checks are designed to be computationally fast and actionable, giving practitioners a clear signal about where leakage originates rather than just confirming that it exists.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Colibri Engine Runs 744B AI Model on a Laptop Using Just 25 GB RAM

Colibri is an open-source, pure C inference engine that enables GLM-5.2, a 744-billion-parameter AI model developed by Z.ai, to run on consumer laptops with as little as 25 GB of RAM. Instead of loading the entire model into memory, Colibri streams only the required 'expert' parameters from a local NVMe SSD on demand, keeping resident RAM usage around 10 GB. The model's Mixture-of-Experts architecture means only a small subset of its 21,504 routed experts are needed per token, making disk-based streaming viable. Performance is significantly slower than cloud alternatives — reaching just 0.28 to 1.83 tokens per second versus 30–50 on an H100 GPU — but the setup runs entirely offline with no API costs or data sharing. Colibri supports Linux, macOS, and Windows, and requires approximately 370 GB of local storage for the quantized model weights.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Builds LIWICODE, a Lightweight Code Analysis Tool to Rival Heavy IDEs

A software developer created LIWICODE, an open-source lightweight code analysis tool, out of frustration with loading large IDEs like Visual Studio just to inspect or benchmark small code blocks. LIWICODE is designed to launch in under 0.5 seconds, consume as little as 30–80 MB of RAM, and requires no complex project setup — users can paste or load code for instant analysis. The tool focuses on structural metrics, logical complexity, and syntax profiling at the code-snippet level rather than full enterprise solutions. By contrast, Visual Studio can occupy 10–40 GB of disk space and consume over 1.5 GB of RAM during active use, making it better suited for large-scale enterprise and cloud projects. The developer published the project on GitHub, where it initially received no stars or views, prompting them to share it with the developer community.

0 comments Read more at DEV Community