►
From YouTube: Aries JavaScript Meeting
Description
Aries JavaScript Meeting
A
A
A
C
C
C
C
A
A
C
C
A
A
A
C
C
A
A
A
A
E
B
B
B
B
Karim
stekelenburg:
and
that
afj
agent
will
then
karim
stekelenburg:
reach
out
to
a
mediator
and
and
to
an
issue,
etc.,
and
I
think
the
biggest
problem
here
is
that
they
have
problems.
yeah,,
just
the
the
test
generation,
or
like
the
the
afj
agent..
The
whole
test
suite.
Couldn't
fire
request
rapidly
enough.?
So
that's
why
they.
A
A
timo
glastra:.
We
want
to
continue
the
discussion
on
didconfi,
too,
because
I
saw
a
lot
of
prs
have
been
opened
and
and
stuff
going
on,
which
looks
exciting..
I
have
an
issue
I
wanted
to
quickly
discuss.
if
we
have
time,
like
keeping
an
htp
socket
open
when
using
implicit
invitations..
I
have
another
topic,
probably.
A
D
D
A
A
C
A
A
A
A
A
A
A
A
A
B
B
We
need
karim,
stekelenburg:,
yeah,
we,.
We
need
some
funding
to
to
get
through
it..
So
we
publish
this
open
call
where
we
well,
did
little
item
breakdown
per
work
back.,
so
we
have.
basically,.
The
call
is
for
the
the
overarching
image
to
this,
to
make
every
frame
javascript,
compatible
with
the
european
standards,,
at
least
that
are
published
in
the
architecture.
reference
framework.
B
A
Timo
glastra:
yeah.
so
yeah,.
I
think
the
answer
is,
we're
we're
working
on
it
and
planning
to
to
to
continue
that
work.
and
and
yeah,.
Looking
with
with
vendors,
to
secure
funding
to
get
that
implemented.
and
yeah,
that
we'll
just
raise
it
here,,
not
as
a
call
for
funding
per
se,,
because
this
is
like
a
open
source
community
call,.
But
more
of
like
an
update
on
like.
A
C
Ariel
gentile:,
it
can
have
the
I
mean,
if
it
has
the
quality
needed
for
for
integrating
to
into
a
fj
core
repository..
Maybe
we
can.
just
we
can
keep
it
on
a
separate
branch,
right?,
because
I
don't
see
why.
like
ii.
Think
I've
raised
this
question
before,,
because
open
id
is
not
really
area.,
as
most
things
are
not
anymore..
A
A
Timo
glastra:
published
is
a
bit
like.
There
are
really
some
things
in
this
that
are
very
specific
to
our
use
case
and
which
types
of
credential
we
use.,
but
I
think,
yeah,.
We
can
look
at
getting
it
in
soon..
I
would
rather
not
have
it
in
extensions,
repo,,
because
we
don't
have
the
other
packages
like
opening
for
vci,
isn't,
in
extension,
repo,,
and
I
think
everything
that
this
is
an
extension
repo
becomes
like
a
pain
to
keep
up
to
date.
A
A
A
D
Karim
stekelenburg:,
yeah.
and
isn't
it?
also
because
that
is,
I'm
just
remembering
that
now,
like,.
I
think
we
said
a
while
ago
that
extensions
is
for
basically
non
protocol
stuff
that
you
built
on
top
of
of
of
a
fj.
So
helper
stuff,
like
the
red
store,
react
hooks.
and
that's.
This
is
really
a
protocol.
B
B
E
A
A
A
A
A
A
A
A
A
A
B
A
A
C
C
C
C
C
C
C
C
C
A
C
C
C
C
C
C
C
A
A
C
C
C
A
A
C
C
C
C
C
C
C
A
C
A
A
A
A
A
A
A
A
A
C
A
Timo
glastra:
yeah.
timo
glastra:,
but
then
we
extend
that
to
like..
We
then
can
have
2
classes
to
find
for
the
same
type,
and
we
just
filter..
We
don't
only
filter
by
the
the
message
type,,
but
also
by
the
did
conversion,,
because
we
know
message
like
this
is
a
did
confess
we
receive..
So
we
look
for
a
handler
with
did
confit
to,
and
if
I
were
to.
A
A
A
Timo
glastra:
weird.
timo
glastra:,
but
that
way
we
do
make
it
a
bit
more
explicit,
because
I
think,
having
each
protocol
automatically
support
like
didcon
v.
one
and
v.
2,
for
protocols
that
haven't
defined
it,
or,
like
that's
probably
also
gonna,
lead
to
issues
and
by
making
it
more
explicit,.
We
probably
also
discourage
it
a
bit
more
of
like
having
it
all.
Automatically,
automatically
work.
between
the
2
did
conversions.
A
A
A
D
F
Tim
bloomfield:
yeah.,
so
this
is,
is
slightly
more
philosophical.
thought
it
with
did
come
v.
one
and
v,
2.,
but
as
as
a
principle,,
you
really
don't
want
to
over,
invest
and
and
early
adopters
right?.
I
mean,
you
look
at
did
come
v.
one,
maybe
has.,
I
don't
know
1,000
couple
of
1,000
users..
I
don't
know
what
the
numbers
really
are
did
come,
could
have
tens
of
millions
or
hundreds
of
millions,.
So
we
don't
doing
something
just
to
preserve
a
backwards
compatibility.
F
A
A
A
A
C
C
C
C
C
C
A
Timo
glastra:
okay,,
I
will
look
into
that..
There
were
some
things
still
extending,,
but
I'll
look
into
getting
the
wrappers
released..
I
think
we
should
then
do
a
update
to
note
18.
in
the
new
wrappers
release
0
5
0.,
which
is
that
change..
So
we
have
that
sorted
out,
and
then
we
can
take
the
time
to
get
this
config
to
merge..