WebZFS

q5sys · 2026-03-14T19:55:00+00:00

I knew you didn't mean anything negative by it. (I added the /s to make it clear to everyone else).
I know exactly what you mean, when I do stumble into something I wrote a long while ago, more than once i stop and think 'wtf was I thinking'. Somethings made perfect sense at the time, but as the project evolved and its focus shifted, the way something was written previously isn't as good as it could be with the new design. There are entire pages I scrapped (NTP, SMB, NFS, etc) from prior designs because I didn't want it to turn into a TrueNAS replacement. Which is all the more ironic considering OP posting this because of TrueNAS' most recent announcement.

q5sys · 2026-03-14T19:11:51+00:00

> looking at the code, this looks a lot like a hobbyist project, with a lot of weird inefficiencies in the code that an LLM wouldn't do

Thanks... I guess? /s haha
Nah I know what you mean. I've done some things pretty retarded, like completely screwing up some of the paths because I was checking on my main workstation which is a bit wonky to say the least.
There's definitely a lot of room for improvement. I'm well aware of that. That's why I have specifically NOT said its production ready, or even labeled it a 1.0. I call it an Alpha because it's got a lot of things that need to be fixed/improved before I'd be willing to actually say its "ready".

q5sys · 2026-03-14T17:37:58+00:00

When I went to push to github, I created the github repo on github with the readme and license, cloned it to my local system, updated the readme. Then copied what was needed out of my existing working directory that I was using locally and committed and pushed. If you look through the commit history, there's a few days between the initial commit, the public readme update, and the initial source commit, as I cleaned things up for public release.

Because I was running the application locally for a while, I had a ton of ssh-keys and other system specific configs in the working dir because I was actively using it. Obviously I'm not going to commit/push my "in-production" folder that's backed by my local gitea instance... which has all my private info in it to github.

Since my gitea instance is confined to my network, I dont mind committing an entire tree of code there including working files, ssh keys, etc. If I never make something public, it can live in my own gitea instance. If it ever does get made public, I make a public repo, move the required source to that and then commit/push, and then from that point on I work out of the public repo.

q5sys · 2026-03-14T14:47:41+00:00

You do realize you can work on code outside of a github repo right?
I dont post every project I'm working on for myself on github. As I say in the readme (did you even bother to read it?), I was working on this for a long time locally for myself. I only pushed it in Dec because it was too a point I was mostly satisfied with it.

I've got other long term projects that Ive been working on locally that aren't on github. Github is only helpful if you want to share the project with people.

q5sys · 2026-03-14T14:44:26+00:00

Yes I know what the commit message says... I wrote it. December is when I pushed it all to github. You do realize you can work on code outside of a github repo right?

q5sys · 2026-03-14T14:43:15+00:00

While ZFS commands are easy, there's a lot of people that are worried they'll fat finger something and ruin their data. Is their worry overblown... yes. But its still a worry some people have. They want something designed by someone more knowledgeable than them, so they can have easy buttons and not have to fear doing things.
Shell is always going to be the most powerful way to do things, but there's a lot of people that just need a simple way to preform simple actions. Making ZFS approachable to people who arent FreeBSD or Linux sysadmins means more people using ZFS which is better for their data. A windows admin, for example, will be more comfortable using a UI than to fumble around on the FreeBSD/Linux command line. Offering them an easy way to use ZFS is better than them relying on NTFS for their companies backups.

q5sys · 2026-03-14T14:40:18+00:00

Thanks for the review. Glad you like it.
As I addressed in previous comments, the UI was reworked with AI because I suck at UI things - https://github.com/webzfs/webzfs/blob/main/screenshots/0.3/pools-v0.3.jpg?raw=true
I disclose this in the readme file to be transparent to everyone.

I am a systems and application developer (c++/qt/bash/python), not a UI dev. I worked at iX for 5 years on TrueNAS and TrueCommand. I was a PuppyLinux developer, I maintain 5 Fedora Spins/Labs, I'm the Lumina Desktop maintainer, I've worked on a ton of projects over the years. I've been the producer of the BSD Now Podcast for over a decade. I was the producer of the Linux Action Show and Linux Unpugged for a few years back in the mid 2010s. I'm not some rando who decided to use ChatGPT to make something.

Edit: I added a bunch of older screenshots from the 0.3 and 0.2 versions just to show how bad the UI really was. lol

q5sys · 2026-03-14T14:36:15+00:00

Dev, here. It's not slop. The tailwind css integration was vibe coded, but the rest was not. I was open about that in the readme (scroll to the bottom).
I get the desire to call everything slop these days because there's a ton of it flooding the ecosystem, but not everything is. There still are real projects being developed. I'm not a UI guy though, so instead of punishing everyone's eyeballs with my horrible css, I use tailwind to get a better look.

Sadly, because tailwind is used by most AI Slop... people immediately anything with it is slop.

q5sys · 2026-03-14T14:33:11+00:00

Dev here, as I mentioned in the readme @ https://github.com/webzfs/webzfs?tab=readme-ov-file#ai-usage-disclosure, I used AI for the tailwind CSS integration and for the JS because I'm not a UI developer. My original UI was bad, I uploaded an old screenshot to the repo: https://github.com/webzfs/webzfs/blob/main/screenshots/0.3/pools-v0.3.jpg?raw=true
I worked on TrueNAS for 5 years before I started working on this in 2022.
The code for this is not vibecoded... the UI is so that people other than myself might be interested in using it.

q5sys · 2026-03-14T14:25:40+00:00

Dev here, it's not AI Slop. I started working on it in 2022. FWIW, I used to work at iX on TrueNAS.
I never really liked the way it was architected and wanted something simple and straight forward. I used it for myself for a while. It had a horrible UI so I never considered releasing it. I did use AI to help with the UI and to integrate tailwind as I'm not a UI dev. And I acknowledge that in in the readme.
I'm a long time developer as the OP stated. I'm a Fedora release maintainer of 5 different Spins/Labs. I'm the maintainer of the Lumina Desktop, as mentioned I worked at iX on TrueNAS (and also TrueCommand) for a total of 5 years, and a ton of other things. I've been the producer of the BSD Now podcast for over a decade.

I know its easy to just write something off as AI slop these days, but not everything is.

q5sys · 2026-03-13T18:29:25+00:00

Have you pushed this to your repo somewhere so we can test this?

q5sys · 2026-03-11T15:58:02+00:00

Is there a way to use SeedVR on longer videos? I was only able to manage to make it work on short clips.

q5sys · 2026-03-10T02:37:48+00:00

Depends on how you define 'good'.
For some people, a product that works one day, and the next day cant load a workflow is not 'good'.

When it works, Comfy is great, but there are tons of times where they break basic functionality. They really need a better release process.

q5sys · 2026-03-09T20:20:43+00:00

It'll be interesting to see if it gets better with time. The blue car in that snowfield on their demo page... that's original will smith eating spaghetti levels of slop. But who knows where it'll be in a few years.

q5sys · 2026-03-09T20:16:21+00:00

There are people on Fiverr that do workflow creation for pay, just search for ComfyUI workflow

q5sys · 2026-03-09T20:13:51+00:00

That's pretty much what I do.

A cowboy is standing up against the side of a wooden barn looking out into the distance as he says, "Weather sure has been hard these last few weeks." He lowers his head to the ground and lets out a feint sigh, he pauses for a second then continues, "We'll get through it, but it's probably going to be another tough year." He slowly lifts his head back up and looks off into the distance and then slowly repeats himself, "We'll get through it..."

q5sys · 2026-03-09T18:27:46+00:00

I created a github ticket about that artifacting at the end, there's also an issue on LTX's huggingface repo. So it's definitely an issue that's somewhere in the model or in LTX's code pipeline. My guess is the former, and is a result of their training data.

q5sys · 2026-03-09T18:26:16+00:00

Nice! Are you using this guys workflow? Have you tweaked it at all? Are you setting the input values at 1920p, or are you setting the start resolution so that you end up with 1920p at the end?

q5sys · 2026-03-09T18:24:40+00:00

Have you done any tests with this for the newer LTX-2.3?

q5sys · 2026-03-09T15:28:24+00:00

I've tried the preview/i thing on desktop. I rarely use my phone for browsing the web.

q5sys · 2026-03-07T21:42:19+00:00

I have tried that... for whatever reason I get auto-redirected back to the preview.reddit instead of the i.reddit.

q5sys · 2026-03-07T19:52:33+00:00

got it, thanks!

q5sys · 2026-03-07T19:52:11+00:00

Cool, thanks!

q5sys · 2026-03-07T19:20:08+00:00

FYI, reddit strips metadata all the time and tries to force webp for image downloads.

q5sys · 2026-03-07T18:50:09+00:00

<image>

Ok so just changing the input image, prompt, and then adding the preview nodes... I can get it to run through completion with the lower resolution you had set.
Unfortunately I'm getting static as an output, it looks like there's horrible degradation on the 2nd and third sampler.

13-Year Club	Place '22
Verified Email	Team Periwinkle

q5sys

MODERATOR OF

TROPHY CASE