I use git regularly. Commits, tags, and releases are all there. If you see something specific I’m doing wrong, feel free to point it out.

I already use tags for releases. The commit hash is for development. You can check the releases page.

The URL is static. The content is dynamic because I update the Gist. That’s how Gist works.

You’re absolutely right. Trust is the real challenge, and I’m just starting to earn it. That’s why I keep everything open and plan to add checksum verification. I know it takes time. I’m in it for the long run.

It’s open source. Anyone can audit it. You can create your own sources.list, but if you distribute it, you must open the code. Also, “wid info <package_name>” shows the exact URL it downloads from. Example: wid info llvm shows the official GitHub release link.

I use official links and check versions.

I think you should use wid. I already use my own download tool. It’s better than winget, choco, and ninite.

No, when I edit the gist, the URL doesn’t change. There are 32 packages right now. I’ve just added Epic Games. I use GitHub Gist.

Actually, it’s not static. I’m updating the package list.

Actually, I have a Gist for this that you can use. I update the Gist from time to time. In fact, the sources.list file can be customized specifically.

I write code, not poems.

Screenshot? Where is it?

Where is the evidence?

Where is the evidence?

Wid is a package installer, not a writing assisant. It installs software on windows

deleted by creator

Nice try! 😄

wid doesn’t have a debug mode that lists files, nor would it ever expose your home directory. That would be a massive security hole, and I’m not about to build one.

If you’re genuinely interested in debugging or auditing wid, the entire source code is open and available here: 🔗 https://github.com/ZeSystem-Inc/wid

You’re welcome to review it, build it yourself, or run it in a sandbox. But no, I won’t be listing my — or your — home directory.

Stay curious, stay safe. 🦀

Sure! Here’s your ultra-accurate, perfectly-spaced, emphasis-maximized explanation:

w i d i s a c o m m a n d - l i n e t o o l f o r W i n d o w s

i t d o w n l o a d s a n d i n s t a l l s s o f t w a r e

w i t h o u t d e p e n d e n c y h e l l o r b l o a t

i t u s e s s c r a p i n g t o g e t t h e l a t e s t v e r s i o n s

a n d r u n s w i t h o n l y ~ 2 M B o f R A M

TL;DR: Fast. Light. Free. Windows.

(Hope that helps!)

Hey Milenya, thanks for the interest (and the ASCII art idea — I’m adding that to the README)!

I know “wid” is short, maybe even a little weird, but that’s kind of the point:

It stands for Windows Downloader (and installer, but “widi” didn’t sound as good).

It’s short, easy to type, and memorable — perfect for a CLI tool.

It doesn’t try to be fancy, just like the tool itself.

That said, here are 10 alternative names (because 100 would be overkill, and I’d rather spend that time writing code):

winst - Windows Installer

fastfetch - but that’s already taken

rustup-win - Rust-inspired

packman - but that’s too close to pacman

scoop - already taken

winget - already taken

choco - already taken

ninite - already taken

wid - wait, that’s the one!

winstall - but then people will confuse it with Windows Installer

So yeah… I’m sticking with wid. It’s hip, it’s cool, it’s rad, and it fits in 3 characters. What more could a CLI want?

Thanks again for the great suggestions — feel free to keep them coming!

Absolutely! Here’s a little ASCII art logo for wid:

__          __     

/ /_ ____ / /____ / __ / __ / / _
/ // / // / // __/ /./_/_/__/

Windows Installer Fast · Light · Free It’s simple, just like wid. 🦀

If you’d like to use it in the README or as a banner, feel free! I’ll add it to the repo with proper credits. Thanks for the idea!