►
From YouTube: Linking Outside the Box - Eugeniu Rusu, Fabian Kirstein
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
All
right,
so,
let's
get
started
so
the
name
of
the
presentation
is
a
blog
to
enable
with
centralized
social
network
which
might
be
ambitious
but
to
decide.
I.
Think
the
best
I,
like
the
problem
that
we're
facing
the
problem
is
probably
familiar
to
a
lot
of
people
here,
which
is
the
problem
of
centralized
identities
and
what
it
basically
means
it's
more
than
this.
And
then
the
topic
is
kind
of.
A
A
A
As
in
all
of
your
data
is
stored
on
the
identity
providers
servers,
so
if
you
say
I
want
to
delete
a
Facebook
photo,
you
have
to
basically
put
your
trust
into
Facebook
that
they
will
indeed
delete
that
photo
and
that
they
are
not
storing
it
somewhere
shopping.
This
is
required,
so
mostly
trust
towards
your
identity
provider.
So
you
really
have
to
trust
your
identity
provider.
You
have
to
make
sure
that
they
don't
do
anything
with
your
data
that
they
don't
claim.
A
You
cannot
be
sure
about
these
things
and
another
problem
is
limited
portability.
So,
in
a
nutshell,
a
lot
of
times
some
identity
providers
will
not
allow
you
to
export
your
data.
A
simple
example
would
be
again.
Facebook
or
Facebook
has
a
certain
export
profile
feature,
but
if
you'd
like
fully
migrated
from
one
service
to
another,
a
lot
of
times,
you're
not
able
to
get
all
of
your
data
from
them,
it's
difficult
to
to
migrate
fully
so-
and
this
is
how
most
identity
providers
work.
C
A
A
A
Which
is
I
think
a
very
important
point,
so
the
data
should
ideally
be
always
on
the
user
side
rather
than
once,
and
it
should
be
portable
and
not
locked
down
to
one
domain
or
one
location.
So
this
is
this
transpose
is
directly
to
what
we
mentioned
before,
and
this
there's
a
couple
of
ways
to
do
some.
An
ID
and
there's
probably
pin
concepts
for
a
while,
and
one
of
the
ways
is
heavily
promoted
by
a
development
team
at
MIT
led
by
Tim
berners-lee,
which
is
solid
spec
or
the
social
linked
data
specification.
A
A
A
Profile
document,
so
it
needs
to
resolve
to
a
document
that
basically
describes
you
who
you
are,
and
perhaps
some
primitive
amounts
of
that
and
also
link
to
some
other
documents
that
further
describe
those
other
documents
can
don't
have
some
specific
access
control
rules
associated
with
them.
So
this
part
has
to
be
public
so
agent.
It
can
be
accessed
by
anyone
to
get
some
primitive
information
about
you
and
then
the
further
exploration
can
be
restricted
by
access
control
rules
and
then
due
to
the
nature
of
how
the
maintenance
work.
So
no.
A
Perfectly
valid,
but
it
is
not
unique
identifier,
so
the
web
ID
really
defines
where
your
identity
is
stored.
It.
It
basically
said
that
this
is
you
arrive
which
describes
you
and
that's
where
the
entry
points
to
your
identity
should
be
stored.
Now
it
doesn't
really
define
how
your
data
should
be.
Formatted
doesn't
really
define
anything.
It
only
says
it
is
there
where
every
agent
hosts
their
own
identity.
A
So
if
an
agent
wants
to
retrieve
some
data
from
you,
he
should
know
how
you
stole
your
data,
you
should
be
able
to
parse
it
read
it
and
make
sense
of
it,
and
if
service
provider
wants
to
do
the
same
should
be
able
to
do
the
same
thing.
So
basically
they
have
to
speak
the
same
language
in
a
nutshell,
they
all
have
to
understand.
This
comes
pretty
natural,
which
is
actually
that
word,
which
you.
E
A
Needs
to
be
used
to
should
be
used
to
describe
it,
so
your
profile
ideally
should
be
stored
in
rdf
for
ya
and
a
difference
serialization
format
such
as
RDF
XML,
but
it
should
be
when
it
linked
data.
It's
the
first
point
and
then
there's
a
second
point:
the
ACL
file,
so
access
control
list,
so
files
that
define
who
is
allowed
to
do
what,
with
some
files
that
you
store
in
your
system,
are
also
valid
links,
data
and
the
data
in
tandem
with
whether
it
simply
makes
sense
because
we
linked
data.
A
A
So
if
you're
taking
data
and
applying
the
web
ID,
which
you
arrive,
identified
users
that
works,
it
is
a
easy
way
to
show
social
relationships
like
this,
because
now
a
parser
could
this
statement.
The
jumpsuit
ratings
card,
which
is
also
validly
data,
parsed
debt
and
jump
on
and
on
and
on,
and
make
meaningful,
perhaps
extract
some
meaningful
information
out
of
that.
A
So
exactly
that's
that's.
Basically,
this
tag
that
is
defined
by
social
in
data
were
solid,
so
they
used
RDF
to
store
your
file
to
store
your
duty,
sterilizing
information.
They
use
web
IDs
to
point
accusers
identifies
for
entities
in
the
system.
They
use
access
control
lists
to
manage
the
for
accession,
which
basically
is
just
another
RTF
file
that
says
that
this
and
this
and
these
agents
are
allowed
to
divisionism
these
things
on
these
files,
everything
being
a
very
pure
right,
good
thing
that
comes
out.
A
A
Solid
envisions
a
world
where
every
user
has
their
data
on
their
side
in
predefined
format
and
applications
can
simply
hook
into
that
data.
So
applications
can
simply
request
access
to
your
server
to
your
user
space,
get
the
data
and
do
some
computations
on
that
or
perhaps
display
it
in
a
graph
or
perhaps
it
depends
on
the
application.
A
System
where
everyone
has
their
identities,
which
they
field
over
time,
they
want
the
one
identity
and
then
a
bunch
of
applications
that
they
can
use
to
manage
different
areas
and
aspects
of
their
identity
and
different
different
functionality
comes
from
different
apps.
We
don't
have
to
use
this
big
monitors
anymore,
and
then
we
talk
about
Yocum
now.
So
let's
ask:
how
do
we
get
into
this
picture
and
they're
also
do
a
very
short
demonstration
if
that
internet
allows
us
to
do
so.
D
A
Renders
it
so
at
the
moment
I'm
a
simple
note
which
doesn't
really
do
anything,
doesn't
really
have
any
any
connection,
so
we
can
do
things
like.
Obviously
we
can
look
at
my
profile
where
there's
some
primitive
information,
so
this
would
be
my
my
web
ID,
my
email
and
that's
about
it.
Show
you
it's
a
very
sort
of
blank
profile
into
things
like
link
to
other
valid
ID
profiles,
so
I
think
we'll
linked,
probably
two
or
three
to
this,
to
really
explain
the
interoperability.
The
first
one
will
be.
Probably
you
are
him.
A
A
Yes,
actually
I
can
started
to
whatever
data
you
at
him
made
public
to
me
and
if
I
go
to
his
profile,
we
can
see
that
we
can
explore
his
that
already
has
a
number
of
connections
to
a
lot
of
other
entities,
all
of
these
being
other
people,
some
of
them
self
hosting
some
of
them
posting
their
data,
then
to
provider,
and
then
some
general
knows
that
he
created
some
pieces
of
information.
His
apologies
to
his
servers
if
I
get
back
to
me.
A
A
No
server
forgets
I'm
talking
whatever
that
you
make
public
comes
back
to
us
and
we
obviously
can
render
some
of
it.
So
this
is
what
we've
extracted
from
his
profile
files.
This
is
quite
a
simple
computation
is
really
snuffing.
Nothing
crazy
and
example.
We
have
another
identity,
that's
hosted
on
the
freedombox
right.
There
is
the
thing
that
kind
of
has
a
circle
around
it.
It's
a
personal
server,
it's
post
back,
it's
a
little
personal
server
server
on
it.
So
if
I
connect
it
and
this
nice
little
feature,
it's
really
not
a
good
present.
A
A
A
Sorry,
maybe
we
can
get
it
working
a
bit
later.
We
can
show
it
to
you.
People
want
to
see
things
bling,
but
this
is
so
you
can.
You
can
connect
to
other
people
who
have
their
identities
on
different
in
different
locations.
So
a
very
extreme
example
would
be
the
freedombox,
which
is
a
server
that
a
self
host
it
has
a
number
of
privacy.
Related
functionality
features
only
it's
developed
by
the
freedombox
foundation.
A
A
A
So
this
URL
is
this.
This
is
basically
what
I
know
this,
which
is
publicly
available,
so
people
can
anyone
can
connect
to
this
node?
Anyone
can
visualize
this.
Not
anyone
can
can
see
this
node,
which
is
what
you
would
expect,
and
so
what
you
can
do
it
and
you
can
edit
the
privacy
settings
of
this
node
and
element
is
public.
I
can
make
it
private,
where
only
icon
at
this
know
that
I
can
actually
add
particular
format,
authorization,
the
people
I
know
the
general
just
web
IDs
out
there
in
the
world.
A
A
A
A
Adding
valuable
information
about
you
and
then
you
can
use
this
identity
to
to
interact
with
a
lot
of
applications
that
are
out
there
in
the
wild.
You
don't
have
to
create
a
new
identity
with
every
application.
You're
using
you
don't
have
to
register
again.
The
dream
would
be.
You
basically
go,
and
you
say
you
connect
with
my
web
ie
and
you'll
be
kind
of
like
the
Facebook
Connect,
but
monkeyville.
A
It
is,
to
a
certain
extent,
because
you
don't
rely
on
a
centralized
identity
provider,
some
people
it
isn't,
because
if
you
rely
on
your
neck
and
some
people
would
say
that
feeling
reliable
electricity
providers
on
a
support,
but
the
peaks
are
weak
point
here
to
a
certain
extent
is
that
it
will
not
depend
on
DNS.
This
is
one
problem
of
the
current
system.
Another
problem
of
the
current
system
is
that
your
identifier
is
this
tightly
coupled
with
the
Transfer
Protocol
with
a
protocol.
So
your
idea.
A
Forward,
slash
forward
slash
whatever
this
is
the
problem,
there's
no
layer
of
abstraction
between
your
identifier
and
the
protocol,
so
there's
no
layer
of
abstraction
between
who
you
are
and
where
you
are-
and
this
is
probably
not
any
case
your
your
server
goes
down.
You
won't
change
by
different
web
ID.
What
happens
if
you
want
to
change
the
different
domain
name?
What
happens
all
of
the
connections
you've
built
until
now
are
broken.
A
A
Employed
this
web
ID
TLS,
which
basically
uses
client
certificates
to
authenticate
and
they
use
I,
don't
know
if
anyone
is
familiar
with
client
certificates
pesach.
This
is
this
is
a
problem.
There's
no
easy
way
to
terminate
the
session.
There's
no
easy
way
to
logout.
There's
no
easy
way
to
subtract.
This
problem
will
build
a
proxy
which
the
user
self
host
on
which
we
use
as
well
for
development
purposes,
but
the
properties
is
quite
straightforward.
A
A
A
So
this
has
aspects
of
the
web
of
trust.
There's
a
lot
of
agents
interacting
between
each
other.
You
can
link
to
other
people.
You
can
give
permissions
to
one
another.
The
idea
of
reputation
and
claims
comes
kind
of
natural
to
this,
so
would
be
really
cool.
If
agents
could
state
something
about
another
agent,
and
this
is
possible
to
a
certain
extent
with
the
current
implementation.
The
trick
is
that
this,
it's
still
on
file
systems
its
own
server.
So
there's
no
in
case
of
hi
Jackson
in
case
of
service
being
compromised
in
case
of
malicious
ages.
A
Difficult
a
one
way
to
fully
verify
that
that
data
hasn't
been
tampered
with
this
another,
so
without
making
claims,
there's
a
way
to
do
claims.
Now,
with
the
current
solid
infrastructure,
the
question
is:
could
it
be
improved
and
making
payments
is
something
that
kind
of
comes
to
your
mind
as
well,
because
this
is
all
about
sharing
information.
This
is
all
about
sharing
data.
A
I'm
gonna
do
this
on
that,
so
there's
a
potential
so
early
for
for
payments,
but
the
biggest
issue
is
this
DNS
dependency,
and
this
is
strong
coupling
between
who
you
are
and
where
you
are
so
what
we
do
here
now
we
were
together
with
five
members:
gonna
come
in
a
minute.
Is
we
kind
of
started
looking
at
that?
It's
only
served
in
the
starting
phase.
There's
no
revolution
coming
search
waiting
for
this.
A
E
E
The
digital
identity
in
the
blockchain-
and
there
are
maybe
third
time's
involved
for
payment
and
some
things
and
maybe
pot
again-
is
this-
that
ID
proxy
and
because
again,
the
debate
is
very
it's
complicated
to
use.
Nobody
actually
does
it.
You
have
to
install
something
in
the
browser
certificate
and
so
on
so-
and
this
is
also
an
issue-
you
may
want
consult
of
a
blockchain
and
we
wrote
down
some
general
considerations
about
it
in
the
first
place.
E
E
E
Song
track,
and
especially
lemon
balm
is
how
can
you
search
for
other
identities,
because
now
you
need
this
net
ID,
if
you,
if
you
would
put
it
in
a
sample
instance,
you
have
second
instance
again
so,
but
you
just
need
it.
I
give
junior
type
in
your
a
key
that
I
do
eurocom
and
yeah
what
we
first
did
kind
of
state-of-the-art
analysis.
E
You
probably
know
some
of
the
projects
I
bet,
there's
a
new
part
and
but
the
landscapes,
the
length
type
of
people
working
with
identities
and
digital
engine
benefit,
but
we
focused
on
the
most
prominent
ones
and
blocks.
Take
it
from
based
on
Bob
James
consensus.
Is
the
company
behind
you
part
and
other
products
and
important?
Also
very
interesting
is
JSON
web
tokens
that
you
put.
If
you
don't
know
it,
and
you
probably
similar
that
approach,
they
want
to
do
digital
identities
and
the
main
mission.
E
There
is
especially
it's
the
common
it's
similar
to
our
vision
that
you
want
to
replace
come
up
with
a
name
password
audiences.
You
just
want
to
block
in
a
different
way,
so
we
don't
have
to
remember
the
password
all
the
time
and
a
concept
is
the
smartphone.
You
have
to
private
key
on
the
smartphone
and
just
like,
like
with
the
Watts.
E
E
They
passed
the
contract
and
you
can
recover
your
identity
because
actually
I
may
be
somewhere
here,
and
you
have
this
little
social
network
which,
as
part
of
your
private
key,
so
they
are
heavily
working
on
key
recovery,
which
is
awesome
issue
for
us,
and
it's
basically
all
of
this,
because
if
you
have
somehow
a
digital
identity
in
the
blockchain
and
you're
facing
the
issue,
how
to
lock
in
how
to
do
I,
you
have
indicated-
and
we
talked
to
with
helium
guys.
Here
we
talk
to
you
pod
and
basically
it
comes
down
to
this.
E
You
still
have
to
save
your
planet
key
somewhere.
There's
no,
actually,
there's
no
way
around
it.
You
can
do
it
in
a
browser
on
you
can
do
it
in
this,
probably
can
have
it
on
a
smartphone.
You
can
write
it
down,
but
this
is
like
some
of
the
conclusion
for
our
little
project
that
you
still
have
to
do.
E
E
All
three
of
them,
which
is
secure,
but
our
identifying
it
still
not
that
you
meaningful,
so
what
we
did
and
we
decide
that
we
only
because
the
project
is
just
five
months
and
that
we
cannot
change
the
solid
in
the
body
infrastructure.
We
have
to
keep
it
as
it
is
it's
based
on
yes,
so
we
designed
an
intermediate
solution
so
to
step
towards
a
completely
subservient
identity.
So.
E
We
took
concepts
from
you,
part
blocks
the
IDE
and
we
didn't
use
you
part,
because
we
didn't
use
it
directly,
because
it's
a
closed
system
somehow
that
this
app,
you
need
to
use
this
app
and
they
advise
us
that
we
are
not
good
idea
to
use
the
contracts
directly
because
I
cannot
ensure
the
security.
If
you
don't
use
that,
so
we
did
our
own
complex
and
based
on
their
concept
and
what
we're
doing
we
are
storing
the
backward.
E
E
Contracts,
we
will
also
offer
the
seats
knowledge.
You
can
see
this
there
to
to
get
your
private
key,
it's
self-service,
so
you
don't
have
to
write
it
to
help,
and
we
have
does
that
ID
proxy,
which
will
not
store
any
longer
the
the
keys
of
the
net
ID,
but
the
key
sign
in
the
contract
and
just
take
each
I'm
using
the
consensus
with
you
a
moment
to
talk
to
the
staff.
Note
and
the
private
keys
are
only
store
for
the
browser
and
communicating
and.
E
E
E
B
E
E
C
C
C
E
D
E
F
E
A
F
C
C
E
C
C
E
E
E
Offering
this
this
method
to
generate
a
twelve
word:
human
readable
seed,
it's
12,
english
words
and
we
are
actually
offering
to
store
this
seat
and
not
the
where
we
so
take
cryptic
private
key.
But
you
have
to
remember
or
write
down
the
scene
yeah
it
still,
let's
still
state-of-the-art
brain.
We
really
talked
to
a
lot
of
aetherium
guys
here
and
it's
like
this
and
you
thought
is
working
on
it,
but
they
told
us
that
it
would
take
at
least
a
couple
of
months
until
there.
F
F
E
A
Basically,
non
human
readable
identify
that
we
solve
different
data
structure
on
different,
not
change.
So
there's
effort
on
that.
There's
also
XDI,
which
is
an
alternative
card
yeah
similar
things,
but
in
the
long
pitch
that
ideal
be
to
kind
of
a
couple
them
or
at
least
introduce
a
certain
amount
of
portability.
Where
you
can
change
alright,
then
you
can
change
your
name.
A
The
golden
the
holy
grail,
for
say
at
least
for
us
at
this
point
in
time,
so
we're
doing
the
little
exploration
step
by
step.
This
was
a
very
simple
straightforward
example
of
integration:
1
to
see
how
this
works,
how
I
will
this
use
our
needs?
So
this
is
by
no
means
a
state
of
the
art.
This
is
by
no
means
a
finished.
Project
is
rather
just
kind
of
a
big.
A
Where
we
have
a
bunch
of
identities,
all
the
news
absolutely
and
it's
still
very
much
development.
You
know
you
see
very
smart
people
behind
very
smart
people
working
on
it
so
and
it
shows
promise
for
a
certain
extent,
and
this
is
really
the
and
this
to
us.
This
is
subjectively
the
weak
point,
because
some
people
would
argue
that
yeah
and.
D
Actually
think,
as
far
as
problems
with
relying
and
kind
of
web
infrastructure
going
over
lines,
nto
and
DNS
is
a
smaller
one.
The
other
one
is
I
feel
like.
While
you
have
reliance
on
any
kind
of
server
or
it's
not
fully
self
sovereign.
Just
because,
like
regular
people
cannot
operate
their
own
servers
like
I
try
to
operate
my
own
store
and
everyone
right.
So
like
it's.
If
you
build
toward
that
model
or
like
it's,
not
it's
the
best,
you
can
possibly
give
us
realistically
federated.
A
There's
some
incentives
that
I
get
like
in
freedom
box,
which
is
you
know
they
sound
like
out
of
the
box
and
you
plug
it
into
the
internet
than
you
have
your
so
they
survive
in
today's.
It
really
tries
to
abstract
a
little
bit
technical
concepts
for
a
lot
of
people,
but
they're
still
troubleshooting,
but
still
maintained
so
in
it
has
usually
I
mean
it
has
challenges.
I
think
you
make
a
very
good
point
here,
actually
that
as
long.