The work those few do help people like you in ways you might not completely fathom. Reddit doesn't auto-regulate itself as much as we think. It's hard work but a small percentage of people who are paid nothing, and use 3rd-party tools to work best.
Further to that, do you have a write-up on your transition from (I assume) full-time work to this system? Did you survive on savings? What's your lifestyle like now compared to then?
How do you deal with things like negative thoughts? I find I am an 'ideas' guy, but will instantly shoot myself in the foot by researching similar services that do better than a one-man-team could do. I also have severe trouble dedicating myself to a complete-project - even if I push past the first issue mentioned above - and will really battle my inner demons who think supplying an MVP is 'good enough'.
I suppose my question is how you fight your mental battles.
Is this more a problem with the publisher and not Steam? I don't imagine Steam dictates what is and isn't a 'linked' game. I would think the publisher has the final say on what gets a new store-page. I'm curious what page the author reached to purchase the game itself.
I think you might want to do a bit more research on Steam's return policy. It's incredibly liberal.
I've played games for 10 hours and returned them with no problem. I don't think you're _wrong_ but I don't think you're right either. I worded my responses well, I told them what was good and bad, and my very reason why.
I've enjoyed their support system for returns and have very little to complain about with it.
1. Iterate through all blocks of comments.
2. Determine if there have been updates within the block of comments first (one line of three updating, for example).
2. For each block of comments, find the proceeding block of code.
3. Compare the last update of comments to the last updates of the code.
4. Warn the user when it's over a threshold.
I'm not trying to be facetious or rude, but that seems like a massive decision against something that was largely fixed? I can understand if you had software-problems with iOS but I didn't see that in your comment.
Managing those kinds of blocker apps, and security and such are all great when you're 'in the zone' and have it fresh at the forefront of your thoughts. For me, it only takes a week or so of not thinking about it before my standards slip and I have Just Another Application™ running.
I'll throw in my 2c. It was my first adventure into a Node.js CMS and used MongoDB for it's database. I'm a Javascript and Frontend Developer.
I've found it chaotically buggy - that is, sometimes it's great, amazing, works as expected and other times it simple fails quietly and in such a way I can't reverse easily - chaotic.
Saving changes to fields is hit-and-miss. Anything 'metadata'-related towards fields is a scary thing now. We use it for a particularly lightweight project but I wish we didn't after experiencing it enough now.
Note: I'm aware of its status, I still think they consider themselves 'alpha' and the developer that chose this was aware of the risks.