The best part of the no-build, small-footprint approach is longevity: no dependency rot, nothing to maintain, and it'll still open and run in ten years. We've half-forgotten that "view source and hack it" is how a lot of us learned the web in the first place. Good to see tools that lean back into that.
Maybe I'm not reading this right, but it has its own markup language called "Bug". This is the opposite of no-rot. If it's using technologies you've never heard of before, who is going to be around to maintain them in 10 years?
A fair amount of software follows the model but does not use the term, everytime I go on the play store to look for an app I encounter many that offer a free version with limited features.
The term doesn't make much sense anymore because we don't share software, we just download it from the source. The business model makes more sense than ever, though.
Most of the shareware I got was downloaded from BBSes and the internet and even these central repositories that are the norm now are nothing new, in the 80s I went to a local BBS that was dedicated to shareware and in the 90s a handful of sites, and there was always the developer's site for the direct download but often they just linked you to one of the big repositories. The only shareware I can remember getting physically was the stuff that came on a disk/cd with some magazine I bought just for the CD filled with shareware. I miss those CDs.
For as long as I can remember shareware was more than the physical sharing, it was the model of a free version that you could share and a paid version and sometimes both versions were the same and it was just requested that you pay if you can (buy me a coffee). Some of this shareware was even adware, I remember getting some drawing program that had a popup every 15 minutes advertising the author's programs, it would go away if you paid; my first "hack" was realizing that I could start the program and then turn the computers date back a day giving me 24 hours and 15 minutes before the popup appeared, after a couple weeks my mom tasked me with fixing the computer, she was having to reset the date every couple days for some reason.
Edit: deleted a comment about source code, realize I misread your post. Should try to fix a couple of those sentences as well, my language skills tend to fall apart when I get nostalgic and I find it very difficult to restructure the thought, I lose the nostalgia.
I meant more as an active use-term for software licensing that kiki uses (and in the sense of the OP's question), not in its historical sense that it is used by writers now.
I happen to have a cat named Kiki who looks rather like the mascot for this project. Her health is failing, now. I just spent the night on my living room floor next to her. I'll, likely have to put her down, today.
I might use this project to make a memorial page for her.
I'm sorry you're dealing with this. I had an orange tabby also named Kiki for most of my childhood through early adulthood, 16 years. He suffered from kidney failure and it was a sad day when we had to put him down.
I'm sorry to hear about Kiki. She's very beautiful, thanks for sharing.
She reminds me of my tuxedo cat Bob who recently passed. I remember laying down all night in the comfort room before he had to be put down and sobbing knowing how much pain he was in. It's really hard.
I think a memorial site is a lovely idea, I created one for my cat as well: https://bob.duchastel.com
I wish we could get back to a “mom and pop” software market. Itch.io feels like it’s doing a lot of work for indie software that used to just be everywhere and easy to stumble onto.
If selling software for money wasn’t such a pain in the arse I would put stuff on my website rather than itch.io
It took me two weeks, plus sending IDs, incorporating an ltd, to get a license to sell software with Paddle. With itch I just need a paypal/stripe account.
I am going through this right now! I am provisionally approved and still waiting. Even worse I am going through SMS phone number verification with SMTP2GO.
Apparently if you wanna send automated texts in America, you need a real phone number. And to not get immediately blocked, you need to fill out a form that goes to the major carriers for approval (like AT&T). And the form is not unlike Paddle's verification. You need a company, EIN, samples of what your texts will look like. Massive pain.
> And the form is not unlike Paddle's verification. You need a company, EIN, samples of what your texts will look like. Massive pain.
In defense of Paddle (I use them for my own livelihood), they're on the hook for remitting sales taxes to ALL the governments where your customers might reside. They also manage customer disputes, chargebacks, refunds etc. I always redirect support emails to Paddle.net [0] which does the trick 99% of the time.
Stripe or PayPal are nothing like that. They're just payment platforms.
Since Paddle takes on so much liability, it seems reasonable to ask for a lot of initial paperwork from its sellers.
Yep, it's called 10DLC. My teams work on telephony integrations, and for the devs to even test that outbound SMS is working, we need to go through this process with every provider we integrate. Massive pain, indeed.
If you accept cryptocurrency you don’t need to do any of this, and not even deal with PayPal (who WILL rob you without a second thought, as has been well documented on the internet for MULTIPLE decades at this point).
I would like to (Bitcoin Lightning only, with a healthy convenience discount) but I'd have to move off Hetzner for my servers because they are really against crypto in a very vague way, and again, that's a lot more work than just using itch.io
Hello, neat project. I am also from Edmonton area. I wonder if we have talked previously, in the the late 90s I ran a local BBS system with my colleague.
"It's built so that if something looks wrong, you can change it yourself without spending hours reading tutorials and watching coding videos"
Does anyone do this?
Every none coder I know just has llms build everything for them - can't imagine why they'd be looking up coding tutorials for a homepage.
include $_GET[...], register_globals, magic quotes, extract($_REQUEST), weak comparisons, loose typing, eval, risky file upload defaults/patterns, preg_replace /e, dangerous deserialization gadget chains, path traversal into includes, and the whole "URLs can be file paths" abstraction...
PHP is basically "RCE-as-a-Service" as far as I'm concerned. Allowing a URL in any function that wanted a file path was an absolutely bone-headed design choice. They made `curl | php` a language feature.
Like everything it depends on your goals. As a novice developer PHP is wonderful. Everything you see as an obvious security failing is exactly what made it great to a new dev back when most of that was still allowed by default.
C and Go are two languages I feel like if you learn them, you can come back years later and if your memory is still good, you could get back up to speed pretty darn quickly. Every few years I go back to Go and try to build web apps using only the standard libraries, and I always find myself very quickly picking up all the concepts.
For some reason, Java has the same feeling. Professionally I do both embedded and statistical computing, and Java's been nearly anathema to this. But every 5 years I patch a hobby project I did once in college, and it comes right back (and with JVM hot reloading too.) It gives me the engineering warm and fuzzies.
I'm not going to blame you _too_ much, since I had similar suspicion, but you could have (as I did) just downloaded the .zip file and examined the contents. In the shareware version, some things are probably missing (I think not all themes are there), but otherwise it's just a bunch of PHP files, no obfuscation or anything. The markup language is configured in a text file, and the parser for that file is just next to it. The configuration is used for configuring the markup parser, which is also present. And so on. It's not open-source only if your definition of OSS is "has to have a Github page".
Just because you can see the source code does not make it open source. Shareware software is proprietary software.
Open source means free software, which is a license that allows unrestricted use of the source code. Shareware isn’t free (as in speech OR as in beer) software.
The definition of OSS is well defined, and isn’t my definition. This is why there is a term called “OSI-approved license”.
Ok, but given that there are no license terms anywhere (not in the .zip with the code, and I don't think there is one on the web page), you also can't say that this particular license disallows modification. The terms are simply not specified.
Further, the very operation of this code requires the user to modify it, as described in the usage instructions. You might say that this only gives permission to modify a particular subset of the provided code, to which I don't have an answer (other than that it's unspecified).
You might not be able to fork it and distribute your modified version to others. It's not free/libre. But you can read it and modify it for your own use. To me, that's plenty enough for a project like this. As far as proprietary code goes, this is as harmless as it can get - instead of criticizing it for not being open enough, it would be better to praise it for being this open, to encourage other authors (who would otherwise keep all the code as closed as possible) to follow this model instead.
Yes, FLOSS is good and great, but it's impossible to make all code like that; in reality, where we deal with DRM, app stores, and heaps of unrepairable, uninspectable, obfuscated, phone-home activated code all around, even a bit more openness helps.