Transcript Part I
Unknown 0:13
Engineering meeting
Unknown 1:29
re there any topics people wanted to discuss before we ask is our community members,and Larry,
Unknown 1:32
let’s see here. I can’t keep track of the whole timeline. But after the most
recent browser push, I want to say um PB Jay was asking about that about the
bug that Apple flagged these basically, like, I need another immediate hot fix
on the browser like yesterday, or something like that. And I think I sent over
to Hank. And I’m just wondering what happened with that. I know we’re trying to
get better about our QA process, but it seems like we’re speeding up those
releases, not like slowing them down. So I was just curious that anything
happened with that and what is the state?
Unknown 2:06
Um sure I can speak to that. Um, nothing happened in terms of breaking that QR
code scanning. There’s some old tickets that got brought up from way back when
will originally built it. And I I guess the way that we’re embedding a web view
in the native, I believe it’s never worked. And I think it just didn’t get
caught by Apple reviewers before now. Yeah,
Unknown 2:36
yeah.
Unknown 2:37
And so what happens is, the native apps actually add like a parameter to the auth flow. And so we can check for that. And basically, we just, we check for that parameter. And if it’s there, we hide the Scan button.
Unknown 2:53
And so I implemented that got some review. Shreyas has caught something for when
you went back and forth, kind of between different views that fix that
yesterday, kind of early afternoon. And so I think Shrey if you can just confirm
that and then I think we will be able to push these to the web. That’s my that’s
my thought.
Unknown 3:16
Yeah, that’s definitely exactly what happened regarding whether that was always there or just showed up recently, I’m pretty sure that flag real asked me to ask them if I get iOS secure, because of this feature, because we knew this wasn’t working. So I feel like it should have been handled. That was the whole point of the flag. I don’t know how it progressed. But yeah,
Unknown 3:41
yeah, if you look at the ticket, I tried find the link I don’t have it open
right now. But I’m Will brought that up. And then you kind of went up basically
said, okay, we added it, but then the PR just got emerged. And it was okay to do
for like, a future date instead of the others. No code right now that deals with
anything like that.
Unknown 4:08
Cool. That all sounds fine. And I sort of assumed you guys would just take care of it, I think I was really asking about was, um, was like, I think he’s got some urgency because he’s like, my, my app is being judged right now at my name. And I’m blocked until it’s done. Like, I can’t be I can’t I can’t be judged by anybody can’t be seen by anybody. So. He’s like, doing a lot of urgency. And I think my question is, are we going to follow that urgency, and like, just do a hot fix best possible, or we are every entered slow mode where we’re rigorously testing this before will possibly released anything. And I didn’t know the status of that, with you guys. So that’s why I was asking about,
Unknown 4:47
I’d be curious to hear probably from somebody like Aaron. I think if we were
going to do with hot fix, we would just push it to the web. One tricky fact is
Amy’s, I believe the only person on the team who can build the Mac native app
right now.
Unknown 5:06
So that’s a limitation,
Unknown 5:10
yeah,
Unknown 5:11
though. Yeah. So I would be in support of pushing this to the web app. I think
that like the answer to Jeff’s question of like, whether or not we’re in like,
slow rigorous testing mode versus like urgency need a hot fix mode is kind of a
third option, which is, well, it’s both like, I feel like this PR has been
tested. and I don’t feel like it would be like missing test coverage at this
point, right. Like, it’s been tested by two different people that aren’t Hank. I
think Hank has also tested it. So I think in terms of shipping this to the web
app, we should just kind of do it.
Unknown 6:05
And then with respect to like, the hot fixes for the native apps, I think it’s like, not a problem in this case. Because like, yeah, this is specifically for kind of fixing the web on mobile,
Unknown 6:21
but also as a principal, like, if, if there’s an issue that’s preventing someone from participating in app mining. I
Unknown 6:27
mean, if you like, as a principle, that should definitely be something that should be in fast mode because that relationship if they have to miss out on app mining,
like, I don’t think there should exist a fast mode where we would accept like, a
high possibility of shipping code that like, break everything, right? Yeah, we
should not have a fast mode where it’s like, oh, there’s this urgent thing that
needs to be fixed. So we’re going to, like, ship something that like we know is
going to break, right? Yeah, that’s not a motive that should exist.
Unknown 7:00
Yeah, we just talked videos that are done on and just see accepted to
the App Store.
Unknown 7:12
So the average viewer, so again, update their app. So that’s we’re trying to fix
just less like user problems. It’s more like just to camera stuff on Android
Unknown 7:25
user testing. Yeah, that’s good, I think is fixes just
Unknown 7:28
to get their approval, and maybe the impact is lower than we realized. I think that’s the I don’t know what the impact is.
Unknown 7:33
Exactly. Right. And also the rankings are do today, right?
Unknown 7:37
Yeah.
Unknown 7:38
Yeah. So whatever damage is, like, it’s done, it’s locked in. So maybe, maybe I’m kind of panicking on whether we need to well, so
I just in my mind, I’m like, I’m thinking like, our bug, and then our, our bug, and then our release, like our subsequent release, causes him to have to resubmit. The recent mission was blocked because of another bug. And now like the entire this of him, not getting kind of on us. That’s, that was kind of one of your
[Clarification that this a public engineering meeting]
Yeah, we can we can move on. I think. I think we’re okay. Here. Seems like you guys are on top of it. I was just curious. Like, what happened?
Unknown 8:42
Oh, so Larry, you said you had a topic you wanted to discuss?
Unknown 8:47
Oh, I just had, a meta meta questions. Always trying to like figure out when
this meeting was without access to the block stack.com calendar. And so it was
kind of challenging. I saw the post from last week, like, and so I knew a title
was last week. And I guess it’s probably the same time this week. Um, but there
was a bit of uncertainty. So. So I just like would suggest that maybe like a
places found where the meeting is committed to publicly so that people can
easily find it instead of guessing, because it’s a there’s a period of time
where it would change, you know, depending on what it looks like in New York,
Unknown 9:27
sort of stuff like that. Yeah, yeah. Cool. Yeah, we should probably create that like engineering meeting post on at least Monday before the cheer.
Unknown 9:43
Yeah, yeah, yeah,
Unknown 9:45
yeah.
Unknown 9:46
Yeah. Cuz, like, I think, like, right after the previous there, I guess still exists a chance that we might change what time the meaning of that?
Unknown 9:56
Yeah,
Unknown 9:57
so maybe we start with just like the Monday before, and there would be really great for, which is always the same time irrespective of what was going on in your neck of the woods. Like, so if you can’t make it, you can’t make it.
Unknown 10:09
Yeah, skipping to the next week, just because, like, I’m not thinking of like, like, people want to put it in their calendar, and then know, it’s a set time every week. And so, so it gets me around, then, like, there becomes a synchronization problem. Yeah, like,
Unknown 10:25
yeah, anyway, that’s just my thoughts.
Unknown 10:30
I can’t recall a time when it’s ever not been at this time, and in a while. So just a couple of mistakes this term,
Unknown 10:39
yeah. Okay. So then, I guess we did, what we could do is, we can just create the civil create them the meeting post, just like immediately following
Unknown 10:51
the
Unknown 10:54
leader, it’s gonna be different. next meeting is going to be different. Like, I mean, at least have like, an announcement during Yes, week. And then on time, and, like, make note of it. And then the meeting notes for the previous read it like,
Unknown 11:06
yeah,
Unknown 11:09
pretty opaque to understand what it was. And I was when I was when I was like, in the interview process, and I was checking the forum, but it was always good, always get posted right before I think she brought up and then I was also like, emailing Ryan, or how
Unknown 11:21
I was doing that, which he didn’t respond to, I’m going, I want to attend the meeting. When is it it gets posted, like seconds before it happens. I’m always late to it, you know, like, healthy out. And as far whatever would happen if we just put it like on blog sec.org right there every week time, you know, eastern time we we do this call, like, here’s the here’s like a shortened link for it.
Unknown 11:43
I wouldn’t care if we would just get like
Unknown 11:44
five times a month people
Unknown 11:46
finished. I really like that. Or like that, like, also commitment. And like in sort of an area if you have a page like how do I get involved? Like, yeah, click on this link.
Unknown 11:57
Yeah,
Unknown 11:59
consider the
Unknown 12:03
websites are like a blockchain, right? It’s immutable
Unknown 12:09
might might be out of gate, and then you’re stuck with it for six months, before we actually get more,
Unknown 12:14
it’s like more beautiful than
Unknown 12:21
Yeah, it’s just like it’s more visible. And what has once been seeing the unseen,
Unknown 12:27
it’s like a classic.
Unknown 12:47
So is there any any other topics anyone would like
to discuss,
Unknown 12:57
I would like to, I would like to understand the status of the 19 release.
Because the Android SDK depends on the feature branch. And I would like to move
it to the main release of blockstack.js.
Definitely Ken’s on vacation vacation is kind of status in the dev tools,
meetings,…
and it’s just been pushed back my whole day and then can be out and him being in Hong Kong last week.
Unknown 13:40
I mean, we do have a working on MPM that you could use it’s like an alpha version. I don’t know. I mean, I know that might not help much. Um, I believe it’s, I believe, it’s on Ken’s plate for like next week, I’m not sure that it’ll get emerged next week.
Unknown 13:59
But there is a little bit more work to do in terms of a migration guide, and backwards compatibility work, which is not done. And so I guess that is like a blocker for the release.
Unknown 14:30
I have a, very, like open ended topic. If nobody has anything else, like more of a
or like something I was hoping to share with everybody at some point. But like
this is, this is a good time setting.
Unknown 14:45
So I think we should do an npm beta release of the new protocol detection
stuff. And so today, just reviewing it now, you’ll be able to actually test
how it works out.
Unknown 14:59
But yeah, I think we should do that soon.
Unknown 15:03
We should also emerge and probably actually released the browser because there
should have no effect on anything and tell the block such as the end user. And
that’s kind of a prerequisite which change so the browser has been updated for
users using the native application to have thi have this whole thing worked out.
Unknown 15:37
Yeah, it’s like a prerequisite
Unknown 15:39
for it to work out. But it’s still everything still works just as soon as it
doesn’t have kind of like challenges getting everybody to quickly like, there’s
like a long tail.
Unknown 15:54
Yeah, and this has old designed to be like, backwards compatible with different
versions. So I think that should be okay. Yeah, and talking with an Hank and
Mark and I looked at this a little bit, and Hank you to actually had a chance
to, like, test actually testing results, right?
Unknown 16:15
Yeah, I have. um, I think it’s, I don’t think there’s going to be any changes
required in the browser. The question on the browser is more of we have, like,
returning, returning kind of an epic of of related are very unwieldy bug fixes,
mostly, like quality of life improvements, and improvements and stuff.
And I think a lot of that’s going to be done like this sprint, as in this week,
next week. And so I could see a release, like towards the end of next week type
of thing. And we do include that I’d be more hesitant to do a release earlier
than that, just especially because we’re doing this hot fix.
I’d rather I don’t know, I’d rather just kind of move a bit more slowly and get a whole released together that we can test out.
Unknown 17:10
Yeah, that’s a timeframe is good, like next week, maybe?
Unknown 17:15
Yeah, I mean, it ultimately. So you’ve got a pull request open for adding the echo response to the browser. Right? Yeah. Ultimately, that needs to be reviewed and QA first, right?
Unknown 17:32
Yeah, and those changes are pretty small. So you keep on this picture, it’s an
npm be released that we get out to developers to test before us before it goes
full release.
Unknown 17:49
Yeah, and I think we probably have that we have three or four developers in the community
that really really
want this so
Unknown 18:00
Do we know exactly who they are so we can ta
to talk to them now
Unknown 18:03
just and then people that have been replying to
Unknown 18:07
various cures
Unknown 18:08
so they’re already involved on GitHub,
Unknown 18:11
the other like they’ve
Unknown 18:12
tested it is fantastic
Unknown 18:15
okay with the empty books Yeah,
Unknown 18:16
one One day I was testing on like a combo I forgot but
Unknown 18:21
it’s really happy to see it
Unknown 18:23
actually the question for you about how the work centers currently working through on
Unknown 18:28
I noticed that the way you’re doing this is through an echo reply key set an item in local stores as unique per app
Unknown 18:33
what happens if two different – if one’s habits able to guess another’s echo reply
Unknown 18:37
tab
Unknown 18:38
echo reply reason being is that we do the code reply early detection
Unknown 18:44
code you’re getting an echo reply key from the query string so if tab a is able to guess tab
Unknown 18:51
bees echo request can’t tab a intercept tab be an indication and steal tabs b applciation ke
Unknown 18:56
applications it’s it’s still a scope to cross origin. So all this happens in the context of that web app. So
it’s in graphite I only have access to local storage and then when graphics
Unknown 19:11
web app is open for the attention of responding with echo replay
Unknown 19:15
unlimited has access
Unknown 19:16
to that local storage funny matter of local stores, though it’s a matter of Can I guess your echo reply
Unknown 19:21
like No, I don’t think that the echo reply protocol like has any security implications here
Unknown 19:32
The echo reply is only to decide whether or not you should attempt to open the link with the blocks that protocol handler or just redirect directly to a blockstack.org
Unknown 19:44
So like, if somebody had a tab open that like replied to the echo
Unknown 19:50
in like, guest the landing key that you generated, like, all I would do is cause your browser like, cause the app to redirect browser I to blockstack.org instead of the local app
Unknown 20:05
was actually the opposite I think,
Unknown 20:09
yeah, and actually the opposite. So get handled by whatever the blockstack protocol handler is installed on your computer.
Unknown 20:25
Alright, so it doesn’t need to be backward secure. Or I guess
Unknown 20:30
no, I don’t really need it. It’s for like, really edge
Unknown 20:35
where users and clicking sign on a blockstack on the same browser on the same website, but in like, different tabs
Unknown 20:43
multiple times. And
Unknown 20:45
then so the intention is so that their replies go back to
Unknown 20:48
the tab that started it.
Unknown 20:53
And as long as there’s no way for interception that I guess my main concern there,
Unknown 20:58
just the next week will release the beta of the
Unknown 21:01
blockstack.js change
Unknown 21:05
and the full block into changes, right. The beta Yeah, the browser,
Unknown 21:10
which should that one, I don’t think we should do an update, I don’t have to read you native betas for the
Unknown 21:15
browser. Not yet.
Unknown 21:18
And so I think as long as we get a couple people to review that I think we can actually just merge
Unknown 21:23
merge button
Unknown 21:37
probably at least find Justin and others jump on it
Unknown 21:43
shouldn’t hear from their users
Unknown 21:47
can get the course I guess
Unknown 21:48
it’s kind of feeling
Unknown 21:52
okay, what’s wraps
Unknown 21:55
anybody in the next week
Unknown 21:57
and then the following Friday? Well, we don’t want to release on a Friday
Unknown 22:03
Can we
Unknown 22:05
get a bit of a
Unknown 22:06
spring right? Yeah,
Unknown 22:08
actually for testing this out. Since you want to have the updated native app install I think maybe we’ll try to get like a Mac
Unknown 22:17
build for the native apps that’s what I think most for our testing with right now you can do on Windows but
Unknown 22:24
internally that’s
Unknown 22:26
probably great.
Unknown 22:28
tested.
Unknown 22:49
can see
Unknown 22:49
the other devs that are in here. Who else we have from the community.
Unknown 24:13
I’ve been reviewing like the like surveys, and the last, like the notes from
our past conversations, like all talking to different teams. And I’ve been
talking to, like, we talked to them about collections. And we’ve had a lot of
internal discussions about collections, but also talk to them about like other
rails, which means like, the inbox is I think, and also some, like, easy ways to
push notifications, and maybe even email invitations.
Unknown 24:42
And those are like really clear, I would say, like, validated things that people want and the way to utilize on their apps. It very clear and straightforward and kind of like, not not theoretical. So I was thinking about like, like, one one thing is like, for years, like working on a chat
Unknown 25:01
like an interface , and that’s kind of related to this. But the other thing I was thinking about was
as it’s more of a question, like if you were if you were using
different apps to like, chat inside the apps with other folks in any way, like chatter message could be anything it could be like liking a photo, or it could be like literally a chat back and forth or whatever would that actually be a collection that you’d want to report into other apps essentially like user control data fully which means like you can access communications from what we’re generating one app in any other app that
Unknown 25:38
that you gave permission to and almost like essentially to me like looks like
almost like email right like any email client and open up all your emails
essentially and anybody that’s sending a communication on blockstak like where
it’s essentially putting text in your in various people’s Gaia should that be
sort of like have a schema or any app can can adjust it and use it however they
want, right? It’s kind of a question just kind of to me means like, we don’t
have to work on collections or, or messaging features, we actually like to them
as one like first big collection should be like a messaging collection and
whatever, we need to implement it and then offer that essentially like anybody
can use that in any app.
Unknown 26:20
It’s an idea like something to work on
Unknown 26:25
so what is the actual question?
Unknown 26:28
I think, I think it’s like, as anybody ever thought about it like that, as anybody has already. forum post,
I think Jude gave a great presentation last week at the meetup that we had here
that like that, I think it’s a first I think it was huge presentation. But, but
the idea of reversing, like, like, right now you have apps to talk to servers,
and the data is behind the server. And then here, you switch the location of the
data, right? The the apps talk to the data, because that’s essentially what
you’re saying,
Unknown 27:01
Yeah, like today, you can definitely enter, you know, pull out and read any data from any app right now, I’m just need to know the Gaia hub prefix which you can get from the profile
because you have to know about all the other apps schemas.
Unknown 27:16
Yeah, I’m almost repurposing the most that we like, if we take on a project to
make our messaging really easy. And blocks that apps that you approach it as a
collection, which means like, if you if you do it, if you implemented in our,
you know, kind of like sanctioned way It means other apps can adjust message
history. So, like, I always use use travelsack, it just feels like a very easy
to understand app to me, like if somebody somebody comments on a photo, and then
somebody else comments and somebody else comments, right, like another app could
ingest those those comments and use it in some other way. If you give them
permission,
Unknown 27:58
my thinking about that the right way? Is there any reason why we wouldn’t do it like that? There’s one other concern, and that is
Unknown 28:04
how do you met? Whether the question is really I think, to me is whether or not
you want to manage collections as a separate entity versus just a series of a
well formed data sets across multiple apps. Here’s a good example of this, like
your pictures he did. He wanted to treat pictures as a first class collection,
that would be a separate key that’s independent of all
Unknown 28:25
the apps,
you’d have a separate key life cycle for it,
Unknown 28:28
you only be able to attend to it wouldn’t be able to delete or modify them. Otherwise, any I could be able to do that, for example,
Unknown 28:36
or like, you know, affiliated one athlete to a partial failure collections
Unknown 28:42
comment,
Unknown 28:44
yeah, you’d want to have
Unknown 28:46
the trick, though, is that if you want to go that route, you’re going to need cooperation from the authenticator
Unknown 28:52
how to make sure, for example, that you can’t, you can’t break them
Unknown 28:56
and break the API promise
Unknown 28:57
that it makes
Unknown 28:58
the other route of keeping a separate app based
Unknown 29:02
like that, definitely easy way to do this would be to create just like a specialized like collections.js library, where like, anything that you store by a collection such as can be layered finish with collections. And we have different types schema that’s reach the data, but it looks like with your data is your collections. And we started across all your apps, like there’s a collections folder interface, basically. Yeah, and each of your apps and then that’s it under that prefixes.
Unknown 29:30
I think it’s more based on what we currently have for this provides developers with a better way to basically push and pull from that, right.
Unknown 29:38
Yeah, yeah, just that you wouldn’t have this notion of
Unknown 29:44
you would necessarily have a notion of like, collections that are private to you that you wouldn’t be able to access so. So here’s an example like it was you have a private document in graphite and you’re trying to use another app like Stealthy, we’re not going to say to us, like, no, right? Like that, that document is private and graphite
Unknown 30:02
that you’d be able to get it
Unknown 30:05
within Noteriot
Unknown 30:06
you would need the key programs like to do this, if this is really an authenticator needs to help you out need to pass like key was dangerous, or the needs to be wholly separate collections facility that were like more aware of, for example, the authenticator immediate access your collections and keep the collections key separate.
Unknown 30:24
Yeah. So that’s the approach I’m planning to take like I’m planning to provide API so if you guys come up with collections I’ll use that if not I’ll just like
make up fake app domain like photos dot something rather right and use that as a use that as a janitor private key, and then the like, like, have an API that browser provides like the apps they can rewrite photos or whatever they want to do and then if they want to like Roca, they just click someplace and turn off.
Unknown 30:53
I think ultimately, I think ultimately, like, like the theme of my my
Unknown 30:57
talk last week was a need to have like software in between, like this, your data. And then the apps are trying to use it to like, mediate
Unknown 31:07
pretty it’s really hard. So because I mean, people already have expectations around this, like you have this on their phone, right? Like you get rich access to your photos you don’t want we just had I just devoted to turn off your phone.
Unknown 31:17
So if we don’t, if we don’t put a filter the latter thing that you’ve described you, then we really don’t know
Unknown 31:23
you, when you often you don’t actually know
Unknown 31:26
what the app is trying to access. It could like, we don’t have any sort of, we could say like this app once is going to access your photos, whatever. But we don’t actually even we can’t really tell like what it has access to what it does it is it grab it from all apps are from all the other apps or like a subset of them are like you don’t really have any exposure to what it’s tempting to access. Whereas if we like lock it down, these we would be able to understand that is trying to access
Unknown 31:51
everything in the collection. Right?
Unknown 31:53
Yeah. So. So the way that the way with this would necessarily work is like for each data type, you’d have a collection of photos would be a collection documents be a collection,
Unknown 32:02
there would be separate piece for
Unknown 32:04
reading and writing different collections. It’s just that if you share those keys with your
Unknown 32:07
apps, then
Unknown 32:09
your app that has the ability to
Unknown 32:12
it, the revocation story gets kind of messy, because you have to be key every other app permission from what happened.
Unknown 32:18
Yeah, so I think that the way to think about this is that like, you actually like, have like, two totally separate concepts. So like, one is like sharing encrypted data between applications, which is the story of like, how to do untrusted or less trustworthy key sharing, like group key encryption and stuff like that group key management. And then the other is just like
Unknown 32:47
a story about standards, which is like, you want to have basically file types that are across different applications. And there’s like, no reason to hide the doing these at the exact same time
Unknown 33:03
just like trying to develop a really complex article that might not be used by anybody.
Unknown 33:10
Oh, that sounds like a job for some standards organization. I
Unknown 33:15
won’t mention
Unknown 33:18
I think I was I think my, my bigger plans. I kind of
Unknown 33:22
Yeah, I shouldn’t, we would kind of do more with what you said, like the latter
Unknown 33:26
kind of more rigorous approach.
Unknown 33:28
And I just think the other point I was, I guess, kind of make more question for you guys is like,
Unknown 33:34
if we just if we, if we think about in boxes and making like messaging easy
Unknown 33:37
on blocks that apps and we have ignore these considerations, we just discussed that I’m thinking we’re gonna have,
Unknown 33:46
we’re gonna have, like, we’re going to encourage, like a fragmented message history, all the different data schemas across every single app. And later on, we’re gonna be like, shit, we should have thought about that. More of a collective like, more as a collection itself?
Unknown 33:57
Well, I mean, given inboxes you see inboxes, right?
Unknown 34:00
This case, I think inboxes is one component of it, basically making they basically making it so that like, there’s a really easy to use solution for putting messaging app, which is like, I think something that like, half the apps are like, have done worked on or
Unknown 34:18
Okay, in some way. I’m a little confused with what you mean by
Unknown 34:20
the messaging like comments, or do you mean, like notifications or
Unknown 34:24
all of it? We may see there’s actually a different access patterns.
Unknown 34:27
Yeah, right. Under the hood mechanism,
Unknown 34:31
I think like, what if we like, just what if we were just talking about like email, like what we just said, we want to build like email in blockstack that other apps or apps can share an inbox or you’re eating, you can access your inbox, the same inbox for different users, then I think it’s going to be a lot harder to have a sharded data schema, because you need to do reason and writes on various different, you know, aspects of this. And you also need like a shared inbox
Unknown 34:59
until I get more sharded approach, I think, would make this a lot more tricky versus one collection. And the collection has an inbox and one, you know, storage address path.
Unknown 35:13
Ideally, we want to be like iOS, right?
Unknown 35:14
Like permissions can be granted
Unknown 35:17
a mind using an app for the first time later, you can regularly like, turn off access, the apps that are granted access, have full read and write access. I mean, we could just provide, like, read or
Unknown 35:29
write
Unknown 35:30
or app, I suppose if you don’t trust it out until
Unknown 35:32
like, right.
Unknown 35:34
But like, that’s where we want to go, right? Like, we want to have that level of sort of
Unknown 35:38
cross app permissions and sort of functionality. We don’t want us to say it’s
Unknown 35:44
this. There’s there’s two things here. I agree with the mark mark saying
Unknown 35:48
these are two things like there’s one
Unknown 35:50
one is you this this data structure thing, like what you could use for messages, like Jeff said, and then to you have like, this idea of a product like blockstack messaging, it’s really easy for app developers to like, add into their into their thing
Unknown 36:07
is that are present manner to my account yet?
Unknown 36:09
Yeah, good, good. Yeah. And I get this, there’s different like, under the hood, it’s all it’s all different, right? If you’re doing like to do push notifications, or the inbox is or you want to do an email like thing,
Unknown 36:17
I get that it’s all implemented differently. But I think the
Unknown 36:21
one is, it’s just made more tricky, because the way our picture works, like, if we were doing it just in Firebase and building an app, it would be more straightforward.
Unknown 36:32
I think, like
Unknown 36:34
I might, my goal would be like to achieve to achieve kind of what is pretty easy in decentralized world, which is, it’s like, if you want to have allowed to users to communicate you your app. It’s like,