Personally I don't see any reason why asset transfers would be wanted by anyone doing legitimate business. The exchange exists for a reason and all trades/transfers should be made publicly on the exchange. Allowing these asset transfers goes against transparency and seems to contradict the principles of Bitcoin.
Because asset transferring has many, many use cases. It's
not just a way to trade assets for bitcoins outside the exchange. rdponticelli has given one great example; another one is borrowing assets (useful for shorting) or gifting them; I have an asset I plan which will simply be impossible to issue at all without transfers (I'm keeping it under wraps for now); many other uses which nobody has yet thought of, and mundane stuff like internal bookkeeping.
I agree with Meni. I will be more than happy to pay the normal fee on the pre-sale transfers.
As a significant shareholder, Mr. Popescu would prefer you skip the glbse listing altogether, never deliver any shares there and just keep spreadsheets.
You have probably a couple dozen people invested, how hard can it be to make a couple dozen payments once a month? Surely less hassle than dealing with this sort of thing on a continuing basis.
If gigavps is content with big players who don't care much about liquidity, sure. But if he wants to also deliver to the many people wanting to invest 1 BTC, he is
not going to pay them each individually.
1) Learn from your mistakes
2) Don't be jerks - by that I mean don't be such knee jerks
3) Develop a process for changes to the ToS, I suggest:
a) Someone finds an issues
b) You all get together and discuss it, think about what you want to change, think of the impact on users
c) You privately contact some of the larger users that would be affected - get their feedback, discuss it with them
d) Float the idea in a post but instead of "We have taken this totally knee jerk reactionary measure to totally fuck with you, what do you think" instead try something like "We are considering doing X, how would this affect you all? What do you think? Should we do this? Why and Why not? etc."
e) Make the changes to the ToS
f) Post the changes, get more feedback
g) If the feedback is negative go back to b)
h) NOW: Make the actual changes to the web site.
The above process would have averted both the Goat shit storm and this one.
+1.
I'm not sure I completely understand the Goat incident but I'm under the impression there were potential security issues, making it too time-critical for this procedure. But there's no excuse to handling the transfer disabling this way.
Because of this, it would be a good idea to offer an official apology for not having followed this procedure.