0:26:03 Well, certainly we touched on already that
bringing together these different people
0:26:06 who came to this, world with different
motivations and different backgrounds do
0:26:12 click and gel and share values together.
0:26:14 So I think that was, a
happy, a happy learning.
0:26:18 Getting a little more
kind of nuts and bolts.
0:26:20 Uh, one of the things that really struck
me was just the element of UI performance.
0:26:25 And obviously we're just talking
about Linear there, but, we
0:26:27 had some demos specifically.
0:26:28 You showed your app, Overtone,
sort of flipping between playlists
0:26:32 and comparing that to Spotify.
0:26:34 then, Aaron showed,
yeah, the demo was Zero.
0:26:37 And we also saw there was a third one.
0:26:39 Maybe it was jazz.
0:26:40 In any case.
0:26:41 Yeah.
0:26:42 The thing that struck me seeing these
different demos, so completely different
0:26:46 people building in many cases, pretty
different products, but all of them
0:26:49 had this feel that was fundamentally
different from most of the software
0:26:54 that we use in our daily lives.
0:26:55 And we've talked about.
0:26:57 UIs should be fast or, you
know, no spinners or whatever.
0:27:01 And I think the way we wrote that in
the original essay, I was thinking
0:27:04 like, okay, I log into Google drive
and it spins for five seconds,
0:27:08 like literally 5, 000 milliseconds
before I get a paint on the screen.
0:27:12 Okay, we can do better than that.
0:27:14 Maybe we could, you know, get things
back in under a thousand milliseconds
0:27:17 or under 500 milliseconds, but all of
these demos show Next frame performance.
0:27:22 That's something where it's, there's
literally just no delay for in
0:27:26 terms of like human perception and
it feels fundamentally different.
0:27:32 And to me, uh, when I think of how
much human kind of energy and just
0:27:37 like soul is lost on waiting for
software all the time, the idea of a
0:27:43 new generation software that is kind of
next frame by default is, Very exciting.
0:27:48 And seeing them side by side, again,
that several other, um, many people
0:27:53 building towards this have ended on
a thing that has this fundamentally
0:27:57 same feel that is the same as each
other, but different from everything
0:28:01 else we know outside of, I don't know,
maybe like video games or something.
0:28:05 That was That would, for
me, was very powerful.
0:28:08 And I think it's like, was not necessarily
a new idea, but just reconfirming
0:28:12 that, seeing that in different
contexts, uh, reestablished for me,
0:28:16 like, Hey, this is worthwhile doing.
0:28:18 and it's just every time I, for
example, do a search in Notion,
0:28:23 particularly, uh, when you're in this
weird middle ground between having
0:28:28 perfect connectivity and offline, this
is where like more traditional, kind
0:28:34 Cache driven, web driven, software is
like trapped in this middle ground.
0:28:39 like I was just riding on a train two
days ago and I was dreading the moment
0:28:44 where I knew I needed to like change my
Notion page and I need to navigate there.
0:28:49 And the, uh, I knew this, I had this
page open yesterday and I wanted to
0:28:54 navigate it and like, it literally took
me 30 seconds until enough packets kind
0:29:00 of flew in and I could navigate there.
0:29:02 And, uh, this can be so different.
0:29:05 And I think it's, uh, the, the different
demos in the conference showed that to us.
0:29:10 So UI performance, and also the, the
different perspectives from, tool builders
0:29:15 and app builders and people outside of
the local-first ecosystem all connecting.
0:29:20 Anything else that, stood out for you
as a, as a theme or a new learning?
0:29:24 Well, obviously sync engines
were, a frequent topic, that
0:29:28 touched on in many ways.
0:29:29 One thing I was quite struck by is how
much similarity in, I guess, architecture,
0:29:36 if that's a word for it, between all
of these different presentations,
0:29:39 which included, you obviously have
the infrastructure creators like
0:29:43 Jazz and DXOS and ElectricSQL and so
forth, where they are very explicitly
0:29:48 and intentionally trying to design
a good general purpose sync engine
0:29:52 infrastructure, architecture, API thing.
0:29:55 For lots of apps to use, but
also we heard a version of that
0:29:59 from many of the app developers.
0:30:00 So for example, GoodNotes, and they're
a really interesting case where a
0:30:03 very successful existing business.
0:30:05 They have like 30 million active users.
0:30:07 They're basically on every
iPad in the world, effectively.
0:30:10 and they, you know, they came to
local-first because they needed a
0:30:13 solution for essentially merging
together rich text changes.
0:30:16 And they're describing how they're,
they're using Automerge to do that, but
0:30:20 their core, Architecture, again, is this
kind of event log model that then is fed
0:30:26 in and, you know, turned in, reactively
rendered, and there's, um, that kind
0:30:32 of event or transaction based system is
something you hear repeated again and
0:30:36 again, and indeed that, uh, there are
many other kind of concepts in the, call
0:30:41 them the architecture diagrams, whether
they actually put a diagram on screen
0:30:44 or not, or just talking about it, you
saw that, again, all these builders,
0:30:47 some coming from the app side, some
coming from the tool side, basically
0:30:51 arrived at kind of the same solution.
0:30:53 And again, that to me is surprising,
but also heartening in the sense that
0:30:57 you give a lot of, different smart and
capable people the same set of starting
0:31:01 conditions and problem statements.
0:31:03 And if they arrive at a similar
solution, that means that solution
0:31:07 is something General purpose of wide
utility, kind of a right solution if
0:31:13 that's, if that's the word for it.
0:31:14 So that was, that was very notable to me.
0:31:17 Indeed, one of the points that
Martin made in his opening talk was,
0:31:20 in a few years, he'd like to see
about going and getting an internet
0:31:25 standard made for a sync protocol.
0:31:28 And, uh, When he gave that, he's
mentioned that to me privately.
0:31:31 And when he mentioned in his talk,
I'm kind of like, yeah, I don't know.
0:31:33 Are we really like three
years away from that?
0:31:35 Like kind of seems like it's
still too early for that.
0:31:38 But then as I saw these architectural
similarities across all these kind of
0:31:42 sync engine solutions, I was left with
the feeling of like, Oh, actually I do
0:31:47 think we're a lot, I think he's right.
0:31:48 I think we are a lot closer
than, than I thought we were.
0:31:50 Yeah, and I, I think this is a, this
is the topic that I can't wait to,
0:31:55 to see materialize more into reality.
0:31:58 And I think there's like
a longer timeframe there.
0:32:01 Maybe in three years from now,
we do the first early drafts
0:32:05 of like a standardization.
0:32:07 Yeah, it's probably start the
process in three years, not finish.
0:32:12 Exactly but until,
until there's like a 1.
0:32:15 0 of something.
0:32:17 There's like a reference
implementation, etc.
0:32:20 That's going to take a longer time and
until maybe there are some pieces that
0:32:25 need to actually trickle into browsers
or operating systems, that's, uh, even
0:32:30 further down the road, but I think
we're certainly reaching a point where
0:32:34 we've explored a bunch of different
approaches in the ecosystem where we can
0:32:39 now try to converge on some of those.
0:32:42 And, what you've mentioned before, the
kind of impromptu working group around
0:32:48 authentication problems, et cetera, that
is a major aspect and there are other
0:32:52 major aspects that need to still be
figured out, but it's really amazing to
0:32:56 see how collaborative the entire ecosystem
is where, yeah, different vendors and
0:33:02 different individual tool builders, app
builders, all come together, share their
0:33:06 experience, and, trying to, to help create
like some sort of, convergent technology
0:33:13 into existence, that's really cool to see.
0:33:16 Another way to frame that same, same
direction you're going is kind of solve
0:33:21 problems versus unsolved problems.
0:33:23 And so increasingly, I think.
0:33:24 A lot of the stuff in the sync engine
side of things, can and should have
0:33:28 many sort of competing solutions out of
the marketplace, um, that fit different
0:33:33 styles and, you know, maybe different
language ecosystems and things like that.
0:33:37 But in some senses, how to do a sync
engine in this way, is mostly figured out.
0:33:44 And actually one of my goals for the,
the conference content was that the
0:33:51 term CRDT should not appear too often.
0:33:55 Um, because typically, again, you
go to, some of the past events, that
0:33:59 have, have existed with this or attend.
0:34:01 You know, a conference or a meetup
or just have a conversation with
0:34:05 someone or anytime the topic comes
up on Hacker News and people tend
0:34:10 to be focused around the, yeah, but
how do you merge changes together?
0:34:13 And there is still plenty of interesting
research being done on the CRDT side
0:34:18 of things, and there will always
be need for new data types as we.
0:34:21 expand the different applications
that people are applying this to,
0:34:23 but ultimately how to build a basic
CRDT and put that into a sync engine
0:34:29 and make that work reliably across
different devices and multi user,
0:34:33 basically have that figured out.
0:34:35 It's just now, it's a small matter
of engineering now, which is still
0:34:38 a huge challenge, but in the sense
of like being a figured out thing.
0:34:44 I think we're, we're basically there.
0:34:46 Whereas there are other things here,
and, uh, this was, uh, you know, a
0:34:49 topic for the day, to some extent,
is what are the unsolved problems?
0:34:52 Um, that includes things like, uh,
schema and, uh, schema migrations, uh,
0:34:57 over time, identity, as I previously
mentioned, kind of authentication,
0:35:02 um, and, and permissions generally.
0:35:05 And there's other stuff as well.
0:35:06 but yeah, I think that as a community,
a way to kind of collaborate loosely,
0:35:10 even though we're all working on our
own projects, is to think in terms of
0:35:14 like, what are the relatively solved
problems that we can codify with, I
0:35:18 don't know, writing or, you know, open
source libraries or things like that.
0:35:21 We say this, this we basically have
settled on the right way to do it.
0:35:26 and there's many implementations of that.
0:35:28 and then other areas where we still need a
wide and diverse set of active experiments
0:35:33 to try to figure out how are we going to,
how are we going to solve this problem
0:35:37 in a local-first, uh, compatible way.
0:35:39 This is also what stood out to me and
talking to speakers, talking to, to
0:35:45 other attendees, is how have they.
0:35:48 who ship products, who shipped apps, how
have they navigated the trade off space?
0:35:54 some have like used off the
shelf, technologies such as
0:35:58 like AutoMerge, Yjs, etc.
0:36:00 But then you're sort of at the mercy of
how far those technologies are along and,
0:36:06 the inherent or current insufficiencies
of those technologies are also, hard
0:36:14 to, advance for, for you yourself.
0:36:17 And, uh, I think there's a notable
other approach for, for app builders,
0:36:23 which is that they don't yet use one
of those off the shelf technologies,
0:36:27 but they've rolled their own.
0:36:29 And, whether that's Good Notes or
whether that's Linear, et cetera,
0:36:32 they've all started so early that They
were convinced this is the right idea,
0:36:37 this is the right approach, but we
don't want to wait five years for the
0:36:41 technologies to be there or to be mature
enough, so they built it themselves.
0:36:44 And I think this is something that
so many of those local-first apps
0:36:50 have that in common, which is very
encouraging for me because, at the
0:36:54 core of it, Those you can make really
drastic trade offs, um, that fit your
0:37:00 app use case and your app requirements
that might not need all the guarantees
0:37:06 something like AutoMerge can provide.
0:37:07 And this can help you going kind
of almost counter intuitively
0:37:12 where, only very few would build
their own Ruby on Rails to ship.
0:37:16 A Rails app, but it, in a way you
can get away with way stricter
0:37:22 trade offs for your specific apps.
0:37:24 So building your own syncing stack
is actually not as much work.
0:37:29 If you, have sort of like a, Like two
months from Linear, if you have that
0:37:34 sort of experience and, if you're
daring enough that you feel like this
0:37:38 is something that you want to do, but
I think that's a, that's a similarity.
0:37:43 And what is most interesting to me about
that as well is that the trade off space
0:37:49 is traversed in a very heterogeneous way.
0:37:55 So, depending on how someone has struck
some trade offs, they might be way
0:38:01 further along to solve certain problems.
0:38:04 So, if you, for example, follow more of
like a event sourced architecture, then
0:38:10 you might have entirely different ways to
deal with the schema migration problem.
0:38:15 Uh, for example, if you, implement your
own CRDT stack or you have other benefits.
0:38:20 So, and I think this now gives us a
pool of experiences where one technology
0:38:26 can learn from the entirely different
architectural approach and, uh,
0:38:31 sort of cross pollinate, the ideas.
0:38:33 And so this was really interesting
to exchange those ideas and that
0:38:38 was kind of my main takeaway.
0:38:40 Absolutely.
0:38:41 I think, you know, maybe the last
takeaway I would probably mention was
0:38:45 just, um, probably some of my favorite
conversations there were talking to the
0:38:50 People I put in the local-first curious
demographic, sometimes they were, you
0:38:53 know, colleagues with someone who was
deeper in that world and this was a chance
0:38:58 for them to better understand this, this
weird thing their colleague was into.
0:39:02 In some cases, they just had
seen the buzz online and wanted
0:39:06 to, to find out about it.
0:39:07 Yeah, for, for example, the, you know,
schema migrations being something that is,
0:39:11 at least the many in the community feel
is, is, is largely an unsolved problem.
0:39:17 And then that caused one person I was
talking to be like, whoa, whoa, whoa, I
0:39:21 don't want to have anything to do with the
technology that, that hasn't solved this.
0:39:25 because you know, this is so, that's
such a fundamental thing to, you
0:39:28 know, building an app in the long term
and with a data stack you can trust.
0:39:32 Which I thought was a, which I thought
was an interesting perspective.
0:39:34 And I was kind of like,
don't worry, we'll solve it.
0:39:36 And that didn't necessarily, you know,
put their, put them at ease, but it is a,
0:39:40 you know, it was a good illustration of
the fact that we are trying to go across
0:39:43 the cusp of the threshold from, you know,
academic, big idea, ivory tower into real
0:39:50 world thing you can use, but you know,
it's, it's, it is still an intermediary,
0:39:55 intermediary state very much.
0:39:57 Very much bleeding edge.
0:39:59 Another person I talked to said basically
that, you know, they were new to it,
0:40:04 but they, the energy that they felt,
was really, um, unique and interesting.
0:40:09 And they, made a comparison I, I
found very positive, which was to
0:40:13 say they basically hadn't felt the
same thing since being part of, or
0:40:16 being around in the React world circa
2013, where kind of, and obviously
0:40:20 there, there was a, a main library
that everything centered around, but I
0:40:23 think in general, the idea of reactive.
0:40:25 UIs and reactive rendering as kind of
the right solution for, for building
0:40:30 applications of all kinds was,
you know, was kind of this fresh,
0:40:35 um, but, but clearly correct idea.
0:40:38 But similarly there, I guess, coming
back to the, you know, still a work
0:40:42 in progress, bleeding edge Stuff to
figure out if you were part of the
0:40:46 React community back then, things
like state management, you would, you
0:40:50 know, you would pick up a library that
was supposed to be the, uh, you know,
0:40:53 this is the way the community does it.
0:40:55 This is the state of
the art and you use it.
0:40:57 And six months later, that
library is deprecated.
0:40:59 And another one is, is now considered
the, and you're like, wait a minute, I'm
0:41:02 trying to build an application here and
I'm not just sort of on shifting sands.
0:41:05 And that is, you know, that of course
is the trade off being, being part of a
0:41:08 community that's still so so young and,
and in the process of figuring it out.
0:41:13 But to me, it's what makes it so exciting.
0:41:14 Cause there are so many problems to
solve and not only engineering and
0:41:19 technology wise, but design wise, we
need whole new UX and UI patterns in
0:41:24 many cases to describe things like.
0:41:26 Sync state, pick a very simple one.
0:41:28 So that being on the frontier in that way
is to me, uh, uh, is quite a lot of fun.
0:41:33 Yeah, it was certainly my happy place.
0:41:35 I consider myself to be like a
technical pioneer and the conference
0:41:41 had an incredible density of other
technical pioneers where it could just
0:41:46 exchange sort of weird battle stories
of how you deal with, taming the
0:41:52 browser to, to do what you want and,
to make things work cross platform or
0:41:58 certain performance tricks, et cetera.
0:42:00 So it was certainly my, my happy place.
0:42:02 I want to slightly shift gears and
talk about another theme that stood
0:42:07 out for me across the different
conversations I had, and also across
0:42:12 the different talks that we heard,
which was more around centered around
0:42:16 the definition of local-first itself.
0:42:19 And Martin kicked off the day
by reiterating, the, the initial
0:42:23 ideals for, for local-first.
0:42:26 And I invite everyone to watch Martin's
amazing, keynote talk there as well
0:42:31 to, to hear those, those words for
yourself, but I think the ideas were.
0:42:36 Kind of reflecting on the initial
essay, how the initial essay laid out,
0:42:41 the, the seven ideals for local-first
software, but that was never really
0:42:46 like a strict definition of what
is local-first software actually.
0:42:50 And also importantly, what
is not local-first software.
0:42:54 So Martin provided, some new ideas about
that, which maybe you want to recap
0:42:59 them here, but this also then led to
an interesting follow up conversation
0:43:05 of like many of the products that were
showed throughout the conference would
0:43:10 not fully qualify as local-first software.
0:43:13 And I think this is, some people
feel more passionate about, like,
0:43:17 very strictly, defining, oh, this
is local-first software, whereas
0:43:21 this is not local-first software.
0:43:23 And I think there's this interesting trade
off and interesting tension for, for us
0:43:28 as a, as a community, as an ecosystem That
I would like to see is that we see, um,
0:43:35 that see like an app sort of like on a
progression, on a spectrum of like growing
0:43:40 up to become local-first and as a powering
technologies such as Automerge, et cetera.
0:43:47 As they mature, it's gonna make
it much easier to build fully
0:43:50 compliant local-first software.
0:43:52 But kinda.
0:43:53 grappling with that definition of
local, pure local-first software, I'd be
0:43:58 curious whether you have some thoughts
on that and want to reflect on it.
0:44:01 Yeah, this is an important question as
the community grows up and especially
0:44:05 again, comparing to a community built
around a particular open source library
0:44:09 or something like that, you don't
have that same definitional thing.
0:44:13 Although even there, you can sometimes
have something where a major new
0:44:15 version, it takes the library in a
different direction and then people
0:44:19 say, this isn't what I was here for.
0:44:21 This isn't the core of
what we're all about.
0:44:24 local-first is unique in that
it is, yeah, philosophy and a
0:44:27 set of ideals, that we think.
0:44:29 imagines a better world or a better
type of software, but not a specific
0:44:33 implementation or single library.
0:44:36 and we always, you know, that initial
definition of the, the goal is data
0:44:40 ownership for people who use computers
for creative and productive purposes.
0:44:45 If I'm writing a book, The book belongs to
me, and the software should reflect that.
0:44:50 and then the seven ideals are sort of
like the, also, in some sense, you could
0:44:53 also describe them as user benefits.
0:44:55 These are things that you get as a
result of kind of building in this
0:45:00 way, and that therefore you can, as we
conceptualize it then, essentially create
0:45:04 a scorecard, and that implies a spectrum.
0:45:06 If you score a zero out of seven,
I think it's fair to say you don't
0:45:10 really count as local-first software.
0:45:12 Uh, you know, try again.
0:45:13 If you score two out of seven,
well, you know, it's a start.
0:45:16 That's, that's pretty good.
0:45:17 If you score five or six out of
seven, then you're doing great.
0:45:21 I mean, I think to some extent it's
almost not even fully achievable in
0:45:26 the real world to, to have truly seven
out of seven and also have a, you
0:45:30 know, a product that's widely used.
0:45:32 I think that will change, I think, as
we continue to, if we push the, push
0:45:35 the boundaries on this, there is a day
when you can imagine that all software,
0:45:39 again, you referenced that earlier, like
things built into the operating system,
0:45:43 fundamentally, I think that the, the
ultimate utopia for local-first or the
0:45:46 ultimate, again, idealized world that
I picture with it is our computers are
0:45:51 fundamentally built in this way and things
are built into the operating system or
0:45:55 into a platform like web technologies
that is specifically designed to support,
0:46:01 um, this way of software existing.
0:46:04 But until then, you know, we'll
take, you know, I think Muse, for
0:46:07 example, we called that local-first
software, but we probably scored a
0:46:10 three or a four out of the seven.
0:46:12 And that was because we identified,
coming back to that trade offs point you
0:46:15 were making earlier, we identified Here
are the things that we think are really
0:46:20 ready for primetime now, where now was
a couple of years ago, and, that we can
0:46:24 implement on our team and that sort of
benefits our business and our users.
0:46:29 Here's some other ones that we're just
going to leave out of scope for now.
0:46:32 That's aspirational for the future, but
right at this moment, it's not pragmatic
0:46:37 for us to, for us to pursue that.
0:46:39 So I think this is sort of the, this
very interesting striking a fine balance
0:46:43 between being pragmatic and being
idealistic, and where being pragmatic
0:46:48 might help you shipping sooner, whereas
being idealistic, might take you longer.
0:46:54 But, uh, enables your users with,
providing more of the benefits and
0:46:58 ultimately full data ownership.
0:47:00 And I think the, the hardest, ideal
to kind of reach right now, which
0:47:04 Martin spelled out, uh, very explicitly
is like, if the, the app builders
0:47:10 go out of business, the app still.
0:47:12 can work and, so that the app is
not, degraded in functionality.
0:47:17 And I think that takes a lot from
a company like Linear, et cetera.
0:47:22 That's probably takes most of the
backseat and accomplishing the ideals,
0:47:27 very understandably so, because
you building an app, et cetera.
0:47:31 got to, for most people got to pay
the bills and this is the hardest
0:47:35 to achieve and, probably also helps
the least in the short term in terms
0:47:40 of getting new users, et cetera.
0:47:42 So I hope that we'll reach at some point,
from a technological advancement that
0:47:47 this is just so easy, that self hosting
becomes so easy, that data ownership,
0:47:52 the operating system all supports that,
that we have a generic sync server.
0:47:57 that we get this ideal almost for free
by using the right technologies, but
0:48:02 I think right now you need to fight
the hardest to achieve that ideal.
0:48:07 Yes, that's right.
0:48:07 And again, that comes into built into
the platforms and the operating systems
0:48:11 and the foundational layer, right?
0:48:13 Like you can try to talk users into
using, I don't know, end to end
0:48:18 encryption in their email by like
generating PGP keys or whatever, but
0:48:24 ultimately, things like the mobile.
0:48:27 Operating system platforms with their
secure enclaves and key management
0:48:30 built in and biometrics and secure
messaging apps that kind of make all
0:48:36 that easy and make it just, again,
part of the foundations where a
0:48:41 regular person can, an app developer
can build this reasonably and a
0:48:44 regular person using it can access it.
0:48:47 It requires more than what any individual.
0:48:50 builder or any individual
app creator can, can do.
0:48:53 So, so you do your best,
uh, with what you have.
0:48:55 Yeah.
0:48:56 So to, yeah, exactly.
0:48:57 So Martin's description, which you
should definitely watch the video of
0:49:00 his talk, but is the thing that makes
something local-first is that no one can
0:49:06 kind of take your data away from you.
0:49:09 And I think in these, it's hard to
separate the data and the app to some
0:49:14 extent, because While there are standard
file formats and things like that, the
0:49:17 reality is just that, like, if Notion
stops working, but I have an export of a
0:49:22 zip file of a bunch of HTML or however it
exports, it's like, well, I kind of have
0:49:28 my data, but not really, I don't, without
the functionality of the application and
0:49:32 the way to navigate links and search and
add new things, whatever, I kind of have,
0:49:37 I really have lost something, like My
corpus of whatever I had in Notion to,
0:49:41 in this example, would be lost to me.
0:49:44 and his description is basically,
yeah, the company going out of
0:49:47 business and being acquired and the
owner deciding to, you know, do a
0:49:51 hard pivot in some direction that, you
know, you know, kicks out a bunch of
0:49:55 the former users and customers, uh,
or just simply, yeah, servers going
0:49:59 offline, right, is the short, is the,
is the near term version of that.
0:50:03 And that, you know, the classic thing
of like, oh, Slack's down, GitHub's
0:50:06 down, or whatever means now I can't
work, that, that would not be the case.
0:50:12 So, I really like that as like a much,
A really boiled down litmus test that
0:50:17 if you have that, all the other stuff is
probably going to tend to come with it.
0:50:22 so I like it as a, again,
an aspirational thing.
0:50:25 I think it's a longer term thing.
0:50:26 I think it's a thing where we're
all trying to move towards.
0:50:29 You can build in that way today,
but again, there are, there are
0:50:31 trade offs to make, especially
if you're a commercial business.
0:50:34 Depending on what exact domain you're in
and what platform you're on and so forth.
0:50:37 For example, it's probably a lot easier
to do that if you're in a, uh, kind
0:50:40 of like a building a native app and
then if you're building a web app.
0:50:43 , but I, I think that is a
really nice, definition.
0:50:46 Now he also said in his talk, you know,
while he is a, a cornerstone person in
0:50:51 this, community, it is a community, right?
0:50:53 No one has, you know, there, there's no,
uh, there's no benevolent dictators here.
0:50:57 Or dictators of any kind, I guess,
and he, he has a lot of moral
0:51:01 authority, but he can't just
say this is, this is what it is.
0:51:04 We all have to decide that for ourselves.
0:51:07 And so, to some extent, I think also this
could kick off a discussion about that for
0:51:12 the community have sort of with itself.
0:51:14 And again, I have my opinions.
0:51:16 You have yours.
0:51:16 Martin has his, um, but I think Again,
we, we may play key roles in the
0:51:21 community and helping get things started.
0:51:23 But what makes it as a community
is we're all defining it together.
0:51:26 So I think to me, it's very healthy to
have those discussions and hopefully it
0:51:30 doesn't turn into a purity or a holier
than thou discussion, but it does turn
0:51:34 into a practically speaking, what unites
us, what are we doing here and how do we