24 ms·
Dang, To address your concerns in reverse order: 1. I'm part of an incubator, and thus all the other companies are on the same IP. I'm not creating bots or vio
by marknadal 12y ago
Dang,
To address your concerns in reverse order:
1. I'm part of an incubator, and thus all the other companies are on the same IP. I'm not creating bots or violating anything, they are upvoting my work out of their own free will. Why is that bad?
2. I've been pitching it as "Open Source Firebase" or "Dropbox for Developers" since my original proof of concept (the submission you linked to in your comment). So of course when I see a bunch of developers in the Firebase thread concerned about Google's acquisition (not knowing if they can trust it/if it will be shut down), I naturally decided to post about my alternative. What wouldn't be appropriate would be if I paraded gun inside the Firebase thread as comments to people, that wouldn't be cool. But now you are punishing and hiding something that other HNers were asking for in the Firebase thread. What do you suggest I do instead?
3. This isn't a repost, it is a new version. In the same way that Meteor 0.8 to Meteor 1.0 shouldn't get buried, the same logic applies here. It is incredibly hurtful that you're trying to accuse me of foul play when I've spent countless hours trying to build something that people will like, especially when it is open source. Why are my new version releases buried but not RethinkDB's, or Meteor's, or Postgres? I feel like I accidentally rubbed you the wrong way by trying to post my work, and I'm sorry for that. What can I do instead?
- dang 12y ago> What can I do instead? It's simply a matter of following the three rules I mentioned: make clear what's changed, use an accurate and neutral title, and don't solicit upvotes.