►
From YouTube: IPFS All Hands 🙌🏽 📞 Feb 5, 2018
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
A
B
C
So
I've
got
some
questions
which
you
guys
can
just
tell
me
to
go.
Read
the
manual
one
of
them
is
about
IP
LD
and
how
far
along
that
project
is,
and
then
the
other
one
is
about
what
is
it
called
C
blower
versus
the
protocol
buffer
thing?
What
do
people
where's
that?
What
what
do
people
think
about
those
which
one
should
I
cry?
You
burst
Paul.
C
I,
assuming
there's
nobody
new
here
from
last
week,
which
there
might
be
people
should
know
me,
but
if
you
don't
I'm
working
on
this
project
called
Nuria,
where
we're
trying
to
create
a
marketplace
for
the
exchange
of
carbon
removal
credits,
and
we
want
to
make
it
as
these
centralized
as
possible
to
create
trust
or
a
platform
for
trust
across
fires
and
sellers
of
these
assets.
And
so
ipfs
is
very
interesting
to
us
possible
distributing
public
data
in
a
way
that
is
decentralized.
E
I
can
try
to
take
a
stab
at
answering
those
questions
and,
given
that
I've
been
reading
the
issues
that
Paul
as
opening
and
the
emails
with
other
questions,
I'll
I'm
going
to
try
to
be
like
specifically
answering
what
your
questions
giving
that
I
have
all
these
other
contacts
but
like
if
someone
else
like
he's
not
following
feel
free
to
like
raise
your
hand
and
stop
me
and
ask
for
more
contacts,
and
so
I
POV
is
many
things.
One
way
to
describe
a
plb
is.
E
It
is
a
canonical
way
to
reference
Aisling
data
and
so
anything
that
you
today
f
access
through
an
can
be
a
get
walk.
It
object
can
be
a
Bitcoin
block,
a
turn
file,
an
IP,
FS
file,
etc,
can
be
described
by
a
type
eld
link
and
right
gal.
The
link
is
a
Content
identifier,
so
the
terms
ID
appears
a
lot
of
times
when
talking
about
IPO
B,
when
when
we
use
a
kill,
the
on
ipfs
or
we
can
use
a
kill,
the
wanna
confess
through
the
deck
API.
E
So
if
you
do
I
press
space
stag
or
if
you
are
using
just
the
parasite,
because
cop
dot
back,
you
will
get
two
function,
calls
and
get
input.
Put
you
can
put
the
egg
nodes,
you
can
even
I
just
drop
some
blob
of
JSON
Mike.
It
will
add
it
to
my
PFS
and
it
will
a
and
it
will
give
you
the
CID
for
that
pop
up
Jason.
If
you
do
get,
you
can
do
two
things.
E
You
can
just
get
a
CID,
so
continent
fire
and
you
get
the
note
back
or
you
can
do
a
CID
plus
a
path.
So
if
you
have
an
object
with
like
a
property
name,
you
can
do
CID,
slash
name
and
now,
instead
of
like
reading
the
the
object,
you
just
read
the
property
that
is
on
the
object
itself,
and
so,
if
that
property,
that
you're
having
that
object,
is
actually
a
link
to
some
other
object.
E
File
and
ipfs
will
be
able
to
use
the
IPL
the
resolver
to
traverse
to
those
multiple
formats
and
find
the
data
that
you
are
actually
looking
for
without
without
having
to
stop
at
any
part
of
the
resolving,
because
it
is
a
different
format
or
because
the
other
structures
are
not
droppable
like
it.
That's
what
it
is
solving
at
the
first
layer,
the
for.
E
So
that
the
answer
to
that
is
shot
to
256
for
everything
that
is
ipfs
files,
but
that
doesn't
mean
that,
like
if
we
are
like
fetching
between
blocks
that
we
are
going
to
use
the
same
ash,
we
we
understand
like
that.
That
is
a
different
ash
on
the
CID
and
we
use
that
to
check
the
integrity
of
the
block
and
so
expending
a
little
bit
more
on
that
and
on
your
previous
question
about
like
what
is,
he
bore
what
is
per
above?
E
E
Pointing
to
other
nodes
at
point
to
other
nodes,
then
eventually
add
the
data
of
the
file,
and
that
is
like
what
you
get
like
the
data
structure
that
you
get
when
you
use
like
ipfs
add
today
we
have
a
new
format
that
comes
with
activist
called
X
Ybor,
and
it
is
essentially
the
same
thing
like
you
can
construct
the
same
bag
with
vacci
board,
but
it
has
other
properties.
For
example,
it
doesn't
require
you
to
have
a
schema.
E
So
if
you
wanted
to
represent
the
file
on
ipfs
with
some
other
structure,
you
are
not
forced
to
like
use
the
data
field
and
the
links
field.
You
can
have
your
own
names.
You're
gonna
have
your
own
metadata.
You
can
have
whatever
you
want,
because
in
the
end
it
is
like
a
JSON
object
in
your
wagon
one
like
this
driving
already
gets
represented.
It
also
has
one
again:
you
know
it
is
a
deck
see
war,
but
it
has
one-to-one
mapping
with
Jason.
So
you
can
use.
C
Just
so
I
imagine
that
I
mentioned
that
Seymour
is
this
specific
specification
and
the
protobuf
is
like
Google's
protocol
buffer
format,
yeah
and
I
mention
they
have
similar
characteristics
in
terms
of
efficiency
and
encoding,
and
things
like
that
not.
E
Necessarily
like
there
are
some
things
or
Arabic
cells
better
than
seawater,
but
axiory's
more
flexible,
just
because
again
one-to-one
mapping
to
Jason.
It's
really
good
for
anything
that
we
do
on
the
web
and
like
what
developers
love
tinkering
with
Jason,
but
for
ipfs.
It
works
really
well,
because
we
can
serialize
a
Jason
into
a
thing
that
is
binary,
packed
and,
and
we
can
use
that
binary
package
formats
to
move
the
nodes
around
and
to
to
make
sure
that
we
always
to
the
same
value.
F
G
So
good
question
the
Seaboard.
D
G
E
C
war
is
the
serialization
format
when
we
have
the
IPL
be
format
the
XE
board.
We
are
already
like
making
some
decisions.
For
example,
we
are
saying:
hey
like
you,
can
ask
Jason
to
this
thing
and
we'll
do
the
sterilization
for
you.
We
are
not
going
to
insert
another
schema
because
C
bar
also
supports
for
schemas.
If
you
want
but
like
we,
we
don't
like
pick
any
schema
for
the
the
serialization,
and
so
it's
actually
we
don't
mess
your
data.
E
E
E
E
Okay,
okay,
so
from
the
start
see
war
is
just
like
a
binary,
Peck
format
to
represent
Jason.
It
actually
sends
four
concise,
binary
object,
representation,
and
we,
when
we
have
the
Dex
award
format
for
IPL
D,
we
are
already
making
some
decisions
of
how
that
format
should
be
used.
For
example,
we
decide
not
to
use
any
specific
schema,
and
so
when
we
grab
a
blob
objects
and
if
you
get
sterilized
to
the
default
schema
that
C
bar
uses
it's
actually,
it
means
like
we
don't
mess
with
your
data.
E
E
But
yeah
you
have
this
resolver
thing
you
plug
in
all
these
formats
and
suddenly
these
full
resolver
gets
like
a
the
ability
to
resolve
through
that
specific
format.
And
so
you
can
do
this
for
again
for
PTO
and
criterium,
for
the
XC
or
for
diaper
above,
and
you
can
create
tomorrow,
exact
message
back.
You
can
create
tomorrow,
your
own
format,
right
you
can.
E
You
can
have
Paul's
service
action,
binary
packs,
whatever
in
any
credit
to
ipfs
and
so
I
profess,
then
we'll
know
how
to
traverse
that
format
as
well,
so
that
if
someone
does
a
query,
a
fetch
for
something
that
is
inside
the
data
structure,
it
can
indeed
like
fetch
some
key
that
he's
on
that
data
structure.
Why.
F
E
E
Exactly
that's
it
and
and
yeah.
We,
if
you
go
to
the
IPL
BR
and
if
you
like,
search
for
Jess,
that's
IPL
B
any
of
those
formats.
You
will
find
like
a
module
for
each
of
the
format's,
which
is
accentuated
clicking.
That
was
describing
then
attaches
to
the
maenge,
resolver
and
and
then,
as
always
like
all
of
them
at
the
same
epi.
So
basically
they
are
just
teaching
IPL
D
to
traverse
into
the
thermos.
So
I
saw
one
more
hand,
but
no
I
don't
see
it
anymore.
B
I,
just
this
generated
question
for
me,
which
is
on
Friday
I,
was
chatting
with
Lars
about
the
fact
that-
and
this
sounds
may
be
similar
in
like
Lib
Lib
p2p,
depending
on
your
implementation.
If
you
don't
have
all
the
same
transports
in
your
implementation
that
another
node
might,
you
might
not
be
able
to
actually
communicate
with
all
the
nodes
out
there,
because
they
might
not
all
speak
the
same
set
of
transports?
Is
this
sort
of
a
is
it?
Does
it
make
sense,
or
is
it
correct
to
think
of
it?
E
The
way
that
works
and
and
by
the
way
this
is
like
IPL,
be
a
level
one.
There's
like
two
more
levels
that
then
offer
other
features,
but
what's
like
just
make
sure
that
everyone
is
really
solid
in
everyone's
minds,
and
so
because
you
I
don't
want
fetching,
you
at
least
still
get
the
data
and
because
the
links
it's
themselves
have
the
multi
collect
so
the
type
of
the
data.
E
H
Just
back
out
of
like
you,
through
in
this
notion
of
resolvers,
without
finding
a
resolver
so
to
Rob's
question:
if
I
have
an
IP,
FS
node,
that's
storing
some
aetherium
transactions,
but
it
does
not
have
the
resolver.
That
knows
how
to
make
sense.
House
knows
how
to
resolve
selectors
within
etherium
content.
That
node
would
still
be
able
to
give
you
the
the
content.
H
It's
your
intersection,
and
so
that
part
you
would
need
an
IP
FS
note
that
has
a
resolver
that
speaks
aetherium
like
that
knows
how
to
parse
an
aetherium,
the
etherium
data
format,
and
so
that's
where
different
nodes
will
have
different
resolvers
and
then
part
of
the
work
is
making
it
so
that
you
could
even
dynamically
load
a
resolver.
If
you
don't
have
it.
A
H
You
recommend
it's
more
that
the
documentation
around
this
is
still
coming
into
existence
and
so
I'm
more
I'm
wondering
which
what
should
be
the
focus
if
we
made
a
couple
tutorials
around
IP
LD.
What
should
those
tutorials
show?
My
inclination
is
to
have
one
tutorial
that
shows
you
just
round-tripping,
some
JSON
through
dag
Seaborg,
so
I
have
some
I
have
some
metadata.
H
That's
maybe
pointing
to
a
get
data
set
and
an
ethereal
transaction
and
I
write
that
into
a
I
P
of
s
and
I'm
able
to
use
that
information
and
load
it
back
down,
use
the
resolvers.
So
maybe
it's
a
tutorial
that
shows
that,
but
also
something
that's
even
simpler
of
I
want
to
create
some
metadata
about
a
file
I,
just
added
ipfs,
so
I
expressed
that
metadata
as
JSON
and
I
persisted
into
ipfs
Anika's
persisted
as
as
IP
LD,
so
that
I
could
then
use
use
that
route
use
resolvers
to
read
the
info.
H
Those
are
the
two
tutorials
that
I
lean
towards
that.
We
should
probably
make
around
this
because
I,
that's
like
scratching
the
surface
of
what
IP
LD
is
and
honestly
I
think
when
you
go
deeper
than
scratching
the
surface.
It
just
confuses
people
like
the
dog.
There
is
documentation,
other
the
good
is
deeper,
but
it's
just
competing
people
that's
far
because
there's
just
too
much
there.
A
Conceptually
awesome,
so
we
are
going
to
I
do
intend
to
in
this
at
10:30
unless
people
want
to
extend
it
and
I
noticed
that
there
are
about
10
or
11
people
that
have
put
their
names
in
the
notes
and
their
918
on
the
call.
So
if
you
haven't
added
your
name
to
the
notes,
please
do
so
any
any
other
topics
or
do
we
want
to
continue
this
conversation
for
another
five
minutes,
I.
E
Did
I
just
wanted
to
point
out
to
some
links,
so
I
posted
here
on
the
chat,
the
interface
IP,
only
format,
which
is
basically
the
interface
that
it's
like
modules,
have
to
implement
to
add
a
new
format
at
the
newspaper
Laurel
power
to
that
kildeer
is
over.
You
can
check
just
IPL
B,
which,
as
well,
it's
it's
where
all
these
other
formats
get
plugged
in
and
like
there's
a
bunch
of
tests
on
like
reading
notes
and
like
going
to
the
nodes
and
doing
traverse
traversal
on
a
nodes.
E
E
The
idea
of
this
to
that
location
so
that
it
creates
then
the
proper
graph
there
is
also
the
UNIX
FS
engine
and
a
UNIX
FS
engine
is
the
module
that
knows
how
to
convert
files,
check
them
and
create
the
graphs,
and
there
is
multiple
layouts,
multiple
topologies,
all
those
were
created.
It's
a
little
bit
more
complex
module
but
like.
If
you
have
time
to
dive
into
the
into
it,
you
will
see
all
these
graphs
are
created
and
how
these
things
get
used
and
yeah.
This
is
the
module
that
keeps
all
the
FCAT
get.
E
Api
is
to
just
be
fast.
So
a
lot
of
great
insights
there
again
like
it'll,
be
great.
This
was
all
a
tutorial
but
yeah
like
we.
We
have
a
hybrid
between
examples,
some
explanation,
some
spec
and
some
code
that
might
help
people
understand
the
other
point.
I
really
want
to
make
again.
This
is
like
level
1,
but
this
is
just
like
getting
ipfs
to
be
able
to
be
the
smirk
of
forest
where
all
the
medical
trees
can
live
and
all
the
mecha
trees
can
be
found
and
you
can
traverse
through
them
from
like.
E
You
can
jump
from
one
tree
to
another
tree,
there's
other
two
layers,
and
that
is
when
we
talk
about
selectors,
where
it's
sort
of
like
you,
just
speaking
a
property
of
a
graph.
You
can
actually
pick
like
an
intersection
of
a
graph,
and
then
there
is
another
thing
which
we
typically
call
transformations,
but
transformations
might
be
also
known
by
grass
theorists
as
processing
referencing
or
ask
people
from
databases
as
query
language,
and
so
that
is
where
we
talk
about.
E
C
E
I
could
be
awesome
to
be
able
to
use
graph
key
all
noise.
Another
like
graph
engines
on
top
of
my
PFS
and
I.
Just
just
I
might
be
festive
like
a
storage
engine
for
them
and
later
like
improve
those
the
ground
on
the
basis
to
understand
what
is
Ashley
so
that
they
can
get
the
benefits
for
their
searches
and
for
the
queries
and
so
on,
but
yet
to
agree
which
you
get
graph
QL
as
a
pro
that.
A
Cool
awesome
stuff,
so
Thank,
You
devide,
thank
you,
Paul
Thank,
You,
Wyatt
and
I
would
just
like
to
say
that
you
know
I've
watched
some
of
Pedro's
tutorials
I,
think
they're,
awesome,
I've
watched
some
of
Victor's
sessions
and
I
think
those
are
very,
very
helpful
as
well.
So
let's
see
I
I
count
about
14
or
15
names
on
the
attendance
list
than
the
notes.
Let's
see
about
18
participants,
so
please
add
your
name
if
you
haven't
done
so
already.
A
There
was
a
comment
to
please
add
all
the
links
that
divvied
posted
in
the
chat
into
the
notes
and
I
think
that
would
be
really
really
helpful.
So
we
are
at
30
minutes
after
the
hour.
According
to
my
clock,
are
there
any
other
topics?
Anything
anyone
would
like
to
say
before
we
wrap
it
up.
We
are
trying
to
keep
these
two
30
minutes.
If.