HiveSQL is more than a simple synchronizer.
It's made of multiple micro-services running simultaneously. It also relies on paid third-party services (ex: language analysis, performance optimizer).
Hard to "opensource" such an infrastructure.
Opensource is always a choice. Setup could be opensourced, documenting process to setup similar environment could be opensourced, paid 3rd party tools could be disclosed (names, why, how they are used, etc.) Micro-services could be explained, etc.
Yes, but all of the processes you describe here are very time consuming and useless if they are not regularly updated.
I didn't say it can't be done. I said it's "hard" to do.
You might be right, as I don't know your setup. Directly asking for 2+ years without first having things documented in case you shutdown or something happens to you, is quite risky to entire community. But if there is already documentation that proofs that anyone could start their own instances, doesn't mean they should do it (given the cost of infrastructure is high as you wrote). It would give a lot more confidence, imho.
I made the proposal a long term one to avoid having to campaign for its funding every N months.
This does not represent a risk to the community because the proposal is not funded in its entirety at one time.
Small payments are made on a regular basis and can be interrupted at any time if the work or services provided no longer meets the expectations of the community.
And what if you just open source the code not the infrastructure so any one could set a hivesql server tracking certain tag or certain community? Opensource is a great choice because anyone could contribute to the code and audit it.
HiveSQL is more than a simple synchronizer.
It's made of multiple micro-services running simultaneously. It also relies on paid third-party services (ex: language analysis, performance optimizer).
Hard to "opensource" such an infrastructure.
Opensource is always a choice. Setup could be opensourced, documenting process to setup similar environment could be opensourced, paid 3rd party tools could be disclosed (names, why, how they are used, etc.) Micro-services could be explained, etc.
Yes, but all of the processes you describe here are very time consuming and useless if they are not regularly updated.
I didn't say it can't be done. I said it's "hard" to do.
You might be right, as I don't know your setup. Directly asking for 2+ years without first having things documented in case you shutdown or something happens to you, is quite risky to entire community. But if there is already documentation that proofs that anyone could start their own instances, doesn't mean they should do it (given the cost of infrastructure is high as you wrote). It would give a lot more confidence, imho.
I made the proposal a long term one to avoid having to campaign for its funding every N months.
This does not represent a risk to the community because the proposal is not funded in its entirety at one time.
Small payments are made on a regular basis and can be interrupted at any time if the work or services provided no longer meets the expectations of the community.
And what if you just open source the code not the infrastructure so any one could set a hivesql server tracking certain tag or certain community? Opensource is a great choice because anyone could contribute to the code and audit it.
What are the cons on opensource hivesql?
Your post has been voted as a part of Encouragement program. Keep up the good work!
Dear reader, follow and support this author, Install Android: https://android.ecency.com, iOS: https://ios.ecency.com mobile app or desktop app for Windows, Mac, Linux: https://desktop.ecency.com
Learn more: https://ecency.com
Join our discord: https://discord.me/ecency