CHAPTER XVIII. RETURN. OF THE MYSTERY OF THE FIERS by Edith Lavelle. This LibriVox recording is in the public domain. Both Mr. and Mrs. Gay looked up disconsolently as the green car approached. Suddenly their expressions of listlessness changed to incredulity, then to rapture. Mary Louise was home. In another second the girl had flown up the steps and was hugging both parents at once. Mrs. Gay could only gasp in her happiness. It was Mr. Gay who asked his daughter whether she was unhurt and unharmed. I'm fine, returned Mary Louise joyfully, and oh, so happy! Darling, murmured her mother, her voice choked with emotion. Now praise these wonderful boys, insisted the girl, my rescuers! Max and Norman tried to look modest and to waive aside their accomplishment with a gesture. But Mr. Gay sieged their hands in a fervor of gratitude. I can't find words to tell you what it means to us, he said. You two boys have succeeded, where four professional detectives failed. It's marvelous! Oh, it wasn't anything at all, except persistence on our part, explained Max. The real credit goes to Mary Louise. It was a swell idea she had. What idea? She demanded Mr. Gay, signalling for help, with semaphore flags, just as we all used to do in the scouts. But where were you, Mary Lou? Asked her father. Sit down and tell us all about it.  No, not specially, replied Mary Louise. They fed us pretty well at the insane asylum. It was fun to watch your parents startled expressions at this announcement. Fun now that the experience was all over. In asylum? They both repeated in horror, and then for the first time they noticed her blue calico dress. Mary Louise nodded and proceeded to tell her story, briefly and quickly, for she remembered that she wanted to catch the two criminals. Has Mr. Frazier run away, too? She inquired, when she had finished. No, he's over at his hotel, replied Mr. Gay. I saw him this morning. You must arrest him, Daddy! cried the girl. He was the cause of the three fires at Shady Nook. I know it! But how do you know Mary Lou? Asked her father. What proof have you? I overheard him and Tom Adams talking in the hotel garage. They didn't actually mention fires, but I'm sure they meant them. I have their conversation down in my notebook. I left it in my desk. It's probably still there. Suppose, suggested Mr. Gay, that you tell us the story of your suspicions and clues from the beginning. While I'm getting lunch, added Mrs. Gay, Mary Louise ran into her bedroom and found the little notebook. I'll just change my dress, she called laughingly, and be with you in a minute, but tell me where Jane and Freckles are. Out hunting for you with Silky, was the reply. A couple of minutes later she returned to the porch, looking more like herself in her own modern clothing. She sat down on the swing and opened her notebook. I first suspected Tom Adams the day after Flix Inn burned down. She began. All of the people of Shady Nook were over on the little island that night on a picnic, and Hattie Adams told me she expected to have Tom take her. But he wasn't anywhere to be found, and the boys saw a big fellow in the woods who answered his description. But I sort of gave up the idea of his being guilty when I heard he had lost some work by Flix Inn burning down. He threw me off the track for a while. I really suspected his feeble-minded sister, Rebecca. Then the Smith's house caught fire, and Rebecca gave us a warning. So I suspected her all the more. Finding that pack of clipped cards in the can of water didn't prove a thing to me. I never believed he was guilty. It was absurd to arrest him, commented Mr. Gay.  Mary Louise's laugh ran out merrily. You and Jane will have to get together, Dad. You agree so perfectly about David McCall. Never did care for the fellow, her father muttered. Give me men with brains and sense. He looked admiringly at Max and Norman. But get on with your story, Mary Lou. It was the day after the Smith's fire that I really seriously suspected Tom Adams, she continued. I trailed him to the store at Four Corners and found him gambling. He told a man that he'd pay him a hundred dollars, which he expected to collect immediately, and that set me thinking. Why? inquired Max, because a fireman doesn't earn a hundred dollars so easily, especially from tight wads like Frasier. Everybody knows that man pays miserable wages. Then besides that I overheard Tom Adams explaining a card trick, and that fact made me guess that he had gotten hold of one of Cliff's decks of cards, and either accidentally or purposely dropped them at the Smith's. Mr. Gay nodded approvingly. He loved to watch the logical working of his daughter's mind. So I began to put two and two together, she went on. Somebody was paying Tom a lot of money. Lots more than a hundred dollars I learned for doing something. What I asked myself could the job be except setting those houses on fire, and who wanted them burned down except Frasier, or possibly Horace Dittmar, who, as you know, is an architect?  Yes, and when Adelaide Dittmar got that threat I was positive Frasier was responsible. He wanted the business, and he was doing everything he could to get it. But even then I had no proof. So what did you do? asked Max. And why did Tom Adams suspect that you knew anything? It was all because of this conversation, answered Mary Louise, opening her notebook.  I even told them I was going over to the farm to talk to Hattie. That was a mistake, remarked Mr. Gay. A mistake I paid for pretty dearly, agreed the girl. But it's all right now, so it really doesn't matter. Now let me read to the conversation between Frasier and Tom Adams on the afternoon I was taken away. Quickly, in the words of the two men, she read to her listeners of Tom's demand for money and Mr. Frasier's reluctant compliance with his claims. When she had finished, she looked eagerly at her father. Isn't Frasier guilty? She asked. Of course he's guilty, agreed the detective, but he won't ever admit it. He'll squirm out of it because we haven't got proof in so many words. He'll say he was talking about something entirely different to Tom Adams. But can't he be arrested? persisted Mary Louise, a note of disappointment creeping into her voice. I don't see how, until we find Tom Adams. He'll establish Frasier's guilt all right. I can't see Adams shouldering the blame alone. Mary Louise frowned. She hated the idea of the hotelkeeper's freedom, even though it might be only temporary. But suddenly her face lighted up with inspiration. I have it, she cried. He can be arrested for signing that paper confining me to the insane asylum. Can't he, dad? Mr. Gay looked startled. What paper? He demanded. Mary Louise explained that, since the commitment had to be signed by two relatives of the patient, Mr. Frasier had posed as her cousin. That was enough, Mr. Gay said immediately. All that they needed as evidence was the paper itself. They would drive over to the institution that afternoon and secure it. Luncheon was indeed a happy meal in the gay household that day. Although Freckles and Jane did not return, the two boys and Mary Louise kept up a constant banter of laughter and merriment. Mr. and Mrs. Gay were quieter, but a light of rapture shone in their eyes. Just at the conclusion of the meal, Mrs. Hunter and Cliff arrived, prepared to enter a house of misery and fear. They could not believe their ears as they heard the gaity from within. Mary Lou cried Cliff incredulously. Cliff? exclaimed the girl, jumping up and running to the screen door. You are free! And you're home! returned the young man, seizing both of her hands. In spite of his arrest, Clifford Hunter was the same carefree young person. In a few minutes he was showing his card tricks to Max and Norman, delighted to find a new audience. When the whole story had been retold to the hunters, with the caution that they say nothing of it to Mr. Frasian, Mary Louise and the three boys walked around the little resort to tell everybody there of the glad names. Then she and her father and Max took the car and drove to the Adams Farm. Mr. Gay thought it would be wise to take old Mr. Adams with them to visit the asylum. And Mary Louise thought it would be interesting to bring Rebecca, just to let Miss Stone and the other attendants meet the real Rebecca Adams. With Max at the wheel they had no difficulty in finding the asylum. What fun it was, Mary Louise thought, to pass through those iron gates now, knowing that she was safe. Yet instinctively she reached for her father's hand and held it securely as the car proceeded up the long dryway. The same doctor and the same head nurse came out to receive them, as upon Mary Louise's first visit. Mr. Gay displayed his badge at once and explained his errand. The woman nodded and hurried into the office for the paper. While she was gone, Rebecca Adams, growing restless, stepped out of the car, lugging her heavy water pitcher in her arms. At the same moment Miss Stone, Mary Louise's special nurse, came out of the building.  Rebecca turned eagerly to the nurse. Can you show me where there is a well of clear water? She asked immediately. Yes, replied Miss Stone gravely. Back of the building. We have a fine well. Oh! cried the woman in ecstasy. At last! She looked over at her father, and there were tears of earnestness in her eyes. Let me stay here, father. This is my home. The more I want to live, her voice grew more whistful. A well of clear water, she repeated. Please take me to it, kind lady. Perhaps it is for the best, agreed old Mr. Adams. There's nobody to take good care of Rebecca at home now that her mother's dead, and I'm crippled up with rheumatism. She can stay if she wants to. And so, at her own request, Rebecca Adams took up her life at the quiet institution, and the rest of the party, with the paper, which was to be used as evidence against Frazier in their hands, drove back to shady nook. Mary Louise went into her bedrooms and put on her prettiest dress, awaiting the arrival of Jane and Freckles, and her friends. What a glorious evening it was going to be for them all! CHAPTER XIX CONCLUSION The Mystery of the Fires by Edith Lavelle This LibriVox recording is in the public domain. Mary Louise was putting the last dabs of powder on her nose, when she heard a car stop at the porch steps. Coming through the screened window of her bedroom, she immediately decided that it must be the detectives. Yes, and oh joy of joys, they had Tom Adams with them. In another moment the men were out of the car and up on the porch where her father joined them. Congratulations! exclaimed Mr. Gay. I see that you've got Tom Adams. I remember him now. Yes, answered one of the men, but he won't admit a thing about your daughter. He says he never saw Mary Louise after she went back to the tennis court that afternoon. On what grounds could you arrest him then? demanded Mr. Gay. He stole a car on his way to the West. Mary Louise repressed a giggle and turned away from the window. Her father evidently meant to find out what he could before he announced his daughter's return. You have a sister, Rebecca, haven't you, Adams? He inquired. The young man nodded. Yes, she's feeble-minded. Why? We know that Mary Louise saw her the afternoon she disappeared. Rebecca told us so. And she also said that you came home that afternoon just as my daughter started to leave the farm. Rebecca's mind wanders a lot, muttered Tom. She don't know what she's talking about half the time. He shifted his feet uneasily. You have been thinking of putting Rebecca into an asylum? persisted Mr. Gay. Yeah, we considered it. Why? Because she's in one now, announced Mr. Gay calmly, of her own free will. An asylum about twenty miles from here. A Dr. Federer, I believe, is the head of the institution. He paused and gazed intently at Tom. The young man's jaw dropped. His face grew white, and his hands trembled. Mr. Gay burst out laughing, and Mary Louise came to the screen door. Hello, Tom, she said quietly. The young man started as if he had seen a ghost, but he managed to stammer a reply. Hello, Miss Gay, he said. All three of the plainclothes men stepped forward in amazement.  They demanded of Mary Louise's father. No, answered Mr. Gay. To be frank, I didn't. Two of her young friends from Riverside did. She was confined in an insane asylum about twenty miles from Shady Nook, under the name of Rebecca Adams. All of Tom's friends fell away from him at this announcement. He knew his game was up. His limbs grew weak. He groveled at the men's feet. Don't send me to the chair! He cried. I didn't harm her. She's all right, ain't she? We'll let the judge and the jury decide that, replied Mr. Gay. Now, suppose you sit down there and tell us the truth, Adams. You might as well, for we know most of it already. The young man crawled into his seat, but he made no attempt to tell his story. We know that you burned three houses here at Shady Nook, said Mr. Gay. We know, too, that you did it because you were bribed by Frasier. Didn't he pay you a certain sum of money to start those fires? Yes, he did, acknowledged Tom. He gave me five hundred dollars. Why did he want them burned down? Asked one of the plainclothes men. He figured that he'd get five hundred, at least, from the hunters during the summer, entertaining their friends and all. Then Flix Fire turned out to be better business yet. All the folks from Shady Nook, except the Dipmars, began eating at the hotel once Ian was gone.  Did Frasier expect to burn any more cottages? That was the next question. No, he wasn't planning on it, only when Mrs. Dipmars started up a boarding house and took his business away from him. That made him sore. But I wasn't going to do no more dirty work. I figured I'd just get my money and clear out. I never did expect to burn Dipmars, only threaten them. Well, what made you do that dreadful thing to marry Louise? Demanded Mr. Gay. I wanted to get rid of her till I made my getaway Frasier, and me, was scared she was on to something, and would send for you and you'd figure it all out, Mr. Gay. Frasier thought if I was gone he'd be safe. He'd just deny everything. The idea of calling Mary Louise Rebecca just popped into my head when she told us she was going over to the farm to see Hattie that afternoon. I knew Hattie and Dad was off to the fair, so I jumped in my car and run over to the asylum and made the arrangements. We just got back in time to never. One of the men stood up. Detective Gay, he said, I think you and I had better go over and arrest Frasier now. These other two men can take charge of Adams. He turned to Mary Louise, who is still standing in the doorway. Is there any question you want to ask this criminal, Miss Gay, before we take him away? Yes, answered Mary Louise, stepping through the doorway. I would like to know how that pack of cards came to be dropped at the smiths, the night of their fire, how Tom happened to have them in his possession. The young man flushed. One day I was watching Hunter do a trick on the hotel porch. I noticed he put the cards in his coat pocket.  I thought they was marked, but they wasn't. Hunter sure is clever at tricks. Then, when I heard people was suspected him of burning his own cottage down for the insurance, I thought it might as well help that suspicion along. So I dropped his pack of cards into that can of water at the smiths. And sure enough it worked. Mary Louise's eyes were filled with contempt, but she did not put her feelings into words. Instead she nodded to the detectives. And the men all left the porch. Fifteen minutes later Frazier's arrest was accomplished, and the three plain-clothes men started for Albany, with both criminals in their custody. Mary Louise and her parents watched them go with a sigh of relief. "'That's that!' said her father with a smile. "'Now if only Jane and Freckles would come,' added her mother, "'we could be perfectly happy. It's time to go to dinner. In a couple of minutes Mrs. Gay's wish was granted. Around the road half a dozen young people came running, for they had just heard the wonderful news that Mary Louise was back. Silky reached his mistress first, then Freckles arrived, with Jane and four of the boys close behind. Never if she lived to be a hundred would Mary Louise forget that wonderful dinner at the Ditmars. The joy of being back home again, the happiness of her friends, the companionship of her father—oh, everything seemed perfect that night to the lovely brown-eyed girl. And not least of it all, was the satisfaction of knowing that the mystery of the fires was solved at last. Shady Nook was safe again for everybody, to enjoy for many, many summers to come. End of Chapter 19 Recording by April 6090, California, United States of America. End of The Mystery of the Fires by Edith Lavelle


I think our preseason has been going pretty well. We've got a lot of new guys on our team and we've been able to get out and scrimmage once. We had a really good battle with St. Mary's and we're excited to get another go this weekend with Washington College and Hartford Community College before we move on to Muhlenberg. And I think practice has been going good, a lot of new faces, a lot of old faces. And so I think the chemistry has been great and our captains with Damian Schmidt and Jack Scalotti have been doing a great job getting the guys focused on what we've got to do to accomplish this season to get back to where we think we need to be. Yeah, each year we kind of play one of the tougher schedules of the nation. So we're always excited to get out there. You know, we opened up with Muhlenberg on the 17th who's a really strong Centennial team and then we go down to CNU who'll be a top five team and then we play Catholic who's a very good landmark team and has had a new coach, a newer coach over the last few years and doing some great things before we really get into the meat of our schedule playing Gettysburg, Dickinson, two of the best teams in the ODAC and Washington and Lee and Lynchburg before we play Salisbury and end up with a very strong Franklin and Marshall team before we get into a solid conference play knowing that Eastern New York and Widener and Messiah are all gonna have much improved teams. So we're excited about our schedule and each week it's gonna be competitive and play against great players and that's what our guys come here to do each and every year. Yeah, we're lucky enough to have a lot of guys last year get all Mac and some other accolades over the year and we're lucky enough to have a few pre-season All-Americans but the guys we got coming back that we're gonna rely on is our defense with Nick Mullevy coming back for his fifth year and Jack Seales coming back for his sixth year and Justin Scorris back for his fifth year, Ryan Quinn's back for his senior season and then we got our core of our middies back all four of them returned from a year ago and then we have a couple of really solid freshmen they think you're gonna contribute for so I think our leadership is gonna come from our defensive end and because we're gonna be much younger in offensive end even though we have, I think we think two of the better middies in the country in Grand Zick and Jack Scalati but we're gonna have a lot of freshmen out there and a lot of sophomores who haven't played for us before so they're much different than we've been in the past bigger kids, you can shoot it better from the outside and a little tougher but it would be a little quicker on the offensive end especially with some of the freshman attackmen that we're probably gonna play this year. Yeah, so we're lucky enough to have probably one of our better freshmen class in a little while here and so we're Gavin Gossin from Florida is gonna play a lot for us along with Daryl Curtis another freshman attackman from California and then we had a transfer who's a freshman from Bellarmine who didn't play who still has four year of eligibility and Kayla Russell, we're expecting a lot out of him might take him a little bit longer than the other guys but he's gonna be pretty good and we have a Hunter Brand who's a freshman out of Urbana High School who's probably gonna be one of the best freshmen in the country, big strong middie that can do a lot of things along with some sophomores that really developed with us and Max Erasic and Colin Dobbins are much improved over the past quality years and we have a senior middie that came in transferred from Siena and so he's gonna help us a lot as well so we're gonna play a lot of different faces in the midfield and a lot of new guys at the attack position but we really like that we think that's really gonna help us and do different things and we might be a little simpler but I think we're gonna be a little more athletic. Yeah, we've been lucky enough over the last, I think about 11 years now we've been doing the Mustang Classic and I think this year is one of our stronger slays eight of the 10 teams are pre-season ranked and a lot of them are in the top five so we're really excited and I think that kind of exposure for us is tremendous but I think it's all about the coaches the coaches have really bought into this event taking two games away from there or maybe home games to come to this event to have it and we're really excited for this event in the 15th and 16th to just show what great lacrosse is for everybody to see and we just can't wait to get out there and get that tournament going again for its 11th year and I think the players love it as much as the coaches now so it's awesome. Can't wait to get everybody out there on the 17th for our opener we hope all the students come out and it's gonna be a great year and a great atmosphere on Mustang Stadium on the 17th and we can't wait to see everybody.


Hello, everyone, welcome back to another ChatGPT tutorial. In this one, I'm going to show you how to train ChatGPT to write in your style, your tone of voice, the way you write your own content. Also, I'm going to show you another example where you can teach ChatGPT to write in a style of somebody else's. For example, if, for example, I'm going to use Cracked.com, they've got like a funny website. You know, they're kind of irreverent and funny and humorous and all that stuff. I'm going to show you how I can write content and train GPT to write in their style. So here we go. The first step is I wrote into the chat. I wrote, are you able to analyze text for tone of voice and style? Yes, I have been trained to analyze text for tone of voice and style. It answered me. Perfect. The next step, and I've got this in my description below, so you can just copy paste it. But what you want to do is you want to go analyze the following text for tone of voice and style. Apply that exact style and tone of voice to all your future responses for this one chat. Keep that in mind. This won't do it forever. It'll do it for this chat. OK, good. So we've got that in mind. Now look at this. Here's what I did. I hit that. And then I copied and pasted in the article from Cracked.com underneath it. So if I go to Cracked.com, I clicked on this. And then I just took this content. And then I just copy pasted it in. So how did I do it? Again, analyze this semicolon, or colon, and then I just added this in. And then I hit Enter. What happens next? It tells you what the tone of voice is. The tone of voice in this text is humorous and sarcastic with a hint of alarm, et cetera, et cetera, et cetera, uses gleefulisms. All right, cool. Then I went right a 300-word blog post in this style about how the Fast and the Furious Part 6 was a cinematic masterpiece.  And I'm looking for it to see if it can match the kind of humorous, goofy style from Cracked.com. And here's what it came back with. Oh boy, buckle up, folks, because we're about to take a wild ride through the highways of our hearts and into the hearts of one of the greatest cinematic master pieces of all time, the Fast and the Furious Part 6. Now, if you read through this, let's start with the facts Part 6 has it all. We've got Vin Diesel and all his muscles that could bench press a small element. We've got the iconic Paul Walker and all his golden-haired glory. And of course, we've got the cars, sweet, sweet, hard-stopping cars. It has matched the tone and style from Cracked.com, which is what I wanted to show you. And it's very hard to write humorous, sarcastic, and then really get that as a chatbot, but it's done it. So this is how you do it. The content's in the description below. If you want to just copy-paste it, you're good to go. Thanks for watching.


So, on this program, we've talked about a number of Republicans who have been exposed for a plethora of reasons, ranging from grooming children to endangering and nearly suffocating children to giving alcohol to minors and indecent exposure, you name it. And in covering all of these stories, I've noticed a bit of a trend. The more anti-LGBTQ-plus the Republican in question is, the more bizarre their scandal turns out to be usually.  But I promise you, you are not going to be able to guess why this particular Republican got into trouble. I'm talking about Joseph Viso Jr., who is running for New Jersey State Assembly. He is a vaccine-skeptical mega-Republican who often complains about illegal immigration and thinks that Democrats are communists. But one of the most important issues to him is seemingly parental rights. And that's because of his anti-LGBTQ-plus disposition. And on his mailer, it's the number one issue that he lists, parental rights and education. And I think that we all know what that means. He also mentions family values later on. And on Facebook, he claimed that LGBTQ-plus people are coming for your children in response to an article alleging that a non-profit was sneaking, quote, gender lessons into schools, whatever that means. And he also shared a post on Facebook signaling his support for the outing of trans kids to their parents, likely not understanding that that could result in child abuse if the parents aren't affirming. So now that you know a bit about him, just try to take a wild guess as to what sort of dirt just came up about him recently. Just think of the craziest thing that you can imagine and then multiply that by 10. You ready?  And somehow, that is not even the most shocking part about this story, because that award goes to the excuse that he used for said behavior. This is a wild one, so buckle up. HuffPost reports, Viso had a dispute with the daycare center, which was next to his business. And he told the globe that daycare employees harassed my men every day. They had cars ticketed every time my men parked on a side street. At some point, he said, he decided to get even by smearing poop on the handles and locks of the childcare facility. After the investigating officer told Viso there was video evidence of his poop smearing, he apologized and said, I'm not proud of what I did. He told the globe that he later cleaned up the dookie stained doors. It was done before anyone got hurt, he said. I'm not going to defend it, but wait for it here. I was a young man. It was a horrible time, and I made a mistake. Viso 52 said, Obama came into office the year before. No, he is not blaming Obama. That would make Viso about 39 at the time, an age when most people have learned not to smear poop.  You know, just when I thought that I've seen everything, a new GOP candidate comes along and just blows my mind. His excuse was he was in a dispute with his neighbor. He was also distraught over Obama's victory.  Now, he says that the reason why this dispute took place was because this daycare, which was next to his electrical business that he owned, was getting his employees ticketed, calling the police on them. But I mean, the question is why would that owner of the daycare do that? Was there a valid reason? Were they parking illegally there? Were they trespassing on top of that? There was allegations that the daycare claims that his employees were blasting loud music that was inappropriate right next to a daycare. So I think that I need more context to determine why this dispute even took place because knowing what I know about him, I just have to automatically assume that he was in the wrong.  Like I said, the most anti-LGBTQ plus politicians are usually the ones with the most bizarre scandals. But that's not all because LGBTQ nation ads in 2016 visa pleaded guilty in federal court to one count of conspiracy to distribute meth alone. Police charged him with possessing 5,000 grams of it enough to make 5 million ecstasy tablets, synthetic and pathogenic street drugs. He said he sold the drugs to help pay for his cancer treatments at the time. In 2014, visa was charged with illegally possessing a sawed-off shotgun near a school and sentenced to two years probation for it. He said he pleaded guilty because he couldn't afford a lawyer. In 2013, he was charged with possession of heroin and smoking materials. He pleaded guilty to possession with intent to use drug paraphernalia. Wow. Now the article brings up lawsuits for non-payment of bills along with the fact that he owed over 200 creditors more than $3 million combined. But I don't think that being poor is a crime, so I don't find that scandalous. But I do find his excuse for distributing meth alone genuinely heartbreaking. That is, if he's telling the truth, which I have my doubts about. But just for a moment, let's be extra charitable to him and assume that he is being honest there. He says he sold drugs to pay for cancer treatments.  And in theory, you'd think that an experience like that would shape his worldview, except it seemingly hasn't. So I recall seeing a mention of healthcare on his mailer. But when you read the details, or what you can make out at least, since the image quality is shittier than the fecal matter that he smeared on doorknobs, you can see that this isn't about healthcare. It's a reference to his anti-vax sentiment, which reads, protect individual right to bodily autonomy, ensure safety and transparency in medical recommendations and the metrics used to suggest them. Now, to be clear, he is not talking about reproductive healthcare when he references bodily autonomy. He's referring to the vaccine mandates that were temporarily enforced during the height of the pandemic. And I just find this so bizarre, so weird.  I mean, the poverty, him having to sell drugs to pay for cancer treatments, assuming he's telling the truth. That's a breaking bad-esque story. So even if you're lying, just the fact that you lied about that tells you that you know that healthcare is an issue. Why not link that to medical debt? He also filed bankruptcy before. The number one cause of bankruptcy is medical debt. Like, there has to be some sort of mechanism in your brain that gets you to think deeper about these issues because you want to be a politician, right? He was also busted for possessing heroin. Why not advocate for drug decriminalization or even gasp legalization? Because he doesn't want to do that. Instead, he's on Twitter sharing memes comparing Joe Biden to Hitler, denying global warming, promoting Ivermectin as a treatment for COVID, and doing January 6th, Apologia, just to name a few things that he's posted about.    It shows why this party cannot be taken seriously because they are incapable of talking about substantive issues that actually need to be addressed. But I'll admit, now that a Republican candidate has literally smeared shit on the doorknobs of a daycare center and blamed Obama for it, it's going to take a lot more for the next scandal to impress me. Like, we're going to have to see a blippy level scandal. Don't Google that, by the way, but we're going to have to see something like that if I'm going to be shocked by it. But I mean, yeah, another family values Republican who wants to protect children from LGBTQ plus people got caught doing something outrageous.  And what's interesting about this story is that I'm not even a little bit surprised, like it's shocking. The details are certainly shocking, but this is something that I think is absolutely within the realm of possibility when we're talking about GOP politicians. So I'm not surprised and I doubt that you were either.


The trend of time poverty I think probably needs very little explanation. We all know what it feels like to be constantly on call. The average American spends 4.7 hours a day staring at their smart devices. And a lot of times it's in service of work. 50% of the young people we spoke to said that they check email even after hours. And even if you're over 35, you tend to do it at just a slightly different level. But universally, irrespective of age, people are growing resentment about, there's no boundary between personal and professional time. So time poverty is our desire to kind of take that back to set aside time, be more purposeful. There's a fun app called Rescue Me. And it works like a dashboard metric that tells you how long you've been on the phone or looking at your apps. And it serves as parental control.  For car companies, the commute time is inextricably tied to how you manage your day to day. And so we have to be thoughtful about making sure that when our customers are in their vehicles, they're worth thinking about, what do they want, how come we achieve their goals. And if that's productivity, then it means constant connection. But for other people, it means different things.


Welcome ladies and gentlemen to a new episode of Time2Football, I'm your top button wearing host Asad Khan and in this video we're going to be discussing Cam Newton and what the future holds for the former first round pick. $19 million is what the Carolina Panthers could save if they decide to release him. That's not a lot of money compared to other first rounders and other franchise quarterbacks. Believe it or not there are many more things I value in this world than money. Here I am in my garage, just bought a used 2010 Nissan Centro right over here, fun driving around the potholes of Metro Atlanta, got a little side swipe right down here, but you know what I like more, the materialistic things, knowledge.  All you do is pretty much guess which player is going to have more fancy points for that week. This week's matchups include Drew Brees vs. James Winston, Alvin Camaro vs. Michael Thomas, Kenny Gallade vs. Austin Hooper and so many more matchups. This past week there was someone that put down $109 and won a grand prize of over $28,000 because they were 12-0 in their predictions. Since then the jackpot has reset but is steadily increasing. To sign up go to www.overlaydfs.com, the link is in the description or download the app for iOS. Hungriest player of the week, the one that wanted it the most. Chiefs kicker Harrison Bucker was an automatic 4 for 4 in his field goals this past Sunday against the Minnesota Vikings, but what makes him the hungriest player of the week was because of the last two field goals that he had for the day, a 54 yarder to tie the game and send it to overtime and then a 44 yarder to win it in overtime. In those high pressure situations, Harrison Bucker had ice in his veins. He was more cold than the frozen hands of a Philadelphia receiver. Get it? Because they keep on, ugh, guess I dropped the ball on that joke, but Bucker led the Chiefs to 26-23 victory over the Vikings and that is why he is the hungriest player of the week. Now we're going to talk about Cam Newton's future. Where is he going to play in 2020? We're going to talk about three specific teams, only the realistic scenarios and not every single quarterback-needed team where it seems like a long shot. For example, the Cincinnati Bengals seems like a long shot. If they truly want to move on from Andy Dalton, they're going to bring in a new quarterback in the 2020 draft or they're going to spend time in developing Ryan Finlay. They're not going to bring in a veteran, let alone a veteran that was drafted in the same class in 2011. The team goes for the Denver Broncos. If they want to move on with Joe Flacco, develop Drew Lott with Miami Dolphins. If they want to move on from Josh Rosen, they're going to draft someone new, more than likely in the 2020 draft. There's option number one. He stays with Carolina Panthers. In my opinion, I feel like this is most likely to happen. Like I said in the beginning of the video, I totally get the $19 million thing, but that's right around the average for a franchise quarterback for someone of Cam Newton's caliber. On top of the money, the reason why the Panthers would move on is because they believe that Kyle Allen or Will Greer, who is related to Nash Greer, that famous viner, would be the future franchise for the Carolina Panthers. And while it makes sense with the way that Kyle Allen has been playing recently, Cam Newton is just on a different level. He's a game changer and not saying that Kyle Allen isn't bad. He's doing great. He's doing what he needs to do to win games, but we just haven't seen that game changing play out of Kyle Allen just yet. This whole offense has been centered around Christian McCaffrey. But if you put Cam Newton back in there and he plays at the highest level possible, then Cam Newton can help the Carolina Panthers get to the Super Bowl. He's done it before. Kyle Allen has a shot to do it this year. But if injuries and age aren't a factor anymore moving forward, then Cam is the best option for Carolina. The second option for him is to play with the Chicago Bears. And while this seems like a realistic opportunity, I just don't see it happening. I feel like the general manager, Ryan Pace, wants to prove that he didn't make a wrong decision by trading up to grab Mitch Trebisky. I feel like Pace doesn't want to go back on his decision. He had to change the draft, Patrick Mahomes, DeSean Watson. Instead, he wants to prove that Mitch Trebisky was the right choice for the Chicago Bears for the next year in 2020. I see Mitch Trebisky being the quarterback. But if we get the same year like we are getting in 2019, at that point, I feel like Pace would accept moving on from Trebisky. However, by that point, by 2021, it'll be too late to sign Cam. So what do you do if the Panthers release some going into 2020? A realistic scenario, even though we don't believe it's going to happen, could be to sign Cam for three or four years on the Chicago Bears. Talent-wise, the Bears are a playoff team with the exception of the quarterback position, the only position holding them back. You don't know how long this window is going to be open to make a playoff run for the next two or three years. So why not bring in a quarterback that is an improvement to not only make the playoffs, but also a Super Bowl run? The last team that we feel like has a chance to sign Cam, the Tennessee Titans. Ryan Tannehill has been playing at a very high level, but is it the future for the Tennessee Titans? The Titans are in a weird spot with quarterbacks. Marcus Mariota, he's done. He's not the future. They're going to move on in Tennessee. Ryan Tannehill, he's been great. But with this contract coming up and with him playing at an elite level, he's going to start asking him and his agent for franchise quarterback level money, 20, 21, $22 million a year. So if they can resign Tannehill for a lot less money, then Tennessee will be content with Tannehill as their quarterback. But if they can, then why not just sign Cam Newton for the same amount of money that Tannehill and his agent are asking for? Tennessee is also doing pretty decent this year. So they're going to be in the middle of the pack for the 2020 draft. So your chances of getting a high first round pick and drafting a franchise quarterback like Tua or Jalen Hertz or maybe even Justin Herbert from Oregon. It's very minimal. So you got two options. Resign Tannehill or bringing a veteran like Cam Newton. But leave a comment down below and join in on the discussion. Where do you think Cam Newton will be playing in 2020? Also, don't forget to like this video and subscribe to this channel so you can stay up to date when we come out with a new episode every single week. Also, hit me up on social media, Instagram, Facebook and Twitter. The username for all three is at time of football. Besides that, thank you guys so much for watching this video and I'll see you next week.


He's a software engineer on the Mozilla Identity Team, the guys who do Persona, Browser ID, and he fights for the open web by building alternatives to centralized proprietary silos. A long-time deviant developer, Francois has been involved in open source for over 10 years now and regularly contributes to several projects. He also volunteers for the FSF, that's the Free Software Foundation, and he leads the development of LibraVatar.org. His talk today is about killing passwords with JavaScript, where we'll understand why asking users for passwords is a bad idea, and then we'll learn the basics of the Browser ID protocol slash Persona, so that you can take advantage of Persona on their own sites or web apps. With that, take it away, Francois. Thank you. Can everybody hear me in the back? Yep. Excellent. Now, if you've been following the tech press recently, you will have noticed a number of companies apologizing publicly after getting their passwords leaked to hackers, right, waking up one day, finding all of their passwords in some basement on the internet. Now, I could make fun of these companies for not following best practices and things like that, but the reality is that doing this is really hard. Keeping passwords secure is a hard problem, because you have to do a whole bunch of things. You have to use a secure hash algorithm, i.e., not MD5. You need to use per user cell values. You have to have a site secret that's outside of the database. Then you need to have password and lockout policies to prevent brute force attacks. And of course, the recovery mechanism that you use for when your users forget their passwords, that has to be just as secure as the rest, otherwise the rest may as well not exist. But what's the biggest problem with this list now? The biggest problem is that these are the 2013 password guidelines. I can guarantee you that in five years, there's going to be even more stuff that you need to do to protect your passwords, because this is an arms race between you, the site owner, and the attackers trying to get at your passwords. Not a good position to be in. So for you, as a site owner, passwords are really a liability. It would be really nice to be able to just get rid of them, right? I don't recommend that you do this right now. But it would be nice, right? So second problem with passwords is that they're really hard to remember. That's a big deal for users. Now you may think, well, users could just harden up and use a password manager, right? There's one every web browser. There's a couple of products that do a really nice job, syncing across devices, all of that stuff. But the reality is that when we ask users what kind of password managers they use, they said, it's one of these. Not exactly the kind that we like people to use. So instead of using password managers, what do users do? They employ this strategy. They just pick a really easy password. That way, it's not a big deal to remember that password, because it's really easy. This is the top 500 passwords, by the way. You may be able to spot a couple of weak ones. The other thing that a lot of users do is this. They just use the same password everywhere. If you've only got one password, it's much easier to remember all of them, because there's only one of them.  Because if that site gets owned, then basically all of your passwords are leaked. So an attacker can just access all of your accounts. So there's lots of problems with this. The other thing, of course, is that passwords will be forgotten, so users have to reset them. You need to provide some kind of mechanism for that to happen. And typically, it looks like this. You type in a username, email address, and then you will receive an email. You click a link, and then you set a new password. The usual password reset flow that every one of us has seen before.  Now, I'm not saying that's necessarily a bad thing, because if you have a strong password and you use two factor authentication, for example, with Gmail, then that password is very strong. And it's not a big deal. But I'm just saying that's the current state of things today. Now, this is an alternative to passwords. One that's quite popular with a lot of sites. And I'm not saying that it's always a bad thing to do this. There are lots of good reasons to go that way, which is outsourcing your passwords to a big for-profit company. But there are big disadvantages as well. And one of them, of course, is what do you do with users that don't have one of these accounts? Nobody is going to create a Facebook account just to log into your site. They're going to use Facebook login. They'll already have a Facebook login, maybe, but they're not going to create a Facebook login for it. So there's a bunch of users that you're going to lose if you don't have another mechanism for logging into your site. But the other thing is that there's an awful lot of users that will not want to sign in with Facebook into your website the first time. Because at that point, they don't have a relationship with your site. They don't trust you yet. And they know that Facebook shares a lot of information with your site. So there's about 10%, 15% of users, sometimes more, that have a Facebook account and won't use it to sign into your website. So you're losing quite a few users, actually. The one that don't have a Facebook account and the ones that don't want to use it. So it's something to think about. Now what about OpenID? OpenID is really interesting because it brought back the idea of decentralization to the idea of web login. Now decentralization is good because it allows users to choose who they trust. When you choose an identity provider, you're basically choosing someone that has the ability to impersonate you on a whole bunch of websites on the internet.  And unfortunately, when we don't have a decentralized system, you're forced into trusting someone that a site has selected for you. That's a problem. Now the biggest problem with OpenID, though, is this. This is one OpenID looks like. It's a URL. Now URLs work for all of us because we know what they are. In fact, many of us probably have a vanity domain that we use, so we have very short and nice URLs. But it doesn't work for the average web user. They're confusing, and they don't associate URLs with themselves. So what did sites do? The sites that are using OpenID. Well, a lot of them said, screw this URL stuff. It doesn't work. Just going to pick the most popular 10, 12, whatever OpenID providers, and then users can just click on the one they have, or choose one of these to log in. But notice what happened here. We just lost the ability for users to choose who they trust. Now they have to choose someone from this list that has been pre-selected by the site. And in fact, that didn't even work because there's far too many choices. It's confusing for users, so a lot of sites said, oh, well, just pick a top two, or whatever it is. So it made OpenID usable at the cost of decentralization. But this is the real reason why we can get behind OpenID as Mozilla. And the best way to understand the privacy problem with OpenID is to think of this analogy. Imagine that the next time you want to check into a hotel when they ask you for a piece of ID to make sure that the name matches the one on the reservation. What if the hotel were to phone up the government that you showed that ID to check that it's actually valid? It would be a little bit creepy because all of a sudden, that government department would have a trail of every hotel you've ever checked into.  They could say, well, you still have debts. You shouldn't be going to these luxury hotels. Pay your debts first. It's a bit of a stretch, I admit. But unfortunately, these are exactly the kinds of powers that we give to an OpenID identity provider. Also, the Twitter, Facebook, and the centralize authorities. But this is the deal with privacy. So all of this to say that the existing login systems on the web are not good enough. That's why we're still stuck with so many passwords. So if we're thinking about the ideal web-wide identity system, what would that look like? Well, the first thing is that just like OpenID, it would be decentralized. It's important to give users the ability to choose who they trust, to change identity providers, and to run their own if they want to. OpenID did this. We should do this. The next thing is it has to be simple. If the user experience is not great, then users are not going to want to use your site. Then you lose a whole bunch of potential customers. Or if they really have to use your site, like it's an internal site and they need to use it to get paid, then they're going to fail, and then they will drive up your support costs. So it has to be simple to actually work. But it also has to be simple for developers. Because if it's not simple for developers, there's no chance it will ever be secure. And finally, we're no longer in 2003. Internet Explorer no longer has 95% market share. We need a system that works on more than one browser. It needs to work on all of the browsers that people use on all of the devices that they use. Otherwise, it's useless. If I was standing here and telling you about a login system that only works in Firefox, you'd be right in not being interested. So what if this were a standard part of a web? What if it came with your web browser, this login system? Well, that's exactly what we're building with Persona. Now let me show you how it works. First thing to know is that Persona is based on the concept of a verified email address. This is my email, or one of my emails. If I can prove to you that I own this email, then when I come to your site, you can create an account for me that's tied to that email address. Next time I come along, I will show you the same proof, and then you can let me in. No password needed. That's the idea. So verified email address. And so I'm going to invite Nigel and Rakesh to join me for a little demo of the browser ID protocol. That's the protocol behind Persona. So I'm going to be the browser. Nigel here is going to be Wikipedia. So I'm going to try to log into Wikipedia using browser ID or Persona. And Rakesh is going to be Gmail, my identity provider, because I've got a Gmail address. So the first thing I'm going to do is, I'm the browser. I'm going to generate a public and private key for that identity. And I'm going to call that a certificate with that email address. So I've got a little certificate here with my email address. And now I need to get it signed, because it needs to be a verified email address. So I'm going to go to Mr. Gmail. Hello, Mr. Gmail. Oh, you don't have a mic. I will bring a mic for you. Let's try again. Hello, Mr. Gmail. Could I get you to sign my certificate, please? Sure. What's your password? Good point. I actually need to authenticate before Gmail agrees to sign my certificate. So. Thank you. That's great, that's great, that's great. So I'm locking this now with my private key. Excellent. Thank you. You can keep your private key. I don't need it. Although that said, it would be really handy next time I need a new certificate. So now here, I've got this certificate that is signed by Gmail. So what I need to do now is I need to create an assertion. Now if I were to use this directly to sign into Wikipedia here, the problem is that Wikipedia might be able to just turn around and then impersonate me on another website, because it would have my certificate. So instead what we do is we don't use certificates directly, we use assertions. Assertions are this little cryptographic bundle that contains three things. It contains, of course, a certificate, but it also contains an audience and an expiry. The audience is just the URL of the site you're trying to log into. So in this case, that's wikipedia.org. The expiry, I'll say expires in two minutes.  So there you go. I'm going to seal my assertion, my certificate in it. And now I'm going to take it to Wikipedia to log in. Hello Wikipedia, log in please. Well, let me check your assertion. The audience is Wikipedia. Oh, that's me. And the expiry is in two minutes. OK, this is the right time. I'm going to look at your certificate. OK, so you have your provider is Gmail. So I'm going to get a key from Gmail. Hello Gmail, can I have your public key? Sure, here you go. Thank you. So notice here that when Nigel went over to Rakesh to request his public key, he left my certificate in here. He didn't actually need to reveal to Gmail who was trying to log into Wikipedia because it's the same public key for everyone. So that's where we get the little progress in there. OK, so I'm going to try and unlock this with Gmail's key. Oh, it works. Welcome to Wikipedia. Thank you. Thank you, Rakesh. Excellent, so that's a browser ID protocol for you. Now, I'm going to show you a little demo of what it looks like on the web. And I'm not going to use the Wi-Fi. Instead, I've got this little screencast here. So this is Vos, a site that uses Persona. It uses Persona and Facebook. And the Vos guy tells us that there's about 60% of users that prefer Persona to Facebook. So let's just sign in with Persona, since it's the most popular option. And here we're using an id.me email address. id.me is a domain that has native support for Persona. So what's happening now is that we're being bounced over to id.me to get a signature on our certificate. id.me is asking for a password, because that's the email password for id.me. That's what they use as a login mechanism. So we provide that. id.me says yes, signs the certificate, it's returned to the browser, used to create an assertion that is then sent to Vos to login. And there you go, as you can see in the corner, I'm logged in. Now because I have the certificate on my browser already, I can use it to sign in to another site that uses Persona for Login. So this is DebugX. As you can see here, I've got my email address already in the dialog. So two clicks to sign in, second click is for User Consent. And there you go, signed into DebugX. So the point of this demo here is that Persona is today a decentralized system. id.me has native support for Persona, and that's where we went to get the signature on the certificate. It was their sign-in page that we saw, but the Mozilla was not involved in that part of the transaction. Now the fact that it's decentralized means that everybody's free to innovate on the login mechanisms that they use to sign in with Persona. We've seen someone that uses PIN codes sent by SNS. There's an identity provider that does that. There's another one that uses Jabber, Ubiquiz, LDAP, that's the one that we use internally at Mozilla, and then even client certificates is a guy that works with C8 that has written one of these. And there's also a slightly crazy person that decided to put, that he didn't want to back end for his identity provider. So he put the public key and a private key in full view of everyone, but he encrypted the private key with a password, so everything happens in the browser. Pretty cool. Not sure we'd recommend it to everyone. But the main thing I want to make here is that we want decentralization. It's a good thing, but it's not a product adoption strategy. And by that, I mean that you can't just wait for all browsers to support Persona before you get started. What we want, where we want to get, is there. We want new functions directly in the DOM. We want functions that are available to all browsers. But how do we get there? Well, one way to get there would be to create an add on or Chrome extension. But then that would require users to install these things before they can use Persona. Not a very good thing. Sites are not going to be interested if only 15% of their users can use it. Next thing we could do is we could build it into Firefox. And in fact, we are doing this. But the problem with this is that we can't rely on this because this is what, a desk, a quarter, a third of the browser market? It's not enough. There's not a site that will be interested in this. Well, we could also build it in Chromio. That's the open source project behind the Chrome web browser. But still, we're looking at, what, like half of the browser market? Three quarters, if we're lucky? I don't know. It's still not enough. We need to have a system that works everywhere. So this is what we decided to do instead. JavaScript. We wrote a temporary JavaScript shim that makes it work in all browsers. And this pattern that I'm going to show you is called lift, or locally isolated feature domain. Now what this means is that if you want trusted code running in the browser, which we do because it's dealing with people's private keys and things like that, the first thing that you're going to do is you're going to get a domain. The domain, in our case, is login.persona.org, this one. And then you're going to use local storage. Now local storage is interesting because everything that will be stored in local storage using the code that's on that domain will be tied to that domain. So if the code on login.persona.org generates a public key and a private key, stores it in local storage, then only that code can access the keys. Which means that another website, Wikipedia, can't actually go and touch the keys. The last piece of the puzzle is post-message. This is what allows us to do cross-domain communications. So the whole thing looks like this. You've got Wikipedia on one side that's talking over a post-message channel to the shim that's running on login.persona.org. And that's the piece that has access to the keys. And over there, it can decide what restricted API to offer to all the sites that use Persona. Make sure that they can use the system. They can't actually have access to the keys. And what this means is that we work on all modern browsers, both on desktop and mobile today. The second part of this, though, is that we can't wait for all domains to add support for Persona before we get started because we're going to wait for a really long time. There's an awful lot of domains on the internet. And so what we built here is a temporary centralized fallback. Now, I say temporary because as soon as a domain gets native support for Persona, the fallback automatically goes away. It's only there for domains that don't support Persona. So let me show you how that works. So this is a slow blog. It's a site that uses only Persona for logins. I'm going to click Sign In. And this time, I'm going to use an aol.com email address. Yes, they still exist. So now what's happening is that it's asking me to pick a password with the fallback identity provider. So when a domain does not support Persona natively, that's where the fallback identity provider kicks in. And this one asks us to set a password that's not specifically the site for all Persona sites, but just to make sure that we don't have to confirm our email all the time. Next thing is that it sends us an email with a unique link to click on. That's to make sure that we're actually the owner of that email address. Before the fallback identity provider is willing to sign certificates on behalf of AOL, it will check that we're actually the rightful owner of that email address. And so there we go. We're all done. We confirmed the email address, and now generated assertion with the sign certificate, and we're logged into Solon. So the point of this demo was to show you that Persona works today with all email domains, either through the fallback or through native support. But we can do better than this. There's a feature called Identity Bridging. And what that is is that if you look at a couple of email providers, they already have an API that people can use to authenticate against them. For example, Yahoo has OpenID. So what we built is a bridge that talks OpenID to Yahoo and BrowserID to your browser. So let's see what that bridge looks like. So this is another Persona-only site called ReasonWell. And I'm going to sign into this one using a yahoo.com email address. And what you're going to see here is that the bridge is going to kick in. And the bridge will then bounce us over to the real yahoo login page. So we don't have to set a new password. We're just using our existing yahoo password. And yahoo will then confirm to the bridge that yes, it's the right person because they authenticated successfully. And then the bridge will be able to sign certificates on behalf of yahoo without having to have an email confirmation step for that user. And so there you go. Certificate is signed. And we're logged in. It's as easy as that. So it works today with yahoo, as you just saw. And it also works with Gmail. So we have a bridge that speaks all of the Gmail and then BrowserID to the browser, which means that today all of these users have a neonated experience with persona. So persona works everywhere. Before I go, though, I want to share with you a couple of quick lessons that we learned in our project. And the first one is that user testing is really important. This is what we use to recommend to people. Just put this button when you want to add persona to your website. Unfortunately, it doesn't work.  So they didn't click on that button. Even worse was this one. Now, a couple of people use this because they had on Facebook, Twitter, and then they just added a third thing that was Mozilla persona. Unfortunately, this was even worse because a number of people were like, oh, well, I use Chrome. I can't click on this because it obviously requires Firefox. It says Mozilla. So don't use this either. What we found is that this one works a lot better. Sign in with your email. Everybody has an email. Just click the button and use it to sign in to this website. Second thing is nobody wants to be first. This is not a surprise, but this is a very popular question that we get. How many users does persona have? It's really annoying when you're trying to start a new project, when you're trying to start a new identity system. The answer is initially zero. But what we did is with this bridging I've just shown you, now we're able to say that we have 700 million users that are ready to go with persona. They don't need a new password. They don't need to click an email link to get started. So that's a big deal for us. And finally, if a problem has been around for a while, like password problem on the web, it's probably a hard problem. See if you can solve parts of it. For example, with persona, we're not going to solve this problem. You're not going to use persona to sign into your server via SSH. You're also not going to be able to use persona to log into your Windows desktop. And that's OK, because persona is designed as a simple login system for the web. That's what we're focusing on. That's the problem we're trying to solve. Now, how simple is it for developers to add to their websites? Well, the answer is it's really just four steps, four pretty easy steps. And you can find them in that URL, which will be at the end of the presentation as well. But just to give you a flavor, the first thing you have to do is to load this JavaScript file. So this is the ship. This is a temporary JavaScript ship that works out in the fact that browsers don't have native support yet. Then what you do is you call a setup function. You pass in two callbacks, the one for when it's time to log your user in, what do you do? And the next one is when it's time to log your user out, what do you do? The third one is you have to hook your login and logout buttons to the right things. So login would call navigator.id.request. No parameters needed. And logout would call logout. Finally, you need to verify the assertion, like Nigel did, server site. It's important because you can't trust a client to not lie about it. And for that, we provide a bunch of libraries. Usually it's just two lines of code, and you're done. And the best part is that you don't need an API key for this.  You don't have to ask for permission before you use persona. Now, I want to leave you with one small request. And that is stop making the problem worse. Stop making the password problem worse on the web. And by that specifically, I mean, if you're building a new website, default to persona. Now, I'm not saying you should always use persona. There's lots of good reasons to use something else sometimes. But don't start with a default of asking users to pick another password. Just start with persona. And if it turns out it's not the right system for you, choose something else. But don't start with passwords. If you have an existing site, please add persona to it. As you've seen with foos, you can easily have persona next to Facebook. And in their experience, it actually works better than Facebook, but for their particular site. But there's no problem in using persona alongside other things. What you might want to get rid of, though, is any sort of fallback mechanism you have, other than the Facebook and Twitter things, if users don't want to use stuff. If you're asking for an email and password, for example, you can replace that with persona. Here's a concrete example. This is how you sign up to Pinterest. This is what they have currently. And this is what I'm suggesting they do instead. Can you see the difference? The difference, of course, is the click handler on that button right here. You change that to use persona.  Thank you very much. I have a question. There's one there. So obviously you need a browser for this to work, right? So what if I want to access an API that's exposed by a website that's behind a persona thing? I'm writing a thick line, a desktop line to invoke an API. I won't be able to use persona there, right? So the question is basically if you're using another application that wants to talk to an application, you'll be a REST API, how to use persona, that kind of stuff. What we have to distinguish is authorization and authentication. Persona is authentication. So what you would do in that case is use a different technology for the authorization part. So for example, say you have a thick client on a Windows desktop or whatever that needs to authenticate with your app. What you would do is you would show a web form initially to the user so that they log in. And at that point, they log into your website. And some kind of token is exchanged. The app keeps the token. And the token can be revoked later. But basically after that, when the app needs to talk to your REST API, then it would just exchange a token. It wouldn't use persona for that part. We only use persona for the initial setup phase. Thank you. We're not trying to replace all of these things that people do. We're trying to get rid of passwords, basically. I'm Kostav. I just want to add something to what you said about the setup part, is that there are plugins available for Drupal, for WordPress. And for Drupal, it's the breeze to setup persona. You just install the Drupal module, and the module does everything on its own. Yeah, there's lots of that URL here, libraries and plugins. There's lots of libraries available for various languages, lots of plugins available for open source software frameworks, things like that. So thank you very much. That's a good point. All right, Francis. In the second video, in the fallback mechanism, when the email comes to the user's inbox, the look and feel of that email was not off the website that he was trying to log in, that could be a really jarring user experience, in my opinion. I'm glad that you pointed that out, because we have a new feature coming in, it will be coming in the next couple of weeks. It's actually committed to the repo. It just needs to go through QA that actually adds branding to the email. So there will be an ability, I believe, to put the logo of the site and then the background color for that site. Just like in the case of Vos, I don't know if you noticed, but Vos actually had a logo on the right-hand side. So in the Persona dialog, you can customize the background color, the logo, as well as the name of the site. So you can actually brand the right half, they can be all branded for your site. The left half is, obviously, asking for the email stuff that's persona-specific. One more question I have is that in Persona, all that information that I get about the user is just his email address, right? So as opposed to if I was using Facebook login, I would get all of his profile and friends and relationship status, and I don't know what it's possible. In your experience, has this been a concern from the website developers? So we've talked to a couple of people that use Persona, like the Debug X guy, for example. We talked to him, the Vos guy. And a couple of them, I want to say all of them, but at least most of them, said, please keep it just the email. We like the simple. And it's a simple story for users as well. Like if you log in, I'm going to get your email and that's it. They really like that, because a lot of people that click on there definitely don't want to click on Facebook for that exact reason. So I think we're probably going to keep it that way. Hello? In the fallback mechanism, you said that the secret key will be stored in the local storage. But I doubt the local storage is not a full-fruits mechanism since any cross-scripting attack, any hacker or any security breacher, if he does a cross-scripting attack on your website, then he will be able to grab those things from the local storage. So how it is secured? So the question was about the security boundary for local storage. If the JavaScript of the shim is compromised, then you're right, then basically that's the JavaScript that has access to the key. They can just take the keys and post them somewhere else. If you're talking about the JavaScript for the site that's compromised or something like that, something that's not on the login.personal.org domain, then that JavaScript doesn't have access to that part of the local storage. So for an attacker to actually get to your keys, they need to actually inject code on our servers on the login.personal.org domain. And that will also go away when we have native support in the browser. So in the native version of persona in Firefox that we're working on, the keys will not be stored in local storage, and the code that's accessing it will not be downloaded through the internet either. But still today, it's safe from a typical cross-site scripting attack. So like what he said, I just wanted to know, now that we have packaged applications using Firefox or Chrome. So suppose I'm building an offline application that I need to run on a user's desktop. And I want the support of persona over there too. Even when internet is not there. So what is the support for that? So that comes down to pretty much the same question that this guy had. You use persona for the initial login to exchange some kind of token, and then you use that token for the authorization kind of aspect, for the everyday kind of request to REST API or whatever. You just present a web view the first time. And so there's people using it successfully on mobile and other things like that, and that's kind of the approach that they use. The last thing you want is to show the password prompt every single time someone signs into your app, of course. Hi, how safe do you think would it be to use persona on a shared computer or a shared browser, maybe? So what happens when, say, you're in internet cafe or something like this? What I didn't show in the demos is that the first time we assume that you are on a shared computer. So we make the certificates valid for a very short amount of time, and they basically go away when you close the browser. Now in most internet cafes, the between users, like the cookies will get cleared, and local storage is actually clear at the same time as cookies. So it's not usually a problem, but we still use short-lived certificates, short-lived sessions, the first time you use persona. The second time we ask you whether or not it's your computer, if it is your computer, then we extend the length of the certificates. If you say that it's a shared computer, then we keep really, really short.  Question from Gmail here. Yeah, question from Gmail. Do you have any suggestions to help sites transition from their current, other than, of course, alter table drop column? Any other suggestions in terms of UX to smooth the transition from their current database-based login system to persona? So what I would recommend there is that first of all, you start in your application to make sure that email addresses are unique for users. So it has to be unique. Then you can add persona support without removing the existing thing that you have. Basically, if someone wants to log in with persona, you just do an email lookup in your database. You find the account that matches that email, and then you sign a person in. The other thing that I would, and so you can keep the two systems for a while while people get used to it. One thing you can do as well is you can be sneaky. And I forgot my password page. You can say, hey, if you were to use persona, you wouldn't need to reset your password. So you can do stuff like that. And then when you're ready, then you can go ahead and get rid of the form and delete your password column. There's a couple of things. If you go on to MDN, the quick setup, at the very last step, step number five is more information about persona. And that's where you can find things on how to make sure everything is secure and also advice like what you just asked for transitioning. Things like having more than one email, changing your email, all sorts of things. So we've got a few things on this. One last question, yeah? So for my understanding, tell me if I'm wrong. Can I think of this as open ID? But instead of URL, we're using email addresses. It's an interesting way. So you can sort of think of it as open ID with emails. But I think what you mean there is open ID because it's decentralized, and it's pretty much the only widespread system that was decentralized. I think it's still different for open ID for three reasons, like usability, of course, as you mentioned, it's not URLs. Also, security. We want to build it into the browser so that it can no longer be fishable, because with open ID, you can just fake someone's ID logging page and grab their password. You can do the same thing currently with persona, because it's all happening in the browser. But in the content window of the browser, but once we pull it out into the browser UI, then it's not going to be possible anymore. And the last thing is privacy. I think it's a really big difference with open ID. With persona, it's a little bit like how you use these things, these passports, to travel to international countries. The first thing you do when you want to go to another country is that you go get a new passport from the passport office, and at that point you don't have to tell them which country you're going to visit. You just get a passport that works for all of them. And then when you go to the other country, you present your passport, and they let you in. But the step of getting a credential and using a credential, those things are separate. They're not in the open ID world. So that's a big difference. That's how we can get the big privacy advantage for persona. So anyways, that was the last question. But I'm going to be here all evening and tomorrow. So also feel free to approach me or other Muslim people if you have any more questions. Thank you very much. One big round of applause, guys. The Mozilla guys are just superstars. Keep going up to their booth and bugging them. They will be, this is their job. They love answering questions and telling people how to do it right. Thank you, Francois. One more round of applause. That was pretty cool, man. Come on.