WEBVTT 00:02.380 --> 00:11.560 okay what is going on guys so I wanted to do this video really quick and I 00:11.560 --> 00:16.860 apologize it's very informal I had to format this workstation so I don't 00:16.860 --> 00:22.780 have anything fancy in terms of like overlays or whatever set up and I 00:22.780 --> 00:29.740 actually ended up realizing that I lost my I didn't back up this document over 00:29.740 --> 00:36.860 here that I kind of want to walk you guys through so this is just going to be a 00:36.860 --> 00:44.000 very informal and hopefully a very like reasonably quick conversation about like 00:44.000 --> 00:51.220 what is and is not possible in terms of like technocracy and stuff like that so 00:51.220 --> 00:56.280 that's my assignment my background is I'm a self-taught technology 00:56.280 --> 01:03.540 professional I graduated high school in the early 2010s and basically from there 01:04.520 --> 01:12.800 worked everything from implementation networking which I hated so not great at 01:12.800 --> 01:17.880 networking but I can work my way through stuff and I've been fortunate to work 01:17.880 --> 01:25.420 for I have a career with like some of the biggest names in technology and kind 01:25.420 --> 01:31.480 of like most recently I've my career probably for the last like five or so 01:31.480 --> 01:39.360 years has been focused on automation integration and systems administration 01:40.300 --> 01:49.700 mostly just kind of focusing on taking companies pet infrastructure and 01:49.700 --> 01:56.120 turning it into cattle so kind of like lowering the barriers for them to not 01:57.100 --> 02:07.260 exactly need like hardcore skilled labor or like knowledge workers or whatever so 02:07.260 --> 02:14.180 what I want to try and do is I want to address some of these points that Terry 02:14.180 --> 02:19.220 brought up so hopefully that will provide some value to you and I also want to 02:19.220 --> 02:30.880 provide like context as I understand it I'm a child of the 90s so kind of some of 02:30.880 --> 02:36.280 some of my knowledge like hearsay and some of it is you know digging your 02:36.280 --> 02:41.700 first like for me I dug my first computer out of a trash heap it was an IBM clone 02:41.700 --> 02:51.180 with a cartridge Intel running Windows 95 so like part of it is experience part of 02:51.180 --> 03:05.140 it is hearsay but I basically caught the tail end of the IT cart era if fellow 03:05.140 --> 03:10.600 technology professionals will understand what that means so to kind of get into 03:10.600 --> 03:14.540 it so what I want to do is I kind of want to like provide context in terms of 03:14.540 --> 03:19.820 like what technology has really been doing like I want to try and make it 03:19.820 --> 03:27.380 material for people who you know maybe you're into books or you're into finance 03:27.380 --> 03:33.560 or whatever and you're not really thinking about technology in terms of 03:33.560 --> 03:39.700 like how it relates to the agenda and stuff like that so I'm gonna try to talk 03:39.700 --> 03:46.820 about technology as if it's a cult right like we I think if you're watching this 03:46.820 --> 03:52.960 video we share an understanding that technology is probably more likely than 03:52.960 --> 04:01.140 not being the technology is more likely than not the means to the ends for 04:02.700 --> 04:09.320 technocratic control of the world it's not some it was a premeditated thing 04:09.320 --> 04:14.220 it's not just oh hey we're gonna give you all this good great thing for your 04:14.220 --> 04:21.080 empowerment and I apologize I'm a little bit scattered brain I'm going on 28 04:21.080 --> 04:28.640 hours now no sleep so but whatever I have time to do this I'm gonna try and do 04:28.640 --> 04:35.680 it so bear with me please and thank you so to kind of get this started as I'm 04:35.680 --> 04:42.100 sure a lot of y'all are aware you know late 60s through 70s computing was very 04:42.100 --> 04:49.380 basic hunch cards mainframes terminals talking to the mainframes and the 04:49.380 --> 04:55.120 industry was kind of focused on how do we get computers out into the world I'm 04:55.120 --> 05:04.780 sure there was like DARPA and the internet and all that jazz oh excuse me but I 05:04.780 --> 05:14.360 don't know anything about that so moving along from the 70s we call it the 70s 05:14.360 --> 05:21.580 to 80s gap that's when we started having operating systems and options like 05:21.580 --> 05:30.860 DOS like basic DOS the start of Microsoft Unix which is like Bell Labs I 05:30.860 --> 05:35.480 think BSD so Berkeley software distribution which is the foundation of 05:35.480 --> 05:48.640 Mac OS those started proliferating and technology was going from institutions 05:49.220 --> 06:03.280 like colleges and universities into business right so call it 80s to 90s now 06:03.280 --> 06:09.120 that technology is working its way through industry it now needs to work its way 06:09.120 --> 06:16.080 through people and this is when we started having like mature Linux windows 06:18.820 --> 06:26.840 IBM Spark trying to think if there's any other operating systems I can think of 06:26.840 --> 06:30.760 from that time we basically had a whole bunch of one-off operating systems 06:30.760 --> 06:36.840 competing for market share of like who would be good but the point I kind of 06:36.840 --> 06:43.100 want to like the thing I really want to like highlight to you guys is this was 06:43.100 --> 06:51.400 the period so like that 80s 90s period where technology was moving you know it 06:51.400 --> 06:56.840 it went from education to industry to now people business people and then 06:56.840 --> 07:02.500 consumer electronics like all the people this is the first instance where the 07:02.500 --> 07:08.680 physical world gets digitized and becomes observable right so we talk about like 07:08.680 --> 07:16.900 social media creating the substance to transact and analyze social interactions 07:16.900 --> 07:24.020 well this comes before that and what you kind of see for example are the filing 07:24.020 --> 07:29.900 cabinets you might have in a business archive those are now filing systems 07:29.900 --> 07:39.700 those are now file systems like NTFS, FAT, EXT, whatever and then you see a bunch of 07:39.700 --> 07:46.700 analogs for a bunch of different things documents become like DOTX, ODTs, photos, 07:46.700 --> 08:01.240 JPEGs or GIFs or whatever music MP3s videos in force databases start to proliferate but 08:01.240 --> 08:05.420 the other part in like the thing to really point out is this is the time when 08:05.420 --> 08:13.540 technology went from a series of linear instructions to concepts like computing 08:13.540 --> 08:17.200 concepts that we know of now like object-oriented programming and stuff 08:17.200 --> 08:24.040 like that becoming a thing and then we had like social media and whatever social 08:24.040 --> 08:33.660 media like crude websites you know it's connected to the odds and tens but then 08:33.660 --> 08:37.320 we started creating social media so really what I kind of want to illustrate 08:37.320 --> 08:42.120 right there is for people who aren't really thinking about this in terms of 08:42.120 --> 08:49.260 like how does technology give technocrats the means to control society it's 08:49.260 --> 08:57.560 because we focused on creating digital analogs for everything that exists in 08:57.560 --> 09:03.440 the material world and then we started pushing everybody into the digital world 09:03.440 --> 09:13.440 while we didn't push we offered it they offered it to the world as technology 09:13.440 --> 09:19.900 that was supposedly supposed to empower us and stuff like that so then we get 09:19.900 --> 09:24.560 into so now we're kind of like moving into okay so the personal computing 09:24.560 --> 09:31.500 revolution was about making you the end user observable it was about moving 09:31.500 --> 09:38.020 you out of the physical world and into the digital world with digital synthetic 09:39.380 --> 09:45.340 replicas or whatever you want to say of all the things you had in real life on 09:45.340 --> 09:53.720 a computer and then the the 2000s and the 2010s hit right and so we're we've 09:53.720 --> 09:58.560 we've kind of like started we've got like client server going on and we have 09:58.560 --> 10:05.520 like databases and you know hard drives are starting to go from like megabytes to 10:05.520 --> 10:10.580 gigabytes because all of a sudden you're having pictures and all this jazz and 10:10.580 --> 10:16.800 this is to say okay cool so technology 1.0 is accomplished and now we need to 10:16.800 --> 10:24.420 move into what we're gonna do next and for me that's virtualization and 10:24.420 --> 10:30.260 starting to think about scaling and hyperscale so during that time we were 10:30.260 --> 10:34.760 kind of so this is the first part where the tech industry thinks to itself okay 10:34.760 --> 10:41.940 how are we going to streamline create capacity and create new capabilities the 10:41.940 --> 10:46.940 big breakthrough there was kind of like alright we're kind of being wasteful 10:46.940 --> 10:56.920 with our resources we realize that we're basically doing one operating system to 10:56.920 --> 11:03.080 one server in a group of servers that are behind a load balancer or a proxy or 11:03.080 --> 11:11.880 some kind of like application gateway and that's savagely inefficient and if we 11:11.880 --> 11:19.200 want to be able to serve more customers a.k.a observe more people have 11:19.200 --> 11:27.440 transactions it would actually be more efficient for us to virtualize everything 11:27.440 --> 11:33.680 so basically the big breakthrough was we in the same way that we virtualized 11:33.680 --> 11:38.600 let's just call it digital artifacts and things like that we then started 11:38.600 --> 11:54.380 digital digitalizing computers so companies started adopting you know ESXi 11:54.380 --> 12:02.760 Zen server QEM UKVM things like that and then they started getting really 12:02.760 --> 12:10.740 efficient with all right now instead of having like a server with a crap ton of 12:10.740 --> 12:15.700 disks we're gonna have a storage area network with a net app appliance or 12:15.700 --> 12:21.800 pure storage appliance for example right we're and we're just gonna connect that 12:21.800 --> 12:27.140 through like iSCSI or whatever to a virtualization server where all of my 12:27.140 --> 12:33.060 fake computers are running from and we basically started making technology 12:33.060 --> 12:39.760 liquid we started like this is kind of where software defined networking and 12:39.760 --> 12:46.020 storage so like s3 I consider software defined because it's it's different 12:46.020 --> 12:52.300 kinds of storage has its own API and whatnot same thing with our 12:52.300 --> 12:58.780 hypervisors well it wasn't necessarily robust you could create virtual software 12:58.780 --> 13:04.280 switches and program them with virtual networks so that was kind of the 13:04.280 --> 13:09.320 precursor to the cloud where we started saying okay we're moving away from a 13:09.320 --> 13:16.120 one-to-one relationship where one server is one operating system is one 13:16.120 --> 13:24.220 workload into we now have application specific hard so this hardware is for 13:24.220 --> 13:31.080 storage this hardware is for networking this hardware is for compute and then we 13:31.080 --> 13:37.880 started conceptualizing so if the computing revolution of the 80s and 13:37.880 --> 13:45.980 90s gave us things like object-oriented programming data-basin objects stuff 13:45.980 --> 13:51.740 like that like digital analogs for things the computing revolution of the 13:51.740 --> 14:01.400 odds and the 10s was making technology more liquid and so I'm bringing this up 14:01.400 --> 14:08.840 I'm bringing this stuff up to y'all to kind of say that like we people are 14:08.840 --> 14:13.660 trying to tell you like we're so far along in technology and you just don't 14:13.660 --> 14:22.660 understand how far along we've come and the reality is we actually have it like 14:22.660 --> 14:29.140 we're not as far along as the powers that be want you to believe if we're being 14:29.140 --> 14:37.240 honest about things we're really only like two iterations into you know the 14:37.240 --> 14:42.840 70s 80s and 90s were rudimentary computing was like basic bitch 14:42.840 --> 14:48.400 computing of what it could be and then you're looking at the you know late 90s 14:48.400 --> 14:54.040 to 2000s to 10s and that's when we started actually making something of 14:54.040 --> 15:01.800 technology and iterating on it and so we're now you know realistically just 15:01.800 --> 15:12.540 past the 2010s and into the 2020s so it's like what 2020 36 I don't know it's 15:12.540 --> 15:24.860 late 2025 way off we're in 2025 so we're five years away from the 2010s right so 15:24.860 --> 15:30.440 moving right along so the key point there before we move on is I'm trying to 15:30.440 --> 15:37.420 illustrate to you guys that we've basically only had two cycles of innovation 15:37.420 --> 15:43.560 let's just call it where the first innovation cycle was taking computers from 15:43.560 --> 15:50.280 basic to being able to represent life and then taking computers that can 15:50.280 --> 15:57.620 represent life and attaching them to systems that are scalable liquid and 15:58.740 --> 16:05.460 performant if that kind of makes sense right we moved past just understanding 16:05.460 --> 16:11.100 how to do that to having a sophisticated deployment like sophisticated deployment 16:11.100 --> 16:17.660 options okay so hopefully I've made that point all right so now we kind of pop 16:17.660 --> 16:26.060 into present day where you know you might hear things like hyper scaling or data 16:26.060 --> 16:31.520 warehousing or data science machine learning AI models and stuff like that 16:32.160 --> 16:37.840 so from the drop I'm just gonna say what I feel like I'm seeing is this repeating 16:37.840 --> 16:48.500 trend where computing just models things it is it's a it's a babadook is not the 16:48.500 --> 17:02.780 right word everything about computing is modeling not thinking right so you and I 17:02.780 --> 17:08.620 we can think we have sophisticated faculties for context and memory and 17:08.620 --> 17:15.380 things like that but a computer really only understands transactional like it 17:15.380 --> 17:21.740 really can only transact between a to b this thing either is what it is or it's 17:21.740 --> 17:27.860 not so kind of where we're at right now is we're in the second or we're in the 17:27.860 --> 17:32.960 first revolution from what you I guess you would say second it depends on how 17:32.960 --> 17:38.700 you want to look at it but the revolution we're in the middle of is kind of 17:38.700 --> 17:44.920 throughout the 2010s when we started figuring out we can make software defined 17:44.920 --> 17:51.800 whatever and sell that as a service to businesses so like pure storage I have 17:51.800 --> 17:57.040 yet to see a company that screws with their pure storage appliance they buy it 17:57.040 --> 18:02.600 it gets installed and if they need anything out of it other than creating 18:02.600 --> 18:07.700 their shares and doing what they need to do pure storage handles it and in some 18:07.700 --> 18:15.660 cases that's also true for VMware if you're using a managed service provider 18:15.660 --> 18:23.720 like a toss trying to think of anyone else that I mean I guess it doesn't matter 18:23.720 --> 18:39.320 but yes so there goes my phone awesome so right now where we are is what the 18:39.320 --> 18:44.760 industry tried and failed to do and I believe this is important for you guys 18:44.760 --> 18:52.060 to understand is during the early 2000s was really when we were figuring out like 18:52.060 --> 18:57.060 how to get more efficient and then in the 2010s was when we were figuring out 18:57.060 --> 19:04.280 software defined whatever and for a period there we were focused on software 19:04.280 --> 19:09.380 defined whatever being on print and that's why you would buy like that's why 19:09.380 --> 19:14.820 you buy storage appliances hypervisors whatever but then the cloud came along 19:14.820 --> 19:25.600 AWS Microsoft Azure Google Cloud Digital Ocean Bolcher Bluehost whatever and what 19:25.600 --> 19:30.020 we thought was going to happen is we were going to have everybody all these 19:30.020 --> 19:35.320 businesses we're going to move their operational footprint from their 19:35.320 --> 19:40.680 co-located data centers or even their own like we own it it's in our building 19:40.680 --> 19:44.840 I've worked in some companies where their data center where their data center was 19:44.840 --> 19:49.260 like in that dead-ass center of the building which was a weird choice but 19:49.260 --> 19:53.340 okay I mean I get it because you got to go through several security layers to 19:53.340 --> 19:58.240 get in there but still it's weird and they thought there was gonna lift and 19:58.240 --> 20:02.480 shift that up into the cloud and the benefit was going to be that the 20:02.480 --> 20:07.300 cloud providers we're gonna give you all these services like all these 20:07.300 --> 20:12.140 different flavors of compute so you're probably used to a computer being a 20:12.140 --> 20:16.620 computer but there are things like functions where it's just executing a 20:16.620 --> 20:22.420 piece of code containers which is a self-contained application with its 20:22.420 --> 20:28.380 dependencies running on top of an operating system so you a kernel let's 20:28.380 --> 20:33.380 be more specific kernel like Linux virtual machines which is kind of like 20:33.380 --> 20:40.760 this like a it's a virtual desktop environment and servers and stuff like 20:40.760 --> 20:46.680 that and then an offer it also offers other things like storage so you have S3 so 20:46.680 --> 20:52.380 you guys are probably just used to block storage your hard drive is a block 20:52.380 --> 21:01.540 storage device but there's also blob file block so that's simple scalable secure 21:01.540 --> 21:06.640 storage but it's also three kinds of storage whatever and then there's 21:06.640 --> 21:12.360 different kinds of databases like MySQL Postgres whatever but then there's 21:12.360 --> 21:30.180 also large-scale data warehousing I think like Aurora DB and I forget so the 21:30.180 --> 21:35.660 point I'm trying to make is is so then the cloud providers stepped in and they 21:35.660 --> 21:41.900 started providing us with all the way beyond the rudimentary here's some 21:41.900 --> 21:46.380 storage here's some here's some processing compute and here's some 21:46.380 --> 21:53.000 networking it's here is computing as an integrated platform and we're gonna 21:53.000 --> 21:59.700 start offering you API's and features for you to construct your cloud 21:59.700 --> 22:05.640 environment with and we thought that was going to work so the industry started 22:05.640 --> 22:11.820 laying people off like myself and you know database admins networking people 22:11.820 --> 22:19.820 whatever because you no longer needed you know network engineers to program 22:19.820 --> 22:23.740 your switches and such you would simply go into your cloud and through the 22:23.740 --> 22:29.240 glory of software defined networking say in this cloud I want there to be five 22:29.240 --> 22:33.660 subnets the cloud will address those automatically and then you just have 22:33.660 --> 22:38.700 to click for a route that basically says hey connect this to this and it 22:38.700 --> 22:44.520 does it right so computing was just or enterprise computing was just 22:44.520 --> 22:51.880 rapidly simplified however that didn't work out because kind of what we're 22:51.880 --> 22:56.980 seeing is first of all it's cost prohibitive like everyone is moving all 22:56.980 --> 23:04.100 their their stuff back to on-premise solutions so co-located data centers or 23:04.100 --> 23:09.020 within their office themselves so there's something called an IDF an 23:09.020 --> 23:16.680 intermediary distribution frame and so if you are you know let's say you're like 23:16.680 --> 23:23.640 a business with like two to five hundred employees chances are you have an IDF in 23:23.640 --> 23:27.820 your suite and that's where you put your computing equipment so your network 23:27.820 --> 23:34.040 switches storage servers whatever and it's cooled it has a connect connection 23:34.040 --> 23:38.760 usually directly from the internet service provider and some people run 23:38.760 --> 23:44.180 their stuff out of that other people purchase rack space and a regional 23:44.180 --> 23:49.320 data center and they put all their stuffs in there and those regional data 23:49.320 --> 23:57.900 centers kind of have the same perks as a cloud data center just that it's your 23:57.900 --> 24:02.520 hardware but they will give you smart hands they will give you people that 24:02.520 --> 24:09.040 like do all things for you if a disk fails they'll swap it out if you get new 24:09.040 --> 24:15.740 hardware shipped in they'll install it get the KVM setup so that you can remote 24:15.740 --> 24:20.900 into it through ILO integrated lights out it basically just means there's 24:20.900 --> 24:25.040 networking for the firmware of the motherboard that lets you interact with 24:25.040 --> 24:30.320 the computer and then there's networking for the server itself that the 24:30.320 --> 24:34.980 operating system talks to the internet so this is kind of say everything is 24:34.980 --> 24:40.660 moving back on prim and it's a mixture of people are continuing to do what they've 24:40.660 --> 24:47.400 always done and just buy a hypervisor or something like that but then also they 24:47.400 --> 24:55.180 have solutions for hyperconverged so Dell for example sells an Azure 24:55.180 --> 25:00.800 product it's like Azure Edge or something like that I don't remember what it's 25:00.800 --> 25:08.180 called at this point but essentially the plan technology now is people who make 25:08.900 --> 25:15.880 the interface that you see on Microsoft Azure's cloud is basically sold to 25:15.880 --> 25:24.040 business rented to businesses off hardware from people like Dell or HP and what 25:24.040 --> 25:28.600 you're essentially getting is a cloud in a box solution where you say okay I'm 25:28.600 --> 25:35.260 gonna spend 50 million dollars on this much technology resource and you're 25:35.260 --> 25:40.800 gonna slap the Azure interface on top of it and Dell is going to manage the 25:40.800 --> 25:45.520 relationship between the hardware we're purchasing and the software we're 25:45.520 --> 25:49.640 renting and we're just going to manage the soft we're just gonna work 25:49.640 --> 25:55.780 inside that software to do what we need to do and that software connects back to 25:55.780 --> 26:02.240 the cloud so just to kind of point that out to y'all that it's really weird how 26:02.240 --> 26:07.500 the big cloud providers are still keeping their hands all up in your 26:07.500 --> 26:12.600 business so they can still see it so if we're talking about decentralized 26:15.180 --> 26:20.380 technology and stuff like that it's decentralized technology is becoming 26:20.380 --> 26:27.320 decentralized in that the computing platforms are centralized but the 26:27.320 --> 26:35.440 burden of operation is being shifted from the cloud providers to the people 26:35.440 --> 26:42.160 that want to do the computing so it's the most disempowering way to do 26:42.160 --> 26:47.700 computing for the sake of convenience okay so that's kind of where like the 26:47.700 --> 26:54.580 technology stuff ends and now we're starting to get into like the agenda 26:54.580 --> 27:02.940 space so kind of what we're doing right now in the technology space is 27:02.940 --> 27:11.540 everything is about data mining and it's basically business intelligence BI for 27:11.540 --> 27:22.280 example and having customer data that you can then make available to a data 27:22.280 --> 27:28.040 scientist machine learning engineer or whatever and what those people do is 27:28.040 --> 27:35.860 discover and model behavior from data so you know who's most likely to buy 27:35.860 --> 27:43.080 this ticket or whatever and then the data science people create you know 27:43.080 --> 27:48.140 prediction models or recommendation models and stuff based off all that 27:48.140 --> 27:53.820 information and that's how you see for example what Amazon tells you you 27:53.820 --> 28:08.480 should buy on the website so I guess let's start here digital twin and 28:08.480 --> 28:17.400 civilization simulation so your phone is already your digital twin there's there's 28:17.400 --> 28:26.120 no if you're using Apple or Google phones if you're using something with iOS or 28:26.120 --> 28:32.120 Android you have to sign into that phone and that phone has your email address 28:32.120 --> 28:38.420 your banking information it has your health information on it if you're 28:38.420 --> 28:43.660 using the platform native tools like Samsung or Google health and Apple health 28:43.660 --> 28:48.440 or if you're someone like me I'm using Garmin so the platform is not 28:48.440 --> 28:55.220 necessarily aware of it but that health data is there and so the whole point is 28:55.220 --> 29:00.860 so like if you're looking at what Apple does for example it's basically leaching 29:00.860 --> 29:08.960 out into every aspect of your life to make it observable Apple has Apple wallets 29:08.960 --> 29:13.780 so that everything you pay for goes through their platform through their 29:13.780 --> 29:20.160 merchants so Apple can kind of skirt the whatever and say oh you know we care 29:20.160 --> 29:23.880 about your privacy but the reality of the situation is they're the 29:23.880 --> 29:29.820 facilitators for people like Visa and MasterCard who are controlling what you 29:29.820 --> 29:35.860 can and cannot spend your money on Apple's just facilitator so the point 29:35.860 --> 29:42.740 of this is that if we're talking about digital twin and civilization simulation 29:42.740 --> 29:49.320 this is why people are saying digital ID is the hill to die on because once 29:49.320 --> 29:55.200 your Apple or Google wallet has your digital ID in there the fact that you 29:55.200 --> 29:59.740 like signed in with the username and email kind of becomes irrelevant 29:59.740 --> 30:12.060 because your instance of Android or iOS becomes uniquely bound to you through 30:12.060 --> 30:18.120 the digital ID inside the operating system right that's that's why there's like 30:18.120 --> 30:25.500 API's there's platform API's they'll let you interact with it your phone 30:25.500 --> 30:35.680 literally becomes a beacon of you right so in terms of digital twin and 30:35.680 --> 30:49.560 civilizational simulation I don't think it's possible for people to I do not think 30:49.560 --> 30:54.700 I think the problem with the solution or the strategy right now is the powers 30:54.700 --> 31:01.440 that be are trying to have a world brain right so they want to have like one 31:01.440 --> 31:08.340 thing one all-knowing blob of compute that is capable of handling all the 31:08.340 --> 31:16.120 variables and that's that's not possible what we can start doing however is 31:16.120 --> 31:22.820 saying okay so with COVID we'll take COVID for example during COVID contact 31:22.820 --> 31:31.080 tracing was implemented so your phone is now going out and sniffing the radio 31:31.080 --> 31:36.820 signals from all other phones and essentially reading the broadcast IDs 31:36.820 --> 31:45.040 of those phones to say to understand oh I'm talking to phone 123 and carriers 31:45.040 --> 31:54.520 can say okay cool well phone 123 is using is using subscriber identification is 31:54.520 --> 32:02.500 module blah which is associated with this person so what you can do is you can 32:02.500 --> 32:10.030 say all right cool I'm going to start visualizing cell tower traffic and I'm 32:10.030 --> 32:22.130 going to do maybe like a second order second order correlation between phones and 32:25.830 --> 32:34.510 people sorry the fatigue just hit you can do a very rudimentary visualization of 32:34.510 --> 32:39.090 where phones are moving within a cellular network and that's why they're set up 32:39.090 --> 33:00.750 as honeycombs so I want to see if there's a visualization I can show you so the 33:00.750 --> 33:08.650 point kind of being the way cell towers are set up is they're set up cell tower 33:08.650 --> 33:15.790 cell tower cell tower cell tower cell tower within like a 6 to 20 mile radius 33:15.790 --> 33:22.130 I'm not a telco engineer but my understanding is it's not like 500 they're 33:22.130 --> 33:29.210 not broadcasting over 500 miles it's it's like five to 20 miles at most depending 33:29.210 --> 33:37.430 on how powerful the the access point is but even then I'm pretty sure it's more 33:37.430 --> 33:42.470 like five to ten miles each so the whole point is cell towers are set up like a 33:42.470 --> 33:48.870 honeycomb to triangulate you within any like polygon let's just call it of the 33:48.870 --> 33:57.470 map so I guess the kind of like say digital twin civilization simulation it 33:57.470 --> 34:08.410 would be possible on a regional scale to work with a carrier to visualize phones 34:08.410 --> 34:16.850 moving through access points and associating that with you know men mostly 34:16.850 --> 34:25.950 go to the bar at 7 o'clock after work in downtown Colorado right and you can start 34:26.930 --> 34:32.230 figuring stuff like that out and then from there you can start extrapolating you 34:32.230 --> 34:42.090 know who's doing what where and when but in terms of like drilling down into like 34:42.090 --> 34:49.330 the individual person and knowing that that dot on the matrix did 45 minutes of 34:49.330 --> 34:53.070 cardio instead of going to the gym or something like that no you're not gonna 34:53.070 --> 35:01.830 have like that real time like analytic capability and that's that's so I'll 35:01.830 --> 35:09.170 just point it out to you this way a Google phone is called a pixel you are 35:09.170 --> 35:17.350 a pixel in the larger image of what is happening in the internet sphere the new 35:17.350 --> 35:24.930 sphere whatever like you might have called it back in the day I think maybe 35:24.930 --> 35:34.070 when we start working on quantum like I'm pretty sure the reason why they want 35:34.070 --> 35:41.470 quantum is to be able to do that lower level whatever but the overall point I 35:41.470 --> 35:49.190 guess I'm trying to make is digital twin and civilization simulation is not a 35:49.190 --> 35:58.610 possibility in the minority report since the best they can do is watch and 35:58.610 --> 36:07.510 observe trends and create like derivative insights but it we learned this 36:07.510 --> 36:13.050 lesson in 2001 when we thought we were just gonna spin up data centers and 36:13.050 --> 36:19.930 log everything that happened that moved through a telco and that didn't work out 36:19.930 --> 36:26.990 and we decided okay it's gonna be something like seven years you're gonna 36:26.990 --> 36:37.530 have intercept rooms and stuff like that so there is that and I guess maybe that 36:37.530 --> 36:46.490 kind of segways into digital ID and gated internet so that that's already here 36:46.490 --> 36:52.330 like whether you want to or not when you sign up for internet you have to prove 36:52.330 --> 36:58.910 your identity and you're paying with your card and stuff like that so in the 36:58.910 --> 37:06.370 same way that your cell phone has an e-sim your internet equipment also has 37:06.370 --> 37:12.370 subscriber identification capabilities inside of it in my case I'm using 5g 37:12.370 --> 37:18.430 internet home internet so same thing I'm pretty sure same thing under the 37:18.430 --> 37:26.010 it's a 5g modem with a subscriber ID and it's all linked to me what people are 37:26.010 --> 37:37.690 saying on geopolitics and empire for example her voyage was saying that you 37:37.690 --> 37:44.310 know they can do it they have the capability they just can't legally do 37:44.310 --> 37:54.690 it he's right like the the name of the game is seed the ground before you turn 37:54.690 --> 38:00.070 on the feature or before it's solution crisis right it's like the solution is 38:00.070 --> 38:07.070 already there they just need a crisis to be able to start doing that so you know 38:07.070 --> 38:17.330 save the children what about porn whatever um as far as social credit score 38:17.330 --> 38:24.070 and let's just call it like carbon allowances and banning of red meat so I 38:24.690 --> 38:31.590 think that's probably like plausible on a regional basis and that's kind of what 38:31.590 --> 38:36.830 this stuff is over here but really kind of the way I see that working out so so 38:36.830 --> 38:46.110 this is my solution for how how you would do that right so I think you would be so 38:46.110 --> 38:50.950 you have a phone right and your app is using the cloud and this is as your 38:50.950 --> 38:55.590 functions in this case and you're you're gonna transact something you're gonna 38:55.590 --> 39:04.770 buy you know some meat pull out some cash whatever that goes into a data 39:04.770 --> 39:13.390 warehouse that data warehouse is mined for insights and then those insights are 39:13.390 --> 39:23.330 modeled with machine learning and AI which produce modules or models excuse me so 39:23.330 --> 39:29.530 what I feel is plausible is there's gonna be an industrial model and then 39:29.530 --> 39:33.290 there's going to be a social model and the way this is basically going to work 39:33.290 --> 39:43.710 is the correct resource allotments are if this is ever going to work the correct 39:44.330 --> 39:52.190 resource allotments behaviors whatever are going to be modeled in regional 39:52.190 --> 39:58.310 behavioral models so this region consumes this much red meat you know 39:58.310 --> 40:07.710 whatever and essentially it's it's just an issue of kind of saying all right this 40:07.710 --> 40:12.890 is acceptable this is not we've hit the quota we haven't hit the quota and as 40:12.890 --> 40:19.390 soon as we hit the quota people start getting denied at the point of their 40:19.390 --> 40:33.190 cell phone right so I know that's pretty nebulous and to maybe try and be like a 40:33.190 --> 40:40.010 little bit more articulate about that is you know we hear conversations about 40:40.010 --> 40:49.430 Palantir and their you know civilization simulation simulation and then we 40:49.430 --> 40:56.850 also hear about like ERP and CRM solutions enterprise resource planning 40:56.850 --> 41:03.250 and customer relationship management platforms and my thing is basically so 41:03.250 --> 41:13.190 like cloud Salesforce SAP so on and so forth so my thing is basically this I 41:13.190 --> 41:21.470 feel like what's going to happen is regionally appropriate consumption 41:21.470 --> 41:30.990 patterns behaviors whatever are going to be modeled in an LLM based off of 41:30.990 --> 41:37.830 integrated and I'm saying that with air quotes customer data and then from there 41:37.830 --> 41:43.050 those LLMs are basically going to be responsible for saying okay there's an 41:43.050 --> 41:50.810 overconsumption of red meat in this area and all the sudden deliveries of red 41:50.810 --> 41:54.950 meat are going to be throttled so it's not that anyone is taking anything away 41:54.950 --> 42:01.990 necessarily it's it's just that the industry will be orchestrated based off 42:01.990 --> 42:12.830 of you know what people say are what what the powers that be say is acceptable 42:12.830 --> 42:19.210 and not and so that that's kind of like a high level I couldn't happen yes 42:19.210 --> 42:26.550 because theoretically if you have the data in an ERP system or something like that 42:26.550 --> 42:32.730 you can model it either with the machine learning model or with an LLM that 42:32.730 --> 42:39.870 recognizes like quantities or whatever but as far as like the social credit 42:39.870 --> 42:47.590 scoring and stuff like that I mean the digital ID is the bulkhead to do that 42:47.590 --> 42:51.730 and I'm gonna repeat something I've heard that you know this isn't my idea but I 42:51.730 --> 43:00.010 happen to agree with it social credit scores are here in terms of your what is 43:00.010 --> 43:04.570 your credit score what's your customer satisfaction rate like if you do gig 43:04.570 --> 43:13.290 apps what's your customer satisfaction rating or you know if if there's 43:13.290 --> 43:19.610 consumption based rewards it's like Amazon for example they give you the 43:19.610 --> 43:25.970 opportunity to bundle purchases into bigger deliveries so instead of getting 43:25.970 --> 43:29.650 like a bunch of different things through a bunch of different days everything 43:29.650 --> 43:34.730 just gets grouped into one delivery and that's low carbon and whatever so the 43:34.730 --> 43:39.930 scoring mechanisms are there for them to start saying like oh this person you 43:39.930 --> 43:45.190 know cares about the climate cold stuff or they don't it's just a matter of 43:45.190 --> 43:50.230 integrating it and having a digital ID which essentially acts like a foreign key 43:50.230 --> 43:55.830 in an integrated system I don't it's a concept in databaseing where you 43:55.830 --> 44:03.490 basically say okay this is a row in the database that represents a person and 44:03.490 --> 44:09.850 the columns are all their attributes and that is a key for you know a row in 44:09.850 --> 44:16.490 another database that might say something like DJ is an eye as a digital ID in the 44:16.490 --> 44:24.570 ID table and he's foreign keyed to black Indian motorcycle in this table like my 44:24.570 --> 44:30.590 motorcycle my motorcycle when I paint it off I got a paper title but it also is a 44:30.590 --> 44:39.670 it's also digitally registered or whatever so it's associated with me so 44:40.650 --> 44:48.870 really the scoring and stuff like that is already happening it's it's more just 44:48.870 --> 44:58.270 they need a way to anchor all of the insights to one person and then they 44:58.270 --> 45:03.970 could start worrying about carbon allowances banning red meat and stuff 45:03.970 --> 45:10.190 like that universal basic well I mean they could probably do if they're giving us 45:10.190 --> 45:16.890 steamy checks now so they can probably do universal basic income but I guess to 45:16.890 --> 45:25.070 maybe like talk about is this possible so I just kind of want to point out this 45:25.070 --> 45:33.350 is these are outdated but this is I believe this one was Amazon AWS and these 45:33.350 --> 45:40.130 blue dots are their data centers and then this is Microsoft Azure and hopefully 45:40.130 --> 45:45.670 you can see these little lines right here so those are express routes and that 45:45.670 --> 45:51.450 basically just means there's fiber cable connecting those data centers and the 45:51.450 --> 45:57.970 reason that's important is just because fibers like millisecond latency it's it is 45:57.970 --> 46:03.830 the closest thing we have to real time and I would imagine if you're if you 46:03.830 --> 46:10.010 have like multiple 10 gig links and stuff like that for a dedicated purpose of 46:10.010 --> 46:17.710 this kind of stuff that provides very low-level intercommunication and that's 46:17.710 --> 46:26.190 important because we'll plop on over here to modeling so so the hypothesis or the 46:26.190 --> 46:30.470 proposed solution for me if I'm saying okay if I want to implement 46:30.470 --> 46:34.810 technocracy and I want to start controlling people and consumption and 46:34.810 --> 46:39.930 things like that how would I do that what I'm hoping to illustrate with this 46:39.930 --> 46:48.670 graphic is these little data centers right here are just Azure data centers alone 46:50.210 --> 46:56.590 and some of these are general but these ones that have labels for example so like 46:56.590 --> 47:01.370 this is US government Virginia and this is US government Department of Defense 47:01.370 --> 47:07.910 East that's Department of Defense that's Department of Defense that's US 47:07.910 --> 47:15.150 government Arizona or Texas and then no this is US government Arizona and this is 47:15.150 --> 47:21.170 US government like South whatever so what I'm trying to point out to you is that as 47:21.170 --> 47:29.070 it stands today there are already regional data centers in the United States that 47:29.070 --> 47:38.150 are 100% dedicated to government means and what I'm trying to point out is you 47:38.150 --> 47:43.390 have basically one or two control nodes per region so I'm just gonna kind of 47:43.390 --> 47:53.670 point out that government nodes are are in key areas but also at borders one of 47:53.670 --> 48:01.110 these was supposed to be a government DC I forget which one is which so really if 48:01.110 --> 48:06.830 I'm sitting here saying okay what are we gonna do well we're gonna ingest we're 48:06.830 --> 48:13.290 gonna watch phones move through cell towers and mine that information for 48:13.830 --> 48:22.990 insights and I've shared this with Gabriel he runs Libre software or Libre 48:22.990 --> 48:23.950 Solutions Network 48:24.680 --> 48:41.560 I'm just gonna do it this way right yeah Libre Solutions Network so he runs that 48:41.560 --> 48:53.440 and I was talking to him the other day about project Genesis which is a smart 48:53.440 --> 49:00.540 5g network which basically means this is an internet network a 5g network that's 49:00.540 --> 49:06.560 built 100% on Amazon so when I'm sitting here telling you the end game could be 49:06.560 --> 49:12.080 we're gonna watch phones move through infrastructure that's what this is like 49:12.080 --> 49:20.460 literally real-time analysis of network traffic to create these kinds of 49:20.460 --> 49:28.700 trends that I'm talking about so I just kind of want to say if if the strategy 49:28.700 --> 49:34.680 is model behavior and implement it regionally then really what it kind of 49:34.680 --> 49:41.240 boils down to is okay if they see a lot of people moving towards bars and they 49:41.240 --> 49:46.940 want to discourage drinking or they see a lot of uptick in red meat sales and 49:46.940 --> 49:51.440 stuff like that the capability and this is just modest this is just for 49:51.440 --> 49:57.700 illustrative like illustrative purposes the capability is there to host these 49:57.700 --> 50:05.440 LLMs like there there's some kind of analytic capability regionally 50:05.440 --> 50:14.540 available with Azure and AWS data centers acting as amplification points 50:14.540 --> 50:22.380 throughout the country to make that happen to Terry's point yeah I I personally 50:22.380 --> 50:32.940 don't see how they would roll out social credit scores carbon allowances and 50:32.940 --> 50:40.080 things like that simply because well yes the capability exists for like real-time 50:41.000 --> 50:46.760 interdiction of transactions so you know you make a transaction here and the 50:46.760 --> 50:57.040 model says you know hey too much red meat in this area the Walmart app might come 50:57.040 --> 51:00.520 back and tell you oh it's out of stock so you wouldn't be able to buy it through 51:00.520 --> 51:04.340 the app you could walk into the store and you would you'd find out you've 51:04.340 --> 51:09.420 been like misled and then you can just buy it with cash or whatever since you 51:09.420 --> 51:14.440 don't have to use a phone app to purchase things but really it cut your purchasing 51:14.440 --> 51:22.360 power has to be tied to a digital something in order to control it and 51:22.360 --> 51:32.780 right now debit cards and cash don't really have that level of control like 51:32.780 --> 51:40.280 yes MasterCard is doing you know carbon scoring and analyzing your purchases and 51:40.280 --> 51:47.760 stuff like that but they can't just turn your ability to purchase things off 51:47.760 --> 51:53.120 without pinging your phone and stuff like that so just kind of culturally and 51:53.120 --> 52:03.280 technologically we are not there but it me so one thing I do kind of want to 52:03.280 --> 52:07.140 provide you guys with is if we're talking about like how would something 52:07.140 --> 52:13.320 like that really even work in the first place it's really just kind of an issue 52:13.320 --> 52:21.180 of what I'm trying to say here the capability exists already because of 52:21.180 --> 52:29.420 this like this being the way things work to stop you it's just an issue of 52:30.380 --> 52:36.960 everything has to be integrated and at that scale like we haven't thought we 52:36.960 --> 52:43.700 don't in we don't as a the technology industry doesn't have a solution for that 52:43.700 --> 52:49.960 yet that yes there are API's and integrations and things like that but 52:49.960 --> 52:55.500 those API's and those integrations have to be orchestrated there has to be like 52:55.500 --> 53:00.540 standards and that's why you're seeing interoperability being the big buzzword 53:00.540 --> 53:07.540 because we don't have that interop we can't say regional data center says 53:07.540 --> 53:11.940 there's too much red meat therefore we're going to send a signal to Walmart 53:11.940 --> 53:17.920 Kroger and Target to say hey stop advertising to your customers that 53:17.920 --> 53:24.620 red meat is available in store through the mobile app or to a butcher or a farmer 53:24.620 --> 53:32.120 saying hey actually you're gonna you're gonna provide 20,000 units of beef instead 53:32.120 --> 53:39.440 of 35,000 units of beef if that makes sense that's not there yet and that's 53:39.440 --> 53:45.000 where things so when people are telling you like that's not possible that's 53:45.000 --> 53:50.420 that's what they're saying because we it's it's getting the people in real life 53:50.420 --> 53:55.800 coordinated with the systems and then it's also coordinating the systems 53:55.800 --> 54:00.760 themselves and that's a bitch of a thing to do and then you also have to look 54:00.760 --> 54:09.980 at the data-basin aspect of it which is it is a significant engineering 54:09.980 --> 54:17.380 challenge at even the hundreds of millions of rows and so if what you're 54:17.380 --> 54:25.000 going to tell me is you're going to try to you have to database at some level 54:25.000 --> 54:30.680 transactions be that someone bought a train ticket someone bought meat someone 54:30.680 --> 54:36.260 posted the social media post whatever somewhere that has to be database and 54:36.260 --> 54:44.180 if you're telling me you think you can handle 8 billion people being transaction 54:44.180 --> 54:51.500 logged throughout their life and I'm using the word transaction because law at 54:51.500 --> 54:57.860 this point and I can't quote you which one but legislation is being written 54:57.860 --> 55:07.620 around transaction so a leading to be right it's just not sustainable like in a 55:07.620 --> 55:12.600 cloud you can ask for a database to be provisioned and the database will be 55:12.600 --> 55:17.000 provisioned but you still have to do like the partitioning and the 55:17.820 --> 55:22.960 performance tuning and stuff like that and the cloud provider will make sure 55:22.960 --> 55:27.760 that the servers and the database software and stuff like that is working 55:27.760 --> 55:34.960 so you can do that job but someone still has to manage the data and if you're if 55:34.960 --> 55:42.960 you're it's like a dog eat it's the snake eating its tail at that point where 55:42.960 --> 55:48.400 if you think you're going to have an AI model tell you when you need to 55:48.400 --> 55:56.940 partition a database or create a read replica or replicate it to another 55:56.940 --> 56:03.900 region or something like that you're sorely mistaken because all AI does is model 56:03.900 --> 56:10.400 existing behavior and predict it it's a model of existing behavior and it 56:10.400 --> 56:16.680 predicts what will happen next so the example I like to use when I talk about 56:16.680 --> 56:23.300 it is LLMs model the behavior of communication it predicts words through 56:23.300 --> 56:32.560 tokens and it doesn't understand the context or the implications of what it's 56:32.560 --> 56:43.660 saying it just predicts for example that at the end of TH belongs E and the word 56:43.660 --> 56:51.960 V was it is the complete token that should have come after the period for 56:51.960 --> 56:56.760 example right like you're starting a new sentence and you're about to talk about a 56:56.760 --> 57:03.880 new object the bus the car whatever just however the tokens managed to be all AI 57:03.880 --> 57:12.380 is doing is predicting and assembling that prediction so from a strategy 57:12.380 --> 57:17.380 perspective unless there's something we don't know about that's not gonna work 57:17.380 --> 57:24.620 and you still need people to operate these footprints and scale these systems but 57:24.620 --> 57:34.500 even then the technology we have nowadays cannot scale to millions on billions 57:34.500 --> 57:42.580 of people we can't we have no concept of we're gonna have 8 billion identity 57:42.580 --> 57:50.560 records with tens to hundreds of millions of database transactions rows in a 57:50.560 --> 57:56.020 database for what all those people have done it's just unsustainable like the 57:56.020 --> 58:03.000 data piece by itself is unsustainable and then you get into operating that and a 58:03.000 --> 58:08.620 lot of what people are saying is true the capacity is just not there for that 58:08.620 --> 58:15.640 level of compute and let's say you solved the capacity problem because we're 58:15.640 --> 58:23.220 only two iterations in to we've literally basically where we're at is we're at the 58:23.220 --> 58:30.000 rudimentary stage of what they want to do so as far as like technology as a 58:30.000 --> 58:37.060 whole for the past like 60 years or thereabouts yes it's gotten more 58:37.060 --> 58:43.200 sophisticated but in relationship to what it's gotten more sophisticated in 58:43.200 --> 58:51.100 relationship to what it was at its base but in terms of what it is now we're 58:51.100 --> 58:56.020 grasping at straws trying to figure out how do we do the technocracy thing and 58:56.560 --> 59:01.900 we just simply don't have that figured out and we're trying to handle that with 59:01.900 --> 59:07.560 things like Ansible Terraform manage services automation data centers and 59:07.560 --> 59:13.760 stuff like that but that just doesn't scale like you know you can maybe operate 59:13.760 --> 59:19.940 a project with a couple million users and stuff like that but you've got to 59:19.940 --> 59:25.820 look at Facebook you know like look to Facebook for how they operate and that's 59:25.820 --> 59:31.020 not even commerce like it's a pain in the ass for them to just send you cat 59:31.020 --> 59:39.280 memes and pictures and stuff like that so that being said one of the other things 59:39.280 --> 59:48.320 is only self-driving EV cars and taxis so to be fair I mean that stuff exists 59:48.320 --> 59:55.720 like California and stuff like that but again the problem with this is AI is 59:55.720 --> 59:59.700 not sentient it never will be sentient it doesn't have a soul it's just 59:59.700 --> 01:00:05.260 predicting things whatever so at the end of the day what you have is a vehicle 01:00:05.260 --> 01:00:13.780 predicting when it needs to break accelerate turn signal whatever and my 01:00:13.780 --> 01:00:19.560 understanding of AI is the longer you let an AI system run the worse the data 01:00:19.560 --> 01:00:26.020 gets it just keeps feeding back into itself and it becomes crude and like 01:00:26.020 --> 01:00:31.400 very rigid and useless and that's kind of why this system that's kind of why 01:00:31.400 --> 01:00:37.680 these systems we talk about depend on having like users giving them 01:00:37.680 --> 01:00:43.120 information like that that's why you have to be using chat GPT and stuff like 01:00:43.120 --> 01:00:48.780 that because you are the fresh data source so we've kind of seen like Tesla 01:00:48.780 --> 01:00:59.620 self-driving fail I think Waymo taxis are what they are they do kind of work and in 01:00:59.620 --> 01:01:06.420 terms of like will they replace cars I mean it's more of a question of these 01:01:06.420 --> 01:01:14.120 people are not going to not let it right it doesn't matter if it works or not 01:01:14.120 --> 01:01:18.240 the point is just that you don't have a car and if you end up giving in 01:01:18.240 --> 01:01:23.240 crashes and stuff like that because a model is becoming progressively dumber 01:01:23.240 --> 01:01:32.080 because it's basically in a feedback loop that ain't it it's just not but I 01:01:32.080 --> 01:01:36.460 don't know I'm not in the machine learning AI space right now but as you 01:01:36.460 --> 01:01:41.880 guys are aware that's kind of what I'm doing and so on and so forth universal 01:01:41.880 --> 01:01:43.100 basic income 01:01:48.240 --> 01:01:51.080 Andrew Yang is I think his name 01:01:55.080 --> 01:02:03.540 yeah this guy tried this back way back just look into him he's tried UBI never 01:02:03.540 --> 01:02:08.760 materialized there have been studies on the outcomes from universal basic income 01:02:08.760 --> 01:02:17.260 and it was horrible it didn't work out and I hate that I don't have like 01:02:17.260 --> 01:02:22.460 scholarly citations for you guys but if you just look into these things the 01:02:23.800 --> 01:02:34.040 effect on human behavior is just wretched it's so bad so yeah look into that 01:02:34.040 --> 01:02:39.180 because I don't want to misspeak but basically UBI as a concept is not 01:02:39.180 --> 01:02:43.380 compatible with humanity people want to work they want to work for their money 01:02:43.380 --> 01:02:49.360 and have their things and if you change that formula all hell breaks loose 01:02:49.360 --> 01:03:30.880 um neural implants so I want to see if I can get back I mean neural link is there 01:03:30.880 --> 01:03:41.340 there's trials and right now people can draw control control computers and 01:03:41.340 --> 01:03:48.660 things like that I don't know man honestly I'm probably not the right person to 01:03:48.660 --> 01:04:03.260 talk to about it but I my gut tells me that in the same way that we have 01:04:03.260 --> 01:04:14.400 managed to take radio signals and essentially blast binary over it and 01:04:14.400 --> 01:04:19.960 make it make sense we can probably do the same thing with the emf that people 01:04:19.960 --> 01:04:25.960 that are brainwaves put out it's just a matter of what is what does that 01:04:25.960 --> 01:04:30.100 interface look like and where do we pick up that radiation but to be honest 01:04:30.100 --> 01:04:34.440 with you that's not something I'm interested in I don't study this so I 01:04:34.440 --> 01:04:40.120 can't really say anything so that's neural implants and then yeah like I 01:04:40.120 --> 01:04:55.610 said so just to maybe kind of point this out is if you look at models models do 01:04:55.610 --> 01:05:04.130 tasks right so we have a model and I don't I don't like I said that just 01:05:04.130 --> 01:05:11.290 set this computer up so I can't show you like show anything but the point I guess 01:05:11.290 --> 01:05:16.750 I'm trying to make is that the way things are explained to us publicly 01:05:16.750 --> 01:05:22.790 general artificial intelligence and super intelligence is just not a thing like 01:05:22.790 --> 01:05:30.250 you just can't fucking do it all of these are our models that maybe do like 01:05:30.250 --> 01:05:35.750 a couple different things but the point I'm trying to illustrate is we model 01:05:35.750 --> 01:05:42.350 behavior like test text classification token classification and the token is 01:05:42.350 --> 01:05:49.910 like a person place thing word whatever object detection whatever and these 01:05:49.910 --> 01:05:56.590 models best case scenario you're running them on like edge compute or 01:05:56.590 --> 01:06:03.190 something like that and you have a cluster of models running so like maybe 01:06:03.190 --> 01:06:13.390 what you could do is excuse me you could have a bunch of these models like 01:06:13.390 --> 01:06:18.410 basically upfront what I'm trying to say is is basically you can have these 01:06:18.410 --> 01:06:23.730 models train them to look for behaviors and do something based off those 01:06:23.730 --> 01:06:30.770 behaviors and stop it at a one-to-one level so for example if this person is 01:06:31.550 --> 01:06:36.890 you know making a request for a purchase of meat you know you can have a model 01:06:36.890 --> 01:06:43.530 come in and say like oh this person has or this region has too much meat 01:06:43.530 --> 01:06:49.290 decline that purchase or whatever but these are essentially the way I think of 01:06:49.290 --> 01:06:56.930 it like synapses but they're not interconnected and so you know depth 01:06:56.930 --> 01:07:04.950 estimation can't as at least as far as I know readily talk to object detection so 01:07:04.950 --> 01:07:11.690 like you can't throw a ball or what we're trying to figure out right now is a 01:07:11.690 --> 01:07:21.030 robot can see a ball and it might singularly know that a ball is a ball but 01:07:21.030 --> 01:07:26.250 it doesn't understand like the context behind like a football baseball basketball 01:07:26.250 --> 01:07:32.070 whatever there's nothing to connect those facilities I'm trying not to like 01:07:32.070 --> 01:07:37.850 babble but I'm trying to explain the point that you know if you're how what 01:07:37.850 --> 01:07:41.890 is the depth away from that ball for me to catch it if someone throws it and 01:07:41.890 --> 01:07:47.470 they're like 20 feet away from me how do I catch that ball there's no 01:07:47.470 --> 01:07:53.510 integration of all these different tasks that a model kid or that these 01:07:53.510 --> 01:08:01.330 different models can do to create an integrated prediction capability like 01:08:01.330 --> 01:08:05.070 at the end of the day the best thing you can do is chain a bunch of 01:08:05.070 --> 01:08:11.230 predictions together to predict that a ball is 20 feet away from you and the 01:08:11.230 --> 01:08:17.930 robot needs to move its hand here to terminate the ball moving through the 01:08:17.930 --> 01:08:25.610 field and catch it so to speak but it's never going to have like second or 01:08:25.610 --> 01:08:32.130 third order context at least the way things are right now like AI is just 01:08:32.130 --> 01:08:41.950 getting worse handling recall as it is right now humanoid robots replacing 01:08:41.950 --> 01:09:02.870 workers mother flip in Neo so you think what they're called yeah so he's 01:09:02.870 --> 01:09:08.750 bringing up like or he's asking about humanoid robots replacing workers my 01:09:08.750 --> 01:09:15.130 understanding that's that's darn if the robot comes in that if you open it like a 01:09:15.130 --> 01:09:26.590 sarcophagus like I'm just I'm just gonna use this as an example literally man 01:09:26.590 --> 01:09:32.590 it's 499 a month to have this robot with a monthly subscription start a 01:09:32.590 --> 01:09:36.570 productivity package and standard delivery so basically what what they're 01:09:36.570 --> 01:09:40.910 saying is we're gonna sell you a robot and we're gonna tell you it's like AI and 01:09:40.910 --> 01:09:46.570 it's doing these things all by itself but your 499 a month is paying someone in 01:09:46.570 --> 01:09:53.670 India to tell me off teleoperate this robot that's what that is like it's not 01:09:53.670 --> 01:10:00.530 AI robots can't wash dishes right it can't take out the trash it's your 01:10:00.530 --> 01:10:05.950 trash bag is too heavy for a robot like this best case scenario you can do a 01:10:05.950 --> 01:10:17.710 really crappy job folding your laundry but it's not going to robotics right now is 01:10:17.710 --> 01:10:23.710 not in a state where it's like practical it's a luxury it's early adopter and 01:10:23.710 --> 01:10:30.510 even then like it's mostly vanity if we're being a hundred percent honest so 01:10:30.510 --> 01:10:43.490 not right now I guess not right now is is my take on that so that being said that 01:10:43.490 --> 01:10:50.110 that's kind of my spiel I apologize that it's not as in-depth as I would want it 01:10:50.110 --> 01:10:57.770 to be I'm I'm not a content creator or a brand I'm a person with some knowledge 01:10:57.770 --> 01:11:06.910 working on stuff and I believe that I can comment on these things and if you'd 01:11:06.910 --> 01:11:15.690 like me to clarify stuff more than happy to do that but yeah whoo an hour and 01:11:15.690 --> 01:11:24.190 11 minutes yeah I did some yapping but yeah so that's the spiel if you have 01:11:24.190 --> 01:11:28.790 specific questions ask and I'll try to give specific answers even if that means 01:11:28.790 --> 01:11:36.790 I need to research but yes overall like yes some things can be done like they 01:11:36.790 --> 01:11:43.110 can just do daily databases and stop things from happening but scale and 01:11:43.110 --> 01:11:48.190 coordination are a problem and if we're being honest about where 01:11:48.190 --> 01:11:56.930 technology is technology is really maybe in its third iteration from being 01:11:56.930 --> 01:12:06.710 basically worthless to have to becoming something that provides fabric to build 01:12:06.710 --> 01:12:12.770 with so yeah let me know what you think cool