140 karma · joined April 30, 2009
Looking back now after almost 20 years (Nov 2009 to now for me), I can see the arc from what node was then to what celld can be now as your thinking has evolved
A distributed operating system running in userspace is the primitive that can break apart the siloing that has become the default across the walled gardens we all operate in
All the best in what's to come
If you want to run or use a community mirror that's totally great!
npm config set registry http://my.awesome.community.mirror
1. Early on we recognized that we would not exist as a company if the node.js community was not successful. That is why we have built and maintain over 200 open-source modules on npm. 2. Infrastructure agnostic (that’s right, you get to choose where your servers live). 3. Multiple platforms (currently Ubuntu and SmartOS). 4. 100% node.js up and down the stack. This is all we do and I think we do it better than anyone else. We also have provisioning, monitoring, and configuration management tools similar to our jitsu CLI for enterprises. 5. Commitment to immediate support: If you have a problem, you have a problem now, not tomorrow, not 3-days from now. As such, we want to make sure we grew our support team to support increased on-boarding and support requests resulting from public availability. 6. Private cloud support: this is currently where most of our customers reside. We license them software that they run in their datacenter or self-managed IaaS account.
So rest assured we ramping up for a public release. Feel free to email me at charlie [at] nodejitsu [d0t] com if you’d like to talk more.
Don’t get me wrong this is important, but it’s not in the same boat as destroying the toxic thinking “you’re not as much of a person as I am”
Posting from a different account and up voting from multiple accounts are two completely different issues. We have never used fake accounts to artificially upvote anything. Period. Nothing provided suggests otherwise. On the subject of data, if the above is an attempt to justify the original decision it is insufficient.
* How were you able to infer that both accounts were in-fact represented by a single individual?
* When one considers it objectively, two accounts with the same IP Address posting comments to HN on the same thread from different accounts is not necessarily malicious. It simply could be two different computers on the same home or work network. Point in fact, Marak and I were roommates during the early days of Nodejitsu. How would you be able to infer the difference?
Full logs of all relevant messages / comments with dates and IP Addresses included are really the only thing that will be satisfactory, feel free to email me: charlie@nodejitsu.com.
I still do not see a pattern of malicious behavior or any malicious behavior at all. As I mentioned before, I am very happy to make this water under the bridge, but please stop making false claims in public without providing more than conjecture.
* Can you enumerate what you claim we did?
* Can you provide log files illustrating your arguments?
If the answer to either of the above is "no", then please keep your false claims to yourself. I'm happy to view this as water under the bridge, but I will not allow lies about my company, Nodejitsu, to circulate: we did not (and would never) use any kind of malicious, automated, or anti-competitive tactics to falsely generate upvotes for anything on *.nodejitsu.com
Again, if you'd like to speak with me personally I am available at charlie@nodejitsu.com.
1. Your moderators are simply unable (or unwilling) to distinguish "sockpuppets" from a legitimate community of developers (that is the node.js community). Yes, when we post something to HN we send out the link via Twitter and IM to colleagues in the node.js community who may potentially upvote it. This is natural "word of mouth". We have never used bots, or any kind of malicious automation to ensure posts reach the front-page.
2. There is no transparency for bans, nor is the ban every communicated to the owner of the HN account. If you think an account is unfairly trying to manipulate the voting system; you have to contact them. Anything less is blatantly ambiguous and unacceptable.
3. Given the silent nature of bans on HN, we have no choice but to move onto a new HN account and continue to submit legitimate posts using legitimate word of mouth dissemination. Perhaps you view this as "sockpuppets," but what other choice do we have?
4. In the particular case of Nodejitsu, this behavior is even more unacceptable. We are a platform-as-a-service where any user can create a publicly available application on a subdomain of nodejitsu.com. How can you ban the entire *.nodejitsu.com domain when we are not responsible for malicious actions (real or perceived) taken by a given user? This is not an admission that any such behavior has taken place; I'm sure that your claim is addressed in [1]-[3].
In the copyright world, site owners are protected by malicious actions of users through DMCA safe-harbor. In such senarios, the owner of the site will be contacted and the malicious behavior (real or perceived) can be addressed and/or removed. By silently banning posts and not communicating with members of the HN community about what you perceive as malicious behavior you are doing yourself a serious detriment. This has (and continues to) raise questions about the legitimacy of the content on HN as just a shill for YCombinator.
If you'd like to speak with me personally you can email charlie@nodejitsu.com
Charlie Robbins Founder and CEO Nodejitsu Inc.
Best Comment: @chjj "Is it me, or is this argument over a single colon?"
https://github.com/joyent/node/pull/1580#issuecomment-192688...
The project had been internal for a year and as such is pretty mature technically, but has a nascent community. If you're thinking about running node.js in production definitely check it out!
I have to disagree with you about it's notoriety. With the v0.5.0 release we have some really interesting features (HTTPS, Websockets) that you simply won't find in other battle-hardened production-ready HTTP proxies. For example, HAProxy has neither of these features and is the library of choice for a lot of developers / sysadmins
Just use dnode and socket.io. The authors (substack and guille respectively) have ridiculous chops when it comes to Node.js and have been working on their projects for more than a year.
http://substack.net/posts/85e1bd/DNode-Asynchronous-Remote-M... http://socket.io
cd /path/to/repository
// create a valid package.json
npm publish .
npm install channel-server
http://github.com/nodejitsu http://github.com/indexzero
Node to win :-D
I'm the author of forever and node-http-proxy and it's good to see our production quality node.js software being used by other people :-)
Would you consider that a valid concern of process monitoring?
Planned features to Forever include this from the command line, but if you use it from node directly one could implement that feature now: