jabo

29 ms·

121.
by jabo 5y ago
Hey Meili team, I work on Typesense and I’m the one who put that comparison matrix together. My intention was to provide as much factual information as possible based on my reading of each search engine’s documentation. This is one reason I
122.
by jabo 5y ago
Data Processing Agreement: https://gdpr.eu/data-processing-agreement/
123.
by jabo 5y ago
We have search relevancy tests baked into the automated test suite that runs on every commit. We keep adding to it as we get feedback about edge cases and new cases. We don’t have comparative relevancy benchmarks. But we fo have performance
124.
by jabo 5y ago
Just a question of priority, based on number of asks for it. We do plan to support it. In the meantime, we introduced a way to turn off typo tolerance and prefix-search on a per-field basis. This has helped some users search for fields cont
125.
by jabo 5y ago
> The issue with Algolia is that they have insane technology but it is mostly used only to search documentation. This is a really interesting side-effect of what Algolia was probably trying to do: use documentation search to spread brand
126.
by jabo 5y ago
Correct, the OS’ OOM reaper will kick-in to try and protect core OS operations. So you don’t want to let it get to that stage - you’d typically want to keep at least 15% free memory for the OS to do its thing. Commercially available RAM tod
127.
by jabo 5y ago
Yes it does - all languages except logographic ones (Chinese, Japanese and Korean) which we are actively working on: https://github.com/typesense/typesense/issues/228
128.
by jabo 5y ago
I haven’t tried to do this myself so I can’t speak to it. But one thing I would add is ElasticSearch is quite versatile and flexible, so I wouldn’t be surprised if you can contort it to get it to work for a wide variety of use cases. This i
129.
by jabo 5y ago
Oh yes. Speed is an important point. ElasticSearch & Solr use disk-first indexing (with RAM as just a cache), whereas Algolia and Typesense use a RAM-first approach where the entire index is stored in memory. This is what makes Algolia&
130.
by jabo 5y ago
What did the migration effort look like when moving from Algolia to ElasticSearch? Also, were you able to replicate the same user experience?
131.
by jabo 5y ago
No, ElasticSearch for example uses a disk-first approach.
132.
by jabo 5y ago
I work on an open source alternative to Algolia called Typesense. Algolia is a great product but can get quite expensive at even moderate scale. If I had a dollar for every time I’ve heard this from Algolia users switching over… I recently
133.
AMA with Typesense Co-Founders(aviyel.com)
4 points by jabo 5y ago|0 comments
134.
Elasticsearch clients now verify if the server is official Elastic distro(github.com)
2 points by jabo 5y ago|0 comments
135.
Universal income for open source maintainers(futureu.europa.eu)
5 points by jabo 5y ago|1 comments
136.
by jabo 5y ago
Love the level of detail that Fly's articles usually go into. We have a distributed CDN-like feature in the hosted version of our open source search engine [1] - we call it our "Search Delivery Network". It works on the same
137.
How Google Cloud plans to kill its 'Killed By Google' reputation(protocol.com)
1 points by jabo 5y ago|0 comments
138.
by jabo 5y ago
Context: I'm the other co-founder of Typesense, mentioned in the article you linked. Kishore and I have worked together on about 12 different side projects over the course of 13 years, and we've tried to adopt this mindset of cons
139.
by jabo 5y ago
There’s an eslint plugin to run only on staged changes: https://news.ycombinator.com/item?id=27643526
140.
by jabo 5y ago
Found an ESLint plugin that will only run on staged changes: https://www.npmjs.com/package/eslint-plugin-diff
141.
by jabo 5y ago
You could have the linter only run on changed files in a precommit hook, instead of on all files.
142.
by jabo 5y ago
Don’t law firms avoid taking on competing companies as clients to avoid any form of conflict of interest?
143.
by jabo 5y ago
That’s great to hear :)
144.
by jabo 5y ago
You’d just need to add for eg a user_id field to all your records and the extension will sync that to Typesense. You can then generate a scoped api key with embedded filters to only fetch results for a particular user_id
145.
Amazon Hair Salon(blog.aboutamazon.co.uk)
1 points by jabo 5y ago|1 comments
146.
Show HN: Firebase Extension for full-text search(github.com)
3 points by jabo 5y ago|4 comments
147.
by jabo 5y ago
I believe Carta already does this: https://cartax.com/
148.
AWS Frankfurt incident(status.aws.amazon.com)
145 points by jabo 5y ago|134 comments
149.
by jabo 5y ago
This is a pretty good book on the topic: https://www.refactoringui.com/
150.
Ask HN: What is your experience using Slack to run your public communities?
1 points by jabo 5y ago|0 comments

More ›