Coral VS lucene

The Coral Project [0] (commenting platform used on Washington Post, New York Times, The Verge) uses an Apache 2.0 license [1]. Which doesn't seem to have prevented it from raking in big SaaS customers.

A lot of people worry about copy-cat services, but it's kind of rare that someone will be able to compete with you as the original in hosting your own service as well as you can. Especially when you consider support and maintenance requirements of a new product you aren't personally developing.

I could see copy-cat services being more of an issue in the late stage of a product though? When everyone knows lots about how to stand it up and use it?

[0] https://coralproject.net/

The Coral Project was created inline with this initiative. They have lots of guides that provide some of the research that was conducted: https://coralproject.net/

For comment system, I choose Coral Project Talk because it could use Akismet and Google Perspective API for reducing spam and harassment. I also need to think about the remove comments when user delete their account (GDPR stuff). Coral Talk has the above functions in the UI.

Another great API that could be self-hosted is Coral. It’s a commenting platform where users can leave online comments. It’s received contributions from over 40 people on Github. It has a good-first-issue tag and also offers a contribution guide.

Yup! We do a Typescript/Node.js/GraphQL back-end with React/Relay/Typescript on the front end.

https://github.com/coralproject/talk

It's pretty nice having the whole code base share types, syntax, structure, etc.

Coral is poorly advertised outside it's ecosystem, but should be considered. https://github.com/coralproject/talk

See https://docs.coralproject.net/coral/v5/integrating/cms/ to get an idea of it's use.

Our highest tier comment system is quite powerful, and is based off Coral Talk by Vox. For beginners like yourself, if we allowed users to integrate Disqus on all tiers, would that alleviate your concerns with using Storipress?

If you need some inspiration, we added support for server caching of responses on Coral: https://github.com/coralproject/talk/blob/develop/src/core/server/app/middleware/graphql/apolloServer.ts#L85-L88

I've seen some examples in which people embed Discourse discussions.

There's also Coral (https://github.com/coralproject/talk) which used to be Mozilla + Vox project before Mozilla handed it over to Vox completely, but I have no experience with it.

First, a review of the landscape. As said in the introduction, there aren't a ton of good options. Apache Lucene is by far the best traditional search index from a speed, performance and functionality standpoint. It's the base for Elasticsearch/OpenSearch and many other projects. But it requires Java.

https://github.com/apache/lucene/issues/10047

2. The Panama Vector API allows CPU's that support it to accelerate vector operations: https://openjdk.org/jeps/438

So this allows fast ANN on Lucene for semantic search!

How did people do this before Lucene supported it? Only through entirely different tools?

Are they forking Lucene or somehow getting the Lucene devs to increase that limit? Because this PR has been open for over a year now: https://github.com/apache/lucene/issues/11507

Lucene's adaptation of Roaring uses the complement idea on a block-wise basis:

https://github.com/apache/lucene/blob/84cae4f27cfd3feb3bb42d...

Like someone said, it's in locations as specified in the path.data. Depending on sharing and replication, it could be on more than one host. Elastic uses Apache Lucene to store documents, since it's open source, that rabbit hole will welcome research :-)

It is pretty clear to me that Elastic is planning to build their ANN features differently than OpenDistro's k-NN implementation, or other plugins modules that extend Easticsearch in similar ways. They now will build on the Apache Lucene capabilities that were collaboratively built "upstream" by a number of individuals, some that work for Amazon and some that work for Elastic.

From the linked issue, it seemed that they were originally planning to develop this as a proprietary feature of Elasticsearch, without contributing the functionality to Apache Lucene, but then changed direction when the Apache Lucene developers (some of which are currently employed to do such work by Amazon) started to build its approximate nearest neighbor (ANN) vector search capabilities. [1]

It's great to see folks that work for Elastic collaborating and building on what is in Apache Lucene to extend the utility of ANN with Hierarchical Navigable Small World Graphs (HNSW) [2]! From this, I think it should be possible to implement an Open Source version of the functionality with a compatible API, if that is something that OpenSearch users seek.

[1] https://issues.apache.org/jira/browse/LUCENE-9004

[2] https://github.com/apache/lucene/pull/250