You are viewing a single comment's thread from:
RE: Make Noise Week 99: Weekly Engagement Report.
Hello good evening.
@royalevidence is my friend so
I think why it seems my account responded was he used my laptop to login so probably he thought he was stoll login not knowing that it is my account that have logined.
Why it is also reading the same memo is because we use the same crypto exchange which is roqqu as currently now, P2P has neen banned in Nigeria using Binance so currently now we use roqqu also so that's why
Hi @mandate,
And why do you use the same memo?
Other users have different memos.
Yes like I said, currently now , he does not have a roqqu account yet due to some personal reasons so for the main time
He always use my own roqqu account to get his Steem sold whenever he wants to get his Steem sold.
@alejos7ven
Ok @mandate @royalevidence, I have several reasons to think that you are the same person. Let’s see:
1- Why you share keys together? Did you know that it is very dangerous?
2- Why @mandate replied so fast? It is more likely you closed your session and opened this other one.
3- royalevidence was not verified in newcomers: https://steemit.com/hive-172186/@royalevidence/achievement-1-publication-by-royalevidence and was introduced by @dprogress with which also shared memos and few other accounts like grace-p, great-a
4- Royal and mandate using the same photo in achievement 1:
https://steemit.com/hive-172186/@royalevidence/achievement-1-publication-by-royalevidence
https://steemit.com/hive-172186/@mandate/achievement-1-introducing-my-self-on-the-steem-ecosystem
5- both using extremely the same style of markdown and writing.
For this reason you both will be excluded permanently of Make Noise project.
cc @steemcurator01
Hello please can I explain everything before you excluded me. It was a mix up actually please can you wait let me explain please how the issue is 🙏 @alejos7ven
What you have to explain? Even in your achievement 1 you say that you are the same person.
That is what I have explained above in the new comments I made to clarify the mixup.
@alejos7ven
I have dropped the detail explanation of where the mixup is and how everything is above in the comments I made