Joep Meindertsma

I'd like to make start on running some external code by creating a mock plugin, compiling it to wasm, registering it to an Atomic-Server and running the plugin. I'd like...

The minimal example worked fine, but now I'd really like to do things with the Store (e.g. get some data, calculate some numbers, return a new resource with these numbers),...

I'm currently working on implementing Search, which I wanted to do as a `plugin` from the start. However, my existing plugin abstraction was surely not powerful enough. For search, I...

I should also consider using [`wasmedge`](https://github.com/second-state/wasmedge-quickjs/), which also features a JS runtime. This is interesting, as JS is such a familiar language for many devs, probably more so than any...

[WasmEdge now supports the `fetch` API](https://github.com/second-state/wasmedge-quickjs/blob/2ec148ee1ac89539cbc57331b637d21774898a57/example_js/wasi_http_fetch.js#L1), which should make things easier. Definitely should try this. Read https://www.secondstate.io/articles/embed-javascript-in-rust/

comment moved to OP

I've been playing with `fp-bindgen` for a couple of hours now, and I think this feels like the most realistic approach for me so far. It works, I can move...

Another solution to all these tauri build requirements is to _not build tauri stuff_ in the CI. Remove it from the workspace, or [exclude it from tests](https://stackoverflow.com/questions/66755529/run-cargo-test-workspace-and-exclude-one-test)

I think I found the issue - invite.rs did a `store.get(public_key)` instead of `store.get(subject)`

I've just pushed a new version to production that should fix this.