- Blurtd RPC node
- ipfs
- ipfs-cluster
- condenser
- imgproxy
- libvips
it's a docker container the builds alert from source, builds condenser from source, and provides every single service that blurt does, top to bottom.
All services are exposed on standard ports, and the entire set up can be load balanced. This ensures that users who choose to set up their own local flavored front and will be able to scale that front end indefinitely.
Can we make a Blurt Engine, etc.?
I'd prefer to do that via the original authors, instead of forking.
100% it's a very solid product and approach.
Are these the same components to develop DApps on top of Blurt?
Or something similar to Steem/Hive-Engine's Tribes?
Blurt in a can could be used to develop dapps but is currently aimed at allowing anyone to easily set up a blurt front end.
Got it. Thanks a lot for bringing these tools to the community.
Blurt-On!
Condenser can be substituted with a desktop app (can be a fork of Ecency), which connects to the blurtd endpoint
https://github.com/ecency/ecency-mobile
....you
You are 100% correct. I was not aware of this product. Thank you!
Interesting