Elasticsearch VS Coral

You could check out their GitHub and see what is going on https://github.com/elastic/elasticsearch/issues

Link to GitHub -->

I believe the 1024 limit has been upped in recent versions of Elasticsearch

https://github.com/elastic/elasticsearch/issues/92458

Elasticsearch is written in Java and its source code is available on Github.

I don't think the murmur3 hash implementation has changed since it was added as the default in version 2.0 (see the [changes](https://github.com/elastic/elasticsearch/commits/main/server/src/main/java/org/elasticsearch/cluster/routing/Murmur3HashFunction.java)). The plugin itself has seen [more changes](https://github.com/elastic/elasticsearch/commits/main/plugins/mapper-murmur3) but that's IMO because of internals and not visible changes in the calculations.

Mysql is not as open source as postgres (long story). And you can see how open elasticsearch is by just having access to the bugs database https://github.com/elastic/elasticsearch/issue

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.