 All right. So you should be able to see what we call the add on now. So that's the table of contents on the left. And if you've played with it, I won't bother you with that part, but the live search feature is in contrast to conventional search conventional search just front ends the wiki search mechanism that exists on jsoftware.com and the forum search mechanism that already exists on jsoftware.com so you can search for, let's say slash colon we and it takes a little bit and it comes back with 213 results in J programming, which you can load up by clicking three results in J beta J chat J source and a bunch in J general, which you can which you can load up the way progressive search or live search handles that same query. A slash code. And you get, I'm going to go ahead and shrink the browser so we can have a little more room to look at the results, yet color coded to column results, and the color coding is that rust. So for example this hit right here examples of the great operator. Rust is forum hits so great behavior is a forum hit examples of great behavior is a format and you can click to load those up on the right teal is wiki hits. And the way this works is we've got a, I've got a local sequel like full text index database of all I think it's about 5000 wiki pages, and all 120 odd thousand forum posts. As you type so I've just type of look for slash co I'm sorry and then on the left is snippets keyword in context. I look for slash co slash co. I get many fewer results because those two tokens occur together much less frequently than it occurs once I've got a slider for the years so right now I'm looking at back to 2021. But I can take that back to 2019 2018. I can go all the way to all documents which goes all the way back to 1998. And now I've got paginated results page three page for page five. I can also say I want only the wiki pages and get those. I can all I can search for English as well as code so if I had we had Roger's last name, I can get posts from him and about him. And of course the one page from J4C that discusses the slash co slash co trick, which I think is described as having an economy that burges on sorcery, which I can only can only agree with. So that's the story. The problem is the local database that I'm going against here the local sequel like full text index database that I'm going against here is one and a quarter gigabytes, which from some perspectives is enormous. On the other hand, I think I mentioned in one of the emails. You can't even buy an SSD with less than 256 gigabytes anymore if you want one you have to make it yourself. In that sense, from a storage perspective this database is a rounding error. If we can deliver updates to it that is content for new posts content for new and change wiki pages incrementally and just have the basically maintain the index locally on each client machine, which I think we can I think I know how to do that with AWS again very then we can deliver what we're calling live search the live search feature of the J wiki viewer, I think in a pretty straightforward and economical fashion.