HN user

pacavaca

197 karma

Co-founder at OneBar.io

Posts58
Comments68
View on HN
flappynote.com 9mo ago

Show HN: Flappy Note – scale singing mini game

pacavaca
2pts1
pacavaca.medium.com 2y ago

Reframing GoPro Videos with OpenCV, YOLO and DeepSORT

pacavaca
2pts0
github.com 5y ago

An extensive list of open-source data visualization tools

pacavaca
3pts0
pacavaca.medium.com 5y ago

I switched to iPhone after using Android for 10 years

pacavaca
2pts0
pacavaca.medium.com 5y ago

Best programming teacher that never taught me a lesson

pacavaca
1pts0
blog.onebar.io 5y ago

Diving into team productivity with Dan Pupius of Range.co

pacavaca
3pts0
blog.onebar.io 5y ago

What Is the Role of a CIO with Yousuf Khan of Ridgevc

pacavaca
1pts0
news.ycombinator.com 5y ago

Are you preserving internal meeting recordings?

pacavaca
1pts0
blog.onebar.io 6y ago

Interview with VP of Customer Success at CloudBees

pacavaca
1pts0
news.ycombinator.com 6y ago

Ask HN: Where do you host internal tools?

pacavaca
2pts2
www.thetodobot.com 6y ago

Show HN: Shared to-do list for Slack and Chrome

pacavaca
1pts0
blog.onebar.io 6y ago

Lightweight project management in Slack or how we ditched Trello

pacavaca
2pts0
blog.onebar.io 6y ago

We built ToDoBot for Slack in 3 days

pacavaca
6pts0
www.thetodobot.com 6y ago

Show HN: Slack-Native TODOs Right in Your Home Tab

pacavaca
2pts3
blog.onebar.io 6y ago

Does it make sense to move all the work to chat?

pacavaca
2pts0
news.ycombinator.com 6y ago

Ask HN: What are some things you wish Slack could do?

pacavaca
2pts1
www.onebar.io 6y ago

Scan your Slack history and build an FAQ bot automatically

pacavaca
1pts1
medium.com 6y ago

Six months with Firefox, worth it?

pacavaca
2pts0
news.ycombinator.com 6y ago

Ask HN: Why code “post-reviews” isn't a thing?

pacavaca
5pts6
techcrunch.com 6y ago

ThoughtSpot hauls in $248M Series E on $1.95B valuation

pacavaca
1pts0
www.indiehackers.com 6y ago

PH Post-Launch Reflection

pacavaca
2pts0
news.ycombinator.com 6y ago

Ask HN: If we ever create the AI, would we be considered gods for it?

pacavaca
1pts2
blog.onebar.io 6y ago

Building a semantic search engine using open-source components

pacavaca
3pts1
blog.onebar.io 6y ago

It's like Pocket, but for your Slack threads

pacavaca
6pts0
blog.onebar.io 7y ago

Poor knowledge sharing is the second biggest challenge for SD teams

pacavaca
1pts0
www.thoughtspot.com 7y ago

ThoughtSpot on Tableau Acquisition

pacavaca
1pts0
news.ycombinator.com 7y ago

Ask HN: Which Slack integrations do you use?

pacavaca
1pts0
blog.onebar.io 7y ago

Show HN: A completely new approach to ticketing in Slack

pacavaca
4pts3
blog.onebar.io 7y ago

Go Beyond the Slackbot

pacavaca
1pts0
blog.onebar.io 7y ago

Show HN: New team wiki for Slack teams

pacavaca
2pts0

I'm trying to pick up some music skills, and part of that is doing ear training. Those who have ever tried it know that it starts with singing a bunch of stuff: just pitch matching, singing scales, singing chords, intervals, etc. Of course, the best way to do it is against a real instrument, but when you're especially bad at it like me, sometimes you want to practice with a tuner to make sure you're even hitting the correct pitches. Singing with a tuner is rather boring, so I made (yes, vibe-coded) a little browser game that is supposed to make it more fun. It's inspired by a TikTok mask with similar mechanics that went somewhat viral. Unfortunately (fortunately), I don't have TickTock, so I had to DIY it with a slightly different style.

Some gotchas: - It's very new, so, might be glitchy - Ideally, you want to sing with a drone, but it'll interfere with pitch-detection so, use headphones - It works on mobile (iphone), but I've seen some rendering issues. If encountered, try refreshing the page.

Otherwise, enjoy! I find the Random mode particularly fun.

I remember trying neovim with Atom a while ago. At that time I realized that me using nvim it's not just about motions/plugins/no mouse, etc, but rather the whole terminal experience. For example, I rely heavily on tmux for splitting my screen whichever way suits the current task best and then, I may spontaneously open nvim in some of the splits or run other CLI tools. This experience is not the same with the CLI built into vscode or any other IDE.

Funny enough, those emails caught my attention too and I was even trying to `curl -v` my way through the redirect chain before stumbling upon this thread.

Weirdly, in my case the links in the email were pointing at lnkd.in/<some payload>, which is a legit Linked in domain. However, with that payload it was 301-me to some garbage script on google storage and then some shady website. I'm curious how did they make lnkd.in respond with 301 to whatever they want and can't there be a vulnerability of some sort.

What do you do if you have a script or a server that you need to make accessible to others in your team? Do you run it from your machine, or ask devops to deploy it somewhere? Is there something better than these two options?

Hey, HN!

Slack has recently released its Home Tab (https://api.slack.com/surfaces/tabs). Basically, it's a dedicated page within the Slack app where your bot can build a pretty advanced UI (way beyond basic messages).

While implementing the Home Tab for our main product, I realized that - Hey! This could be a perfect place for all my TODOs to live. I'm part of Apple, Google and a bit of Linux ecosystems and there aren't too many apps that I use consistently across the board. Slack is one of them and I often just DM myself to store a quick note or TODO that I can later view somewhere else. Why can't there be a bot for that?

Said - Done! I and the team hacked together the ToDoBot in 3 days and published it in the Slack store for everyone to use for free. Please check it out and let me know what you think!

Hey, HN!

We've spent the last five months playing with BERT, Universal Sentence Encoder, FAISS, and other cool tools, and look at what we've built!

You can point this thing at any of your Slack channels (preferably one with many Q&As), and it will automatically build an FAQ bot out of it^

The bot will then stay in the channel and respond to trivial questions using previous conversations - kind of what helpdesk teams do half of the times but manually.

^ - automatically, but with some human curation

^^ - yes, it screams privacy concerns, but we only scan what you tell us to, and helpdesk channels usually only have boring stuff about laptops, licenses, and VPNs not working. Please don't add our bot to your top-secret channels.

So, what do you think?

It has to freaking stop crashing first. And stop freezing my computer with just 20 tabs open (for 32gb of ram). And complete their password manager. And implement recent standards to make apps work. And... Yeah, I'm still using it instead of Chrome just because I want to depend less on Google, but dammit Chrome is better.

Wow, thanks for the extended answer! I liked the part about "any code not written by me is a garbage", although I'm mostly trying to drop this attitude :D Jokes aside, I got your point, but it's still about catching errors upfront, during a more tedious code-review.

I've probably over-exaggerated a bit how "terrible" our merged code is but anyway, my point is that at the "review" phase the code is still "imaginary". We think that it'll work, but it hasn't been integrated with anything yet, it hasn't been battle-tested or, often, even used. Obviously, we find a lot of issues after the merge and filing tickets allows us only "not to forget to fix them". I feel like there should be a standard practice aimed at preventing those issues from RE-occurring.

Yeah, but the problems is that I (and I'm sure many other people) just can't pay enough attention to every detail DURING the code review. Yet after the review, when you start using the code, issues just reveal themselves without any extra effort. I'm just looking for ways to prevent them from reproducing I think.

Completely on a side note, but I've just recently realized how much of a noise-cancellation magic comes buil-in with Zoom. My wife was grinding coffee literally next to me, and no one on the call could hear it. Now I'm learning that the whole standalone startup exists dedicated to doing it for all the platforms. Cool!

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!

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 ;)