I didn’t know GitHub Pages was a thing for this use case. I’ll look into it — it might be a better fit for future projects.
mietkiewski_dev
joined 4 days ago
That applies to licensed software. Here you’re not buying a license — just the right to use the tool. A license is only needed if someone wants to copy, modify or redistribute it.
Buying the product gives people the right to use it — the license is only needed for redistribution or modifying the files. But yeah, you’re right that adding a license would make everything clearer. I’ll include one next time to avoid any confusion.
Just to clarify — I don’t have any issue with people analyzing or quoting small parts of the code. The project is intentionally distributed on Gumroad as a “0$+” closed‑source release rather than as an open‑source GitHub repo. Since there’s no license file, it defaults to all rights reserved, which means full files can’t be redistributed.
Part of this project is also a learning exercise for me in how to package and distribute small tools. I’m genuinely interested in feedback on this approach.
But if someone posts the entire file publicly, it makes it harder for me to actually demonstrate the distribution model I’m experimenting with — the whole point was to release it through Gumroad, not as a fully exposed source dump.
Nice... Music definitely helps.
Hey, could you remove the full Main.py from your comment? The project is closed‑source, so sharing the entire file isn’t allowed. Thanks!
Nice. For me those first steps always stretch out… I sit down “just to start” and suddenly 20 minutes are gone.
I’m still experimenting with what helps me start working. If you have any small rituals or tricks, I’d love to hear them.
Starting has always been the hardest part for me. Curious what helps you get going — I’m still figuring it out myself.
Fair point — I get where you’re coming from. I’m still experimenting with distribution, so this setup isn’t final. GitHub Pages might be a cleaner option, I’ll check it out.