►
From YouTube: IPFS Weekly Call 🙌🏽📞 January 7, 2019
Description
IPFS Newsletter: https://tinyletter.com/ipfsnewsletter
ProtoSchool: https://proto.school/#/
Host Your Own ProtoSchool Chapter: https://proto.school/#/host
B
B
So
if
you're
part
of
the
call
put
your
name
in
that'd
be
great
and
we
will
begin
this
call
with
announcements
from
Davi,
then
we'll
get
into
our
main
presentation
from
rüdiger,
and
we
will
end
our
call
with
questions
and
answers,
and
you
can
put
your
questions
in
the
chat
and
that
will
be
our
call
today.
So
without
further
ado,
let
us
start
with
Davi.
A
All
right,
thank
you.
So
much
so
I
have
like
four
little
things.
It's
basically
homework
where
everyone
to
check
out,
and
so
the
first
one
is
that
I
try
to
paint
a
picture
of
what
our
planning
is.
So
we
have
room
maps,
we
have
okay,
ours.
We
have
Kanban
boards,
we
have
all
sorts
of
things
and
so
I
try
to
ok
like
if
I
were
to
kind
of
like
distill
this
down
and
like
understand
like.
A
Where
do
we
touch
each
of
these
things
like
when
we
apply
them
when
we
use
them
and
I
try
to
make
like
this
one
slide?
It
doesn't
have
very
fancy
graphics,
it
is
just
something
I
did
with
keynotes,
but
I
hope
it's
helpful.
At
least
it
was
helpful
to
me
to
guide
other
people
through
hey,
like
we
have
row
mapping.
A
This
is
a
really
really
plenty
thing:
we
have
okay,
ours,
and
this
is
it
fortunately
planning
and
that
we
track
progress,
and
or
this
is
where
our
meetings
or
our
hack
weeks
coming
to
play,
I
to
increase
the
shared
understanding
of
the
group
and
I
tackle
new
new
ideas,
our
new
problems,
and
then
we
have
things
that
we
help
us
like
super
eyes.
Every
week,
like
the
same
time,
is
a
cars
like
this
one,
the
Kanban
boards
and
so
on,
and
so
like
we
share
your
feedback.
A
Tell
me
if
this
is
helpful,
especially
for
people
that
are
new
to
this
community,
that
new
to
the
project
I
know.
There's
a
lot
of
details.
We
have
been
taking
a
lot
of,
like
we've,
been
investing
a
lot
of
time
operating
the
team
management
repo
to
also
make
sure
that
the
onboarding
is
super.
So
that's
the
first
one.
Please
review
that
PR
that
I
just
posted
here
on
June
that
it
also
promotes
the.
The
second
thing
is
that
I
want
to
it's
a
proposal,
it's
basically
making
the
maintainer
protocol
or
wide.
A
Everyone
I
feel
more
ownership
of
the
project
so
that
that
kind
of
like
helps
the
project,
move,
faster
and
and
I
think
we
can
upgrade
these
to
make
it
work
wide.
Throughout
the
other
code
projects
without
following
like
we
can
have
a
material
for
the
specs
people
like
someone
that
can
like
label
the
issues
or
at
least
give
some
feedback
to
people
that
ask
questions
there
or
someone
to
the
Ducks
repo
at
the
website,
etc.
A
Like
someone
that
are
only
is
responsible
to
like
give
some
feedback,
but
I
also
like
that,
can
room
the
issue
that
kind
of
label
it.
That
can
be
the
first
person
which
is
replying
to
a
new
question.
So
that's
like
there
is
more
engagement,
and
so
please
review
the
PR
and
then
the
next
one
is
also
available.
A
This
is
for
your
bike
ideas
and
so
the
next
one
is
about
repo
badges,
I
love.
You
know,
notice
and
so
I
think
they're
helpful
and
right
now
we
went
from
2,000
like
2017,
where
there
were
no
working
groups
to
late
2018,
where
we
have
a
working
group
process
and
I
working
obsessed,
I
wish
with
their
own
okay,
ours
and
their
own
teams
and
so
on.
A
But
now
we
have
like
more,
like
544
repos
across
five
organizations,
and
sometimes
it's
hard
who
owns
this
repo,
who
is
responsible
to
make
sure
like
it's,
not
you
shouldn't,
be
archived
or
who
do
I
ask
questions
about
the
kill
that
is
living
here
and
sometimes
like
that
is
kind
of
like
fuzzy.
There
are
projects
that
move
from
one
working
group
to
another
working
because
they
get
put
started
more
open.
It
makes
more
sense
to
other
working
you
to
take
it
over.
A
So
I
think
the
badges
are
a
good
idea,
like
you
put
it
better,
the
top
of
the
Remi
like
you
know,
we
belong.
So
the
working
group
can
then
like
check
in
and
see
the
project
that
they
are
tackling
yeah
I'll
comment
on
that
PR
as
well
and
was
another
waste.
The
infamous
please
check
here.
Here's
requests
there,
they're
10,
open
to
requests
and
I
guess
like
well.
Everyone
just
came
back
from
holidays,
so
just
by
Jane
on
all
the
discussions
that
they
have
before
all
it
is,
but
like
please
do
as
soon
as
possible.
A
Humpable
can
we
shoot
to
every
Smerch
by
the
end
of
this
week,
like
the
version
that
we
commit
to
this
quarter
so
that
we
all
have
a
shared
understanding
all
like
what
each
working
group
is
going
to
focus.
It
is
also
next
an
opportunity
for
the
community
to
kind
of
page
in
of
like
what
are
going
to
be
our
primary
priorities
for
this
quarter
and
give
us
feedback.
A
C
A
It's
definitely
I
can
comment
concerning
open
source
projects
and
that's
why
I
there's
different
strategies
for
different
projects.
The
maintainer
protocol,
the
wing
maintainer
protocol
kind
of
like
tries
to
cover
for
that
because
in
the
end,
it's
not
some
sort
like
LM
when
grabbing
moment,
where,
like
someone
just
arrive
and
say
now,
I'm
the
maintainer
for
people,
it's
kind
of
like
a
a
ritual
process
where
someone
by
contributing
to
the
project
by
like
basically
gaining
trust
with
the
other
contributors,
can
then
be
nominated,
invited
to
become
the
maintainer
of
their
people.
A
That
said,
we
actually
like
still
keep
the
tech
leads
to
be
the
real,
like
the
people
that
release
the
top-level
projects
so
go.
Ipfs,
Jessup
EFS,
just
like
it
appear
like
there
is
some
more
kind
of
like
proven
work
to
be
able
to
release
the
thing
that
I
could
then
everyone
installs
we,
we
are
a
little
bit
more
flexible
with
internal
pieces.
A
A
People
as
well,
and
the
tech
lead
for
that
side
of
the
project,
and
so
the
there
is
like
the
actually
not
do
it
somewhere
like
a
trio
in
which,
like
people
kind
of
like
just
help,
each
other
make
sure
that
they
are
making
the
right
decisions
reviewing
the
PRS
in
a
correct
way
that
their
writings
are
getting
merged,
that
they
are
make
it
like
that.
The
new
maintain
your's
actually
get
to
the
opportunity
to
learn
all
the
context
from
previous
decisions.
A
So
when
we
implemented
this
image
as
ecosystem,
like
a
big
part
of
my
role
like
doing
a
transition,
was
just
pointing
people
to
issues
where
we
had
discussion
saying.
This
is
not
a
great
idea
right
now,
because
we
have
consider
these
situations
and
so
as
a
human
index
of
all
ipfs
knowledge.
I
was
like
just
like
pointing
people
to
like
just
like
gather
and
get
that
context
as
well
as
I.
Have
it
in
my
over
time.
A
It's
something
that
kind
of
like
spreads
gossips
over
and
like
more
people,
become
more
informed
and
more
confident
to
make
more
decisions,
but,
but
still
it
is
like
a
concern
to
have
and
something
to
remind
ourselves
to
make
sure
to
perhaps
like
every
quarter.
Just
do
a
round
of
my
chickens
like,
let's
see
who
has
permissions
to
what
was
for
me.
A
D
Want
to
point
out
that
the
Linux
kernel
actually
has
an
Athena
protocol
as
well,
where
each
module
has
because
maintainers
file
that
says,
who
maintains
it
and
Linux
will
like
do
a
get
pull
from
there.
I
post,
emergent
changes,
but
I
think
you
can
solve
the
final
control,
but
he
doesn't
necessarily
go
everything
with
a
fine-tooth
comb
yeah.
D
E
We
do
still
have
these
kind
of
maintain
like
lead,
maintainer
roles
so
like
we
have
like
lead,
maintainer
forego
ipfs
that
might
provide
feedback
to
many
different
module,
maintainer
x',
and
then
we
might
have
lead
maintainer
for
IP
of
s.
That
might
provide
feedback
to
many
different
captain's
across
to
us
and
go
in
other
communities,
and
I
think
that's
something
that
we
should
just
continue
to
to
support
and
make
sure
we
use
it
and
as
long
as
this
doesn't
agree,
disagree
with
that
I'm,
a
hundred
percent
on
board
I'll.
C
Just
throw
in
the
rest
of
my
comments
in
that
in
the
PR
thing,
I'll
just
point
out
that
Steven
said
this
is
what
we
already
having
go
ipfs.
So
david's
proposal
is
proposing
to
change
that.
So,
if
two
beads
proposing
that
we
should
take
this
protocol
and
apply
it
across
the
rest
of
the
work,
is
it
a
protocol?
That's
already
in
place,
Ingo,
ipfs
or
not
so
they're
like
I'm,
confused
on
what's
changing
and
what's
staying
the
same
then
right.
D
That
this
was
what
we
haven't
got,
that
is
the
technique
controlling
what
goes
in
and
out
collected
myself,
the
Munroe,
not
the
wrestling
maintainer
protocol.
Currently,
he
goes
because
I
pretty
much
anyone
with
right
actors
converse
things
to
other
opposed,
except
for
the
gopis
main
one
I
think
this
one
would
basically
delegate
control.
Specifically,
this
is
responsible
for
this
rep
out
of
this
person's
on,
for
this
replica,
cetera,
I
believe
in
JavaScript
this
one
person,
I,
don't
know
if
I
think
there's
one
person
responsible
for
the
main
rep
though,
but
I
don't
know
so.
A
As
I
guess,
like
a
good
clarification
is
really
to
like
just
go
to
the
the
protocol
itself.
So
there's
everyone
by
choosing
on
what
is
described
there,
but
but
like
you
as
a
point
of
clarification
for
the
whole
group,
there's
definitely
a
distinction
between
them
and
Dana
of
the
repo
and
so
the
person
that
can
review
the
requests
that
can
give
advice
that
can
label
the
issue
that
can
given
that,
like
all
of
the
criteria,
were
met
for
a
pull
request
and
merge
and
therefore
then
release
that
code.
A
And
then
there
is
other
people
in
the
projects
that
kind
of
like
spread
their
responsibilities
across
multiple
areas
of
their
expertise.
That
are
this,
like
typically
titled.
The
tech
leads
of
the
project
that
actually
have
more
a
clear
understanding
like
what
is
the
strategic
trajectory
that
the
project
is
taking
until
the
maintainer
protocol
is
not
clear
by
trying
to
silo
people
into
being
responsible
for
the
whole
strategy
office
in
your
repo.
A
It
is
more
like
distributing
the
responsibility,
the
ownership
of
the
multiple
pieces
of
the
place
and
giving
people
autonomy
to
to
be
able
to
like
merge,
code,
review
or
review
the
feedback
merge
code
and
like
the
real
result,
is
that
you
get
a
code
base
and
I
can
a
repo
base.
That
is
way
more
curated
way,
more
groomed.
That
way
that
contributors
get
responses
way
faster,
because
that
there
is
more
people
to
home,
ask
questions,
and
so
yeah
I
guess
like
there's
like
some
things
like.
A
D
B
Anyone
has
any
other
conditional
concerns
or
questions
you
can
leave
the
issues,
leave
an
issue
and
they
github
link
in
the
chat.
So
without
further
ado,
we
will
begin
our
main
presentation.
Rudiger
is
going
to
explain
how
he
uses
IP
FS
in
is
your
is
name
to
go
your
company
attics
active
awesome.
Thank
you.
Take
it
away.
F
Okay,
so
two
words
about
me:
I'm
old
guy
I've
been
doing
software
development
since
professionally
so
paid
money
since
to
the
1999
and
I've
got
the
10
years.
Experience
in
the
space
industry
and
in
2016
I
was
kind
of
convinced
by
a
good
friend
of
mine,
wouldn't
cool,
who
is
CTO
backticks
to
drone
tactics
and
now
I'm
going
to
share
my
screen
and
talk
a
little
bit
about
what
we
do
without
FS
and
that
takes
and
what
we
do
in
general.
F
Also
and
I
will
be
interesting
for
you,
so
can
see
that
this
mechanic,
okay,
okay,
so
first
of
all,
first
of
all,
a
few
words
about
ethics,
so
ethics,
the
startup
founded
in
2016,
there's
three
founders,
two
mechanical
engineers.
One
is
a
software
engineer
and
physicist,
and
so
we
have
some
domain
knowledge
in
both
manufacturing
and
software.
F
We
are
based
in
Munich,
Central
Europe,
but
just
as
protocol
labs,
we
are
fully
distributed
engineering
team.
But
since
we
are
in
a
very
early
stage
we
confine
ourselves
to
the
European
time
zones.
So
we
got
people
in
Madrid
and
in
Sofia
that
that's
the
extent
of
it,
but
we
wouldn't
hire
somebody
in
the
US
or
in
New
Zealand.
Unfortunately,
so
what
we
do
we
a
very
high
level
overview?
What
we
do
is
we
are
doing
digitalization
of
manufacturing
processes.
F
So
one
thing
that
that
always
comes
up
when,
when
we
talk
about
what
we
do
is
all
right,
they're
doing
robots,
and
actually
that's
not
what
we
do.
That's
not
not
the
core
of
it.
What
we
do
is
not
primarily
about
automation,
so
what
we
do.
Basically,
we
want
to
have
a
way
to
coordinate
all
the
things
that
have
been
the
factory,
whether
it's
a
robot,
that's
that's
doing
something
or
a
worker
or
some
kind
of
logistics,
that's
happening.
F
Any
process
that
happens
in
a
factory
at
a
high
level
is
something
we
are
interested
in
to
to
automate
or
to
physio
facilitate,
and
you
could
say,
I
mean.
Obviously,
there
are
some
cases
where
automation
is
very
useful,
I
mean
if
you
have
a
place
with
which
stamps
metal
pieces.
You
don't
want
the
human
to
do
that,
but
there
are
lots
of
lots
of
situations
where
humans
are
quite
quite
adjectives,
and
so
what
we
want
to
do
kind
of
a
mission
statement
is
we
want
to
use
digital
technology
to
keep
you
labour
competitive
with
automation.
F
So
it's
not
just
about
automating
everything,
but
basically
make
sure
that
humans
is
efficient
as
they
can
be
in
a
factory
and
I
got
a
quote
for
this
from
either
musk.
Yes,
excessive
automation
at
Tesla
was
a
mistake
to
be
precise,
my
mistake
humans
are
underrated
and
that's
something
we
can
really
get
behind
and
acting's.
Okay.
So
that's
a
big
picture
of
you
so
far.
We
have
basically
been
development.
F
I
could
talk
about
this
for
50
minutes
of
20
or
but
the
basic
idea
is:
we
want
to
allow
people
that
have
manufacturing
domain
knowledge,
so
they
know
how
many
fetching
works,
but
they
don't
have
this
immune
systems
knowledge,
it's
quite
a
few
of
those
people,
and
we
want
these
people
to
enable
these
people
to
write
resilient
applications
for
manufacturing.
So
we
want
to
enable
them
to
be
able
to
write
applications
which
are
petition
tolerant.
So
they
work
when
there's
some
kind
of
network
error
in
the
factory
and
they
are
distributed.
F
Okay,
so
just
before
I
go
into
details,
how
exactly
we
use
a
TFS
I
just
want
to
show
a
few
pictures
from
our
customers.
So
this
is
a
glass
manufacturing
plant.
These
houses
that
you
see
there
are
basically
they
are
glowing
red
because
they
have
been
have
been
just
produced
out
of
a
block
of
molten
glass,
and
this
is
an
industrial
tablet
and
an
Android
tablet
which
is
used
by
the
worker
to
call
what's
happening
here.
F
So,
for
example,
if
there's
some
kind
of
error
in
one
of
the
machines,
you
cannot
the
error
here
and
so
on,
and
this
is
running
yet
acting
so
s
and
acting
supplications
and
it's
also
running
ipfs,
obviously,
because
we
are
using
active
s
kind
of
light
so
on
networking
stack
so
to
speak.
This
is
another
application.
This
is
public
transport
maintenance
facility.
So
in
time
for
Germany
there
is
a
facility
that
performs
regular
maintenance
on
subway
trains
and
in
order
to
coordinate
what
needs
to
be
done
for
this
regular
maintenance.
There's.
F
Basically
these
two
things
they
have
to
do
and
then
there's
not
will
be
some
things
that
they
do
based
on
me.
So
something's
broken.
They
fix
it
and
to
cooperate
this
here.
Also,
we
have
the
Android
tablet,
which
is
attached
to
distinguish
coffee
shop
floor
board
and
there
we
have
the
acting
supplication
running.
F
So
this
is
a
close-up
view
of
the
thing.
As
you
can
see,
this
is
a
very,
very
normal
Android
tablet,
but
it's
from
a
software
point
of
view.
Well,
it's
a
little
bit
more
expensive
and
it's
and
it's
rocked
so
it's
watertight
and
you
can
drop
it
from
2
meters
of
concrete
without
breaking,
which
is
very
helpful
in
the
factory.
F
So
it's
way
more
robust
than
my
macbook
pro
and
as
you
can
see,
this
is
running
an
application
which
allows
you
to
track
progress
on
some
production
step
and
you
can
lock
how
many
things
you
have
produced,
and
you
can
say
you
know
I'm
finished
with
the
activity.
Is
this
something
called
production
data
acquisition
and
are
going
to
detail
about
that
a
little
bit
later?
F
This
is
another
application.
In
this
case,
this
is
in
a
inner
machine
in
a
manufacturing
machine.
There
are
these
Edina
rails
where,
where
all
the
equipment
is
that
the
powers,
the
machine
and,
in
addition
to
all
the
usual
equipment
that
this
machine
there
is
this.
This
grey
box
is
an
industrial
raspberry
pie.
So
it
has
a
very
fancy
name,
but
essentially
is
a
raspberry
pie
with
more
case,
and
this
is
also
running
yet
its
platform.
F
So
it's
also
running
go
Adventist
and
this
obviously,
this
kind
of
machine
can
only
be
used
for
ready,
low
death
rates,
so
some
kind
of
counters.
You
cannot
be
use
for
machine
learning,
but
if
you
just
want
to
get
some
data-
and
this
is
this
way
to
go-
they
are
not
that
expensive
and
they
are
very
racked,
and
you
just
put
them
into
into
these
derails
and
connect
them
to
the
machine.
F
F
If
you
go
into
even
even
very
reasonably
modern
factories,
you
will
see
that
the
front
office
is
very
modern,
but
once
you
go
down
to
the
shop
floor,
you'll
always
see
these
paper
based
production
production
orders
not
in
our
factories,
but
in
a
very,
very
large
fraction
of
the
small
to
medium
sized
factories.
You
still
have
this
and
it's
not
not
all
that,
because
you
know
one
thing
about
paper
is
that
it
always
works.
F
So
this
is
the
last
slide
of
this
part.
So
this
is
all
the
places
where
we
have
active
solutions
deployed
and
they're
all
running
ipfs.
So
these
are
a
bunch
of
factories
in
in
central
europe,
where
we
have
all
our
software
deployed
and
we
have
also
ipfs
deployed
mostly,
they
are
pretty
small
deployments,
we're
trying
to
grow
them
next
year,
but
it's
very
nice
to
have
these
things
actually
in
production.
F
F
So
one
thing:
I
was
interested
in
content
in
a
storage
even
before
I
learned
about
ipfs
I'll
get
uses
it
so
kind
of
everybody
knows
it
since
2008
or
whatever
and
I
think,
especially
for
a
manufacturing
data.
It's
very
nice
to
have
this
safety
against
data
corruption,
because
the
data
is
kind
of
important.
F
It
might
be
that
some
some
batch
of
comm
production
is
is
deficient,
and
then
you
have
to
prove
that
you
did
everything
according
to
to
the
rules
and
if
you
have
content
read
storage,
there
is
not
much
way
to
tamper
with
the
data,
so
that's
very
important
property
for
us.
It
was
of
our
customers.
Next
things
auditability.
You
can
basically
have
an
audit
trail
which,
which
you
can
prove
that
is
at
a
certain
time,
and
if
it's
certain
factory,
some
things
happen
and
location
transparency
I
mean
I.
F
Petition
tolerance
is
also
very
important
for
us.
Like
I
mentioned,
we
want
to
replace
paper
and
one
thing:
that's
really
great
about
papers
that
always
works.
You
don't
have
to
have
the
piece
of
paper
or
connect
it
to
another
piece
of
paper,
just
take
to
be
some
paper
at
the
pen
and
that's
it,
and
so,
if
you
want
to
replace
paper,
we
have
to
have
to
build
on
something
which
is
also
resilient.
That's
basically
where
we
use,
invest
well
and
yeah.
F
Next
thing
is
diploma
with
large
assets,
so
we
have
quite
some
work
instruction.
Videos.
If
you
have
some
kind
of
manual
production
step,
then
often
the
factories
have
videos
which
tell
the
workers
exactly
how
this
step
is
to
be
performed,
and
it's
quite
useful
body
to
be
able
to
take
a
large
number
of
videos
and
put
them
on
lots
of
devices
using
ipfs,
and
it
doesn't
work
as
good
and
as
it's
supposed
to
work
we'll
get
to
that
later.
F
But
in
principle
it's
it's
a
great
way
to
distribute
large
assets
and
I,
given
that
these
factories
often
have
a
very,
very
slow
connection
to
the
calendar.
So
imagine
you
have
20
devices
and
each
of
them
was
about
the
video.
That
would
not
be
good,
so
we
also
use
a
FSS
infrastructure
for
a
particular
development.
F
F
F
F
Then
we
have
these
Android
based
industrial
tablets
like
the
one
I've
shown,
and
we
also
have
n
dot
based
barcode
scanners
for
logistics
applications.
So
this
this
is
a
barcode
scanner.
Basically,
it's
an
Android
tablet
which
has
a
laser
which
can
scan
barcodes.
These
things
are
actually
quite
neat.
They
can
scan
barcodes
over
a
distance
of
20
meters.
F
So
if
the
customer
has
an
ERP,
for
example,
on
side,
you
put
a
virtual
machine
next
to
the
EAP,
so
basically
in
the
same
rack,
and
if
the
customer
has
some
sub
cloud
system,
we
also
put
a
system
in
the
north
of
our
system
in
the
same
cloud
as
close
as
possible.
Basically
so
the
network
network
topology
speaking
okay.
So
this
lets
interrupt
this
little
bit
and
do
a
little
demo.
F
Will
be
hard
to
recognize,
but
I
still
think
it's
fun
to
series.
So
this
is
one
of
these
industrial
Android
tablets,
and
on
that
you
can
see.
This
is
for
a
workstation
which
is
called
hand
cleaning
and
there
you
have
the
different
activities
which
are
which
can
be
performed
at
a
workstation
and
then
the
work
basically
tap
on
one
activity
and
then
you
can
join
the
activity
so
now.
F
F
F
F
F
Yes,
I
mean
just
just
once
all
right:
okay,
okay,
so
this
is
basically
how
we
do
it
on
the
on
the
Android
devices.
So
we
got
a
shell
app
and
abet
view
in
which
we
got
the
our
acting's
apps,
and
these
act
accepts
that's
one
thing
that
you
might
find
confusing:
they
talk
to
go
I
profess
process
by
a
REST
API,
so
we
don't
use
JSF
s
and
we
also
don't
use
JSF
s
API
for
various
reasons,
but
we
just
use
the
REST
API
directly.
We
have
got
business
running
on
this
Android
device.
B
E
This
is
awesome
and
I'm
curious,
whether
or
what
you've
experienced
or
how
much
interest
there
is
from
various
factory
clients
around
kind
of
a
either
a
resiliency
or
an
offline
sort
of
perspective,
of
being
able
to
kind
of
run
and
host
this
content
in
a
more
distributed
fashion
and
curious
from
from
your
perspective,
having
a
lot
of
those
conversations
what
you've
experienced
in
terms
of
their
feedback
and
how
much
the
factor
that
is
for
them.
Well,.
F
It
is
I
mean
very
much
depends.
Some
customers
are
not
really
aware
of
of
the
problems
with
with
having
a
centralized
application,
but
they
will
definitely
notice
once
it
breaks,
and
you
often
have
these
situations
where
the
factory
kind
of
doesn't
work,
because
the
ERP
currently
is
broken
because
the
ERP
is
in
a
different
location.
So
once
you
explain
to
them
that
this
would
not
happen,
it's
it's.
Actually,
it's
a
good
sell,
then,
and
then
in
other
situations,
you
you
actually
they
they
immediately
understand
the
benefit.
F
For
example
in
we
have
logistics
applications
and
they
are
basically
you
have
a
scanner
and
you
track
material
movements
and
they
often
don't
have
good
Wi-Fi
coverage
in
their
warehouse.
So
they
immediately
understand
that
they
need
to
be
able
to
to
perform
a
movement
without
having
Wi-Fi
coverage,
because
it's
impossible
to
get
good
Wi-Fi
coverage
in
a
warehouse
full
of
like
metal
barrels.
So
many
people
actually
get
it.
Sometimes
we
have
to
help
them
a
little
bit
to
understand,
but
they
they
get
the
benefit.
F
Definitely
it's
just
the
half
thing
is
that
we
need
to
have
a
programming
model
which
is
easy
enough.
That
that
people
don't
have
to
be
distributed
systems
experts
to
write
this
software,
because
otherwise
I
mean
these.
These
people
are
domain.
Experts,
I
really
really
really
know
about
their
domain,
but
they
don't
know
about
petition
for
rents
or
cap
theorem
or
CID
T's
or
any
of
that,
and
they
shouldn't
have
to
know
right.
G
G
F
The
switch
is
kind
of
new,
so
currently
we
don't
use
it,
but
when
it
was
released,
we
were
immediately
thinking
about
that
that
we
there
would
be
several
ways
we
could
use
it.
So
we're
thinking
about
it.
Let's
put
it
that
way.
Okay,
thank
you.
It's
it's
very,
very
useful,
because
these
companies
often
have
a
very
respective
firewall
and
any
way
to
get
around.
There
would
be
very
useful.
G
F
B
F
B
If
you
have
any
additional
questions
after
the
presentation,
you
can
leave
them
in
a
comment
section
and
three
next
week,
Terry
we'll
be
presenting
proto
school,
so
proto
school.
It's
not
the
launch
is
next
week.
But
if
you
want
to
experiment
with
proto
school,
then
please
go
ahead.
It's
really
exciting
and
if
you
actually
want
to
start
proto
school
meet
up
in
your
city,
plea
I'll
leave
those
weights
in
the
comments
section,
you
can
go
and
start
a
proto
school
network
in
your
city.
So
thank
you
ever.
Thank
you.