Comment by jdenning
I just took a look at your project - you really need to simplify the README. I read the whole thing but it’s still not clear to me what you app actually does.
I have no idea what a “Social Operating System” is supposed to be. Seems like it’s a web/mobile app framework, but it’s completely unclear why I would want to use it. You need an “elevator pitch”.
There are hundreds of frameworks, if you want developers to use yours, maybe show some example code? No one is going to spend a bunch of effort trying to build with your framework if they can’t see an advantage.
Not trying to be a hater, I care and want you to succeed
Edit: just read some of the links in the readme - so it also has something to do with crypto and micropayments? Why would I want to use your “QBUX”? Would a developer only be able to get paid in your crypto? If so, why should they trust that you won’t rugpull? If you want people to care about your project, you need to think about what they care about (pro tip: nobody cares about making you rich via support contracts or shitcoin schemes. Sorry.)
I am not sure what you read that said any of the things you asserted in the "Edit" section. None of that is true. The token doesn't even exist yet. There is no "rugpull" possible in any event.
But I think this illustrates perfectly what I said originally. Context matters. The context on HN is "I see a word that triggers me (token / web3) somewhere and I immediately assume all these things I haven't seen or read, and forget about anything you actually did."
That's why it is very important how you present things. The original Facebook was just a bunch of profiles in php. And yet people used it like mad and investors camped out Zuck's dorm room. It's not so much about what you build but how you present it.