BISQ was one of the motivations for a new(er) laptop. Of course, it was still slow as anything, and you have to keep the bloated client online just to provide liquidity, so it didn't work out. And that laptop doesn't even work anymore, and I have no idea what role BISQ may have played in that.
I wonder if what you build could be structured like an API. If you made it simple enough for almost anyone to start developing on top of, where what you coded was the protocol barebones. I imagine there are so many cool utilities that people could build on top of the basics. It's like a framework.
Here are all kinds of cool project ideas:
- Some sort of automatic liquidity pool that creates buy/sell orders to keep a certain ratio of two different coins.
- A stop loss function that sells automatically if the price falls.
- A super lightweight client that just keeps one order active and alerts when it fills.
- A mobile phone application.
- Integration with other APIs to fulfill orders automatically.
If you built the bare bones building blocks, then it could open BISQ up so widely, and so many cool tools could be built for people everywhere. A lot of technical bitcoiners would build their own tools.