►
From YouTube: Dynamic Data and Capabilities WG — January 08, 2019
A
A
A
A
A
A
Please
focus
on
that
and
please
keep
it's
limited
to
the
three
minutes
so
with
that
we
don't
over
run
into
the
second
half
of
the
of
the
meeting
nice.
So,
let's
start
in
the
order
of
the
attendee
list.
I
haven't
put
my
name
here
yet
I'm
the
worst
attendee
all
right,
so
starting
with
Jim.
You
want
to
give
your
update.
C
At
this
time
it
only
takes
a
minute-
it's
very
nice
and
very
small
can
take
in
self-contained,
which
is
what
I
was
going
for,
so
I'm
pretty
happy
with
being
able
to
simulate
small
scenarios
in
very,
very
few
lines
of
code,
so
so
that
was
the
main
thing,
I
I
coated
or
the
over
the
break,
and
then
I
also
said.
Last
week,
I
sat
in
on
a
few
other
working
groups,
so
I
sat
in
on
the
browser's
working
group.
They
talked
a
bit
about
what
I
did
in
Tokyo
went
met
with
Google.
C
There
I
was
doing
some
stuff
with
the
web
packaged
thing
that
Google's
been
working
on
for
Google
Chrome,
so
that
was
sort
of
neat
and
then
I
sat
in
on
the
community
working
group,
meeting,
meeting,
yeah
and
just
sort
of
expiring
on
what
they're
doing
so
this
week,
I
there's
there's
some
peer
pad
maintenance
I
need
to
do,
and
we
also
we
should
also
talk
about
like.
Are
we
going
to
rename
pure
base?
There
was
an
issue
where
the
other
guy,
who
has
the
project
pure
base,
he
doesn't
want
to
give
up
the
name.
C
B
Sorry
I
was
muted
so
anyway,
going
on
to
my
concluded,
step
tasks,
so
I've
finished
helping
business
centers
with
the
changes
required
to
the
build
process
of
this
gasified
so
that
we
could
publish
the
accession
on
both
Chrome
and
Firefox.
That
was
finished,
infinitely
publish
on
Firefox.
We
can't
really
do
it
right
now,
because
we
need
a
privacy
policy,
so
we
reached
out
the
legal
team,
but
because
they
are
sort
of
overwhelms
they
they
haven't
respond
to
us
yet
so
we
kind
of
box
on
on
Firefox.
B
We
all
try
to
ping
them
so
soon,
so
that
perhaps
we
can,
we
can
get
a
privacy
policy
earlier
also
I've
started
contributing
to
a
professor
Clark.
So
we
had
the
meeting
with
a
professor
of
developers
and
also
better
Teixeira
was
was
with
me.
So
the
the
conversation
is
about
versamark
and
a
professor
and
a
single
similarities
of
the
projects,
projects
and
half
code.
We
converge
to
a
solution
and
we
decided
to
use
ipfs
law,
but
that
requires
some
changes
improvements.
B
So
we
listed
those
improvements
and
created
issues
there
and
started
tackle
tackle
those
issues.
Some
of
them
were
made
by
the
developers
of
Professor
Park,
the
main
developers,
and
some
others
were
made
by
me
at
the
moment.
I've
as
I
have
a
full
request
that
is
in
review,
which
brings
on
IPL
this
IPL.
B
So
so
yeah
I've
been
consuming
the
path
to
ipfs,
vlog
and
also
I've
created
the
initial
draft
of
that
into
the
background.
I
agree
Martin,
so
I've
put
the
content
itself
on
a
gist,
but
if
you,
if
you,
if
you
guys
want
me
to
put
on
a
Google
document,
so
that
it's
easier
for
us
to
collaborate,
I
can
do
so.
It's
very
easy
to
actually
transform
it.
So
yeah
I'm
waiting
for
feedback
on
on
that
I.
B
So
if
anyone
is
interested
in
contributing
to
the
projects,
please
let
me
know
either
in
the
in
the
issue
or
even
you
can
manifest
your
interest
in
the
gist
or
even
the
Google
Documents
will
document.
If,
if
I,
you
know,
if
I
will
put
you
okay,
just
you
know
but
put
a
comment
there
saying
I
want
to
do
that
and
I
will
assign
that
to
you
and
I
think
that's
it.
D
Hey
everyone
happy
new
year,
so
basically
I've
been
working
in
general
on
trying
to
make
discovery
faster
and,
as
I've
been
working
on,
that
I
found
a
lot
of
stuff
in
underlying
p2p
libraries
and
floods.
I've
been
in
switch
and
WebSockets
are
where
I
found
that
we
often
use
Pauline
instead
of
responding
to
events
and
at
each
level
of
the
stack
as
we
go
up
that
polling
kind
of
builds
on
itself,
so
it
ends
up
making
things
very
slow.
E
So
I
did
a
few
like
a
multi
writer.
I
can
ask
related
stuff
trying
to
get
I
switched
over
from
using
Carter
buffs
to
go
IPL
DC
board
so
that
we're
sort
of
it's
a
little
easier
to
work
with
when
we
start
bringing
the
rest
of
the
graph
structures,
so
I'm
not
replicating
work
and
put
together
some
like
content
resolvers
like
things
that
you
can
use
on
top
of
the
graph
I
left,
the
graph
layer
set
set.
Cr
DT
is
network
and
sort
of
emulating
single
writer,
IP
NS,
but
with
conflicts
all
right.
E
So
it's
over
right,
but
if
you
have
two
things
that
overwrite
at
the
same
time,
then
you
get
a
conflict
I'm
starting
to
list
up
the
peer
based
concepts
and
putting
together
a
little
bit
about
Message
Queuing.
Just
so
I
can
get
thoughts
out
to
people
and
get
feedback
from
them
and
then
I
can
get
to
that
later.
E
Organization
over
public
channels
like
what
you
guys
are
doing
with
the
rest
of
the
peer
based
stuff
and
I
guess
at
least
having
some
basic
implementation
of
that
ego
is
nice,
because
then
we
can,
when
we
start
building
this
stuff
back,
taking
some
of
the
peer
base
stuff
and
living
in
it
to
go.
Also
I'll,
be
there.
So
I'll
probably
start
pumping
yet
in
a
little
and
run
stuff
by
at
direct
to
make
sure
I'm
doing
it.
E
The
better
way
you
haven't
he's
seen
it
bingum
the
wrong
way
and
I'm
gonna
be
out
for
I'm
gonna,
be
out
between
part
of
next
week
in
the
following
week.
So
just
like
a
heads
up
about
that
and
there's
gonna
be
Justin
Carmack
from
dr.
who
I
met
with
last
month
and
his
works
with
docker,
and
you
know,
the
noise
framework
will
probably
be
crashing
next.
Our
next
meeting
I
won't
be
there.
So
just
let
need
it
letting
you
know.
A
A
So
I
did
a
dependency
a
bit
storm
on
pubis
and
also
did
something
that
was
approached
last
on
last
night's
meeting
by
Jim,
which
is
Delta
batch
batching.
The
deltas
for
quicker
updates
and
I
managed
to
do
that
in
a
way
that
doesn't
break
that
doesn't
break
the
our
GAC
rdt
and
because
Delta
batches,
our
deltas,
are
sometimes
dependent
on
previous
history
and
and
so
I.
A
With
that
in
place,
I
created
some
more
tests
and
I
had
managed
to
bring
the
concurrency
level
of
the
n2
and
load
tests
to
eight
peers,
which
I
wasn't
able
to
do
before
so
I'm.
Very
curious
of
trying
out
pure
pod
again,
the
dev
branch
of
pure
pod.
Again
against
is
this
current
state
of
master
of
pure
base.
Next
is
again
out
speed.
Pi,
try
to
speed
up
the
tests
for
for
peer
base
would
protect
pure
IDs,
because
I
guess
we
spend
like
80%
of
the
time
creating
pure
IDs
on
the
tail.
A
That's
something
I
forgot
here,
which
is
pure
base
renaming,
will
be
like
a
poll
of
name.
Alternatives
for
peer
bags
already
have
a
few
and
then
I'm
also
going
to
dive
a
bit
into.
Hopefully,
a
bit
into
gear
base
connection
management
so
trying
to
in
tandem
with,
with
with
dirt
working
on
connection
management.
That's
been
I,
think
they're
there.
There
could
be
some
improvements
there
that
already
been
a
lot
of
improvements
there
on
connection
management,
and
we
have.
A
We
have
to
have
better
insights
on
which
connections
we're
holding,
because
we
have
like
stats
by
ipfs
or
levy
to
piece
stats,
and
we
have
States
stats
on
on
peer
base.
We
have
to
make
sure
the
stats
on
pure
base
are
accurate
and
that
the
connection
count
is
actually
accurate
and-
and
that's
that's,
where
I'm
going
to
start
with
and
so
that
we
can
speed
up
collaborations
where
for
a
large
number
of
peers,
and
that's
for
me
under.
F
Sosa,
okay,
guys
so
I've
concluded
the
proposal
for
the
draft
regarding
sitemap
for
IBM.
We
try
to
define
the
priorities
regarding
the
user
journeys
and
the
multiple
pages
today
I
was
helping
Sara
Zarr
Widow
chased
for
the
idea,
breakdown
and
currently
in
progress.
There
are
the
regarding
airbase,
the
collaboration
lifecycle,
UI
and
UX
guidelines,
which
were
was
prepared
with
Marco
and
Azure.
F
Now
I'm,
following
federal
federal
sentence
with
the
animations
and
an
implementation
regarding
discussing
file,
I,
don't
have
anything
but
for
now
I
was
on
vacations
with
no
leaders
in
this
week
so
and
the
next
steps
will
be
continuing
with
the
approaches
and
the
concepts
for
for
that
IDM.
Regarding
the.
G
G
Some
of
the
days
during
the
holidays
so
concluded
the
breakdown
of
the
peer
based
plan,
mainly
strategic
product
management
activities
and
outbound
activities,
and
which,
which
translated
into
2019
OPRS
now
in
progress
while
we're
starting
the
the
poro
protocol
chapter-
and
that's
that's
some
discussion-
that's
that's
starting,
which
might
be
handy
for
for
the
DDC,
where
I'm
currently
working
on
the
collaboration
lifecycle
drafts,
that's
proving
to
be
well
a
lot
more
work
than
then
then
we
probably
expected.
Initially,
the
current
status
is
on
that
to
link
there
on
the
quick
pad.
G
You
can
have
a
look.
There
are
the
more
we
think
about
it.
More
questions
come
up
and,
of
course,
the
the
the
big
win
here
will
be
simplifying
it
because
it's
always
easy
to
just
add
more
stuff,
but
the
more
detail
we
put
into
it
the
more
complicated
it
becomes
for
both
for
the
user,
for
the
developer
and
for
the
designer.
So
the
devil
is
really
in
the
details
here.
G
This
is
important
for,
for
the
whole
group,
some
of
the
things
that
we
are
right
now
considering
have
implications
on
on
both
on
the
developer
experience,
so
we're
talking,
potentially
changing
ap
ice.
We're
change
potentially
talking
about
how
we
approach
the
community-
and
this
is
following
on
the
on
the
meeting
that
we
had
with
Michael,
Ezreal
and
and
and
Jim
was
there
as
well.
My
personal
view
is
that
if
we
want
to
stick,
we
want
we
need
to
be
designing
these
for,
for
a
more
average
developer
or
even
a
more
inish
a
new
developer.
G
So
we
need
to
have
that
discussion
because
I
mean
to
see
if
there's
buying
in
changing
all
these
things,
because
some
of
these
are
not
compatible
with
what
we
have
currently
then
I'm
starting
the
discussing
the
new
iteration
on
IBM,
UX
and
UI.
So
have
had
a
couple
discussions
with
with
both
Andres
yesterday
and
today.
Right
now,
I
don't
have
anything
anything
blocks.
I
moved
my
my
task
of
putting
discusses
fire
on
Firefox
to
to
Pedro,
so
he's
taking
care
of
that
now.
G
Next
I
need
to
to
finally
do
the
events
that
peach
I
didn't
have
enough
time
so
far,
I'm
hoping
that
today,
I
can
get
a
good
advanced
and
and
send
that
then
I
need
to
define
a
more
specific
plan
for
peer
base,
specifically
resources
and
milestones.
This
is
something
that
I
will
be
sharing
with
you
Pedro
first
to
make
sure
we're
on
the
same
page
and
finally,
hopefully
I'm.
A
That's
it.
Thank
you,
alright,
just
on
a
quick
note
next
week,
I'll
be
in
Porto
on
Liberty
week
and
also
in
this
gist
for
the
for
the
collaboration,
lifecycle,
I.
Think
then,
at
least
at
the
Institute
should
take
a
look
at
that,
because
there's
the
there
are
some
proposals
for
changing
the
names
of
things
or
what
is
so
starting
with
something
a
collaboration
or
joining
or
at
all
those
verbs
that
we
we
should
get
a
consensus
on
I
believe.
H
H
C
H
D
A
Cool.
Thank
you
thank
for
that.
So
we,
we
kind
of
I
think
if
there
was
no
one
else
that
wants
to
give
their
update
I
think
we
finished
right
before
the
scheduled
time,
which
is
awesome.
Thank
you
for
the
summarizing
of
all
your
efforts
in
these
last
three
weeks.
So
next
in
in
the
agenda
is
something
very
quick.
I
would
like
to
point
out
I've
seen
that
you
have
made
a
custom.
A
Some
of
you
have
made
a
custom
of
joining
other
working
group
meetings,
namely
Yui
and
browsers,
and
I
know
that
that
I
didn't
as
also
joins
some
girl,
related
working
groups
and
I
would
like
to
encourage
that.
There's
also
some
dependency
on
infrastructure,
for
instance
on
my
parts
and
there
also
some
Co,
some
Co
work
that
we're
going
to
start
to
do
with
the
GUI
and
and
web
browsers
working
groups,
so
I
would
encourage
everyone
to
participate
in
these
meetings.
A
If
you
have
something
that
we
would
like
to
ask
from
them,
or
just
just
lurking
and
seeing
what
what
they're
they're
up
to
and
and
that's
that's-
that's
not
a
job
of
only
the
captain
of
the
working
group
to
transmit
the
dependencies.
I
think
we
should
this
cross-pollination
since
the
2019
milestones.
Are
there
there's
a
big
milestone
for
a
DFS
whole
ipfs
group
that
relates
to
dynamic
pattern.
Working
group
I
think
we
there
is,
there
is
the
need
for
for
this
cross
and
cross
work,
cross-pollination,
just
just
and
yeah
I
think
we
have
demo
scheduled.
C
Here's
my
code,
so
I've
created
a
project
called
his
pure
basic
state
playground.
So
there's
only
two
files
in
it,
and
so
my
idea
is
to
instead
of
doing
a
web
view,
I
just
do
a
terminal
based
UI
and
see
if
I
can
get
the
amount
of
code
really
reduced.
So
so
there's
a
there's,
a
master
controlling
process
in
a
child
process
and
what
the
master
controlling
process
does
is.
It
starts
at
two
separate
child
processes
and
they
talk
to
each
other.
It
also
starts
a
rendez-vous
process,
so
I'll
give
you
the
demo.
C
So
this
is
it's,
it's
a
keyboard
driven
and
the
keyboard
is
just
a
spacebar
and
it
drives
it
to
the
different
states.
So
I'm,
starting
in
the
initial
state
here,
I
hit
space.
You
can
see,
it
says,
move
to
the
rendezvous
started
state
and
you
can
see
there's
some
logging
and
capturing.
So
what
it
did
here
was
a
hit
spacebar.
They
used
ojs
to
start
a
sub
process
which
just
starts
a
rendezvous
service
in
there.
If
I
move
to
the
next
state
here.
C
C
C
C
Yeah
they
have
a
I
was
attracted
text.
They
have
a
nice
bunch
of
documentation
and
the
author
has
been
quite
active,
going
to
conferences
and
promoting
it,
and
it's
all
written
in
typescript
so
seems
pretty
solid
in
terms
of
the
the
technology
behind
it.
So
it
was
good
I've.
My
initial
impression
of
it
was
it
works
really
well
for
it
too,
simple,
state
machines.
C
It's
the
reason
to
use
this
one
instead
of
just
writing
up
your
own
state
machine,
which
would
just
be
a
few
lines
of
JavaScript.
Is
it
has
all
this
support
for
doing
sort
of
hierarchical
state
machines
and
but
at
this
there's
sort
of
like
different
ways
to
do
it?
So
I
was
playing
around
with
this
ability
to
have
like
parallel
States
state
machines.
C
They
have
like
a
master
state
machine,
then
you
can
embed
for
each
worker
or
each
yeah,
sure
I
guess
a
child
I
could
do
the
separate
state
machine
for
each
of
them
and
then
I
should
have
embedded
them,
but
there's
they
also
support
other
ways
of
doing
it,
where
you
can
sort
of
compose
state
machines
together
using
two
actor
model
and
you're.
Sending
events
between
things
so
because
things
in
a
subprocess
I
sort
of
had
to
do
a
little
bit
of
that
anyway.
C
C
So
that's
my
that's
my
main
learning
from
it,
but
III
like
I,
like
it
I
like
it's,
not
a
lot
of
code
like
it
see
it's
easy
to
go
in
here
and
you
can
see
states
in
like
there's
a
new
state
I
create
pure
base
into
the
starting
state.
I
call
app
start
here,
then
mister
started
state
and
then
I
create
the
collaboration.
So
there's
a
lot
of
boilerplate,
but
the
actual
code
is
really
really
simple
and
then
here's
the
part
where
I
like
where
it
types
so
there's
not
a
you
know.
D
C
C
C
So
this
is
sort
of
nice,
so
you
could
do
sort
of
I
think
you
want
to
keep
your
like
individual
state
machines
quite
simple,
but
then
you
could
sort
of
view.
The
hierarchy.
I,
don't
know
how
the
visualizer
would
work
with
the
sort
of
actor
model,
where
there's
different
events
coming
back
for
it,
but
potentially
I
could
create
like,
in
my
little
example,
app
cradle
a
web
server
and
then
load
this
thing
into
it.
And
then
you
can
sort
of
visually
see
the
states,
so
that
might
be
really
interesting
for
some
things.
C
What
I'm
sort
of
really
interested
in
the
state
machines,
because
we
could
use
it
to
sort
of
hook
into
the
plumbing
and
especially
for
things
like
connection
management
like
set
up
very
specific
simulations
and
not
a
lot
of
code
like
two
files
and
like
make
sort
of
examples
of
you
know
this.
This
is
how
the
state
the
connection
management
worked
before
this
changed,
and
then
this
is
how
it
works.
After
this
change,
we
could
even
just
you
could
make
two
separate
workers.
C
A
C
A
D
A
C
D
C
There's
a
I
believe
there's
some
books
and
things
that
I
didn't
read
the
book,
obviously,
but
that
this
is
based
on
so
there's
a
bit
of
a
background
on
a
bit
of
a
community
built
around
so
there's
out,
there's
an
XML
implementation,
I
think
that
goes
along
with
this
book.
So
this
is
sort
of
like
a
follow-on
implementation
done
in
JavaScript.
C
So
the
author
here
is
and
isn't
inventing
this
from
scratch.
So
there's
already
a
bit
of
a
community
around
this
he's
trying
to
make
this
compatible
with
this
XML
based
one.
Well.
That
said
that
that
meat
tells
me
that
this
particular
state
machine
implementation
is
a
little
bit
on
the
heavy
side.
So
it's
not
that
much
javis!
C
It's
not
that
much
typescript,
but
you
know,
in
terms
of
like
a
state
machine,
can
just
be
a
few
lines
of
JavaScript,
so
mm-hmm
so
I
think
it's
it's
good
for
these
types
of
little
experiments,
I'm
doing
where
I'm,
not
we
don't
care
about
bundle
size
for
very
anything
like
that.
I'd
be
hesitant
to
build
this
into
our
core
libraries
unless
he
gave
us
like
some
real
benefits.
C
C
It's
basically
react
for
the
console,
except
I,
can't
even
find
where
the
you
guys-
oh
yeah,
here
this
so
so
this
is
my.
This
is
my
whole
UI
here.
You
know
it's
basically
just
rendering
that
in
a
sort
of
declaratively-
and
it's
just
like
react,
it
will
only
update
the
characters.
It's
like
a
virtual
Dom
for
your
terminal.
C
A
B
A
B
D
A
A
I
see
right,
let's
go
yeah
cool,
so
there's
a
5/1
map
has
the
pull
requests
for
the
working
groups?
Okay,
so
this
is
like
long-term
whole
year
holy
year.
Road
map
and
you
can
click
the
preview
and-
and
there
are
this-
is
the
proposal.
So
this
is
a
pull
request
with
the
the
markdown
document
for
all
the
milestones
for
the
for
this
year
and
drilling
down
for
this
quarter,
which
was
which
what
you
were
asking.
A
A
A
It
has
to
do
with
developer
adoption
of
of
pupils
and
be
able
to
create
dynamic,
apps
web
apps
on
on
top
of
on
top
of
it.
So
it
entails
having
your
website
have
a
good
documentation,
starting
to
build
the
specification
and
all
the
things
around
the
communication
strategy
also
about
education.
So
Jim
is
going
to
delete
that
part
integrating
that
into
the
community
working
group
or
what
ifs,
which
is
was
responsible
for
just
launching
proto
school
website,
which
now
has
a
portal
by
his
chapter
and
other
chapters
around
around
the
world.
A
So
I
encourage
you
to
check
that
and
also
have
so
user
experience
guidelines.
There's
a
an
effort
going
on
on
on
that.
We've
already
started
on
the
collaboration
lifecycle,
think
identity
solution,
so
the
IDM
is
going
to
be
a
big
big
thing.
A
big
drive
on
this
first
quarter,
led
by
Andre,
crush
and
and
some
people
on
the
Moxie
team
also
also.
A
Reference
reference
implementation,
where,
for
for
the
specify
and
specify
I
want,
is
going
to
be
further
improved
and
and
developed
throughout
this
this
quarter
and
also
to
work
with
a
partner,
we're
already
started
working
with
with
some
companies
that
that's
or
some
projects,
and
that
will
require
that
have
some
objects
share,
some
of
the
common
goals
and
so
to
work
with
them
and
support
each
other
is
a
goal
for
this
quarter.
Also,
that's
mostly
and
like
in
a
quick
gist.
The
things
that
we
have
planned
for
for
this
quarter.
D
A
Work
also
trying
to
know
where
we
can
help
in
this
particular
case
textile,
where
we
can
help
with
their
biggest
pain
points,
but
right
now
to
be
frank,
we're
just
on
the
face
of
understanding
their
their
current
state,
how
well
their
their
work
and
how
they,
how
they
do
things.
So,
basically,
there's
there's
some
parallels
to
what
we've
been
doing
so
far,
but
they're
further
down
the
road
on
some
other
aspects
like
identity,
for
instance,
or
state
replication
or
persistence,
for
instance,
is
one
of
them
work.
A
You
recover
recovery
data
recovery
and,
and
it's
it's
mostly
gathering
knowledge
right
now
and
it's
there
is
there's
it's
totally
public
and
there
is,
and
we
plan
to
make
the
work
more
more
public
on
the
near
future
and
increasingly
start
cooperating
with
with
them.
Furthermore,
there's
in
terms
of
the
textile,
what
they're
doing
the
textile
project
and
what
they're
doing
they're
more
on
the
mobile
side
and
the
user
go-go
and
implementation.
D
A
E
So
what
are
the
things
where
you
guys
already
have
some
of
this,
and
you
have
other
things
that
you
know
you
think
worked
the
way
you
did
it
or
didn't
work,
the
way
you
did
it
or
would
be
willing
to
replace
with
something
we
built
if
we
did
build
it
so
I
think
just
first
is
taking
an
internal
accounting
and
then
and
then
going
out
and
figuring
out.
What's
out
there,
there's
a
bunch
of
people
to
talk
to
and
just
sort
of
looking
for
more
the
whole
process
is
this
point
is
just
exploration
so
yeah.
E
Anybody
knows
anybody,
just
you
know,
send
them
our
way.
Our
Cody
ethic
is
also
looking
into
the
stuff
as
part
of
the
collaborations
working
group.
So
at
this
point
just
trying
to
learn
more
because
you
know
like
textile
has
their
cafes
and
stuff
and
they
do
sort
of
their
own.
Take
on
how
persistence,
works
or
messaging
works
when
you're
offline
and
that's
partially
just
because
they
needed
to
get
something
off
the
ground
and
figuring
out
what
part
of
that
is
optimal
versus
what
part
of
that
is
necessary
is
is
the
other?
A
I
I
It
seems
to
not
be
like
even
loading
the
page
itself
for
me,
mm-hmm,
okay
anyway,
so
I
guess
the
the
most
immediately
relevant
updates
is
that,
right
before
the
holiday
break,
we
ended
up
having
I
call
people
or,
whereas
with
answers
from
and
Peter
it
was
on
there
and
I.
Think
that's
the
only
person
or
I
and.
I
Unfortunately,
the
outcome
of
that
was
not
super
promising.
Basically,
there's
still
a
lot
of
skepticism
from
their
side
that
our
tech
is
one
way
to
be
used
into
will
be
a
net
advantage
for
them
I'm
trying
to
recover
a
pure
pad.
That
has
all
the
notes
from
that.
So
I'll
send
that
to
the
group,
so
I
think
that
and
the
shirt
takeaway
is
that
one.
We
definitely
need
to
improve
performance
instability
significantly
before
that
conversation
can
really
happen.
Internist
and
two
is
that
there's
probably
is
conversation
we
had
about
like
features,
and
things
like
that.
I
So
I
think
we
basically
need
to
cool
that
initiative
slightly,
but
still
it's
not
off
the
table.
It's
just
kind
of
a
little
bit
a
little
bit
tempered,
but
probably
more
like
a
key
to
kind
of
thing
in
terms
of
other
collaborations.
Textile,
of
course,
is
a
big
one.
I
don't
know
if
any
of
you
were
on
the
the
idea
vest
calls
yesterday,
but
acted
X
showed
their
industrial
motivation
stuff,
which
is
super
cool
and
I.
A
E
B
So
I
think,
first
of
all,
as
far
as
I
know
and
and
by
looking
at
echoes
and
it
uses
a
deck
underneath.
So
especially
if
you
look
at
the
entries,
GS
file
and
take
entry
into
is
IO
file.
That's
where
the
dog
layer
is
on.
So
officially
it's
not
using
it's
not
using
a
TLD,
but
it
is
a
data
since
that
in
store
objects.
And
then
you
have
like
heads
not
head,
sorry
next
pointer,
which
is
a
CID
or
a
multi
hash,
because
they
have
to
multi
hashes
because
they
are
older
projects.
B
So
they
are
not
using
IP
OD.
But
the
pull
request
that
I've
made
will
be
using
IP
LD
and
also
will
transform
all
the
multi
ashes
within
the
code
to
see
IDs.
Because
the
series
is
the
new
spec
of
you
know:
content-addressable
IDs,
so
yeah,
it's
currently
using
tags,
and
then
you
have
like
a
tie
breaker
that
I
think
it's
currently
in
a
pull
request
as
well.
So
essentially
they
were
simply
less
write
means
a
scenario.
B
B
But
they
also
have
a
replication
strategy,
not
not
built
in,
but
at
least
the
strategy
is
there,
and
we
don't
need
that
in
terms
of
the
that
discussed
if
I
use
case
that
that
we
we
know
about
so
I
have
mixed
feelings
about
all
of
this.
After
knowing
more
about
the
code,
perhaps
we
could.
We
could
discuss
that
offline
and
then
think
about
that
later.
A
Yeah
I'm
not
sure
what
I
understood
the
dekat
to
me
that
we
were
saying
it
in
about
having
the
the
log
built
on
top
of
a
nag
or
vice
versa
as
well.
Well,
I'm,
not
sure
I
caught
it,
but
I
think
I.
Think
it's
that's
that's
right!
So
do
we
have
IPL
D
and
then
we
have
multi
writer
log
console.log,
it's
not
it's
not
there
in
your
law!
It's
it's
like
it's
a
branch,
a
branch
e,
a
causal
branch
log,
potentially
branching,
but.
B
We
get
like
yeah.
The
thing
is
actually
underneath
that
I
think
I
saw
in
there
infestation.
So
it's
not
really.
On
top.
So
that's
not
to
be
a
problem.
The
problem
was
what
I
was
saying
is
that
they
had
much
more
than
a
simple
dagger
like
structure
where
you
can
resolve
into
a
flattened
list
of
events.
They
have
all
the
whole
replication
system
around
around
how
multiple
logs
merge
together
is
actually
there
implemented
there
and
in
some
scenarios
you
don't
need
that
me
AB.
A
B
B
Merge,
so
it's
not
really
a
problem,
it's
just
that
you
have
to
account
for
that
explicit,
merge
node
when
you
watch
your
traversing
along,
so
that
you
can
ignore
those
nodes.
Whenever
your
question
in
case
of
first
value
have
an
explicit
much
if
you
want
but
yeah
you're
right.
The
see
oddity
already
takes
texture
of
the
you
know,
adding
entries
not
not
interest
but
heading
heads,
so
they
solved
that
using
a
different
system
that
we
currently
don't
need
to
ask.
But
we
must
have
because
we
don't
have
access
to
underlying
interests.
A
A
G
A
It's
a
little
bit
to
be
thing:
I
wasn't
expecting
to
to
come.
The
vid
asked
me
if
I
wanted
to
come
since
it's
a
gathering
of
people
in
Portugal
and
I'm
not
too
far
away,
but
besides
that,
it's
not
not
really
fundamental
to
do
to
what
at
least
what
we're
doing.
I
think
but
I'll
take
the
chance
to
to
work
a
bit
and
then
to
join,
to
to
join
some
conversation
and
some
with
some
some
people,
okay,
otherwise
or
NNC,
and
see
some
some
people
again.
Yeah
all.
G
G
C
G
Okay,
cool
the
I'm
mainly
asking
this,
because
we
need
to
I
think
at
least
these
initial
groups
need
to
align
and
and
see
how
we
can
support
each
other,
because
I
suspect
that
a
lot
of
the
work
like
setting
up
the
content
for
some
initial
workshops
and
that's
that
sort
of
stuff
could
and
should
probably
be
shared.
Like
let's
say
we
do
a
design
like
ten
workshops
or
something
like
that.
Maybe
we
can
split
it
between
the
several
chapters
and
it's
chapter
designs,
some
of
them
and
then
shares
with
the
rest.
C
Like
Michael
Rogers
is
in
charge
of
the
the
community
thing
in
proto
school
and
they
put
a
lot
of
work
into
it.
It's
really
quite
impressive.
It's
a
whole
application
that
they're
writing
that
will
power
all
this
and
okay.
It's
interesting!
It's
gonna
be
interesting
to
see
how
it
comes
together
with
group
when
they
launch
it.
Okay,
in.
A
Terms
of
the
things
that
that
that
we're
going
to
be
able
to
offer
from
the
dynamic
data
working
group
to
the
community
Jim
is,
is
the
Dakota
guide
to
I,
mean
so
said.
There's
the
effort
I
think
we
have
to
join
join.
So
both
of
you
have
to
talk
about
about
about
this.
What
about
the
community
since
Jim
has
has
had
a
lot
of
experience
in
creating
articles
and
blog
posts
and
videos
and
demos
and
workshops
there
is
its
its
present
on
on
Doc
er
2019,
you
know
cures.
A
His
name
is
is
on
on
the
outbound,
the
articles
and
videos
that
we're
going
to
produce
on
during
this
this
this
quarter
so
yeah
you,
you
guys
talk
to
each
other.
We
have
I'm
also
interested
in
that
net
aspect.
Of
course,
I'd
like
to
never
there.
There
are
some
ideas
already
of
just
like
brainstorming
ideas
for
subjects
for
articles
and
and
workshops,
but
yeah,
but
that's
after
that's,
somehow
blah
status.
All
that
yeah.
C
I
I
think
we'll
do
some
of
our
own
stuff
that
stand
alone
in
the,
but
that
will
also
work
with
with
what
the
the
community
teams
working
with
doing,
because
the
they've
done
this
all
before
like
they
have
experience
like
they
know
they
have
a
template
that
they
know
will
work
and
they're
rolling
that
out.
That's
really
exciting
to
piece
are
going
about
with
that
nice.