anshum4n

I am not sure if you got to try adding an action item. You can just type "@ams6110 Need to do something" and meetnotes records it as an action item which would then be tracked and followed up, the key being follow-up and status tracking.

The idea there is that while taking notes I don't want to look at the screen and click a button to add an action item, set its assignee and due date etc. I would rather participate more in the meeting and just keep typing (touch typist should get me), with the tool being smart enough to parse it as an action item. Its not as smart as it should be, but thats where we want to be.

Another small but neat feature is interactive widgets. I am not sure if you saw the how you can run an instant rating with all the participating. Its just one widget right now, but we are planning to add many more like poll, survey, mini-workflows, scrum templates etc.

Let me know if that did / didn't make sense. Happy to hear feedback!

PS: Before this, I myself was a heavy user for Google Docs for taking notes.

@wwalser You got us! I am surprised as well that we got to HN front page and the amazing discussion that ensued. While that blog took couple weeks to put together, I believe its testimony more to how everyone hates meetings and how they are run, rather than our ingenuity in writing the blog.

We believe meetings are world wide epidemic. There are lot many tools trying to make them just a tad bit better. The real ingenuity on our part would be if meetnotes.co ends up solving the pain in a major way! I believe we are on the cusp of change and it can just about be done with some AI, a bit of NLP and some great UX thrown in!

Would love to get feedback and hear opinion.

Agree. But much easier to know we should follow-up than to actually do it Especially for the more technical minded people (me included). Wish there was an AI that can automate it!

For me though, number of meetings you get pulled into without Agenda or need is the number one time killer!

Exact same thing that we are using for a realtime collaborative app. Generate token on server-side with access to certain keys.

However, we had to redo our json structure once we started thinking authorisation. It sucked and in retrospect should have thought about it earlier, but it seems to work.

Typically authorisation layers on top of existing data, but in this case, we had to redo data structure keeping auth in mind. Is that why you feel its brittle?

Would be great if you can put in some examples where we can optimise parametric queries using this. One common instance is IN queries where if the number of params for IN clause is small, it might make sense to blow it up into multiple equals clauses, allowing better use of indexes. MySQL query optimiser is horrible with IN clauses and causes table-scans. I have seen table scans and skipping other indexes even when IN clause has zero cardinality (in which case its better to just remove it altogether).

Couldn't immediately think of other cases, but that one example sounds useful for this.