7

I usually also close a number of duplicates, but some of these are distinct and should be reopened imo. Writing secure Smart Contracts in Solidity? is a community wiki and I think it should be allowed and would be very helpful for the community; not all list/resource type of questions are bad. How was the recursion created that lead to theDAO hack? is ...


6

I agree. We should eliminate this type of question. If for no other reason that we wouldn't want to give bad advice. Plus--if we're giving advice of this type, we should get paid for it. Not sure if you can add a new flag type, but it would be helpful and more clear than a simple 'off-topic.'


5

"leads to an opinionate outcome" should not be a waiver for closing everything. It means two things: (1) there is no final objective outcome and answers could be only subjective, (2) there is a final outcome but the community is strongly opinionated and passionated about it, so I don't want to have the hassle as a moderator and OMG politics. Clearly only (1) ...


3

As a matter of emerging policy, the Community Wiki setting has been all but deprecated. A user's answer should virtually never be forced to Wiki (to remove reputation or otherwise) unless it is explicitly set or requested by the author, and the ability to mark a question Community Wiki (with all its answer) has already been removed. See The Future of ...


2

I would say remain as is. While I see that the question is not very specific, it's very well on-topic and an actual issue the users faces. In general, I think it's good to have frequently asked questions featured on Stack Exchange. This could be a good example for a canonical question on how to get testnet ether with all options available and strings ...


Only top voted, non community-wiki answers of a minimum length are eligible