►
From YouTube: Mass Adoption and Use-Cases: Golem and UX Challenges
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
So
imagine
you
have
a
car
which
is
actually
hard
for
me,
because
I
do
not
have
one
but
bear
with
me.
You
have
a
car
and
where
is
it
now?
It's
probably
parked
somewhere,
either
here
or
at
home,
because
you
are
sitting
here.
So
it
is
currently
doing
nothing,
and
even
when
you
use
it,
you
will
get
stuck
behind
a
traffic
light
or
in
a
traffic
jam,
so
while
you're
using
it
you're,
not
always
using
its
full
potential
or
power.
So
now,
let's
take
this
example
from
the
car
and
apply
it
to
a
computer.
A
When
we
think
about
it,
our
computer
actually
has
the
same
two
problems
that
our
car
has
we're,
not
using
it
all
the
time
and
even
if
we
are
using
it,
we're
not
always
using
it
to
its
full
potential.
So
this
is
exactly
where
God
comes
in.
Gholem
allows
you
to
share
your
computing
power
with
other
people
in
the
distributed
network
when
you
are
not
using
it
as
much
as
you
have
power,
for
it
also
works
the
other
way
around.
A
A
There's
an
overview
of
schema
of
the
Gollum
Network,
the
requester
nodes,
gholem
people
that
use
golden
which
are
requesting
tasks
from
the
network
providers
are
the
nodes
that
give
their
computing
power
to
the
network
and
in
the
future
we
will
have
developers
that
will
be
able
to
write
use
cases
onto
column
because
we
as
bone
factory
cannot
think
of
them
all.
So,
let's
go
through
a
step
by
step
approach.
A
A
A
One
of
the
idle
column
providers
receives
this
message
and
wants
to
pick
up
this
tasks,
so
what
it
does
is
it
will
download
the
files
and
it
will
start
the
computation
after
a
while,
it
is
done
with
the
computation,
so
it
will
send
the
resources
back,
but
the
requester
cannot
be
fully
sure.
This
is
exactly
as
it
requested
the
task,
so
what
it
will
do
is
it
runs
some
small
tests
locally
to
confirm
that
the
resultant
receives
back
is
actually
the
expected
results,
and
when
this
is
the
case,
they
will
pay
the
provider.
A
A
As
you
can
see,
when
the
golem
note
is
already
done
in
about
40
minutes,
the
blender
note
is
only
at
8%
a
few
hours
later
about
12
times.
The
blender
note
is
finally
done,
but
this
is
nothing
against
blender,
because
golem
will
use
the
exact
same
blender
under
the
hood.
The
big
difference
here
is
that
golem
runs
the
computation
on
40
computers,
while
blender
only
uses
one.
A
This
is
the
last
slide
of
the
introduction.
These
are
some
screens
from
our
app
and
they
empower
the
flow
that
I
described
earlier.
In
the
first
screen.
We
see
the
wallet
where
the
users
can
manage
their
funds.
We
use
GMT
to
pay
for
the
computations,
which
is
gold
on
the
network
token,
and
we
pay
ethereal
to
pay
for
the
gas
for
using
the
ethereal
Network
below
this.
You
can
change
your
settings,
for
example,
how
many
resources
you
want
to
give
to
the
Golem
network
in
a
second
screen.
A
A
You
also
see
some
other
settings
like
the
current
bid
is
0.1
gmt
per
hour,
and
when
we
press
start
task,
we
will
move
to
the
last
screen
where
we
get
an
overview
of
all
currently
computing
tasks.
When
you
hit
the
details,
you
can
see
which
parts
of
your
blender
render
are
already
received
back
and
you
can
almost
live
see
the
picture
fall
together.
A
The
approach
that
we
took
to
prepare
for
more
users
is
to
research,
empathize,
evaluate
and
improve.
We
started
off
with
a
desk
research
to
find
out
who
our
blender
users
really
are.
After
that
we
needed
to
get
quantitative
knowledge,
qualitative
knowledge
about
what
their
needs
were
and
how
they
would
want
to
use
our
applications.
A
A
In
the
second
part
of
the
talk
we
dove
in
deep
with
those
blender
users
to
talk
about
every
single
detail
of
the
process
that
it
just
went
through.
This
gave
us
a
good
understanding
of
how
they
saw
the
things
that
we
designed
and
how
they
were
trying
to
use
it.
After
these
talks,
we
had
a
huge
list
of
tasks
that
we
could
pick
up
to
improve
their
user
experience.
A
So
why
did
we
go
to
maintenance?
Firstly,
our
community
was
really
expecting
it
of
us
in
our
initial
roadmap.
We
made
a
wrong
estimation,
so
we
really
needed
to
push
from
that
site,
but
we
also
knew
that
to
get
real
valuable
user
feedback,
we
had
to
move
out
application
out
of
the
laboratory
environment
and
into
the
real
world.
A
A
Anything
is
nothing.
No
questions
asked
no
problems.
Nobody
seemed
to
have
pick
up
on
our
news.
First,
we
started
to
doubt
ourselves.
Maybe
we
had
underestimated
the
potential
of
pelham,
maybe
we
over
stretch,
we
don't
know,
but
after
a
few
hours,
we
noticed
that
the
news
hit
off
and
our
tech
support
that
we
prepared
carefully
was
definitely
needed
in
the
week
after
we
release
the
testers
channel
on
our
rocket
Jets
exploded.
A
We
had
over
almost
a
thousand
users
on
the
network
in
the
first
week
of
release.
Sometimes
we
noticed
that
even
with
three
people
in
the
tester
support,
yet
it
wasn't
barely
enough
to
make
it,
but
we
made
it,
and
thanks
to
this,
we
had
a
good
understanding
of
what
issues
the
users
were
facing.
We
were
able
to
benchmark
the
network
and
scale
up
and
see
his
full
capabilities
as
a
comparison.
The
test
networks
that
we
use
the
tests
on
were
always
between
10
and
on
an
extreme
case
in
the
Christmas
holiday.
A
It
was
50
notes,
but
it
was
never
never
more.
So
a
thousand
notes
was
ginormous
skill
for
us
also
because
the
developers
were
on
tech
support
ships.
They
were
able
to
get
closer
to
new,
to
the
users,
get
to
know
them
and
get
to
know
how
they
use
the
app,
which
was
very
valuable
for
them
to
be
able
to
develop
better
afterwards
and
last,
but
definitely
not
not
least,
we
had
very
happy
users
after
these
ships.
It
was
very
rewarding
to
see
so
many
people
happy
with
our
maintenance
release.
A
A
Here,
you
see
some
of
the
growth
that
I
was
talking
about
earlier,
from,
for
example,
the
blender
users
interviews,
but
also
the
maintenance
release.
This
is
in
December
2017
and
the
user
interface,
which
I
feel
it's
still
very
technical
because
it
was
made
mainly
by
technical
people,
but
in
the
last
half
a
year,
we've
improved
a
lot
borders,
a
lot
of
user
experience
designers
and
that
made
us
able
to
grow
and
make
the
app
more.
You
and
user-friendly.
A
We
couldn't
have
done
this
without
our
awesome
community.
We
have
a
super
amazing
group
of
people
in
the
testers
channel
and
on
reddit
that
are
great
to
help
each
other
out.
Usually
we
only
need
to
explain
an
issue
one
two
three
times
and
then
a
snowball
starts
rolling
where
users
start
helping
each
other.
At
this
point
they
will
only
reach
back
out
when
something
is
new
or
something
is
good
to
share.
So
great
shout
out.