►
From YouTube: 🖧 IPLD Every-two-weeks Sync 🙌🏽 2022-04-26
Description
An every two weeks meeting to sync up on all IPLD (https://ipld.io) related topics. It's open for everyone and recorded. https://github.com/ipld/team-mgmt
A
B
Hello,
I
haven't
been
here
since
a
couple
meetings
back,
but
I
haven't
been
up
to
too
much
mainly
been
working
on
the
what
is
ipld
image,
updating
it
to
new
stuff
from
warp
fork,
and
we
got
a
clean
copy
from
the
whiteboard
sketch
done
from
the
design.
Shop
and
rods
gave
some
useful
feedback
for
adding
and
removing
some
stuff
from
the
image
and
from
the
wording.
So
I've
just
been
working
on
that
probably
going
to
get
it
merged
soonish.
B
The
other
thing
is
that
we've
set
up
a
reviewer's
team
in
the
ipld
organization,
so
part
of
that
is
we
have
this
new
github
automation
thing
for
making
changes
to
the
github
org,
so
we
can
do
pull
requests
to
modify
some
json
files
to
create
new
teams
and
the
first
team
that
we
have
for
that
is
this
reviewers
team,
and
so
I'm
testing
it
out
right
now
to
have
an
easy
way
to
kind
of
tag.
B
People
to
review,
pull
requests
right
now,
it's
just
for
the
ipld
ipld
repo,
which
is
mostly
concerned
with
like
spec
work
and
the
website.
But
potentially
we
might
look
into
seeing
if
we
can
have
a
similar
approach
for
the
go
ipld,
prime
repo
or
anything
else,
so
that's
kind
of
a
work
in
prog
progress.
I'm
I've
got
some
docs
in
the
readme
together
kind
of
looking
to
see
if
we
could
use
it
in
github
issue
templates
and
also
kind
of
seeing
the
limitations.
B
So
one
thing
that
would
be
useful
is:
if
anyone
cares
about
processes
like
this
ping
me
on
discord
or
matrix
or
whatever,
particularly
folks,
on
the
go
ipld
prime
team
it'd
be
cool
to
talk
about,
or
we
can
talk
on
this
on
the
github
issue.
So
I
think
I
can
link
to
the
issue
now
sorry
I'll
link
to
the
issue
after
yeah
and
then.
Finally,
the
other
thing
is
that
the
ipld
url
scheme
document
that
I
put
together
has
been
getting
more
reviews
and
more
kind
of
like
feedback.
B
It's
still
kind
of
up
in
the
air
on
what
it
will
look
like
mainly
the
questions
are
like
how
much
functionality
should
we
or
shouldn't
we
have
a
really
good
credit
or
really
good
feedback
that
a
dean
gave
was
that
right
now?
It's
not
differentiating
too
much
from
the
ipfs
gateway
and
what
it
has
for
loading
data
in
different
ipld
formats,
but
we're
kind
of
talking
about
what
we
can
do.
That'll
actually
make
it
more
useful
for
developers
as
well.
B
I've
been
talking
to
my
developer
friend,
who's
working
on
the
agricore
mobile
dev
grants
with
me,
and
so
we're
looking
at
maybe
starting
to
mess
around
with
some
of
these
ipld
protocols
to
see
if
we
could
make
them
useful
in
this,
like
experimental
peer-to-peer
web
context,
probably
won't
have
anything
stable
until
we
get
some
sort
of
consensus,
but
we
might
have
time
to
experiment,
maybe
early
to
mid,
may
yeah.
B
So
that's
all
I've
got
for
now
yeah
any
questions,
I'm
in
discord
and
matrix
and
everywhere
else,
or
we
can
talk
about
it
after
today,.
D
Mine's
been
a
little
bit
scattered
across
various
things
and
I'm
I'm
working
on
other
things
while
doing
little
bits
and
pieces,
but
I
did
do
a
big,
huge
chunk
of
work
on
the
weekend
because
I
needed
a
weekend
project,
so
the
the
javascript
bitcoin
codec,
I
I
wrote
this
originally
to
I
pldfi
the
entire
bitcoin
chain
in
two
years
ago.
We
were
going
to
store
it
on
filecoin
early
on,
but
ran
into
some
hiccups
with
that.
But
anyway
I
have.
D
I
have
almost
all
of
the
bitcoin
chain,
ipl
dfi
in
in
and
put
in
car
files
stored
on
s3,
but
the
codec
itself
is
was
written
against
an
experimental
version
of
our
newer
ipld
stack,
and
so
it
doesn't
work
with
anything
anymore.
D
It
was
it's
completely
unrecognizable
when,
when
compared
to
our
current
ipld
code-
and
it's
been
a
to
do
for
a
long
time
to
to
upgrade
it's
which
but
just
really
hard
to
prioritize
because
it
doesn't
really
have
a
user
anyway,
I
did
that
on
the
weekend,
because
it
was
just
a
bit
of
fun
and
it's
nearly
all
done
actually
a
lot
of
work,
but
really
satisfying
to
have
a
such
a
complex,
codec
working.
D
So
it
does
the
entire
entirety
of
the
bitcoin
content,
address,
structure
and
yeah,
it's
it.
D
I
I
there's
a
whole
lot
of
other
bit
of
tool
chain
that
I
want
to
get
working
again
so
that
I
can
incrementally
keep
on
extracting
all
the
data
and
possibly
actually
publish
eventually
publish
it
to
the
dht
in
some
form,
but
I'll
be
talking
to
adeen
about
how
to
do
that
with
the
billions
of
blocks
so
yeah
the
fun
little
thing
there
was
a
security
release.
I
think
this
was
published
a
couple
weeks
ago.
D
It
was
fixed,
maybe
a
month
ago,
in
the
in
the
dag
pb
codec,
that
that
guy
pdf
appeal
ipld
prime
uses
whenever
you
used
pp.
So,
underneath
the
xfs,
so
this
is
in
lotus
and
go
ivfs
and
a
bunch
of
other
places.
D
So
certain
blocks
are
a
problem,
so
there's
the
security
advisory
on
github.
If
you're
using
go
appeal
to
go,
kodak
get
dagpb
on
github,
then
github
should
be
alerting
you
to
this.
The
need
to
upgrade
for
this
I
think
dependent
bot,
will
show
up
and
do
this,
regardless
of
whether
you
have
depend
upon
enabled
or
not.
D
D
I
think
it
was
either
a
flaky
or
a
just
a
failing
test,
and
so
that
gets
us
a
step
towards
this
unified
ci
platform
that
we're
using
across
all
of
our
repos
there's.
The
next
step
is
windows
which
I
might
chew
off
at
some
point
in
the
future,
but
this
is
sort
of
like
lower
priority
work
and,
lastly,
just
to
note
a
I
did
a
walkthrough
with
lindsay
who's
running
the
protocol.
D
Labs
network
launch
pad
program
a
a
tutorial
that
I
like
a
hands-on
tutorial,
that
I
found
really
helpful
when
trying
to
explain
ipld
and
graphs
and
routes
and
snapshots
and
all
these
these
concepts
to
to
some
new
folks.
I
did
this
last
year
with
with
a
couple
of
people
and
they
found
it
really
valuable.
So
I
wrote
it
up
and
I
I
took
lindsay
through
it
on
video
and
she's
recorded
that
and
put
that
on
youtube
and
they've
used
it
for
this
current
iteration
of
launchpad.
D
She
might
be
making
it
more
profession
and
and
doing
a
better
version
of
it,
for
maybe
the
future
version.
But
I
I
quite
like
this
as
a
a
hands-on
way
to
talk
about
these
concepts
using
unix
of
s
and
and
it's
it's
inspecting
a
dag
and
looking
at
roots
and
the
cids
and
and
it
actually
uses
the
what's
the
flick.
So
it
actually
uses
the
ipld
slash,
ipl
repo,
which
has
auto
publishing
on
fleek,
so
to
interrupt
to
to
make
a
new
dag
to
modify
the
dag.
D
Anyone
walking
through
this
tutorial
just
has
to
open
a
pull
request
to
that
repo,
and
that's
what
I
say
in
the
instructions
open
a
pull
request
and
we
won't
merge
it,
but
fleek
will
automatically
build
your
branches,
so
it's
a
good
way
for
anyone
learning
to
to
create
a
whole
new
dag
and
then
you
inspect
the
dag.
It's
not
quite
as
nice
as
as
would
be
good
because
one
of
the
problems
we
have
with
that
one
of
the
prop
one
of
the
features
we
have
enabled
on
that
repo
is.
D
We
have
cache
busting
timestamps
on
all
the
links,
so
you
don't
get
the
really
nice
deduplication
of
of
files
and
directories
that
you
would
do
otherwise,
but
but
there
is
so
there's
a
way
of
demonstrating
it.
Anyway,
that's
a
bit
of
fun
and
that's
me:
hey
dean.
E
All
right
yeah,
so
I
got
pointed
by,
I
wrote
it
some
stuff
that
iraqi
was
thinking
about
with
with
you
cans,
I
think
there's
a
bunch
to
like
extract
from
this.
E
That's
been
interesting
and
probably
more
to
go
on
here,
which
is,
I
think,
there's
some
stress
between
like
well
there's
like
what's
a
codec,
what's
an
adl,
what
are
all
of
these
things,
especially
when
you're
coming
from
the
javascript
stack,
where
a
lot
of
this
is
less
well-defined
or
are
not
there
at
all,
and
then
there's
like,
even
if
the
stack
you
know
was
matching
what
gohan
or
is
matching
the
things
that
we
wish
were
in
go
at
the
moment.
E
A
lot
of
ipld
is
dealt
around
like
how
do
I
move?
How
do
I
structure
and
restructure
and
reinterpret
data
and
signatures?
Sort
of
look
like
that,
but
they're
not
really
like
that
right.
It's
just
like
oh
yeah,
the
data
looks
exactly
the
same
as
it
did
before.
E
It's
just
I've
checked
it
now
and
with
throughout,
like
most
of
ipld,
it's
like
if
all
else
fails,
and
you
don't
know
where
to
put
something
make
a
new
codec,
and
so
the
question
is
like:
is
there
something
better
we
can
be
doing
or
suggesting
here
for
people
who
are
starting
fresh
codecs
are
sort
of
always
the
answer
for
your
backwards
compatibility
with
some.
You
know
random
format,
but
if
you're
starting
something
newer,
is
there
like
a
better
way
right
that
gender
is
more
compatibility?
E
So
I
was
thinking
a
little
bit
about
that.
It's
some
conversation
that
will
probably
continue
from
there
something
I
decided
to
do
yesterday
because
I
was
like
yeah.
E
Why
not
is
I
hear
shawwan
has
collisions
and,
and
that
also
like
places
like
git,
have
been
running
some
c
code
to
check
if
you
are
using
something
that
seems
collision
like
and
that's
how
they've
been
getting
away
with
not
upgrading
to
shot
2
like
several
years
ago,
and
so
I
was
like
sure,
let's
just
do
sego
and
made
a
wrapper
for
it
seems
easy
enough.
E
The
main
issue
is
that
the
go
multihash
uses
the
go
interface
for
hashes,
which
don't
have
errors
anywhere,
and
so
what
is
a?
What
is
a
poor
sha
one
to
do
when
it's
it's
found
a
collision
and
wants
to
tell
you
that,
like
please
don't
use
me,
and
so
maybe
we
want
to
make
some
changes
there.
E
All
the
all
of
my
prototype
code,
you've
seen
me
like
demo
in
the
last
session,
or
so
is
now
up
on
github.
I
am
hoping
to
have
more
specs
for
people
to
look
at,
so
they
don't
have
to
read
gross
code
before
next
time,
and
I
guess
the
last
one
is
and
something's
been
floating
around
my
mind
recently,
which
is
even
if
we
have
a
protocol
for
transferring
large
blocks
around
in
an
incrementally
verifiable
way.
E
A
Thanks,
I
just
reminded
myself
that
I
also
have
something
ipd
related.
A
A
So
the
goal
is
to
find
a
way
on
how
to
represent
those
things
in
ipld
and
I've
also
linked
a
document
which
explains
all
those
things
and
we
are
still
discussing
because
so
I
think
I
have
a
fairly
good
understanding,
but
it's
still,
the
questions
are
around
like
again,
which
we
had
previously
with
like
what
is
a
codec?
Should
it
be
a
codex?
Should
it
be
a
multi-hash?
A
Where
do
we
do
the
signaling?
Is
it
if
we
put
another
coding?
Is
it
more
about
the
semantics,
and
so
so
I
get
where
they're
coming
from,
but
my
goal
really
is
so
to
that.
We
find
a
way
that
it's
interoperable
with
what
we
currently
have,
ideally
because
like
they
need
slightly
different
things
and
like
so
it's
an
interesting
problem.
A
I'm
still
talking
to
them,
there's
also
a
discord
server,
but
also
bridge
to
matrix
in
case
someone
is
interested
in
and
yeah
so
there's,
basically
an
ipad
lead
channel
for
the
log
project
where
we're
discussing
and
yeah.
So
I
think
this
week
I
have
another
meeting
with
someone
from
the
folks
and
I
hope
we
can
figure
it
out,
but
yeah
I'm
still
not
happy
what
we
came
up
with
and
yeah
we'll
see
how
this
goes.
A
But
I
think
this
document
in
the
meeting
notes
because,
like
I
think
it's
a
really
nice
write-up
and
like
it's
clearly
that
the
folks
understand
like
what
like
what
ipad
is,
and
there
might
be
some
edge
cases
but
still
like
it's.
I
think
it's
a
really
good
document
on
how
to
like
think
about
data
and
yeah
how
to
do
things
so
yeah
we'll
see
how
this
turns
out.
A
So
I
keep
everyone
updated
once
we
come
up
with
something
and
because
eventually
they
need
codecs,
and
then
we
need
to
discuss
it
on
the
repository
on
like
how
to
actually
do
it.
Yeah
interesting
use
case
yeah,
all
right
so
does
anyone
else
wants
to
give
an
update
or
share
news
or
anything.
A
If
not,
then
I
have
put
an
agenda
item
on
the
list,
because
one
thing,
but
it's
just
like
it-
should
be
a
long
discussion.
It's
just
something
I
wanted
to
mention,
because
I
had
a
meeting
with
eric
like
two
or
three
weeks
ago,
and
what
was
kind
of
interesting
is
that
we
came
on
like
like
what
is
ipod,
actually
useful
for
and
then
also
discussed
like
about
his
current
state
and
about
his
future
state
and
what
then.
A
My
thoughts
were
like
what
I
really
would
be
interested
in
in
what
like
how
people
see
the
what
their
vision
is
of
ipld
or
like
what
it
enables
in
the
future
and
really
like
in
the
long
term.
So
basically,
what
is
your
ideal
ipld
thing
that
you
want
to
build,
because
I
kind
of
agreed
with
eric
that
what
we
currently
have
in
either
of
the
stacks
is
kind
of
like
it's
kind
of
useful.
A
A
I
don't
think
I
remember
anything,
but
I
didn't
so
I
should
have
because
it
would
be
now
nice
to
read
so
basically
what
I
would
like
to
see
if
they
see
if
people
were
to
talk
about
or
basically
if
they
were
to
write
down
something
like
how
they
envision
ipd
or
how
it
might
be
useful
in
the
long
term
would,
I
think,
would
be
totally
interesting
because
I
feel
like
so
many
people
have
so
many
different
ideas
on
what
ipld
is
or
what
it
could
be
that
yeah.
A
It
might
be
interesting
to
basically
get
the
visions
written
down
or
yeah
kind
of
like
an
exploration
report
or
something
so
that
people
can
edit
refer
on
to
and
say
well
like
that's
what
I
want
to
build
yeah
just
as
idea
to
think
about
because
like
for
me,
if
I'm
so
deep
into
it's
like
kind
of
like
I'm,
oh,
is,
is
there?
Is
there
also
an
english
saying
that
you?
Basically
you
can't
see
so
the
literal
translation
is,
you
can't
see
the
the
trees
for
the
first,
the.
D
E
E
But
my
my
like
go-to
of
like
I
couldn't,
have
done
this
without
ipld
right
is
you
know,
sort
of
backwards,
compatibility
like
backwards
compatibility
things
within
like,
like
the
ipfs
context
like
I
just
want
to
move
around
graphs,
don't
care
whose
graphs
they
are
or
what
their
form
was.
If
they're
hash
link
graphs,
I
want
to
move
them
around
and
kind
of.
E
If
you
just
stick
with
like
a
protobuf,
it
doesn't
work.
If
you
stick
with
a
protobuf.
What
you
end
up
with
is
is
bittorrent,
which
is
like
they
chose
a
format
for
for
files
and
directories
and
the
way
they
were
going
to
structure
it.
There's
only
one
way
and
that's
how
you
do
it
or
you
could
do
what
git
did,
which
is
they
not
only
did
you
know
they
did
that,
and
then
they
also
decided
they
were
going
to
hardcode
their
hash
functions.
E
While
they
were
there
and
then
when
it
broke,
they
were
going
to
like
hard
code
them
a
second
time
instead
of
learning
the
lesson
right,
and
so
I
feel
like
most
of
this
is
about
like
being
able
to
build
the
tools
that
do
what
you
want
to
do
without
being
locked
into
the
without
being
locked
into
some
of
the
irrelevant
decisions
around
like.
How
exactly
did
I
structure
my
bytes
on
the
wire
or
like
which,
which
of
these
ident,
mostly
identical
hash
functions?
Did
I
actually
use
you
get
to
build
tooling?
D
I
keep
on
reflecting
on
the
the
blockchain
problem
that
we
have
and
they
call
it
a
problem
because
it's
a
it
is
a
problem
for
us,
because
the
blockchains
use
content
addressing
for
a
different
reason
than
we
view
it
like
it,
and
actually
it's
not
just
blockchains,
but
but
it,
but
it
is
particularly
apparent
in
blockchains
blockchains
use
a
content
addressing
for
a
consensus
mechanism
for
inclusion,
for
you
know
doing
merkle
merkle
proofs.
D
Essentially
we
use
we
use
content
addressing
for
from
a
navigation
perspective,
so
they
want
to
go
upwards
and
get
a
root
hash
and
that's
your
signifier.
We
want
to
go
downwards
because
we
want
to
navigate
to
data
and
blockchains
never
want
to.
They
never
want
to
navigate
by
content
stress
they
they
want
to.
D
They
want
to
assure
that
the
data
being
looked
at
is
part
of
the
root
content
address,
but
once
you've
done
that
it's
like
yeah
whatever,
and
so
we
keep
on
bumping
into
these
data
structures
that
are
that
are
content
addressed,
but
really
hacky
in
you
know,
in
a
way
where
you
can
see
it's
they're
built
for
the
inclusion
problem.
D
How
do
we
get
this
bit
of
data
included
in
the
root
hash
and
it's
not
for
the
navigation
problem
at
all,
so
every
blockchain
other
than
filecoin
has
this
problem
for
when
we
apply
ipld
to
it
of
trying
to
make
it
fit.
And
you
know
it's
really,
some
of
it's
really
nasty
too
and
and
that
sort
of
exposes
a
lot
of
the
weaknesses
of
of
ipld.
D
D
I
tried
to
find
the
framework
for
launch
launchpad
and
I
think
git
is
a
really
nice
example
of
an
application
that
that
users
actually
uses
content
addressing
for
a
bit
of
navigation,
because
people
use
the
hashes
to
dig
down
into
things,
but
it
it
does
produce
a
very
clean
content
address
tree.
So
there
are
applications
outside
of
the
the
sort
of
the
consensus,
the
pure
consensus,
blockchain
model.
That
is
a
little
bit
more
like
we.
A
Yes,
that's
kind
of
like,
like
it's
a
similar
problem
to
the
problem
with
the
lurk
data,
which
is
also
like
it's
it's
kind
of
addressed
but,
like
everything
is,
is
a
field
element
and
like
it's
not
really
like.
It
is
hashes,
but
it's
a
field
element.
It's
a
hash
and
a
field
element
and
like
it's,
it
gets
tricky
and
it's
like
it's
yeah,
so
whether
he
gets
into
the
cryptographic
space
and
then
yeah.
A
It's
just
so
and
coming
from
there
something
that
paul's,
who
said,
which
I
kind
of
agree
agree
with,
is
like
he
says
that,
from
his
understanding
of
what
I
see
a
cid
is
supposed
to
do,
it
fits
totally
what
they
want
to
do,
but
the
problem
is
that
our
seids
don't
fit
or
like
yeah.
A
Basically,
the
format
which
you
were
choosing
doesn't
really
fit
in
it's
kind
of
interesting
that
they
really
have
credit
risk
pointers,
but
it
doesn't
fit
our
cid
model
quite
well,
so
yeah
we'll
see
yeah
so
for
me,
like
as
people,
are
sharing
their
thoughts.
So
one
thing
I'd
like
to
see
is
like,
I
also
see
the
power
of
content
addressing
and
what
I'd
really
like
to
see
is
like
yeah,
just
an
easier
way
to
like
build
your
applications
in
your
data
structures.
A
Let's
say
you
build
a
to-do
list
or
whatever,
and
you
can
just
make
it
in
a
content-addressed
way
and
it's
just
easy
and
then
you
get
basically
all
the
benefits
of
being
content
addressed
like
you
can
replicate
it
easily
and
it
can
address
it
easily
and
so
on,
but
you
don't
really
have
to
think
about
it.
Okay,
hopefully
like
to
me,
hopefully
ipld,
will
help
with
those
things.
E
Had
had
one
that
he
posted
on
the
channel
because
he
can't
get
zoomed
to
work
this
time,
but
we'll
endeavor
to
next
time.
D
E
Is
I'd
also
suggest
that
ipld
is
just
a
really
practical
implementation
of
the
promise
of
linked
open
data
and
there's
something
extremely
powerful
and
having
a
practical
implementation
of
something
as
complex
as
linked
data.
A
D
Yeah
and
on
that
point,
that's
one
of
the
one
of
the
things
that,
like
the
vision
for
ipld,
that
I
really
would
like
to
see
us
I
personally
would
like
to
pursue
is
the
is
being
able
to
have
a
greater
offering
of
data
structures
above
it.
So
you
know
a
hampton
is
our
workhorse,
but
we
really
do
need
a
lot
more
optionality
for
storing
data
that
can
build
towards,
so
people
can
really
use
their
content
address
data
as
a
database
that
suits
their
application.
D
D
You
know
the
version,
you
know
zero
or
version
one
of
go
version:
zero,
one
of
javascript,
it's
all
sort
of
mangy
and
not
very
happy
to
play
with,
but
really
getting
a
really
nice
interface,
where
you
can
just
take
this
piece
and
then
build
a
really
complex
data
database
type
thing
in
content
into
australia.
That
would
that
would
achieve
the
kind
of
vision
that
I
have
for
ipld.
A
And
there
was
also
in
that
chat.
There
was
a
question
on
where
to
submit
eurovision.
If
you
have
one
so
I
propose
so
in
the
ipld.
So
in
a
github
ipld
slash
ipod
repository,
we
have
a
subdirectory
called
notebook
where
we
store
things
called
exploration
reports,
but
it's
just
just
a
fancy
name
to
kind
of
like
do
you
explore
something?
It
could
even
be
a
vision,
and
you
just
want
to
put
it
somewhere
where
it
is
persisted
in.
You
can
link
to
it
and
people
can
discuss.
A
So
I
would
propose
making
a
pr
to
this
directory
and
then
yeah
have
it
there.
Yeah.
A
Yeah,
so
it's
like
yeah,
it's
just
open
for
everyone
and
just
like
so
they
won't
be
like.
So
I
wouldn't
expect
that
someone
would
re,
would
yeah
so
probably
just
be
merged,
basically
because
yeah,
it's
your
explanation,
cool.
B
Yeah,
I
have
some
ideas
coming
from
the
peer-to-peer
web
space
because,
like
one
thing
I
see
in
having
made
things
using
different
peer-to-peer
web
protocols
is
like
right
now.
A
lot
of
the
focus
is
on
reading
data
being
produced
by
somewhere
else
and
a
lot
of
the
data
isn't
just
these
like
really
plain
formats
like
files
or
pretty
much
files,
and
I
see
ipld
as
having
the
potential
to
have
a
lot
more
advanced
data
structures.
B
So,
for
example,
like
databases
where
you
can
have
index
data
where
people
can
quickly
traverse
through
an
arbitrary
data
set
and
just
quickly
download
just
what
they
need
and
so
applications
could
author
data
locally
and
publish
to
these
indexes
and
they
could
merge
other
people's
data
together.
So
I
see
it
as
a
way
to
kind
of
like
work
with
data
in
a
more
raw
way
than
what
bittorrent
or
ipfs
itself
can
offer
yeah,
because
files
are
great
but
they're
they're,
not
very
great
for
performance
when
you
have
really
complex
structures.
B
A
Thanks
all
right
anything
else
from
anyone,
I
need
to
check
the
notes.
E
If
people
are
down
to
talk
about
signatures
and
such
and
how
we
might
do
those
sorts
of
things,
I
I'd
be
interested.
But
if
that's
that's
not
what
the
crowd's
interested
in
then
no
worries.
E
E
When,
when
when
we
see
people
who
try
and
do
like
sign
data
that
they're
moving
around
or
that
they're
putting
as
ipld,
and
maybe
they
want
to
move
around
over
ipfs
or
store
on
filecoin
or
or
whatever,
I
think
sometimes
what
we
run
into
is
there's
like
there's
like
two
different
pieces
of
the
thing
one
is
and
it
sort
of
boils
it
seems
to
boil
down
to.
E
You
know
sort
of
deeper
in
the
ipld
layers.
It
needs
to
be
like
nope.
This
thing
wasn't
signed
properly,
reject
right,
maybe
that's
a
codec
or
something,
and
if
the
answer
is
like
no,
I'm
I'm
okay,
you
know
I'm
okay,
you
know
traversing
or
doing
all
sorts
of
things
with
this
data
that
is,
you
know,
was
not
signed
and
like
we'll
figure
out
somewhere
else
in
the
stock.
E
Where
we
do
this-
or
we
do
this,
like
validation
of,
is
this
the
thing
that
is
safe
right
and
that's
like
a
different
story,
and
that
might
be
like
one
avenue
where
we
start
to
like
pull
at
this,
like,
I
know
the
I
feel
the
docs.
Currently
some
people
like
it,
some
people
don't
take
sort
of
a
we're.
Gonna,
give
you
all
the
information
kind
of
stance
or
whenever
there's
like
a
tricky
problem
that
doesn't
like
assert.
This
is
the
way
to
solve
that
problem.
E
It
just
sort
of
lays
out
for
you
what
the
options
are.
If
we
were
going
to
continue
down
that
route
of
sort
of
laying
out
what
the
options
were.
This
feels
like
another
one
of
those
to
help
people
who
do
signatures
understand
like
which
of
these
behaviors.
Do
you
want,
but
I
think
also
there's
probably
a
good
argument
to
be
made
for
simplified,
or
you
know
less
for
those
who
don't
who
aren't
so
interested
in
all
of
the
optionality
like?
E
What's
the
basic
go-to's
here
we
have
the
same
thing
sort
of
in
the
ipfs
specs,
where
there's
probably
going
to
be
a
lot
of
specs
for
a
lot
of
things,
and
we
probably
want
to
have
a
subset
of
them.
That
are
the
you
know
you
just
want
to
get
going.
Do
abc,
as
opposed
to
here
are
the
1000
things
you
might
choose
to
implement.
If
you
want
to
do
all
of
them,.
D
I
I
had
something
similar
with
I.
I
had
basically
that
problem
when
I
was
helping
out
with
the
dag
jose
codec,
where
so
it
can,
it
can
do
all
of
the
things
with
signing.
E
D
And
it's,
and
it's
like
built
around
best
practice
like
the
jose
spec
around
the
jws
spec
around
signing
is,
is
very
sophisticated
because
it
does.
It
can
allow
all
the
different
algorithms
and
the
different
you
know
some
of
the
modern
modalities
of
signing,
but
that
leaves
you
with
this
problem
of
okay.
I
just
want
to
sign
some
stuff.
What
do
I
do?
D
What
is
the
best
practice?
What
can
I
actually
just
pick
off
the
shelf
and
put
in,
and
you
can
do
that
with
with
the
with
doug
jose,
but
I
actually
I
was
writing
an
example
of
of
how
to
do
it
and
and
one
and
go
in
one
in
javascript
so
that
you
could
produce
and
consume
the
same
data
and
and
coming
up
with
a
solution
that
worked
in
both
was.
D
I
can't
remember
whether
I
actually
got
to
the
got
to
there
in
the
end,
but
it
was
really
difficult
because
both
both
languages,
the
the
tool
set
available
in
both
languages,
had
chosen
different
options
for
their.
You
know
best
practice
and
the
things
they
supported.
D
So
even
that
was
difficult
because
of
the
option.
Space
was
so
huge
and
I
think
that's
just
that.
That's
that's
sort
of
a
one
of
these
problems
with
cryptography
is
we
we
say
this
is.
This
is
a
very
serious
problem,
so
we're
gonna
open
up
the
optionality
and
we're
going
to
write
lots
about
it
and
make
it
buyer.
D
D
In
my
you
know,
tls
config
in
my
web
server
I
don't
know
yeah,
it
seems
like
a
pretty
generic
problem
and
if-
and
you
know,
if
we're
brave
we'd
pick
it
off
and
say,
he's
he's
the
way
you
should
do
it
and
maybe
he's
a
backup
way
in
case
that
one
breaks.
E
I
feel
like
well,
I
don't
know
if
it's
quite
the
same
thing,
but
it's
kind
of
like
if
the
if
the
back
end
underneath
everything
is,
is
sort
of
generic
enough
that
you
can.
You
can
plug
in
the
different
things,
then
it
should
enable
you
to
better.
Tell
someone
like
here
is
a
recommended
way
to
do
something,
because,
if
you're
wrong,
they
have
more
outs
as
opposed
to.
E
If
you
you
were
sort
of
hard-coding
everything
you'd
have
to
tell
them
like
here
are
all
of
the
various
things
you
should
be
very
careful
of
before
you
hard
code,
which
is
like
the
best
hash
function
whereas
like
if
you
didn't
care
like,
if
you
had
the
ability
to
choose,
you
could
be
like.
Well,
I
don't
know
just
use
shatsu,
it's
probably
fine,
right
and,
and
let
people
like,
oh
okay,
turns
out
shot
two
sucks.
Blake
three
is
the
new
thing,
all
right.
A
All
right
so
last
call
for
agenda
items
or
anything
else,
all
right,
then
yeah,
but
also,
I
always
forget
to
mention
that
we
now
close
the
live
streamings.
But
if
you
want
to
hang
out,
we
sometimes
discuss
also
off-topic
things
or
just
hang
out
so
feel
free
to
hang
out
even
after
I
close
the
meeting
and
close
the
live
stream
all
right,
but
for
the
live
stream.
It's
enough
for
today.
So
yeah
see
you
all
in
two
weeks
again
goodbye.