WEBVTT

NOTE recognizability 0.900

NOTE language en-us

00:00:00.020 --> 00:00:04.010
Oracle is said to be announced as take talks tech partner in the

00:00:04.010 --> 00:00:08.920
us the chinese social media app chose oracle as its new us partner while we

00:00:08.920 --> 00:00:13.860
popular video sharing amp with the potentially new partner after being threatened by

00:00:13.860 --> 00:00:19.070
...from president travel has been expressing concerns about

00:00:19.070 --> 00:00:24.290
takes talks us data which basically he's saying that because...talk is

00:00:24.290 --> 00:00:29.280
by this chinese company...dance he is worried that the talk is giving

00:00:29.280 --> 00:00:33.950
away us customer information to beijing to the chinese government

00:00:33.950 --> 00:00:38.510
...talk I said again and again it's not doing this...all us data in the us

00:00:38.510 --> 00:00:43.370
would back...not handing over but us officials are worried that some

00:00:43.370 --> 00:00:48.550
time in the future it could hand...to the...government and that represents

00:00:48.550 --> 00:00:53.300
the national security risks...then child issued this pair of order is one of

00:00:53.300 --> 00:00:58.370
which would am...talk in the us starting september twenty...

00:00:58.370 --> 00:01:03.040
stuff and...one which goes through this different us department of treasury

00:01:03.040 --> 00:01:06.250
process...basically make talks chinese owner

00:01:06.250 --> 00:01:10.650
...best from the company in the us so to talk is going to partner with oracle

00:01:10.650 --> 00:01:15.240
but it doesn't seem like it's going to be a full...instead take talk

00:01:15.240 --> 00:01:20.130
has submitted this proposal to the trunk administration that basically would let oracle

00:01:20.130 --> 00:01:27.340
...technology partner which we think means management of its us data.

00:01:27.340 --> 00:01:31.130
It seemed for a long-time like microsoft was the front-runner to buy

00:01:31.130 --> 00:01:34.250
...talks us operations microsoft was the first come out

00:01:34.250 --> 00:01:38.900
publicly and say yes we are trying to buy to talk in the us we're very interested

00:01:38.900 --> 00:01:44.440
but then beijing the chinese...the day also wanted to

00:01:44.440 --> 00:01:49.840
...part of the deal basically they said they would have to

00:01:49.840 --> 00:01:54.600
take talks telling...proprietary algorithm to an american company and that

00:01:54.600 --> 00:02:00.600
seem to me what microsoft was interested in and ultimately to talk ended up.

00:02:00.600 --> 00:02:05.290
We don't have the details of that deal but what we think it says is basically

00:02:05.290 --> 00:02:08.960
the oracle would take control of tick talks data and

00:02:08.960 --> 00:02:13.690
...it in the us we're not actually own

00:02:13.690 --> 00:02:18.580
it talks us operations which is what they were saying was going to happen before

00:02:18.580 --> 00:02:23.250
oracle manages a lot of data for a lot of different companies and it's possible that

00:02:23.250 --> 00:02:26.780
...was looking for a way to kind of only

00:02:26.780 --> 00:02:30.710
sell itself but rather get a partner in place that

00:02:30.710 --> 00:02:34.560
would satisfy the us government but still allowed to

00:02:34.560 --> 00:02:37.990
talk to really control of...operations another reason

00:02:37.990 --> 00:02:41.970
weeping oracle might have been chosen as oracle has really good relationships

00:02:41.970 --> 00:02:45.680
with administration larry ellison and its founder

00:02:45.680 --> 00:02:51.280
...current ceo africa paths...eight...of.

00:02:51.280 --> 00:02:55.150
Now we just wait to see if the trump administration is going to

00:02:55.150 --> 00:02:59.930
accept this steal from...talking oracle again we don't really know exactly what

00:02:59.930 --> 00:03:04.730
the deal holds but if they accept the deal what we can assume will happen is that

00:03:04.730 --> 00:03:08.780
to talk users in the us will still be able to use the abnormally

00:03:08.780 --> 00:03:13.360
and it dust might have a different data management structure that would be so on the back-end

00:03:13.360 --> 00:03:14.920
the users probably one...

00:03:14.920 --> 00:03:20.900
node the interesting thing about this is that it seems to be just another example

00:03:20.900 --> 00:03:27.060
of the escalating tensions between the us and china it's kind of unprecedented

00:03:27.060 --> 00:03:32.180
...a social media company of b...the us like this we've never seen a

00:03:32.180 --> 00:03:37.280
huge consumer app get bands like this one could potentially so it

00:03:37.280 --> 00:03:41.100
seems to be really caught up in the politics of international relations.