►
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
Hi,
I'm
melanie
everyone,
I'm
working
on
the
fpm,
but
I
made
this
demo
for
paris
p2p
a
couple
months
ago
from
my
launchpad
project.
I
didn't
think
it'd
be
that
interesting,
but
people
kept
saying
it'd
be
really
interesting.
So
here
it
is
it's
our
rust
lip
pier
running
in
webassembly
in
the
browser.
A
So
on
the
right
we
have
just
like
a
compiled
server.
That's
just
like
normal
lib
p2p
on
rust
and
on
the
left.
We
have
the
browser
with
really
good
web
design
stuff.
So
so
we
just
so.
This
is
the
peer
address.
Well,
it's
the
local
host.
You
don't
get
my
ap
and
then
you
pass
in
its
websockets
because
that's
the
easiest
one
to
connect
to
and
there
we
go.
A
We
have
a
connection
to
this
peer
id
and,
as
you
can
see
it
matches,
and
then
we
have
gossip
sub,
which
is
actually
something
I
didn't
have
in
last
demo.
So
we'll
test
with
a
message
so
hello
world
and
there
we
go.
We
have
hello
world
coming
from
the
browser
to
to
the
server
with
assembly.
A
And
just
to
prove
that
I'm
I'm
still
saying
I'll
connect
another
pier
and
hi
juan
and
there
we
go
and
then
even
on
the
other
one.
We
have
high
honda
so.
A
This
tab
is
using
yeah
sure
sure.
A
A
No
and
I
have
not
connected
to
more
than
a
couple
connections
at
the
same
time,
io
through
foot
is
also
not
tested
or
benchmarked,
which
is
why
I,
whenever
I
try
to
do
this
talk
or
not
talk,
it's
not
a
talk.
It's
a
demo.
Whenever
I
do
the
demo,
I
put
warning
flags
and
try
to
say
warning
flags.
A
It's
like
this
probably
won't
be
as
fast
as
javascript,
because
you
know
javascript
is
optimized
and
it
has
direct
bindings
to
the
I
o
that
the
browser
gives
it
so
like
it's
not
faster,
but
you
have
it
now.
It
is
an
option
and
this
demo
only
works
with
gossip
sub
with
a
pr
that
has
to
be
opened
in
the
repeat
of
your
rest.
So
you
have
to
wait
for
that,
but
the
previous
demo
does,
if
it's
just
flood
sub
yeah,
oh
and
package
size.
A
Yes,
okay,
I
know
what
you're
talking
about.
I
definitely
don't
have
it,
but
from
some
actually
no,
we
have
the
output
file
in
the
district
package,
awesome
containing
folder,
1.4,
megabytes,
yeah
and
that's
not
compressed
or
anything
with
gzip.
So.
A
A
The
website
bindings
are
done
with
an
awesome
thing
that
someone
else
made
for
it's
actually
part
of
liberty,
pier.
Currently
it's
the
webassembly
or
yeah
wasn't.
B
A
It's
a
cargo
flag,
it
wasn't
ext
websockets
yep.
Theoretically,
you
could
have
more
transports
but
yeah.
Okay,
that's
the
end
of
my
demo.
B
So
first
comment
question:
this
is
great.
I
love
this
okay,
no,
no,
no,
the
question:
what
are
the
downsides
like?
Is
there
a
maximum
throughput?
This
thing
can
do
like
doing
this
in
wasm
versus
doing
this
in
rust,
for
the
trade-offs
other.
A
It's
single
threaded,
very
much
so
if
you
try
to
do
multi-threaded
stuff,
it
gets
weird
and
complicated,
really
quick
and
you
lose
performance
right
away.
A
I
wouldn't
like
try
to
embed
this
in
like
node.js
and
like
have
this
as
the
I
o,
like
the
peer-to-peer
thing
just
I
know,
but
performance,
wise
and
throughput,
it
just
needs
to
get
benchmark
and
it'd
be
cool
if
other
people
can
help
out
with
that,
especially
just
making
this
like
a
fully
fledged
thing.
A
This
is
very
much
a
hacky
project,
but
definitely
having
like
yeah
benchmarks
would
be
cool,
and
then
we
could
start
comparing
against
js,
and
then
we
can
make
some
arguments
to
before
and
against
doing
more
things
as
well,
because
you
can
do
throughput
raw
throughput
of
just
like
into
of
assembly
in
the
browser
and
out
of
webassembly
yeah.