customer's username replaced by "Customer" - page 3

 
Sergey Golubev:

The meaning is the following: they hide the name/data/contacts of the customer to prevent the customer and applicants to contact with each other (by PM or any). Because some of the applicants are trying to make the contacts with the customer to make a job without freelance service. So, the customer will be hiden until he select the coder who will implement a solution.

Means: they are hiding the customer's data from the applicants (not from the coder who was selected to make a job). 

But what if develoepr wasn't interested to work with that customer ?

You know that some customers are keeping the jobs open for more than 30 days without any reply so then we should request arbitration that affects our profile or just waiting.....

this was only one of the reason that developer might not interested, so there is no need to apply on that job at the beginning.
 
Hossein Nouri:
But what if develoepr wasn't interested to work with that customer ?

You know that some customers are keeping the jobs open for more than 30 days without any reply so then we should request arbitration that affects our profile or just waiting.....

this was only one of the reason that developer might not interested, so there is no need to apply on that job at the beginning.
The discussion is still going on here (it is 18 pages on the thread for now - the thread was started the day before yesterday) so we will see the situation.
 
Sergey Golubev:
The discussion is still going on here (it is 18 pages on the thread for now) so we will see the situation.
Alright, thanks.
 

Форум по трейдингу, автоматическим торговым системам и тестированию торговых стратегий

Программистам, нужны ли в сервисе ФРИЛАНС фильтры для отбора заказов

Renat Fatkhullin, 2017.02.10 19:25

Considered. One of the important changes in the input hourly rate that is quite common. The customer will be able to hire a developer hourly job and then settle on the fact. In fact, this is where the money is made basic earnings. We want to attract companies that they are found on the developers a lot of their problems. And, we will open the possibility to develop and solutions on the server, managerial, and report Data Feed API for developers certified by us. This is another very lucrative segment of the work, which is now closed because this area is very expensive prices.
This is very interesting 
 
This is totally ridiculous. I assume that we are not hidden from the customer?

There are some customers that I have had lengthy discussions with who have then just not followed through with the job. See how many outdated jobs there are. Jobs that have just been dropped or the developer and customer have made a private deal to not pay through mql5.

Other times, I have wasted time ironing out details so that I know exactly what the customer wants (They are usually very vague regarding the details). Then they want a sample code which they obviously test in the strategy tester. They find that it doesn't make profits and then you don't hear from them again.

We need to know who the customer is so that we can avoid the known time wasters.
 

I agree ive seen a guy offer 1000$ Dollar for good ideas and then he listen to all coders talk and collects all the combined knowledge and then decides it wasn't worth 1k and he disappeared.

Some good thinking is needed for this freelance system.

I perfectly understand that they do not want deals outside of the freelance section my guess is that they discovered that a lot was going on in PM after someone posted a new job.

So that issue they have successfully prevented by using customer in stead of username.

 
As a coder myself, I personally opted not to offer my services in the Freelance section for many reasons, mostly negative. One reason in particular, is the double standard that MetaQuotes implements, namely that coders have to be “vetted” and prove who they are and openly identify themselves with a real name, but customers on the other hand, don’t undergo any such vetting and present themselves under an alias. They can even easily have several “false” accounts which makes things even worse.

This “new”, even more anonymous “feature” that MetaQuotes is presenting, makes the system even more atrocious. In my humble opinion, both customers and coders should be vetted and present themselves with real names so as to have transparency on both sides of the transaction.

I find this double standard very disturbing!
 
Marco vd Heijden:

I agree ive seen a guy offer 1000$ Dollar for good ideas and then he listen to all coders talk and collects all the combined knowledge and then decides it wasn't worth 1k and he disappeared.

Some good thinking is needed for this freelance system.


Definitely needs good thinking

eg the ridiculous amount of steps that you need to go through from implementing a job to completion.

If one party is asleep while the other is online it can take days to complete, making a job overdue.

I perfectly understand that they do not want deals outside of the freelance section my guess is that they discovered that a lot was going on in PM after someone posted a new job.

So that issue they have successfully prevented by using customer in stead of username.
Not really, if the customer wants, he can just give the developer his email
 

It's better if the system lets the customers choose the option to hide their name when they post the project.

Some customers don't want to hide their name. 

 
Cuong Truong:

It's better if the system lets the customers choose the option to hide their name when they post the project.

Some customers don't want to hide their name. 

Actually this doesn't make any difference cause those customers that I mentioned before will hide their name, cause no body wants to work with them.

This system only was needed about the private jobs, cause personally I noticed that I offered some price to my customer but someone else messaged him a lower price through the chat, so privacy is a good thing but not everywhere.
Reason: