frugalfirbolg

Hmm, judging from the source code the default listenAddress is on '0.0.0.0:3100' so it's listening on every interface, but it's instantiated to use TLS and in server.go HandleServerRequest does SSH authentication.

This service is separate from whatever the developer is working on that needs to call to it. If the work in progress exposes temporary credentials it's not the end of the world.

Do you have any concerns about doing the research and confirming the market exists for this product and then getting 'Sherlocked'? Did you spend any time evaluating other platforms such as Android? I understand from my own experience how challenging that platform can be, just curious to see if you looked into it as an alternative or hedge.

Just the fact that they didn't have a way to record and verify whether the deployment was done properly boggles my mind. When I worked at a bank we had package management to do deployments, a separate tool for taking inventory of installed software (in case of users managing to sneak third party programs on to their system), and on top of that a web framework for tracking milestones during projects that allowed for manual entry by technicians and automated input from scripts so tasks that had to be done by hand like replacing hardware could be coordinated with build scripts and management could monitor the whole thing from a dashboard.

Sadly their marketing pitch does not convey an understanding of human interactions. The example you pointed out is reminiscent of a bad Turing test chat bot with a lexicon of topics to crawl through.

Still, the ability to dynamically generate a topical chat bot from a corpus of digital artifacts is interesting. I'm currently envisioning their work as a natural language parser front end with subject specific response decoration and a machine learning algorithm to trigger "self-initiated" conversation and topic selection.

No doubt it will be used for marketing spam. I can just imagine my digital ghost telling anecdotes about how in my day and age Intel was a respectable company and that most of my computers used their CPUs, so my ancestor should consider them for their computing needs... <sigh> reminds me of a Futurama episode.

I'd still like to see why they think they can do better than what's already out there. Especially if they're making a play for academic funding, they need to publish something.

Note: this comment is without the benefit of searching for each of the team members prior works; if the company is not pointing to any particular technique or publication I'm not enthused enough to dig deeper.

I'd love to see some publications from their R&D to outline how this won't turn into another one of those chat bot apps that you can have write Facebook posts in your style based on frequency analysis of your past posts.

This could open up some nice possibilities for browser based and Node.js driven distributed computing.

Thanks, I was just looking for something like this!

Not sure, but I thought when I looked at the charts that the spikes to higher latency and exception rates looked like unicorn horns poking over the horizon.

I've reached a very similar conclusion and for smaller pages that don't need frequent updates I usually go with static HTML if possible, pre-rendering the static HTML from templates during the build phase if there are many pages with similar layouts. If the site really is meant to grow (lots of posts, many items in inventory, etc) then a framework like Wordpress still makes sense, but for a company landing page or a vanity site I don't see the need.

The idea of a barebones programming sandbox attracted me to this, but then reading through the rest of the site I felt like it was an attempt at sublime evangelism using Biblical passages as allegory for programming philosophy that then rambles on into a testimonial blog post.

I like resources such as the source code by address page, and the lack of complicated structures that get in the way of kernel programming, and I think it would still be fun to dig through the I/O and process management code when I have time to translate the naming paradigm so I can follow it.

Yeah, in theory they would check the heights in the atlas versus the effective height of a given load, not just the height on paper. Why the truck was overloaded also begs a look at company policies. If this particular site is experiencing this issue 2 or 3 times a month then I wonder if the cost of guessing wrong and congesting the tunnel isn't high enough compared to just sending two trucks.

I'm also surprised that the drivers or their company failed to check a truck atlas when planning the route. I imagine the company has just as much incentive to prevent incidents.