►
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
Okay,
so
this
is
a
facility
for
public
transport
maintenance
in
Frankfurt
Germany.
You
have
this
thing
called
the
shop
floor
board,
which
is
a
very
analog
thing
where
people
coordinate
what
they
need
to
work
on
and
in
the
middle.
This
is
a
tablet.
I
got
one
here.
If
you
want
to
know
how
it
works
exactly
took
me
later,
where
they
can
basically
figure
out
what
they
have
to
work
on
and
track
what
they
are
working
on
and
stuff
like
that.
Next
thing
come
on.
A
This
is
this:
is
a
scaffolding
repair
factory
in
in
UK?
They
see
a
close-up
of
how
these
tablets
are
being
mounted
in
the
factory,
so
it's
all
very
industrial,
very
ugly,
but
very
solid,
and
as
a
last
thing,
it's
one
of
my
favorites.
This
is
a
glass
manufacturing
factory.
So
whenever
you
have
a
drinking
glass,
it
gets
manufactured
in
one
of
these
factories.
These
are
glowing
glass
bottles
and
what
they
use.
A
The
tablet
for
is
to
optimize
the
setup
process,
because
these
are
very
complex
and
very
analog
machines
which
they
have
to
set
up
and
they
need
to
make
the
dissenter
process
deterministic.
Okay,
so
enough
pictures.
Now
it's
just
boring
bullets,
so
acting
so
s.
Well,
we
build
all
this
on
is
something
called
acting
so
s,
it's
not
really
an
operating
system,
but
something
which
you
might
think
of
as
an
operating
system.
A
It's
kind
of
a
runtime
for
writing,
applications
for
factories
and
the
basic
idea
is
this
I'm
sure
most
of
you
are
familiar
with
this
most
applications
in
come
on
in
industry.
Manufacturing
industry
are
on
this
axis
and
this
works
very
well.
It's
very
simple
programming
model,
but
at
least
slash
pictures
which
look
like
this
you've
got:
one
fed,
node
and
lots
of
tried
which
talk
to
the
node.
A
You
couldn't
figure
out
how
to
draw
outlines
so
I
left
them
out,
but
I
think
you
get
the
idea
and
I
think
so,
as
on
the
other
axis,
so
we
are
available
in
petition
tolerant,
but
not
consistent,
obviously,
after
a
consistency
at
some
point.
So
what
we're
doing
is
eventual
consistency,
and
this
enables
us
to
do
architectures
like
this,
which
looks
much
nicer
and
it's
much
more
resilient,
because
if
a
few
of
them
go
away,
the
other
can
still
talk
to
each
other.
Ok.
So
what
works?
What
doesn't
in
ipfs?
A
So
this
is
just
my
personal
opinion.
We
are
building
or
distributed
content,
rest
storage
and
for
us
it
works
pretty
well,
it
doesn't
work
very
well
currently
at
the
global
scale,
but
for
our
little
private
swarm
it
works
very
well
for
us,
then
pops
up
works
really
well,
but
we
had
some
issues
with
natural
virtual
private
swarms
works.
Well,
it's
a
very
nice,
very
simple
feature,
but
it's
experimental
and
we
hate
to
build
on
experimental
features.
So
I
would
love
to
this
thing
to
become
non
experimental.
A
Android
support,
Android
support
works
surprisingly.
Well.
We
just
take
the
arm
binary
and
put
it
on
Android,
but
there
are
some
issues
which
don't
because
it's
not
an
Android
build,
but
it's
just
normal.
Our
arm
be
hood
and
next
thing
I
pns
for
us.
It
doesn't
work
at
all.
We
tried
and
tried
and
tried
it
now.
We
just
use
dns
link,
so
I
won't
try
it
again
unless
somebody
really
convinced
me
that
this
time
will
work
perfect
resource
usage
is
could
be
better,
but
we
see
a
trend
in
the
right
direction.
A
Let's
put
it
that
way.
Now,
I
got
a
wish
list.
Ok,
we
are
very
grateful
for
what
protocol
left
us
for
us,
but
nevertheless,
I
got
a
wish
list
so
wish
list
basic
interactions
like
this
beauty
contest
or
pops
up
and
IP
NS.
They
just
have
to
work.
You
need
to
rely
on
them.
Just
like
you
rely
on
cat
and
some
UNIX
tools.
Currently,
that's
not
the
case.
A
They
have
got
to
have
high
performance
high
performance.
What
do
you
mean
by
high
performance
within
factor
of
2
of
what's
physically
possible?
That's
what
I
would
consider
high
performance
if
you
have
two
nodes
and
you
want
to
copy
data
from
A
to
B,
it
should
be
half
as
fast
as
the
wire
allows.
That's
fine
I
mean
I,
accept
this
overhead,
but
it
should
not
be
a
factor
of
ten
slower
and
physically
possible
next
thing.
Officially
supported
recite
profess,
we're
currently
writing
stuff
in
rust,
because
we
need
the
performance.
A
It
would
be
really
great
if
we
could
integrate
a
device
on
the
same
process
instead
of
talking
to
it.
Why
HTTP
and
last
thing
please,
there
seems
to
be
a
tendency
to
make
things
makes
very
very
complex
things
which
are
very
nice
amazing
concepts,
but
that's
cool,
but
please
first
make
the
basics
work.
Well,
I
mean
okay,
you
can
it's
always
fun
to
write
these
spaced
out
projects,
but
for
us
that
worked
with
useless
stuff
in
production,
it's
really
important
that
the
basics
work
like
like
yeah.