►
From YouTube: IPFS All Hands 🙌🏽 📞 Jan 15, 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).
B
B
C
And
at
this
point
we've
you
finish
up
the
RFC,
I,
guess:
okay
at
this
problem,
the
motivation
behind
that
to
get
a
little
bit
of
background
is
for
number
one:
supporting
files,
they're
too
big
for
a
single
IP,
offense
Ruffo
and
number
two
being
able
to
support
the
basic
functionality
for
more
sophisticated
fault,
tolerant
applications.
So
at
this
point
the
RFC
is
pretty
like
it's
premature
and
we
would
like
comments
from
other
people.
C
The
two
major
groups
that
we'd
like
to
hear
back
from
are
people
with
in-depth
knowledge
of
go
ipfs,
specifically
able
to
know
a
lot
about
importers,
decks
garbage
collection
and
then
the
second
group.
While
we
really
like
feedback
from
our
people
with
more
of
a
user
mind,
so
people
that
are
like
using
ipfs
profiles
and.
D
B
B
Good
question
explains
mine
I.
Had
we
had
like
a
small
wing
on
the
browser
extension
front,
yeah
yeah,
a
big
one.
A
D
A
A
A
D
E
E
E
E
E
E
C
C
E
A
Alright,
thank
you
so
much
for
the
demo
I've
been
following
the
developments
on
that
trust
for
a
while
and
if
I
understand
correctly,
mainly
what
this
enables
is
to
generate
certificates
on
the
fly
so
that
browser
loads
are
basically
the
browser.
Runtime
doesn't
complain
when
we
try
to
dial
to
an
on
domain
non
pls
notes
from
an
HTTP
server
domain
right.
A
E
And
it
also
provides
DNS
but
I
had
to
change
the
path
words
generate
certificates,
because
that
would
require
on
public
key
infrastructure
and
getting
improved
as
a
certificate
authority
and
that's
a
bit
expensive.
That's
why
I'm
using
less
and
could
quite
cut
certificates
instead,
I
could
remove
the
common
name
and
only
if
I
can't
listen
to
the
kids.
So
nobody
could
smoke
the
website
and
then
it
would
be
safe
because
it's
encrypted
anyway,
mm-hmm.
A
E
A
E
A
Because,
like
if
they
know
these
are
my
public
IP,
then
we
can
just
direct
connect
because
we
went
over
the
hump
that
the
browser
is
set
for
us,
which
is,
it
has
to
be
at
ssl/tls,
enabled
endpoint.
That
is
also
using
anyway,
but
you
still
need
to
I
pour
out
of
the
non
public
IP
listening
notes.
Yes,.
D
A
A
Sorry
I
didn't
understand.
Yeah
I,
actually,
I'm,
not
aware
if,
if
I
have
a
process
running
on
my
local
machine
and
if
I
set
up
dynamic
DNS
for
that
process,
so
basically
I
applied
the
domain
name.
Every
time.
I
acted
changes
of
my
local
machine
because
it's
running
on
my
house
a
lot
on
public
you
all
about
the
sitter
doesn't
have
a
static.
Ip
can
I
set
up
as
SSL
certificate
for
that.
E
A
E
A
This
is
pretty
cool,
so
how
easy
it
is
to
set
up
this.
Do
that
sorry,
I
didn't
get
the
last
word.
How
can
users
try
node
for
us
today?
Do
they
have
to
have
a
custom
version
of
we
live
here.
D
E
F
G
I
think
so
you're
using
let's
encrypt
to
actually
just
as
the
certificate
authority,
so
you're
he's
creating
a
dynamic,
DNS
and,
and
so
it
still
needs
to
be
signed
by
a
central
authority
in
order
for
it
to
be
trusted
so
and
I
think
that's
going
to
do.
B's
question
is
like
how
are
you
getting
an
external
node
in
order
to
validate
the
IP
at
or
at
least
the
external
facing
IP
address
to
sign
a
certificate
I'm
just.
E
E
D
E
E
D
E
G
E
G
D
My
point
is:
if
you
already
have
wild
card
certificates,
you
don't
have
to
have
people
register
domains
you
can
just
have
them,
use
their
IP
address
dot
your
top-level
domain,
in
which
case
the
wild
card,
to
be
able
work
for
that.
So
the
people
just
use
the
domain
they
want,
because
that's
like
that's
the
domain
that
their
own
traffic
strategy
so
make
sense.
Like
you
make
it
to
someone,
looks
up
IP
address
dot
domain
name.
They
get
that
IP
address.
A
So
sorry
for
for
jumping
in
Stephen,
so
it
feels
like
we
there's
a
lot
of
questions
here
and
that
we
should
follow
up
on
this.
Perhaps
in
another,
medium
I
have
to
heat
a
tissue
or
I
get
a
triple
matchy.
Is
there
a
ripple
where
people
can
go
to
us?
Sorry,
shoo.
E
Yes
right
and
if
you
do
not
trust
repo
questions
can
be
asked
and
about
the
part
with
the
maintenance
they're
getting
but
never
Trevor
domain
name,
but
everything
that
matches
to
Whitecap
could
be
used
as
a
domain
name,
but
to
keep
them
unique.
I'm,
hashing,
pure
ID,
so
that
nobody
can
just
use
the
domain
name
of
that
knowledge.
All.
A
A
B
B
It
does
not
work
the
hack
that
enables
us
to
support
those
protocols
works
only
on
desktop
so
start
with
Firefox
59
will
have
kinda
native
protocol.
Still
the
origin
stuff
will
not
be
solved
like
the
way
the
origins
were
calculated
will
still
work
like
for
any
regular
site,
but
still
it's
a
step
in
right
direction.
We
won't
have
to
use
prefixed
protocols
anywhere
at
least
feel
under
Firefox,
5
and
another
item,
for
my
end
is
like
quick
summary
of
UX
or
GUI
efforts
when
it
comes
to
IDF
s.
B
It's
mostly
summary
of
current
developments
around
browser
extensions,
but
we
also
discuss
and
push
some
things
like
integration
with
brave
browser
which
enables
us
to
support
much
more
than
we
can
in
Firefox.
So
if
anyone
is
interested
in
current
status,
snapshot,
there's
a
short
comment,
I
think
as
a
tldr,
and
if
anyone
is
interested
in
user
experience
or
it's
not
like,
if
someone
is
interested
in
in
user
experience
as
user
experience
expert
or
maybe
you
as
a
user,
we
would
appreciate
some
feedback
for
two.
B
Two
efforts
we
are
pushing
currently
one
is
to
flesh
out
user
journey,
especially
the
initial
one
onboarding.
So
if
anyone
has
any
ideas
how
this
sampling
could
be
improved,
we
already
have
a
working
document.
If
you
don't
have
access
to
that
document,
please
request.
We
will
provide
you
access.
What
we
want
to
do
is
to
cover
as
much
as
possible
different
ways
we
can
introduce
user
to
ipfs
and
which
we
want
to
do
is
to
create
one
very
easy
journey
for
that
user,
and
we
wanted
to
provide
user
with
good
examples.
Why
ipfs?
B
It
is
useful
to
non-technical
user.
We
think
we
can't
provide
some
added
value
for
that
and
we
want
to
design
entire
journey,
starting
with
landing
on
the
idea
first
I/o
and
going
to
getting
static
instructions.
So
that's
one
thing:
we
appreciate
some
feedback
and
another
one
is
we
have
initial
draft
of
ipfs
brand
book
guidelines?
It's
like
initial
document
that
will
be
used
for
static
conversation
about
how
we
want
visual
sight
of
our
application,
so
that
would
be
a
browser
extension
ipfs
desktop,
which
was
called
idea.
B
Fest
action
before
probably
web
UI
will
also
be
redesigned
to
follow
this
one
visual
style
guide
and
this
brand
book
is
a
first
step
in
that
direction.
We
wants
to
like
establish
initial
the
common
language,
common
vocabulary
for
creating
user
interfaces
and,
if
anything,
looks
weird
or
maybe,
if
you
want
to
request
some
clarification
or
guidelines
for
specific
use
case
in
application,
you
have
in
mind
it
can
be
an
imaginary
application.
You
can
provide
some
feedback
there
and
yeah.
That's
that's
all
from
my
end
and
now
I
think
it
will
be
okey
arse
and
much.
F
Just
letting
everyone
know
that
there
is
so,
the
working
groups
are
still
working
on
their
okie
hours
and
they're
gonna
be
firmed
up
this
week,
so
they're
already,
they
already
have
drafts
put
together
and
then
we'll
be
reviewing
them.
So
they're
still
subject
to
change.
But
if
you
have
comments
that
you'd
like
to
put
in
the
now
is
the
time
because
okay,
ours
get
seals
about
a
week
from
now
make
sure
to
get
locked
in
stone
and
then
those
are
the
okay
okay
recorders.
So
we.
F
Them
at
the
end
of
the
court,
you
know
I'll
put
the
link
to
the
spreadsheet
in
here
in
a
moment.
So
it's
just
like
a
PSA
for
those
who
who
aren't
already
following
along
with
you,
okay,.