I have spent four long months building up the Hashgraph proposal. I have been active in their Telegram and Discord channels, tweeted and retweeted about it, posted on their official website, and have been working with the engineering and marketing team of the company to help grow the community.
We have had great feedback and will continue to get more as the project gets built out. We have seen some incredible questions will have answers to provide shortly after the proposal and commitment phase is over.
With just days to go in the proposal, the mods closed 8 of the questions that were asked and well-received. I understand that the role of the moderators is just this, and the timing is not (and should not be) a factor, but the closures are not warranted and are detracting from people's knowledge and understanding of the subject.
The closed questions were marked as duplicates, when, in reality, they are not. The reason for the closure is a simple misunderstanding by the moderators of the technology in the proposal. I do not expect moderators to understand every proposal, but I do expect them to attempt to understand by reaching out to proposal owners rather than taking away from the work of the people promoting the proposal.
How can we help the moderators better understand the technology being proposed rather than allowing them to ignorantly close it?
To cite a few of the questions that are subject to the closures:
Question: What programming languages can I use to create a smart contract?
"Duplicate": What languages, other than Java, will be supported by the API?
Justification as to why the closure is invalid: The smart contract language and the API languages are two different things. Someone may use Java, Go, or Python to interact with the API, which then interacts with the network. The Smart Contracts are are written in another language and get deployed to the network. Similar to in other distributed ledger technologies, smart contracts and API languages are different (for example, Ethereum smart contracts are written in Solidity and Vyper, while their API is available in Go, Python, Javascript, etc.).
Question: What is the best language to learn for beginning developers that want to work with Hashgraph?
Reason for Closure: "Not constructive"
Justification as to why the closure is invalid: This is an extremely valid question that I get asked on other channels than simply this proposal. There are preferred languages to learn when learning about this technology. For example, the only available language to interact with right now is Java, so this would be a good answer to the question. The person asking may also want to deal with Smart Contracts, so he may want to learn Solidity. There are a number of languages that cover different ground in this technology, so this question is extremely constructive.
Question: When will Hashgraph support other programming languages besides Java?
"Duplicate": What languages, other than Java, will be supported by the API?
Justification as to why the closure is invalid: These are two very distinct questions that are both valid. One is referring to the languages that will be supported by the API. The other refers to the timing the release. For example, this asks about the timing of a difficulty bomb, while this questions describes what it is.
Question: How a node can joining HH platform?
"Duplicate": What are the requirements to run a node?
Justification as to why the closure is invalid: One is asking about the process of joining the platform (what website to go to, how to sign up, what scripts to run, etc.)? The other is asking about the requirements (what hardware requirements, what software requirements, what corporate formation, etc.).
Question: Perhaps HH SC .sol code/pattern standards be denoted as HRC / HIP . Hedera Improvement Proposal
Reason for Closure: "Not a real question"
Justification as to why the closure is invalid: While this is a valid reason for closure, a simple edit to the wording of the question would have been infinitely more beneficial to the proposal (not having a question versus having a well formatted question). I suggested the wording update on September 4th and would have hoped that this would be updated, not closed.