Developer Builds Cross-Platform VPN Client Using Pure Dart, No Native Frameworks

·1 views

A developer has created sstp_client, a fully Dart-based implementation of Microsoft's Secure Socket Tunneling Protocol (MS-SSTP) and Point-to-Point Protocol (PPP), capable of running on Linux, Windows, and macOS. The project was built to test how far Dart could be pushed beyond its typical UI development role into low-level systems programming. The architecture is split into decoupled layers handling TLS transport, SSTP framing, PPP negotiation, and platform-specific TUN device routing. Platform differences were addressed individually, including Wintun driver integration on Windows and utun socket handling on macOS, using Dart's Foreign Function Interface. The work highlights Dart's potential for network-level and systems programming outside the Flutter ecosystem.

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)

Developer Releases Open-Source Claude Code Plugin With 3,500+ Tests for Context Control

A developer has released an open-source Python plugin called Chamnan (v1.22.1) designed to improve context management, token budgeting, and security when working with Claude Code on large or sensitive codebases. Built using only Python's standard library with no external dependencies, the tool pre-processes repository data locally before it reaches Claude Code, preventing unintended data leaks. The plugin also retains session memory across interactions, reducing redundant token usage by storing project history and architectural decisions in a local directory. Development involved reviewing over 1,000 research papers and technical documents, with reliability validated through more than 3,500 automated tests. The developer has published the project on GitHub and is seeking community feedback on edge cases, safety features, and potential improvements.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Tests Tick Data Strategies for Gold and Silver Trading via Precious Metals API

A quantitative developer has shared findings from live testing of tick-level data streams for gold (XAUUSD) and silver (XAGUSD) trading using the ALLTICK API via WebSocket connections. Unlike minute-bar data, tick data captures every individual price quote with timestamps, preserving the microstructural detail that gets erased during volatile events like Non-Farm Payrolls or CPI releases. Four strategy types were evaluated, with correlation arbitrage between gold and silver and event-driven scalping around macro announcements yielding the strongest combined results. The developer noted that data quality — including dropped packets, duplicate messages, and out-of-order ticks — proved a greater operational challenge than strategy logic itself. Running dual continuous precious metals subscriptions costs roughly a few tens of dollars per month in server expenses.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why Repeating Yourself Louder Never Works — and What to Do Instead

Software engineer and writer Asael Shinder argues that failed explanations stem from using the wrong frame, not the wrong words. He recommends preparing at least three versions of any technical idea — mechanical, consequence-based, and analogical — to suit different audiences such as engineers, product managers, or long-tenured colleagues. Shinder advises communicators to watch for physical cues like a lean or a genuine follow-up question to know when understanding has clicked. He cautions against continuing to explain past the point of comprehension, calling it a failure in itself. When all three approaches miss, he suggests asking the listener to paraphrase back what they heard, as their misunderstanding will reveal which angle to try next.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Decide What to Automate in Web App Regression Testing

A QA team once spent two days manually regression testing a multi-page quiz form that behaved differently across user roles and account states, highlighting the hidden complexity of repetitive test cycles. The core challenge was not the mechanical clicking but maintaining a reliable definition of expected outcomes across varied scenarios. Experts suggest splitting regression problems into three layers: unit tests for calculation logic, API or integration tests for permissions and data storage, and browser end-to-end tests only for full user journey validation. Tools like Playwright or Cypress are capable but are not complete solutions on their own; choosing the right test type for each risk matters more than picking a tool first. A practical starting point is one role, one prepared account, and one defined path — not full coverage from day one.

0 comments Read more at DEV Community