Hey guys, real is the game here today.   I'll be doing a world bucks gift card giveaways All right, so let's begin with this All right, man. We're a where we going. Okay, where are we going? Oh, yeah, we're here. Hey Hold up. We're here with my boy right here super saying God Look at him. Oh my god. Hey, he's a savage bro. He told me he's in school right now Yeah, so he's in school right now, please some roadblocks with this Oh, oh roadblocks super boy joined us. What's up, my boy? Hey, we got two guys here. All right. Oh and Anita's in here.  Well, we felt 51 meters. How many oh how many meters did you fall? There's 65.  Oh, I broke more bones. So I kind of wonder man But so hey you want to try to climb the mountain? It'll be epic. It'll be epic if we jump off from the top. We can we go? Oh, yo, that person jump from way up there I didn't see him. Oh You can go like first person on this too. It's super weird.  Wait, look at me. Look at me. Wait, why yeah? Hey, I'm like a name first person though. Oh first person All right, it's kind of weird wait We have to get like on the same level like you can't look around with the camera like only with the oh there you are, bro Hey, what's up, man? How you doing, bro? Hey, bro over here. Just smiling. You know Look at that beautiful view on the back kind of like like Minecraft.  Oh Right man, I don't know how to get up there. Let's try to climb find a way. Let's get up there somehow Wait, can we go up this way? I'll just follow you. This is hard Oh Look at the body Dude the body would just follow the path the body just fell through. I mean fell by I just press follow me and then keep jumping Bro, you know the way okay, let's go.  I know I'm not gonna make it. I'm just gonna throw myself. I'm gonna throw myself Look down. Look down. Oh, wow. This is the farthest I can go. All right. Oh, look at super saying Oh, okay. He caught himself. All right. I'm going bro That sounds painful man Dude Dude, you hear the sounds of the game like how the bones actually snap that's pretty Like very detailed. It's making my arms hurt. I broke 23 bones.  I saw a tunnel here like a cave. So let's go check that out Hey Super Saiyan's still here. Oh, I don't know how long he has to go back to his class I'm telling you like try it out. It's kind of weird. Wait, how do you do it? Uh, just click on the eye right there on the left Oh, oh, okay. Like you don't need it like you you can't use the mouse at all just the arrows like Oh, I just felt okay.  Oh, yeah, it's very difficult Bad idea. That is a bad idea Okay, let's go up here Oh, man This didn't take forever Let's not go all the way to the top not all the way Yeah, but I mean almost to the tippy top and then let's jump straight there. Oh, yeah, but what if it like teleports us Yeah, that's how I was saying like, so where should we stop? We're almost at the top though I think we should go to the top. It's gonna be epic. Okay, you go first though. I don't want to get teleported down You're the you're the bait. All right, so we're gonna see if he gets teleported and not down Okay, oh, did he make it? He made it. Well, he made it through. How come I didn't he made it? Oh He's a wizard, bro Okay, you teleported us that is not fair. Okay, let's just throw ourselves man Up over this You have to buy it first that's like oh, we haven't bought it. Oh my god, we haven't bought it Okay, okay Change map. Yeah. Oh my god. We I didn't even see that. We had no idea 25 get the second one All right, we got it. Nice. Okay. How do you switch you just pick it? Uh, I think so. Do you just pick it? Is that considered? All right main menu No, I'm just gonna press start Yeah, it is. Oh, no, no, it's different. Look, look up the stairs up here. Oh, it is different Where were you? Okay. Nice. I'm right next to you We're all lost and confused. Oh, this looks cool.  Oh there you go. What? I wasn't I wasn't there. You saw it. Oh, well because the camera Oh my god Dude, this is so awesome Timing all the way up there It's all the way over. Would you ever do this like in real life in real life? Would you guys do this in real life? I don't know bro. This is kind of scary Oh Okay, we can't go. Oh, we have to buy that too. Okay, so let's just go until I'm just gonna. Yeah, I'm out Oh, oh my god. Yeah, I'm painful. This must be Where am I uh second Second oh my cap's round. Oh, hopefully yeah, there's oh like the astronaut. No I thought the astronaut wanted to go to the moon. That's the Go splatter south down there. Where are you at? Where? All right, hold on. How much is the next one? Is it like a hundred thousand? Let's go all the way up though and like let's not go to the end. Yeah, we'll jump off from like the top All right before we get to it. Oh wait, can we jump down here? Oh, yeah, look we can. Yeah, it's where we came from. Let's try this one It's like going down this viral tunnel. Oh my god Hi, but I mean just to see you Oh, the homies is chilling He's still playing with us. That's funny. All right, let's go up there then Geronimo We'll just stop J. R. Frost though Oh I know right Dude come on How you running fast on me? Oh, yeah, it's the animation Your head looks funny. Where are you going? You gotta come on. Hey, where are you going bro? We're going the wrong way All right, so let's stop. Oh my god He is lost. Let's stop right here. You have to buy the next one.  Oh, I'm still going. Oh, I'm still going. Okay. Yes Oh my god Okay, how much is an extra? Let's let's check it out. Let's check out the third one. Where's the third one at? Okay, uh, wait you can't go 100,000. I could afford it. I'm pretty sure you can't too, right? Are you at 70? Come on, bro All right, I'm leaving Just see you in the next world buddy. Okay. Now we're up here. Oh my god. How high up is this? What is that guy doing? I think he's contemplating about life right now. He's looking over the edge He's like should I do it or not? Don't do it buddy I'll give you some robux. Oh my god.  I want to go to the top Look to the top top. That's gonna be awesome I found you Round summary, dude, we got a concussion this round. That's very bad I wonder if you can actually oof. You think so? Yeah Maybe at the top top, huh?  What? Why did you jump back up? Did you guys saw that? Dude their bodies like flew back up What are you at? You hear yet? Almost there 100,000 All right, we can't go to that one yet. So let's just jump off from here. Hopefully we'll go all the way down Please no, okay. No We kind of messed up Wait, where are you?  Yeah, where are you at right here? Yo, yo, what's up, man? Yo, all right. Where are we jumping off from? I tried jumping off from the top, but like I don't know if you can go to like the very top up there because No, they'll teleport us go as high as possible I mean just trying to get a good angle because if you go up there, you're gonna get stopped here This is kind of a good angle right here. Yeah, this let's go. Yay. Oh my god Look, there's something right there.  I got 432. Oh, that's my top so far average break 25 Let's try a little bit man in the same place in the same place. That's gonna be impossible But let's try it. Wait, where are you at right here? All right, can you jump at the same time? All right, but All right, wait, we need a good angle again. Let's go over here. Not that I all right. Let's go back there Yeah, I didn't like the spot.  Wait for me. I'll run behind you, man Go right next to me. All right. Go look at me. Look at me first All right. Let's look at each other first person.  I love you, man. Oh my god. Where are you? Should we jump first person? I'm gonna jump first person. All right, cool Okay, ready?  This is very easy first person, man. No, it was a bad job Dude, let's say 491 little breaks 491 dude, I got splattered right in the beginning That was not cool. It was the first person, bro. You couldn't guide it. Yeah, let's do it again It's landing in spot 250 k's next one Okay, let's go. We got some work to do my god. That's a lot of money. You have to be very dedicated. Where are you? Super saying god, how are you feeling? You're good. You're good, my boy.  You're all right, man. Oof Don't stop up here. Look at the body just flying by. That's so funny, man Play again I landed right into this Hey, he did the challenge 511 total break 511. I think you passed my top one They were your way. Don't jump yet We're here. All right, three two You jumped a little higher than me there And I stopped that boulder that boulder stopped me. Oh seven oh eight beat that seven oh eight seven oh eight Five thirty nine. We wow. Oh man. Oh, yeah, dude. Are you okay, bro? That's a lot I don't know man. I'm surprised we didn't die there All right. Well say bye to the camera All right, there you go, man All right, you guys. Well, thank you guys for watching. Thank you guys for the main support If you guys enjoyed the video make sure to slap the like button if you new to the channel Make sure to subscribe and I'll see you guys in the next one. Bye


religious, pu object indeed, thebruity, and ultramani.  dhpan impür hene parfi kombvi of ebrabap 약간 fun. 外 ar infor admonchriRETVar vendeto reast  fotele .... .. My favorite soldiers are very hard target, without asking for buffs else they can achieve to give a replaces. These people aren't required to that the passive. The ISA is very cool that they don't stand a chance to give those as additional buffs. It's crushed Jackie, who centrally has터�esting skill levels basically. Pro groove is very powerful. It will help with your opponents Ginae. This is the fight. croar lit m k main model


or all manuals that refer to a certain error constant. Such search keys can even be combined. So if you don't know exactly whether it will be a function type or a variable type or a function argument, your search term will show up in. You just give multiple macro names and search for the same keywords and all of them at the same time. If you don't know at all what kind of thing you are searching for or how it might be marked up, you can use, you can search across all the search keys. Remember, if you don't supply this any, then it just searches in the title line. In, if you supply the any, then it searches in everything that's marked up in any way. You can even use regular expressions. If you exchange the equal sign by a tilde, then it uses regular expressions for searching in those keys. You can construct complex search queries. For example here, I am saying, I want to see all section one manuals that either contain TBL in the title line or contain a name EQN. Obviously I'm interested in graph extensions and it shows me a list of matches but only from the matching section. So terms are you joined with O and if you specify a section with minus X, it's appended with end. You can also make the end or O explicit like in find. You can even use parenthesis to group it. So for example here I'm saying, I want section one manuals having terminal as a word in the title line but which also have a mention of either research unix or old BSD. So I want traditional terminal tools and it gives me indeed a list of tools that have been around for a long time. Such stuff is working basically since this year. In the meantime we can see that later or even in the web interface that it works. Not only the input format, so I've shown so far has been improved but also the output format. Traditionally you always get the name and the section of the manuals that match because that's what you need here. This first column that's what you need to actually look at the manual with man. By default you would get here after the dash, the title line but you can explicitly request some other macro not the ND macro, some other macro to be shown. For example here I'm saying, I want to see manuals having wireless in the title line but I don't want to see the title line. I already know that contains wireless. I want to see the kernel configuration directives from these manuals. So I can see on one with these wireless adapters see at first sight whether they attach at PCI or at cart bus or wherever with one command. Traditionally I would have to do apropos and then look with man at each of them separately. And now we come to the surprise topic of this talk. It's a thing that wasn't completed when I proposed the talk that has been done really during the last two or three months. Traditionally the mandoc toolbox didn't include the man program itself. Our philosophy was mandoc is for formatting and man is for displaying. But we have changed that. The next mandoc release will also contain the man program so that all mandoc man apropos what is have the same user interface and they all do the same steps now. They first decide how to interpret your command line arguments, then build a list of matching manual pages, decide which kind of output provide to you depending on your options, maybe spawn a pager and finally loop around the list of pages and produce an output for each of them. Let's look at the ways the command line arguments can be interpreted. If you specify the minus L option then the command line arguments are just file names. So it takes each file name, maybe formats it, maybe shows it. That's the default operation mode for mandoc. As mandoc always worked. If you call it as man in the default mode, the command line arguments are names of manual pages. So it looks up just like traditional man did, those names in the file system and shows you the manual pages. If you use the F argument it does what is used to do. So look for names as complete words. If you use the minus K it supports the full apropo syntax. What is new is that no matter which of the command names you use, you can always use all of them options. So you can even say what is minus L and it will work just as mandoc. So you just need to remember one set of options. All the traditional database selection options work with all the commands. So to show you one example, probably just do that out of the presentation. You? Yes, probably a good idea. Let me see. Not there. It's right. No, still more. So usually you do something like, oh no, that's a bad one. I always get the, anything. Usually I get a manual just formatted for output on the terminal. Now with the new tool, I say man minus thtml, html monkey typing. I get it formatted as html. So I put a links minus standard in after it. Here I have the manual as html. Firefox doesn't work like that, I think. No, Firefox. But anyway, or another thing I say apropo mdoc, I get a list of manuals that match. I say apropo, which didn't work in the past. I give it an output option that was only supported by man in the past, but not by apropo. I get the file names. Man, sorry. Man minus v graph always worked. You get the file names instead of the formatted pages. Now apropo minus v also works. So having all combinations of all options is quite handy without having to remember something else for each command. So these database selection options, the traditional ones, no work with all the commands. The output options, minus a doesn't show just the first manual matching, but all the manuals matching one after the other. So I could say apropo some keyword with minus a and I get all the matching manuals right away so that in my less, in my pager, I can search through all of them. Minus h is a traditional option from man to just shows the synopsis. Now also works with apropo. I've already shown minus w to show the file names and even the parser and formator output options now work with all of them. Like for example, what is maybe relatively, I guess I've already shown an example with minus t of thtml. And finally the c output option to suppress the pager is also there for all. So that's the unified interface we now have and a nice anecdote about it is that a few months ago I presented in Ottawa at BSD Cannes and I presented a list of things to do five or six entries and this unified interface was not on the list. I had no idea I would do it. But then on the beginning of August, so about six or seven weeks ago, Paul Onishok of Alpine Linux asked, well, why don't you do man or do you do man? And almost without thinking, I wanted to reply, no, we don't do that. Then I stopped and thought, well, why not? And realized the code was almost all already there. I just had to reshuffle it a bit. I needed to do two releases first. So it took about two weeks until it was finished from the idea on August nine, first working version still in the same months and then in August 26, I had it integrated in OpenBSD. Admittedly in OpenBSD, it's so far only integrated for Apropos, what is, and Mandok. Man is still the traditional tool. Some bugs need to be fixed there. To not get too technical, I will be a bit shorter on these two slides. One of the problems we still have is what a name is. You expect that when you say man something, it shows you the manual page for something. So the manual page that is called something dot one or so. So the traditional man only looks at file names. The new man looks for names in more places, like in the prologue that you just learned how to write in the name section, in the synopsis section and all that will show up as manuals in man now, which can be annoying. For example, I happen to have the GNU core utility installed. Now when I take man LS on OpenBSD, I get the GNU LS manual because it also has LS in the name section. That's obviously bad. That's the thing I need to fix before we can enable that. And there are a few more things. One very nice thing that Kristaps did two or three years ago is a minus I interactive option. That's the following. You run an apropo command. You get a list of possible matches with numbers in front and then you say, oh, I want to see number five. Just type five, enter and get the manual page without going back to the shell in between and having to retype the name and possibly mistyping it. That will probably be integrated, but it's not done yet. And there are some problems with man conference so on, I'll cut that here. What is probably more interesting for you is that it not only works at the shell, typing interactively, but you can also do the full power of this semantic complex and searches on the web. So the best thing to explain that is probably a live demo. I have here, yes. Oh, let's do it a different way. I start from the open BSD site. I go to manual pages here, right on the open BSD page. What's wrong with it? Is that a problem with the network here or with... So this one works.  I don't understand. Okay, something is wrong with the network and I don't know what it is. So we can try again later maybe after the working phase I can try to do the demo again. Right now, let's just say, just explain it in words. You can enter the same apropos searches. You can enter at the command line into the web interface. So even if you don't have open BSD installed, you can do the semantic searches for manual pages. With all the good stuff I've shown before for the command line. It has a few additional features even compared to the terminal, of course, because it's on the web. It can do hyperlinks, both inside pages from one section to the other and across pages pointing from one page to the other. And there is additional potential that is not yet really used because the HTML elements have annotations stating the syntactic functions. So that could be used for CSS or for further markup. Right now, the markup on the web is only the same as that terminal, but one could add to that. At this point, I'd like to extend a special thanks to Sébastien Marie, a French colleague who did an extensive security audit of this code and reported to considerable number of security bugs that meanwhile have all been fixed, but that was quite useful to have. Yeah, so we already had the coffee break. I was planning to, yeah, we're right on time, planning to have a few minutes on system integration. And then the second working phase. So to speed this up, first, what is system integration all about? The traditional way is to either format all the manuals while you are building the operation system and installing pre-formatted manuals. Some operating systems do that. Or to install unformatted manuals. And then at runtime, when a user runs MAN, the MAN in the background traditionally calls NROV, the formator, to format the manual page and pipes the output to the user's pager. Now, quite some operating systems switch in this second way from using NROV to MAN doc, which is better because it's smaller, it doesn't use C++ in the base system, it's faster and many other things. The systems already having done that include OpenBSD and HATBSD. FreeBSD is about to do the switch. So I prepared something for in case there would have been any freeBSD developers here to explain in-depth what they still need to do to get there. I guess I will skip most of it, just a few points. The first thing they need to do is what some of you have done here. Try in the tree whether everything really builds with MAN doc, figure out the fatal issues, report the non-fatal ones to us and so on. Yeah, that's about the non-fatal. Of course, if you're doing the system integration, it's more important than if you are just doing quality checking to see that the output from MAN doc is really the same as the output from NROV because you don't want your manuals to change, you just want to exchange the tool. And then finally, you switch over the tree by exchanging the tool. At that point, it's important to do it right after a release when you have a long time to fix potential problems. Yeah, regression testing is not really interesting here for this audience because it's about regression testing of the tool itself, right? So much about base system integration, just very brief. Manual pages in ports, are you aware of what ports is about?  Some, but some are looking confused. It's, if you take software that is developed operating system independently and make it run on a particular operating system, that's, yeah. So in that case, you get very diverse manual pages written by many different people in many different styles using all kinds of unusual functionalities. So about 95% of them will work with MAN doc and about 5% will not work with MAN doc because they are using low-level NROV functionality that simply isn't implemented yet or will maybe never be implemented because MAN doc is not a full NROV processor. So you have to do something that those manuals that can't form it with your new base system tool MAN doc still can be looked at by users. You can't just run NROV and then you remain with 5% of manual pages that are still gone, simply gone. The OpenBSD solution to that developed by Mark Espie who is also here and who is giving a talk on porting in general. Is to add a flag to the port make file saying this port needs NROV for formatting and if that flag is set in the port build system pre-format the pages during the build and install the formatted version. If that flag is absent, just install the unformatted one so that it gets possessed at runtime by the usual MAN doc in the usual MAN doc way. That works quite well, very reliably, very simply. In OpenBSD, we did it in the way that first we marked all the ports having manuals as use graph to be on the safe side and then by hand checked all of them and switched them away from use graph. We have about 8,000 ports and 1,200 of them still use graph so more than 3,000 have been checked in the last three years and have been moved to use MAN doc. Yeah, okay, I'll skip that. Obviously we are also improving MAN doc all the time, fixing bugs, implementing new functionality that helps particular, here is a list of some macros and requests that have recently been implemented. Obviously that helps in particular for ports because manuals and ports are using lots of weird stuff. Oh, I didn't really talk about Mac what is because that's also more for operating system developers. If you switch over, if you pull graph out of the tree completely, FreeBSD will probably never do that because there are a lot of developers who think that having a real fully professional type setting system in base is important but NetBSD might do that at some point and you have to pay attention to a few additional things but again, as you are not changing the base systems, not go into the details here. If you're interested, you can read that later. Okay, so now, we have an opportunity for working a bit more. What would be especially interesting, if in the second phase, if you have a Unix system around where you can install the latest version of MDoc ML from CVS, to do that to really test the search tools, a few people said they expected in this tutorial more of an introduction to the philosophy of writing manuals in general and I talked to Chris Depps. He's willing to use this second working phase to give a short presentation on that after asking what exactly you need is certainly competent to do that right away and then I will have helped those people who want to try out the very latest search functionality to get that going. Of course, if you have started something in the first working phase that you think is really interesting, you can also continue that and try to get it to a state where you can send me patches that I can commit then. So I'd suggest that Chris Depps would get into this area and everybody who wants to join on more philosophical and groundbreaking stuff can join with them and people who want to test search functionality should probably show up that I helped them get started to get the latest MoDoc. If you have an OpenBSD current system, you already have it. So who has an OpenBSD current system? Okay, so you can do that easily. That would be the number of stars here so the number of stars here is about the difficulty so that would probably 8.4.1 or maybe 8.4.2. If you don't have that, who is interested to do that but does not have an OpenBSD current system? Okay, in that case, just take my notebook because on your phone it won't work and we don't need that right now. Just get over, I'll come back, just get over here to one of the terminals. Yeah, here this one, for example, use the shell and yeah, there you can. Okay, so I understand the remaining people are continuing the work that was interrupted by the coffee break, right? That's good, yeah. Okay, so and yeah. It's a fresh install from this morning so I did have to make what is, but yeah. Yeah, so at about the, it's now 16, yeah, it's now seven minutes after five. So at about 20, 22 minutes after five I'll start the wrap up. Giving you an overview of what the status in the various systems is and yeah. Okay, so you are good probably, you were good anyway. Okay, you are joining too? Yes, of course. Just come back, say at 22 or something like that. Then when you come back, guys. Yeah, yeah, I think we got ahead of those groups. We'll just continue mainly with chins and then do some examples or something a little bit. Yeah, yeah, I think that done is probably a larger project but yeah. Yeah, okay, it was just, it was the first thing that came to mind that had reasonably simple and not man-dog, man-page, so. Yeah, looks useful, yeah. Okay. Problems. Okay, you're actually getting mostly the same results because if a manual page is system-independent, it also shows up when you are asking for a bit specific architecture because it is valid for that architecture, yeah. Oh, I already fixed it. Yeah, I thought it was about a bit confused about, because in those cases, the bottom name is part of the sentence or the multiple authors. Okay, can you show one of the examples? Yeah, okay. Yeah, so in this example, it's part of the sentence and there's a period. Yeah, should I do this period, should I do it? Yeah. Is it part of the name or it goes the line itself? No, what you did is actually right. I only very briefly touched that. If you have trading punctuation with almost all macros, you can just put it as an additional argument at the end. Type the following, please type mandoc minus capital T, tree and now pipe to less, first the final name, of course. Type that to less. Like that, you see the syntax tree expanded. If you now go to the point where the author is, then you see that the author name itself, Steve Levine, is in the element, but it realizes that the dot is punctuation and puts it outside the element. So that's a feature of the mandoc, one of the advanced features of the mandoc language I only mentioned briefly. That is completely correct, yes. Basically, all the punctuation marks just go to the end of the list, yeah. Yes, so from the, wait a minute, from the perspective of punctuation, that looks perfect. However, the BR is a bit of a bit strange. Yes, but please show how that looks when you format it. Just mandoc file name and if you want, you can pipe it to less, yes. You have line breaks in there that may come as a surprise. The reason for these line breaks is that the AN macro can be used in the following way.  So you want a list of authors. That's the default mode. On the other hand, you could also have a text where the author- I saw there was, I checked it. Very good, yes, exactly. So here you have to put an AN minus no split in front, such that you get rid of these. Okay, so yes, that looks like you will have some touches to send me afterwards. Yes, of course. Oh, that looks strange. Oh, there are two ways you can do that. No, wait, you want to do what? You want to, ah, there is, that is the one thing where there is no option. So you can get from the man command to all other commands, and you can get from all commands to each other, but you cannot get from another command to man. There is no option for that. The reason is that I didn't want to introduce any new options. I only wanted to extend the existing options because I don't want to introduce more complication. So there is no option for saying I just want to see one single manual. Once I introduce the minus I option, you can use that. It may even work. Try man doc minus I pseudo, what it does. It says, no such file or directory. No, it's not yet implemented, yeah. So you found the one case where, so if you want man, you really need to type man, but all other directions, yeah. Good observation, yes. So you can get less in a loop so that we can keep looking at the file while we edit it. Because we first did it with cap, but we lose the format in that way. What I usually do is type something like the editor command, then a semicolon, then the formator command with a pipe to less. So what then happens is that, as soon as I exit the editor, it at once starts the formator and less. So I see the result. When I type quit, I'm back to the shell again, but then I can just recall the last command and run it again. That is quite convenient when editing. Of course you can construct a while loop, a shell while loop around it. That wasn't our first idea. But then you probably need a sub-shell, but usually you just do it the way I explained that. That's good enough. No, Parker Brothers is the name of a games manufacturing company. Yes, that's Barry Brachmann is the author name, I think. Finding stuff. Between what is and apropos, what is has a much more restricted command line syntax. So if you can only give words to what is, while apropos can use the full expression syntax I presented. And even if you give only words to apropos, then it searches for these words as substrings. So there might be trailing or leading characters. While what is looks for the word boundaries makes sure that there are no prefixes or suffixes. So usually the results from what is is a subset of the results from apropos, which is not really new. That's how it works for decades. That will give a lot of results, yes. It's basically everything that contains the word pearl in the title line. So this comma is a new line or I believe it's here. You actually know it matters. You actually have to leave it on the author name line because if you put it on the next line, there would be a blank in the form of the output because no, the internal mechanism to recognize it as trailing punctuation only works if it's on the same line. So if you end the line, then it's like the, here we are finished. So you have a trailing blank. And then the comma is something like the start of the next sentence. And that was, oh, would I usually do at that point? Yeah, that works. There is a trick to get a similar thing quicker. If you just say CVS up blank minus DP, small D, capital P, the, yes, like that. The options are not strictly required, but it's a good habit to use these options because it will give you new parts and directories. If you do that, it will report which files are modified and at the same time, check whether anything has been updated upstream. That's a very convenient way to find your own changes in the tree. Yeah, switching to a different source code management system is a bit tricky. Yesterday, I attended a tutorial on SVN and had the same experience. Everything is different. I'm used to both CVS and Git, but yeah. What was the contraction? I think it's called a contraction, yeah. So if there is only contraction, then it can stay as it is. Well, I say it may be, but if you have found it and even fixed it, then just include the patch and I'll see whether I can get it in with it. For example, if there are multiple patches in the same tree and they can be committed together, then it's not spam either. So no, I think in this case, so if you would already be a new developer who were going to commit it himself, then the usual advice would be to make sure that every patch is small and self-contained and only does one well-defined thing. On the other hand, these changes are relatively simple and straightforward and all of similar nature. So it's basically one thing you are doing. And in particular, since you're not going to commit it yourself, it's much less work to just send a single patch. And then if it needs to be split up, it's even less work for me to split it up myself if it needs to be split up. So just send me one patch, yeah. Okay, good. We're back in a minute. Where did Chris stop scared to? Yes, do you know? They're in the... Ah, you're coming back for the wrap up. Good. You have to flip up to the problem. Yeah. Yeah. Yeah, you would. Yeah. Yeah. Yeah. Yeah. Yeah. Okay. So, I'm sorry that I might have to reclaim my notebook, but it seems like it helped a bit to get here. Okay. Where is the mouse? What? Okay. Sorry, I confused my notebook by plugging in and out stuff. So you have two or three additional minutes before I can do the wrap up. Okay. So the small side session worked for you? Yeah. Yeah, that's a development notebook. So I have separate partitions for different parts of the source trees and the object areas and so on. Sorry? Everything was mounted is now checked. Yeah. Sure. Okay. So back in working order, mobile 1409 talk, PDF. And I guess I have to move this thing away. Yeah. Back in working order, page 50 or something. Okay. For the wrap up, I'm briefly going through, I'm going to go back to page 50. I'm briefly going through the various operation systems that this conference applies to and telling you what the status in respect with respect to manuals is in OpenBSD. We were the first operating system completely switching to Mandok and it's now almost four years that that graph is completely disconnected from the build and Mandok is the only documentation formator in the OpenBSD based system. So since October, 2010. And since April this year, we are having the full make what is. Yeah, that's a good idea. Thank you. Since April this year, we are having the full make what is apropo functionality that some of you have been experimenting with. So that's nearly a finished story. Of course, there are a few things still to do. I will come to that later in the very last slide, future things to do. Future things are likely to again happen in OpenBSD first. The second system to switch to using Mandok as the default formator was NetBSD. NetBSD also had Mandok in base very early already in 2009. Jörg Sonnenberger did that. He's in the room right beside in the NetBSD developer summit. Yes, he's here. Just saw him. And Jörg Sonnenberger and Thomas Klausner also support Mandok in PKG source. A portable, a porting system with supports lots and lots of different platforms. So that's quite important. The point in time when they switched was basically 2012 in one big step. The next thing NetBSD should probably do is figure out how to get semantic searching. But that's a rather big problem because right now they have full text search that is not semantic, but also using SQLite. So they have to figure out how to integrate the two searching systems, the homegrown one they did and the semantic searching. That would be tricky. You can be glad that you need not do it. Now, FreeBSD and Dragonfly both have Mandok in the base system. FreeBSD sends version 10. But in both FreeBSD and Dragonfly, it's only installed and not yet used by default. Semantic searching is not yet supported at all, not even as an option. The next steps then would be to update to the latest release, 1.13.1, and then to actually use it to format manuals. And unless they manage to do that, it's not much use talking about anything else for those systems. Ulrich Böhlein in FreeBSD has done a lot of preparatory work. Franco Fichtner in Dragonfly also, so they should manage to do it. Now, there is one more system that recently switched to using Mandok. Any of you have any guess what that could be? It runs on Apple. Kristaps has always tested it. I heard something else. Oh, I gave it away. Right, forgot about it, sorry. That's an amazing thing that happened there. Years ago in 2010 or 2011, two guys from Illumos briefly spoke to me and they're never again. And I thought, well, they are not doing anything. And then this July, just a few months ago, suddenly one giant commit happened. And they did all in one step. They imported Mandok into base. They switched from installing formatted manuals to unformatted manuals, and they switched from using graph as a formatted to using Mandok as a formatted, all in one commit, and it just worked. I have no idea how to manage to get, they managed to get such a giant switch working at once, but there weren't even many cleanup commits afterwards. Must have done a tremendous amount of testing. So right now, Illumos is the only non-BSD that is using Mandok by default. Minix, by the way, the Minix chief, like Professor Tannenbaum is here and is giving a talk, Minix has opened BSD, has Mandok in base because they have imported it from NetBSD, they have most of the NetBSD user land, but they are not using it and it is very old, it's three years old, I never updated it. Mac OS X has an old port, an old package from 2010, but it seems Mac ports it is, yeah. Oh, they have, oh, I didn't even know that. Okay, so if anybody is using, actually using Mac OS and finds a port, just tell me, I'm always interested in keeping track of who's using it to be able to actually help people. Well, so it definitely runs on Mac OS, and, but not very actively maintained. Recently I noticed, yes? One dot, one dot three, no. One dot three dot zero. Well, that's worse than prehistoric. I mean, everything that is older than one dot 11 is really, really ancient, like three or four years old. One dot. Okay, we can figure out that afterwards, yeah. Yeah, interesting. And I recently realized that there is even a cycling port for Windows. I never talked to the guy, Jakov Selkovitz, but I dropped him a mail but didn't receive an answer yet. So even for Windows users, there might be a way to get that, but I don't really know much about Windows so I can't help much there. Yeah, status in Linux. There's one Linux distribution that is very actively maintaining their port. Also has it for a long time, which is Alpine Linux. Alpine Linux, a small French distribution focusing on keeping it small and simple, also for embedded stuff. They have provided a lot of feedback. Then, of course, Arch Linux and Slackware Linux, both have ports. And recently, this April, a guy popped up who has basically prepared ports for everything, CentOS, DBM, Fedora, RIT, Sousa, Ubuntu. But of course, it takes a long time to get anything into those systems so we should probably speak again in two or three years whether anything has actually been imported, yes? There's also, if you install it, it won't... Okay, I never heard about that distribution but I will have a look. Oh, actually, that's not a good idea to replace graph because the main purpose of graph is a type setting system. So you use it for setting books or talks or something. Well, Mandok is a documentation system so it may well be that you need both at the same time. But yeah, it's just... Yeah, it's good that you shared. Just mentioned that you shouldn't do it that way because it might mislead people if it just stands like that. Okay, so possibly future directions. There are still quite a few of things I'd like to do. Of course, replace the traditional MAN implementation in OpenBSD with the Mandok one, which is more powerful. Switch the default output mode from T-asky to T-local. That's actually a very easy thing to do. It will not affect people who are using the C-local because we'll just do the same as before but it will be more convenient for people using a new UTF-8 local. Then I'd like to integrate pre-conf into Mandok that will especially be interesting for Russian and Japanese people who are using UTF-8 manuals in non-English languages will make the command line for running the formator much easier. And there is a lot of work going on conversion tools like the Libre SSL documentation is right now all in the Perl documentation format pod and we are converting it to M-Doc and Kristaps and myself are working on tools to facilitate that. That's of course related to Mandok. Some other projects of a similar way like providing tools to, some of you have started to do manual translations from MAN to Mandok, from MAN to M-Doc. There is also a project to use an existing tool by Eric and Raymond to couple that with M-Doc to get manuals translated from MAN to M-Doc semi-automatically you will still have to do manual post-processing of course. And I'd also like to do some low-level infrastructure work on Mandok that I'll not bore you with so there is still an interesting future. And finally I'd like to mention a few people who helped with this, of course Kristaps Johnson who wrote the tool in the first place a few years ago then Jörg Sonnenberger from NetBSD who helped write important code in particular in the initial phase a few years ago. There have been a considerable number of people from various projects who contributed patches Franco, Christos, Tzugutomi. Very important is the work that Mark Espi and OpenBSD has done on Ports integration. I think I wouldn't have been able to go anywhere with lots and lots of discussions with the OpenBSD manual maintainer, Jason McIntyre. The whole thing probably wouldn't have happened either without Theo Derrath, the OpenBSD project lead who invited Kristaps to commit the stuff otherwise I'd probably have missed the whole thing completely. Then thanks again to Sebastian Marie for the recent security check on the web thingy. The main people who helped porting are Thomas Klausner NetBSD who is always also in the room beside who did the NetBSD porting and Ulrich of course and FreeBSD. There were a lot more people in OpenBSD which I'm not all name who did various things to help us and a very long list, actually an impressive list. All these people reported bugs or suggestions that were actually acted on. So each of these names resulted in at least one commit. Yeah, and then I used lots of pictures. So, do you have any questions to finish the session? Anything else you should like to know about manuals? Kristaps? Who's written a manual page here? Who would if it were easier to do? Oh. Actually, I thought about how to use the macros correctly because I just started translating a man page to end up and I didn't really, it looks quite okay, but I guess I have a real warning and I have no idea what to do now. Even after looking at the mandoc portable manual. Okay. To make it look almost like the original man page I wanted to translate. So I managed to do that but now I've got four warnings and I'm pretty sure I've done something slightly wrong but yeah, it's not entirely clear how to do it right. Okay, so that's a. So to have like one complete man page way show had to remove different stuff. That's probably Kristaps tutorial, yes. Well, they would be, because it's so simple generally. It's like you either have a program, you have functions, function library or advice and it would just take you through the questions and it would actually get a meaningful document out there and just, you know, spit it out. Not for really using it after you have collected a bit of experience but for getting started that would be an interesting thing. Yeah. So that interestingly there is also something I'm taking back from here because my impression is that there are quite a few experienced people around here who do a lot of software development and that in contrast to what I think, the stuff is a bit less easy to approach than I thought and that maybe I even started on a level that was a bit advanced. So my impression is that there is really a need for basic documentation, basic tutorials and tools to get started. Yeah, so we should definitely clean up and improve your tutorials and what is already there is a recommendation. Besides the, if you want to read a bit more of it when you get home, then of course you have the slides to look at again. You have the write-up which has a bit, a lot more of technical detail. You have the tutorial but there is lots of stuff for us to improve in particular for beginners. That's interesting for me. Yeah. Anything you want to say for the wrap-up? Maybe what, anything you missed or anything you enjoyed particularly? Okay. Nice to hear that. Nice to hear that. Okay. Yeah.  Enjoy. Thank you.


What's up everybody, Jayz here for JaspysKaysBricks.com. We just sold out this team random that helped sell out Bowman, Chrome, Picker team number 21.  And you're guaranteed a team, guys. So 21 total spots, we're gonna take the 21 customer names, randomize them only. And whatever team you match up with is what you get. So whoever comes at number one gets the Guardians, whoever comes at number 21 gets the Blue Jays and all those teams in between. So dice roll it, randomize names, paste the names with the teams. And you see what you guys get. Here we go, roll. One is six seven times, lucky number seven. Good luck, guys. One, two, three, four, five, six, seven. Boom, seven. Chris Butler at the top, all the way down to Jason Kay at the bottom. Now let's see what you guys got. Match you up. This was a slightly 18 there. So Chris, congratulations, you got the Guardians. Joe with the Nationals, Jason Kay with the Yankees, Davis with the Mariners, Aaron with the Rockies, Chris Butler with the Padres, Emma with the Rays, Joe with the Rangers, Matthew with the Red Sox, Mike with the Orioles, Jacob with the Royals, last ball module, Devin with the Angels, Mike with the Mets, Travis with the Giants, Joe with the Braves, Jason Kay with the Cubs, Joe with the Phillies, Zagreb with the Marlins, Jason Kay with the A's, Clint Tigers, Jason Kay, Blue Jays. So there you go, guys. That's how you guys matched up. So in a separate video, we're gonna start the break, number 21's coming up next. Good luck, guys.


So we have one, two, five, six, seven, eight, nine, ten. So let's distribute our ones. Okay, one, two, two, two, two, two, two, two. Oh, that was supposed to be three. Four, one, two, three, four. Four, eight, twelve, sixteen. That's count, one, two, three, four, five, six, seven, eight, nine, ten, eleven, twelve, thirteen, fourteen, fifteen, sixteen, seventeen, thirteen, seventeen over here. So we brought ten, we have four over here, those should be fourteen. Huh? Yeah, that's seventeen. Four, eight, twelve, sixteen. One, one, one, one, one, one, one, one, one, one, ten. We have one ten and four ones. Fourteen and we have, we can put our R over our one remainder. We got to write a statement. Timer going off means that your time is up. I heard some really interesting conversations going on. I love the way that you were helping your partner, supporting each other's success. Great job.


Hello everyone, welcome to theCUBE's presentation of the AWS Startup Showcase. The theme this showcase is MARTEC, the emerging cloud scale customer experiences. Season two of episode three, the ongoing series covering the startups, the hot startups, talking about analytics, data, all things MARTEC. I'm your host, John Furrier. Here we're joined by Krista Wicklund, founder and CEO of UnitQ. Here to talk about harnessing the power of user feedback to empower marketing. Thanks for joining us today. Thank you so much, John. Happy to be here. In these new shifts in the market when you've got cloud scale, open source software is completely changing the software business, we know that. There's no longer a software category, it's cloud, integration, data. That's the new normal, that's the new category. So as companies are building their products and want to do a good job, it used to be you send out surveys, you try to get the product market fit, and if you were smart, you got it right the third, fourth, 10th time. If you were lucky, like some companies, you get it right the first time. But the holy grail is to get it right the first time. And now there's new data acquisition opportunities that you guys are in the middle of that can tap customers or prospects or end users to get data before things are shipped or built or to iterate on products. This is the customer feedback loop or data voice of the customer journey. It's a gold mine. And it's you guys, it's your secret weapon. Take us through what this is about now. I mean, it's not just surveys. What's different? So yeah, if we go back to like, why are we building unit queue, which is we want to build a quality company, which is basically how do we, how do we enable other companies to build higher quality experiences by tapping into already existing data assets? And the one we are in particularly excited about is user feedback. So me and my co-founder Nick and we're doing now the second company together. We spent 14 years. So we're like an old married couple. We accept each other and we don't fight anymore, which is great. We did a consumer company called Scout, which was sold five years ago. And Scout was kind of early in the whole mobile, you know, mobile first, I guess we were actually mobile first company. And when we launched this one, we immediately had the entire world as our marketplace, right? Like any modern company. We launched a product. We have support for many languages. It's multiple platforms.  And that brings some complexities as it relates to staying on top of the quality of the experience, because how do I test everything pre-production? How do I make sure that our Polish Android users are having a good day? And we found at Scout, personally, like I could discover million dollar bugs, but just drinking coffee and reading feedback. And we're like, well, there's got to be a better way to actually harness the end user feedback that they are leaving in so many different places. So, you know, what UNIQ does is that we basically aggregate all different sources of user feedback, which can be app store reviews, Reddit posts, tweets, comments on your Facebook ads. It can be better business bureau reports we don't like to get too many of those, of course, but really anything on the public domain that mentions or refers to your product, we want to ingest that data in this machine. And then all the private sources. So, you probably have a support system deployed, a send desk or an intercom, you might have a chat box like an ADA or and so forth. And your end user is going to leave a lot of feedback there as well. So we take all of these channels, plug it into the machine, and then we're able to take this qualitative data, which, and I actually think like, when an end user leaves a piece of feedback, it's an act of love. Like they took time out of the day and they're going to tell you, hey, this is not working for me or hey, this is working for me and they're giving you feedback. But how do we package these very, this very messy multi-channel, multiple languages all over the place data? How can we distill it into something that's quantifiable? Because I want to be able to monitor these different signals. So I want to turn user feedback into time series. Because with time series, I can now treat this the same way as Datalog treats machine logs. I want to be able to see anomalies and I want to know when something breaks. So what we do here is that we break down your data in something called quality monitors, which is basically machine learning models that can aggregate the same type of feedback data in this very fine grained and discrete buckets. And we deploy up to a thousand of these quality monitors per product. And so we can get down to the root cause, let's say password reset link is not working. And it's in that root cause, the granularity that we see that companies take action on the data. And I think historically, there has been like the workflow between marketing and support and engineering and product has been a bit broken. Like they've been siloed from a data perspective. They've been siloed from a workflow perspective where support will get a bunch of tickets around some issue in production. And they're trained to copy and paste some examples and throw it over the wall, file a JIRA ticket. And then they don't know what happens. So what we see with the platform we built is that these teams are able to rally around a single source of truth. They're like, yes, password reset link seems to have broken. This is not a user error. It's not a fix later or I can't reproduce. We're looking at the data and yes, something broke, we need to fix it. I mean, the data silo is a huge issue. Different channels, omni-channel now, there's more and more channels that people are talking in. So that's huge. I want to get to that. But also you said that it's a labor of love to leave a comment or feedback. But also, I remember from my early days breaking into the business at IBM and Yulit Packard where I worked, people who complain are the most loyal customers. If you service them. So it's complaints, it's leaving feedback. And then there's also reading between the lines with like app errors or potentially what's going on under the covers that people may not be complaining about, but they're leaving maybe gesture data or some sort of digital trail. So this is the confluence of the multitude of data sources and then you got the silo locations. It's a complicated problem. It's very complicated. And when you think about like, so I started, I came to Bay Area in 2005, my dream was to be a quant analyst on Wall Street and I ended up in QA at VMware. So I started at VMware in Palo Alto and didn't have a driver's license. I had to bike around, which was super exciting. And we were shipping box software, right? This was literally a box with a DVD that's been burned. And if that DVD had bugs in it, guess what? It'll be very costly to then have to ship out and everything. So the, I love the VMware example because the test cycles were long and brutal. It was like a six month deal to get through all these different cases and there couldn't be any bugs. But then as the industry moved into the cloud, CICD, ship at will. And if you look at a modern company, you'll have at least 20 plus integrations into your product analytics, add SDKs, authentication SDKs and so forth. And these integrations, they morph and they break and you have like connectivity issues. Is your product working as well on CalTrain when you're driving up and down versus Wi-Fi? You have language specific bugs that happen. Android is also quite a fragmented market. The binary may not perform as well on that device versus that device. So how do we make sure that we test everything before we ship? The answer is we can't. There's no company today that can test everything before they ship in particular in consumer. And the epiphany we had at our last company Scout was that, hey, wait a minute, the end user, they're testing every configuration. They're sitting on the latest device, the oldest device. They're sitting on Japanese language, on Swedish language. They are in different code paths because our product executed differently depending on if you were a paid user or a free immune user or if you were certain demographical data. There's so many ways that you would have to test. And PagerDuty actually had a study they came out with recently where they said 51% of all end user impacting issues are discovered first by the end user when they surveyed a bunch of customers. And again, like the cool part is they will tell you what's not working. So now how do we tap into that? So what I'd like to say is, hey, your end user is like your ultimate test group and you're in a curious sort of the layer that converts them into your extended test team like that they can actually, now the signals they're producing is making it through to the different teams in the organization. You know, I think that's the script that you guys are flipping. If I could just interject because to me, when I hear you're talking, I hear, okay, you're letting the customers be an input into the product development process and there's many different pipelines of that development and that could be whether you're iterating or geography releases, all kinds of different pipelines to get to the market. But in the old days, it was like just customer satisfaction, complaint call center or I'm complaining, how do I get support? Nothing made itself into the product improvement except for slow moving waterfall based processes. And then maybe six months later, a small tweak could be improved. Here, you're taking direct input from collective intelligence. Okay. Direct input and on timing is very important here, right? So how do you know if the product is working as it should in all these different flavors and configurations right now? How do you know if it's working well and how do you know if you're improving or not improving over time? And I think the industry, what can we look at as far as when it relates to quality so I can look at star ratings, right? So what's the star rating in the app store? Well, star ratings, that's an average over time. So it's something that you may have a lot of issues in production today and you're going to get dinged on star ratings over the next few months and then it brings down the score. NPS is another one where we're not going to run NPS surveys every day. We're going to run it once a quarter, maybe once a month, which we're really, really aggressive. And that's also a snapshot in time. And we need to have the finger on the pulse of product quality today. I need to know if this release is good or not good. I need to know if anything broke. And I think that real-time aspect, what we see as stuff sort of bubbles up the stack and not into production, we see up to a 50% reduction in time to fix these end user impacting issues. And I think we also need to appreciate, like when someone takes time out of the day to write an app review or email support or write that Reddit post, it's pretty serious. It's not going to be like, Oh, I don't like the shade of blue on this button. You know, it's going to be something like, I got double billed or hey, someone took over my account or I can't reset my password anymore. The capture, I'm solving it, but like I can't get through to the next phase. And we see a lot of these trajectory impacting bugs and quality issues in these work, these flows in the product that you're not testing every day. So if you work at Snapchat, your employees probably going to use Snapchat every day. Are they going to sign up every day? No. Are they going to do passive reset every day? No. And these things are very hard to instrument lower in the stack. You know, I think this is, and again, this is again, back to these big problems. It's smoke before fire. And you're essentially seeing it early with your process. Can you give an example of how this new focus or new mindset of user feedback data can help customers increase their experience? Can you give some examples? Because folks watching will be like, okay, I love this value, sell me on this idea I'm sold. Okay, I want to tap into my prospects and my customers, my end users to help me improve my product. Because again, we can measure everything now. With data. We can measure everything. We can even measure quality these days. So when we started this company, I went out to talk to a bunch of friends or entrepreneurs and VCs and board members. And I asked them this very simple question. So in your board meetings and or on all hands, how do you talk about quality of the product? Do you have a metric? And everyone said, no. Okay, so are you a data-driven company? Yes, we're very data-driven. Yeah, go David. But you're not really sure if quality, how do you compare against competition? Are you doing as good as them? Worse, better? Are you improving over time? And how do you measure it? And they're like, well, it's kind of, kind of like a blind spot of the company. And then you ask, well, do you think quality of the experience is important? And they say, yeah, well, why? Well, top of funnel growth, you know, higher quality products going to spread faster, organically, we're going to get better star ratings. We're going to have the storefront's going to look better. And of course, more importantly, they said the different conversion cycles in the product box itself, that if you have bugs and friction or an interface that's hard to use, then the inputs, the signups, it's not going to convert as well. So you're going to get dinged on retention, engagement, conversion to paid and so forth. And that's what we've seen with the companies we work with. It is that poor quality acts as a filter function for the entire business if you're a product-led company. So if you think about product-led company, where the product is really the centerpiece, and if it performs really, really well, then it allows you to hire more engineers. You can spend more on marketing. You know, everything is sort of fed by this product atom in the middle. And then quality can make that thing perform worse or better. And we developed a metric actually called the unit queue score. So if you go to our website, unitq.com, we have indexed the 5,000 largest apps in the world. And we're able to then, on a daily basis, update the score because the score is not something you do once a month or once a quarter, it's something that changes continuously. So now you can get a score between zero and 100. If you get the score of 100, that means that our AI doesn't find any quality issues reported in that data set. And if your score is 90, that means that 10% will be a quality issue. So now you can do a lot of fun stuff. Like you can start benchmarking against competition. So you can see, well, I'm Spotify, how do I rank against Deezer or SoundCloud or others in my space. And what we've seen is that as the score goes up, we see this real big impact on KPI, such as conversion, organic growth, retention, ultimately revenue, right? And so that was very satisfying for us when we launched that quality actually still really, really matters. And I think we all agree it does, but how do we make a science out of it? And that's what we've done. And when we, we were very lucky early on to get some incredible brands that we work with. So like Pinterest is a big customer of ours. We have Spotify, we just signed New Bank, Chime. So like, we even signed BetterHelp recently and the world's largest Bible app. So when you look at like the types of businesses that we work with, it's truly a universal, very broad field where if you have a digital exhaust of feedback, I can guarantee you there are insights in there that are being neglected. So Chris, I got- Because of these manual workflows. Yeah, please go ahead. I got to ask you because this is a really great example of this new shift, right? The new shift of leveraging data, flipping the script, everything's flipping the script here, right? So you're talking about how you, what the value proposition is. Hey, board example's a good one. How do you measure quality? There's no KPI for that. So it's almost category creating in its own way in that this net new things, it's okay to be new, it's just new. So the question is, if I'm a customer, I buy it. I can see my product teams engaging with this. I can see how it changes my marketing and customer experience teams. How do I operationalize this? Okay, so what do I do? So do I reorganize my marketing team? So take me through the impact of the customer that you're seeing. What are they resonating towards? Obviously, they're getting that data's key. And that's a holy grail. We all know that. But what do I got to do to change my environment? What's my operationalization piece of it? Yeah, and that's one of the coolest parts, I think. And that is, we're not going to add, let's start with your user base. We're not going to ask you to ask your users to do something differently. They're already producing this data every day. Like they are, they are treating about it. They're putting in that produce, they're emailing support, they're engaging with your support chat bot. They're already doing it. And every day that you're not leveraging that data. So like the data that was produced today is less valuable tomorrow. And in 30 days, our target is probably useless. Unless it's the same guy commenting. Yeah. So the first we need to make everyone understand, well, yeah, the data is there and we don't need to do anything differently with the end user. And then what we do is we ask the customer to tell us where should we listen in the public domain? So do you want the ready post, the trust pilot, like what channels should we listen into? And then our machine basically starts ingesting that data. So we have integrations with all these different sites. And then to get access to private data, it will be, if you're on send desk, you have to issue a send desk token, right? So you don't need any engineering hours except your IT person will have to grant us access to the data source. And then when we go live, we basically build up this taxonomy with the customer. So we don't want to try and impose our view of the world of how do you describe the product with these buckets, these quality monitors. So we work with the company to then build out this taxonomy. So it's sort of like a bespoke solution that we can bootstrap with previous work we've done where you don't have these very, very fine buckets of where stuff could go wrong. And then what we do is there are different ways to hook this into the workflow. So one is just to use our products, it's a SaaS product as anything else. So you log in and you can then get this overview of how is quality trending in different markets on different platforms, different languages and what is impacting them? What is driving this unit Q score? That's not good enough. And all of these different signals, we can then hook into Gira, for instance, we have a Gira integration, we have a page to do the integration so we can wake up engineers if certain things break. We also tag tickets in your support system, which is actually quite cool where let's say you have 200 people who've wrote into support saying, I got double-billed on Android. It turns out there was some bug that double-billed them. Well, now we can tag all of these users in Send Desk and then the support team can then reach out to that segment of users and say, hey, we heard that you had this bug with double billing, we're so sorry, we're working on it. And then when we push fix, we can then email the same group again and maybe give them a little gift card or something for the thank you. So you can have, even like big companies can have that small company experience. So it's groups that use us like at Pinterest, we have 800 accounts. So it's really through, marketing has a vested interest because they want to know what is impacting the end user because brand and product, the lines are basically gone. So if the product is not working, then my spend into this machine is going to be less efficient. The reputation of our company is going to be worse. And the challenge for marketers before UnitQ was how do I engage with engineering and products? I'm dealing with anecdotal data and life, my own experience of like, hey, I've never seen this type of complaints before. I think something is going on. And then engineering would be like, well, I have 5,000 bugs in JIRA. Why does this one matter? When did it start? Is this a growing issue? And all of this- You have to replicate the problem, right? And then it goes on and on and on. And a lot of times reproducing bugs is really hard because it works on my device because you don't sit on that device that it happened on. So now when marketing can come with indisputable data and say, hey, something broke here. And we see the same with support. Product engineering, of course, for them we sort of talk about, hey, listen, you've invested a lot in the observability of your stack, haven't you? Yeah, yeah, yeah. So you have a data dog in the bottom, absolutely. You have an FD on the client, absolutely. Well, what about the last mile? How the product manifests itself? Shouldn't you monitor that as well using machines? They're like, yeah, that'd be really cool. So it's sort of like the, because we see this, like there's no way to instrument everything sort of lower in the stack to capture these bugs that leak out. So it resonates really well there. And even for the engineer who's going to fix it, I call it like empathy data where I get assigned a bug to fix. Well, now I can read all the feedback. I can actually see, and I can see the feedback coming in. Oh, there's users out there suffering from this bug. And then when I fix it and I deploy the fix, and I see the trend go down to zero, and then I can celebrate it. So that whole feedback loop is very powerful. And that's real-time, it's usually missed too. This is the power of user feedback. You guys got a great product, unit queue. Great to have you on Founder and see a Christian. Wicklin, thanks for coming on and sharing in the showcase. For the last 30 seconds, the minute we have left, put a plug in for the company. What are you guys looking for? Give a quick pitch for the company, real quick for the folks out there, looking for more people, funding status, number of employees, give a quick plug. Yes, so we raised our A-run from Google, and then we raised our B from Excel that we closed late last year. So we're not raising money. We are hiring across go-to markets, engineering, and we love to work with people who are passionate about quality and data. We're always, of course, looking for customers who are interested in upping their game. And hey, listen, competing with features is really hard because you can copy features very quickly. Competing with content, content is commodity. You're going to get the same movies more or less on all these different providers and competing on price we're not willing to do. You're going to pay 10 bucks a month for music. So how do you compete today? And if your competitor has a better fine-tuned piano, then your competitor will have better efficiencies and they're going to retain customers and users better. And you don't want to lose on quality because it is actually a deterministic and fixable problem. So yeah, come talk to us if you're, if you want to have the game there. Great stuff, you know, the iteration lean startup model kind of some say took craft out of building the product, but this is now bringing the craftmanship into the product cycle when you can get that data from customers and users who are going to be happy that you fixed it, that you're listening and that the product got better. So it's a flywheel of loyalty, quality, brand, all if you can figure it out, it's the holy grail. I think it is, it's a goldmine and every day you're not leveraging these assets, your user feedback that's there, it's a missed opportunity. So thanks so much for coming on. Congratulations to you and your startup. You guys back together, the band is back together up into the right, doing well. We'll check in with you later. Thanks for coming on the showcase, appreciate it. Thank you, John, appreciate it very much. Okay, Ava your startup showcase. This is season two, episode three of the ongoing series. This one's about Mar-Tech, cloud experiences are scaling. I'm John Furrier, your host. Thanks for watching.


All right, Polo Buddies, thanks for being here in this video. I'm going to talk to you about some truth, some things that are going to change, some things that are saying the same, just some things that are going on with the channel. Thanks for being here. And at the end of the video, I'm going to do a preview of my upcoming what not auction for tonight at 9 15 p.m. Eastern Standard Time. So I hope to see you there. It's going to be vintage kids toddler baby clothing. There is a link down in the description. Hey, hello, buddies. Thanks for watching amazing, right? All right, let's get started. Let's talk about the channel, the Polo Buddies YouTube channel. What's going on with Polo Buddies and what you can expect in the future. Not much is changing, to be quite honest, but if you have been on the channel a while, you have noticed probably that I have started to incorporate in more sourcing videos like going to the Goodwill Bins and garage sales and trying to be more interactive with you guys with the reseller vlogs. I'm getting some people saying they love the reseller vlogs. Other people hate them. Some people want long videos. Some people want short videos. I'm never going to please everyone. I am trying my best and I'm trying to give you guys a wide variety of content. That's what I'm trying to do. Thank you all so much. Like, that's the first thing I want to say is thank you. I just hit twenty eight thousand subscribers and I just can't even believe it. Now, the truth, OK, some changes are going on in my life. I am a full time eBay seller who sells on Poshmark and McCurry. I basically start my items on eBay and I will cross post to McCurry and Poshmark with Liz Perfectly. If you don't know about Liz Perfectly, we're not going to go into that right now. But there is a demo video down below. It will help you cross post and get more eyes on your items. I highly recommend it. I've been talking about it forever. So demo video down there. If you want to try it 30% off with referral code BOLO buddies, all one word. That's all I'm going to say about it. Am I still doing that? Yes, I am going to continue to be a full time reseller. What is new? What not? You guys, I was going to start it. And I believed this. No, I'm sorry, it was August. I think I was going to start in August.   And I kept putting it off. And in December, I did my first show and you guys, I am hooked. I absolutely love it. Number one, I get to hang out with you guys. And for those of you that have come over and hung out and supported me, whether that be just watching and hanging out and chatting in the comments or buying something, thank you so much. I am just overwhelmed with the support that I have gotten on what not. I just I can't I really can't even believe it. So if you're not following me on whatnot and you would like to check it out, basically what what not is is it's an auction site. And I was fighting it because I tell you guys all the time I list my items on eBay. I list them at a higher price point and I wait for the right buyer. I am a long tail reseller.  Like I was going to be giving stuff away and I was going to be done with the show and I was going to be like, oh, I just gave all this money away. But you know what? It doesn't feel that way at all. Like I get done with the show and I'm like, I am so happy that that part of my money pile is gone. Now I can go source more people are getting great deals. I'm already having people messaging me with things that they've sold that they bought from me and which is incredible because really I didn't. I didn't start what not thinking I am going to cater to resellers. I started what not thinking I'm going to build my business and I'm just going to auction these items off. If it's a reseller, awesome. If it's not fine, I don't know what my items are going to sell for. I am just going to get on there and do the best I can. Start my items at a reasonable price and let the people watching decide what the value of my item is. That's what I thought. And that's what's been happening. But people are buying my stuff and reselling it. Now, as far as looking things up, I do not have time. So I have done vintage clothing, which holy cow, I had three amazing shows. If you guys came to those shows, you know, like just incredible stuff. Right? I'm in the middle of working on my second vintage baby clothing and toddlers, kids, vintage clothing. So what happened with the first show? Was it a success? Yes. But let me tell you my failure. OK, there was one bag and you'll see it in my preview video. I'm like, I'm not going to go through this one. This one will be a mystery. Well, I kind of I did one bag first and it was great. Everything's I think I sold everything almost.  And it was I think maybe I had been stored in someone's attic or something like that. It was their kids' baby clothes and a lot of them were stained. And this is the byproduct of that. All of these items were stained. And I started showing these piece by piece and they had issues.   And finally, I stopped and I was like, all right, let's move on to something else. But by that time, I had kind of lost my audience. I'm going to be honest with you. And I felt like shocks because I've got all of these amazing, incredible items. At the end of the video, I'm going to show you what I have left and what is coming tonight at 9 15 p.m. Eastern Standard Time on my what not channel. These vintage baby toddler kids' clothes are incredible.  If you if you want to join to get the $15 with the referral link, join. So you get that $15 to shop. And then I'll also link down below the link that will take you directly to my show. But I think if you use that link, it's going to take you to me anyway. And I'm Bolo buddies, all one word over there. And you can just bookmark the show. So we are going to talk about the stuff that's left. But if you decide to do what not, maybe don't make that mistake. I was thinking this is going to be exciting. There might be a home run in there and there could have been. But it was kind of a won't want. So these are coming back. There were some people that expressed interest in me bundling them so that they can they would be a TLC. This is going to be a TLC lot. All vintage baby kids clothes stains mostly. And I didn't wash anything. So maybe you guys didn't know how to do that special stuff to get stains out. You might be able to clean them up. You might be able to use them for patterns. They might be cutters. Who knows? I don't know what you guys do with that stuff. I am not crafty at all, but I know that people buy this stuff.  If I have a what not show, they're very well could be. I was going to put them over on my sourcing with fellow buddies channel, but they're just not getting the views. And I think a lot of you kind of enjoy just me showing you what I found. And it's kind of like a haul video, but they're not super educational.  So let me know in the comments. What do you think about the preview videos? Do you like them? Is it going to depend on what I'm showing? Like I feel like the vintage clothing went over well because people love seeing vintage clothing. But I don't know, I'm just kind of feeling things out. But the reseller blogs, I do continue, do plan to continue to do those. Not every, not all the time. I mean, you guys watch these videos and you see a 20 to 30 minute video. The editing on those videos can take two to three hours.  So I'm putting a ton of time into YouTube. Now I have added what not. So let me tell you how what not works, OK? If you are actually going to set up a catalog, that's going to take you a long time. I don't do a catalog. Everything is I just you come to the show and it's going to be a surprise.  But what I'm showing, it's it's just going to be a surprise because I don't have time to do a catalog. I am usually on what not. I started 9 15. I've kind of decided that's going to be my time. That way I can get all of my shipments done before I go on. And I like all my eBay and all my Poshmark and Mercari, all those shipments are done. OK, so 9 15 is kind of my time slot. And then the problem is, is once I go on, I have a really hard time stopping. And it's been like, I think I got off at 3 30 in the morning one night. So 9 15. Oh my gosh, how many hours is that? Like five, six hours on straight. But I'm hanging out with you guys and it feels like 30 minutes. I mean, it goes so fast. So that part is awesome. I love that part. After the show, I have to sort everything into piles. I have to package them and then I have to create labels. So that sorting, packing, putting the labels on. That can take another four to five hours, depending on how many items I sold. There's been a few shows that I've sold over a hundred items. The Christmas items I was selling breakables. So that was kind of crazy. But I did get some new bubble wrap and I am using American bubble boys. So if you guys are interested in getting bubble wrap, I do have a link down below for that. I'm loving it. It's that other stuff I had will just say not good. But I talked about that in a past video. I had bought some bubble bubble wrap locally and it was just not good. And if you guys received some of those vintage Christmas ornaments from me from my what not show, you're probably like, why does this ornament have three pieces of bubble wrap around it? Well, it's because it's my old bubble wrap. The new bubble wrap is incredible. So American bubble boy link down below. That is my referral link. So check it out. I'm going to show you guys what I have left for my show on Tuesday night. Some really great items. So let me get to that. And I would love your feedback down in the comments. Just kind of let me know what your favorite video is. Somebody like mentioned, they don't like the sound effects. When I slow it down and speed it up. And make funny voices. But I got to tell you guys that it makes me happy. I'm going to keep doing it.  So I hope you guys are enjoying it and it's not like I hope it's more people like it than people that don't like it. I guess let me know in the comments, it would be great to get your feedback. I'm not going to be offended by that. Like you guys, I am fine with you guys telling me things that you would like me to do differently. I can't say that I will change. But I definitely take it into consideration. I know there's been some people that have complained about me talking about products that I use, you guys, I'm going to tell you most channels flip flop around. They're using different things all the time. They're just telling you what they're getting paid to tell you. I'm not doing that. I do have referrals that helps me keep this channel going because right now the ad revenue like I don't get thousands and thousands and thousands of views on my videos. OK, so somebody who is getting 50 and 70 and 80,000 views, they're making money. I'm doing OK. I'm not complaining, but those referrals, they do help. Every little bit helps. And those of you that have bought me coffee lately, so unexpected. Thank you so much. And you know who you are. I have reached out to you and thank you personally. Thank you. I appreciate it. But again, none of that is expected or required. You know, I don't expect any of that. Do I appreciate it? Yes. Do I work really hard? Yes, I work really hard. All right, let me show you these these vintage kids clothes. OK, and these are coming tonight at 9.15 p.m. Eastern Standard Time. OK, you guys, this is everything that's coming to the Tuesday night show. There is so much left.  Was that Sunday night show? So we've still got the Raggedy Ann and just a little side note. I do have a link tree, and I will link it down in the description of the video. I'm going to try to push out notifications to those of you that are interested in my what not shows with that. So I think it comes to your email. So if you subscribe to my link tree, you will get notifications when I'm going to go live on what not. Hopefully that's the plan. Plus, if you're following me on what not, you should get a notification from them as well. I think that's how it works, but I will tell you there's people I follow and I don't get their notifications. So if there's anything else I can do, I put it on Facebook. I put it on my community page. There's just been people asking like I never know when you're on. So those would be the things to do. Turn the bell on for this channel. That will alert you when I post new videos. That will also alert you when I post on the community page. This is a Bonnie Jean dress. Here's a little plaid skirt by Green Dog. Look at this. This is incredible. And I'm just going to give you guys a quick preview here. Look at this. Look at the presents they open. I did not get really, I'm just going to say I didn't get to the good stuff. I have so many Polly, well, not a ton, but I think two or three Polly Flinders and is it Flinders? Yeah, so I just found out that it's not Polly Finders. It's Polly Flinders. Everybody told me thanks so much for telling me. Vintage Oshkosh Bagash, so cute. So I've been saying it wrong this whole time. Hearts and flowers. Look at this one. I love this denim dress. This is a Polly Flinders. It's an excellent condition. Look at this, this beautiful little cute butterfly. Rose cottage there. This is one that eagle one that I showed. Eagles Eye and it says Eagles Eye in the back and it has this really great border around the bottom. Let me move some stuff around here. So this one is just absolutely darling. Love it. We've got this vintage jamboree. How cute is that? This one here, I think it has a little hat that goes with it. It's Bonnie something and it's got a hat. It's adorable. This is another baby bagash, Oshkosh Bagash. So cute. The Disney store never ran this one. There were so many things I just didn't get to. Here's another jamboree. Look at that color block. Would you call that color block? Adorable. Never ran this. Martin and Barnett, San Francisco, some sort of fancy like blanket, I think. Never got to the Princeton. Never got to the YMCA. These are single. Well, this one's a single stitch. I think this one's made in the USA. And yeah, I made in the USA. I don't know how to tell if it's single stitch, if it's a ringer. So just these really, really cute dresses. This one is Swiss Dot. This is smocked, I think is what it's called. I have this. I absolutely love this. It's made in Japan. It's this adorable little shawl. This is plum pudding, I think is what it's called. Yeah, plum pudding, and it is fantastic. It's this leaf print. It is a bigger size. This is a size seven. I think that's the largest size I have. This one here looks like it's got some staining. So I'll probably put that in with the other stuff. This is high girls, floral dress. This one here, I think, is a Polly Flinders also. So if you watched my other video, some of you've probably seen most of these, but trying to do a better angle or a better view. Jan Briggs, look at that. Look at those poofy sleeves. Oh, my goodness, how vintage is that? Would that be 80s, you think? That one's a size eight. Baby's First Christmas. This is brand new. This one right here is another one that is brand new. It's got a little hat in it. I don't think I showed these. And it's definitely, you know, a vintage tag, maybe not super, super old vintage Thomas, the train is made in China, but it is still a vintage top. We've got this tie dye bag. So I guess you'd call that tie dye. So it's the baby slips down in it. I think this is another Polly Flinders. And it is a size five. Super cute. It's got the smocking. Here's another plum pudding, blue little dress. We've got this purple check. I'm going to try to make this quick just to do a quick preview for you guys. Cute little here's Ralph Lauren, but it's got some red where the red has faded. So it'd need a new collar. A little green Christmas dress. This one right here, this next one. Oh, my goodness, look at these little gingerbreads. It's so cute. Little turtleneck. It's called Rare Two. So another little Christmas dress, sweater. This is precious moments, but there's nothing on it. Kind of kind of boring. Little red dress, but warm, right? This one has some staining on the actual lace. But besides that, it is just it's stunning. So somebody will have to fix that up. Here's another red Christmas dress, this little sailor romper. Some of these items I did show. All right, this one is itty bitty and I just love this. It's like, I don't know if it's a coat or a dress. Or if it's a mix, this little thing right here. Look how cute. Oh, my goodness, these clothes are incredible. So I hope to see you guys. Just going to do a quick little preview. That's some sort of towel. And then I sold out of I had three of these and I sold out of those, but I kept two of them for tonight's show. And then nobody wanted this one. I thought it was really, really cute. And then I also have these vintage, hand-made baby blankets here. And I did not show this yet. It's a fitted crib sheet. So that's kind of what's coming. It's a lot. It's going to be a lot of fun. So I hope to see you guys Tuesday night, 9 15 p.m. Eastern Standard Time. And again, make sure that you go down. And if you're not already joined to what not, join with my link and you'll get $15 to shop. And if you're already on what not, I'm Bola Buddy, so I would appreciate the follow. What do you guys think? That is a massive load, right? Lots and lots of stuff. Thank you so much for being here. Thank you for watching. Your feedback is very welcomed in the comments. Just be nice. Be nice about it. You know, I'm doing the best I can. I really am. I know I don't pronounce things well, and I'm trying to make light of it because it is what it is. So I am who I am. And I thank all of you that are here and supporting me and accepting me for who I am. Thank you so much. It means so much to me. And I'm excited to see where the channel goes in 2023. So thanks for watching.


In this video, we'll look at how to log volunteer hours. There are three easy ways to log your volunteer hours. For the first method, we'll start from your volunteer dashboard. We'll click on volunteer hours and click on add hours. This will scroll you to the bottom of a page where you will select the opportunity for which you'd like to add hours. If there's a shift, you'll be prompted to select the correct shift. You'll select the date that you performed those volunteer hours and enter the number of volunteer hours worked. At this point, you'll click submit hour entry and the hours will appear in your full hour log. For the second method, from any page on the get connected site, you can click on add hours on the top navigation pane. This will bring you back to the bottom of the same area that we just logged in. You will again be prompted to select the correct opportunity, select the date that those hours were performed and enter the number of hours worked. As we did before, you'll click on submit hour entry. For the third method, we'll start in our dashboard. From here, you'll click on opportunity responses. Find the opportunity for which you'd like to log hours, go to the dropdown on the right hand side of the page and select add hours. This will take you back to the same area where you previously logged hours, except now you can see that the opportunity has been automatically populated as has the date and the number of hours. Confirm that this information is correct and hit submit hour entry as we did before. Now, if you want to change an hour submission, you can navigate to your track hours tab. Find the hour entry that you'd like to edit and click on the pencil on the right hand side of the page. This will take us back to the same area and it will auto-populate with all of the information that was originally submitted for this hour log. Edit any information that needs to be changed and click on update hour entry. You'll also notice that hour entries show up in two different colors. Yellow entries are those that are waiting for approval from the program's volunteer coordinator. All yellow entries may still be edited by volunteers. Green hour entries are those that have already been reviewed and approved by the program's coordinator. These may not be edited by the volunteer. If you need to edit an entry that has already been approved, please reach out to your program's coordinator. Thank you for watching this video and please contact the city of Fort Worth volunteer programs with any questions.