RE: Everything is going to be gamed
You are viewing a single comment's thread:
What this means is that no matter the system created, there is always likely to be those who will look to use it in ways it was not designed to be used meaning - Ab-use - wrongly used.
If a tool serves a purpose, and is used in a manner not designed to be used, it is still a tool, it was used to accomplish a goal, such as the hammer breaking a skull. Should hammers be banned? Using the claw of the hammer to dig a shallow hole to plant a seed because that was the tool you had at hand, should it be banned because it was not used correctly or should you be punished for using it incorrectly and against it's design?
At the blockchain level, we are all bound by the code, but society has a far more open and complex set of rules - and no one knows them all.
Un-like walking life, there are people who know the code and rules of the block chain. Odds are that there is at least one person that can code around all the block chain code and get the results they want. Did they violate the code? or did they use the code to their advantage. Did they find a new use for the tools of the code? Like a hammer it can serve it's original designed purpose, it can be used to take life, and it can be used to start life.
This my point, using a tool for unintended purposes isn't right or wrong, it is just how it gets applied. I personally am one of the people who will make do with what is available, rather than buying a specific tool for the job. I find it part of my creative process to "fix" something with stuff that wasn't designed for that purpose. Everyone has used a knife as a screwdriver...
The blockchain workarounds are interesting as it is generally frowned upon to bypass the blockchain, even though that is essentially part of the code. Of course, there are more value adding actions than others.
I understood that, people get to wrapped up in "that is not designed for that" issues. Tools are tools if it get the job done it worked. More people need to figure that out, and not be so petty about using things in manners not designed to be used.
!ENGAGE
I need practice remembering that above.
In regards to the ENGAGE, putting a number after, r.g !ENGAGE 20 will distribute that number of the tokens - without the number it will distribute 1 :)
See it has been awhile, I thought it was auto 25 with no number. So let me try and fix that, !ENGAGE 25. Thank you for that information now I know.
ENGAGEtokens.ENGAGEtokens.ENGAGEtokens.