A rolling fork of Lemmy that brings PubSub to retail inventories. https://github.com/Lemventory
Using Nostr for this project instead
I was recently made aware of NOSTR. Thinking through the implementation of this project, it makes a LOT more sense to use the tech behind NOSTR for this rather than pub-sub.
Here's a rundown of NOSTR market, which seems to satisfy many of the needs we have for inventory much better than pub-sub..
Requirements Is this a feature request? For questions or discussions use https://lemmy.ml/c/lemmy_support Did you check to see if this issue already exists? Is this only a feature request? Do not p...
Before I actualy write a single line of Rust or Typescript code in my fork of Lemmy, I aim to Nixify their build instructions and dev environment to make onboarding of new contributors (while also improving reproducibility).
So far, it has been tough since the Lemmy devs heavily utlize Docker and Ansible to achieve a similar level of reproducibility. It has been a challenge to incorporate their build instructions into a nix flake because their codebase utilizes submodules that depend on eachother. If you have any pointers, please reply here or on github. I don't mean to be such a Nix fanboi but I swear by it for my projects and I'd love to bring that power to Lemmy's dev team.