WEBVTT

00:00:01.439 --> 00:00:08.639
welcome to the WAN Show the first WAN Show of 2018 and

00:00:06.240 --> 00:00:12.400
uh the last wednesday the last WAN Show of this week

00:00:10.160 --> 00:00:16.400
before ces there we go i forgot what was important yes is gonna happen soon yeah

00:00:14.559 --> 00:00:19.920
that's that's i'm gonna blame my mind scattering on that so who's all going

00:00:18.320 --> 00:00:24.080
because this is your first year it's my first year it's gonna be alex's first

00:00:21.840 --> 00:00:30.160
year alex the greatish yeah it's gonna be Jake's first time uh away from home

00:00:27.519 --> 00:00:32.360
yes away from the nest his mom's driving him to the airport but after that he's a

00:00:31.840 --> 00:00:37.600
free man in vegas 18. i'm going to give her a

00:00:35.600 --> 00:00:41.680
wink from the parking lot there oh yeah a knowing smile

00:00:40.559 --> 00:00:47.760
oh wow um and then so so you alex Jake max

00:00:46.399 --> 00:00:51.760
yeah and then i think that's everyone who hasn't been

00:00:50.000 --> 00:00:55.920
i'm not sure if pelo was there last year or not he's been around there's gonna be

00:00:53.520 --> 00:01:02.239
a pack of us though hey brandon look out was pella at ces last year yes yeah okay

00:00:59.359 --> 00:01:06.320
so it's out so it's all just writers who weren't there last year

00:01:03.680 --> 00:01:09.760
whoa and max coleman was almost here i almost jumped in from the camera right

00:01:07.920 --> 00:01:13.520
all right okay so that's that's what's going on with ces that's going to be

00:01:10.960 --> 00:01:17.680
next week expect a huge torrent of videos to be hitting youtube and

00:01:15.360 --> 00:01:21.439
Floatplane it's going to be insane tons of stuff coming excited and stressed

00:01:19.920 --> 00:01:25.280
you should be already it's a pretty insane experience i have performance

00:01:23.040 --> 00:01:28.479
anxiety on the one hand i'm so stoked because as a kid i i subscribed to xbox

00:01:27.439 --> 00:01:33.840
magazine and they were always talking about going to e3 yeah and i was like oh that's so amazing it's totally different

00:01:32.159 --> 00:01:37.600
sure but i never thought that i'd go to any yes giant conference like that and

00:01:35.920 --> 00:01:41.439
see all this cutting-edge stuff face up cbs is more

00:01:39.520 --> 00:01:45.759
more insanity in terms of like that suits me

00:01:44.320 --> 00:01:51.280
the the people on the floor where you need to go so e3 is nicely contained in

00:01:48.079 --> 00:01:53.360
one building and they're like super way

00:01:51.280 --> 00:01:56.880
more hardcore or at least they were they've loosened it up a little bit

00:01:54.720 --> 00:02:00.079
about who could go so there wasn't a ton of people on the floor and it's all in

00:01:58.159 --> 00:02:04.079
one building this is well early in the earlier days like in the early 2000s it

00:02:02.159 --> 00:02:07.360
was less expensive yes yes and then they tightened it up yeah you should grow

00:02:05.520 --> 00:02:09.920
your beard longer you have so much more wisdom than i do and our beards are the

00:02:08.879 --> 00:02:16.879
same length this doesn't make any sense uh but yeah ces is going to be insane um

00:02:14.319 --> 00:02:23.280
i'll be at ces with a mustache no wisdom your first time all that off yeah no no

00:02:19.760 --> 00:02:24.400
i was like i don't know

00:02:23.280 --> 00:02:30.959
either way what we're going to talk about this week is a lot of Intel stuff a lot of ARM stuff

00:02:28.319 --> 00:02:36.480
a lot of AMD stuff as you guys know uh cpus right now are in kind of a terrible

00:02:33.920 --> 00:02:40.239
spot with meltdown and spectre both going around rampaging things where i'll

00:02:38.480 --> 00:02:43.920
talk about um we're going to talk about what different

00:02:42.080 --> 00:02:47.280
companies are doing to deal with this how it's being dealt with how it might

00:02:45.599 --> 00:02:51.440
affect you how it's affecting other companies different responses that are happening

00:02:49.920 --> 00:02:55.920
due to it all that kind of stuff we're gonna talk about all that kind of stuff and there's a bunch of other interesting

00:02:53.920 --> 00:02:59.280
things as well um like some stuff to do with spotify

00:02:58.400 --> 00:03:04.080
uh and luke's super secret new year's

00:03:01.440 --> 00:03:07.440
resolution well the intro for dramatic effect

00:03:08.879 --> 00:03:11.200
yes

00:03:13.920 --> 00:03:17.200
i made that last bit up

00:03:26.560 --> 00:03:31.319
eat about as much sugar as i usually do

00:03:32.959 --> 00:03:37.920
yay sponsored strasbourg for making this

00:03:36.159 --> 00:03:41.200
show viable moving back okay

00:03:39.840 --> 00:03:46.400
let's get into it um i'm going to post

00:03:43.280 --> 00:03:48.959
an rs technica thread it was uh or a

00:03:46.400 --> 00:03:53.680
post uh an article article there we go we'll go with that it's posted by uh

00:03:50.879 --> 00:03:58.799
peter bright it's a very good article thank you peter bright for making a very

00:03:55.920 --> 00:04:01.680
nice concise package this is everything that's going on it's way too long most

00:04:00.480 --> 00:04:07.760
people aren't going to read it grab a coffee and a donut to go through it kind of article there's a lot of information

00:04:04.879 --> 00:04:11.760
this whole story is like an onion with layers yeah so we're going to take

00:04:09.599 --> 00:04:16.160
you through the entire story of how these vulnerabilities were discovered uh

00:04:14.480 --> 00:04:20.560
the what the response from the parties involved was and kind of all the

00:04:18.400 --> 00:04:25.840
insanity that has ensued and is still ensuing today yes so i'm gonna jump

00:04:23.919 --> 00:04:29.680
slightly forward and explain what they are and then we'll jump back to the start

00:04:28.320 --> 00:04:33.120
and explain how it was found and all that kind of stuff okay sense okay and

00:04:31.600 --> 00:04:36.720
jump around a little bit it's gonna be crazy tension so i'm gonna steal some of

00:04:35.120 --> 00:04:40.160
this from rs technica again thank you very much peter bright uh mel so there's

00:04:39.360 --> 00:04:44.960
two main uh vulnerabilities and they're kind of

00:04:42.720 --> 00:04:51.120
related they are kind of related they they source from the same type of uh

00:04:47.520 --> 00:04:53.440
area so jumping to the rs article um

00:04:51.120 --> 00:04:57.840
modern processors perform speculative execution that's where a lot of this is

00:04:55.040 --> 00:05:02.880
based on that is where a processor will assume what needs to be done next and do

00:05:00.240 --> 00:05:06.560
that thing do those calculations and then if it is wrong and that isn't

00:05:04.639 --> 00:05:11.199
what's happening next that is fine it doesn't matter it ditches all that code

00:05:08.960 --> 00:05:15.360
no big deal if it's right then hey it's already done it and it's able to execute

00:05:12.720 --> 00:05:19.759
that thing faster this is a great thing it makes things run a lot faster

00:05:18.000 --> 00:05:22.720
it's not a big deal that it's running some code and coming up with some

00:05:21.199 --> 00:05:25.840
answers and then ditching those answers because it's making a lot of other

00:05:24.479 --> 00:05:30.560
things faster when it does guess correctly pretty much only upside

00:05:28.720 --> 00:05:35.360
yeah this is a property of modern cpus yes

00:05:33.360 --> 00:05:39.199
that would be a reason why spoiler alert

00:05:37.440 --> 00:05:42.320
these these vulnerabilities don't really have as much of an impact on older much

00:05:41.520 --> 00:05:47.199
older chips yeah um so spectre and meltdown

00:05:46.000 --> 00:05:52.000
that we're going to be talking about today um are

00:05:49.680 --> 00:05:56.160
it perturbs the processor state in detectable ways which is bad that

00:05:54.479 --> 00:06:00.080
essentially when you break that down means that these vulnerabilities can

00:05:58.960 --> 00:06:04.080
watch even though it doesn't have access to

00:06:02.320 --> 00:06:07.440
these code paths these speculative execution code paths it can figure out

00:06:05.840 --> 00:06:11.120
what they're doing which is bad because it gives them more

00:06:09.199 --> 00:06:14.160
information and it could result in more things down the line

00:06:12.720 --> 00:06:18.960
meltdown inspector is what we know of right now so again to break down what

00:06:16.160 --> 00:06:23.520
meltdown and spectre are meltdown it's applicable to every Intel chip made

00:06:21.520 --> 00:06:27.039
for many years i don't think we know necessarily right now actually there is

00:06:24.960 --> 00:06:31.919
a list yeah you should show the list i don't entirely know if the list is you

00:06:29.280 --> 00:06:35.600
don't believe my list oh we didn't do screenshots we have an HDMI

00:06:34.160 --> 00:06:40.400
the classic meme of wancho which is it's late screen

00:06:38.400 --> 00:06:45.039
sharing is never not prepared and audio doesn't work

00:06:42.319 --> 00:06:49.000
yes except what screen is that

00:06:49.440 --> 00:06:52.960
that's not up on either

00:06:53.520 --> 00:07:00.479
that's awesome um hold on

00:06:57.600 --> 00:07:04.880
anyways there is a list i can post it in the twitch chat so you guys can check it

00:07:03.120 --> 00:07:09.120
out yourselves suffice to say it's basically every Intel trip for the last

00:07:06.479 --> 00:07:12.800
15 years yeah kind of a big deal and it's going to affect different chips in

00:07:11.199 --> 00:07:16.720
different ways which is another interesting part newer chips have

00:07:14.960 --> 00:07:21.440
certain standards which will actually help them deal with this um a little bit

00:07:19.680 --> 00:07:26.000
better than certain older chips it also affects different programs differently

00:07:24.319 --> 00:07:30.160
so certain programs are going to get hit by this really heavily

00:07:27.759 --> 00:07:34.400
microsoft has found i will go into that more later but microsoft has found that

00:07:32.240 --> 00:07:38.240
certain antiviruses have been using things in undocumented ways that utilize

00:07:37.440 --> 00:07:42.080
this type of stuff so when they try to turn

00:07:40.639 --> 00:07:46.319
it off again we're going to get into that more later i'm trying to be vague because we'll go more deeply into that

00:07:44.400 --> 00:07:51.120
later uh it causes problems for the antivirus programs which is a nightmare

00:07:49.199 --> 00:07:56.960
but anyways it's all it's all a whole mess but basically a verbal table of contents

00:07:55.199 --> 00:08:01.520
thank you uh meltdown chapter one applicable to

00:07:59.199 --> 00:08:06.240
every Intel chip for many years listed in the twitch chat um and will be in the

00:08:04.160 --> 00:08:09.919
dock if you access the forum so if you're watching

00:08:08.080 --> 00:08:16.319
this on youtube or you're listening to this on soundcloud which a few people do

00:08:13.919 --> 00:08:19.919
it does actually happen some people do listen to this on soundcloud uh you can

00:08:18.160 --> 00:08:23.680
go into the description and there will be a forum link if you go to that

00:08:22.000 --> 00:08:27.360
that'll show the doc and in the doc there will be a link with all capital

00:08:25.599 --> 00:08:32.159
letters that says list of affected Intel cpus anyways moving on every Intel chip

00:08:30.240 --> 00:08:35.919
for many years along with certain high performance ARM designs only high

00:08:34.080 --> 00:08:39.440
performance ARM designs this flaw depends on the way that

00:08:37.599 --> 00:08:44.560
operating systems share memory between user programs and the kernel and the

00:08:41.519 --> 00:08:47.040
solution right now um carries some

00:08:44.560 --> 00:08:50.720
performance penalty in certain cases really brutal ones i believe the highest

00:08:49.360 --> 00:08:54.399
reporter that i've seen is about 30 percent yeah but i think that's more

00:08:52.800 --> 00:08:58.000
anonymous it's usually i think it's usually especially if i have a newer CPU

00:08:56.080 --> 00:09:02.720
it's about five percent yeah yeah it's no very rarely that bad it's also only

00:09:01.120 --> 00:09:07.279
certain processes and programs that are gonna get affected by it and it's also

00:09:05.519 --> 00:09:10.880
less as impactful if you have newer chips and it's going to depend on what you're doing too i've heard in gaming it

00:09:10.080 --> 00:09:15.760
can be it can result in like three frames

00:09:13.279 --> 00:09:19.360
per second yeah fbs so yeah but it really is gonna depend

00:09:17.920 --> 00:09:24.240
um but the the answer to this is to put an

00:09:22.320 --> 00:09:28.399
end to that sharing of memory between user programs

00:09:26.480 --> 00:09:34.560
and the kernel which is why there's that performance penalty and then spectre um

00:09:31.760 --> 00:09:37.360
it's applicable to chips from Intel AMD and ARM

00:09:35.760 --> 00:09:43.200
this is where some of the confusion came in that we're going to talk about soon where uh AMD didn't think they were

00:09:40.880 --> 00:09:47.600
susceptible to anything and then now it's just Intel's susceptible to more

00:09:45.440 --> 00:09:51.920
stuff and everyone's susceptible to some things and each company is trying to

00:09:49.200 --> 00:09:55.040
minimize what are the the optics yeah like

00:09:52.720 --> 00:09:58.800
AMD said this is a near zero chance of affecting us and and Intel doesn't want

00:09:57.440 --> 00:10:03.519
their stock to drop so they're saying yes it does affect you yeah yeah it's a

00:10:01.680 --> 00:10:06.800
lot of politics involved as well there's a huge amount of politics in this we'll

00:10:05.040 --> 00:10:11.360
get into that a little bit more in the future um

00:10:09.040 --> 00:10:15.279
yeah it even says Intel AMD ARM and probably every other processor on the

00:10:13.040 --> 00:10:20.399
market that offers speculative execution which is like all of them um

00:10:18.399 --> 00:10:25.519
it's also more subtle it encompasses a trick testing array bounds to read

00:10:22.800 --> 00:10:30.720
memory within single processes which can be used to attack the integrity of

00:10:28.000 --> 00:10:36.399
virtual machines and sandboxes which is rough that's a big deal for the

00:10:32.720 --> 00:10:38.480
cloud yeah um and and cross process

00:10:36.399 --> 00:10:42.800
attacks using processors branch predictors which is the thing that i was

00:10:39.839 --> 00:10:45.040
mentioning earlier where it can uh take little bits of resulting

00:10:44.000 --> 00:10:49.680
information to figure out what it was actually doing fixes for some aspects of

00:10:47.760 --> 00:10:54.959
spectre appear to have been developed already but protecting against the whole range

00:10:52.399 --> 00:11:00.880
of fixes will require modification or at least recompilation of at-risk programs

00:10:57.600 --> 00:11:02.880
and that is also a very rough part

00:11:00.880 --> 00:11:06.480
because that brings way more players into the space because now you're

00:11:04.480 --> 00:11:11.740
talking about programs too so i think it's fair to say that the only true fix

00:11:08.160 --> 00:11:15.610
is new chip architecture

00:11:15.680 --> 00:11:20.800
um one it depends what we're talking about

00:11:19.040 --> 00:11:24.399
unfortunately the sketchy one that requires the most amount of tinkering

00:11:22.720 --> 00:11:27.440
level fixing for the most amount of people is spectre which affects

00:11:26.320 --> 00:11:32.560
everybody everybody that has speculative

00:11:29.360 --> 00:11:36.000
processing um which so that's that's

00:11:32.560 --> 00:11:37.040
really annoying but you can on a single

00:11:36.000 --> 00:11:42.320
system know that you're okay if

00:11:40.079 --> 00:11:47.040
you go through like everything make sure everything has been uh modified or

00:11:44.560 --> 00:11:51.200
recompiled that is affected by this make sure your os level is happy all that

00:11:49.360 --> 00:11:54.720
kind of stuff turn on Windows updates guys

00:11:52.720 --> 00:11:59.040
at least yeah um

00:11:56.480 --> 00:12:03.839
it's this this it's it's it's kind of a nightmare so how did this first get

00:12:01.760 --> 00:12:08.079
discovered do you want to jump us there i know i thought i was the only question

00:12:06.079 --> 00:12:11.200
but i i can clarify some things because you know okay

00:12:09.760 --> 00:12:15.360
so the way this was discovered was through google project zero

00:12:13.360 --> 00:12:20.880
project zero is one of those little google subsidiaries that has a

00:12:18.320 --> 00:12:24.320
specific task their task is to find what are called zero day bugs or

00:12:22.959 --> 00:12:29.839
vulnerabilities that's where the zero from project zero comes from that's right so basically you're finding a bug

00:12:27.920 --> 00:12:34.399
as soon as you can as fast as you can and fixing it as soon as it's found so

00:12:32.079 --> 00:12:38.880
the way this works is there are bug bounties a certain amount of money put

00:12:36.959 --> 00:12:44.079
up if bugs are found so all these freelancers joe schmoe's hackers

00:12:41.440 --> 00:12:47.279
white hats around the world are actively searching for bugs

00:12:45.760 --> 00:12:52.560
among the uh the suite of software and hardware that

00:12:49.920 --> 00:12:57.839
is on project zero's list so a company can say we're on your list we want your

00:12:54.480 --> 00:12:59.120
freelancers uh to find bugs for us yeah

00:12:57.839 --> 00:13:04.880
so a person it's a really cool program uh found this vulnerability i believe in

00:13:02.560 --> 00:13:07.680
the summer time actually it's been a bit people have been working on this for a

00:13:06.000 --> 00:13:11.600
little while yeah and they notified Intel at the time

00:13:09.680 --> 00:13:15.839
yeah but it's only just become known to the public this week one quick thing

00:13:13.600 --> 00:13:20.320
someone in the chat was like idiot this doesn't affect iphones apple has already

00:13:18.079 --> 00:13:26.880
issued um apple has updated both iOS and macOS to

00:13:23.519 --> 00:13:30.560
use dual page table mappings i believe

00:13:26.880 --> 00:13:32.399
specifically for spectre yeah so

00:13:30.560 --> 00:13:37.440
it does affect the thing is it's such a low level vulnerability

00:13:34.959 --> 00:13:40.560
that if apple is going to patch it they're doing it at a higher level so

00:13:38.959 --> 00:13:45.200
they're only going to be able to defend

00:13:42.000 --> 00:13:47.120
from certain aspects of it yeah well and

00:13:45.200 --> 00:13:49.440
there's some nice stuff like we're jumping around all over the place i know

00:13:48.399 --> 00:13:55.440
it's gonna be a little bit hard to follow um i would highly recommend checking out

00:13:53.360 --> 00:13:58.959
the WAN Show doc on the forum for this reading a few of the different actual

00:13:57.199 --> 00:14:04.320
articles that have been properly posted we're trying to talk live

00:14:02.160 --> 00:14:07.279
the rs article is really good but also with something like this

00:14:05.760 --> 00:14:10.720
you should cross-reference information just to make sure you're getting everything good so if this is affecting

00:14:09.360 --> 00:14:16.560
you or you're really interested in this i would definitely recommend diving into it but

00:14:13.600 --> 00:14:20.240
people like amazon with s2 instances are pushing updates of their own which is

00:14:18.320 --> 00:14:24.399
like handling everything on their side which is really nice um but there's

00:14:22.880 --> 00:14:28.880
that's that's not the case in all situations but sorry continue

00:14:27.199 --> 00:14:31.440
well you continue so what happened after that they found it moving after that the

00:14:30.240 --> 00:14:36.800
universities they made a nice white paper about it yeah so universities from

00:14:34.480 --> 00:14:40.639
america i remember it because it's 3a countries america austria and australia

00:14:39.519 --> 00:14:45.040
boom um oh no it did this thing

00:14:43.360 --> 00:14:48.800
randomly when we're doing the WAN Show i get signed out of my google account and

00:14:47.199 --> 00:14:53.279
i have to it's okay i don't actually need it this second i'll get signed in

00:14:50.320 --> 00:14:56.000
while i'm talking oh lastpass oh this whole thing you're screwed it's so much

00:14:54.720 --> 00:15:01.680
you're gonna need your yeah and everything now hopefully not we'll see though

00:14:59.920 --> 00:15:09.279
but yeah universities from america australia and austria and google project

00:15:05.120 --> 00:15:11.600
zero and people working at microsoft and

00:15:09.279 --> 00:15:15.120
google and amazon and all these huge companies all came together to try to

00:15:13.120 --> 00:15:20.800
work on this and they've been working on it actually

00:15:17.199 --> 00:15:21.920
for quite a while

00:15:20.800 --> 00:15:27.440
there's this is where we get into

00:15:25.040 --> 00:15:32.480
there's a lot of different information and it's a little bit confusing what

00:15:29.600 --> 00:15:38.800
happened next but the public figured out and the public figured out

00:15:34.480 --> 00:15:40.639
not that long ago uh the main

00:15:38.800 --> 00:15:44.240
article that really blew up in a lot of people's minds because it was much more

00:15:42.079 --> 00:15:47.760
public-facing i believe was the register article

00:15:45.120 --> 00:15:50.480
register.cod at uk which is posted in the landoc if you want to check it out

00:15:49.279 --> 00:15:54.800
on the forum that was as far as i know one of the

00:15:52.720 --> 00:15:59.759
biggest explosions in terms of more people knowing there was talk about

00:15:57.040 --> 00:16:03.759
it on on more like programmer focused back channels this was a big news outlet

00:16:02.079 --> 00:16:07.759
bringing it on i could be wrong about that it could have been someone else first this is the first one i saw same

00:16:06.720 --> 00:16:13.360
and i think it's the first one most people saw

00:16:09.920 --> 00:16:17.120
it got to there as far as i know

00:16:13.360 --> 00:16:20.079
because a programmer at AMD

00:16:17.120 --> 00:16:25.519
pushed code to the Linux kernel let's see here ah

00:16:23.920 --> 00:16:30.000
yeah so there was an embargo on all this kind of stuff through the google project

00:16:27.360 --> 00:16:33.839
zero platform um not everyone agrees with having embargoes on these types of

00:16:31.680 --> 00:16:37.120
things some people position themselves with like all information should be open

00:16:36.079 --> 00:16:42.880
everyone should know everything that's going on um and your opinion on that is

00:16:40.399 --> 00:16:48.079
whatever's ease but there was an embargo and it wasn't like technically

00:16:46.079 --> 00:16:53.680
broken i don't know you can frame that however you want um but

00:16:51.920 --> 00:16:58.160
yeah so it says it's true that AMD didn't actually reveal the details of

00:16:55.519 --> 00:17:02.160
the flaw before the embargo was up but one of the company's developers came

00:17:00.160 --> 00:17:06.400
very close and close enough to infer what was actually going on

00:17:04.480 --> 00:17:11.520
an AMD developer contributed a Linux patch that excluded AMD chips from the

00:17:08.720 --> 00:17:16.160
meltdown mitigation in the note with the patch the developer wrote the AMD micro

00:17:13.839 --> 00:17:20.240
architecture does not allow memory references including speculative

00:17:17.839 --> 00:17:24.959
references that access higher privileged data when running in a lesser privileged

00:17:22.480 --> 00:17:29.280
mode when that access would result in a page fault so with that information

00:17:27.280 --> 00:17:34.400
knowing that people are writing code and it's extremely

00:17:30.799 --> 00:17:36.320
important having that basically is like

00:17:34.400 --> 00:17:39.280
we are not vulnerable to this and knowing that people are working on

00:17:37.600 --> 00:17:42.799
something very major and he's like excluding themselves from you can kind

00:17:40.960 --> 00:17:47.840
of figure out what's going on um but then the guy kind of got uh

00:17:45.760 --> 00:17:51.600
murked by a but wait there's another there's more

00:17:49.600 --> 00:17:56.080
yeah so there's always two this is where the politics part comes in because and

00:17:53.840 --> 00:17:59.520
okay this is where it gets confusing too

00:17:57.440 --> 00:18:03.840
because i have also heard that there was stuff at google that was

00:18:01.600 --> 00:18:08.080
leaked there's also been some emails that have been leaked there's been tons

00:18:05.760 --> 00:18:12.480
of different stuff i'm not entirely sure which spark was lit first

00:18:10.559 --> 00:18:16.960
this is what i read in the arts technica article there's other stuff that i've

00:18:14.160 --> 00:18:21.600
read who knows anyway it got exposed to the public at some point

00:18:20.000 --> 00:18:26.640
and from there people started freaking the hell out and that was mostly based

00:18:24.799 --> 00:18:30.799
around meltdown that's where we got most of our

00:18:27.919 --> 00:18:33.840
information about meltdown which AMD is essentially

00:18:32.000 --> 00:18:36.720
as of right now as far as i know as far as i've seen published everywhere

00:18:35.200 --> 00:18:40.240
they're excluded from that they're fine with meltdown and that's why there's a

00:18:38.400 --> 00:18:44.799
bunch of confusion even when you google this because there's a timeline here

00:18:41.919 --> 00:18:48.720
where the first part of the media wave was everyone responding to meltdown and

00:18:46.960 --> 00:18:53.280
saying like yeah you're going to read articles that say AMD is not affected

00:18:50.559 --> 00:18:58.080
it'll say that in bold um but it depends when that was written yeah like the the

00:18:55.200 --> 00:19:00.720
the register article which exposed a lot of this stuff and really started

00:18:59.679 --> 00:19:04.720
exploding things like i was saying earlier specifically says Intel CPU

00:19:03.360 --> 00:19:10.799
design flaw um then there's another one by the

00:19:07.280 --> 00:19:12.640
enquirer that says Intel ARM and AMD all

00:19:10.799 --> 00:19:17.200
affected by meltdown and spectre security bypassing CPU design flaw in

00:19:15.280 --> 00:19:20.880
the freaking title so who knows because that one says that AMD is affected by

00:19:19.039 --> 00:19:23.520
meltdown but then almost everything else is saying that AMD isn't affected by

00:19:22.400 --> 00:19:30.000
meltdown i'm kind of going with the isn't side of things but then this is where it gets

00:19:26.880 --> 00:19:32.559
political because AMD goes hahaha we're

00:19:30.000 --> 00:19:38.480
not affected where everything's fine and then Intel releases super vague

00:19:35.600 --> 00:19:43.520
really confusing details like uh one of my favorite lines it's it's in the rs

00:19:41.039 --> 00:19:48.400
article um the company's initial statement produced

00:19:45.760 --> 00:19:53.520
on wednesday says for example these exploits do not

00:19:51.360 --> 00:19:55.840
have the potential to corrupt modify or delete data

00:19:54.799 --> 00:20:01.360
um which is great because that is completely not the point and no one

00:19:58.960 --> 00:20:05.440
claimed that it did any of those things that's like there's another cnbc article

00:20:03.360 --> 00:20:10.000
uh someone in the forum linked where it's like

00:20:06.400 --> 00:20:10.000
this doesn't affect NVIDIA

00:20:12.400 --> 00:20:18.240
but it's just a relevant title for all those or AMD graphics like all the

00:20:16.720 --> 00:20:23.919
non-techie people who just bought NVIDIA's stock because it was going gangbusters this year yeah they're like

00:20:21.360 --> 00:20:28.159
thank god computer stuff we're safe

00:20:25.679 --> 00:20:30.559
yeah so it's it's it's confusing for a lot of people again i would highly

00:20:29.360 --> 00:20:36.159
recommend that you read these articles but we'll do our best to go through stuff but anyways that's where it

00:20:33.919 --> 00:20:39.919
started getting political because AMD is trying to sit over here and be like yes

00:20:37.600 --> 00:20:44.000
it's not us and then Intel's responding to that by being like uh confusing

00:20:41.919 --> 00:20:51.280
statements and then i like that AMD dance you did yeah

00:20:48.640 --> 00:20:55.919
but then spectre comes out of nowhere and now it's everybody everybody's

00:20:53.679 --> 00:21:00.320
included everyone who uses speculative processing

00:20:57.120 --> 00:21:02.880
not even just ARM Intel and AMD which is

00:21:00.320 --> 00:21:07.120
all the ones we largely know about but like basically every chipmaker that uses

00:21:04.960 --> 00:21:09.590
speculative processing you're screwed lock up your daughters and shoot your

00:21:08.720 --> 00:21:11.840
sons

00:21:11.840 --> 00:21:18.960
that was a grand tough dollar reference yes yeah uh so i want to talk about what

00:21:16.720 --> 00:21:24.000
how how affected is the average person here what can they do about it because

00:21:20.640 --> 00:21:25.919
i've i have heard slash read that

00:21:24.000 --> 00:21:30.240
even though the vulnerability does affect all these chips that we all have

00:21:28.480 --> 00:21:33.360
this isn't something that you can really exploit willy-nilly does it take quite a

00:21:32.080 --> 00:21:39.440
bit of work to as far as i know it takes quite a bit of work most random people are not going to

00:21:37.200 --> 00:21:43.280
be targets for this as far as i know again this is really early especially

00:21:41.360 --> 00:21:46.960
right now and i'm juggling a lot of different conflicting information but

00:21:45.280 --> 00:21:50.640
especially if right you're adept at exploiting this right now you're going

00:21:48.320 --> 00:21:58.400
to go for the the highest value juicy targets not not for um

00:21:54.400 --> 00:21:59.919
bob schwarmez's battlefield 4 gaming pc

00:21:58.400 --> 00:22:04.400
i just came up with that name i like it though it's pretty sweet does that make

00:22:02.159 --> 00:22:08.799
that a gamer he's got a restaurant um oh yeah yeah oh i just touched shawarmas

00:22:07.360 --> 00:22:12.480
okay oh nice he gets that all the time yeah

00:22:10.559 --> 00:22:16.799
that makes sense yeah anyways yeah like it's it's very unlikely that uh

00:22:14.880 --> 00:22:20.720
your personal pc is gonna get attacked it's very unlikely to tie back to that

00:22:19.280 --> 00:22:24.559
dude calling someone an idiot in the twitch chat that your iphone is going to

00:22:22.640 --> 00:22:28.559
get attacked but essentially all these processors are susceptible to spectre

00:22:26.720 --> 00:22:32.240
there are updates that are coming certain programs are going to have to be

00:22:29.919 --> 00:22:36.400
recompiled or modified those things are going to happen especially for major

00:22:34.480 --> 00:22:40.000
mainline programs so we can look forward to a lot of blue

00:22:37.840 --> 00:22:45.440
screens at ces you look forward to a lot of updates um

00:22:42.960 --> 00:22:47.760
Windows updates program updates lots of different things are going to be

00:22:46.559 --> 00:22:54.320
updating this is where we're going to tie into what different companies have done

00:22:52.000 --> 00:22:57.200
ARM has released a really really nice white paper detailing how it affects

00:22:55.919 --> 00:23:01.360
their processors and all this kind of stuff which is going to be uninteresting

00:22:59.280 --> 00:23:04.480
for almost everybody in this audience because those are

00:23:02.720 --> 00:23:08.720
for the most point not consumer level processors and what i mean by that is

00:23:06.480 --> 00:23:12.080
not consumer serviceable processors they're things like in your phone or in

00:23:10.320 --> 00:23:17.679
your iot devices or all these other kind of things i doubt that you're

00:23:14.320 --> 00:23:19.200
running a desktop setup that has an ARM

00:23:17.679 --> 00:23:22.799
processor but you know you might be doing something weird

00:23:21.200 --> 00:23:27.760
it's possible you could plug in your phone if it's possible it exists yeah it's out

00:23:26.000 --> 00:23:32.320
there you could plug in your phone and use like external keyboards and do weird stuff

00:23:30.799 --> 00:23:36.640
yeah it's it's i doubt anyone watching has that set up

00:23:34.320 --> 00:23:41.600
but it is possible anyways uh are you ready for this aspect

00:23:39.360 --> 00:23:48.960
oh let's jump let's jump there in a quick moment so so yeah apple is already

00:23:45.120 --> 00:23:50.559
releasing updates for iOS macOS and

00:23:48.960 --> 00:23:55.679
dealing with some other crazy things microsoft is going ham the microsoft

00:23:52.720 --> 00:23:59.840
section of this article is super long one thing that i really like that they

00:23:57.280 --> 00:24:03.520
did microsoft has already published a powershell script that describes the

00:24:01.760 --> 00:24:08.320
current system protection against meltdown inspector on your computer um

00:24:06.400 --> 00:24:12.320
so if you're into powershell if you're comfortable with that

00:24:09.679 --> 00:24:15.440
check out the rs article it's linked in the forum link in the description if

00:24:13.919 --> 00:24:18.880
you're watching this on archive if not i've already posted in twitch chat there

00:24:17.200 --> 00:24:22.000
you go and you can check out what's going on on

00:24:20.320 --> 00:24:28.880
your own system they're releasing updates for edge internet explorer

00:24:25.200 --> 00:24:30.840
uh Windows itself uh mozilla is trying

00:24:28.880 --> 00:24:33.760
to copy some of them

00:24:32.400 --> 00:24:39.200
yeah whatever they're trying to copy some of their approaches to different things there's

00:24:36.799 --> 00:24:43.679
tons of stuff going on microsoft uh has already updated its azure cloud

00:24:41.279 --> 00:24:47.279
computing platform which is awesome i would expect that google was updated

00:24:45.279 --> 00:24:50.320
before we even heard about this oh they've been on top of this for a

00:24:48.720 --> 00:24:54.559
long time yeah amazon has already started rolling out

00:24:53.279 --> 00:24:59.600
patches for ec2 in terms of meltdown

00:24:58.000 --> 00:25:05.039
again spectre is going to be weird for all this kind of stuff i'm mostly talking about meltdown uh google's two

00:25:03.039 --> 00:25:08.880
consumer facing operating systems Android and chrome os both depend on

00:25:07.120 --> 00:25:13.360
Linux kernels and that's already been being worked on as i mentioned earlier

00:25:10.240 --> 00:25:16.400
the AMD guy working on Linux kernels um

00:25:13.360 --> 00:25:18.880
and most and but most Android hardware

00:25:16.400 --> 00:25:22.400
and most an Android is a weird thing to think about because

00:25:20.880 --> 00:25:28.960
uh there's a lot of really low end Android devices most people don't think about um but

00:25:25.679 --> 00:25:31.679
isn't susceptible to meltdown yet

00:25:28.960 --> 00:25:37.120
but that's going to change probably anyways right now it's a huge mess

00:25:34.880 --> 00:25:41.039
everything's a mess it's mostly a mess because it was leaked

00:25:39.279 --> 00:25:45.120
and when it was leaked everyone had to scramble super hard to solve it instead

00:25:43.840 --> 00:25:48.480
of trying to take their time and be very coordinated

00:25:47.120 --> 00:25:53.600
about everything and very behind the scenes and then one day you just get a Windows update you don't even know

00:25:50.960 --> 00:25:57.520
anything was ever wrong um no instead of that everyone's freaking the hell out

00:25:55.120 --> 00:26:03.919
and trying to solve all this at once and speaking of how this was very behind

00:26:00.080 --> 00:26:06.000
doors for a while huh uh Intel ceo sold

00:26:03.919 --> 00:26:09.360
what is it like 49 or 24 million 24 million dollars worth of

00:26:08.400 --> 00:26:14.559
stock right so he knew about this google told Intel about this in the

00:26:13.679 --> 00:26:19.120
summer uh so the ceo knew

00:26:17.200 --> 00:26:23.039
that they were going to have a fiasco once the public found out about this

00:26:21.200 --> 00:26:26.880
he knew the gravity of the situation and then before

00:26:24.640 --> 00:26:30.320
this became public he sold 24 million dollars worth of his stock in the

00:26:28.880 --> 00:26:35.520
company which was a major i think a majority of his stock

00:26:32.640 --> 00:26:39.120
so that doesn't look very good no um

00:26:36.799 --> 00:26:41.679
but but i think this is actually kind of clickbaity

00:26:40.320 --> 00:26:45.440
because Intel says that the stock sale was

00:26:43.440 --> 00:26:51.200
unrelated to the vulnerability and came as part of a planned divestiture program

00:26:48.320 --> 00:26:54.640
and those things are things they exist um the other thing is Intel stock price

00:26:53.200 --> 00:26:59.360
has only fallen about two bucks since

00:26:57.039 --> 00:27:03.279
this fiasco kind of hit the public so that's it's not like it tanked and this

00:27:01.200 --> 00:27:08.000
is like a huge insider trading thing granted two dollars like with the number

00:27:05.360 --> 00:27:11.520
of shares outstanding it's still like millions of dollars

00:27:09.360 --> 00:27:14.799
coming and going mostly going from Intel stock right now so it is

00:27:12.960 --> 00:27:19.679
it is huge but i think this is a little clickbaity

00:27:16.799 --> 00:27:23.440
it's it it really depends um i'm sure there's going to be legal oversight into

00:27:21.440 --> 00:27:28.720
this because like man if if

00:27:26.159 --> 00:27:32.640
if that was planned without insider trading and this was

00:27:30.320 --> 00:27:36.799
just routine whatever the timing on that yeah

00:27:34.720 --> 00:27:40.799
like you couldn't be worse in the last huge amount of years it could could not

00:27:38.960 --> 00:27:45.840
be worse timing so it could be an unfortunate coincidence i think people

00:27:42.720 --> 00:27:47.919
claiming that it's insider

00:27:45.840 --> 00:27:52.080
are you can't really hammer on them too hard

00:27:50.000 --> 00:27:57.039
because there's a lot of things a lot of red lights going off in terms of timing

00:27:54.720 --> 00:28:00.480
in terms of how much it was 24 million dollars is quite a bit of money i also

00:27:58.640 --> 00:28:03.360
read this is why this is so confusing i read a number that was over 40.

00:28:02.559 --> 00:28:09.840
um but like i'm not even saying it's right because i just read that like well

00:28:07.200 --> 00:28:12.880
actually if this program uh it could be in multiple phases so that was the

00:28:11.520 --> 00:28:16.880
number that went out recently in december so it could be over 40 like

00:28:15.039 --> 00:28:23.279
since summer since he's known maybe sure yeah i don't know um

00:28:20.080 --> 00:28:25.360
yeah it's a mess but

00:28:23.279 --> 00:28:29.520
potentially looking into his legal ramifications for what that might

00:28:28.240 --> 00:28:33.440
potentially end up being in terms of insider trading or not and i'm sure if

00:28:31.679 --> 00:28:37.360
it was planned he has tons of documentation for it and if it goes back

00:28:35.600 --> 00:28:41.919
before this bug was released to them he's gonna be fine um if it doesn't

00:28:40.880 --> 00:28:46.320
that's gonna that's gonna be a little bit if it was planned and it is fine you're probably

00:28:45.039 --> 00:28:50.960
not gonna hear about it because no one's gonna click on that article yeah it's just it's gonna be boring it's not a

00:28:49.360 --> 00:28:55.120
story it'll be too boring to bring up on wayne's show you know it's not boring

00:28:53.520 --> 00:28:59.840
until getting sued over this vulnerability super hard yeah there are

00:28:57.600 --> 00:29:05.120
multiple lawsuits uh hold on one quick second before we go forward this article

00:29:02.080 --> 00:29:08.799
was posted by sc2 mitch on the forum the

00:29:05.120 --> 00:29:12.080
previous one was found by james uh and

00:29:08.799 --> 00:29:14.720
the big whole entire thread the source

00:29:12.080 --> 00:29:17.760
that we have for that is doctor who 1975 on the forum he's getting the credit but

00:29:16.159 --> 00:29:20.720
there actually are like six i'm sure there's a lot and i'm sure there's going

00:29:19.279 --> 00:29:25.039
to continue to be more thank you to everybody who's been posting about this stuff and that's not to say the

00:29:23.520 --> 00:29:29.360
duplicate threads there's just so many facts there's there's and and there's

00:29:27.520 --> 00:29:33.200
conflicting ones and there's ones that grow on other ones and it's a nightmare

00:29:31.440 --> 00:29:37.039
our forum is a happening place if you don't go there you should yeah it's cute

00:29:35.440 --> 00:29:39.600
yeah the people who are suing Intel do you

00:29:38.799 --> 00:29:44.880
think so here's the grounds of at least one of them okay the lawsuit this lawsuit

00:29:43.440 --> 00:29:49.520
particularly i think it was maybe the first one garcia v Intel corporation

00:29:46.960 --> 00:29:54.000
filed on wednesday january 3rd the suits plaintiffs plaintiffs allege

00:29:51.840 --> 00:29:58.480
that the computer chips containing the fatal security flaw well there's a lot

00:29:56.000 --> 00:30:02.240
of f's here they violate california and tennessee law specifically the

00:30:00.399 --> 00:30:06.240
plaintiff's spring claims for breach of warranty and violations of consumer

00:30:04.240 --> 00:30:10.399
protection statutes alleging that Intel's selling of computer chips with

00:30:08.159 --> 00:30:14.399
this fatal security flaw misled consumers about the performance and

00:30:12.000 --> 00:30:20.080
reliability of the computers operating with this hardware

00:30:17.200 --> 00:30:22.799
um my first thought like they have a quote here saying that they look forward

00:30:21.440 --> 00:30:29.440
to holding Intel responsible for exposing millions of americans to unnecessary data and security risks or

00:30:26.880 --> 00:30:32.480
data risks data security risk um that sounds noble it's like yeah

00:30:31.279 --> 00:30:36.799
stick them break them over the coals like someone's fighting a good fight for us but my first thought actually when i

00:30:35.200 --> 00:30:41.360
read this was like i think these people might be those like

00:30:39.120 --> 00:30:45.840
professional sewers yeah who are like because there's a very second i can see

00:30:43.200 --> 00:30:50.799
there's also there's also constantly security issues with this type of stuff

00:30:48.159 --> 00:30:54.240
it's just usually handled it's usually much smaller

00:30:52.799 --> 00:30:59.200
and it's usually handled much more quietly

00:30:55.919 --> 00:31:01.440
um like like if you could sue microsoft

00:30:59.200 --> 00:31:06.320
for having a security vulnerability in Windows microsoft would be gone it's

00:31:04.320 --> 00:31:10.399
just it's obviously because of the scale yeah the scale is why this is a big

00:31:07.760 --> 00:31:13.520
headline and a big deal skills and and suitable

00:31:11.440 --> 00:31:17.760
yeah someone said it's usually handled by the

00:31:14.960 --> 00:31:22.480
nsa i have no freaking idea someone said in the chat uh he sold them shortly

00:31:20.000 --> 00:31:26.559
before ime vulnerabilities became public in november uh yeah that's not what we

00:31:25.200 --> 00:31:31.279
were talking about though if it was planned

00:31:28.240 --> 00:31:33.760
far beforehand if if if he comes in one

00:31:31.279 --> 00:31:37.200
day and board of director guys and his or his financial advisors or whatever

00:31:35.679 --> 00:31:41.440
the heck i don't know i'm not into this kind of money are like hey we should

00:31:39.360 --> 00:31:44.799
downscale our stock whatever that thing that you said um it's not going to

00:31:43.440 --> 00:31:48.559
happen the next day it would be planned on paper for a while

00:31:46.880 --> 00:31:53.360
it's he's moving a huge amount of stock it's going to happen over time um

00:31:51.600 --> 00:31:56.480
yeah anyways that's about it for that

00:31:54.960 --> 00:32:00.559
that's we did it i hope we did it

00:31:58.159 --> 00:32:03.760
again there is a huge amount of information

00:32:02.080 --> 00:32:08.159
if we actually wanted to go over every single little tiny bit of it would take

00:32:05.120 --> 00:32:10.240
us the entire show and more uh if you do

00:32:08.159 --> 00:32:13.760
want to know more and if you're into computers and hardware this is super

00:32:12.000 --> 00:32:18.480
interesting i would highly recommend you read more come up with your own opinions

00:32:15.519 --> 00:32:22.399
about it all that kind of stuff um check out the links that will be in the

00:32:20.000 --> 00:32:26.720
forum uh doc thing that i'll be posting that'll

00:32:24.080 --> 00:32:32.559
be in the description on youtube and um yeah good idea on youtube and soundcloud

00:32:29.919 --> 00:32:35.919
and there we go that's it that's the giant

00:32:33.519 --> 00:32:41.279
not just Intel definitely everybody but mostly Intel and people are trying to

00:32:38.880 --> 00:32:44.880
obscure information and some information is out there and crazy stuff and no

00:32:43.039 --> 00:32:48.399
official information completely entirely yet put your head in the sand what can

00:32:46.559 --> 00:32:53.600
you do about it really it's probably not going to affect you update Windows live

00:32:50.960 --> 00:32:58.159
your life yeah am i right for the most part yeah there is a loud

00:32:55.919 --> 00:33:00.880
minority who's going go you're not you're not

00:32:59.200 --> 00:33:05.919
insane it's it's it's definitely affecting some people it's affecting

00:33:02.320 --> 00:33:07.519
Floatplane um and it's it's going to

00:33:05.919 --> 00:33:10.960
affect other kind of businesses

00:33:09.200 --> 00:33:14.640
as you've seen google and amazon and microsoft are all tweaking out right now

00:33:13.679 --> 00:33:18.880
um yeah anyways and now a word from our

00:33:16.960 --> 00:33:25.840
sponsors yeah give me yes book

00:33:21.519 --> 00:33:25.840
all right why is there no lower third

00:33:28.559 --> 00:33:34.720
all right well there just isn't one how's it going um freshbooks is the

00:33:32.720 --> 00:33:38.559
small business accounting software that you need if you want to do awesome stuff

00:33:37.679 --> 00:33:43.919
like uh like what run a vps hosting company hmm

00:33:43.120 --> 00:33:49.200
or or uh run two vps hosting companies or

00:33:47.120 --> 00:33:54.240
run a dog grooming shop or a plumbing company any any like i know a lot of

00:33:51.440 --> 00:33:58.799
people in the audience run small scale uh computer hardware technician service

00:33:57.120 --> 00:34:03.279
companies i know i did when i was younger going around doing small scale

00:34:00.960 --> 00:34:07.840
i.t work for some businesses and building computers for people and doing

00:34:05.279 --> 00:34:10.480
it stuff around as much as i could while i was going to school because the hours

00:34:09.040 --> 00:34:13.520
were all nice and flexible because you're working for yourself and you can

00:34:12.480 --> 00:34:17.839
often just remote into machines and fix them from home and all that kind of stuff

00:34:16.079 --> 00:34:22.079
it's great and you can manage the invoices and finances that are a

00:34:20.159 --> 00:34:26.159
nightmare i can tell you from personal experience are a nightmare if not

00:34:24.879 --> 00:34:30.800
if you don't have fresh books you can generate invoices in an extremely short

00:34:28.720 --> 00:34:34.240
period of time you can check if those people have seen the invoice this is all

00:34:32.960 --> 00:34:38.079
super helpful because you don't want to spend all your time while you could be

00:34:36.000 --> 00:34:42.560
studying or working or doing other more productive things uh chasing people down

00:34:40.480 --> 00:34:46.000
for invoices it does it for you which is great you can set up online payments

00:34:44.560 --> 00:34:52.560
with just a couple clicks which is awesome and you can get paid up to four days faster which is super cool

00:34:50.159 --> 00:34:57.119
so yeah stop the guessing games get paid for an unrestricted 30-day free trial go

00:34:54.800 --> 00:35:01.200
to freshbooks.com tech tips and enter Linus tech tips in the how did you hear

00:34:58.560 --> 00:35:04.240
about a section freshbooks is great and moving on

00:35:03.040 --> 00:35:09.920
if you are doing what i just said running a

00:35:06.880 --> 00:35:11.599
small scale it business thing you might

00:35:09.920 --> 00:35:14.960
want to bring a laptop somewhere and have that hooked up and be able to use

00:35:13.520 --> 00:35:19.359
your laptop and the other computer all at once or there's tons of other use

00:35:17.280 --> 00:35:22.720
cases for this say you go to work and when you're at work you work on a laptop

00:35:21.040 --> 00:35:25.839
i know i was at the twitch offices we're on twitch right now is that the twitch

00:35:24.160 --> 00:35:29.359
offices not that long ago a lot of people worked on laptops there you'd be

00:35:27.760 --> 00:35:32.480
able to pick up your laptop from work where it's connected into the monitors

00:35:30.800 --> 00:35:38.160
and all nicely hooked up bring it home put that on a dock or something like

00:35:35.839 --> 00:35:41.920
just i have a little laptop holding ARM plug it into power or whatever and over

00:35:40.079 --> 00:35:45.280
the network your keyboard or mouse will connect from your main computer to your

00:35:43.760 --> 00:35:48.400
laptop what are you talking about you can drag and drop documents what

00:35:47.200 --> 00:35:54.880
business are you even talking about synergy you didn't say that yet i did synergy

00:35:52.240 --> 00:35:58.880
two synergy two the sequel yeah this is synergy two not synergy one

00:35:57.440 --> 00:36:03.280
um synergy two instead of just having all

00:36:01.200 --> 00:36:06.720
the awesome stuff that synergy one has and it has as well with it like mouse

00:36:05.359 --> 00:36:10.800
and keyboard going from computer to computer uh like being able to drag and

00:36:08.640 --> 00:36:13.440
drop files it working over the network so you don't have to plug them into usb

00:36:12.320 --> 00:36:18.079
or anything you just have to be on the same network it also has stuff like

00:36:15.520 --> 00:36:21.680
cloud bridge so it can work across vpns and tricky home networks if you have a

00:36:19.599 --> 00:36:25.440
weird setup and if you get the pro version you get to access other cool

00:36:23.520 --> 00:36:30.880
features like clipboard sharing drag and drop files copy and pasting lock screen

00:36:28.800 --> 00:36:35.680
sync and tons more which is great it has ssl encryption which is nice you're not

00:36:33.280 --> 00:36:39.920
going to get jacked into all the time share anywhere automatically control any

00:36:37.520 --> 00:36:43.760
computer without reconfiguring which is really nice one thing that synergy 2 is

00:36:41.760 --> 00:36:47.200
apparently a lot better at is detecting computers

00:36:45.119 --> 00:36:51.440
which is nice because synergy was a little bit harder to set up before oh it

00:36:48.880 --> 00:36:58.400
should be easier now yeah so you can go to um this link right here

00:36:54.880 --> 00:37:00.720
seamless dot com slash synergy wan three

00:36:58.400 --> 00:37:04.560
specifically that three there is important

00:37:02.000 --> 00:37:09.680
and save 50 when you do that oh wow really oh yeah

00:37:06.880 --> 00:37:14.240
not bad say 50 okay um and then last but not least we have

00:37:12.240 --> 00:37:18.640
squarespace we've had squarespace for a long time they have 24 7 live chat and

00:37:16.560 --> 00:37:23.760
email support so if you're running your little it business thing you have

00:37:21.359 --> 00:37:27.119
synergy you have freshbooks all that is running nicely and you have your little

00:37:25.200 --> 00:37:32.079
website advertising your services and you have troubles with your site you can

00:37:29.760 --> 00:37:36.880
call their i t support or you can uh you can live chat or email their

00:37:34.160 --> 00:37:39.680
live support um and it's only 12 bucks a month you get a free domain if you

00:37:38.160 --> 00:37:43.040
subscribe for a year which is cool because domains you you usually rent

00:37:41.599 --> 00:37:48.000
them for a year anyways so if you want the domain for a year you subscribe for a year they come together it's all nice

00:37:46.079 --> 00:37:52.640
they have a commerce module so you can use their free online store they have

00:37:50.240 --> 00:37:56.800
cover pages so you can have one nice beautiful page if you want that set up

00:37:55.359 --> 00:38:02.160
or you can even if you want to have some type of blog or something like that you can publish content in apple news format

00:38:00.480 --> 00:38:09.680
directly from their blog module which is cool and if you go to squarespace.com forward

00:38:06.320 --> 00:38:12.160
slash LTT and use offer code LTT you get

00:38:09.680 --> 00:38:16.400
10 off your first purchase so there you go someone in the twitch

00:38:14.079 --> 00:38:25.200
chat was scrolled by it was like what are those glasses these these you fool

00:38:21.280 --> 00:38:26.640
you don't even know your own folly

00:38:25.200 --> 00:38:30.560
oh dear all right what do you want to talk about now uh

00:38:28.640 --> 00:38:36.400
some fun stuff here yeah let's go forward pick one i believe oh

00:38:33.599 --> 00:38:41.920
that's boring yeah nah okay screw it if you have an hp if you have an hp laptop

00:38:39.760 --> 00:38:46.560
um this is me not talking about this one it might be getting recalled right now

00:38:43.280 --> 00:38:47.839
there's a big list of pro books and zen

00:38:46.560 --> 00:38:52.720
books that are getting recalled because of the battery uh

00:38:50.000 --> 00:38:56.720
you can get a free battery fix from hp if you send it back in don't bring it to

00:38:54.400 --> 00:38:59.599
a third party fixer guy because these aren't actually supposed to be user

00:38:58.079 --> 00:39:05.760
fixable batteries so give it a google look it up see if your

00:39:03.119 --> 00:39:09.280
hp book or notebook is one of the effective ones

00:39:07.280 --> 00:39:12.160
and get that puppy fix it and no reason to bring it to a third party anyways

00:39:10.880 --> 00:39:15.760
because this is a actual recall that hp is asking you to

00:39:14.560 --> 00:39:18.720
contact them about so they should be handling everything yeah yeah so i

00:39:17.599 --> 00:39:23.359
wouldn't i wouldn't worry we don't want to have a note 7s situation here just

00:39:20.720 --> 00:39:26.720
yeah don't even send her in yeah yeah that's probably a good idea this one

00:39:24.720 --> 00:39:32.079
next spotify sure

00:39:28.640 --> 00:39:34.079
all right so spotify um they're possibly

00:39:32.079 --> 00:39:38.480
on the hook for a 1.6 billion dollar copyright

00:39:35.920 --> 00:39:42.720
that's a lot of money why you might ask because they've been

00:39:40.320 --> 00:39:46.240
streaming songs without giving money or getting consent from the owners of those

00:39:44.720 --> 00:39:50.720
songs yeah pretty much uh

00:39:48.160 --> 00:39:54.960
so it's what's the name of the company music publishing yeah they've got tom

00:39:52.800 --> 00:40:01.200
petty neil young and rage against the machines tom morello and many more so

00:39:58.079 --> 00:40:03.920
that's some pretty major names

00:40:01.200 --> 00:40:08.240
last summer spotify faced a suggested 43 million settlement which is still yet to

00:40:06.079 --> 00:40:12.640
be approved in court and they also agreed to a 30 million

00:40:10.400 --> 00:40:17.839
dollar settlement with national music publishers association and mpa for

00:40:15.440 --> 00:40:20.320
unpaid royalties in 2016. so they're just getting

00:40:19.040 --> 00:40:27.440
stomped on you got to license that content bro yeah speaking of music streaming rumor rumor

00:40:25.040 --> 00:40:31.440
has it that youtube are grown youtube is going to launch a

00:40:29.359 --> 00:40:35.440
music streaming surface why you might ask since google play services already

00:40:33.200 --> 00:40:39.839
heard google play music already exists we don't

00:40:36.839 --> 00:40:41.359
know this would actually be the uh

00:40:39.839 --> 00:40:45.760
alphabet the parent company of google and youtube this will be their third

00:40:43.200 --> 00:40:49.119
attempt at at a music service actually um because google play music launched in

00:40:47.680 --> 00:40:53.520
2011 and to my estimation is doing just fine

00:40:51.599 --> 00:40:56.400
um but on top of that i use it they had something called uh yeah i just switched

00:40:54.960 --> 00:40:59.839
to it from spotify actually and i am digging that algorithm that's pretty

00:40:58.000 --> 00:41:02.960
good of course the algorithm's off yeah of course why would you think that

00:41:01.280 --> 00:41:06.319
someone like spotify could beat google who owns youtube youtube by the way

00:41:04.560 --> 00:41:10.480
being the second largest search engine in the world that's bigger than bing

00:41:07.599 --> 00:41:15.440
youtube search engines is huge their their algorithm for what to play next

00:41:13.200 --> 00:41:18.560
keeps you on youtube for hours doing not what you noticed

00:41:16.720 --> 00:41:22.000
yeah so obviously their their music algorithm is great you can search a song

00:41:20.880 --> 00:41:26.720
and it'll just go for the rest of the night it's awesome oh someone said google play music streaming service has

00:41:24.960 --> 00:41:30.160
not supported my company that pisses me off a huge amount but youtube red oh my

00:41:28.800 --> 00:41:36.720
goodness i want to watch i think it's called minefield yeah vsauce

00:41:34.640 --> 00:41:39.839
it's on youtube red i can't do the thing yeah they want you that's the teaser

00:41:38.319 --> 00:41:42.880
they give you one episode to watch and then you got a youtube reddit i think i

00:41:41.839 --> 00:41:46.960
might like subscribe temporarily while we're in vegas

00:41:45.440 --> 00:41:51.760
and just try to like binge the engine you don't have time yeah

00:41:49.920 --> 00:41:56.000
do you if you have time to watch that then that gives me uh

00:41:53.520 --> 00:41:58.480
no i don't um let's go back every time that i go to ces i'm like oh i'm gonna

00:41:57.440 --> 00:42:03.119
do all these things i'm gonna bring my personal camera i'm gonna take cool photos i'm gonna do all this kind of

00:42:01.119 --> 00:42:07.280
cool extra stuff on the side and then it's like nope you work from like eight

00:42:05.839 --> 00:42:11.599
to like three and then you sleep for a few hours

00:42:10.079 --> 00:42:15.520
and then you get back up and keep going i'm really hoping just to eat meals

00:42:13.440 --> 00:42:18.800
that's all i want i want to go to vegas and actually be able to hit at least one

00:42:16.800 --> 00:42:21.839
buffet you'll probably average one or two a day

00:42:19.920 --> 00:42:25.839
yeah okay meals yeah yeah yeah i don't want to just have to eat that sparrow

00:42:23.760 --> 00:42:29.520
pizza that's in the convention center the whole time yeah there is okay

00:42:27.920 --> 00:42:33.520
there's some hidden spots in the convention center on floor two teach me

00:42:31.440 --> 00:42:36.880
your ways yeah don't tell them don't tell everyone here they won't be hidden

00:42:35.599 --> 00:42:43.359
that's a good call so back to the chronology after google play came out in 2011 a thing that i had never heard of

00:42:40.560 --> 00:42:48.880
called youtube music key came along in 2014 which gave subscribers ad-free

00:42:45.920 --> 00:42:51.599
music videos which is awesome because obviously a ton of awesome music and

00:42:50.480 --> 00:42:57.280
remixes and everything that are on youtube but you hit play you try to put that on a party and then ads interrupt

00:42:54.960 --> 00:43:01.200
it and you look like a dork um but then youtube

00:42:59.520 --> 00:43:05.920
music key kind of just turned into youtube red

00:43:02.960 --> 00:43:10.839
in 2016 yeah which expands to letting you watch any video without advertising

00:43:08.400 --> 00:43:16.560
and now it's just kind of like its own thing so so they keep just changing

00:43:14.240 --> 00:43:21.200
stuff in super weird ways this uh service this alleged rumored

00:43:19.119 --> 00:43:25.119
service is internally referred to as remix

00:43:22.640 --> 00:43:27.520
um okay it's gonna have on-demand elements uh

00:43:26.400 --> 00:43:32.800
like um a regular like a spotify but it's also gonna have some youtube elements maybe

00:43:30.800 --> 00:43:35.920
like some video clips maybe some lyrics on screen that'd be nice so you can

00:43:34.319 --> 00:43:40.800
already do youtube music videos through google play

00:43:38.400 --> 00:43:45.200
music but all right all right i i don't know i think uh part of this might come

00:43:42.480 --> 00:43:48.160
from the supply side um apparently some of the

00:43:46.560 --> 00:43:50.560
creators whose music is getting listened to

00:43:49.599 --> 00:43:54.560
through youtube they don't feel like they're getting compensated as as fairly

00:43:52.880 --> 00:43:57.839
as they would be on dedicated music streaming services like google play

00:43:55.920 --> 00:44:02.240
music or on spotify so it might be like a money thing

00:44:00.240 --> 00:44:04.319
okay they put it on there but yeah okay

00:44:03.520 --> 00:44:06.720
yeah i guess

00:44:07.119 --> 00:44:13.040
you give him an inch i i don't know i don't know yeah um

00:44:11.359 --> 00:44:17.280
that's for deploying this thing uh warner music group is already on board

00:44:15.280 --> 00:44:20.720
they're one of the big three yeah in the music business and

00:44:18.800 --> 00:44:24.720
the other two of the three already in talks with youtube that includes sony

00:44:22.960 --> 00:44:30.640
music entertainment and universal music group uh they're also talking to merlin

00:44:27.200 --> 00:44:32.319
a consortium consortium of independent

00:44:30.640 --> 00:44:36.400
labels so hopefully they'll have a good spread on content

00:44:34.480 --> 00:44:41.200
yeah i like i don't know it'll probably be

00:44:38.640 --> 00:44:45.200
good i it seems weird because it seems like alphabet is now creating things to

00:44:43.760 --> 00:44:49.040
compete against themselves yeah um this is like a

00:44:47.760 --> 00:44:53.119
hangouts allowed yeah which is so yeah that's a

00:44:51.760 --> 00:44:56.880
good call so maybe it's not that weird for them it's because they're they're so

00:44:55.040 --> 00:45:01.680
federated that they don't talk and they step on each other all the time yeah

00:44:59.599 --> 00:45:06.160
um anyways going back to the google play music thing one of my favorite things

00:45:02.960 --> 00:45:08.079
about it is just how creepy it is

00:45:06.160 --> 00:45:11.520
it'll pull in a lot of data which is unsurprising because it's google so

00:45:09.599 --> 00:45:16.319
it'll like know when you're at the gym yeah yeah you can you can turn on load

00:45:13.680 --> 00:45:20.079
uh locations notifications locations notifications so it's like huh i see

00:45:18.480 --> 00:45:24.000
you're in the border lineup i'm going to play gangster rap to make you suck

00:45:24.640 --> 00:45:29.680
yeah um i don't know it's it's

00:45:28.160 --> 00:45:34.880
it's interesting every once in a while i'll just jump into the different playlists that it recommends for me to

00:45:32.480 --> 00:45:38.800
try to see where it's trying to take me and sometimes you know it'll go off in

00:45:37.280 --> 00:45:42.000
totally a weird direction i'm like i don't like any of this stuff but often

00:45:40.560 --> 00:45:46.640
it's pretty good i've been happy with it because when i i had two problems with

00:45:43.599 --> 00:45:48.319
spotify the first was the discover

00:45:46.640 --> 00:45:52.400
playlist was just totally like stuff i didn't listen to at all

00:45:49.920 --> 00:45:56.480
and the the second was now maybe you can do this on certain

00:45:54.079 --> 00:46:00.480
services with spotify but i usually use this with my tv

00:45:58.079 --> 00:46:04.240
and my google home and what i want to do is i have a song on this on in my head

00:46:02.560 --> 00:46:07.760
and i'm like i want to play this song and then that's all i want to do and

00:46:05.920 --> 00:46:11.680
after that i wanted to just go forever playing related music and google play

00:46:10.160 --> 00:46:15.359
music is wicked at that that's very good at that not only will it play other

00:46:13.440 --> 00:46:18.400
songs that you'll like they might not even be from bands you know of yeah i

00:46:17.200 --> 00:46:22.560
started with a nine inch nails song the other day nine snails die hard

00:46:20.800 --> 00:46:26.079
the next 10 songs were for bands i never heard of i didn't skip a single one

00:46:23.839 --> 00:46:28.960
they're so sweet nice uh i actually really like doing that sometimes yeah

00:46:27.599 --> 00:46:31.760
it's wicked if you try to do this on spotify guess what the second song will

00:46:30.880 --> 00:46:37.599
be the second song will be the same song again because

00:46:35.440 --> 00:46:40.480
instead of playing the song you search for and then a bunch of related songs it

00:46:39.359 --> 00:46:46.319
will play all the search results so it'll be like

00:46:44.319 --> 00:46:50.079
so you try to put on uh so be like that same song or like

00:46:48.079 --> 00:46:54.880
remixed by someone else yeah you try to put on stairway to heaven you get started to heaven then you get live then

00:46:52.640 --> 00:47:00.560
you get cover yeah it's like yes yes spotify this is what i wanted

00:46:58.319 --> 00:47:04.480
no one's ever wanted this i'm gonna hopefully troll at least one

00:47:03.119 --> 00:47:08.400
person okay google play that hipster song with

00:47:06.800 --> 00:47:11.680
the whistling okay so that's in one of their

00:47:10.480 --> 00:47:16.800
you jerk did it work uh no no dang

00:47:15.119 --> 00:47:20.000
oh i should have said with google play music so sometimes it gets confused if

00:47:18.560 --> 00:47:24.960
you don't include that i don't know why but because you can have a different default music player yeah yeah so if you

00:47:23.359 --> 00:47:29.359
have two installed it might have to like ask or whatever but

00:47:26.960 --> 00:47:34.000
you got me it did it yes some people got it okay now let it keep going

00:47:32.400 --> 00:47:38.560
you can even mute it and leave it off on the side or whatever but let it keep

00:47:35.920 --> 00:47:42.720
going it does a pretty good job and it doesn't continue to play hipster whistle

00:47:40.480 --> 00:47:47.760
songs or what do you mean that good job well it continues to play

00:47:45.040 --> 00:47:52.079
hipstery kind of songs but that actually sound kind of similar and fun with the

00:47:50.160 --> 00:47:56.800
same tonality and all these other kind of things it does it does a pretty good

00:47:53.839 --> 00:48:01.760
job i ended up um already cancelled some people are like

00:47:58.640 --> 00:48:03.760
no screw it um someone actually said it

00:48:01.760 --> 00:48:06.880
didn't recognize the voice yeah my yeah i've got that recently someone tried to

00:48:05.040 --> 00:48:10.400
troll me and then google was like that doesn't sound like james yeah my

00:48:08.560 --> 00:48:14.480
girlfriend even trying to impersonate my voice couldn't get into my phone using

00:48:12.480 --> 00:48:18.240
that's not surprising yeah you know i know but it's just it's it's interesting

00:48:16.000 --> 00:48:22.960
it did a pretty good job i would love to hear three devices

00:48:21.440 --> 00:48:27.599
some guys said three devices are playing that song in my house right now when i did the there was a previous WAN Show

00:48:25.920 --> 00:48:31.839
where i did this a similar command with some weird russian song that goes

00:48:29.760 --> 00:48:35.680
yes people people kept tweeting me like man it was it was 1am my whole family is

00:48:34.559 --> 00:48:40.800
awake now yeah it's pretty bad we gotta we put a lockdown on that recently okay

00:48:39.440 --> 00:48:43.680
so we're adapting maybe maybe that was bad you did that on purpose yeah i did

00:48:42.480 --> 00:48:48.000
it's the accidental ones we're looking out for hey there's actually an amazon

00:48:45.599 --> 00:48:51.280
echo uh topic here we can go right into sure

00:48:48.720 --> 00:48:57.760
so this has to do with amazon trying to monetize and

00:48:54.160 --> 00:48:59.760
place ad units into echo devices so

00:48:57.760 --> 00:49:05.200
there's a thread on the forum by man keys who actually pretty much supplied a

00:49:02.559 --> 00:49:09.040
lot of almost all of the threads today thank you man thank you very much

00:49:06.720 --> 00:49:12.640
however i kind of think that you're making your title for this is uh fake

00:49:11.440 --> 00:49:17.280
news because as far as i read it's not the case that

00:49:15.200 --> 00:49:22.240
your amazon echo is going to be reading out ads

00:49:19.359 --> 00:49:24.960
to you that would be so brutal um as far as i've seen i don't think that's

00:49:23.760 --> 00:49:30.000
what they're trying to do but what they are trying to do is

00:49:26.800 --> 00:49:31.440
have brands be like the sponsored search

00:49:30.000 --> 00:49:35.760
results so just like when you google something um if you google new truck

00:49:34.240 --> 00:49:39.760
there's gonna be a ford ad at the top of your search results page right but

00:49:38.240 --> 00:49:44.480
now we're talking about voice so there's no page there's just there's gonna be a

00:49:42.000 --> 00:49:47.119
suggested product so if you ask like there's an example here that says

00:49:46.000 --> 00:49:51.200
if you ask a-l-e-x-a because we're not trying to

00:49:49.280 --> 00:49:54.880
trigger the vocal commands anymore good idea um to add an item to your shopping

00:49:53.760 --> 00:50:00.640
cart it will suggest you buy a particular brand so i think that means like

00:49:57.280 --> 00:50:02.880
a-l-e-x-a uh can you add some toothpaste

00:50:00.640 --> 00:50:06.640
to my shopping cart and it'll be like okay i can look for a brand like colgate

00:50:04.960 --> 00:50:10.480
would you like that and if you're like no it can find some other stuff but the default

00:50:09.359 --> 00:50:17.200
matters because a lot of people are gonna be like yeah yeah instead of being like no actually i would like sensodyne

00:50:14.640 --> 00:50:21.520
complete because i got a little wimpy teeth

00:50:18.559 --> 00:50:24.160
i don't flaws so

00:50:22.319 --> 00:50:26.960
yeah it's that is really

00:50:30.319 --> 00:50:36.559
yeah so apparently it might suggest it based on

00:50:33.839 --> 00:50:41.160
your previous purchasing decisions which is not that bad so that would be a

00:50:38.480 --> 00:50:48.079
situation like hey alexa i would like some surface cleaner

00:50:44.880 --> 00:50:50.720
and they know that you bought a clorox

00:50:48.079 --> 00:50:54.720
clorox product in the past so they'll say okay do you want

00:50:53.440 --> 00:50:59.920
pine saw that kind of makes sense um it's going

00:50:57.520 --> 00:51:03.200
to keep people in a little bubble which is maybe not great but if you're just

00:51:02.000 --> 00:51:07.119
trying to order something with a voice command you're probably not trying to shop around you're probably just trying

00:51:05.920 --> 00:51:11.200
to stay within your bubble you probably just want the transaction done faster so

00:51:09.119 --> 00:51:14.319
that's maybe not a bad thing um i'd be interested in hearing what other people

00:51:12.400 --> 00:51:18.319
have opinions in terms of that if i'm making a purchasing decision that i'm

00:51:16.240 --> 00:51:22.160
even remotely unsure of i always research this is probably for your

00:51:20.160 --> 00:51:25.520
second time buying something yeah right so and and it says that it's going to

00:51:24.079 --> 00:51:28.480
suggest things based on what people have previously bought so if you've already

00:51:27.280 --> 00:51:32.559
bought one of these and you're like hey i need some toothpaste and you've been buying the same toothpaste for freaking

00:51:31.359 --> 00:51:37.440
ever and it's like hey do you want the same toothpaste that you've been buying for freaking ever you'll just say yes

00:51:35.920 --> 00:51:41.359
and then well that's what we want but now we're talking about that not happening because of sponsored

00:51:40.400 --> 00:51:47.040
posts yeah do you want the thing you've always been getting or do you want this new featured

00:51:45.119 --> 00:51:49.680
product that like maybe sucks but they paid money

00:51:48.400 --> 00:51:53.200
so that's what is going to be the default yeah

00:51:51.760 --> 00:51:58.079
interesting it would be cool if they had a voice

00:51:55.200 --> 00:52:04.839
command for like no i'd like the usual uh the huge you know what i mean

00:52:00.079 --> 00:52:04.839
well like like if you're if you're uh

00:52:06.559 --> 00:52:11.920
they might know what you want like the dude at mucho burrito knows my order

00:52:10.880 --> 00:52:17.920
um the people at subway over here they know me too yeah it took them like six months

00:52:15.839 --> 00:52:21.119
i have a very simple order i get everything for the veggies like

00:52:19.440 --> 00:52:24.800
everything yeah so it's like they have two decisions anyway they're on it now

00:52:23.200 --> 00:52:29.040
here's my question and i think this is interesting i don't know

00:52:27.119 --> 00:52:32.480
i think there's a if you're a glass half full person or a glass half empty person

00:52:30.640 --> 00:52:37.040
you might have two answers here okay is it likely

00:52:33.760 --> 00:52:39.440
that google will also seek to monetize

00:52:37.040 --> 00:52:43.440
in uh similar ways because google has if they already are

00:52:41.599 --> 00:52:48.960
they're the main advertiser in this space right but is it antithetical to

00:52:46.160 --> 00:52:52.160
google's mission statement or corporate culture

00:52:49.920 --> 00:52:56.000
given that they're coming from a place where they're taking the world's

00:52:54.160 --> 00:53:00.480
information and putting down onto one search result page they're giving you

00:52:57.839 --> 00:53:04.640
options it's democratic it's supposed to be based on like the

00:53:02.880 --> 00:53:09.040
the link juice of the internet you know the democracy the population

00:53:06.720 --> 00:53:13.119
popularity contest of the internet here um when you get into voice you only get

00:53:11.200 --> 00:53:16.559
one answer so does google do the same thing

00:53:14.960 --> 00:53:20.880
amazon's doing or do they never do that

00:53:19.040 --> 00:53:26.640
i suspect they will i gotta get that green yeah paid

00:53:23.599 --> 00:53:28.559
advertising is is google's whole thing i

00:53:26.640 --> 00:53:32.160
would highly sweetest they would i this this is just making me think like we

00:53:30.079 --> 00:53:37.680
need more competition for amazon um because like with google situation

00:53:35.280 --> 00:53:40.640
what is it going to suggest you buy can you even auto buy things through

00:53:39.280 --> 00:53:44.720
voice with google walmart they have a partnership with walmart

00:53:44.720 --> 00:53:51.599
yeah well i just like it's it's the same situation with amazon where it's just

00:53:49.040 --> 00:53:54.960
some like giant massive company eating everything up

00:53:52.960 --> 00:53:59.920
this is going to take more purchasing from other random companies i don't know

00:53:57.920 --> 00:54:04.160
alibaba is coming soon yeah that'll happen well that'll

00:54:01.599 --> 00:54:09.359
usability up here yeah the usability of alibaba is not there compared to amazon

00:54:07.040 --> 00:54:13.680
google has its own shop express yeah come on man

00:54:11.200 --> 00:54:18.880
it's not there i mean like on the same scale in terms of usability um

00:54:16.720 --> 00:54:23.520
trust like if something is a prime product on amazon

00:54:20.960 --> 00:54:26.640
um if it's shipped by amazon it's a prime product it's

00:54:28.880 --> 00:54:36.880
uh it's a high likeliness that you're going to get it on time that you're going to be able to have an easy time

00:54:33.760 --> 00:54:38.800
with returns and warranty and all that

00:54:36.880 --> 00:54:42.559
other kind of stuff i i don't know it's it

00:54:40.160 --> 00:54:46.880
it shelters you like most normal stores do and a lot of online situations don't

00:54:45.040 --> 00:54:50.640
do that properly and their shipping sucks and stuff like

00:54:48.559 --> 00:54:54.400
i understand why amazon's where they're at but

00:54:51.680 --> 00:54:56.800
they need better competition one more

00:54:55.440 --> 00:55:01.280
well we got to do flow plans so let's do Floatplane and one more i'm gonna i

00:54:59.280 --> 00:55:06.480
don't even know if i can screen share um maybe you did the wrong guy yeah i'm

00:55:04.000 --> 00:55:10.319
gonna try that you can find me in the club

00:55:08.720 --> 00:55:14.720
we don't call it that anymore it was full playing club

00:55:13.359 --> 00:55:17.119
come on man um

00:55:17.440 --> 00:55:23.520
it's still not i don't know if we're going to be able

00:55:20.720 --> 00:55:23.520
to show it

00:55:24.720 --> 00:55:30.640
well either way screen sharing is not happy right now

00:55:29.280 --> 00:55:34.800
but full plane has a bunch of really cool stuff on it at the moment there's

00:55:32.720 --> 00:55:38.400
even one thing that doesn't happen that much there's a poll

00:55:36.319 --> 00:55:45.520
there's a there's a discussion poll asking you guys how uh you guys want us

00:55:42.079 --> 00:55:46.960
to share ces content on Floatplane

00:55:45.520 --> 00:55:50.559
because there's a few different good questions usually we don't care what you

00:55:48.720 --> 00:55:55.040
think still not working so we will not be able to screen share um oh i bet you

00:55:53.119 --> 00:55:59.359
i know why it's not working and i could fix it if i had more time but i don't

00:55:57.119 --> 00:56:02.880
that's okay um there's yeah there's a poll asking how you guys want us to

00:56:01.280 --> 00:56:08.079
share content and essentially the decision was with something like youtube

00:56:05.920 --> 00:56:12.400
we have to time out our releases or youtube's algorithm is gonna be like no

00:56:10.000 --> 00:56:14.319
screw you guys and they're already they're already gonna do that a little

00:56:13.599 --> 00:56:19.200
bit because of just the nature of how rapid fire we have to do ces content but we're

00:56:17.680 --> 00:56:24.400
going to do our best to spread it out and make the youtube robot happy um but

00:56:22.319 --> 00:56:28.559
with flow plane whatever it doesn't it doesn't matter we don't

00:56:26.160 --> 00:56:33.359
have to fight any weird algorithm so you guys have so far decided post it in

00:56:30.720 --> 00:56:37.200
the main section and just fire letter writ fire hose let her go so

00:56:35.920 --> 00:56:42.000
right when it's ready we're just gonna post it up you guys gonna get the content a little bit faster it's not

00:56:40.400 --> 00:56:46.960
gonna be the one week window that it normally is because that would be terrible um but it is going to be a

00:56:45.119 --> 00:56:50.640
little bit faster in general we're going to get it up to you guys right away it's

00:56:49.200 --> 00:56:54.319
going to be good you can look like a twitter magician

00:56:52.400 --> 00:56:59.359
yeah you're going to be in the know this video's coming remember it's going to be

00:56:56.720 --> 00:57:03.839
awesome um on here regardless outside of the pool there is a tech wiki for why is

00:57:01.760 --> 00:57:07.119
Windows display scaling so bad i'm excited for that i know a fair amount

00:57:05.359 --> 00:57:11.200
about it because i did the uh surface

00:57:09.200 --> 00:57:14.079
studio review and there's a lot of really interesting information in that

00:57:12.799 --> 00:57:18.240
as to why the screen is the resolution and uh

00:57:16.880 --> 00:57:22.960
aspect ratio and stuff that it is it seems to me like a topic that's like

00:57:20.319 --> 00:57:27.119
yeah it sucks but it has to be this way yeah like you just haven't thought about

00:57:24.400 --> 00:57:31.839
it as hard as the engineers it sucks for a reason uh there's the

00:57:29.119 --> 00:57:37.920
oneplus 5t review now in white if you haven't seen the ad for that it's been

00:57:35.040 --> 00:57:43.040
everywhere so i'd be surprised there's a flow plane exclusive behind

00:57:40.400 --> 00:57:47.280
the scene uh from right before christmas that just got released so i don't know

00:57:45.119 --> 00:57:50.799
got released now but either way it just came out i will not spoil you guys gotta

00:57:48.960 --> 00:57:53.839
see it um so the behind the scenes thing i know some people are

00:57:52.559 --> 00:57:58.079
salty that we don't release this in other places but youtube would destroy

00:57:56.319 --> 00:58:02.480
our search ability if we did that because most people don't care about these things um i think they're awesome

00:58:01.440 --> 00:58:08.559
and the people that do care about them are pretty hardcore about it but anyways

00:58:05.040 --> 00:58:12.160
there's the 13 gpus in one pc mining

00:58:08.559 --> 00:58:14.319
adventure part two this is a very large

00:58:12.160 --> 00:58:19.680
departure from the um kind of amateur hour mining adventure

00:58:17.440 --> 00:58:23.200
part one just you know you know there was some comments they were accurate

00:58:21.520 --> 00:58:28.480
we're just you know what but we're moving forward

00:58:24.559 --> 00:58:31.440
part two strong return part three

00:58:28.480 --> 00:58:34.799
is gonna be even stronger of a return so we're coming at you with some really

00:58:33.040 --> 00:58:40.319
interesting mining adventure videos they're coming pci express 4.0 as fast

00:58:37.920 --> 00:58:46.880
as possible john back at it again with the epic videos um an LTT handmade uh

00:58:44.480 --> 00:58:51.440
there's an ltvt video of a handmade portable arcade box um nothing

00:58:52.799 --> 00:58:58.319
as far as i know check it out uh super cool and there's also

00:58:57.280 --> 00:59:03.200
um some like extra footage from the chiller

00:59:01.440 --> 00:59:07.040
resurrection which is super cool so if you're into that there's extra footage

00:59:05.359 --> 00:59:10.799
the untold story of the chili resurrection again stuff that if we

00:59:09.200 --> 00:59:13.920
threw this on youtube people wouldn't care as much it would hurt the channel

00:59:12.480 --> 00:59:17.839
so we're just throwing it on flow plane for the super hard course and that's it

00:59:15.839 --> 00:59:23.359
we're done moving on to now this weekend there's gonna be another keyboard video

00:59:20.480 --> 00:59:25.920
oh a zany keyboard video us i think we almost did every one of

00:59:25.359 --> 00:59:32.559
them zaniness is ending here

00:59:31.040 --> 00:59:35.920
okay we have another one yeah i think so this is a little simple

00:59:34.480 --> 00:59:40.319
guy yeah sure let's just do that unsurprisingly if you think about it

00:59:37.520 --> 00:59:44.240
2017 was the biggest year ever for electric car sales wow i'm super

00:59:42.160 --> 00:59:47.599
surprised actually tell me more there was a time in like in

00:59:46.640 --> 00:59:52.079
the 30s yes like before the model t where

00:59:50.079 --> 00:59:55.760
electric cars actually were the main uh had the most market share above

00:59:53.680 --> 00:59:58.960
combustion engines but since then this is the biggest year ever someone asked

00:59:57.200 --> 01:00:02.720
about the dust video i'm going to just say this right now the

01:00:00.880 --> 01:00:05.920
dust video is going to happen i'm going to be in it Linus is going to

01:00:04.319 --> 01:00:09.839
be in it there's possibly other people that'll be in it this is probably not

01:00:08.480 --> 01:00:15.440
i don't even know what this is oh this is pretty i understand where you're going with that but no it's uh the dust

01:00:13.520 --> 01:00:19.760
computers are up in the corner i'm not going to be in it guys

01:00:18.160 --> 01:00:24.799
you should just you should just walk through the screen at some point hey

01:00:22.559 --> 01:00:27.680
um yeah it is going to happen we haven't filmed it yet

01:00:26.240 --> 01:00:31.680
means it's not going to be filmed to at least after ces so it's going to be at

01:00:29.760 --> 01:00:34.799
least another week until it's filmed but it's going to happen eventually

01:00:33.280 --> 01:00:41.040
anyways let me chuck some numbers at you here yeah december marks the 27th 27th

01:00:38.880 --> 01:00:45.440
month of consecutive sales gains for plug-in vehicles

01:00:42.559 --> 01:00:51.440
meaning evs so in 2017 there was nearly 200 000 evs sold in the us 199 826 this

01:00:49.760 --> 01:00:54.839
compares to 100

01:00:53.040 --> 01:00:59.440
158 614 so what is that like a 30 increase

01:00:58.079 --> 01:01:05.440
pretty decent so if you break that down by the top five browns that were sold

01:01:03.200 --> 01:01:10.720
the tesla model s was the number one seller at 27 060. next in line

01:01:08.960 --> 01:01:15.119
chevy bolt chevy bolt the the electric version at

01:01:13.280 --> 01:01:19.119
twenty three thousand two hundred ninety seven next in line back to tesla it was

01:01:17.280 --> 01:01:22.319
the model x twenty over twenty one thousand of those sold

01:01:20.559 --> 01:01:26.240
and then what was that i just last i read the last bullet

01:01:23.920 --> 01:01:29.200
points okay okay i thought you were like model x no no no no no

01:01:28.400 --> 01:01:35.119
no i love the waterline it's got the frunk um

01:01:32.960 --> 01:01:39.040
the fourth one was uh the prius prius prime from toyota over twenty thousand

01:01:37.040 --> 01:01:44.720
almost twenty one thousand sold and everyone wants to know how many tesla

01:01:41.359 --> 01:01:47.359
model threes got delivered in 2017 and

01:01:44.720 --> 01:01:52.160
it looks like it was about two thousand about two grand they're doing what a

01:01:49.040 --> 01:01:53.760
thousand a week now uh which is less

01:01:52.160 --> 01:01:57.839
than a previous promise that they'd be doing 5000 a week by the end of the year

01:01:55.200 --> 01:02:03.680
they're now hoping to hit 5000 a week by this summer in terms of production

01:02:00.240 --> 01:02:05.200
estimations that's pretty standard um

01:02:03.680 --> 01:02:09.440
from what we've been able to expect so far is there's the estimation they won't

01:02:07.520 --> 01:02:12.559
hit it but they'll do pretty darn good um and that's cool because they'll

01:02:11.119 --> 01:02:17.839
figure it out eventually there you go

01:02:14.480 --> 01:02:20.720
um someone said in chat stream Labs is

01:02:17.839 --> 01:02:24.640
releasing their own kind of version of obs because obs is open source that is a

01:02:22.880 --> 01:02:28.319
thing i'm going to be screening with that on my personal stream i believe

01:02:26.640 --> 01:02:31.760
Colton is as well but i don't know if i'll end up using it we'll see

01:02:30.079 --> 01:02:36.000
that's another interesting news bit though because if you're into streaming

01:02:33.599 --> 01:02:40.960
it streamlines a lot of haha get it streamlines a lot of different stuff

01:02:37.440 --> 01:02:42.240
which is cool and uh i think we will see

01:02:40.960 --> 01:02:47.599
you guys at sea yes yes we have so far never

01:02:45.920 --> 01:02:52.880
missed a WAN Show at ces so theoretically there will be a WAN Show

01:02:50.319 --> 01:02:55.839
at ces but every single year it's super random

01:02:54.079 --> 01:03:01.839
how it works is super random who's on it is super random where we are is super

01:02:58.160 --> 01:03:03.599
random what time it starts

01:03:01.839 --> 01:03:07.040
not that that's different from normal but it's pretty random it'd be pretty

01:03:04.880 --> 01:03:11.839
cool if we did it from a plane like we have wi-fi on the plane the

01:03:09.599 --> 01:03:16.400
dope you might even be able to get by with

01:03:13.760 --> 01:03:19.599
like a super crappo resolution if we get like everyone else on the

01:03:17.680 --> 01:03:23.520
plane to not use wi-fi you might be able to get by with a super terrible

01:03:21.200 --> 01:03:27.839
resolution um if you think sitting beside a baby on a plane sucks wait till

01:03:25.760 --> 01:03:31.119
you're beside two podcasters i think it would just get

01:03:29.520 --> 01:03:36.000
rejected from twitch though because the latency

01:03:33.039 --> 01:03:39.760
because like i i connected to a game while i was on a plane just to check out

01:03:37.839 --> 01:03:43.920
my latency and it was like quite a few seconds between input

01:03:42.319 --> 01:03:47.440
and what actually happened well we can always do another pre-recorded one like

01:03:45.359 --> 01:03:50.880
this one was oh

01:03:48.799 --> 01:03:54.799
why no i'm joking

01:03:52.640 --> 01:03:59.839
i'm joking it says friday january 5th right there

01:03:58.160 --> 01:04:04.559
oh jk no the joke i gotta go man

01:04:04.799 --> 01:04:13.480
anyways uh i'll see i'll see you guys ces videos ces one

01:04:09.200 --> 01:04:13.480
show next week see you later goodbye
