►
From YouTube: TokenScript Weekly Meeting 20200827
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).
C
Hello,
hello,
talk.
C
C
James
brown
told
me
that
he
will
be
back
in
about
five
minutes,
so
we
actually
have
a
bit
of
time
to
chat
about
weather
and
stuff.
What's
the
protocol
first,
the
weather
right.
D
Had
like
a
lot
of
long
weather
the
last
couple
of
weeks,
but
this
week
it's
getting
cold
and
rainy
again
like
we're
back
to
normal
summer
weather,
which
is
you
know,
like
18
degrees
and
cloudy
and
rainy
perfect
for
cryptographer
yeah.
Exactly.
C
Okay,
yeah,
it's
so
good
here
standing
here.
I
didn't
have
time
to
ride,
of
course,
but
other
than
that
the
horse
is
just
eating
grass
all
day.
C
Oh
yeah,
of
course,
of
course,
since
we
have
about
four
million
century
james
brown
joins
and-
and
I
think
it's
important
that
he
joins,
can
we
just
review
the
concept
of
token
negotiation
if
that
has
not
been
discussed
with
you
before?
Actually
this
is
an
age-old
concept,
and
it's
also.
C
C
I
refined
it,
of
course,
after
left
having
left
the
bank
because
back
in
the
bank,
nobody
cared
about
the
web
application,
so
it
was
token
negotiation
on
the
business
level
and
this
application
that
was
not
not
on
the
web,
and
so
I
passed
an
article
to
tor
introduction
article,
which
said
things
that
I
think
would
already
know.
But
nevertheless,
if
we
are
waiting,
I
just
I
I'll
send
a
quote
forward.
A
copy
to
boon
and
sign
on.
Okay
sounds
good
yeah.
C
F
G
F
F
F
C
C
E
C
F
C
Parts
first
is
the
universal
defined
by
having
one
key
and
you
can
use
that
login
to
all
the
websites.
Of
course
you
can,
you
cannot
use
the
same
key.
Otherwise,
if
it's,
if
otherwise,
your
access
becomes
a
linkable,
so
they
have
to
be
key
derivation,
but
the
idea
is
the
same
and
the
second
being
login,
which
means
you
can
use
that
key
authentication.
And
since
you
have
a
key,
you
can
authenticate.
Since
you
have
authenticate
you
can
log
in.
Therefore,
nothing
has
to
do
with
password.
E
I
I
think
I
miss
a
part
of
it
you're,
saying
you're,
saying
that
you
don't
have
to
deal
with
password.
Are
you
saying
that
that's
no
good,
or
are
you
saying
that
that's
not
a
problem?
Oh
so.
C
So
so
the
okay
so
number
one,
the
universal
login
has
two
parts.
The
universal
part
is
one
key
opens
every
door
logs
into
every
website
and
number
two
is
that
the
the
login
process
does
not
require
password.
So
that's
just
the
definition
of
universal
login.
To
my
understanding,
there
are
a
few
such
projects,
and
most
of
them
are
based
on
ethereum,
private,
key
public
key,
and
your
question
is
whether
or
not
this.
H
C
C
E
I'm
saying
I
wonder
if
universal
login
or
just
login
in
general
is
useful
to
look
at
because
it
is.
It
allows
us
to
bridge
to
non-blockchain
systems.
C
Oh
yeah,
so
we
we
so
so
I'm
not
advising
like.
Let's
get
rid
of
vlogging,
I'm
just.
C
As
login,
if
you
want
to
just
because
people
like
to
use
the
concept
login
of
the
following
tokens,
the
amazing
bundle,
token,
the
proof
of
age,
the
gamer
credit,
token
and
yeah.
Actually,
I
made
only
fall
in
this
example,
the
most
suitable
token
as
a
login.
If
you
want
to
return,
the
login
concept
to
the
user
is
probably
the
first.
C
It's
all
up
to
the
website
if
they
want
landlording
becomes
a
concept
that
is
not
not
about
web
authentication,
but
about
user
experience.
E
C
Oh
yes,
I
I
wouldn't
envision
that
we
will
do
not
touch
login
at
all.
Every
website
will
have
to
be
compatible
with
non-blockchain
users,
so
they
always
will
have
a
login
system
with
username
and
password.
Let's
not
touch
it.
C
Let's
simply
add
some
negotiation
in
this
story.
In
this
game
story.
Let's
say:
king
gamer,
green
gamer
is
an
online
game
store,
let's
see
user
already
use
screen,
gamer,
username
and
password
login,
but
they
can
still
use
the
amazing
bundle.
Token
approve
a
page
token.
C
E
C
Yep
james,
so
thank
you
and
we've
been
looking
for
you
in
a
bit
sorry
a
bit
and
let
me
let
me
share
the
thing.
C
So
so
this
is
a.
This
is
a
modified
example
to
be
compatible
with
token
negotiation
from
the
previous
example
that
we
we
discussed
in
the
last
token
script
meeting
the
previous
meeting
was
about
how
to
build
a
website,
and
that
has
a
token
card
and
a
token
action
in
it
recall
that
james,
yes
yeah.
So
it's
the
same
website
and
also
just
like
the
previous
website.
C
So
this
website
has
an
so
I
imagine
that
there
will
be
two
negotiation
mechanism,
either
automatic
negotiation
or
like
a
or
like
javascript
control
the
negotiation.
This
one
is
the
simpler
one.
This
one
is
the
automatic
negotiation.
C
So
observe
that
in
the
beginning,
as
usual,
the
website
provided
token
script,
and
then
it
has
a
then
it
has
a
declaration
of
what
token
is
accepted.
C
If
you,
if
you
want
to
do
a
future,
but
it's
not
required
and
then
the
then
we're
going
to
also
also
that
providing
token
script
when
you
use
tokens
when
you
use
a
token
script
on
the
web,
it's
not
required
and
that
you
provide
the
token
script
file.
There
are
a
lot
of
reasons
for
this
and
I'll
just
skip
this
for
now,
and
then
we
have
the
tenth
line.
C
The
title,
of
course,
and
then
we
have
the
bootstrap.js
bootstrap.js
is
only
at
work.
If
the
browser
doesn't
have
a
tokenscript
engine,
then
we
have
the
java
actual
javascript,
so
the
actual
javascript
is
between
18
and
27.
F
C
C
Okay,
so
yeah
yeah,
yes,
so
automatic
negotiation,
meaning
that,
since
this
webpage
already
declared
what
token
it
is
interested
in
the
let's
first
assume.
F
C
Is
a
token
script
engine
the
engine
would
interpret
the
which
tokens
needed
and
check
if
the
user,
the
one,
what
user's
wallet
has
the
corresponding
token.
F
C
F
C
Enter
button
here,
which
is
enters
in
is
action
of
the
of
the
entry
token
has
the
corresponding.
C
Javascript
event
link
to
it
and
here
are
the
response,
the
relevant
code,
to
do
when
the
interaction
is
executed.
C
D
C
For
user's
address
so
so
far,
we
are
talking
about
the
case
where
the
user
has
a
token
the
case.
The
token
is
someone
else's
token
is
going
to
be
discussing
separately,
and
then
this
bit
of
javascript
is
able
to
first
find
the
user's
ethereum
address
that
might
trigger
the
browser
to
ask
user
to
choose
a
address.
C
B
B
C
C
B
B
Yeah,
I
understand
that,
but
I
did
not
understand
how
so
so
the
browser
must
be
ethereum
enabled.
You
know
at
least.
C
C
C
Actually,
I
was
expecting
a
hailstorm
of
questions,
so
james
did
this
make
sense
to
you
james.
H
Oh
well,
at
a
at
a
abstract
level,
it
does
yes.
I
mean
I
want
to
see
what
was
inside
that
token
script.
Bootstrap.Js.
C
Oh
okay,
so.
C
It
I
mean
next
meeting
literally
next,
like
right
after
this
meeting
eight
o'clock,
there's
another
meeting
with
oleg,
where
I
explain.
What's
in
the
bootstrap.
H
Okay
with
the.
C
C
Make
sense
for
you?
Yes,
okay,
so
first
and
have
deployed
token
script
in
the
web
like
this
is
optional.
H
Okay,
yeah,
that
makes
sense.
Okay.
The
other
question
that
I
was
thinking
of
is
this:
slightly
below
you've
got
token
card,
equals
new
token
dot,
token
view,
so
I'm
guessing
this
is
something
that
is
a
new
section
inside
took
a
script.
C
Actually,
this
has
nothing
to
do
with
talking
script,
but
no
change
to
the
script.
Okay,
so
so
token
view
is
simply
talking
hard.
I
probably
can
see
it
too
just
to
make
it
more
clearer.
I
think.
H
Then
how
does
it
know
which
one
to
which
one
to
I
presume
it
just
goes
straight
for
the
the
view
rather
than
the
item
view.
C
Yeah
something
like
this:
okay,
maybe
yeah.
Oh
yeah!
This
is
a
not
setting
stone.
So
do
you
did
you
have
the
question
of
how
the
token
object
is
obtained.
H
I'm
guessing
that
the
hang
on
well
token
is
usually
from
yeah
it's
from
the
react
above
it
isn't
it
the
token.
on
activate
you're,
passing
it
in
from
there.
Oh,
yes,
yes,
so
either
the
wallet
or
the
other
wallet
or
the
token
script
bootstrap
is
creating
that
yeah.
C
Yes,
it's
through
a
negotiation.
The
negotiation
is
simply
a
fancy
word
to
say
in
this
case
to
say
that
the
screen
pops
up
the
list
of
entry
tokens
and
say
if
you
want
to
use
one
of
them
on
this
website
yeah-
and
this
is
an
this-
is
not
an
automatic
negotiation.
C
You
will
need
to
start
like
something
like
this,
which
is
injected,
and
that
allows
you
to
do
things.
For
example,
if
you
have
an
application
where
you
can
bundle
a
lot
of
tickets
into
a
ticket
bundle,
so
imagine
that
five
ticket
tokens
goes
in
and
one
techie
bundle
token
comes
out.
Then
you
will
need
a
negotiator,
because
this
is
not
automatically
negotiated,
because
it's
not
the
website
says
that
okay,
I'm
interested
in
the
tickets,
you
have
diva
ticket
or
whatever,
but
it's
like
you
get
a
container
and
you
get
plus
button
every
time.
H
Yeah,
that
makes
sense,
so
I
can
see
how
the
wallet
would
produce
that
would
produce
a
list
from
that.
Yeah.
C
C
C
E
C
C
C
Yep,
so
that
would
be
the
this
is
also
what
you
have
in
mind
right.
C
Yes,
okay,
so
argument
is
that
you
have
one
one
more
function:
layer
and
one
more
object.
C
So
I
hope-
and
there
is
a
way
to
make
javascript
developers
really
like,
doesn't
have
to
learn
anything.
They
just
need
to
know
they
want
to
use
a
token
and
they
can
learn
it
like
in.
Let's
see
three
or
five
minutes
that
how
to
interact
with
the
token
yeah-
and
I
think
this
might
be
popular
but
automatic
negotiations
also
have
the
advantage
that
you
can
index
what
token
is
relevant
to
you.
So
imagine
you
have
a
future
version
of
google,
which
knows
what
token
you
have
in
your
wallet.
Then
it
might.
E
E
C
Is
it
correct?
No,
we
miss
one
thing,
so
I
think
the
second
version
is
longer
than
the
first
and
then
I
don't
want
to
give
web
developers
a
reason
to
to
say,
like
hey,
I'm
not
comfortable
with
this.
E
But
the
second
version
has
a
few
benefits,
because
when
you
talk
about
learning,
both
both
versions
requires
the
developer
to
copy
one
or
two
lines
for
token
negotiation.
The
other
thing
is,
it
seems
like.
The
second
version
is
easier
to
debug.
C
E
C
Yeah
yeah,
it
is
the
case,
but
you
have
to
ask
if
a
web,
if
a
website
that
uses
a
token
must
be
an
application.
C
What,
if
what
sets
our
applications
strictly,
then
we
shouldn't
be
seeing
anyone
using
html
anymore.
So,
let's
say
all
that
then
or
do
you
think
that
the
trend
is
going
towards
that
direction.
E
C
And
how
do
they
provide,
and
let's
say
if
amazon
amazon
is
a
content
website
as
well
as
application,
and
if,
if
it's
built
with
a
single
javascript
line
yeah,
I
think
this
is
a
little
off
topic.
But
if
you
stand
so
how
does
a
google
search
for
content
you
just?
Yes,
you
have
to
have
the
special
interface
on
the
html
page
generated
for
google.
C
E
E
No,
you
don't
have
to
one
way
is
that
that
that's
actually
not
allowed
by
google,
but
one
thing
is
the
other
way
is
even
with
with
with
this
this
architecture
I
described,
you
can
still
modify
your
urls,
even
though
you
don't
reload
your
entire
html
page.
F
C
The
excess,
the
success
of
our
technology
on
that
future
we
may
or
may
not
be
correct.
So
I
hope
there
are
two
ways
to
do
that.
C
Sure
does
that
like
so
so,
so
the
concept
concept
is
not
really
new.
C
Actually
in
2008,
I
think
was
a
time
when
people
believe
that
you
know
2008
was
the
time
when
html5
goes
out
and
one
of
the
major
reasons
camera
5
is
like
w3's
approach
of
using
xhtml
was
that
xhtml
tries
to
view
a
web
page
as
information
set
and
html5
also
see
it
has
information
set
but
more
in
the
application
front,
and
that
was
hugely
welcome,
because
2008
was
the
year
where
people
start
to
see
web
apps
applications
and
and
many
people
believe
that
in
the
future
html
will,
we
will
simply
be
in
memory,
object,
manipulated
by
javascript
and
it
didn't
happen
today.
C
That
we
won't
have
three
minutes
more.
Can
we
is
this
the
the
do?
You
have
any
any
other
questions.
I
might
go
down
this
rabbit
hole
through
this
approach.
So
if
you
see
something
I'm
doing
around,
this
is
probably
the
moment
to
remind
me,
because
this
is
still
incomplete.
C
C
C
C
Hello,
what's
the
first
one
so
currently
view
allows
three
elements:
one.
F
C
Script,
the
other
is
view.
The
third
is
link
right.
Yes,
okay,
let's
link
to
stylesheet
so,
and
you
know
that
we
wanted
to
have
a
manifest
support,
which
is
the
capacity
to
link
other
resources
and.
C
And
instead
of
embedding
them
into
html
into
xml
refer
to
them
by
their
digest,
and
this
this
has
been
going
on
for
a
long
time,
but
we
haven't
got
around
to
do
that,
but
I'm
thinking
of
simply
making
view
a
html
container
so
in
the
future.
C
Anything
that
is
allowed
in
your
camera
inside
it.
Basically,
you
can
refer,
refer
to
a
element,
a
html
file
in
the
view,
or
you
can
embed
it
or
you
can
refer
to
it,
but
I
think
most
people
will
choose
to
refer
to
it
and
it
will
be
a
complete
html
file
that
you
can
open
with
with
the
header
and
body
stuff.
E
C
Sorry,
the
advantage
being
that
it's
easier
to
refer
to
a
external
resource
as
html
and
if
they
want
to
share
the
javascript
code
inside
each
html
file.
They
can
still
do
so
by
a
second
layer
of
link
inside
the
html
files
files.
If
they
want
to
share
the
same
javascript
stylesheet
and
such
html
file
would
require
an
integrity
which
can
be
done
automatically.
E
C
Yes,
it
includes
the
html
tag
in
the
beginning
of
the
file,
so
there's
a
pattern.
There's
a
there's,
a
pattern
here,
maybe
I
can.
I
can
show
it
in
here.
Maybe
this
is
a.
C
C
Input,
okay,
so
the
you
can
choose
either
to
use
this
or
use
this.
So
in
our
case
it
will
be
the
view
html
equals
to.
C
Yeah,
like
oh
so,
your
html.
E
A
C
Javascript
version
they
can
simply
create
a
camera
that
only
has
one
line
which
is
referred
to
the
javascript,
and
this
time
they
don't
have
to
worry
about.
Google
compatibility.
E
E
No
does
it
mean
that
we
have
to
restrict
it
to
one
webview
per
per
item.
C
That's
a
that's
interesting
question.
I
guess
we
we
talked
about
it
second
time
in
the
meeting
we're
almost
running
out
of
time.
That's
a
valid
concern.
Thank
you
and
I
don't
have
a
straight
answer.
Yeah.
C
C
C
C
Well,
the
first
is
developer
comfortability
comfort.
Previously
we,
if
we
allow
segments
like
ssh,
came
out.
I
heard
resistance
from
sangali
and
sangali's
developers
and,
second
being
that
it
kind
of
allow
the
number
of
references
to
be
smaller,
which
might
be
implementation
issue.
C
So
right
now
we
refer
to
scripts
and
styles
in
different
places
and
probably
each
camera.
So
there
are
three
references
per
view.
It
might
becomes
one
reference,
and
if
there
is
one
reference,
the
web
developers
will
be
able
to
use
the
tools
they
are
comfortable
with
in
order
to
debug
multiple
views
at
one
time
and
and
thirdly,
there
is
a
very
small
argument
to
be
made
in
your
favor.
Actually,
then,
a
while
ago,
you
were
against
adding
new
type
of
view
called
guide
or
help,
but
if
you
allow
html,
you
can
simply
add
a
help.
C
Reference
in
header
which
will
be
handled
by
depending
on
the
browser
so
so
html5
allows
every
web
page
to
provide
a
help,
link
and
that
users
who
are
confused
click
that
link.
Then
you
will
see
another
web
page
that
explains
the
current
web
page.
We
can
reuse
that
instead
of
adding
guide
view,
which
you
always
objected,
remember.
E
C
Yeah,
I
can
write
the
list
down.
We
don't
have
to
decide
this
today,
and
this
is
just
one
of
the
half
topic
that
I
can
insert
into
this
meeting
yeah
and
if
you
haven't,
you
can
stay
here.
If
you
like,
and
I'm
going
to
stay
here
until
next
meeting
begin,
you
can
come
back
and
keep
asking
questions
on
this
one
who
whoever
wants
to
live,
can
leave.
Now.
A
D
Gonna
leave
thanks
for
the
meeting
see
you
guys.
C
C
H
This
the
negotiator
that
you
have
there
if
this
is
let's
say
I'm
running-
let's
say
they
don't
have
the
the
selection
filter
that
you
have
at
the
top
and
they're
just
using
this
negotiate
method.
When
this
is
running
inside
the
wallet,
do
we
do
do
we
hook
that
method
and
then
and
then
provide
it
from
inside
the
wallet
itself?
I'm
guessing
that
we
would
do.
H
Okay,
yeah,
that's
fine!
So
basically
it's
it's
going
yeah,
but
it
has
to
pass
through
the
wallet,
though,
if
it's
running
surfaces
running
on
the
wallet,
then.
H
There's
got
to
be
some
kind
of
engine
happening
that
queries
the
wallet,
but
I
does
the
code
go
through
the
wallet
or
does
it
would
you
have
a
bunch
of
javascript
that
has
some
standard
interface.
C
C
C
And
then
the
negotiator,
as
I
explained,
you
cannot
skip
negotiator.
What?
If
the
developer,
choose
to
build
a
website,
and
that
has
only
one
page,
then
you
will
not
be
able
to
change
the.
You
will
not
be
able
to
start
a
new
negotiation
on
a
different
page.
C
So
if
you
say
that
the
checkout
is
done
by
a
special
page
by
a
special
page,
then
the
checkout
page
can
declare
that
they
are
interested
in
some
payment
tokens
and
that's
all
good.
But
if
the
guy
decided
to
write
the
shopping
cart
system
where
checkout
is
in
the
same
web
page
as
the
listing
of
products,
then
without
negotiator,
it
will
not
be
able
to
ask
for
payment
token
during
checkout.
C
Yeah
yeah,
so
it's
so
it's
not
possible
to
get
do
away
negotiator,
but
it's
possible
to
do
away
the
declaration
like
six,
but
I
would
prefer
six
to
be
there
because
I
hope
it
reduced
the
learning
curve
for
some
developers
and
makes
a
token
a
integral
part
of
the
search
engine
enabled
ecosystem.
C
C
E
F
C
C
Foreign,
okay,
so
yeah.
B
C
Have
any
questions
if
you
think
this
is
not
right,
just
tell
me
earlier,
because
next
few
weeks
I
will
be
focusing
on
this
and
then
yeah
just
send
me
a
message
anytime.
A
E
H
Okay,
I'm
gonna
get
going
too
so
talk
to
you
later.