Readit News logoReadit News
jabo commented on My startup banking story (2023)   mitchellh.com/writing/my-... · Posted by u/dvrp
laksmanv · 5 months ago
What banks are recommended for startups if not chase?
jabo · 5 months ago
Mercury
jabo commented on The Effect of Noise on Sleep   empirical.health/blog/eff... · Posted by u/brandonb
jabo · 7 months ago
Wonder if white noise counts as noise from this perspective. Or if it’s mainly unexpected noises that make sleep quality worse.
jabo commented on <Blink> and <Marquee> (2020)   danq.me/2020/11/11/blink-... · Posted by u/ghssds
jabo · 8 months ago
The day I discovered that marquee tags have a direction attribute, using which you can make the text go up/down left/right and use multiple of these tags, is still etched in my memory.
jabo commented on Meilisearch – search engine API bringing AI-powered hybrid search   github.com/meilisearch/me... · Posted by u/modinfo
irevoire · 10 months ago
I hate the way typesense are doing their « hybrid search ». It’s called fusion search and the idea is that you have no idea of how well the semantic and full text search are being doing, so you’re going to randomly mix them together without looking at all at the results both searches are returning.

I tried to explain them in an issue that in this state it was pretty much useless because you would always have one or the other search strategy that would give you awful results, but they basically said « some other engine are doing that as well so we won’t try to improve it » + a ton a justification instead of just admitting that this strategy is bad.

jabo · 10 months ago
We generally tend to engage in in-depth conversations with our users.

But in this case, when you opened the GitHub issue, we noticed that you’re part of the Meilisearch team, so we didn’t want to spend too much time explaining something in-depth to someone who was just doing competitive research, when we could have instead spent that time helping other Typesense users. Which is why the response to you might have seemed brief.

For what it’s worth, the approach used in Typesense is called Reciprocal Rank Fusion (RRF) and it’s a well researched topic that has a bunch of academic papers published on it. So it’s best to read those papers to understand the tradeoffs involved.

jabo commented on MusicBrainz: An open music encyclopedia   musicbrainz.org/... · Posted by u/mmh0000
jabo · a year ago
If anyone's interested, a while ago I downloaded the MusicBrainz database and built a search-as-you-type experience here with about 32M songs:

https://songs-search.typesense.org

The dataset has been very helpful to benchmark Typesense across releases. So I'm grateful that it exists!

jabo commented on Show HN: I scraped 25M Shopify products to build a search engine   searchagora.com/... · Posted by u/pencildiver
dangoodmanUT · 2 years ago
Yo fuck mongo just use RDS or some digitalocean DB. Or really just use opensearch/elasticsearch, or even typesense (don't bother with raft it's so broken) or meilisearch
jabo · 2 years ago
We’ve interacted before on Twitter and GitHub, and I want to address your point about Raft in Typesense since you mention it explicitly:

I can confidently say that Raft in Typesense is NOT broken.

We run thousands of clusters on Typesense Cloud serving close to 2 Billion searches per month, reliably.

We have airlines using us, a few national retailers with 100s of physical stores in their POS systems, logistic companies for scheduling, food delivery apps, large entertainment sites, etc - collectively these are use cases where a downtime of even an hour could cause millions of dollars in loss. And we power these reliably on Typesense Cloud, using Raft.

For an n-node cluster, the Raft protocol only guarantees auto-recovery for a failure of up to (n-1)/2 nodes. Beyond that, manual intervention is needed. This is by design to prevent a split brain situation. This not a Typesense thing, but a Raft protocol thing.

u/jabo

KarmaCake day3778November 20, 2010
About
mail At jbos d0T co
View Original