He sent it to @minnowbooster so he has not gifted his SP to someone else!!! Please check that again!!!!
You are viewing a single comment's thread from:
He sent it to @minnowbooster so he has not gifted his SP to someone else!!! Please check that again!!!!
His memo was clearly in the format of gifting it to someone else. Luckily we have many posts explaining how the memo needs to be and we have a tool that creates the memo for you.
Sending natural language requests has the risk of being misunderstood. We have a discord with many helpful people if you are unsure of what to send and we will gladly proofread it for you if you ask.
bullshit,
Like I told you we since then fixed our memos to make this more clear. But the memo format is
<weeks> <user>and your memo has no weeks number, so it defaults to 1 and the user is clearly @forThis may not be what you expect but that is why the correct format for a memo is important. The bot cannot read minds sadly. And @smooth-a owns 45 steem like I said since he filled the order.
When it is obvious that there was a human mistake in communication with a bot that resulted in an unfair delegation of 2500 Steems to some one named @for. Then is there a problem in taking back your delegated rights and confer it to the one who deserves it rightfully???
The problem is that taking back the delegation takes one week, so 25 STEEM are already gone. Delegating to the other user means a second week gone. So 'refunding' means paying a second 50 STEEM.
We can refund the 5 STEEM in BuildTeam possesion once we are sure you know how to send a right memo from now on. But the other 45 STEEM are not ours to give.
ok. But I think your post should be prepared to handle such goof ups. If the memo format sent to the bot is not in the format suggested e.g. "<weeks <user" or whatever then no such request should be entertained. Slightest deviation from the standard format should be rejected asking to give request in proper format.
That is true. I am currently planning to implement it so that all memos with too many parameters get rejected.
fun fact: There exist a memo that cannot be detected, for example
4 weeksand if @weeks exists there is nothing we could do.See how you wrote 'for 4 weeks delegation of 2500 steem, thanks'?
Yes, we are observing what he wrote and what he meant. Now we want to see how you resolve this issue amicably. How much human are the humans behind this automated bot is my prime concern before entering into any business relationship with this bot.
See my reply below. We make 10% on these orders and we have over 22 000 happy users, a lot of whom are Steemians who have invested in our services. We would have to sacrifice revenue from 10 orders of this magnitude or 100 smaller orders just because your friend made a mistake. Does that sound fair to you? Fair to the people who already have entered 'into a business relationship with this bot?'. We need to find a solution that is fair to all.
could @fyrstikken please look into this, the service was clearly not provided, and the refund was never given, 50 Steem stolen from me.
Better not confuse minnowbooster with booster 🐐
If a user doesn't follow the instructions and enters another user's user name in the memo field and delegates SP to someone else, there really isn't much we can do. Your friend instructed the bot to delegate to the account @for
you will notice that I never used @for in that memo, and I was never informed by @minnowbooster of any filled order or refund. Obviously when a new service is offered, and mistakes occur, then it would be agreeable to all to make good.
Correct the memo's don't require the @ just like sending steem to someone doesn't require it, though I think this is a good idea. The problem here is we make 10% on these orders, to refund you because you made a mistake would cost us the revenue from 10 orders of the same size and 100 of our smaller orders. I am happy to work with you on this, but you'll need to give some ground, because the instructions on how to you use the service are clear and we have not intentionally or unintentionally ripped anyone off here. You just didn't follow the instructions.
If your order wasn't filled we would have refuneded it no questions - but someone did delegate to the account @for and @for did receive a notification saying it was successful. You are out 50 Steem, a delegator is out 2500 SP and we are down on time and PR. Lets try and find a solution which minimizes loss to all parties. Are you available on discord? As resolving there would be a little easier than back and forth on the blockchain.
Hope we can find a solution.
maybe the silver lining to this is creating an error free process for the future, left a message for you on chat.
Cool I will log on to .chat now and we will sort this out. Bear with me.
Well your first word is 'for' and that was exactly it. I notice you used it. It is hard to help you, when you don't think about it.