WEBVTT 00:00.000 --> 00:15.000 Okay, it is really my honor and pleasure to introduce Alas Speaker, who is Mr. Ben Pate, who 00:15.000 --> 00:23.520 I've got to know a tiny bit on the Fediverse, and through events like 34 and his general 00:23.520 --> 00:29.280 enthusiasm for making cool staff to self-problems, which I think is something that a lot 00:29.280 --> 00:36.880 of us relate to. So, Ben, you are the final speaker on the longest social that webbed 00:36.880 --> 00:42.680 every day that we've had at Foss Dam, I believe it may also be your first time in this 00:42.680 --> 00:44.680 part of the world. 00:44.680 --> 00:45.680 The whole continent. 00:45.680 --> 00:46.680 Yeah. 00:46.680 --> 00:50.920 So, really warm welcome, please everybody to that for Ben, I'll leave it to you. 00:51.920 --> 00:52.920 James is tiny. 00:52.920 --> 00:54.920 Okay, awesome. 00:56.920 --> 00:58.920 Hi, I'm Ben. 00:58.920 --> 01:04.520 I'm doing a bunch of stuff, I'm working on a whole bunch of projects, and it doesn't all 01:04.520 --> 01:11.520 make sense when I try to explain it. So, this presentation kind of is going to wander 01:11.520 --> 01:16.320 a lot, and I apologize, but I know it's going to come back around eventually and I hope 01:16.320 --> 01:19.920 it makes sense to you guys, because it makes sense to me when I go to sleep. 01:19.920 --> 01:25.520 I'm the creative emissary, which is a Fediver server, it's open source, anyone can install 01:25.520 --> 01:30.760 it, and emissary is the platform that other services can run on top of, and I'll show 01:30.760 --> 01:34.920 you a couple of those. 01:34.920 --> 01:42.960 The news of the world is dark, and I put that directly in the hands of social media and 01:42.960 --> 01:47.600 the internet, and the good thing about going last in a day like this is everyone's already 01:47.600 --> 01:53.000 said all the cool things. I can just kind of put them together a little bit. I really 01:53.000 --> 01:59.080 think that distributed networks are the way out, and so this is my way out. This is the 01:59.080 --> 02:04.440 one thing I'm going to work on for my whole life, because I need to feel like I'm doing 02:04.440 --> 02:10.800 something to make things better. There's a scene in Lord of the Rings where Frodo has just 02:10.800 --> 02:15.840 been, oh, we all speak high Elvis here. Okay, good. 02:15.840 --> 02:21.960 Cinderin, I'll translate for the normies, but I figured that there's this one scene where 02:21.960 --> 02:26.320 Frodo has just been given this horrible task, and he's like, I don't want to do this, 02:26.320 --> 02:31.200 and Gandalf says, well, we don't really get to choose, but we can choose what we do with 02:31.200 --> 02:36.960 the times it's given us, and so that is what I want to do. I want to choose what I'm 02:36.960 --> 02:42.360 going to do with the time that's given me. This is another thing that really sticks in my 02:42.360 --> 02:47.560 head a lot. I went out and counted not everybody, but I went to Google, and there's 8 billion 02:47.560 --> 02:52.920 people, and so when I look at what I want to do with the time that's given me is I think 02:52.920 --> 03:04.160 that the Fediver should serve everybody. And thank you for clapping so much, because that's 03:04.160 --> 03:09.760 not always met with like cheers. There's a lot of people who have really good reasons to 03:09.760 --> 03:16.200 want to keep things small. They came here. I feel like we're a network of misfits and 03:16.200 --> 03:25.040 outcasts, and as I am as well. But to the people who say that we want to keep it small, 03:25.040 --> 03:32.200 I say, no, it needs to be big, because you can't just make something beautiful, and 03:32.200 --> 03:38.520 then keep it to yourself. If this is worth what we say it's worth, if it is as good, and 03:38.520 --> 03:43.160 the force for change that we want it to be, then it has to be available to everybody. We 03:43.160 --> 03:49.360 can't afford to just serve 1% of the population. And at this point right now, if every 03:49.360 --> 03:56.960 Fediver's server in the world, 10 times it's number of users, we would serve maybe 1% of 03:56.960 --> 04:06.800 the population. That's not enough. So what do we do? This is a model for the technology 04:06.800 --> 04:13.800 adoption cycle. It's pretty well understood that how people come into using any sort of new 04:13.800 --> 04:21.000 technology. There's this thing called the chasm, which basically represents this idea 04:21.080 --> 04:27.360 that different groups of people need different things out of every new kind of technology. 04:27.360 --> 04:34.520 And in Fediver's terms, the innovators are you guys. And then the next group of people 04:34.520 --> 04:38.800 coming down the line wanting to use this, they're going to need different things out 04:38.800 --> 04:43.560 of the software than what you need out of it. Innovators fall in love with the technology 04:43.560 --> 04:48.960 themselves, but early adopters, they look for new stuff, but I got to have a good use 04:48.960 --> 04:56.400 case for it. So what's preventing the Fedivers from crossing that chasm? Fortunately, we've 04:56.400 --> 05:03.280 seen many other software packages platforms that don't cross the chasm. I asked Google, 05:03.280 --> 05:07.440 why did you fail? And the answers were the same across the board for all of these. And 05:07.440 --> 05:14.120 I double-clicked it. So you missed my cool animation. But they all failed for the same 05:14.160 --> 05:20.120 four reasons. Low user engagement, user experience issues, lack of a killer feature, and 05:20.120 --> 05:24.880 operational failures. I want to focus on the first three because I'm so short of time. I'm 05:24.880 --> 05:30.280 already like five minutes behind. But if we put these into a little chart and we say, 05:30.280 --> 05:35.920 well, what can we do about each one of these things? Here's my proposal. I think user engagement 05:35.920 --> 05:42.280 requires compelling content. There's also relationships and are my friends there and everything 05:42.280 --> 05:47.880 else, but I've got to have a reason to come to this network. And I think that user experience 05:47.880 --> 05:52.200 is something that people are going to judge across the entire Fedivers. User experiences 05:52.200 --> 05:56.600 isn't just what color of blue are you using for your button, but it is, how do I get from 05:56.600 --> 06:02.840 point A to point B? And killer features have to be something that the big networks can't replicate. 06:02.840 --> 06:07.000 It's a fundamental structural thing that they can't do because they're always going to out 06:07.000 --> 06:11.240 on us. They're always going to have more people and resources and time and everything else. 06:11.240 --> 06:18.200 So we have to come up with something that fundamentally a centralized network can't do. 06:18.200 --> 06:24.280 So I feel like I know about this a little bit. I didn't talk too much about my projects yet, 06:24.280 --> 06:30.520 but bandwagon is a site for musicians to post their content. And through bandwagon, I talk 06:30.520 --> 06:35.400 to hundreds of musicians and they all have really the same thing. They want to sell their stuff 06:35.400 --> 06:39.960 online. They're working, maybe they just want to pay for the new guitar, maybe they're trying 06:39.960 --> 06:44.760 to make this their side gig, but they need to be able to pay, or they need to be able to sell their 06:44.760 --> 06:51.400 work in a place that's designed for them that isn't going to charge them too much for it, 06:51.400 --> 06:57.400 and isn't going to go down that instead of vacation rabbit hole. And whenever I mention money 06:57.400 --> 07:06.360 on the Fedivers, someone says that this isn't the place for that, but the thing is it's not about 07:06.440 --> 07:11.560 these money on the Fedivers or not. It's more about how do we put money on the Fedivers. We already 07:11.560 --> 07:17.800 have plenty of ways to pay for things and buy things, everything else, but can we do it in a way 07:17.800 --> 07:25.560 that respects people at an individual level and doesn't put the profits for the platform first? 07:27.560 --> 07:34.520 When I talk about being judged as a single ecosystem, what I mean is this. In the early 2000s, 07:34.520 --> 07:43.400 Jake Mealson was the monotheistic deity of all of user experience, and he said it's a really 07:43.400 --> 07:49.400 simple idea, but users expectations for your website are formed on other websites. They don't 07:49.960 --> 07:54.120 they don't come to your website and want to read the manual, right, and that really hasn't 07:54.120 --> 08:00.440 changed. So I think that the same thing applies to the Fedivers, but when people come to the Fedivers, 08:00.520 --> 08:06.120 their expectations are formed out there, not on your Fedivers app, not on the client, not on your 08:06.120 --> 08:11.800 website. Everything that happens on the web starts out there, and then maybe comes to you, 08:11.800 --> 08:19.560 if you do the right thing, but you can't start with the experience being here or else that user experience 08:19.560 --> 08:26.520 dies. I couldn't see the person, but I hope that there's still here, someone was asking about 08:26.520 --> 08:32.440 share buttons. Share buttons and signups and all these things that they've come up several times 08:32.440 --> 08:39.080 through the day. I went to share this to get their buttons just as an example of it, and they've 08:39.080 --> 08:44.360 even got dig on there. I don't think that the new platform has launched. They've got this thing called 08:44.440 --> 08:53.720 Plurk. You people know that? The hell is Plurk? I will derail the whole conversation, but what is 08:55.720 --> 09:02.600 I picked it was a social network where stuff didn't go up and down because left side to side. 09:02.600 --> 09:11.000 That was the killer feature. All right, and this I'll bring up this is why MSR exists because someone 09:11.080 --> 09:20.920 wants a side-to-side fee. But if I can't do this with the Fedivers, and this has already been pretty 09:20.920 --> 09:28.920 well described and documented, getting something to share or like on the Fedivers from where I already 09:28.920 --> 09:34.760 am out on the website, that's very difficult to do. Fortunately, there's this brilliant software 09:34.760 --> 09:42.920 developer in the United States. He has been working on something that so activity intents are 09:42.920 --> 09:49.320 my attempt to fix this, and activity intents basically are a way for a server to publish. Here's 09:49.320 --> 09:56.360 a list of the things that you can get to remotely, and then a client out on the web can post a link 09:56.360 --> 10:01.560 that post that little button that gets me back to the right place on my own server. I don't have to 10:01.560 --> 10:08.280 worry about OAuth connections or any other additional APIs. All the interaction happens on my home 10:08.280 --> 10:13.240 server, but activity intents connects those things together so that I can get where I need to be. 10:14.520 --> 10:20.600 Activity intents is just an example of connecting the Fedivers more tightly together. This same 10:20.600 --> 10:26.840 idea applies for search, discovery, conversations, all of that stuff. We have to behave like a single 10:26.920 --> 10:35.000 organism, not like many interconnected individuals. The last thing about the last thing on our 10:35.000 --> 10:40.760 checklist is it must be a strategic advantage. I think that the most strategic advantage we have 10:40.760 --> 10:46.360 on the Fedivers is it should not stuck. You shouldn't be stuck on one particular instance. 10:47.560 --> 10:53.080 All the corporate for profit networks that they need you to stay on their thing to see their 10:53.080 --> 10:58.280 ads and to pay them more money. I don't care if you're using my software or my servers. I just 10:58.280 --> 11:04.280 want you on the Fedivers because that is a part of the solution I'm working for. There's a bunch 11:04.280 --> 11:09.080 of other things that I think that we can do. I think that we can do better jobs serving micro 11:09.080 --> 11:14.040 communities with targeted applications. I think that the Fedivers has an opportunity to be 11:14.040 --> 11:18.920 something like a universal inbox. I think we're always going to do a better job of credibility 11:18.920 --> 11:27.800 trust and safety. But to go back into the freedom to leave, we have this technology right now. 11:27.800 --> 11:34.360 We can do this right now, but just people aren't quite implementing it yet. The W3C is working on 11:34.360 --> 11:41.240 the Lola data portability standard, which allows you to pick up your whole profile, your whole 11:41.240 --> 11:47.960 friends and move over here to a new server. If we can get that implemented, I will have QR codes 11:47.960 --> 11:53.400 and stuff for you at the end. Get out your cameras in a minute. But if we can get that implemented, 11:53.400 --> 11:59.880 then we have a strategic advantage that prevents intensification and actually helps solve the 11:59.880 --> 12:05.400 instance-chooser sign-up situation where I come in. I don't know where to go. Well, here's a list of 12:05.400 --> 12:11.880 15 servers in your country. With Lola, all you have to do is start somewhere. Anywhere, it doesn't 12:11.880 --> 12:17.080 matter. You can always move to the server that matches you better when you figure out this whole thing. 12:18.600 --> 12:25.000 So, that's my checklist. That's what I think would make the Fediverse more competitive and help us 12:25.000 --> 12:31.240 to grow in this area. Bring creators, avoid the pitfalls of the past, make lightweight apps for 12:31.240 --> 12:39.960 micro-communities, activity intents, FEP-3B-08, please implement it. Better search and discovery tools, 12:40.680 --> 12:47.240 being able to move from server to server, unified inbox for small digital spaces, 12:47.240 --> 12:53.960 and better trust and safety. So, now let me take a second and show you what I'm doing with the time 12:53.960 --> 13:00.360 that I have. The activity pub, the Fediverse story, usually goes something like activity pub is the 13:00.360 --> 13:07.000 core. We've got massed on, does that for micro-blocks, peer tube, add something else for video, 13:07.080 --> 13:13.240 and then PixelFed, add something for photos. You can do articles with right freely, but I keep hitting 13:13.240 --> 13:20.360 double buttons. I'm sorry. But how much is in the middle? How much is like redone again and again 13:20.360 --> 13:24.680 and again. And this is what Fedify is trying to solve. This is what bonfire is trying to solve. 13:24.680 --> 13:31.160 Can we do something that is a little more flexible? Because these have a, oh sorry. These applications 13:31.160 --> 13:36.520 take a lot of extra stuff. There's so much in the middle of there. It takes years to build these 13:36.520 --> 13:43.560 applications. And so when you start looking at it in those terms, can't we do something that combines 13:43.560 --> 13:49.480 all of these together that maybe doesn't do everything that each one does, but gives us enough of a core 13:49.480 --> 13:56.120 that we have something we can build customizations on top of. And that's the primary work that I'm 13:56.120 --> 14:02.520 doing. It's called Emissary. And I've built several test apps, example apps, and I want to show 14:02.520 --> 14:10.280 you a couple of those. Bandwagon is, as I said, it's a, it's a site for musicians to post their music. 14:10.280 --> 14:21.400 And right? And everyone has brought tremendous creativity to this. I'm blown away. And in 14:21.400 --> 14:28.760 really good Fediver style, there's some wacky stuff. But you people can bring all sorts of music 14:28.760 --> 14:36.680 and creativity to the Fediver so you can share and like online. Bandwagon has a really cool 14:36.680 --> 14:43.000 search engine that doesn't just let you look from music, but it lets you hear, let's search for 14:43.000 --> 14:49.320 metal. It lets you follow those search results as an activity intent. So right here, I can click 14:49.400 --> 14:56.040 this button and then I will get essentially a pop up that says, do you want to follow this? 14:56.040 --> 15:02.040 And you'll get any time someone posts on that tag, you'll get those results in your newsfeed. 15:03.960 --> 15:13.000 Bandwagon also works with the indie beat, which go Kirsten. Kirsten is a complete rock star 15:13.000 --> 15:18.600 and I'm sad that she couldn't come all the way across the the ocean to be here. But the indie 15:18.600 --> 15:24.360 beat radio is a radio station that's playing music that was opted in by bandwagon artists and they 15:24.360 --> 15:29.320 even just released a indie beat TV. So now they're doing music videos as well. 15:30.600 --> 15:39.480 That's bandwagon. Then I did Atlas Maps, which is a social mapping app that lets you annotate 15:39.480 --> 15:46.360 different places in time and space in the world. I made a demo here of this is Boulder. 15:46.600 --> 15:50.200 Is that the bookstore? Oh, that's Triton. Triton is the best most hippiest 15:50.200 --> 15:56.040 bookstore in all of Boulder. Here's another one. But I can go and put annotations on the map 15:56.040 --> 16:02.040 and then share that with my friends. The coolest thing about Atlas Maps is I built this in six 16:02.040 --> 16:06.600 weeks and most of that time was actually spent building in a whole bunch of new geolocation 16:06.600 --> 16:12.520 services that I hadn't had to use before. So it uses the same federated search engine that I have 16:12.520 --> 16:17.720 in bandwagon. It just looks different because now it's all displayed in the different UX on the map. 16:18.520 --> 16:24.040 And then I can even share search results in a QR code with a friend and then they can look at 16:24.040 --> 16:30.040 that and follow themselves in this particular place in time. I was also building something called 16:30.040 --> 16:36.040 Quartilicious, which is going to be something like Patreon or Substack where you can subscribe 16:36.040 --> 16:41.720 to a person and using the same payment processing that we have in bandwagon, you can actually 16:41.720 --> 16:50.840 buy a premiere feed from that. But then Evan here, we'll talk about that. I think you get the 16:50.840 --> 16:59.400 idea. Emissary is one server that does many, many things. And each one of those is programmable. 16:59.960 --> 17:05.800 I can basically post anything I want on a GitHub and then download that into my emissary 17:05.880 --> 17:14.760 and use those templates. It's mostly programming, but it's programming inside of a very tight 17:14.760 --> 17:21.960 box. And so I'm trying to make it so that we don't have runaway plugins or processes that we 17:21.960 --> 17:28.600 can't quite trust. Everything runs inside of these little action steps that do the actual work. 17:28.600 --> 17:32.680 So it makes it really easy for you to mix and match and plug and play the stuff that you want. 17:33.000 --> 17:41.000 In 2025, we rolled out the online payments. That uses your own Stripe account. I'm hoping I can 17:41.000 --> 17:49.000 have other payment processors in the future. But this is the mechanism that lets us share things 17:49.000 --> 17:57.240 or charge for one time download or possibly a membership subscription. And then at the end of last 17:57.240 --> 18:05.240 year, I rolled out what as far as I know, the first real implementation of Lolo. So I want you to 18:05.240 --> 18:10.680 leave my servers. Please go make your own server over there and then use the data portability to pick 18:10.680 --> 18:16.440 everything up and put it all down in a new place. I think that is, again, the best thing we can do 18:16.440 --> 18:24.120 for the future of the Fediverse. Going forward, there's a lot. There's really a lot. One of the 18:24.120 --> 18:31.000 big things that I had planned was to make a better inbox, a better experience for small spaces again, 18:31.000 --> 18:37.320 a way to have small communities that stand out from this larger worldwide network that we have. 18:38.920 --> 18:44.200 And then, and then Evan came along and said, hey, well, you do some into encrypted messages as well. 18:44.920 --> 18:54.760 And so I am really excited and kind of honored that I'm doing this. But with funding from the 18:54.760 --> 19:00.120 sovereign tech fund, with leadership from the social web foundation, bonfire and emissary are 19:00.120 --> 19:11.480 going to be building end to end encrypted messages. And there's a lot of technical stuff in there. 19:11.480 --> 19:15.480 And people are come out with a whole bunch of questions, well, we'll do this or we'll do that. 19:16.520 --> 19:21.560 The basic thing is that MLS messaging is an industry standard that has been very, very well thought through 19:21.560 --> 19:29.160 by people who know so much more cryptography than me. It is the right kind of foundation to be doing this on. 19:29.160 --> 19:36.040 And then we're building it into activity pub so that right alongside of my existing network and with my existing 19:36.120 --> 19:43.400 contacts, if they support end to end encrypted messages, everything is just already ETE. And if not, 19:43.400 --> 19:49.880 then we can use regular direct messages. So when I go back to my checklist for 2026, 19:50.600 --> 19:55.000 that's what I'm a series doing. And all the things that I believe are going to help us to grow 19:55.000 --> 20:03.400 the Fediverse are there. And then I got an extra bonus encrypted messaging is another killer feature. 20:03.400 --> 20:11.000 I hadn't even thought of. So that's what I'm doing. It's been a crazy year. 20:15.160 --> 20:21.400 I think the last thing I want to leave with is what can you guys do. And here's the things that I know 20:21.400 --> 20:27.160 of that I'm involved in. And if anyone is interested, this is something that we're building right now. 20:27.720 --> 20:32.120 And I'm going to put status updates on this page about where we are and what's happening. 20:32.840 --> 20:41.160 It will be usable. Well, it will be something that we hope other platforms will join us and 20:41.160 --> 20:48.920 do this as well as soon as we have worked out how all of the specs go. If you are a developer, 20:48.920 --> 20:54.440 no developer happens to be the head of communications for a large software platform. 20:55.000 --> 20:58.920 I really want you guys to look at activity intents because I think that this 20:59.560 --> 21:07.800 helps bring the Fediverse much more closely together. If you are involved in any software platforms, 21:08.680 --> 21:18.520 please, please, please look at data portability. The spec for me was not super easy to look at. 21:18.520 --> 21:26.520 It's still a lot of brainstorming. But that's okay. The core ideas are there. And if anyone wants 21:26.600 --> 21:33.480 help with this or with with any of these, I want to be a resource to try to make these things happen. 21:34.760 --> 21:40.680 And then the last thing is if you are an HTML developer, and that's all you know. Well, 21:40.680 --> 21:47.320 HTML and JSON, you can build a completely working federated app on the Fediverse today 21:47.320 --> 21:53.400 if you can figure out how to use emissary. I want to work with anyone who is interested in building 21:53.400 --> 22:00.360 their own custom things to see if emissary can be the platform that would work for you. 22:03.560 --> 22:08.200 I don't know what that QR code is. Oh, that's my master on. So if you'd like to connect 22:08.200 --> 22:17.080 on a master on, please do so. I just made it. So the last thing is that whatever you do, 22:17.080 --> 22:24.440 whether it is working with the things that I've put up here or your own software packages or 22:24.440 --> 22:29.000 your own communities or anything else, I really believe that anything we can do that makes the Fediverse 22:29.000 --> 22:36.440 better is a win for humanity. And so if this is the last thing I get to say up here for the time 22:36.520 --> 22:41.720 that's given me, let's do that together. Thanks. 22:50.360 --> 22:55.800 Now, all of the speakers in my favorite, but I have to say that was an amazing way to 22:56.600 --> 23:02.760 to close us out today. And from the applause I just heard, I think that's a shared view. 23:03.080 --> 23:09.080 Does anybody have a question for Ben? Ian has one and then there's another one? 23:11.720 --> 23:16.680 I'm going to have to read self-ish question. So as someone who understands 23:17.640 --> 23:26.360 service side setup and also is a front end designer, could I build the apps that I've been thinking 23:26.360 --> 23:34.920 about for us? Okay, let's talk. So the templates that JSON that I showed, that is like the skeleton 23:34.920 --> 23:41.480 and then within that skeleton you have HTML files that would represent the different views 23:41.480 --> 23:47.400 of an object that we're looking at. You also can set up the data schema a bunch of rules about 23:47.400 --> 23:53.560 how it behaves and you can even map things in and out. So if you want to create custom JSON 23:53.560 --> 24:01.240 LD, that can be driven by that JSON config. Thanks for the talk. I just looked into 24:03.160 --> 24:07.400 your Go activity platform implementation and it says it's going to explode my computer 24:07.400 --> 24:12.280 who uses and we're currently exploring with loudly, we also right and go. So what would 24:12.280 --> 24:17.960 be the first steps to maybe integrate MSRE for our entry point activity panel? 24:18.280 --> 24:26.520 I think the first thing is to install it and play with it. Look at the templates that are there. 24:27.560 --> 24:31.800 I've tried to do as much documentation as I can without knowing what people were going to want 24:31.800 --> 24:39.160 documented. But there are a number of different end points into it. You could also drive the 24:39.160 --> 24:43.800 it's MongoDB in the back end so you could just write stuff into MongoDB and it would show 24:43.880 --> 24:50.280 up straight on on the MSRE site. Did I answer your question correctly? Cool. 24:54.680 --> 25:05.400 Okay, so the last two talks kind of have a point at which they sort of overlap and meet. 25:05.400 --> 25:13.400 So with bandwagon, right? One of the important things for musical artists is live performance 25:13.480 --> 25:19.880 for a whole bunch of reasons, right? Not every musical artist, right? But a lot of people, 25:20.600 --> 25:27.320 the live performance is where you really get the spark, right? In addition to the cash. 25:28.840 --> 25:35.720 And so that clearly has an interaction with what mobiles on and other people who are doing 25:36.600 --> 25:46.360 events do, right? So have you thought about how that fits together? And then in terms of, 25:46.360 --> 25:53.080 if I just a little bit extra, in terms of what Alexander was talking about, in terms of 25:54.120 --> 26:04.520 importing events, could one say use MSRE to build on to an existing platform to bring it on to the 26:04.520 --> 26:11.640 Fediverse, so it could federate with mobiles on. Do you think? Yeah, so federating between apps 26:11.640 --> 26:18.280 is certainly a possibility. Typically, you wouldn't take one app and put it on top of another, 26:18.280 --> 26:23.720 because they have so much of their own. That whole thing that mess I showed up there, like it's 26:23.720 --> 26:30.920 it's a mess. But I wanted to show you one thing. Can you see it? Yeah, so bandwagon actually does 26:31.080 --> 26:41.800 have a calendar. Bandwagon actually does have a calendar. And it is, at its best, it might become a 26:41.800 --> 26:49.480 third of what mobiles on does. But it does allow band members to post information about where 26:49.480 --> 26:52.280 they're going to be and when they're going to be in links to the tickets and everything else. 26:53.320 --> 26:58.440 Now, this search engine could certainly pull in things from other sites, and that is something 26:59.080 --> 27:05.160 that it is intended to do. Right now, it can understand other MSRE sites, opening that up to others. 27:05.160 --> 27:07.160 We just got to do another thing on the task list. 27:09.560 --> 27:16.680 No, no, absolutely not. No. The birds have had that right. That's what the question 27:17.960 --> 27:23.080 I could be there and we could talk about it. Right. But the feature will not. Right. That's what I 27:23.080 --> 27:28.840 thought they're going to miss me. Yeah. I'm going to try. If I'm out of bed, I'm an American, 27:28.840 --> 27:34.360 and I'm waking up at like two in the morning to do all this thing. So I might be passed out 27:34.360 --> 27:42.280 tomorrow. I don't know. All right, listen. We're just coming up to the top of the hour. Thank you, 27:42.280 --> 27:46.760 band again. So much for coming over. Thank you for coming. Really, really appreciate it.