►
From YouTube: 🖧 IPLD Every-two-weeks Sync 🙌🏽 2022-10-11
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
Welcome
everyone
to
this
week's
ipld
sync
meeting:
it's
October,
the
10th
2022
and
it's
every
two
weeks.
We
go
over
the
stuff
that
people
have
worked
on
and
then
discuss
any
open
engine
items
or
answer
questions
or
yeah
discuss
any
hyperly
related
things.
So,
let's
see
oh
I,
yeah
I
have
some
update.
That
is
written
down,
which
I
will
just
quickly
read
out,
as
the
person
mentioned.
So
Steve
has
an
update,
but
he
can't
be
here
so.
A
Yes,
so
yeah,
that's
also
like
an
important
thing.
So
in
about
two
weeks
two
to
three
weeks,
there
is
a
big
event
in
Lisbon
for
ipfs
called
ipfscam,
and
there
are
also
there's
obviously
room
for
ipld
and
yeah,
and
Steve
here
says
that
there
should
probably
be
also
a
place
to
do
some
sessions
about
Italy
and
he's
looking
for
people
kind
of
driving
this
and
making
sure
there
are
sessions.
So
if
anyone
volunteers
once
I
get
into
it
would
be
great.
A
Yeah
so
yeah,
so
it
would
be
great
to
have
some
roadmap
for
ipld
what
people
want
and
want
to
see
or
want
to
work
on
or
we'll
work
on,
perhaps
even
before
the
event
and
yeah
and
also
Juan
would
be
happy
to
meet
with
people
and
yeah
yeah,
even
yeah
before
the
event
or
during
the
event,
to
check
their
on
the
timelines
and
thought
with
items
or
ideas
we
have.
So
if
anyone
has
ideas,
yeah,
probably.
A
Yeah,
so
the
question
is
who
is
driving
this
because
because
like
we
can
do
it
through
GitHub,
I
guess
but
yeah?
So
if
anyone's
watching
this
feel
free
to
catch
us
on
the
the
chat
channels
like
on
Matrix,
Discord
or
select,
I,
think
everything
is
bridged
and
also
yeah.
Just
on
the
github.com
iPod
slash
I
will
produce
the
iPod
repo
feel
free
to
open
issues,
and
then
we
will
like
yeah,
go
from
there.
C
A
Yep
yep
yeah,
it's
good
and
then
also
like
people
could
also
like
even
then
comment,
even
so
after
this
meeting,
the
meeting
loads
are
up
totally
disappears,
also
feel
free
to
comment
there
them
all
right.
Yes,
so
having
said,
or
this
get
me
back
to
the
other
things,
so
yeah
I
have
a
petite.
So
next
on
my
list
is
move.
D
A
Yeah
we
can
also
just
like
go
on
with
Rod.
Perhaps
if
you
are
not
ready
yet.
C
Really
enough
I
didn't
actually
come
as
prepared
as
I
wanted
to
to
do
this
because
there's
a
bunch
of
other
stuff.
It's
it's
not
it's
again.
It's
always
some
minor
things
that
I've
been
chasing
around,
but
I've
got
the
two
main
major-ish
things
in
in
the
notes
that
that
I've
been
working
on
one
is
go
Michael
daggers
at
0.8
release
out.
That
is
a
fairly
important
update.
There's
there's
multiple
situations
where
you
can
put
a
Proto
node
into
a
state
that
will
Panic
and
yeah.
C
C
So
there's
sort
of
lots
of
you
know
just
protection
around
it
really.
So
that's
0.8
is
out.
That
is
a
strongly
recommended
update
and
the
other
thing
is
Chase.
Multi
formats
will
finally
have
a
release
today,
if
all
goes
well,
but
it
seems
to
be
going
well.
C
We've
been
working
on
this
for
a
long
time,
so
I've
put
in
a
bunch
of
work.
A
couple
of
months
ago
to
do
to
start
the
esm.
Only
migration
for
that
and
gazala
has
been
working
on
typescript
interface
for
cids,
for
some
time
really
wanted
to
get
that
in
and
we're
finally
getting
that
over
line
and
we're
calling
that
interface
link
rather
than
CID.
C
So
we
have
so
you
can
just
use
that
as
your
interface,
where
you
accept
cids,
but
don't
necessarily
need
the
concrete
version
so
that
that
should
make
both
esm
only
and
that
interface
should
make
JavaScript
code
look
a
little
bit
different
going
forward,
but
the
next
step
after
release
of
this,
which
will
be
version
15,
is
just
going
to
be
the
flow
on
impact
of
having
an
esm,
only
release
that
we
have
to
absorb
everywhere
else.
C
So
there's
going
to
be
a
lot
more
esm,
upgrading
throughout
our
stack,
so
the
Codex
and
all
the
pieces
that
consume
multi-formats.
Now
that
are
trying
to
do
common
JS
as
well,
are
going
to
have
to
be
changed
to
this
was
sort
of
you
know
about
to
press
the
button
and
get
notifications
from
depend
about
that.
Stuff
is
all
broken.
So
so
that's
that's
more
work
to
go
anyway.
That's
that
will
be
a
relief
to
get
that
out
so
they're.
The
two
main
things
from
me.
A
Thanks
I
see
that
moth
has
left
the
room
so.
C
I
have
I
have
one
more
now
that
Alexandra's
here
he's
reminded
me.
His
presence
has
reminded
me:
we
we
have
so
we
have
the
wonderful
contribution
of
Julia.
C
Let
me
just
find
this
issue,
so
Julia
is
doing
a
ux
review
of
ipld.io
and
I'm.
Gonna
put
these
notes,
but
I'll
put
in
the
chat
just
for
now
and
so
she's
going
over,
and
we've
asked
her
to
have
a
look
at
ideas
for
improving
both
the
design
like
design
is.
One
is
the
big
thing
we
want,
and
also
just
ux
from
a
user
perspective
coming
in
and
how
people
interact
with
it
and
so
we're
having
a
very
active
conversation.
C
We
have
a
so
there's
the
issue
there
she's
working
from
a
figma
file,
and
if
anybody
wants
access
to
that,
you
can
just
drop
a
note
in
that
issue
and
we
can
give
you
access.
I
think
you've
got
to
put
your
email
address.
We
do
have
a
slack
Channel,
but
I
think
it's
private.
We
need
to
make
it
public
for
this.
It's
not
we're,
not
it's
not
rapid
and
we
don't
actually
have
anyone
assigned
specifically
to
do
the
implementation
work.
So
this
is
sort
of
a
slow
roll
thing
to
be
just
getting.
C
The
ball
started
on
the
the
review
stuff,
so
yeah,
that's
cool,
be
nice
to
get
a
a
fresh
bit
of
paint
on
there
anyway.
That's
that
issue,
number
240
in
the
ipld
repo
and
again
there's
a
slack
Channel
and
I'll
in
in
filecoin
slack
and
wherever
that's
bridge
to
Discord
and
other
places.
I'll
put
a
note
about
that
channel
when
we
get
it
made
public
and
you
can
join
in
if
anyone's
interested
foreign.
E
Thank
goodness
yeah,
so
I've
been
working
more
on
specs
and
stuff.
E
Gateways
and
also
an
IPL
ipld
URL
scheme,
so
I've
been
kind
of
talking
about
it
for
a
while,
but
I've
added
some
more
details
to
the
spec
based
on
the
experiments
I've
run
so
far
and
I've
also
been
working
on
integrating
it
with
the
agricore
browser.
I
was
actually
wondering
if
I
could
how
to
do
a
demo,
real
quick.
If
people
are
interested.
A
E
E
The
an
ipld
URL,
so
what
I
can
do
now
is
kind
of
look
at
what
that
structure
looks
like
in
dag
Json,
one
of
the
features
kind
of
requests
data
to
be
sent
to
you
in
a
different
format
than
what
will
happen.
E
D
A
In
the
in
the
oh
and
the
okay
and
the
web
developer
tools,
okay,
okay,
he's
gone
so
okay
anyway,
so
all
right,
then
we
just
I
guess
we
just
go
on
with
people
on
the
list.
Okay,.
C
You're
a
little
bit
right,
buddy
we
saw
we
saw
enough
of
that
to
make
some
sense
of
it,
but
it
was
a
little
bit
choppy
dang,
okay,.
E
E
For
optimization,
but
cool
thing
is
that
this
ipld
Handler
and
the
ability
to
have.
E
So
it
says
have
like
a
large
hint
that
you
want
to
just
manually
trench
through.
You
can
make
use
of
Records
protocol
handlers.
E
C
E
C
Question
I
do
have
questions
about
codex
because
when
you
were
uploading
that
hello
world
thing
did
that
just
get
encoded
as
a
a
rule
it
could
like.
Well,
there
was
no
codec
information
there,
but
in
yet
you
could
render
it.
What
was
it
encoded.
E
Yeah
so
I
encoded
it
or
when
you
post
to
the
ipfs
protocol
handlers
in
agricor.
It's
someone
should
write
a
book
Gateway
option
in
kubo's
Gateway,
where
you
can
add
arbitrary
bytes
and
when
it
gets
back
the
URL
it
sniffs
the
file
extension
to
get
a
mime
type,
so
there
I
posted
to
example.html,
and
so
when
I
copied
the
resulting
ipfs
link.
The
protocol
Handler
noted
that
is
ml
encoding.
So
it's
at
the
content
type
to
be
text
HTML
with
charset
utf-8.
E
E
Yeah
so
yeah,
so
that's
for
ipfs,
however,
with
iplt
when
you're
uploading,
there
is
a
post
Handler
for
ipld,
but
when
you're
uploading
it
it
expects
you
to
update
or
upload
data
in
the
ipld
Codex.
So
if
you
specify
well.
E
Go
to
the
IPL
protocol
hamster
you
can
specify
the
encoding
that
your
content
is
in
right
and
then
you
can
also
specify
a
different
format
for
it
to
save.
In
so,
I
could
use
a
thumb
post
data
to
the
ipld
node,
but
then
I
could
give
it
a
little
hint
saying
that
I
want
you
to
save
this
as
dag
seabort.
So
applications
can
use
codecs
that
they
don't
have
to
do
extra
Imports
for
while
still
saving
stuff
in
the
most
efficient
way
possible,
which
I
think
is
a
useful
distinction.
C
E
Yep
exactly
which
is
kind
of
exposing
it
in
a
Webby
way
for
I
guess
most
web
depths,
but
also
this
is
useful
if
you're
using
curl
as
your
main
interface
yeah.
E
Another
thing
I've
been
working
on
is
working
off
of
what
Steve
mentioned
about
people's
roadmaps
for
ipld,
so
I'm,
putting
together
a
large
blog
post
of
all
of
the
things,
I
think
we
could
do
with
ipld
to
make
it
more
of
it
more
accessible
to
people
and
kind
of
position
it
within
other
things
that
are
going
on,
like
wnfs,
iro
and
work
on
ipvm,
as
well
as
different
new
data
structures
that
are
coming
out
like
trolley
trees
and
the
stuff
Michael's
working
at
dag
house
for
verifiable
queries
in
ucans.
E
So
I'm,
probably
because
there's
something
particular
we're
going
to
release
that
this
week.
For
folks
to
talk
about
yeah
and
I.
Think
that's
all
I've
really
got
next
I'm
going
to
be
working
off
of
what
we
did
in
multi-formats
to
start
migrating
more
of
the
libraries
to
esm,
which
should
be
fun
and
less
painful.
A
E
Yeah
totally
we
have
weekly
teammate
meetings
for
the
ipld
team
on
Tuesdays,
so
ideally
either
today
or
early
tomorrow
or
we'll
get
to
it
as
a
team
next
week,
which
is
posted
in
the
chat.
So
we
can
discuss.
D
Okay,
so
I
do
not
have
too
many
things
to
update,
because
I
have
graduated
mostly
into
being
an
iPod
using
it
so
digging
around
in
the
libraries
of
the
corbetts,
but
I
would
like
to
say
probably
at
the
ipfs
camp,
that's
coming
up
in
Lisbon
at
the
end
of
October,
if
you
haven't
heard
of
it
yet
it's
a
thing:
go
look
for
the
website,
I!
Think
it's
2022.mypfs.k
or
something
it'll
be
fun.
D
It'll,
be
lots
of
things
and
you'll
probably
hear
me
talk
a
little
bit
about
iPod
data
structures
in
applications.
You
know
in
some
of
the
applications
I'm
personally
looking
at
are
like
how
to
version
data,
how
to
map
names
onto
half
sheets
of
stuff?
How
to
do
I.
Don't
know
package
management
descriptions
stuff
like
that,
but
it's
all
going
to
be
just
iPod
inactory,
so
it
will
be
at
least
nothing
I'm
going
to
talk
about
is
going
to
be
IPL.
Guts
they'll
just
be
like.
D
How
do
we
use
this
to
solve
problems
so
I
hope,
that'll
be
fun
and
many
other
people
will
talk
about
many
other
things,
but
I
have
no
idea
whatever
so
go.
Look
at
the
website.
D
There's
a
person
named
dust
mop
on
GitHub
who's,
still
hacking
away
on
the
go
datalark
repo
in
the
iPod
GitHub
org,
which
is
bringing
ipld
bindings
into
starlock
if
you're
using
The,
gulling,
starlock
Interpreter
and
the
latest
work
there
is
we're
bringing
all
of
support
for
all
of
the
possible
mutation
syntaxes
in
starlock,
which
is
edit
and
python,
does
so
like
you
know
we
reach
into
it
language,
assigned
by
array,
index
and
stuff
like
that.
D
We
had
not
supported
all
of
the
syntaxes
for
mutations
until
recently
in
the
last
couple
of
commits
Landing
in
that
repo
are
now
supporting
mutation.
One
word
freely.
This
is
interesting
in
part,
because
the
go
iPod
libraries
that
it's
building
on
don't
support
mutation
very
much
you're,
very
aggressively
copy
on
right
sort
of
algorithms.
You
always
have
to
construct
a
new
one,
so
the
datalark
library
is
building
what
the
dust
mop
calls
mutation
sidecars.
So
there's
a
object
memory
that
you
interact
with
from
your
python
Starlight
service
syntax.
D
So
that
has
a
pointed
to
the
ipld
data
that
is
frozen
already
and
according
to
all
of
the
mutations
that
are
just
tracks,
and
so
you
can
use
that
to
continue
Community
mutations
or
to
read
back
the
mutated
data
and
as
soon
as
you
call
the
freeze
operand
in
startup
or
trying
to
get
iPod
Library
data
back
up,
it
applies
all
the
mutations
produces
the
copy
automate
copy
to
now.
It's
kind
of
it's
kind
of
slick,
kind,
of
cool,
I
hope
this
skills,
like
The
Best
of
Both,
Worlds
sort
of
related.
D
I
think
that's
the
end
of
the
updates
that
I
should
share
and
I'm
dragging
somebody
else
on.
The
screen
is
maybe
working
on
constant
addressable
data
structures
and
file
systems,
but
I
don't
know
if
he'll
want
to
spend
any
time
on
camera.
B
Yeah
I
mean
I'm
fluffy
on
the
internet,
I've
been
playing
around
a
bit
with
ipld
in
general,
marking
three
structures
to
represent
artifacts,
build
out
effects
from
from
package
managers
and
build
systems
and
to
see
how
to
distribute
them
and
make
use
of.
B
We
sharing
of
certain
Parts
in
these
artifacts
by
using
component
address.
Stashing
and
I
am
I'm
just
playing
around
with
my
pld
and
seeing
how
I
can
make
it
work
for
that
specific
use
case
to
potentially
distribute
yeah
these
artifacts
through
ipld
through
our
PFS
in
here.
B
It's
still
very,
very
early,
very
work
in
progress,
but
but
it's
exciting
and
I
yeah.
That's
all
I
can
say.
A
Cool
things,
so,
let's
see
all
right
does
anyone
else
wants
to
share
anything
or
has
any
updates
or
questions.
A
Yeah
then,
okay,
so
I
probably
only
have
I
guess.
One
item
because,
like
what
I
really
want
to
see
for
years
is
that
there
is
some
JavaScript
version
of
ipld
which
is
like
ipfs,
but
without
including
xfs.
So
it's
just
the
or
just,
but
it's
it's
basically
ipld
and
like
the
networking
and
pops
up
and
whatever
like
everything.
But
okay,
oh
I,
see
in
the
third
room
that
it's
already
a
thing
or
it
becomes
a
thing.
E
Yeah,
so
part
of
the
road
mapping
that
I've
been
planning
is
exposing
a
higher
level
API
to
do
all
of
the
fancy
ipld
things
so
right
now
we
have
traversal,
we
have
ADLs
and
data
model
and
in
go
ipld
Prime,
it's
put
behind
a
bunch
of
useful
typed
interfaces
that
are
divorced
from
actual
peer-to-peer
file,
transfer
or
data
transfer,
and
in
JavaScript
we
have
like
a
dozen
libraries
that
are
all
doing
some
ipld
stuff,
and
most
of
them
are
also
pretty
separate
from
the
peer-to-peer
all
in
one
use
case,
I've
been
working
on
this
other
thing:
I'm
calling
JS
ipld
result
which
might
be
reading
to
JSI
pld
system,
which
is
kind
of
an
out
of
the
box.
E
I,
don't
know
why
Zoom
hates
me
this
is
awful
anyways,
but
to
expose
ipld,
URLs
and
ipld
lenses
as
a
first
class
interface
for
developers
to
use
and
I
want
to
make
it
easy
to
just
import
a
thing
and
be
like
I
want
to
read
from
my
pld
URLs
I
want
to
apply
lenses
to
some
data.
E
I
want
to
mutate
existing
data
with
patches
and
have
one
place
where
we
have
all
of
these
nice
high
level
features
and
an
out
of
the
box
implementation
for
how
data
is
loaded
and
saved,
which
can
be
changed
for
more
advanced
use.
Cases
like
where
you
don't
want
to
include
slippy2p,
but
just
have
something
out
of
the
box
for
people
to
start
playing
with
I'm,
also
hoping
to
get
some
of
this
stuff
into
foreign.
E
With
the
itld
or
with
the
Kubo
Gateway
or
some
other
gateways
like
Ira
and
that'll,
also
give
us
like
another
obvious
place
for
using
this
stuff.
So
if
we
can
get
ipld
URLs
in
a
spec
and
into
iro,
then
we
can
get
some
usable
high-level
interfaces
for
ipld
that
aren't
unixfs,
that
are
a
break
from
Legacy
code
that
are
more
clean
and
using
higher
level
features.
So
that's
something
that
I'm
actively
working
on
this
year.
A
Things
and
then
put
them
yeah
somewhere
and
then
it
they
get
I,
don't
know,
I
get
a
pub
sub
event
to
somewhere
else,
and
so
on
so
really
like
like
yeah,
basically
the
local
first
thing,
and
then
it
will
automatically
somehow
distribute
it
somewhere.
This
is
what
I'm
I'm,
after
basically
without
having.
A
E
A
A
Oh,
it
is
the
plan.
So
what
do
you
have
things
or
do
you
plan
to
just
share
them
directly
with
move,
then.
C
Yeah
I
I
have
I,
have
trouble
when
thinking
about
Road
mapping
I'm
just
I'm
in
this
place
that
I
think
others
have
been
in
where
you're
in
the
weeds
too
much
and
it's
hard
to
look
up
and
see.
What's
ahead,
you
know
we
have
this
project
board
for
ipld.
That
is
really
large.
That
I'd
really
like
to
get
made
small
and
I
just
haven't,
haven't
like
I.
C
Don't
have
the
time
to
make
to
squash
that
board
I'd
really
like
to
be
able
to
squash
it
so
that
we
can
get
on
top
of
things
and
then
feel
like
we
can
build
some
to
build
new
stuff.
So
you
know
I'm
actually
happy
to
have
the
most
able
to
think
about.
You
know
future
type
stuff
for
particularly
JavaScript
stack.
C
I
really
would
love
to
see
more
data
structure
work.
That's
a
long,
long-standing
desire
for
me
and
I.
Think
that's
I
think
that's
going
to
be
the
strength
of
ipld
as
all
this
stuff.
Other
stuff
happens
around
it.
C
If,
if
we
can
be
supporting
the
building
of
Novel
data
structures,
then
that's
I
think
that's
one
of
the
biggest
things
we
can
do
vocal.
You
pointed
me
to
some
interesting
stuff
in
the
rust
the
rust
fbm
work
recently,
where
they
were
playing
with
the
the
Hampton
implementation
and
using
identity
hashes
to
get
ordered
entries
in
the
Hampton,
which
is
at
the
same
time,
terrifying,
but
also
novel
and
interesting,
but
sort
of
pulling
in
that
work
and
documenting
it
and
experimenting
with
it
and
and
socializing.
A
All
right
on
the
chat
there
was
a
project
called
a
graphology
mentioned
that
I
haven't
heard
of
so.
If
anyone
wants
to
check
it
out,
it's
obviously
about
graphs
and
JavaScript
yeah
I
haven't
checked
out,
I
can't
say
anything
about
it.
B
Just
I
just
thought
about
it
and
I
find
it
very
interesting,
the
the
thinking
behind
it,
the
person
that
started
the
project
started
I,
guess
like
five
years
ago
or
so
and
did
some
presentations
around
it
and
it's
it
seems
very
heavily
like
inspired
in
the.
B
It
seems
to
have
a
very
heavy
thought
data
structure
back
end
and
why
not
and
I
was
wondering
if
any
of
you
knew
about
it
already
and,
and
maybe
there's
I
was
I
was
thinking
if,
if
maybe
we
can
start
thinking
of
how
we
can
better
integrate
with
other
libraries,
other
implementations
and
and
why
not
around
data
structures
around
graphs
and
maybe
maybe
an
enabling
or
facilitating
Integrations
to
use
ipld
as
as
part
of
some
of
the
the
layers,
but
not
not
on
on
the
so
high-tech,
like
blockchain
world.
B
So
we
could
maybe
use
other
Market
markets
as
as
a
source
of
talent,
the
source
of
knowledge
of
sort
of,
maybe
funding.
So
as
I
started
wondering
a
bit
about
that.
C
Was
that
this
my
thoughts
just
quickly
having
a
look
at
this
graphology
thing?
So
we
definitely
have
questions
about
how
to
have
a
better
graph
interface
from
JavaScript.
C
We,
we
know
what
that
looks
like
in
go,
but
JavaScript
presents
new
challenges
where
we
can't
just
put
those
same
Concepts
right
across
so
this.
This
does
look
interesting
in
at
least
in
suggesting
some
ways
forward,
and
maybe
maybe
what
we
need
to
do
in
JavaScript
with
this
is
rather
than
trying
to
copy
the
the
go
patterns
directly
is
has
come
up
with
entirely
new
patterns
for
manipulating
and
maintaining
graphs,
while
also
being
true
to
to
the
viple
stack,
because
we
want
to
retain.
C
We
want
to
the
ideal
is
that
we
we
get
some
kind
of
unified
place
where
we
we
have
this
notion
of
selectors
and
ADLs,
that
you
can
layer,
but
it
has
to
it,
has
to
work
sensibly
in
each
of
the
languages.
We
do
it
in
and
that's
the
biggest
challenge
we
have
I
think.
E
At
risk
of
disconnecting
myself
again,
I've
also
been
thinking
about
graphs
and
ipld,
but
from
the
context
of
graph
databases
and
rdf,
which
is
used
for
stuff,
like
Json
LD,
so
there's
ways
of
representing
strongly
typed
graphs
of
information
in
the
rdf
space,
which
I
think
work
decently.
Well,
with
content
addressing,
we
still
need
to
figure
out
what
mutation
would
look
like
in
these
spaces,
but
there
are
also
query
languages
for
this,
like
sparkle,
which
are
made
for
querying
arbitrary
graphs
and
there's
some
other
I.
E
Think
Gremlin
is
another
graph
query
language,
but
in
the
kind
of
like
graph
database
space,
there's
like
a
bunch
of
approaches
to
storing
graphs
and
I'm
hoping
to
partner
with
some
groups
that
do
rdf,
like
the
authors
of
activity
Pub
or,
if
you've
seen
them
around.
Bengo
does
lots
of
cool
stuff
around
dids
and
stuff,
and
so
that's
kind
of
more.
E
Where
I
was
thinking
where
we
standardize
on
the
data
and
standardize
on
query
languages
rather
than
having
something
in
ipld
itself,
because
looking
at
this
graphology
graph,
it
is
not
everything
that
it
can
do.
Will
work
in
ipld
just
due
to
the
way
it
works
and
the
way
its
mutability
works
so
trying
to
glue
ipld
into
this
would
be
a
lot
more
difficult
than
just
having
proper
graphs
built
on
top
of
ipld.
A
All
right,
thank
you
anything
else.
People
want
to
talk
about.
A
Else
I
would
close
the
live
stream
other
than
the
live
stream.
There's
also
the
after
party
for
things
that
people
don't
want
to
see
a
publicly
in
the
Stream
or
just
talking
about
off-topic
things
yeah
all
right,
then
thanks
everyone
for
attending.
It
was
good
to
see
so
many
people
and
oh
by
the
way,
I
think
we
should
like
I
propose.
A
A
Yeah
so
yeah,
so
for
everyone
watching
we
skip
this
meeting
next
week,
so
we
see
as
all
again
in
four
weeks
and
they're,
probably
with
lots
of
news,
because
in
between
was
the
ipfs
camp
and
yeah
and
as
we
see
us
in
four
weeks,
also
the
note
that
this
meeting
stays
on
UTC
time,
so
it
won't
shift.
Even
if
your
time
zone
changes,
this
meeting
will
be
at
in
21
hours.
A
UTC
all
right
see
you
all
in
four
weeks,
then
goodbye
everyone.