WEBVTT 00:00.950 --> 00:04.880 In this video we're talking about Osint tools and website tools. 00:06.870 --> 00:07.800 At some point. 00:07.800 --> 00:13.650 Your favorite tool, whether it's a website or a tool that we go that we're installing or becomes part 00:13.650 --> 00:20.130 of the Trace Labs or Seaside Linux or any other distribution, it is going to break at some point. 00:21.300 --> 00:22.500 So. 00:23.880 --> 00:28.860 That's just to warn you that yes, your tool will most likely break at some point. 00:28.860 --> 00:34.620 It may get fixed at some point it may not, depending on how severe the issue is. 00:34.770 --> 00:39.360 It's not always the fault of the manufacturer or whoever programmed those tools. 00:39.450 --> 00:46.980 A lot of times websites will make changes on their end, and it makes it harder for people making investigation 00:46.980 --> 00:48.480 tools to. 00:49.230 --> 00:54.210 Get around that and still be able to collect the information that they're looking for. 00:54.210 --> 00:57.930 Things like Facebook constantly tweaks their security. 00:58.020 --> 01:02.220 Uh, Twitter slash X, Instagram and so on and so forth. 01:04.200 --> 01:11.730 So a absolutely prime example is when Twitter got taken over when it got bought out. 01:12.510 --> 01:19.770 The Twitter site, the servers, the API which these tools will hook into. 01:20.820 --> 01:25.560 Came crashing down in a pretty spectacular fashion. 01:25.560 --> 01:33.870 So there's been a there was all sorts of issues, all sorts of turmoil, wholesale changes to how Twitter 01:33.870 --> 01:40.530 works, uh, how information that's getting out there, the API in itself, we can see here Twitter 01:40.530 --> 01:46.830 API keeps breaking even, even for developers paying $42,000 for it. 01:46.980 --> 01:49.590 Um, API response codes and errors. 01:49.590 --> 01:52.170 How a single engineer brought down Twitter. 01:52.590 --> 01:52.890 Um. 01:54.350 --> 01:56.600 In other issues with the. 01:57.610 --> 02:07.390 Uh, CEO at the time, making changes, sweeping changes to that platform that caused a lot of issues. 02:07.390 --> 02:13.750 And most of the tools that were that we used for OS and for Twitter no longer worked. 02:13.810 --> 02:20.260 Matter of fact, most of them still don't work anymore, and they probably won't as long as they continue 02:20.260 --> 02:23.200 to keep locking down Twitter and making it. 02:23.350 --> 02:27.160 Well, I'm going to say pretty unfriendly for investigations. 02:29.870 --> 02:35.510 That's why whenever a tool breaks, we have a couple of options. 02:35.510 --> 02:39.140 We can go and we can try another tool, which may work. 02:39.530 --> 02:46.370 But if that doesn't work, also, the one thing you could always rely on is your methodology. 02:46.940 --> 02:55.370 So no matter what they do to Twitter for the most part, or X or Facebook or Instagram or Snapchat and 02:55.370 --> 02:56.570 so on and so forth. 02:57.680 --> 02:59.960 Get your methodology down. 03:00.230 --> 03:06.080 Figure out how you're going to tackle the problem and take that manual approach again. 03:06.260 --> 03:12.620 Because again, those APIs could break, they could lock things down and so on and so forth. 03:12.620 --> 03:19.460 But for the most part, you can always rely on good old fashioned methodology to get you through and 03:19.880 --> 03:23.360 to gather that information during your investigations. 03:23.360 --> 03:25.130 So keep that in mind. 03:25.130 --> 03:32.420 And again, if you're if the tool breaks, that's not a stopping point for you. 03:32.420 --> 03:39.590 Again, you can find another tool or better yet, fall back on your methodology for your investigations. 03:40.010 --> 03:46.070 So this was about tools and websites and those things breaking. 03:46.070 --> 03:47.390 Thank you for watching. 03:47.390 --> 03:48.770 I'll see you in the next video.