FactGraph VS go-plugin

I used to have a project like this. I was going to call it FactGraph: https://github.com/FactGraph/FactGraph/wiki

My idea was to build up a big community-maintained database containing facts and evidence, where everything is linked into a huge network. Everything would have a weight (sometimes automatically calculated from parent nodes), and the software would calculate probabilities for some big questions. Every user could also build their own personalized graph to explore their own worldview, and maybe even uncover some cognitive dissonance that they weren't aware of. Or you could use it to compare and contrast different philosophies, religions. Could even calculate a "coherence score" for each religion and denomination after crunching all of the available evidence.

Then I discovered RootClaim: https://www.rootclaim.com

They're doing something very similar, with a more targeted approach where they focus on some specific questions. e.g. COVID-19: https://www.rootclaim.com/analysis/what-is-the-source-of-cov...

RootClaim really seems to be nailing it so far, and hopefully they can continue to grow and become something like the project I was imagining.

I am looking forward to a mix of both - I am hoping to add a concept called "operator" which would be a go-plugin [1], just like terraform providers, but build backends. So, someone would be able to, say, write a Slack plugin (in Go, or anything over RPC) which sends a message once a build is complete - like Jenkins/GitHub actions, or just scripts that we can reuse like GitLab CI through `modules`.

Perhaps a new registry where we can push custom modules and providers (operators in this case), I'm curious to know about if we have any existing implementations we could reuse for the registry.

[1]: https://github.com/hashicorp/go-plugin

I'd recommend looking into a different approach for plugins such as hashicorp/go-plugin (which uses multiple process PIDs and RPC communication between them) or traefik/yaegi (which implements a Go-compatible scripting language that can be interpreted at runtime and which still supports most Go modules).

You'll never fully protect your code from someone who's dead-set on reverse-engineering it, however, you can use https://github.com/hashicorp/go-plugin or a similar RPC technique, which will let you ship binary plugins and will also be less fragile and janky compared to something made with `-buildmode=plugin`.

The plugin system that hashicorp uses for all their projects works very well. It's essentially a local RPC implementation. https://github.com/hashicorp/go-plugin

can you try older go-plugin versions? The only major change in v1.4.4 was a bugfix for automtls. https://github.com/hashicorp/go-plugin/blob/master/CHANGELOG.md