►
From YouTube: Dynamic Data and Capabilities WG — April 03, 2018
A
All
right,
everyone
welcome
to
the
inaugural
the
first
meeting
of
the
dynamic
data
and
capabilities
working
group,
so
I'm.
My
name
is
Pedro
and
the
lead
of
this
working
group
thanks
for
joining.
So
if
you
could
put
your
names
on
the
attendee
list
of
the
notes,
please
I
would
much
appreciate
it.
I
just
pasted
a
hit
pad
link
on
the
chat.
A
A
A
A
So
first
the
goals
of
the
of
the
working
group.
But
this
is
something
that
is
not
written
in
stone.
It's
kind
of
in
motion,
but
I
think
it
sums
up
in
an
abstract
way.
What
what
the
goal
is
is
to
research,
the
research
and
development
of
building
blocks
that
enable
collaborative
applications,
providing
solutions
for
security,
identity,
access
control,
concurrency,
a
synchronization
offline
and
near
real-time
collaboration
on
top
of
IP
offense.
A
A
So
here
are
the
current
issues
that
we're
trying
to
track.
There
are
like
three
big
groups
of
things
that
we're
going
to
address
we're
going
to
try
to
address.
First
all
so
this
is
like
an
open
list,
feel
free
to
add
your
your
suggestions
or
your
questions
here.
So
as
I
was
saying,
three
main
groups
charities.
If
for
people
that
don't
know
what
Sierra
teas
are,
there's
there's
a
good
some
on
on
the
resource
further
down
on
on
a
grid
pad
here,
sorry,
this
is
cutting
it
away,
yep.
A
So
there's
a
security
research
link
here
for
people
that
if
people
want
to
use
to
know
more
about
strategies,
so
basically
they
allow
in
a
very
assertive
way
they
allow
for
collaborative
real-time
and
shared
editing
of
data
structures,
and
one
of
the
use
cases
would
be
like
a
Google
Doc.
For
instance,
Google
Doc
would
be
a
good
case
for
people
changing
the
same
data
structure
incorrectly,
and
so
it
requires
no
no
synchronization
between
the
peers.
A
So
there
are
there
a
bunch
of
issues
open
here.
I,
could
you
can
go
through
those
later
if
we
could
go
through
those
later?
If
you
want
to
so,
first
one
is
charities
to
enable
the
collaborative
editing
of
their
structures
and
the
other
one
is
identity.
So
how
those
know
about
the
humans
behind
or
the
the
person's
the
person
behind
each
one
of
the
peers,
and
how
do
you
prove
certain
things
to
each
other?
A
The
other
one
is
the
vids
kinda,
descriptive,
cryptographic,
cryptographic
ACLs,
so
a
way
to
give
permissions
and
take
permissions
from
those
peers
or
from
those
people
over
certain
resources
that
we
want
to
manage
on
our
applications.
So
those
are
the
three
main
groups
that
were
going
to
try
to
track
what
I
said.
People
can
join
in
and
add
issues
and
and
and
remove
the
issues.
This
is
what
we're
going
to
use
to
coordinate
all
the
work.
A
A
There's
also,
this
biweekly
meeting
that
were,
we
can
use
to
to
sync
up
with
each
other
and
there's
a
bunch
of
list
of
current
endeavors
going
on
which
are
more
applications
and
libraries
I
like
byproducts
of
this.
This
group,
one
of
them,
is
pure
pad,
which
is
centralized
collaborative
near
real
time.
Editor
that
uses
shared
it
is
underneath
its.
There
is
a
first
alpha
version
out
there
and
there
are
a
lot
of
people
working
on
on
a
new
version
of
pure
pad.
A
A
lot
of
new
features
has
its
own
repo,
which
you
can
can
join
in
and
check
it
out.
There's
y
ipfs
connector
what
she
has
is
library
for
the
implements
charities.
So
why?
Because
connector
is
something
that
takes
a
white
yjs
and
use
this
black
offense
pops
of
network
to
four
notes
to
discover
and
talk
each
other
there's
also
be
reality.
Pure
charity
is
the
library
that
implements
up
operational
strategies
and
then
in
an
abstract
way,
but
also
pecially
TIFs,
which
is
an
implementation
of
that
over
ipfs.
A
So
like
a
transport
of
knights
over
a
PFS
and
there's
a
bunch
of
them,
one
of
them
is
temporary,
which
is
like
a
centralized
eventually
consistence
TV
store
kv,
store
over
PFS
and
again
for
free
to
add
any
endeavors
that
you
want
to
start
working
on
or
have
been
working
on
here
on
this
Rigney
page
more
resources,
let's
see
I,
think
that's.
It.
B
I
think
one
thing
that
hasn't
been
said
is
essentially
so
there
has
been
a
lot
of
development
on
creating
these
building
blocks
for
new
applications
and
like
for
the
last
year,
Pedro
as
being
like
pretty
much
like
carrying
like
just
taking
his
ship
forward
and
like
working
with
other
people.
Some
of
them
are
present
here,
but
he
has
been
like
creating
all
these
building
blocks
by
himself
to
create
apps
like
peer
path.
B
Now
we
have
this
working
group
that
the
purpose,
as
Pedroia
explained
like
it,
is
to
continue
this
development,
but,
as
the
name
suggests
like
working
group,
is
to
include
more
people
in
the
conversation
so
that
more
people
can
participate,
possibly
with
their
time.
The
idea
suggest
and
so
on,
and
so
like
right
now
like
the
working
group,
is
explaining
right.
B
So
Pedro
is
like
the
lead
and
pretty
much
like
that,
the
only
for
that
one
person
and
you
will
be
interested
in
knowing
it's
like
who
is
available,
slash
interested
on
on
being
part
of
these
challenges
like
in
part
of
this
development,
and
perhaps
with
that
like
it
will
be
good
to
do
the
round
of
interest
so
that
everyone
could
like
explain
like
who
they
are
or
just
introduce
themselves
and
explain
what
they
are
interested
and
what
they've
been
doing
so
far.
It's
not
everyone
is
on
the
same
page,
yep.
A
That's
the
the
next
item
on
the
agenda.
I
can
I
can
go,
go
ahead
and
give
the
first
the
first
one
just
just
to
set
the
template
so
yeah
I'm,
Pedro
I'm,
lead
of
this
working
group.
I've
been
working
for
for
protocol
apps
for
a
bit
over
a
year
on
J's,
J,
ipfs,
related
stuff
and
all
the
libraries
underneath
all
not
all,
but
some
of
them,
and
before
that
well
I've
been
a
software
engineer
for
20
years,
I'm,
mostly
interested
in
decentralized,
well
distributed
systems
and
more
lately
centralized
systems.
A
A
Others
I
have
performance
issues
of
austerity
over
IP
LD,
so
for
those
who
don't
know
I
peel
D
is
is
like
a
language
that
padma
square
allows
grabs
the
build
on
on
top
of
a
DFS
and
charities,
and
people
at
EFS
is
a
word
of
that.
Oh,
and
there
are
some
issues
in
transmitting
equations
charity
operations
on
combat
and
I'm
working
on
that
and
they're
like
I.
A
A
E
A
C
C
A
F
F
And
adding
0
of
having
embedded
JS
ipfs
node
within
web
browser
I
feel
this
is
like
a
prerequisite
for
any
work
that
is
done
by
your
working
group,
or
at
least
it
provides
better
user
experience.
When
someone
wants
to
quickly
start
playing
with
stuff,
they
can,
for
example,
right
now.
They
can
just
installed
ipfs
combined
for
beta
channel
and
it
can
switch
to
embedded
node
and
play
with
even
pub/sub.
You
are
able,
thanks
to
Allan's
patch,
we
are
able
to
initialize,
but
that
node
with
arbitrary
configuration.
F
G
Yeah
hi,
my
name
is
Brendan
O'brien
I'm,
the
founder
of
a
project
called
query.
We're
building,
get
four
data
sets
on
ipfs
and
we're
really
interested
in
a
lot
of
things
that
touch
the
dynamic
data
side
of
things.
Our
current
sort
of
architecture
structure.
It
is
an
overlay
network
on
top
of
an
overlay
network,
and
we
have
sort
of
were
confronting
identity
problems,
access,
control
problems
and
pin
tracking
under
churn
problems
in
real
ways.
G
So
we're
really
excited
to
sort
of
just
like
get
messy
share,
notes,
try
and
collaborate
in
ways
that
can
hopefully
advance
a
number
of
these
issues,
so
anything
I
can
do
to
sort
of
help.
Contribute
to
the
thinking
happening
here
not
and
be
super
excited
to
do
so.
We
also
have
our
code,
is
completely
open
and
so
we'll
be
happily
sort
of
sharing
and
tracking
anything
as
we
sort
of
make
developments
here.
But
one
of
our
big
sort
of
driving
forces
at
the
company
is
trying
to
avoid
sort
of
inventing
new
specifications.
A
G
We're
really
looking
forward
to
that.
I
want
to
take
a
good
look
at
CR
DTS
before
I
get
super
connection
to
it,
because
for
us
we
have
a
little
a
little
less
need
for
live
sort
of
collaborative
editing,
but
that's
definitely
sort
of
like
the
concept
of
a
session
or
the
concept
of
sort
of
a
live
session
is
really
important
to
us
sort
of
in
a
longer
term.
So
I'm
interested
to
see
like
how
do
whether
a
CR
DT
is
a
good
application
that,
like
scales
in
this
sort
of
300
mm
Z
peers
range.
A
C
Ollie
ollie
the
web
apps
for
many
years,
notably
worked
with
Pedro
and
Alan,
building
the
first
iteration
of
pier
pad
and
now
working
with
little
on
ipfs
and
web
browsers
and
the
ipfs
gooeys,
so
building
out
rebuilding
the
existing
give
ease
to
let
the
demonstrate
what
we're
capable
of,
and
so
the
big
interest
in
the
co
DTS
and
what
Pedro
has
been
working
on
a
it's
the
future
and
it
I
just
think.
It's
super
exciting
and
B.
B
Night
rider
who
I
wanted
to
be
a
little
just
a
PFS
and
just
be
projects
amongst
other
random
things.
I
guess
I'm,
one
of
the
original
instigators
to
get
this
exp
work
to
start
get
started
on
IP,
Joslyn
and
I've,
been
just
in
sync
with
better
development
super
excited
for
all
of
this
and
what
it
enables
I
really
excited
for
all
the
apps.
That
will
be
a
blow
to
be
created.
We've
like
these
building
blocks,
you'll
come
out
of
this
working
group
in
yeah,
fun,
stuff.
H
H
So
yeah
just
interested
in
this,
like
all
he
said
well,
I,
did
a
bit
of
work
on
Pierre
pad
for
making
it
look
pretty
when
it
first
came
out
and
now
it's
awesome
and
I've
been
working
a
lot
with,
as
little
said
on,
ipfs
companion
been
adding
window
ipfs.
So
in
ipfs
companion,
whenever
you
visit
a
website,
it'll,
add
a
window
type
EFS
object
and
I'm
hoping
to
send
a
PR
to
Pierre
pad
pretty
soon
to
take
advantage
of
that.
H
A
I
I
Are
you
able
to
hear
me?
Yes,
okay,
yeah,
so
I've
been
doing
a
kind
of
a
bit
tour
for
shopping,
so
it's
like
everybody
is
going
to
maintain
the
christ
history
of
the
product
and
everybody
is
going
to
share
the
data
of
the
market.
So
currently
we
have
applications
like
honey
or
camel
camel
camel,
but
they
are
using
as
our
client
doc
pictures
so
I
just
want
to
make
it
decent,
reluctant
I
made
in
Pontic
I'll
show
you.
I
I
I
I
A
A
I
A
A
A
F
A
Oh,
hopefully
I
was
meeting.
I
was
okay.
All
right
I
was
oh,
it
should
be
me
so
I
just
released
a
new
version
of
I
profess
connected
today,
I'm
I
was
in
vacation
last
week,
so
person
to
point
to
point
out,
which
is
a
new
IP.
First
pub/sub
room
version,
so
I'm
not
actively
using
this.
This
package,
but
I'm,
maintaining
maintaining
it
so
which
is
basically
exactly
the
question.
Yeah.
A
A
F
I
A
Right
right
now
we
have
a
very
crude
mechanism
for
authentication
on
the
applications
that
were
billing,
so,
namely
pure
pads,
which
is
really
just
passing
a
key
on
the
hash
pass,
a
hash
of
the
URL.
So
it's
like
a
way
of
passing
a
key
off.
Man
theoretically
could
transmit
those
over
any
other
channel.
So
just
just
a
bunch
of
keys,
there's
a
read
key
and
there's
a
right
key.
There
ricky
allows
you
to
fold
the
strategy,
so
the
folder
changes
but
doesn't
allow
you
to
make
any
changes.
A
The
right
key
makes
you
allows
you
to
make
changes
so
the
basically,
when
you
write
something
you
sign
it
and
encrypt,
then
when
is
when
you
create
an
operation,
sign
it
encrypted
and
the
operation
being
signs
can
be
validated
by
other
peers.
And
if
the
the
violation
fails,
you
don't
know
you
don't
incorporate
that
change
into
your
theology.
So
this
is
a
very
crude
way
of
of
having
that,
because
anyone
with
you
with
the
right
key
can
send
a
quantity
to
someone
else,
and
then
we
don't
have
any
control
over
over
that.
A
So
yeah
there's
a
lot
of
pending
work
on
on
that
area.
There's
a
lot
of
research.
Also
on
that
area,
I've
listed
a
bunch
of
research,
while
research
and
actual
implementations
on
on
identity
and
access
control
management
we
need
we
need.
We
need
to
pick
as
a
group.
We
need
to
pick
one
or
more
and
implement
them
and
see
where
it
leads.
G
A
Well,
yeah,
there's
I
mean
there's
like
an
issue
for
each
one
of
these
things
that
are
that
out
and
more.
We
couldn't
track
that
there
and
there's
also
in
terms
of
which
the
CID
research
well
charities,
don't
really
tackle
identity
or
access
control,
they're
they're
more
there.
They
work
over
a
network
of
trusted
nodes.
A
A
People
can
create
a
new
issue
here
or
create
a
new
repo,
an
endpoint
that
that
issue
to
that
that
repo
it's
it's
kind
of
open
I,
want
to
have
a
waffle
board,
also
to
track
track,
that
all
the
issues
and
perhaps
have
multiple
multiple
ripples
on
on
the
same
board
knows
that
that's
possible,
but
but
yeah
you
have
any
suggestion.
Brennan.
G
But
it's
effectively
just
an
extension
on
exactly
what
you
just
said,
basically
using
some
sort
of
github
repo
and
it's
basically
an
organizational
choice
above
all
else,
but
more
than
happy
to
do
that,
it's
issues
or
whatever.
But
it's
I,
think
the
most
important
thing
is
just
being
able
to
get
that
quick
overview.
Ok,
where
what's
the
list
of
documents
that
are
worth
checking
out,
what
are
people
sort
of
finding
useful
right.
A
If
it's
something
that
we're
going
yeah
we're
going
to
produce
and
collect,
we
could
also
add
add
documents
to
to
this
repo
right
right
now
until
we
exhaust
the
issues
like
if
issues
become
very
hard
to
to
scan,
we
could
then
then
then
come
up
with
some
other
way.
We
can
revisit
revisit
this
and
in
two
weeks,
perhaps
and
see
what
goes
but
that
that
research,
if
it
relates
to
these
topics,
perhaps
it
would
be
helpful.
A
B
B
B
B
Cool
I
have
a
one
question
and
one
point
which
I
my
question
to
the
crib
I,
don't
know
if
the
Guara,
following
that,
okay
can
I
can
I
go
forward.
Mm-Hmm,
okay,
so
I
will
start
with
my
question
first,
which
is
so
right
now,
like
the
web,
I'm
glad
that
the
web
browser
two-piece
here
because
they
have
been
not
only
in
injecting
ipfs
into
web
browsers
through
an
extension
on
true
integration
or
even
through
a
desktop
application.
They
actually
started
the
work
of
providing
nicer
api's
for
web
developers
to
like
have
access.
B
It's
it's
more
of
a
building
block
to
build
Street
applications,
and
so
I'm
really
interested
to
understand
that
if
there
is
a
need
for
a
CREP
like
key
value,
store
could
be
part
of
the
ipfs
collection
of
tools
that
web
developers
will
get
used
to
by
default
or
if
there
isn't,
even
like
a
generic
thing,
that
we
can
actually
put
it
there
for
anyone
developer
to
use
and
and
I
like
that
question.
If
that
answer
is
no,
it
makes
everything
has
to
be
specific,
specific
their
own
data
pipe.
B
F
Not
sure
if
it's
a
direct
answer
to
your
question,
but
we
have
something
like
a
proof
of
concept
when
it
comes
to
providing
API
like
providing
some
sugarcoating
for
web
developer
or
distributed
app
developer
when
it
comes
to
NFS.
So
what
we
did
is
we
predicts
all
paths
for,
writes
and
reads
from
aquifers
files
API
with
some
like
half
that
is
scoping
access
of
every
app
to
a
specific
subtree
of
entire
IP
first
files
through
right.
F
So
what
this
means
is
that
applicate
provides
isolation
between
data
that
was
written
to
ipfs
files
by
different
apps,
so
that
apps
cannot
change
each
other's
data.
So
that's
like
a
first
experiment
on
a
big
crowd
to
providing
some
sugar
coating
on
top
of
existing
api's.
It's
like
it's
the
same
api.
What
we
do
we
like,
transparently
prefix,
all
all,
writes
and
reads,
and
what
is
related
to
this
is
that
what
should
be
user
experience
and
I
think
I've
I'm,
not
sure
if
I
had
liked
this
discussion.
F
I
think
I
started
this
talking
about
this
yesterday,
but
my
laptop
overheated.
So
if
it
will
overheat
once
again,
so
I
try
to
like
keep
it
minimal,
so
the
user
experience
of
current
web
is
that
browser
does
not
ask
you
to
allow
it
to
have
access
to
local,
store
courage
or
save
cookies
and
stuff
like
that,
though,
there
is
no
dialogue.
Do
you
want
to
allow
this
website
to
like
set
local
storage
under
some
limit
right
and
I?
F
F
F
Otherwise,
we'll
like
end
up
it's
my
leg,
favorite
example
is
the
Windows
Vista
user
access
controls?
That's
just
people
there.
It
was.
It
was
like
the
horror
of
training
users
to
don't
read
anything
and
just
blindly
accept
all
yeah.
So
I
really
don't
want
to
go
that
route
and
I
think
what
we
could
do
is
to
go
this
unboxing
way
route.
I
B
B
Have
like,
when
you
ask
generally
like,
should
you
give
the
decision,
the
power
for
the
user
to
decide
or
not?
I
guess
like
the
default.
Iso
will
be
like,
of
course,
like
always
what
the
user
design,
but
when
you
feel
like
asking
the
user
to
decide
on
300
different
things,
then
it's
not
a
vision
anymore.
It
just
like
a
reflex
of
like
it's
just
clicking.
Yes,
that's
a
very
good
point
and
and
so
yeah
thank
you
for
your
answer.
B
I
have
like
a
couple
of
like
random
ideas
in
my
head
from,
for
example,
having
almost
like
a
building
block
store,
where
you
can
almost
say:
oh
I
want
the
desert.
Okay,
so
I
wanted
a
yjs
thing
and
then,
like
you,
click
yes
adds
to
my
PFS
into
a
browser
extension
I
profess
nodes
and
instead
of
a
then
I
professors
cannot
have
access
to
this
API
as
well.
B
H
H
If
s
is
kind
of
what
you're
saying
David,
you
know,
we
need
a
way
to
figure
out
what
what
should
and
shouldn't
be
in
core
and
that
I'm
just
saying
that
that
might
you
know
using
making
use
of
web
extension
and
making
use
of
desktop
in
that
way.
It
might
be
one
way
to
do
it,
and
so
I
think
Lydell
was
just
saying.
You
know
we've
added
this
whole
em
FS
scoping
to
companion,
and
that's
just
one
example
where
we've
we've
done
something
that
isn't
explicitly
in
in
ipfs
and
we've
also
got
this
whole
permission.
H
This
idea
of
permissions
for
ipfs
they
also
isn't
in
ipfs
but
as
I
think
has
been
discussed
previously
and
hasn't.
We
have
a
consensus
of
how
that
should
work,
but
we've
added
something
that
works,
and
it's
just
an
example
of
things
that
we
can
try
out
in
the
web
extension
the
that
could
then
be
the
ideas
from
that
can
be
iterated
on
quite
quickly
or
changed
without
just
releasing
a
new
version
of
ifs
with
a
half-baked
idea
or
something
in
and
Rickon.
We
can
sort
of.
We
have
a
mechanism
for
trying
stuff
out.
G
G
And
it
would
be
great
if
the
identity
systems
that
we
were
participating
in
weren't
reinventing
this
wheel
of
managing
access,
control
and
sort
of
immigrate,
tablets.
I
love,
some
of
the
permission
screens
that
have
come
out
of
proper
OAuth
integrations.
It's
makes,
makes
my
life
easier,
so
I'd
love
to
see
that
you
know
trans
trans
fat
beta
transfer
over
and
if
we
could
bring
down
the
developer
overhead
of
learning
OS
and
any
of
that
garbage.
That
would
be
really
cool.
In
my
opinion,
yeah.
A
A
It's
like
it's
like
a
way:
I
weigh
too
well
to
store
claims
to
store
proofs
and
to
store
claims
and
proofs
on
on
local
machines,
so
on
a
laptop
or
a
phone.
Well.
That
here
generally,
is
that,
as
a
user
can
only
provide
to
the
application,
specific
claim
or
specific
proof
that
that
application
needs,
for
instance,
I
need
to
prove
that
I
am
over
18
years
old.
G
Totally
and
very
excited
to
look
at
that,
I
think
the
really
exciting
thing
here
that
is
that
we
could
also
be
requesting
access
to
resources
that
are
sort
of
traditionally,
because
you're
operating
on
the
machines
that
can
serve
up
storage
and
compute
I.
Think
there's
some
exciting
things
to
sort
of
extend
that,
but
yeah
I'll
definitely
look
into
this
self
suffering.
Poverty,
yeah.
A
There's
a
bunch
yeah,
there's
lots
of
diff
well
I'll
paste
the
issue
that
tracks
identity
on
the
working
group
up
with
some
some
more
links,
but
that
I've
been
researching
lately
on
that
on
that
subject
which
well
I
didn't.
It
is
not
something
that
I'm
tackling
right,
not
personally,
but
someone
needs
to
so
I'm
just
going
to
put
those
links
over
there
and
someone.
Hopefully,
someone
will
will
absorb
those.
A
And
in
terms
of
what
you
said
of
it,
I
think
in
terms
of
having
like,
like
I
totally
agree
name
spacing,
is,
is
necessary
in
terms
of
strategies.
Specific
strategies
may
be
a
bit
too
early
to
do
that,
because
I
was
so
experimenting
a
bit
for,
for
instance,
just
given
a
quick
example
in
terms
of
scaling.
B
Can
I
go
okay,
cool,
so
the
only
or
one
small
thing
that
happened
today?
It
was
kind
of
like
a
reorg
of
the
pier
taps,
building
blocks
on
the
IPF
scpi
ripple,
so
after
after
some
work
that
fritzy
and
endale
and
others
from,
and
yet
that
I've
been
doing
or
building
a
block,
wheel,
ipfs
and
basically
taking
some
of
the
world
activities
with
charities
and
capabilities
for
pier
pad
and
I
just
creating
a
general
platform.
B
So
that,
like
you,
can
build
apps
weed
out
the
platform
and
that
can
be
block
and
be
forum
like
issues
like
be
capable
to
support
model
use
cases.
So
with
all
that
development,
and
that
conversation
we
decided.
Okay,
let's
I,
just
like
create
this
kind
of,
like
small
/,
large
endeavor
of
not
necessarily
creating
like
complete
apps,
but
actually
just
like
testing
the
technology
testing.
These
building
blocks.
Getting
the
conversation
going
getting
the
examples
going
clinic
is
open
the
product,
it's
like
a
peer
peer
on
peer
forum,
etc.
B
People
are
using
these
primitives,
these
cryptographic,
ACL,
primitives
and
more,
and
so
now
you
can
check
out
on
that
repo
again
like
the
organization,
just
the
the
cleanup
was
on
this
morning.
So
it's
pretty
simple
right
now
but,
like
you,
can
see,
there's
a
list
already
of
like
the
apps
that
have
been
built
or
that
are
in
progress
peer,
bad
peer,
flipchart,
your
blog.
B
Then
there
is
like
the
building
blocks
PFF
core
and
that
that
is
what
is
getting
transformed
into
becoming
like
the
peer
platform
and
like
Pierce,
ATT,
PAP,
fests
could
mirror
and
and
also
some
examples,
and
so,
ideally
in
the
soon
future,
you
will
have
apps
that
you
are
familiar
with
like
you
have
built
in
the
centralized
web.
So,
like
you
know
what
are
your
challenges
and
you
will
have
a
version
for
the
decentralized
web,
and
so
you
can
better
map
your
knowledge
from
one
to
the
other
and
I
understand
how
to
do
things.
B
A
B
A
A
H
Yeah,
hey
just
quickly
really
quickly,
one
of
our
otice.
You
create
a
place
where
people
can
register
for
using
windowed
ipfs
like
a
website
kind
of
like
experiments
on
like
on
the
chrome,
experiments
website
and
it'll
be
cool
if
we
had
some
cross-pollination
which,
in
there
or
register
different
apps
and
app
types
and
stuff
like
that,.