Status Town Hall, 10 Sep 2018

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Status Townhall - September 10, 2018

Description

General

00:01:26 - Intro
00:01:29 - Experimenting with Peer Performance Reviews
00:02:50 - Peer performance reviews
00:04:59 - Status Core OKRs Q3ish (Aug-Oct)
00:05:24 - Improve decentralization with light client support
00:10:53 - Improve UX to increase engagement
00:11:53 - First steps towards a DAO
00:13:58 - Developers rely on Status dev tools
00:17:02 - Reduce our wall of shame

Non Tech Updates

00:18:48 - Welcome, new Core Contributors
00:19:16 - People
00:20:55 - Status Studio

Marketing

00:24:26 - Campaigns
00:25:41 - Community Competition - #CommuniTEE
00:27:54 - Category 1 - Status
00:28:28 - Category 2 - dat crypto culture
00:28:58 - ETHBerline Recap
00:30:18 - UniTimes WeChat AMA with Oskar
00:31:26 - Briefly on ETHIS
00:32:21 - Status Hackathon
00:33:20 - Devcon4
00:33:53 - Content and Channel Report
00:35:02 - Web Refresh

UX/UXR

00:37:05 - Berlin Design Team Meetup

Infra & Tooling

00:39:20 - Infrastructure Automation

Chat

00:40:20 - #core-chat
00:42:03 - #289-perfect-forward-secrecy

Wallet & Account

00:43:47 - #151-ens-usernames
00:46:45 - #170-wallet-improvements
00:47:31 - #279-SNT-Voting-Dapp

DApps & Developers

00:50:16 - DApps & Developers
00:52:51 - Embark

Desktop

00:54:05 - #desktop

Hardware Wallet

00:58:03 - #290-hardware-wallet-light
01:00:51 - #229-hardware-wallet-pro

Research

01:01:55 - #67-nimbus

Q&A

01:04:03 - Q&A

A

B

That's all good all.

A

Right, okay, so you have control now: Johnny yep, yeah, okay,.

B

And a year.

C

B

Right, cool and we're live on YouTube.

C

Amazing: okay, see what screen Johnny Z I.

B

I, don't see your screen now: okay,.

C

Anyone in one seconds to change something.

D

C

C

Are we ready to go? There's the life, be a link set up as well live.

B

Peter's not working right now, I think I have their own stream key gonna end, but we are on YouTube my.

C

Problem might also be because they're streaming from the UX unconference, okay.

B

C

Hello, everybody and welcome to our 18th town halls, Tambor tenth 2018. As always, we have a lot of stuff to get through. So let's just kick it off. We begin today with experimenting with PSP air performance reviews with j-b.

E

Okay, hi everyone, I am Jonathan, also known as JV, and this is the beginning of week, number nine for meiosis, which is awesome. So thanks Sara, for making my first couple of months. So enjoyable I wanted to talk today about kind of experimenting with peer performance reviews and give you some more details about what we'll be doing in the next month or so. First off. Why would we experiment with peer performance reviews? You know really we people option as an organization.

E

We want to get a deeper understanding of what everyone is working on and the contributions and impacts that we're having traditional companies do this in a very traditional way. You might be surprised to hear so in a traditional company. You know your manager or your director would basically look at your work and they'd give you a rating or a school. It would be a kind of a secret thing normally and then every kind of six or twelve months.

E

You would repeat the process and basically someone would decide top down how you're doing and tell you that that wouldn't work for us. Obviously so in people ups, we've been looking over the last few months to design something that would really fit more with this thesis structure and the values and principles that we have, and so want, is just to share a few bits and pieces around that.

E

So we've been looking to design a system that there really fits so something that's open and transparent about what each of us are working on, not something that that's closed and secret, something that is peer based. So all of us allowing the community members and ourselves to to really provide feedback and insight onto the work that we're doing and not be reliant on a hierarchy or a manager, and then also something that is lightweight so for those of you that have worked in kind of big organizations or other companies.

E

You'll know that performance processes can be very long and taxing, so we're looking to make something: that's very kind of lightweight and usable for everyone without being too too difficult.

E

We really want to recognize the efforts and the contribution everyone is making and understand those better and also give everyone the opportunity to provide and receive feedback on their work on the screen. You can see kind of a small screenshot of something that the people ops team has been playing around with for the last couple of weeks, using slack and really just a lightweight way of for everyone, so posts the work that they're doing and for the community and the people involved here to kind of react and comment and ask questions.

E

This is a first straf than a first attempt, so at least to our knowledge. You know there is no no perfectly designs set in stone way of doing performance management across an organization like this, so we're just going to try something and we'd love your kind of feedback and help and support to do that. If you have any ideas, there's a post up on discuss around performance management and performance reviews and there's a newly created channel, perf 2018.

E

So if you're interested in this topic- or you have insights or suggestions, we'd love to hear them over the next two to three weeks, we'll be iterating a process and then trying to refine how we would use a system and at all and looking to launch there soon after and give everyone the opportunity to share what they're doing and for everyone else to review and read about what we're all doing as a community.

E

Thank you thanks.

C

So much Jonathan and that moves us straight and Sergei ours. While we're talking about reviews and Oscar.

F

Yeah sure so I thought we'd do a midpoint check-in for co workers and there's two people get to understanding where we're at, and we can do any course corrections. That's necessary. You can see up on the screen sort of briefly the objectives and then I think we can go over. So if each each main objective, very briefly for the people who know more about it, something you can go to next slide. Please, yes, Adam online.

G

Yep I am hey. Can you hear me? Yes, okay, okay I can go with the first one, so so, as far as I know, this swarm just started.

G

What we have down on the peer-to-peer side is that we provided some integration with LDS on like basic to checking the syncing on the on the on the server nodes and also discovering alias peers from that tree of network. But this swarm is gonna actually make the le s working in the app. So so we pretty much make sure that alias is working correctly. So even when you sing the dead chain, you you're able to create transactions, getting new blogs and so on so forth, because this is not checked.

G

But what we have done so far is that the chain is thinking and it can sync to the newest box, but yeah the rest needs to be verified. So that's pretty much what this forum is gonna do and if there are gonna, be any issues, it's gonna fix them, so so yeah, the next one and this copper a protocol with latency under one second.

G

So we pretty much implemented this protocol and tested it on our staging fleet and it's pretty good it's much faster and it all it pretty much does everything what we put in the requirements. The next step is to release this on our bed athlete, but that requires some testing. We don't want to break the previous versions, so um we plan it to do it with the next release, which is zero. Nine, twenty eight. As far as I remember so it's it's coming. It's probably gonna be Nick next or within two weeks yeah.

G

That's that the block one is pretty much done around this. The next one is since incentive by layer, proof of concept and spike Owen counties to provide. So for now we were just mostly talking about it. Is we're still not really figure out, like the like the exact on how you want to push it forward?

G

There's a couple of ideas: research papers about different different things, like proof of proof of stake, that we were looking into and proof coos custody for my servers, for example, but they add nothing, nothing really specific period and the next one, its whisper spam protection. This is also ongoing.

G

There's cause there's the proof of the proof of concept that is Demetri working on it's pretty much gonna work, this way that it's gonna rightly meet by IP or right here and that are sending too much traffic, so you would be able, from from mobile perspective, you would be able to see which peer contributes, the most your traffic and maybe remove like decide what to get messages from one particular public chat, because it consumes too much traffic or something like that. So so it could be much or you would have like much more control over.

G

What's got into your into your phone, for example. So can you get the next slide? Please, and there are two more things so the the next one is 50 users running status notes. This is mostly about integration with the F node and improving documentation. So if someone would like to run a status, no, that should be super easy. Alright.

G

Now we are doing that in the car on our servers and that's fairly easy, there's just a matter specific, a couple of options, but you need to document that this kind of internal knowledge right now, then we need to put that into into into wiki in some Doc's, so other people can do that and pretty much around and node and joints and status network and be a part of it haven't, really want to be just part of that.

G

Your network in the file, the final one is made servers discoverable my servers, this kind of posts right now we got to the point where we have made servers and they are discovered using this Kaveri protocol. We have also a very simple smart contract that allows you to register your main servers and and just make sure that they are kind of trusted.

G

This is also very simple solution, but what we wanted to achieve here is to increase the number of my servers that people can choose from and yeah. However, we are also thinking about the redesign in servers because there's more issues around my servers architecture right now and maybe that could result in Lake Tahoe. We had rearing this and rewriting my servers pretty much, but um but yet this is not yet decided. So that's a bit thanks.

C

So much Adam that moves us into UX.

H

Hey, that's me, can you hear me yep.

I

H

Perfect and so the first 110 percent of musician es name was currently scored in a zero, because registration isn't open to you there's yet, and the 60 percent confidence level comes primarily from the fact that 10% of you years feels like an ambitious target based on both the engagement that we've seen in the past, with other centers features and also because of the low discoverability is our feature.

H

Current designs have a look listed in the profile screen, so it's a bit hidden, but even if we change this I think that 5% would be a more realistic stretch. Target increased chat, daily, active users by 500%. This one isn't properly scored. Yet Adam is actually pulling lists for data for the past three months today and we can use this for data combined with either historical data from Mixpanel or potentially am acting years data as a proxy for our user base here and that's it for the slide.

C

This steps towards to water down on mrs. Graham.

J

Everyone working hard on decentralized scaffolding, force organization and we're making good progress on the S&T voting duck, gave the scored in 0.3 and a silly person confidence on that.

J

Largely for that, as we believe that, if we provide Hardware wallet, support, namely ledger we'll be able to easily give it 50 people to to contribute and then for the million isn't he voted with I think we're doing quite well here, since the first vote got over half a million S&T and voted on so I think once we get hardware model support and people can vote with the S&T that they store no hardware wallet. We should hit that fairly I think fairly easily with regards to adding top of democracy.

J

Barely Richard and Ricard are doing awesome, work and the so she applies more for that. The other two balls, but they didn't awesome, work to try, remove friction for the users. That's, namely reducing gas costs or get away with gas costs. Well, it's really amazing is that each one of them are trying to do this through different methods, which just goes to show how I'm interesting in new the spaces.

J

With regards to adding topic, democracy to S&T, 30 recorders, doing some awesome research on this in terms of how to how to scale it up and bad moment, it's pretty much in the research phases so get an or point to you and at the tips in confidence, because until we starts actually a planet, we don't know, then, with regards to five percent of poor contributor compensation. Three liquid pledges. This one needs a lot more work and we haven't really started on it. A big reason for those.

J

We believe that the items above it need we need the learnings from those items in order to start working on that, but yeah. That's that's our first steps towards that Thank.

C

You Graham, exciting stuff, that's right so for developers.

H

Thanks I'm, just a new developer site live with three sections: complete this one's RNA at a 1.0. We finished it and you can check out the progress on Doc status. I am, and now that we have a new technical writer on trial, will collaborate with the new Indian and Julian on this documentation. Efforts are picking up again and that's get a lot better. Organized a new developer can follow the build status, QuickStart set up status and twenty minutes or less, and this score has no mathematical foundation at home.

H

But basically alex has made fixes to our build scripts, which I'm blocked a lot of the common issues. People were running into with running status locally. However, we still see issues with this from time to time, and we think this is due to two reasons. First could be developers local set up, and the second could be that changes have been made to the build script since that aren't necessarily communicated throughout the Oregon that we aren't actually aware that might be causing issues so to improve. Here.

H

We need to at first test the process on a range of different machines and operating systems, and then second communicate a little bit better amongst ourselves if changes are being made to the script and then, lastly, for me, is to external teams, using extension, I've scored. This sort of point, for it seems like a better goal here, would actually need to say that we have two solid extensions and use cases built.

H

We've, that's a lot more reasonable, like prog, and we're we're very close to having one solid extension built now and so choose maybe, but we're also in talks with some other teams about potential integrations to.

H

Unless, when I you take cool.

C

See ya. The last thing he has 70% of DFS are optimized for stylus, which is a program that we're thinking of putting together for developers we're still not entirely sure what optimizer status was. There was sort of two different options for us either. If we had decided that implementing dab, curation of some kind of sorts was a priority, then that might have led to a certain kind of optimized for status program.

C

The other option is, of course, different DFS that actually use extensions would qualify to be optimized for status and be rewarded in some way for like integrating with our native features and using our components and making a slick user experience. Obviously, both of those are sort of just blocked by technical considerations.

C

At the moment, this further research to be done on how to do data curation in a more complete manner, with decentralized search and there's some interesting people in Berlin that we met and talked to about that and extensions is definitely going to change the world. A lot of people are really excited about exactly how that looks, but there's still some technical considerations to be talked through and Young posted. A really interesting thing on discussed today about some of the sort of technical protocol considerations to go through with extensions.

C

So if you are interested in nets and extensions going to make developers lives so much easier, I encourage you to read it and comments that moves us into reducing our Wall of shame, which is back to Oscar.

F

Sure so, first off OOP sorry pervert food security. We blame MEP imputation is functional and we also have formal spec. It has been started, it's not she done by Andrea and Pedro some work around UX and K exchangers own. So that's the zero point, seven and fairly, confident in that being achieved is quarter as for top ten wall of shame. There are so bunch of them and they're kind of spread for our teams and so on. We have finished a few of them and this multiple in progress.

F

But it's still sort of too uncertain to to tell this is miles away. You can look into more detail principals. The main thing we achieve there is that which concerns around them and we have more than 50% of Kokiri to sign them and we're also starting to see use of them more broadly in teams and presentations and how people think about things which was ultimately the indigo we're still not at 100%, but it's likely that that will only come. Come to fruition, well swear a vow and that's with a specific blocker and so on.

F

So we're not gonna. Do anything more than that? We're happy with having a supermajority for that on that, for now, as for coaching is being assessed for security impact course been doing, a lot of amazing work there, and this some heard some good stuff happening in the blocks in week in Berlin, in terms of coming up with security practices across the industry, and so on and document eaves are in progress and hopefully we'll see more of this week to come. That's all full of shame.

C

Thanks Oscar so into some of our non tech updates and thanks Jonathan for welcoming a new core contributor cool.

E

Yes, welcome arseny, so hopefully we'll have many more new joiners, but welcome to everyone that's joined recently. We are still hiring so lots of open roles will be refreshing. The priority order of the roles that we're working on as have some updates on how we're doing recruiting in a future Town Hall. If we could pop to the next slide, please thank you. So three, three broader updates one so Prague I am super excited about program meeting everyone in person.

E

You should start please to book your transport for Prague and add to the spreadsheets, and we can ensure that we have the right number of hotel rooms and order logistics or sits. So any questions. You know police asking the people optional, but please stop working your your Transport for Prague code of conduct, so many of you, you will have seen that we refreshed our code of conducts and put it in our new handbook. Please do check it out. The code of conduct isn't set in stone.

E

So if there's something missing or there's an important addition that you can recommend, you know again, please do contact us. You know in the addition absence of like traditional management or Araki, it's really up to us in the community to kind of enforce these standards ourselves and to set these standards. So they're gonna call out that if you see anything, that kind of doesn't add a sort of conduct. Please do please do call it out and then, thirdly, and really exciting me recruiting updates so we'll talk about this more in the future.

E

But we are beginning to tests more non-traditional methods of recruiting. So, traditional being you apply to status with the CV, you interview do a round of interviews and then we make you an offer where we're really starting to push those boundaries and try different methods of assessing people, both through trials and part-time work and scrapping interviews in some cases altogether. So just that kind of call out that you'll see kind of different, weird and wonderful ways of joining and contributing to statuses, full-time core contributors.

C

As always, the more the merrier right, the status to do and our educational dollars would actually.

K

Quite fast, in the last couple of weeks, we've done three major three major. We pushed on three major topics. The first one is that we created a an educational content, map or graph that essentially shows the relationships between various education topics and content that will be on status studio. You can take a look at that.

K

It's the link is, on the right hand, side column, it's gotten some really good feedback from technical experts here at status, so it's looking very robust and it will inform defining our personalized and customized learning paths for the various users that come to status studio for education. The second piece that we pushed on heavily was creating a poll that was shared at 8th Berlin and we got 8 responses so far to it.

K

I will be sharing the summary of those responses to those questions from the survey on the Status channel this week, but all in all, it looks like there is a lot of enthusiasm from experience developers as well as new developers. Forests for a product like status to do, which is great. There was some good feedback in there as well around prioritizing the various features that status to do is planning to have both on the ide side as well as educational paradigms. So that's something I'll share. It's a it's.

K

A pretty high-level survey, so shouldn't should be shareable with as many developers as we can share it with even outside ëthe Berlin. So we will be posting it on our social channels as well. The link for that is also on the right hand, side so would request everyone to broadcast it and share it at events that you might be attending workshops, etc, where, where developers might be the primary audience or even on your own, personal socials, that'll really help us out a lot and the third big push was recruiting for the studio team.

K

So we are still looking to fill a senior UX, UI role, the front-end developer role and the tech content writer role. So if you have referrals, please send them over, you can send them over to me. My email is listed there or to Barbara, Harry or JB who are working on this as well.

K

In the coming weeks, the the focus will shift on further fleshing out and detailing these personalized learning, algorithms or paths that you're talking about on status, studio for education, but also shifting gears a little bit and fleshing out in more detail the IDE MVP requirements and and tech specs, and things like that and what's needed, what's needed to be built there we'll continue to brand studio, I think Ned and the marketing team have already begun on that and we'll start executing on some of the high level marketing marketing plan for studio for the rest of 2018 as well.

K

That's it on my am thank.

C

You so much actually, as always, a really really great updates and I do encourage everybody to share that link arts. It's important that we gather developers feedback from as many diverse places as we can to make this a complete experience.

C

It's like, since in marketing with Johnny and Shawn thanks.

B

Andy so we're we, we had two campaigns running or we just wrapped one, and we ran a digital hackathon with bounty one. The goal of this one was to create app that can be used for an event right, so sorry adapt that can you using an event using Embarq to try and help promote our hackathon, but then also raise awareness for embarq, and we saw some really good responses there. So it's a nice way to tap into the developer community there.

B

You can see some stats down at the bottom over a thousand views, 13 users I think in total there are around 10 submissions and the team's reviewing those now and we'll announce the winners shortly and then. Last week we launched a joint campaign with the get coin team. It's 60 bounties over the course of one month, and the the incentive here is, if all bounties are completed at the end of the month, will issue an smt bonus to everyone.

B

Who's completed a bounty and we launched with 13 bounties last week, all defined by the embark team and within six hours, work had started on all of them, which is really encouraging to see so we'll be we'll be announcing the next batch of bounties shortly. So that's exciting.

L

M

Yep, okay, so on to the community competition. So yeah really awesome we're at the halfway point right now, so the first stage of the campaign or the competition was to actually get all the community entries first and foremost. So again, this is all being led by by hutch. It's doing an amazing job on this, but then also um Jessica Jessica angel from the art community she's been doing an amazing job as well rallying the community. Behind this, so we had a total of 191 designs.

M

Submissions, which was amazing, I, really blew us away in terms of other metrics. So far, we've had a 539 mentions of community or proof of wear which are kind of our two hashtags. We ran for the competition.

M

Obviously the reach was 3.2 million and the total engagements. The other piece that was really awesome, was that we actually saw entry across a broad spectrum of countries which they compared to our meme competition. Even you know, we got to see some designs come through from Korea and China, and even our even our spanish-speaking community, so that was really awesome, but that's only the first phase of it. So the first phase was the design phase. Then we went into the voting phase which actually kicked off at F Berlin.

M

There was there's kind of two elements to voting. One was a voting gap which there's been a confusion around. It was meant to be primarily for the F Berlin participants to vote on the spot. You know some people also voted that weren't an F Berlin, but there was that element, but then for everyone else. Voting still continues. So please be sure to LIKE and retweet your favorite design. We will be amplifying them and like retweeting and promoting the finalists in the next day or two.

M

So if you haven't seen the finalists on your socials you'll see them surely voting closes on the 14th of September so be sure to get in and like and retweet your favorite design and then obviously we'll go ahead and print them onto the next one. I just.

C

Quickly before we move on, wanna show the design on Iran, which is a psychedelic status.

C

Made by yellow is definitely the best shirt.

M

So if you want to see the designs, we've got two categories. The first one is can designs that are based on our values. So it's a combination of you know. Some of these you'll see there they're based on our values. Other ones will just be based on our branding in general, but you'll see the five year. So some really cool designs, just gained you'll, helped narrow these down, and now it's entirely up to the community.

M

We will choose the most engaged t-shirt, as the people's vote vote will be the choice that we print on to the next one, and then this was and he's gonna hate me saying it that crypto culture, something was a bit more broader, allowing for a more you know, creativity, flexibility, I, thought Andy would particularly like the Africa one, but but yeah some really cool ones here as well. So again we're gonna, be we have two categories will be printing the finalists, the the winners in both categories, so please be sure to get in your votes.

M

C

Obviously, I love the Africa, but still like vote Fibonacci goes.

M

Kook now on to F Berlin, so I am gonna, give a lot of credit to a lot of people, because there was a lot of people that were involved in this. Obviously, you know everyone did a great job with all the content contribution you know there was. Everyone was just busy on Twitter posting contents that that's it wonders for us. We also had you know how I identified Milan a member of our community, who became a roving reporter.

M

So taking the lessons from ëthe India, we applied it for four at Berlin and Milan did an amazing job. You know Kim and Hutch and myself. You know we're busy kind of working with Gianni and Milan the entire weekend trying to get our content pipeline going. So that was that was an awesome effort there so yeah. So in total, what we saw was we saw a total of six hundred forty one status mentions, which is you know up on top of earth India, which is awesome.

M

The total impressions off the back of those mentions is 5.4 million, and the total engagements of status related contents was one 1766. So in total we had around thirty eight pieces of content across Berlin and that wasn't actually all from the Status channel. That was a culmination of all the different, the different community members and core contributors that were there, so that was that was really awesome all to the next one. Sorry I'm gonna stop talking immediately after this, so we did a so halfway through the weeks it was a very busy week.

M

Last week, I'm halfway through the week, we actually hosted a AMA on WeChat with a community group, slash media group in China called uni times, so they were a sponsor of the etherium Industry summit, which is what Oscar will speak to next, and you know as a piece of promotion in the build up. So that's we actually hosted a about one hour, AMA with a developer community in in China, and it was all done through WeChat, so he shoutout to Stephen our part-time community manager in China really helped us cue that up as well.

M

So a total total number of participants was 580, but then there were actually other WeChat groups that were also in parallel. They were asking questions, so in total there were another 2074 members as well. If you won't actually see what the questions were, we actually have them in English or if you want to flex your your simplified Chinese jump in and you can have a look at it there as well I.

M

Think Oscar is gonna, speak to this cool.

F

Yeah, so thanks John, so this weekend there was a conference in Hong Kong from scalability in this intuition from 2,000 people, and it was a kind of a mix of fum, 2.0 researchers and sort of I guess more traditional industry. What's interesting about it. Is that I feel like in in Asia this sort of a completely different blockchain ecosystem, that's quite mature in terms of integration with banks and governments and these kinds of things- and you know it was in thing to see it firsthand these people and what you're working on.

F

So if anyone gets a chance to grow and if these conference I would recommend it and I believe they will upload videos later, I also gave a speech on sort of security experience and Nimbus and developer ecosystem and these kinds of things, that's it for me. Thank.

C

You Oscar, alright.

B

So here is a new design that Ned Michael, hazel and Christian have been working on. It's the new websites, a new branding and we're getting ready to launch this at the end of the week and really excited about this, because it'll really start to pull the events. You know the look and feel and the ethos and just the vibe of everything together.

B

The next steps for this is localization into any language, really we'll put out a call to the community to localize it and then we'll push that to production and then just working with the team this week to to identify various experiences and happenings and really to come up with something that will enrich the experience for everyone there. And if you have an idea. This goes out to anyone.

B

If you have an idea for something you'd like to do, share or see at the hackathon, please PLEASE paying me or anyone in the hackathon channel, and we can work with you to make that happen.

C

Yeah, it's not like the happenings the most happening thing that happens at the hackathon.

B

And then a quick reminder so DEFCON 4 is coming up obviously, and the next wave of tickets is set for release 1:00 a.m. GMT +2, so, whatever time zone you're in please, please remember to use the promo code, that's been shared out in the DEFCON 4 channel and try and buy your ticket last time tickets went out or sold out extremely quickly, so we should all be ready. It should be a reminder in your calendar as well.

M

Cool I'll jump in for this one again.

L

M

Cool so yeah, just quick recap, so, obviously, with any kind of ethical event, we see our overall mentions increase quite dramatically, but on top of that we had the we had the FS event, which actually did get some coverage. I couldn't really understand much of it, but if you can actually see on the bottom right hand, side there was some. There was some coverage of Oscars presentation, which was awesome to see some press coverage there, so yeah. So overall we increased by 47%.

M

The great thing to see on the bottom two is that in previous weeks or in previous town halls, the past two we were kind of, we were on a downward projection on our own channels and there was some learnings there in terms of the frequency of publishing and we had been impacted from an algorithm standpoint. Fortunately, from an impression standpoint, where we've hit flat and from an engagement standpoint, we've actually gone up a 34 percent since the previous fortnight.

M

So that's that's a huge win and it's just testament to all the great work that everyone's doing across the board and F Berlin was just awesome because we really had a lot of conversation happening there. So great cool.

C

Web refresh is joining Ned's.

B

Gonna jump on this one hi.

N

Yeah I just wanted to give a quick update where we got to on the web refresh plan. So we basically broke this down into kind of three phases. With the first phase, we're gonna try to get accomplished kind of like pre hackathon and that kind of just entails in the first phase, taking a lot of the existing design elements that have been created that are really working that Andre and Dennis had worked very hard on.

N

So we want to leverage a lot of that language and unify the whole brand ecosystem together, so very simply start to be able to differentiate things and see how everything works together on these two platforms.

N

So we can also then test react and goes together and see what works best for everybody and then, in the second phase, we kind of want to continue the auditing of these tools and slowly start to upgrade them for the future, and the third phase would be using those upgraded tools and languages and components and UX interfaces to really shape this new visual language that we can scale for the future.

N

So essentially, we all have collectively InDesign been looking at looking at these current principles and applying them to our own design principles and thinking about how we can scale that up for everybody to use. So that's the plan.

B

One one added note on this and Michael's shared out a doc requesting content from the team from every individual team to define their own principles and those principles will ultimately live on. You know the website so Michael. If you can share that doc out again in maybe the marketing channel, and then we can all get around to that.

C

Cool I think that might be the fun the principles as they apply to our overall principles, but buckle makes make it clear. We move into UX and ux r with pets thanks.

L

Daddy, so we just wanted to give a quick update on some of the work that actually went on last week, as everyone has been doing. Of course, the the design team usually likes to to meet when there's kind of like a major events, that's in Europe or elsewhere, where we can all get together. So we spent about three days last week, diving into a couple topic areas that we wanted to do together.

L

Face-To-Face so tennis, for example, looked at some of this hardware wallet work that he's most recently been working on, and we did a little bit of a review. Of that. Another example is has to let a kind of a cool brand and personality exercise where took a look at or really asked ourselves what our status users or who our status users are.

L

What are some of the attributes that make up as that as user for for a little bit more depth, and so that was some sort of like interesting results from that and then to mix things up, we got an intro to the whisper protocol from Eric.

L

You came in and did about a 90 minutes session on it or the Q&A session, plus some informational insights, which was really really helpful, so kudos to Eric for doing that, and then also we on Thursday, we had six user to study sessions where we we took a look at certain some proposed redesigns for chat, commands and inline messaging, which we plan to have a debrief and kind of a result share up later this week. So this is quite quite interesting.

L

Insights from that, so next up as well and we've all planted to try anything or most of us trying to get that are trying to get together for Prague as well and the DEF CON, so we'll have another sort of meet up at that point.

L

As I mentioned the UX, our insights are coming either later this week or next and as Ned mentioned with a big task. Looking into you a web refresh in an in your design system. Think.

C

That's yeah, my apologies for the messages coming in over your speaking there. This is coming to you live from the UX on conference in Berlin and the slight interruption anyway that moves us into the inference. Fooling with you, Jakob is.

F

Younger Jacob yeah he's been he's, not here a second briefly.

F

Yes, there's been some work around Ron Jenkins and parallel bill. Sup also load balancing for the swarm cluster and some analytics set up new cluster started. Work on deterministic builds was up and then coming up. It's tinker's tested, builds on Windows and some more drinking stuff. It's been a lot of work on Jenkins, but it's really shaping up so great work and take up and everyone else who chimed in with Igor and Andrew and a bunch of others. Yeah.

C

Definitely, let's see you go for helping out there, it's been a long process, but well worth well that moves us into chat and Pedro hi.

O

Yeah so last couple of weeks we were mostly focused on PFS and helping out with the hardware wallets. There were also parallels. Some work done in several non user facing improvements that will help with, for instance, testing it's something that we saw the last and I think one or two weeks ago we saw issues with mail server, but it wasn't easy to get to the logs and to test different leads. So that's something we implemented under the Advanced section.

O

So it's be much easier from now on to debug, lower level stuff, and we also cleaned up this configuration from status quo, which there were many places where defaults were living in, and that was several different ways in favoring status go so this was all we unified them in a single way.

O

So it will be much easier for new contributors to figure out where to how are things working on that also, there was this work on chat, badges and the ability to scroll to the unread or to the bottom of the chat it hasn't been merged. Yet because there's some problem with restoring position on Android, so we're not yet happy with workarounds that we've had to to apply so still in progress, yeah and that's it for chatting thanks.

C

So much and perfect forward secrecy from umbrella.

C

If he's around, otherwise maybe Pedro can just talk us through a little bit more about what's happening with PFS.

O

O

O

We've been working on implementing.

P

Sorry and yes, the new thing that we've been working on these multi device and a group chat sauce so that the encryption layer, so that user can seamlessly use desktop and mobile by flying. So that's something that we're working on. So that's kind of been done. There are three bugs to fix, but we'll continue with a documentation. New stuff will be documented as we go along and this week and next week we'll be focused. You know and basically push you know.

P

Basically rough version of group charts as they were before, but using PFS, which allows us basically to test BFS. It's going to be featured toggled in a safe way, essentially, messages to send through its new chat with anybody know at least would use PMS. That's all it's.

C

Really really incredible news not only is perfect forward secrecy, part of our Wall of shame and really important, see like that I'm doing privacy push the group trying to achieve its status, but also the fact that you're bringing back group chats just deserves absolutely massive kudos. So thank you so much for that work, Andreea and that leads us into wallet in accounts. The first is ENS username with Ricardo.

I

Hey progress: okay, let's read some other. He then in a special condition, see the Registrar that we protecting the smartphone track or leg over usernames that we decided our minimalism link, someone severed more words and to be only alphanumeric tractors, similar names.

I

There was a four week factor of the original star contract to simplify the features with these Lexus changes that for the flesh metal, we are better support to a proven cow of the mini-me total on the contract in the UI. So right now you don't need to approve the token first and then register you can do it everything just one one typing the password only was in a state of UI.

I

We finished the full coverage of the tests of the Bismarck context, and the hue I also has been only optimizing for status and talks with the users of news on status, which should forget.

I

The next step should be the reviewing the final opening. So a little, we are having some problems you find some out. There seems like they are all busy. So if someone knows some suit, we have some who we can talk with to find solves. Some reviewers we also going to do some internal audit with the two. So yes, by this outlet of that, the very actively like there is sauce announcer that developer spritz, that that can help us internally. Only in this context also, we need the integration of DNS usernames look up, they stay Kozak.

I

So it's one from the.

I

Once you join the swarm to the greatest I think it's pretty straightforward, it's just looking up in the contract minutes compact, we usually take very then resolve it.

C

Cool, thank you so much for father yeah, one of the key findings, I. Think of the UX testing sessions that we've been doing, particularly in pelennor on this week, has been just how much people struggle with randomly generated names and having easily accessible user name. It's gonna make a real real difference to onboarding, and you know another really exciting thing that's been going on, and one of the features that I've had just love of working at status is that we can broadcast from Berlin and then get updates from interrupt in smart contracts.

C

Lorries in the Brazilian rainforests- and it's just you know one of the neat features of status and what what happens here. So thanks that moves.

I

C

I

User names, who would help user networks unit by unit by themselves? So if you don't want to try them something wants to kill themselves on animals right, of course, like.

C

Yeah as much room for expression and freedom as he wants, that's the whole points. So even it's 170 in wallet, one of the improvements with Quran, if he's around otherwise we'll just skip the slide for this week,.

C

Cool we're missing, Goren, not a problem. It's a voting to 79 with Graham cool.

J

So this week we have a survey ready that go so a big thanks to Patrick, Sean and hutch, for coordinating that we're gonna be sending out to 100 people and it's gonna be in five different languages and pays 50 SMTP response. Basically we're looking to find out what are the big topics that holders of S&T your care to vote on and and then something investigated as well, is how can we make voting more attractive?

J

We thought we pretty neat if you could get a collectible imma, so that's like a participation type reward so to research that we had a meeting with the pixel or a team myself and Barry, and what we found out was at this very moment. It's probably gonna, be you know two too much to kind of take what they have at the very instance to bring into the voting gap. So it we think further out the line we can do that. But in the meantime we can.

J

We can definitely do some sort of concierge MVP, similar to what the marketing team did by pre, buying a bunch of entities and then giving them out randomly to people who participated votes. So you think we're gonna be trying. Doubts like that.

J

Otherwise had an interesting to meets reviewing designs and user flows with Mary and Patrick, and what we realize is that, where someone keeps the S&T has a huge impact on the UX, and so the first thing that you have to figure out is the better handling of allowing users who hold the S&T and say a ledger wallet, for example, to use the version that and partake in status governance.

J

So that's the first feature we're going to be working on otherwise very kindly put up a github repo for the smart contracts and the voting that and while it's that important well, we realize that, in order to maximize work done on, this really need to be taken advantage of community involvement and participation. So we're gonna be attempting to get some bounties up for voting that work and yeah. That's essentially what we're gonna be looking at next week gain some bounties gain.

J

Some survey results, updating designs and hopefully getting some feedback and researching one other thing through the flow is investigations with Murray and Patrick, as we realized the best possible flow. The the easiest user experience is that if a user has status on the mobile app and has S&T and if they're in their wallet it's a cinch, it's a beautiful experience. They can always go to status, check group to to ask questions.

J

So on that note, we're going to be researching how to bring more of these government's features into chats, starting with sucking on how we can get to voting that to work with extensions and yeah. That's the the weekend to.

C

Mexico have such flow much future, which moves us into depths and developers with Rachel again now.

H

You say um so on the user side at least past two weeks, couple updates, if you own a piece of students where you can ask those tokens in your status wallet thanks to Julian, we've added support for that token, because first of all, digital art is dope and second of all, we wanted to support pic Sierra.

H

As the newest member of our incubator program, Andre is working on a very cool feature to pop up a chat modal from the browser, so that will generate a whisper topic for each DAP, which means that you can imagine if you're already using crypto, kitties you'll be able to open a public chat about crypto key means directly from the app and from there you can chat with other. You know: Kitty owners or breeders. So we like this idea to help build a community around ads and facilitate communication between users in a decentralized way.

H

A security update from Alex we're also working on implementing meta masters, phishing to text, block protection system, known crypto, phishing websites, and we're also going to be implementing Google, Safe Browsing API to warn users against other known, scam websites. That's all a work in progress for developers the web three opt-in flow. If you are a developer who's ready to test that implementation from the IP to that can be toggled on from development mode inside status.

H

Now it turns out that the update actually conflicted with the existing standard, so by making it optional from development mode, you should be able to test than you opted in a controlled way without breaking your existing web 3 implementation. Also, our first version of E&S resolution in the browser is on production. With this, we currently only support ipfs hosted sites where the resolver utilizes the content field, but we're participating in discussion about a more comprehensive standard than this.

H

That would also support swarm with other browsers and then for the next two weeks finishing up that work. They just mentioned above and then switching our focus back to extensions and other tools. Our big goal is to finish the first full extension use case, which will be a chat command and a great example of that, but we're also going to implement it's going to be sending you or your on of teams within chat. After speaking, some developers Verlaine, we feel validated that there's been a demand for this kind of command.

H

We're also gonna, like we'd, be adding a QR code scanner API. This is coming from a question. You know incubate our team at block party, but you know it's also been requested by a couple of other developers. So we'll do a bit of research and other. You can use cases for the hub as well.

C

Thank You Rachel interim buck with yuria.

C

Who we might also write.

A

So so this last Lux weeks, we launched the burning campaign as it was already mentioned. We also implemented support for the EIP 1102, which is coming in the next version of embark. So this way that's trying to generated would embark will be compatible both with existing solutions and future solutions, namely with Madame, masque and other deaf browsers.

A

We also are revamping the swarm support, we're creating a JavaScript library to support the new swarm api's.

A

We are finalizing the code coverage and this last two weeks will also been doing a lot of bonk hunting for three point you so that's been taking a bit longer than we when we taught, but will be worth it for the next two weeks, we're going to be releasing three point two and we're also going to be doing more parties.

A

That's it this week. Oh thank.

C

You so much fury in the desktop with fiddly.

D

Guys, the past two weeks, we've been following a couple of attack factors, a couple of long-standing projects that are already completely nearing completion or the Mac OS code, siding and lots of a lots and lots of various jenkins and build pipeline improvements.

D

In relation to that, there is some work done and on the improving of test coverage using expect generated, testing also max has completed break but integration, which is a nice little tool that helps with crashes reporting, have been also some mac OS build fixes because we only support mac OS for now and on the code from not related to packaging and distribution.

D

So on the react native desktop- and there was some ongoing work on the chat window, actually the underlying proponent, for the chat window in order to make it more performant and in order to fix some issues that have been plaguing it for for some time, like jumping and some clicking, could click on press event, handler processing problems and we've also had just recently a very first external team chatting contribution from Andre on some profile name and picture editing PR. So thanks very much for that.

D

We also plan to work together with Julian on incorporating some extensions work so that you have some extensions that could be developed in order to target both mobile and desktop platforms at once from the get-go and generally, our plans for the next two weeks: good, continuing working on the scroll view and react native upgrade so that we unblocked some of the PRS that have been waiting for the desktop upgrade to o56 on mobile, again completing our test coverage projects and more och fixing, because we still have some issues that are there in to-do list.

D

As you see, there were still then issues into the list. Yeah and I know when this will happen exactly maybe for six weeks. Hopefully we could manage to do this before our off-site meeting in hackathon and the ad of October. We would like to move for status test simply become as a preferred solution for as an internal chat solution, instead of slack so first time at initially.

D

This will be a very, maybe not very bad, at quite a bare-bones experience compared to spec, but we promised it will keep adding more and more features so that it it's worthy and better alternative yeah. So that's my update.

O

We're going to discuss tomorrow in our weekly meeting is to use the desktop on the chat team for daily development, so that should also help uncover pain points.

C

Yeah, absolutely you got a dog food, rentals and the I know. That's Chad is on a flight at the moment, but he would definitely want me to say that there are whispers of a revolution moving through slack and we've got to get over to desktop. So also all core contributors prepare yourself for that see.

C

If you can go to uh Natalie's page download, the images that are there at the moment play around with them see if you have any issues, give us your feedback and that's really going to help the process as we move this along and also desktop and extensions. Oh, my so that moves us into hardware wallets with Kido II. Yes,.

Q

Hi everyone so for the hardware, what it light, there's been actually quite a lot of work in the past two weeks and we are in this important step where we define exactly the product with a detailed UI flow that define all the exact screens and that content, taking into account all the castes and the events that can occur.

Q

And so this effort is ongoing and then it is doing a real great work putting that down, and it really is a team effort to take into account all the constraints we have, whether they are about technical constraints, user experience or content. So what's next is we want to reach a first team? A crude version of this UI flow in the coming days. Run user testing on it make the necessary changes to the flow so that we can actually start the doing fermentation to subdue software implementation, and we also want to define the packaging.

Q

As for the Android software and from implementation, we have now a first prototype for the installation. It's running, meaning we can actually upload a card with the applet through NFC. So congratulations to Andrea McKay Michaela for that, and we want to now finalize that we have some stability issues.

Q

I've now called for participation and feedback here, since we have an architectural decision to take. That's actually going beyond the hardware Wallet scope not going to go through all details. Now what we have to decide is which derivation path we use from our master secrets to get the whisper key and when the user has, on other words, which the relation path we used to get database key. So this map, at least the whisper one is, is used even when there's no, how about it.

Q

So this is really a team effort where we need some consensus to make a decision, and it's not a choice that it is it wavered. So please go check Mackay a post in discuss about this, provide some feedback so that we can reach a consensus and move on.

Q

As for sourcing, we had meetings last week actually with the the top three suppliers of Java cards, which are German and XP and Damian, so good progress there and one priority for the coming two weeks is to evaluate the the NXP one, which seems to be quite honest on our web Pro.

Q

The goal our goal is to evaluate the options we have for the main chip that we use, so we met last week with both st STMicroelectronics and NXT and what we're looking at priorities the ability will have to use open source software on the chip. The level of physical protections would get against the tags and, of course, the power consumption.

Q

So what's next, we'll continue with this effort, get some documentation from an XP that the promise to us get a natural demo ball from SD micro for our target chip, which is the stm32 WB, and also understand the microchip offer microchips, another chip supplier yeah by meeting with them so yeah, that's it for holidays. Thank.

C

You so much Guillory and that moves us into our house action research with mommy, so.

R

On numbers, for the past two weeks, we were mostly focused on, let's say infrastructure, so we had devops autumn clean up with everything, aligned, fast castes and manageable by everyone in the team. We also realized for implementing the byzantium fork that we couldn't use any of the ce o--'s plus plus the library due to licensing. So we are going to implement from scratch as zeddicus nuts cryptography that are used in some free compiled, it will probably take a month. Also.

R

We also had a lot of improvement in a blockchain state, so adding the upstream tests you to Nimbus and also enabling reconstruction of the blockchain state from peers and.

R

Some steps toward contract call and creation, then we have also started on less protocol and on the research side on the earth. 2.0 simulating proof of stake votes and we also detected some design issues that would be reported to the Ephraim foundation next first day for the charting code. So for the next two weeks we have lots of goals, but mostly advancing on contact calls which are blocking our pcs.

C

Thank you so much Mary, really interesting stuff, as always, and that moves us into Q&A and anything from the audience. Johnny is the anything in the YouTube channel or yeah.

B

No direct questions, but there was a comment about sound notifications within the app. If there's an update on that.

C

This should be I know that there was a pull request that was merged I feel like it's 596, but does a droid. You know.

O

Yeah, as far as I know, it should be working. Kids should have been released, I've.

H

Been getting them if you get a direct message and you have sound on, but.

C

If the questioner is not getting them, then feel free to either take your phone and report three insta-buck or suggests an improvements in our Help Center in the app that's the easiest way to make sure that we can grab rather insta-buck is the easiest way to make sure that we can grab that we'll grab the logs and see if there's something going going wrong if you're not receiving, sounds push notifications, the.

N

The one thing I wanted to add before we finish is: there's a discuss post about tweaking the format of the townhall. So after almost 20 town halls, we are team, size has grown a lot and so there's a lot of other things that we can there's a lot of updates is a lot that people want to.

N

You know tell us and things like that, so what we're planning on doing is splitting it up, so that we give teams more of an opportunity, maybe fifteen to twenty minutes with a lot less frequency and that allows teams to have Q&A it allows them to. You know, show demos and for those that haven't seen it there's a discuss post and you can see the details and from next town hall will be implementing that change.

N

So hopefully we can stick within the hour and start to give people a lot more kind of depth on each topic. If you have any thoughts on that, then obviously leave some comments and discuss otherwise. From next week from fortnight, from now, you'll see a tweaked uptown mole.

C

Cool I'm, looking forward to that personally and with no further questions, I think that that brings to an end our 18th one and thanks for joining us, we'll see you next week for an improved version of the townhall like.

N

P

J