Live data from Hacker News

Hosting for Webhooks and Transform Streams

hook.io

11–20 of 35 posts

Re: Hosting for Webhooks and Transform Streams

#12

Like most websites of such projects, its missing the "What is X" that explains what problem your "product X" solves. (yes you are selling your product) And gives context such as being a supplement to Y and an alternative to Z. After reading every page, i still have no idea what it does, what its for and how i can learn more about Y and Z so i can understand why i need X.

It clicked for me when I saw the example curl request;

    `curl --data 'foo=bar&hello=there' http://hook.io/Marak/echo`
But yeah, up till then I felt a bit uncomfortable that the assumption was made that I already knew what it was all about.

Gotta say I really like it, maybe put the example curl request much nearer the top in a big font size?

Re: Hosting for Webhooks and Transform Streams

#13
post #8

Presumably you could pipe output through multiple hooks and chain actions up, making them composable?

100% yes. Composability is one of the greatest strengths of microservices. Here is a live example of merging multiple hooks: http://hook.io/Marak/merge and of using piping hooks together: http://hook.io/Marak/pipe

Fantastic!

Re: Hosting for Webhooks and Transform Streams

#14
post #9

"This application will be able to read and write your public and secret gists." Probably a good idea to create a separate GitHub account due to the "secret gists" permission.

We don't need access to private gists and are not enumerating the Gist API in anyway. The only code that gets shared with the site is when a new gist is created. Never previous gists. I'll investigate the Github API scope settings immediately and see if I can make the access level only public gist. Thanks for the head-up.

Thanks for the response! Keep up the great work.

Re: Hosting for Webhooks and Transform Streams

#15
Isn't this the same site from three years ago? Back then, it "aimed to take on Erlang".

https://news.ycombinator.com/item?id=2809827

... and tried to fork Node's EventEmitter into "EventEmitter2":

http://blog.nodejitsu.com/distribute-nodejs-apps-with-hookio...

This time it's "HTTP Microservices", eh? Maybe next time it'll be even more incredibly powerful and surprisingly simple.

Re: Hosting for Webhooks and Transform Streams

#17
post #12

Like most websites of such projects, its missing the "What is X" that explains what problem your "product X" solves. (yes you are selling your product) And gives context such as being a supplement to Y and an alternative to Z. After reading every page, i still have no idea what it does, what its for and how i can learn more about Y and Z so i can understand why i need X.

It clicked for me when I saw the example curl request; `curl --data 'foo=bar&hello=there' http://hook.io/Marak/echo` But yeah, up till then I felt a bit uncomfortable that the assumption was made that I already knew what it was all about. Gotta say I really like it, maybe put the example curl request much nearer the top in a big font size?

Thanks for the feedback!

I took the curl example added it to the homepage right under the tagline.

Thinking of a Hook as a standard Unix Pipe really helps solidifying the entire concept.

Re: Hosting for Webhooks and Transform Streams

#18

Isn't this the same site from three years ago? Back then, it "aimed to take on Erlang". https://news.ycombinator.com/item?id=2809827 ... and tried to fork Node's EventEmitter into "EventEmitter2": http://blog.nodejitsu.com/distribute-nodejs-apps-with-hookio... This time it's "HTTP Microservices", eh? Maybe next time it'll be even more incredibly powerful and surprisingly simple.

That's an entirely different project from Nodejitsu. I don't know if it's still active.

The hook.io domain actually expired and went to public auction recently and I was able to purchase it.

Re: Hosting for Webhooks and Transform Streams

#20
post #18

Isn't this the same site from three years ago? Back then, it "aimed to take on Erlang". https://news.ycombinator.com/item?id=2809827 ... and tried to fork Node's EventEmitter into "EventEmitter2": http://blog.nodejitsu.com/distribute-nodejs-apps-with-hookio... This time it's "HTTP Microservices", eh? Maybe next time it'll be even more incredibly powerful and surprisingly simple.

That's an entirely different project from Nodejitsu. I don't know if it's still active. The hook.io domain actually expired and went to public auction recently and I was able to purchase it.

Um... If it was an "entirely different" project from Nodejitsu, then why was it your project four years ago:

https://news.ycombinator.com/item?id=1666304

Post reply on HN