pacavaca's comments

Components used:

    Tensorflow and Simple Tensorflow Serving

    Pre-trained Universal Sentence Encoder

    Docker

    Python 3

    FAISS by Facebook

    ElasticSearch

    gRPC

Like the Toolkit!

Thank you, airocker!

Hello, HN!

Today I'm sharing a case and solution that we've gradually discovered and developed while running the original OneBar idea by our beta-customers. I posted a link to a blog post, because it better describes what we've built, but the whole thing is live and functional, so please feel free to signup and play with it!

Here's a brief summary:

Problem: A lot of internal teams have to deal with a flow of ad-hoc work-requests coming from Slack. In order to organize and track work they need to somehow turn Slack conversations into tickets. Slack offers "slack actions" to solve this problem, but they don't work well with arbitrarily structured conversations (e.g. multiple messages, threads, etc).

Solution We propose a completely new interface separate from Slack, where you can conveniently Select relevant messages from any discussion, turn them into tickets and then track in OneBar. Right now our workflow is mainly UI based, but we provide some AI assistance and plan to build up more of it in the future.

We spent quite some time building this thing, and I'd really love to hear your feedback, good or bad. Thank you! peace

Hello, HN!

We've been working on OneBar since spring, and ran it for about three months in a few companies. We're now ready to show it to the broader world! (it's still in beta though ;) )

A few things OneBar can do for your team:

- Store Q&As (just like Quora or StackOverflow)

- Search the KB right from Slack (via a bot)

- Source questions from Slack, and assign them to team members

- Save Slack threads as Q&A

- Automatically cross-link content

Here's one particular thing that worked well during the test: https://blog.onebar.io/crowdsource-your-companys-glossary-in...

We would highly appreciate HNs feedback on OneBar. Thanks in advance for checking it out!

Interesting. We already use something in our company that gives us "go/" links, but I'm not quite sure what it's powered by :)

Let's see what they do for the real YC W19 :D

Ubuntu 18.04 symlinks /usr/bin/vim to nvim when you install Neovim, so it kind of calls them the same. But ok, I agree that technically they are 100% different

But isn't Neovim a legitimate Vim?

But why should it matter for customers who does the job? I mean, if you don't tell anybody, and pretend it's 100% AI then it's bad, but if it "will eventually become AI", and your investors and everybody interested in the technical details know how it's actually done, then what's wrong? A true "AI" should be able to pass a Turing test, so for the customer, it should be indistinguishable, and shouldn't matter.

Of course, the privacy concerns are there, but then again, if it's a real "AI", then it may be worse for the computer to read your data than for a random low paid worker ;)

Just found this provocative post on HN (the other HN). The interesting part is that it comes from a Java programmer. When I was writing Java and using big IDEs myself, I was too advocating for longer lines. And now? Now I'm all Vim for 3 years, and 80 char limitation never made more sense than now! Being able to split your screen whichever way you want and still read the code is precious.

Right. That's pretty much why I'm asking. From the engineering standpoint it just doesn't make sense to have all these organization, they're just adding a huge overhead to the system. However, I agree that it is how it is for a reason, just trying to understand the driving forces that form the current taxation system.

This looks like a provocative question, but ok. We're working on a Q&A knowledge base deeply integrated with slack: https://www.producthunt.com/upcoming/all-new-onebar

Where does it store the data? Can I connect it to my existing DB or will I have to create an etl pipeline first?

And yes, 'your' is important in this case. I definitely didn't want it to sound like another Docker-blaming article.

Hmm. I didn't notice that 'your' is not in the HN title. So, is it a filtering or I just forgot to type it?

Hmm. I'm definitely not an expert in hypervisor implementations but I would guess that it should not proxy any calls to the host kernel...

The point was not to complain about how bad the Docker is but rather to highlight that a lot of unexpected things may come from the fact that the kernel is shared. "Logging too much" was just a reason for the posix_fadvise being called too often but this becomes a problem ONLY when the kernel is shared. In case of virtualization, everyone gets its own version of fadvise (the kernel) and the conflict doesn't happen.

Right. And the sad part is that they can afford their support being this terrible - they simply don't care about a few hundred customers fleeing them. But on the user end - I and my wife were so frustrated by their support today so that you can see, I've even started this topic :D

P.S. the support question was not even about using their product but about buying

Not really. My point was that there's a lot of space between MS Paint and Photoshop (iMovie and Premiere), etc, and there seem to be enough people, willing to pay half price for the half of features. I'm not saying I want it for free, all I'm saying is that $500/year (creative suite price) is way too much for occasional picture/video editing.