Shareholders examine the strategy of Linkedin,Microsoft, and the supportcenter
I am going to share the F5 problem with you.
Something is going seriously wrong here.
Because the whole F5 case is vanished I had to open a new case at Linkedin
The agents of the supportcenter is only doing her job, don;t blame them when they have to do their job even when it is demanded from the board of the supportcenter,Linkedin and Microsoft.
Since a few days I am not able to sent information. she is using a casenumber.Only that case is vanished.
Even when you reply I receive a message failure notice that it could not be delivered at the adress I am replying to
Re: Case #: 170917-000694 [Case: 171208-001414]
- [email protected]
- Vandaag om 19:45
Aan
Tekst van het bericht
Sorry, we were unable to deliver your message to the following address.
550: 5.7.0 domain ninaderon.com is listed at https://www.surbl.org
Shareholders, first of all there is an answer.Only let me remind you that when I have test it and it is not solved then legal action will follow.I have given them time enough for investigating and solving the whole f5 problem.
Second I have asked Linkedin and Microsoft to give me the names of the third parties that are collecting data at Linkedin and Microsoft.
Even when the f5 problem is solved, and I don't receive answers that goes over the third parties then all parties are not of the hook.You are informed.
I discussed your issue with our engineering team and they have deployed fixes regarding reappearance of suggestions in people you may know section. I request you to please check now and let me know if the issue still persists. If yes, please give me one name of the member (as an example) who appeared once you clicked on the remove mark and I'll look into it further. Also, please allow me to remove one people suggestion on your behalf from this end to reach the root cause. I shall wait for your findings.
Manager TIM Venture Capital, I am inventor of a new economic model at quantum leap level combined with a virtual central bank in dimensions made possible in 2019 through EC and EP the acceptance of virtual.
6 年https://www.fool.com/investing/general/2016/02/01/why-did-linkedin-corp-stock-drop-12-in-january.aspx
Manager TIM Venture Capital, I am inventor of a new economic model at quantum leap level combined with a virtual central bank in dimensions made possible in 2019 through EC and EP the acceptance of virtual.
6 年We're able to identify the issue from our end as well and working on fixing the root cause. I checked the status progress with my team and unfortunately, there is no estimated timeline when it'll be fixed. They're actively working on fixing it and it can take longer than usual. Sometime a small change can impact lots of related features and can hamper other crucial activity; hence, we're testing the fixes and working to resolves this issue as soon as possible.
Manager TIM Venture Capital, I am inventor of a new economic model at quantum leap level combined with a virtual central bank in dimensions made possible in 2019 through EC and EP the acceptance of virtual.
6 年When the problem is solved here for my email,office, then claims will come your way from my emailprovider and other companies. You have crossed the line here Microsoft.
Manager TIM Venture Capital, I am inventor of a new economic model at quantum leap level combined with a virtual central bank in dimensions made possible in 2019 through EC and EP the acceptance of virtual.
6 年I am not pleased shareholders, when f5 problem cannot be solved and the IT department has the budget used for their priorities. I have turned offf Word at Linkedin and when this app effect my mail, then claims will come your way from the emailprovider and the other companies
Manager TIM Venture Capital, I am inventor of a new economic model at quantum leap level combined with a virtual central bank in dimensions made possible in 2019 through EC and EP the acceptance of virtual.
6 年The answer of Linkedin Trust and Safety Thanks for your patience and we are incredibly sorry for the inconvenience caused. The engineering team confirmed the mentioned but is still being worked upon. We will respond to your previous case (171018-005889.) once the bug is resolved.