Comment by roadbeats | Hacker News Reader

Comment by roadbeats | Hacker News Reader

Thanks everyone upvoted! It may look like a simple website but I spent a lot of time on this project :) Besides of programming, I shot that little video [1] in homepage, it was my first time to do voice-over :)

I created a invite code for HN, so you can sign up without wait; https://getkozmos.com/signup?code=HNEWS

Here is some brief info for HN users. It's built on Go, Elastic Search and (Pr)eact. The extensions use IndexedDB [2] to create a database [3] that users read/write, and that database gets synced with Kozmos servers. This makes Kozmos' like button work consistently, even when Kozmos is down or user has bad / no connection.

How will Kozmos monetize ? Kozmos will always be free for bookmarking privately. In the next version, I'll introduce public collections which users can use for creating nicely organized bookmark collections, and this feature will be available for only paid users.

For more details, I wrote a blog post; https://medium.com/@azerbike/introducing-kozmos-a-new-bookma...

Thank you,

Azer

1. https://www.youtube.com/watch?v=fs_OOQaJRfQ

2. https://github.com/azer/indexeddb

3. https://github.com/kozmos/likedb

Noticed a typo in the onboarding flow: http://i.imgur.com/qbXQHrR.png

Should probably be something like "Kozmos will add the <3 button to your browser..." or at least "Kozmos will add to your browser the <3 button..." (which sounds awkward but is grammatically correct)

How are you doing the classification with ElasticSearch? Are you hardcoding keywords for different preset categories, such as blogs/music, or are you doing some kind of machine learning to figure out what each person's relevant categories are?

I extract keywords from the meta tags and open graph contents.

Any chance you might add the ability for manual tags? It's a must have for me.

Hi Azer. Something in the page is causing keys to be missed on all text inputs in the page (sign up, login). It is really annoying since it prevents me from typing at normal speed, probably a rough keyup event handler doing some validation?

Some users reported that but I can't reproduce it. Here is the code of the input component; https://gist.github.com/azer/87e6919fc24ad08839e01b1ee3158b4...

It depends on where your prop is coming from - at a guess I assume you're passing the value up the chain to some ancestor who is doing a setState. This'll cause the entire tree to re-render, including this component, and will cause a lockup if you're editing while this happens.

You can probably resolve this by implementing a shouldComponentUpdate here, or just debounce change handler.

You need to debounce

Looks cool! What client-side encryption methods are you using to keep data private before it goes to the servers? Also, how are you generating the encryption keys?

Reply on news.ycombinator.com