cozo VS Coral

I can figure parts of it out from https://github.com/cozodb/cozo/blob/main/cozo-core/tests/air_routes.rs which is enough to get started

I've been keeping an eye on https://github.com/cozodb/cozo which is pretty close to something I've wanted, a sqlite version of datalog/datomic.

Finally, the one product I was extremely impressed with and felt was genuinely impressive as a database in general was cozodb.

Take a look at cozodb. It meets most of your goals and I've been really enjoying using it. It might give you some inspiration or something to contribute to.

Sure. They're called 'partials' sometimes. Useful if you want to rerender just part of a page. This is a pattern used by HTMX, a 'js framework' that accepts fragments of html in an http response and injects it into the page. This is good because it avoids the flash and state loss of a whole page reload. See the HTMX essay on template fragments for a more complete argument [0].

This is a go template for an interactive todos app [1] that I'm experimenting with. The html content of the entire page is present in one template definition which is split into 6 inline {{block}} definitions / "fragments". The page supports 5 interactions indicated by {{define}} definitions, each of which reuse various block fragments relevant to that interaction. I'm in the process of converting it to use embedded cozodb [2] queries which act as a server side data store. The idea here is that the entire 'app', including all html fragments, styles, http requests and responses, db schema, and queries are embedded into this single 100-line file.

[0]: https://htmx.org/essays/template-fragments/

[1]: https://github.com/infogulch/go-htmx/blob/master/templates/t...

[2]: https://github.com/cozodb/cozo

If anyone wants to try a FOSS vector-relational-graph hybrid database for more complicated workloads than simple vector search, here it is: https://github.com/cozodb/cozo/

About the integrated vector search: https://docs.cozodb.org/en/latest/releases/v0.6.html

It also does duplicate detection (Minhash-LSH) and full-text search within the query language itself: https://docs.cozodb.org/en/latest/releases/v0.7.html

HN discussion a few days ago: https://news.ycombinator.com/item?id=35641164

Disclaimer: I wrote it.

You are probably talking about this cozo.

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.