ahochhaus

9 ms·

1. 31.▲
   How to approach your own career like an entrepreneur(fortune.com)

   2 points by ahochhaus 12y ago|0 comments
2. 32.▲
   Go 1.4 is released(blog.golang.org)

   453 points by ahochhaus 12y ago|257 comments
3. 33.▲
   by ahochhaus 12y ago

   Great feedback. We are too light on details. I'm adding a more detailed description shortly. The original idea with the video was to show the types of functionality that FormBig exposes (eg: integrated logins, JS-based logic, rich text
4. 34.▲
   by ahochhaus 12y ago

   We don't have a final pricing model figured out yet, but we would like to support applications with a variety of needs. If we had a per-form based pricing option would that meet your needs? Can you describe your use case a bit and the
5. 35.▲
   by ahochhaus 12y ago

   The two co-founders (myself and eksurfus) are here to answer any questions. We are hoping to gain insight into specific use cases for FormBig to guide our to market strategy and development priorities. Thanks for any feedback you can offer.
6. 36.▲
   Ask HN: Use cases for forms-based software tool?

   10 points by ahochhaus 12y ago|11 comments
7. 37.▲
   by ahochhaus 12y ago

   I agree. If at some point dropinchat.com allowed for messaging between networks XMPP support would be great to add. At this point we only allowing for messaging other drop in chat users so no such protocol is needed. My only point was that
8. 38.▲
   by ahochhaus 12y ago

   Sorry for the XSS problems. They are fixed now so it is safe to visit and test again if you like. Thanks owenversteeg for warning everyone.
9. 39.▲
   by ahochhaus 12y ago

   At this point dropinchat.com does not support sending messages to more than one user. However, we do plan to add that feature as our team has time. The documentation on dropinchat.com mentions "groups" as a set of users which are
10. 40.▲
    by ahochhaus 12y ago

    Hi scrollaway. Thanks for the support. XMPP seems really great in a context of needing to inter-operate with other servers. However, for our use-case all communication was in a silo of a single site so this was not a major benefit to Drop-I
11. 41.▲
    by ahochhaus 12y ago

    Hi waitingkuo. Thanks for the encouragement. Currently I wouldn't recommend using Drop-In Chat in a production context as the code is too new and not really stable. When we get to the point we think the product is ready for production
12. 42.▲
    by ahochhaus 12y ago

    Thanks for the encouragement. What we have is certainly just a first step. We will continue to keep making incremental improvements now that YC Hacks is over.
13. 43.▲
    by ahochhaus 12y ago

    Drop-In Chat had a few different XSS flaws. They should all be fixed now. Thanks for finding them and pointing them out! Sorry for the slow security fix, I was traveling after leaving YC Hacks. Please do let me know if you find anything els
14. 44.▲
    by ahochhaus 12y ago

    Thanks for the feedback. Please keep it coming if you think of anything else. We will be prioritizing what to work on.
15. 45.▲
    by ahochhaus 12y ago

    If you are willing to build on go, we open sourced the "wc" (WebChannel) library which handles all of the messages for dropinchat. http://gopkg.in/samegoal/wc.v0 Also, out of curiosity, if dropinchat provided
16. 46.▲
    by ahochhaus 12y ago

    I looked at chatango and I think the intended use case is a bit different than dropinchat. Drop-in chat provides user-to-user instant messaging. As best I can tell, chatango (primarily?) provides broadcast style communication. Is this corre
17. 47.▲
    by ahochhaus 12y ago

    Hi, I just checked out interlude. Cool project. I think the intent of our app is slightly different than yours. Our hope was to allow users of authenticated web applications to chat with one another. Our demo is misleading in this regard as
18. 48.▲
    by ahochhaus 12y ago

    For the time being we are going to keep this completely free to gauge interest. At some point we would likely charge, but at this point don't have solid plans about what the pricing would look like. Sorry I can't be more precise.
19. 49.▲
    by ahochhaus 12y ago

    Makes sense, thanks for the clarification.
20. 50.▲
    by ahochhaus 12y ago

    The back end is golang. The client server messaging protocol is BrowserChannel/WebChannel. https://code.google.com/p/libevent-browserchannel-server/wik... We open sourced the BrowserChannel library here: htt
21. 51.▲
    by ahochhaus 12y ago

    Thanks Walkman. That is a good idea. We had thought of group chats and chat rooms but a public "broadcast to all" option is interesting too. Kind of like a default room that everyone is in. Is that what you are saying?
22. 52.▲
    by ahochhaus 12y ago

    Thanks! We will add CSS styling to the configuration options in the DIC variable. Let us know if you think of anything else.
23. 53.▲
    by ahochhaus 12y ago

    One of the app authors here. We did this for YC hacks and ran out of time (30 hours). At this point we don't store the chats for anything but we plan on adding that soon. At that point, the admin should be able to search. Please let us
24. 54.▲
    Show HN: Drop-In Chat – Chatify your app(dropinchat.com)

    49 points by ahochhaus 12y ago|45 comments
25. 55.▲
    by ahochhaus 15y ago

    Milwaukee, WI (H1B) http://careers.joelonsoftware.com/jobs#/11923/software-engin... SameGoal is hiring talented software engineers who are experts in distributed systems, C++ and building world-class user-friendly products. Our platform b