惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

云风的 BLOG
云风的 BLOG
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
博客园 - 叶小钗
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
V
V2EX
酷 壳 – CoolShell
酷 壳 – CoolShell
月光博客
月光博客
人人都是产品经理
人人都是产品经理
宝玉的分享
宝玉的分享
博客园 - 司徒正美
WordPress大学
WordPress大学
Microsoft Azure Blog
Microsoft Azure Blog
罗磊的独立博客
Vercel News
Vercel News
T
The Blog of Author Tim Ferriss
T
Tailwind CSS Blog
A
About on SuperTechFans
Apple Machine Learning Research
Apple Machine Learning Research
L
LangChain Blog
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
V
Visual Studio Blog
S
SegmentFault 最新的问题
Google DeepMind News
Google DeepMind News
博客园 - 聂微东

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
WSL UI, WSL Dashboard, and a "Counterfeit" Claim That Doe...
Ian Packard · 2026-06-17 · via DEV Community

There is now a second free WSL management tool out there called WSL Dashboard, published by a developer who goes by owu on GitHub. It is open source, it has more GitHub stars than WSL UI, and it is clearly the product of real effort. I have no problem with any of that. Competition is good for users, and WSL deserves more than one good GUI.

What I do have a problem with is this notice, which appears both on wslui.com and in the WSL Dashboard README:

"This software is not distributed through the Microsoft Store. Any application listed there under the same name is unauthorized and may be counterfeit. Please do not download it to avoid potential scams."

WSL UI is on the Microsoft Store. It has been since January. So that notice is, in plain terms, telling people that the genuine, certified, earlier WSL tool is a counterfeit scam.

It isn't. And the entire claim falls apart the moment you look at the dates — all of which are public, timestamped, and independently verifiable.

What this post is, and what it isn't

This is not a "my project is better than yours" post. I'm not going to pick apart WSL Dashboard's features or pretend it's a bad piece of software. It isn't.

This is a correction of one specific, factual claim: that the version of WSL UI on the Microsoft Store is unauthorized or counterfeit. That claim is demonstrably false, and because it's aimed at a tool people trust, it's worth setting straight properly — with evidence, not adjectives.

The timeline

Every date below comes from a public record. I've linked the sources so you don't have to take my word for any of it.

Date Event How to verify
2008-12-11 octasoft.co.uk registered. Octasoft Ltd has existed for well over a decade. Nominet WHOIS for octasoft.co.uk
2025-12-14 The octasoft-ltd/wsl-ui repository is created. GitHub API (created_at)
2026-01-10 WSL UI's first public release, v0.2.0. WSL UI releases
2026-01-13 WSL UI v0.14.0 is published to the Microsoft Store. The announcement post
2026-01-18 The owu/wsl-dashboard repository is created — 35 days after WSL UI's, and 5 days after WSL UI was already on the Store. GitHub API (created_at)
2026-01-19 WSL Dashboard's first release, v0.1.0. WSL Dashboard releases
2026-04-25 wslui.com is registered by owu — four months after WSL UI shipped, three months after it reached the Store. RDAP for wslui.com (registration date)
2026-05-02 The "may be counterfeit" notice is added to the WSL Dashboard README, in a commit titled simply notice. The exact commit

You can read the full timeline at a glance in the diagram at the top of this post.

Three things that don't add up

1. The "counterfeit" came first

The notice warns people away from "any application listed [on the Microsoft Store] under the same name." But WSL UI was on the Microsoft Store on 13 January 2026five days before the WSL Dashboard repository even existed, and nearly four months before the counterfeit notice was written.

You cannot be a counterfeit of something that doesn't exist yet. The Microsoft Store listing is the original, published first, by a company (Octasoft Ltd) with a verifiable corporate history going back to 2008. The Store certifies the publisher identity before anything goes live — that's the whole point of the certification process I wrote about back in January.

2. They named it "WSL Dashboard" — but bought wslui.com

Here's the part I find hardest to read as an accident. The product is called WSL Dashboard. The repository is wsl-dashboard. The site title, the README, the download buttons — all say WSL Dashboard.

But the domain they registered is wslui.com — the obvious domain for a product called WSL UI. Which is my project's name, not theirs.

So the situation is: a tool that isn't called "WSL UI" registered the "WSL UI" domain, four months after WSL UI was already established, and then used that domain to tell people the real WSL UI is a counterfeit.

3. Stars aren't a time machine

WSL Dashboard currently has far more GitHub stars than WSL UI — somewhere north of 2,600 to my ~250 at the time of writing. Good for them; genuinely. Popularity is earned and theirs is growing faster than mine.

But stars don't change chronology. A more popular project that arrived second is still the project that arrived second. The dates above don't move no matter how many people star a repository.

Alternatives are welcome. Smears aren't.

I want to be completely clear, because this is the actual point of the post:

I am glad WSL Dashboard exists. More tools mean more ideas, more pressure to improve, and more choice for the people who actually use WSL every day. If you've tried both and you prefer WSL Dashboard, that's a perfectly good outcome. Use what works for you. That has never been my objection and it never will be.

My objection is narrow and specific: don't tell users that the original, certified tool is a counterfeit scam. That's not competition. It's not "marketing." It's a false statement about a real product that real people rely on, and it damages trust in WSL tooling generally — including, eventually, WSL Dashboard's own.

Compete on features. Compete on performance — WSL Dashboard's ~10MB Rust-and-Slint footprint is a genuinely nice number, and I'd happily lose users to a faster tool fair and square. Compete on anything you like. Just not on a claim the public record flatly contradicts.

For WSL UI users: how to confirm you've got the real thing

If the notice gave you a moment's doubt, here's how to verify the Microsoft Store listing yourself, without trusting me either:

  • Check the publisher. On the Store listing, the publisher is Octasoft Ltd. Microsoft verifies publisher identity during certification — an "unauthorized" copy can't list itself under a certified publisher's name.
  • Cross-check GitHub. The Store build and the octasoft-ltd/wsl-ui repository are the same project, by the same author, and the repo predates everything discussed here.
  • Look at the dates. Everything in the table above is in a public API or registry. If anything I've said is wrong, the records will show it — please tell me and I'll correct it.

WSL UI is, and always has been, free for personal use, open source, and minimal on telemetry. None of that changed.

An open invitation

To owu: I don't want a feud, and I'm not asking you to take your tool down or stop competing. I'm asking one thing — remove the "counterfeit" notice, from both wslui.com and the README. It's untrue, the timeline proves it, and you don't need it. Your tool can stand on its own merits.

Build the better dashboard if you can. I'll keep trying to build the better WSL UI. Users win either way — which is how this is supposed to work.


Every claim in this post is backed by a public, timestamped source. The counterfeit notice has been preserved in the Wayback Machine and remains in the WSL Dashboard git history, so this record stands regardless of any later edits.


Originally published at https://wsl-ui.octasoft.co.uk/blog/wsl-ui-and-the-counterfeit-claim